Supported transaction tracking flows

CICS-related transaction flows

• Transactions entering CICS® Transaction Server for z/OS through HTTP, SOAP, or JSON distributed entry points, through z/OS Connect Enterprise Edition, and through CICS Transaction Gateway.

• Transactions flowing into Db2®, IBM MQ, IMS DB, outbound webservices, and VSAM I/O timing from CICS Transaction Server for z/OS.

• Downstream transactions that are started over DTP and DPL can be tracked, additional configuration is needed for DTP downstream transactions. For more information about the configuration, see Configuring Z APM Connect CICS TS Data Producer to filter DTP transactions.

• Transaction entering CICS Transaction Server for z/OS through IBM MQ for z/OS. For more information, see Tracking IBM MQ to CICS.

• Downstream transactions from one CICS region to another with IBM MQ as the intermediary. For more information about the configuration, see Tracking CICS to MQ to CICS transaction flows.

• Downstream (distributed) applications monitored by other Instana agents when the transactions enter CICS Transaction Server for z/OS through IBM MQ for z/OS. See Tracking CICS to MQ to an Instana monitored application.

• Transactions entering the CICS Transaction Server for z/OS without an upstream trace context. For information about configuring the functionality, see Tracking CICS transactions coming in without an upstream trace context.

IMS-related transaction flows

• Transactions entering IMS Connect through an IMS Transaction Manager resource adapter (IMS TM resource adapter).

• Transactions entering IMS Connect through z/OS Connect Enterprise Edition.

• Transactions flowing into IMS through IMS Connect.

• Transactions flowing into IMS accessing IMS Full-function Databases.

• IMS PLEX \(IMS to IMS\) transactions.

• IMS FastPath \(FP\) transactions.

• IMS FastPath DEDB and MSDB Databases.

• IMS Full Function to FP DEDB and MSDB Databases.

• IMS MQ Bridge Transactions.

Transaction flows to Db2 for z/OS through JDBC calls

• Inbound transaction flows to Db2 for z/OS directly via Type 4 JDBC calls. The following transaction data will be reported to the Instana backend:

  • Performance metrics for SQL calls made by the application.

  • Db2 timeouts and Db2 deadlocks including blocker and waiter data.

  

• Transactions tracing for WebSphere® Application Server (WAS) on z/OS or WebSphere® Liberty (Liberty) on z/OS. The following transaction flows are supported:

  • Webservices HTTP(S) calls from WAS or Liberty Java application into CICS.

  • JDBC calls from WAS or Liberty on z/OS to Db2 for z/OS.

Available components

IBM Instana Observability for z/OS utilizes core Z APM Connect Components that work seamlessly with Instana.

• Components on z/OS side:

  • Z APM Connect Base

  • Z APM Connect CICS TS Data Producer

  • Z APM Connect IMS Data Producer

  • Z APM Connect Interceptor for tracking z/OS Connect EE

  • Z APM Connect request monitoring exit (server-side) for tracking CICS Transaction Gateway (CICS TG)

  • IBM MQ Monitoring Subsystem component

  • Z Common Data Provider

• Components on distributed side:

  • Z APM Connect Distributed Gateway

  • Z APM Connect request monitoring exits (client-side) for tracking CICS Transaction Gateway (CICS TG)

For a detailed introduction about each component, see Z APM Connect components.