CICS backtrace and PurePath
The following figure shows a CICS Service-Level Backtrace that was started by an MQ call. The message was initially put into the queue by a Java application, so the CICS PurePath® distributed trace has been linked to the Java PurePath distributed trace by MQ tagging. You can see all the way back to the Mobil App.
In the row of the top service, select the Analyze menu and select Distributed traces. You will see the CICS distributed traces requests. To explore the PurePath distributed trace and its timings, select a distributed trace from the list or select Trace from the button menu. If you hover over any line you see the timings for that process.
Selecting a distributed trace name, you will get a more detailed view with tabs. It defaults to the Summary tab.
The following image show the details displayed at the Summary tab. You can see all the metadata including the transaction ID, job name, system ID, task ID, unit of work ID, and more.
If you select Code Level this will show you the details of the calls made. You can select on any of these to see the metadata of each call.
Example Transaction Flows
The following screenshots show the transaction flow from a web application through MQ to CICS with DB2 calls.