gtpo1mblOperations

ZNPIU-Display PIU Trace Table

Use this command to display the entries in the path information unit (PIU) trace table.

Requirements and Restrictions

Format




COMPACT
creates a compacted display of the PIU trace table entries.

FORMAT
creates a formatted display of the PIU trace table entries. The transmission header (TH) values in the PIU trace table entries are translated. The entire response/request unit (RU) being traced is displayed.

LONG
creates the same display as the FORMAT parameter.

ALL
displays all the entries in the PIU trace table.

number
is the number of entries in the PIU trace table that you want to display, from 1-999.

Control
includes high-performance routing (HPR) control messages in the information that is displayed.

NOControl
omits HPR control messages from the information that is displayed.

Headers
includes the network layer header (NHDR) and transport header (THDR) in the network layer packets (NLPs) that are displayed.

NOHeaders
omits the NHDR and THDR from the NLPs that are displayed.

Data
includes the RU in the information that is displayed.

NOData
omits the RU from the information that is displayed.

Additional Information

Examples

The following list provides descriptions of the fields contained in the information that is displayed. A subset of these fields is displayed depending on the parameters that you specify.

 BSN 
is the byte sequence number (BSN) of the rapid transport protocol (RTP) connection (NLP only)

 CCW 
is the channel command word (CCW) area index

 CNT 
is the count; that is, the combined length of the request/response header (RH) and the RU (FID4 only)

 CTC HDR 
is the eight-byte channel-to-channel header (CTC only)

 DNA 
is the destination network address (FID4 only)

 DNAME 
is the destination name
Note:
The DNAME and ONAME fields contain the words ROUTE.SETUP if the entry contains an HPR ROUTE_SETUP command.

 DRID 
is the destination resource identifier (RID)
Note:
For TPF/APPC sessions, either the DRID or ORID is the SCBID.

 ERVR 
is the explicit route, virtual route, and transmission priority (FID4 only)

 FID5 
is the FID5 transmission header (NLP only)

 IN 
is the channel command word area index

 LNKHDR 
is the link header (FID2 and NLP only)

 NHDR 
is the network layer header (NLP only)

 ONA 
is the origin network address (FID4 only)

 ONAME 
is the origin name
Note:
The DNAME and ONAME fields contain the words ROUTE.SETUP if the entry contains an HPR ROUTE_SETUP command.

 ORID 
is the origin RID
Note:
For TPF/APPC sessions, either the DRID or ORID is the SCBID.

 PCID 
is the procedure correlation identifier

 RH 
is the request/response header

 RH INDICS 
is one or more of the following RH indicators:

 -RSP 
Negative response

 BB 
Begin brackets

 CD 
Change direction

 CEB 
Conditional end bracket

 CS 
Code selection indicator

 DFC 
Data flow control PIU

 DR 
Definite response requested

 EB 
End brackets

 ED 
Enciphered data

 ER 
Exception response requested

 FI 
Format indicator

 FIC 
First in chain

 FMD 
Function management data PIU

 LIC 
Last in chain

 MIC 
Middle in chain

 NC 
Network control PIU

 NR 
No response requested

 OIC 
Only in chain

 PAC 
Pacing request or pacing response

 PID 
Padded data

 PRSP 
Positive response

 QR 
Queued response

 REQ 
Request

 RLW 
Request larger window size

 RSP 
Response

 SC 
Session control PIU

 SDI 
Sense data indicator

 RTP 
is the rapid transport protocol control block (RTPCB) index (NLP only)

 RU 
is the request/response unit or 8-byte channel-to-channel (CTC) header

 RW 
is the read/write operation code

 RWI 
is the read/write operation code

 SA1 
is the session address (SA) that the TPF system assigned to the HPR LU-LU session (NLP only)

 SA2 
is the SA that the remote RTP endpoint assigned to the HPR LU-LU session (NLP only)

 SEGMENTS 
indicates the presence of the following optional segments in the THDR (NLP only):

 ARB 
Adaptive Rate Based segment (X'22')

 CF 
Connection Fault segment (X'12')

 CIE 
Connection Identifier Exchange segment (X'10')

 COB 
Client Out of Band segment (X'0F')

 CS 
Connection Setup segment (X'0D')

 SI 
Switching Information segment (X'14')

 STATUS 
Status segment (X'0E')

 SEQ 
is the sequence number of the session

 SID 
is the session identifier (FID2 only)

 TCID1 
is the transport connection identifier (TCID) that the TPF system assigned to the RTP connection (NLP only)

 TCID2 
is the TCID that the remote RTP endpoint assigned to the RTP connection (NLP only)

 TH 
is bytes 0 and 1 of the FID2 transmission header (FID2 only)

 THDR 
is the transport header (NLP only)

 TIME 
is the time stamp

 VRSQ 
is the virtual route sequence number (FID4 only).

