Examining Dumps › Entries in the CICS Trace Table › Special Entries

Special Entries

CA InterTest for CICS writes special entries into the CICS Trace Table to assist you in your analysis efforts. These entries appear in the Trace Table when it is found in a dump, and when it is displayed with a CORE=STRA command (at a breakpoint) or the CORE=TRT command.

In the CICS formatted dump, these special entries are identified as follows:

USER 195.

Unlike the regular CICS‑written entries, the CA InterTest for CICS entries provide displacements, which are the same displacements you can find in the listing of the program. CA InterTest for CICS writes these entries into the Trace Table, in addition to those issued by the monitored program and the CICS software, when the monitored program is about to:

• Issue a CICS request (command).
• Issue a CICS request (macro).
• Be stopped at a CA InterTest for CICS breakpoint or resume execution after a CA InterTest for CICS breakpoint.
• Execute an instruction for which CA InterTest for CICS disregards a presumed error condition because of an OVR (Override) option in effect.
• Issue a DL/I request.
• Issue a CICS request (either command or macro) and the active online NUP= option will affect the request.
• Issue a call to software defined in the CA InterTest for CICS IN25UEXI table.

The entries issued for these cases consist of two fields, which are described next.

• Field A contains the displacement of the request (or the breakpoint) from the beginning of the program, expressed as four hexadecimal digits. If the request was made outside the program, this field contains the address instead.
• Field B contains the following bytes:
  • At a CICS command, bytes 0 to 3 contain four hexadecimal digits that specify the command code (such as, 0204 for a handle condition).
  • At a CICS macro, bytes 0 to 1 contain two characters that describe the service type (SC = storage control, FC = file control, and so on) and bytes 2 to 3 contain the request field in the TCA.
  • At a breakpoint, bytes 0 to 2 contain the code indicating the type of breakpoint (ABP = automatic breakpoint, UBP = unconditional breakpoint, and so on) and byte 3 contains either a B (for Before the breakpoint) or an A (for After the breakpoint).
  • At each override condition, bytes 0 to 2 contain the characters OVR and byte 3 contains the hexadecimal error rode. (The OVR option cancels the Automatic Breakpoint display.)
  • At a DL/I request, bytes 0 to 1 contain the characters DL.
  • At an NUP‑affected request, bytes 0 to 2 contain the characters NUP (the online NUP= option prevents updates to files).
  • At a call to CA InterTest for CICS‑recognized software, bytes 0 to 1 contain the characters US and bytes 2 to 3 contain the numeric identifier from the IN25UEXI table.

CA InterTest for CICS also writes four entries into the Extents Trace Table when the monitored program is about to pass control directly to another program (by a branch instruction and not by a CICS command or macro) and the online FOL= option is in effect. These entries are as follows:

• In field A, the first entry contains the displacement that passes control. In field B, it contains the characters FROM.
• In fields A and B, the second entry contains the name of the program that passes control.
• In field A, the third entry contains the displacement that obtains control. In field B, it contains the characters INTO.
• In fields A and B, the fourth entry contains the name of the program that obtains control.

When monitoring is dropped because of a BYP option or a request by an IN25UEXI routine, field B contains DROP.