What can you do when the application EXEC DB2 call has an unexpected return address with OMEGAMON for CICS?
bobby_g 060000DF9B Visits (2184)
I was recently directed to a Technote within OMEGAMON for CICS on z/OS for V 4.2.0 and higher by my level 3 representative that outlined a condition when OMEGAMON CICS is configured to collect DB2 statistics but the CICS Interdependency Analyzer for z/OS is unable to collect the DB2 data and the application EXEC DB2 calls might have an unexpected return address when viewed in an XRMIOUT exit or a dump.
Please note that this information will subsequently be documented in the OMEGAMON XE for CICS on z/OS: Troubleshooting Guide.
You would do the following to diagnose the problem.
OMEGAMON makes the call from the BALR in this sequence:
JUMPADS DC 2AL4(0)
DC C'CALLER R14 ='
JUMPR14 DC AL4(0)
JUMPSTCK DC XL8'0'
To resolve this problem, R14 needs to point to the LM; the application return address can be found in the field labelled, JUMPR14.