In the following example, 29 entries from the PIU trace table are displayed in a compacted format. The entries contain both FID2 and FID4 PIUs.

+--------------------------------------------------------------------------------+
|User:   ZNPIU 29                                                                |
|                                                                                |
|System: NPIU0004I 08.36.49 PIU TRACE TABLE                                      |
|        RW IN  DRID   ORID   DNA     ONA  VRSQ SEQ  CNT    RH   RU              |
|        RW IN  DRID   ORID   LNKHDR   TH  SID  SEQ         RH   RU              |
|        RW IN  DRID   ORID   RTP         PCID       SEQ    RH   RU              |
|        32 01 000000 000000 00790000 2F00 0101 0944      6B8000 3101070330200002|
|        31 01 000136 000070 00790000 2F00 0101 0944      EB8000 3101070330200002|
|        52 01 000070 000136 000E0000 2F00 0101 0945      6B8000 A0              |
|        51 01 000136 000070 000E0000 2F00 0101 0945      EB8000 A0              |
|        31 01 000136 000070 002E0000 2E00 0101 0001      039100 D3D401C3D3E4C2C2|
|        32 01 000070 000136 00100000 2F00 0101 0000      830100 000001          |
|        51 01 000136 000070 002E0000 2E00 0101 0002      039100 D3D401C3D3E4C2C2|
|        52 01 000070 000136 00100000 2F00 0101 0000      830100 000001          |
|        31 01 000136 000070 002E0000 2E00 0101 0003      039100 D3D401C3D3E4C2C2|
|        32 01 000070 000136 00100000 2F00 0101 0000      830100 000001          |
|        51 01 000136 000070 00220000 2E00 0101 0004      039100 D3D404C3D3E4C2C2|
|        52 01 000070 000136 00100000 2F00 0101 0000      830100 000001          |
|        31 01 000136 000070 00220000 2E00 0101 0005      039100 D3D404C3D3E4C2C2|
|        32 01 000070 000136 00100000 2F00 0101 0000      830100 000001          |
|        51 01 000136 000070 00220000 2E00 0101 0006      039100 D3D404C3D3E4C2C2|
|        52 01 000070 000136 00100000 2F00 0101 0000      830100 000001          |
|        32 02 000002 00000F 0B0000 1F0000 0000 0000 0018 2B0000 0F00000100000000|
|        31 02 00000F 000002 1F0000 0B0000 0000 0001 0018 2B0000 0F00000100000000|
|        51 02 00000F 000002 1F0000 0B0000 0000 0001 0028 2B0000 0B00000100000100|
|        52 02 000002 00000F 0B0000 1F0000 0000 0001 0034 2B0000 0C00000100010100|
|        31 02 00000F 000002 1F0000 0B0000 0000 0001 0016 2B8000 0D00000100800080|
|        32 02 000002 00000F 0B0000 1F0000 4000 0001 0004 AB8000 0D              |
|        51 02 00000F 000002 1F0000 0B0000 4000 0001 0000                        |
|        31 01 000136 000070 00220000 2E00 0101 0007      039100 D3D404C3D3E4C2C2|
|        32 01 000070 000136 00100000 2F00 0101 0000      830100 000001          |
|        51 01 000136 000070 002E0000 2E00 0101 0008      039100 D3D401C3D3E4C2C2|
|        52 01 000070 000136 00100000 2F00 0101 0000      830100 000001          |
|        31 01 000136 000070 002E0000 2E00 0101 0009      039100 D3D401C3D3E4C2C2|
|        32 01 000070 000136 00100000 2F00 0101 0000      830100 000001          |
|        153 PIUS IN TRACE TABLE                                                 |
+--------------------------------------------------------------------------------+

In the following example, five entries from the PIU trace table are displayed in a compacted format. The entries contain both FID4 PIUs and 8-byte CTC headers.

+--------------------------------------------------------------------------------+
|User:   ZNPIU COMPACT 5                                                         |
|                                                                                |
|System: NPIU0004I 17.36.50 PIU TRACE TABLE                                      |
|        RW IN  DRID   ORID   DNA     ONA  VRSQ SEQ  CNT    RH   RU              |
|        RW IN  DRID   ORID   LNKHDR   TH  SID  SEQ         RH   RU              |
|        RW IN  DRID   ORID   RTP         PCID       SEQ    RH   RU              |
|        06 0B 00003F 800002 0A007C 0B0002 000C 0001 004D EB8000 31001307B0B0D0B1|
|        05 0B                                                   003F0001055E0544|
|        05 0B 000002 000001 0B0000 0A0001 000D 0003 0025 0B8000 8186460A0A688B50|
|        06 0B                                                   002000010544055E|
|        06 0B 000001 000002 0A0000 0B0001 000D 0003 0006 8B8000 818646          |
|        35 PIUS IN TRACE TABLE                                                  |
+--------------------------------------------------------------------------------+

