gtpp1m15 | Program Development Support Reference |
The online and offline DOF utilities format and print the following trace tables:
The collated macro trace table provides a snapshot of system activity by scanning every ECB when a system error occurs. Each ECB in the TPF system maintains its own separate macro trace table. The most recent trace entries are extracted and displayed. The ECB address, macro, program that issued the macro, location where the SVC occurred, parameter information (as appropriate), SVC old PSW information, the SVC code identifying the macro, the SVC index (as appropriate), and the time stamp. This provides an abbreviated real-time trace of all system activity. The ZSTRC command controls system trace options.
The DOF utility prints the trace table when a dump is issued. The entries are displayed in reverse chronological order, beginning with the most resent. A collated macro trace display is included for each I-stream that was active at the time of the dump. There is no LAST entry. This is not a wraparound trace table. One entry of the macro trace table is written per line. For a sample of the collated macro trace table see Collated Macro Trace Table.
The collated input/output (I/O) trace table shows the I/O activity at the time an I/O error occurs. The table contains information for each I-stream that was active at the time of the I/O error dump. See Collated Input/Output (I/O) Trace Table for more information.
The Systems Network Architecture input/output (I/O) trace table contains trace information for SNA I/O interrupts that occur during Network Control Program (NCP) exchange identifier (XID) exchanges, adjacent link station (ALS) XID exchanges, and channel-to-channel (CTC) XID exchanges. Information about significant steps in XID7 processing for CTC devices is also logged in this table. It also contains detailed trace information for NCP, ALS, and CTC asynchronous interrupts. Normal data transfer operations and attention-only interrupts that occur during NCP and ALS data transfer operations are not traced. For more information about the SNA I/O trace table, see the TPF ACF/SNA Data Communications Reference.
The SNA I/O trace table is included in system error dumps that have the control program keyword (ICP) specified in the dump override table. The DOF utility prints the SNA I/O trace table when these dumps are issued and labels it with the XID dump tag. See the IOTBL DSECT for information about how to interpret the contents of the SNA I/O trace table.
The path information unit (PIU) trace table contains a copy of the data transferred between the TPF system and remote resources. This trace table is included in system error dumps that have the SNA keyword (ISNA) specified in the dump override table.
When system error dumps are issued, the DOF utility prints the PIU trace table and labels it with the PIU dump tag.
See TPF ACF/SNA Data Communications Reference for more information about the PIU trace table. See the IPTBL DSECT for more information about how to interpret the contents of the PIU trace table.
Output from the real-time trace (RTT) utility is printed as it is read from the log tape. The trace output is formatted according to the parameters specified with the trace commands that were entered online or read from the test unit tape by the program test vehicle (PTV) utility. The activating command is included in the trace output.
Output from the RTT utility may be interrupted by system error processing. When a system error macro is issued, the system error routines force system error dumps to the real-time tape. When the dump occurs, queued real-time tape output is bypassed. The SYSTEM ERROR NUMBER nnn OCCURRED HERE message, which contains the dump sequence number, is written to tape.
This allows the system error dump to be precisely placed within the traced period. Another real-time trace header is printed before the DOF utility continues to process the trace output after the dump processing is completed.
When it is a catastrophic system error, the catastrophic system error dump may cause the TPF system to enter a WAIT state. After a catastrophic system error dump is completely written, any queued RTT output to the real-time tape is written by the same tape write routine used by the system error routines. Therefore, queued RTT information is not lost when the WAIT state prohibits tape processing.
The communication control program (CCP) trace routine provides a sequential record of CCP macros, start I/O and halt I/O activity, and multiplexor interrupts that occur on one line, or on one or more groups of lines. The CPP trace routine is initiated, modified, and terminated by commands. These messages and the collected CCP trace data are stored in a main storage block. You can optionally use this block in main storage only as a wrap-around log, or when full, to write its contents to tape. If a main storage log only, it is output unformatted whenever a dump occurs. If written to the RTL, the DOF utility produces a formatted list of all items traced including the commands used for the CCP trace activity. On any dump that occurs, the wrap-around CCP trace main storage block appears with a record of the last forty activities traced. See the TPF Non-SNA Data Communications Reference for more information about CPP trace operations.
The DOF utility formats and prints: