Monitoring the output communications area
A routed transaction can pass information back to the dynamic transaction routing program in its output communications area. When invoked at transaction termination, your routing program can examine the output communications area (pointed to by DYRACMAA).
This is an example of how this facility could be used:
- You have a CICSplex consisting of sets of functionally-equivalent
TORs and AORs, and need to identify any inter-transaction affinities
that may affect transaction routing. You could use the CICS® Interdependency Analyzer to
do this, but there are some affinities that the utility cannot detect
(for example, those created by non-CICS functions). Also, some transactions
may sometimes create affinities, and sometimes not.
For information about the CICS Interdependency Analyzer, see CICS Interdependency Analyzer for z/OS.
However, the routed transactions themselves know when an affinity is created, and can communicate this to the dynamic transaction routing program. The routing program is then able to route such transactions accordingly.
See also Modifying the application’s containers.