In the following example, five entries from the PIU trace table are formatted and displayed. The TH values are translated and the entire RU being traced is displayed. The entries contain FID2 PIUs, FID4 PIUs, and 8-byte CTC headers.

+--------------------------------------------------------------------------------+
|User:   ZNPIU FORMAT 5                                                          |
|                                                                                |
|System: NPIU0005I 09.52.59 PIU TRACE TABLE                                      |
|        RWI-31 CCW-01 DNAME- ELMNGR            ONAME- VTAMNET.CLUAA001          |
|           PCID-E383BE9553F2DA86 TIME-52.32  DRID-000102 ORID-0000BC            |
|           LNKHDR-002E0000  TH-2E00 SID-0101 SEQ-0001   RH-039100               |
|           RU-                 RH INDICS- REQ FMD OIC ER PAC                    |
|              0    0    D3D401C3 D3E4C1C1 F0F0F120 E3D7C6C1     LM.CLUAA 001.TPF|
|             16   10    40404040 01000000 00E3D7C6 C1C1F3F0     ........ .TPFAA3|
|             32   20    40                                      .               |
|        RWI-06 CCW-0B CTC HDR-003A00010205024D                                  |
|        RWI-06 CCW-0B DNAME- TPFA              ONAME- TPFB                      |
|           PCID-0000000000000000 TIME-54.24  DRID-000001 ORID-000002            |
|           DNA-0A0000 ONA-0B0001 ERVR-0001 VRSQ-0005 SEQ-0001 CNT-0020 RH-EB8000|
|           RU-ACTCDRM          RH INDICS- RSP SC FI PRSP                        |
|              0    0    14021111 40404040 40404040 05000000     ........ ........|
|             16   10    000B3F06 0600274E B40020FE 00           ........ .....  |
|        RWI-05 CCW-0B CTC HDR-00670001052E03F4                                  |
|        RWI-05 CCW-0B DNAME- APPC              ONAME- APPA                      |
|           PCID-0A0A3CC050800001 TIME-56.23  DRID-800001 ORID-00003F            |
|           DNA-0B0002 ONA-0A007C ERVR-0001 VRSQ-000C SEQ-0001 CNT-004D RH-6B8000|
|           RU-BIND             RH INDICS- REQ SC FI OIC DR                      |
|              0    0    31001307 B0B0D0B1 3F3FA7F8 3F3F0602     ........ ...8....|
|             16   10    00000000 00000000 27000008 C1D7D7C1     ........ ....APP|
|             32   20    40404040 1B000902 C6D4F140 40404040     ........ FM1.....|
|             48   30    0903000A 3CC05080 00010504 C1D7D7C1     ........ ....APP|
|             64   40    0008C1D7 D7C34040 4040                  ..APPC.. ..     |
|        99 PIUS IN TRACE TABLE                                                  |
+--------------------------------------------------------------------------------+

In the following example, a formatted NLP is displayed. The HEADERS parameter was specified so that the NHDR and THDR are also displayed.

+--------------------------------------------------------------------------------+
|User:   ZNPIU FORMAT 1 HEADERS                                                  |
|                                                                                |
|System: NPIU0005I 01.06.31 PIU TRACE TABLE                                      |
|        RWI-31 CCW-01 DNAME- VTAMNET.LCL8DD    ONAME- G623                      |
|           PCID-E383BE95191C9BAA TIME-03.39  DRID-00023E ORID-00091A            |
|           LNKHDR-00890000 TCID1-2366C462C2000002 TCID2-0BBEA50900000083 SEQ-000|
|           RTP-000002 SA1-E383BE95191C9BAA SA2-0000000007000001 BSN-000002B4    |
|           NHDR                                                                 |
|              0    0    C2088000 0220D000 00000000 0000FF00     B....... ........|
|           THDR           SEGMENTS- STATUS                                      |
|              0    0    0BBEA509 00000083 3004000A 0000004D     ........ ........|
|             16   10    000002B4 050E0000 00020E21 000000D3     ........ .......|
|             32   20    00000000 00000000                       ........        |
|           FID5-5C0000060000000007000001      RH-038000                         |
|           RU-                 RH INDICS- REQ FMD OIC DR                        |
|              0    0    F1F7115C F0D8D9E3 F260D9D6 E4E3C9D5     17..0QRT 2-ROUTI|
|             16   10    C740C9D5 C440C9D5 E5C1D3C9 C46B40C5     G.IND.IN VALID,.|
|             32   20    D5E3C5D9 406F40C6 D6D940C8 C5D3D740     NTER...F OR.HELP.|
|             48   30    40404040 40404040 40404040 404E         ........ ...... |
|        426 PIUS IN TRACE TABLE                                                 |
+--------------------------------------------------------------------------------+

Related Information

See TPF ACF/SNA Data Communications Reference for more information about the PIU trace facility and high-performance routing (HPR) support.