SYSPRINT reports

The SYSPRINT reports contain the following information:

A summary of the ACF/TAP control parameters used in processing the trace file
Operational and status messages
Network error messages (from the network error report)

The SYSPRINT reports can optionally contain the following information:

TIC trace data (when INPUT=LINE and TIC trace data is present)
3710 trace data (when INPUT=NETCTLR and 3710 trace data is present)
A summary of each trace record on a trace file, even if ACF/TAP did not process the trace record
A summary of records specified by:
- INPUT=type
- START=count
- END=count
- STIME=hh.mm.ss
- ETIME=hh.mm.ss
- SDATE=mmddyyyy
- EDATE=mmddyyyy
- NODE=nodename
PIU summary (PRINT=YES)
A hexadecimal dump of each trace record.

Table 1 shows the result of specifying a particular SUMMARY value.

Table 1. SUMMARY values and results
SUMMARY value	Result
EVERY	ACF/TAP summarizes every trace record in the trace file, even if it is a type that ACF/TAP does not process.
ALL	ACF/TAP summarizes all of the trace records of INPUT=type.
YES	ACF/TAP summarizes all records that it processes.

When records are selectively processed by time, date, count, or nodename, SUMMARY=ALL might produce more summary records than SUMMARY=YES. This is illustrated in Figure 1.

Figure 1. SUMMARY parameter illustration

Depending on the input source, the format of the summary record of each trace record is different. In all cases, ACF/TAP includes the timestamp, if present, in the trace record. ACF/TAP also includes other helpful source-dependent information, such as GTF, resource identifier (RID), format identifier (FID), and element identifier (EID).

ACF/TAP includes two sequence numbers in the trace file summary. One number is the ACF/TAP-assigned absolute sequence number, and the other number is the ACF/TAP-assigned process number (which is the same as the message number except for line trace records). For a line trace, the sequence number identifies the trace data block.

This topic contains SYSPRINT reports. See the following figures:

You can determine message sequence numbers of frames within the block data from the line trace summary report and the line trace detail report.

Table 2 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 reports.

Table 2. SYSPRINT 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	Start-up messages and control parameters. For Figure 1, the parameters in effect for the SYSPRINT were SUMMARY=YES and PRINT=YES. Because SUMMARY=YES was specified, records summarized were selected based on the parameters INPUT, START, END, and NODE.
3	Information about the trace file. See Messages. DSJ201I is an example of a GTF FID message.
4	DSJ201I Message This is the trace record description.
5	The contents of TH, RH, and RU. The result unless PRINT=NO is specified. For BSC devices, the first byte (2 characters) of the request/response unit is a pad byte. The actual request or response unit begins with the third character.
6	Direction (transmit or receive).
7	Hexadecimal dump of the data vector. For SDLC MOD 8 and SDLC MOD 128, the station address and control character are separated by a blank for clarity. For example: `MOD 8 - AA CC DDDDDDDD MOD 128 - AA CC DDDDDDDD (for unnumbered frames) MOD 128 - AA CC CC DDDDDDDD (for numbered frames) BSC/SS - DDDDDDDD` where: AA Station address CC Control character DD Data
8	The EBCDIC translation of the data vector's hexadecimal dump.
9	The line name.
10	The physical unit name of the device that is being traced.
11	The line adapter status.
12	Element number The ACF/TAP-assigned sequence number.
13	Trace type Identification of TIC, LINE, BUFFER, or NRF trace.
14	A hexadecimal dump of the trace element with EBCDIC translation to the right.