Track your transaction's origin and route
JanakiS 27000496GC Visits (1385)
In any TXSeries deployment, it's a common practice to have a transaction span across multiple TXSeries regions on the same machine or across multiple machines. For example, a transaction originating from a client (say a CTG client) traverses more than a region before completing the work.
Do you feel dizzy with such transactions travelling across to multiple regions? Is a multiple hop configuration turning out to be tough to manage? Perhaps, you would like to track where the transaction originated and the peer region who passed on this request. Such a transaction tracker would definitely prove handy in a complex multi-region configuration.
TXSeries for Multiplatforms V8.1 provides you a transaction tracking capability, made available through Distributed Program Link (DPL) user exits. If you are aware of Remote Task Information feature in TXSeries for Multiplatforms V7.1, you're almost there.
With the transaction tracking capability of TXSeries V8.1, information related to peer region and the originator (client) is published through DPL user exit fields. These fields are defined in the header file cicsue.h (present in <product install path>/include). Also, these fields can be availed as and when required. With TXSeries 7.1, similar information was available through Remote Task Information extra partition TDQ file (CRTI.out).
Note that this capability is provided only for cics_tcp and ppc_tcp communication protocols.
Interested to explore / exploit this capability? Find more details here.