gtpp1m1h | Program Development Support Reference |
On the first page of a system dump is the line, SYSTEM TRACES ACTIVE, which indicates whether C function trace is active and which trace options are specified. The CDEBUG, STACK, STATIC, and XHOOKS parameters are displayed on this line if they have been specified previously by the ZSTRC command. System dumps are similar to the sample dumps shown starting with Trace Output without Stack and Static Data except that the sample dumps do not have the SYSTEM TRACES ACTIVE line.
Because of performance considerations, only certain ECBs are formatted and dumped. The criteria for formatting and dumping ECBs follows:
The C function trace user area (for each ECB) is not dumped if the area exists. The C function trace user area is allocated using the USERSIZE parameter on the SETTC macro. You can allocate space and put whatever trace data you desire into that area. The C function trace table header contains the address and length of the user area. It is your responsibility to format and print the C function trace user area if desired.
The C function trace table is allocated automatically the first time you use it.
When breakpoints other than program entry breakpoints and program exit breakpoints are compiled into the C programs and turned on by entering ZSTRC ALTER CDEBUG XHOOKS or by issuing the ENATC macro with the OTHERS=ON parameter specified, and when the assembler breakpoint instruction is invoked, the control is transferred to the CTRY copy member of the CCISOC module. CTRY builds a trace table entry in the C function trace table for breakpoints other than program entry breakpoints and program exit breakpoints.
The CID fields that follow here are updated to reflect relevant information of the current trace entry for tracing of program entry breakpoints, program exit breakpoints, and other breakpoints.