Tracking CICS transactions coming in without an upstream trace context

Edit online

You can edit the AGMSYSIN parameter data set to enable CICS® transaction monitoring that comes in without any upstream trace context.

Note: MQ polling scenarios are not supported.

Modify the AGMSYSIN parameter data set that you use to configure the CICS TS Data Producer. Use the INCLUDE and EXCLUDE statements for filtering the CICS transactions with the NOCTXTRACE keyword set to YES.

Note:

Configure the NOCTXTRACE filter in the first CICS region to support tracking CICS transactions coming in without an upstream trace context.

Refer to the following examples to use the filters:

Table 1. INCLUDE statements
Example Description
TYPE=I,TRANSID=XYZA,NOCTXTRACE=YES Monitor CICS transaction XYZA coming in without an upstream trace context.
TYPE=I,TRANSID=XYZ*,NOCTXTRACE=YES Monitor CICS transactions which have the first 3 characters as XYZ coming in without an upstream trace context.
TYPE=I,TRANSID=XY*,NOCTXTRACE=YES Monitor CICS transactions which have the first 2 characters as XY coming in without an upstream trace context.
TYPE=I,TRANSID=X*,NOCTXTRACE=YES Monitor CICS transactions which have the first characters as X coming in without an upstream trace context.
Table 2. EXCLUDE statements
Example Description
TYPE=E,TRANSID=XYZA,NOCTXTRACE=YES Do not monitor CICS transaction XYZA coming in without an upstream trace context.
TYPE=E,TRANSID=XYZ*,NOCTXTRACE=YES Do not monitor CICS transactions which have the first 3 characters as XYZ coming in without an upstream trace context.
TYPE=E,TRANSID=XY*,NOCTXTRACE=YES Do not monitor CICS transactions which have the first 2 characters as XY coming in without an upstream trace context.
TYPE=E,TRANSID=X*,NOCTXTRACE=YES Do not monitor CICS transactions which have the first characters as X coming in without an upstream trace context.
Note:

  • By default, if you do not define a filter, then IBM® Z APM Connect does not trace the transactions coming in without an upstream context.

  • If you configure TRANSID=*, then IBM Z APM Connect ignores the record and displays an error message.
  • You must configure the NOCTXTRACE value as YES or IBM Z APM Connect ignores the record and displays an error message.
  • You can configure a maximum of 250 INCLUDE and EXCLUDE statements respectively, including the DTP filters.

  • In the AGMSYSIN parameter dataset, the EXCLUDE statements take precedence over the INCLUDE statements.

  • For CICS No Upstream context tracking, the AGMSYSIN parameter dataset must be unique for each CICS region. Because the INCLUDE and EXCLUDE statements in the AGMSYSIN parameter dataset do not specify the CICS regions. The CICS transaction IDs in the INCLUDE and EXCLUDE statements pertain to the CICS transaction that it is running in the CICS region to which the AGMSYSIN is allocated to.

  • Only the first * is taken into consideration for pattern matching. Any string after the * is ignored. For example, TRANSID=AB*C is same as TRANSID=AB* (All no upstream trace context transactions starting with AB will be tracked).
  • You can use the modify command on the console to run the AGMU,FILTER=DTP,LIST command in a CICS TS region to display the transactions given in the AGMSYSIN.
  • You can use the AGMU,STOP command followed by the AGMU,START command to pick up the changes to AGMSYSIN. There is no need to recycle the CICS region.