Connection monitoring

The types of activities monitored across a connection are:

• distributed transaction processing (DTP)

  DTP refers to a transaction on one CICS talking to a transaction on another CICS. The XEIIN and XEIOUT exits are used for DTP data collection.

• distributed program link (DPL)

  DPL refers to a program running on one CICS that does an EXEC CICS LINK to a program defined as remote, or the EXEC command supplies a SYSID. Connection timing for CICS TS 3.1 and earlier uses the XEIIN and XEIOUT exit points. CICS TS 3.2 and later uses the XPCREQC exit point.

• transient data (TD) request function shipping

  TD queue requests can be function shipped to another CICS if the TD queue is defined as remote, or a SYSID is specified on the EXEC CICS statement. TD request processing is done with a CSMx transaction on the remote system. TD function shipping data is trapped with the XEIIN and the XTDEREQC exit points.

• temporary storage (TS) request function shipping

  TS queue requests can be function shipped to another CICS if the TS queue is defined as remote (or indirect), or a SYSID is specified on the EXEC CICS statement. TS request processing is done with a CSMx transaction on the remote system. TS function shipping data is trapped via the XEIIN and the XTSEREQC exit points.

• file request function shipping

  File requests can be function shipped to another CICS if the file is defined as remote, or a SYSID is specified on the EXEC CICS statement. File request processing is done with a CSMx transaction on the remote system.

• IBM IMS/DBCTL request function shipping

  Database access is done with the EXEC DLI or CALLDLI commands specifying a PSB. A DFHPSBxx table specifies the SYSID where the PSB is located. The shipped request runs under a CSMx transaction on the remote side. The XDLIPRE and XDLIPOST global exit points are used to gather data.

  To gather connection timing for remote DBCTL requests, PSB=YES must be specified in the CMRSOPT.

• interval control request function shipping

  Interval control requests can be function shipped to another CICS if a SYSID is specified on the EXEC CICS statement. Interval control request processing is done with a CSMx transaction on the remote system. Interval control function shipping data is trapped with the XEIIN and the XICEREQC exit points.

For each connection used by a task, the total time and count for all activity is accumulated, along with each individual activity type’s time and count. The time represents the elapsed time from when a request leaves the sending CICS until the request returns.

This section contains the following topic: