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


LUNAME network address cross-reference report

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

The selection parameter is LUPRT.

This report associates network addresses with logical unit names.

Figure 1 shows a sample 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 is 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. LUNAME network address cross-reference report
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 message number.
3
TYPE
Trace information displayed:
L
Line
B
Buffer or PIU
T
TG Trace
N
NTO Trace
4
DIR
Message direction as it pertains to the host for buffer trace, and to NCP for line trace. The following values are available:
I
In
O
Out
5
Form identifier (FID)
One of the following transmission header types:
2
FID2
4
FID4
6
OSAF-OEF DSAF-DEF
A 4-byte subarea address followed by a 2-byte element origin address on the first line, and the destination addresses on the second line.
7
LFSID/OAF DAF
17-bit FID2 LFSID
8
SEQNO
The transmission header sequence number in hexadecimal.
9
PLUNAME/SLUNAME
The primary logical unit name (PLUNAME) appears on the first line, and the secondary logical unit name (SLUNAME) appears on the second line. For more information about PLUNAME/SLUNAME, see the BIND RU description in the z/OS Communications Server: SNA Network Implementation Guide.
10
PCID
The procedure correlation ID identifies the session. This item also appears if the column header appears as an index number.
11
DATE
The date in the trace record.
12
TIME
The time in the trace report.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014