z/OS Communications Server: ACF/TAP Trace Analysis Handbook
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Network error report

z/OS Communications Server: ACF/TAP Trace Analysis Handbook
GC27-3645-00

The selection parameter is NEPRT.

Figure 1 shows a sample report.

This report lists the error messages and a one line summary (such as incorrect commands, sense codes, or BIND failures) of error conditions that have occurred in the network. See Figure 1 to see the trace data that can be produced on each report.

ACF/TAP supports VTAM® full buffer trace data but prints a maximum of 256 bytes per record. Starting with SSP V4R8, the control parameter LONGPIU=YES can be specified, and up to 4096 bytes of VTAM full buffer trace data per PIU are printed. This could be 4096 bytes from one GTF record or 4096 bytes reassembled from multiple GTF records.

The SYSPRINT report displays the complete buffer trace data when DUMP=YES is specified. For more information, see the information about the buffer contents trace in z/OS Communications Server: SNA Diagnosis Vol 2, FFST Dumps and the VIT.

Table 1 describes the column headers and the trace data contained in this report type. To locate this information about the sample reports, reference the numbers (n) listed in this table to the corresponding numbers (n) shown in the sample report.

Table 1. Network error report description
Reference number (n) Report column headers and the trace data
1 The page heading contains the report name, report parameter, and the date the report was printed or displayed.
2
ERROR
Identification of error messages. Messages DSJ100I through DSJ199I are described in Messages.
3
MESSAGE NUMBER
The ACF/TAP-assigned sequence number.
4
ADDITIONAL INFORMATION
The sense data in hexadecimal format for message DSJ126I.
5
SUMMARY
A single keyword that summarizes the error condition. It is self-explanatory.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014