CICS Transaction Server sensor

The CICS Transaction Server sensor captures MQ, DB2 and CICS API calls.

Sensor configuration

To edit the System Profile specific settings, right click you System Profile, and select Edit System Profile > Agent Group/tier > Sensor Configuration and then select the CICS Transaction Server item in the Sensor Configuration list.

Sensor properties

  • Enable DB2 sensor: Enables/disables DB2 API details. If disabled, no DB2 API call information reports in the traces produced by any of the enabled sensors.

    • Enable aggregation: Produces a summarized report of DB2 activity. For example if a CICS transaction issues 50 INSERT API calls, one node is produced to show all 50 calls instead of 50 separate nodes per each insert. Aggregation reduces the number of events processed by the AppMon Server, and thus improves overall performance on the AppMon Server. Return values are not available in aggregation mode.
    • Capture DB2 fetches: When enabled each DB2 fetch causes data to be sent to the AppMon Server. In CICS systems that have transactions which issue an excessive number of FETCH calls, performance can be greatly improved by disabling the capture of DB2 fetches.
  • Enable DL/I sensor: Enables/disables CICS DLI API details. If disabled, no DL/I API call information is reported in the traces produced by any of the enabled sensors.

    • Enable aggregation: Produces a summarized report of DLI activity. For example if a CICS transaction issues 50 ISRT API calls, one node is produced to show the 50 calls 50 separate nodes per each call. Aggregation reduces the number of events processed by the AppMon Server, and thus improves overall performance on the AppMon Server. Return values (DL/I status codes) are not available in aggregation mode.
  • Enable SOAP sensor: Enables/disables the SOAP Sensor, which traces all outgoing SOAP requests originating from CICS transactions that are being traced by any enabled sensor; and all incoming SOAP requests that have an HTTP header with an AppMon tag. Note that no inbound SOAP request tracing occurs unless the request flows through a CICS SOAP pipeline that has been reconfigured to include the ZDTSOAPH header program.

  • Enable CTG sensor: Enables/disables the CTG Sensor. You must install the Java Agent in the CTG. For more information, see CICS Transaction Gateway.

  • CICS subagent name format: Adapts the CICS subagent name to append either the SubSystemID, or the Jobname, or the SNA ID. This property must be set in the agent mapping of the zRemoteAgent(s). The CICS Transaction Sensor must be placed first. The change takes effect upon the next CICS subagent registration event.

  • Enable Tracing LE Programs: Enables/disables the LE Sensor, which traces COBOL and PLI dynamic calls through the LE runtime.

    • Program include filters: A list of program name patterns to be traced by the LE sensor when they are invoked through LE runtime dynamic calls. Each entry in the list may be a program name or a program name prefix with an asterisk at the end. The LE sensor ignores LE dynamic calls to programs whose names do not match an entry in the list. By default, all program names are enabled.
    • Program exclude filters: A list of program name patterns to be excluded from tracing by the LE sensor. Each entry in the list may be a program name or a program name prefix with an asterisk at the end. The LE sensor ignores programs whose names match an entry in the list. If a particular program name matches both the include and exclude lists, the exclude list takes priority and the program is ignored.

    Note that any PL/I program that is FETCHed to be used as table instead of being executed MUST be excluded, or the associated application may not function properly

  • Enable MQ sensor: Enables/disables the MQ Sensor.

    • Queue include filters: A list of queue name patterns to be traced. Each entry in the list may be a queue name or a queue name prefix with an asterisk at the end. The MQ sensor ignores messages from queues whose names do not match an entry in the list. By default, all queue names are enabled.
    • Queue exclude filters: A list of queue name patterns to be excluded from tracing. Each entry in the list may be a queue name or a queue name prefix with an asterisk at the end. The MQ sensor ignores messages from queues whose names match an entry in the list. If a particular queue name matches both the include and exclude lists, the exclude list takes priority and transactions that process this queue are ignored.
  • Enable transaction start sensor: Enables/disables the transaction start sensor, which traces any transaction that matches the transaction filters without setting a tag to link it to a previous path. Set filters carefully as this interferes with other sensors such as MQ and SOAP that need to set tags after the start of a CICS transaction. It does not affect the CTG sensor or tracing of transactions that are linked to a parent CICS transaction that issued a START or DPL LINK request. This sensor can be used to start a path to trace a CICS transaction that cannot be linked to previous activity outside CICS. Note that the CICS and IMS ADK may be used to support tagging of transactions that use unsupported protocols as an alternative to the transaction sensor.

  • Transaction filter: A list of transaction code patterns to be traced. Each entry in the list may be a transaction code or a transaction code prefix with an asterisk at the end. The TX sensor ignores transactions whose names do not match an entry in the list. An entry with a single asterisk (*) is ignored because monitoring CICS internal transactions is not recommended.

  • Enable Node Limit: Sets a limit on the number of nodes in a single transaction within CICS. The default limit is 500.