Transaction tracking can assist in diagnosing problems that sometimes occur when complex distributed transactions spread across a CICSplex.
Transaction tracking is available for Java™, ECI V2 and .NET client requests, through the availability of origin data to the monitoring exits. Origin data associated with each transaction is forwarded by CICS® on each subsequent DPL between CICS regions. This enables tracking of requests associated with a given client application, as they pass through the Gateway daemon, through the connected CICS servers, to the target programs in CICS.
Any tasks in CICS initiated using ECI through IPIC connections have associated origin data in CICS carrying a fully-qualified APPLID field. Origin data in CICS can be viewed using CICSPlex® SM or using the INQUIRE ASSOCIATION SPI command. You can also use the CICS Transaction Gateway request monitoring exits in the Gateway daemon to view the origin data, and Java client applications have access to origin data in their request monitoring exits. These commands allow an administrator to identify the Client application that originated a particular task.
If you specify an APPLID and APPLID qualifier for the Client application, they are used in the origin data. If they are not specified, but you are running in remote mode and the values are specified in the configuration file, these values are used. If an APPLID and APPLID qualifier are not specified at all, the values automatically generated by CICS for the IPIC connection are used. The fully-qualified APPLID can be viewed in CICS using the CEMT INQUIRE IPCONN command. It is displayed in the Applid and NetworkId fields.