Track your transaction's origin and route – How do you do it?
JanakiS 27000496GC Visits (1767)
You'd have come across the Transaction tracking capability provided with TXSeries for Multiplatforms V8.1. This capability is the apt choice for you to track the traversal route of your transaction in a complex multi-region configuration.
If you have this requirement: “To locate the transaction's origin and peer details at any region”, then what you need to do is just 3 steps.
Enable Remote Task Information. (i.e. in the front end region, set EnableTaskInfo=yes in RD stanza and SendTaskInfo=yes in the CD stanza entry pointing to the back end region).
Customize the DPL user exit to utilize the newly published fields in cicsue.h for Remote Task Information.
These fields are defined in a new structure called RemoteInfo within the DPL user exit structure.
(Tip: Wondering how to customize/configure a user exit? Here, you go).
Now, cold start the region and check the peer and origin information at each region.
So, considering this example in figure 1, at region 2, information gathered would be as follows:
while at region 1, only origin information (pertaining to CTG) will be available and peer information will remain empty, since it is not relevant.
Now, with this sort of information, you must be sure to locate the whole traversal route of the transaction. Isn't it?