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


Network data traffic report

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

The selection parameter is DTPRT.

Figure 1 shows a sample report.

This report is a hexadecimal and character format printout of the request and response units that have data associated with them. ACF/TAP formats only the data that remains following the analysis of the transmission header, request header, and request and response unit command bytes, and a summary of any network commands.

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 will be 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 further 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. Network data traffic 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
MESSAGE NUMBER
The ACF/TAP-assigned sequence number.
3
GROUP SUMMARY
The source of the data.
4
MESSAGE DATA
Data in hexadecimal format.
5 This is the EBCDIC equivalent of the hexadecimal message data.
6
ENTRY SUMMARY
The summary of any network commands.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014