Appendix B. Correlating Scanner and Reporter output to source
This appendix describes how to match the EXEC CICS command in the Reporter report and/or the Scanner detail report with the actual program source code. It also gives some examples of the procedures described.
Reporter output
The reported offset of a command is the offset from the start of the load module of the BALR to the CICS stub. To get the offset from the start of the program, subtract the length of the CICS stub from the offset reported. (You may also need to subtract the lengths of any additional preceding CSECTs.) You can then use the compiler listing to ®nd the command.
Scanner output
The reported offset of a command is the offset from the start of the load module of the CICS command argument zero.6 This is a constant and is therefore located in the literal pool for the program. As with the Reporter, subtract the length of the CICS stub and preceding CSECTS to get the offset from the start of the program. You should then be able to locate the argument zero in the compiler listing. Next, match the argument zero to the command, which involves ®nding the instruction that referenced the argument zero, using the compiler listing.
Examples
This section gives some examples of the procedures for the Scanner.
Example 1±Assembler-language
Before the BALR to the CICS stub, the CICS translator generates an LA instruction with the argument zero as source. For example:
LA 14,=X©02028000080700000000000000000000000000000000©
To locate the EXEC CICS command, you can match the argument zero in the literal pool with the same argument zero in the LA instruction.
6. For an explanation of argument zero, see ªNotes on terminologyº on page x.
© Copyright IBM Corp. 1994, 1999 | 71 |
