Use this command to do the following:
Requirements and Restrictions
You can enter this message only in 1052 state or higher.
Format
- STArt
- starts the PIU trace facility or starts writing the PIU trace table to the
real-time tape.
- Vronly
- traces only network control commands, VR pacing requests, and VR pacing
responses.
- Note:
- If you specify VRONLY, the value of the ID parameter must be the name of an
NCP or CTC link.
- ALL
- traces data transferred between the TPF system and all remote SNA
resources.
- Netid-identifier
- traces data for a specific LU, CDRM, SSCP, ALS, CTC link, or NCP, where
identifier is the 1- to 8-character network identifier (ID) of the
resource. The network ID and name of a resource must both begin
with a letter (A-Z), @, #, or $. The
remaining characters can be letters (A-Z), numbers (0-9),
@, #, or $.
Notes:
- You can use the asterisk (*) as a wildcard character to specify a group of
network identifiers that begin or end with a common string of
characters. For example, to start tracing data for all resources that
have a network identifier beginning with SNA, enter SNA*.
- To specify an SNA network ID or resource name that contains dollar
signs ($), you must type two consecutive dollar signs
($$) for each dollar sign in the network ID or resource
name. For example, if the SNA resource name is $SNANAME, you must type
$$SNANAME.
- Id-resource
- traces data for a specific LU, ALS, CDRM, SSCP, CTC link, or NCP, where
resource is the 1- to 8-character name of the resource.
The network ID and name of a resource must both begin with a letter
(A-Z), @, #, or $. The remaining
characters can be letters (A-Z), numbers (0-9), @,
#, or $.
Notes:
- If you specify the name of an NCP, ALS, or CTC link, all data for
resources that have sessions through that NCP, ALS, or CTC link is
traced.
- You can use the asterisk (*) as a wildcard character to specify a group of
resource names that begin or end with a common string of characters.
For example, to start tracing data for all resources that have a name ending
with NCP, enter *NCP.
- To specify an SNA network ID or resource name that contains dollar
signs ($), you must type two consecutive dollar signs
($$) for each dollar sign in the network ID or resource
name. For example, if the SNA resource name is $SNANAME, you must type
$$SNANAME.
- Hpr
- traces all HPR traffic, which includes all NLPs on all RTP connections and
HPR ROUTE_SETUP commands.
- Statchng
- traces only data flowing for HPR state changes on RTP connections.
State changes include HPR ROUTE_SETUP commands, RTP connections starting, RTP
connections stopping, and path switches.
- Rtp-index
- traces data on a specific RTP connection, where index is the 1-
to 6-digit hexadecimal rapid transport protocol control block (RTPCB) index of
the RTP connection.
- Note:
- The specified RTP connection must be active.
- Tape
- automatically writes each 4-KB block of the PIU trace table to the
real-time tape once the 4-KB block is full.
- Note:
- If the length of the queue to the real-time tape exceeds the tape
queue threshold value defined by the PIUTAPEQ parameter in the SNAKEY macro,
the PIU trace facility stops writing the PIU trace table to tape until the
queue falls below this value again.
- STOp
- stops the PIU trace facility or stops writing the PIU trace table to the
real-time tape.
- ALL
- stops tracing data transferred between the TPF system and all remote SNA
resources. (This trace was defined by entering ZNTRP START ALL.)
Traces defined for specific resources remain active.
- ALLR
- stops the PIU trace facility completely. All of the traces defined
end and data is no longer stored in the PIU trace table.
- Netid-identifier
- stops a trace defined for a specific LU, CDRM, SSCP, ALS, CTC link, or
NCP, where identifier is the 1- to 8-character network identifier of
the resource. The network ID and name of a resource must both
begin with a letter (A-Z), @, #, or $.
The remaining characters can be letters (A-Z), numbers (0-9),
@, #, or $.
Notes:
- You can use the asterisk (*) as a wildcard character to specify a group of
network identifiers that begin or end with a common string of
characters. For example, to stop traces defined for all resources that
have a network identifier beginning with SNA, enter SNA*.
- To specify an SNA network ID or resource name that contains dollar
signs ($), you must type two consecutive dollar signs
($$) for each dollar sign in the network ID or resource
name. For example, if the SNA resource name is $SNANAME, you must type
$$SNANAME.
- Id-resource
- stops a trace defined for a specific LU, CDRM, SSCP, ALS, CTC link, or
NCP, where identifier is the 1- to 8-character network identifier of
the resource. The network ID and name of a resource must both
begin with a letter (A-Z), @, #, or $.
The remaining characters can be letters (A-Z), numbers (0-9),
@, #, or $.
Notes:
- If you specify the name of an NCP, ALS, or CTC link, data for resources
that have sessions through that NCP or ALS will no longer be traced, unless a
specific trace was defined for one of those resources.
- You can use the asterisk (*) as a wildcard character to specify a group of
resource names that begin or end with a common string of characters.
For example, to stop traces defined for all resources that have a name ending
with NCP, enter *NCP.
- To specify an SNA network ID or resource name that contains dollar
signs ($), you must type two consecutive dollar signs
($$) for each dollar sign in the network ID or resource
name. For example, if the SNA resource name is $SNANAME, you must type
$$SNANAME.
- Hpr
- stops tracing HPR traffic. (This trace was defined by entering
ZNTRP START HPR.) If traces were defined for specific LUs or RTP
connections, those traces remains active.
- Rtp-index
- stops a trace defined for a specific RTP connection, where index
is the 1- to 6-digit hexadecimal RTPCB index of the RTP connection.
- Tape
- stops automatically writing the PIU trace table to real-time
tape. When you specify this parameter, the PIU trace table is written
to tape one last time, whether or not the the current 4-KB block is
full.
- Rusz rsize
- changes the number of bytes of the RU being stored in the PIU trace table
for data messages on LU-LU sessions, where rsize is a decimal number
in the range 8-3840.
- Crusz csize
- changes the number of bytes of the RU being stored in the PIU trace table
for SNA commands, data flowing on CDRM-CDRM sessions, and data flowing on
CP-CP sessions, where csize is a decimal number in the range
8-3840.
- Display
- displays information about the data being traced.
- Options
- displays the status of the PIU trace facility. The information
displayed indicates:
- Whether the PIU trace table is currently being written to tape
- The size of the RU stored in the PIU trace table for data messages on
LU-LU sessions
- The size of the RU stored in the PIU trace table for SNA commands, data
flowing on CDRM-CDRM sessions, and data flowing on CP-CP sessions.
Additional Information
- Online help information is available for this command. To display
the help information, enter one of the following:
ZNTRP HELP
ZNTRP ?
- The PIU trace facility stores 21 bytes of the RU in the PIU trace table
for data messages on LU-LU sessions unless you change this value by using the
RUSZ parameter.
- The PIU trace facility stores 21 bytes of the RU in the PIU trace table
for SNA commands, data flowing on CDRM-CDRM sessions, and data flowing on
CP-CP sessions unless you change this value by using the CRUSZ
parameter.
- The 8-byte header that precedes all read and write operations during
normal CTC data transfer operations is also stored in the PIU trace
table.
- If you specify the ID parameter without specifying the NETID parameter,
the PIU trace facility selects the first resource in the collating sequence of
the network identifiers.
- You can use the ZNDLU, ZNALS, and ZNETW DISPLAY commands to display status
information about a specific LU, CDRM, SSCP, ALS, NCP, or CTC link.
- You can use the ZNPIU command to display the data that was traced and
stored in the PIU trace table.
Examples
The PIU trace facility is started for the PBPB resource in the SNANET
network in the following example.
+--------------------------------------------------------------------------------+
|User: ZNTRP START NETID-SNANET ID-PBPB |
| |
|System: ZNTRP0001I 13.11.13 PIU TRACE STARTED FOR SNANET.PBPB |
+--------------------------------------------------------------------------------+
The PIU trace facility is started for all resources that have a name ending
in the characters AT in the following example.
+--------------------------------------------------------------------------------+
|User: ZNTRP START ID-*AT |
| |
|System: NTRP0008I 13.11.13 PIU TRACE STARTED FOR ALL RESOURCES CHOSEN WITH |
| SELECTION CRITERIA --- NAME- *AT |
+--------------------------------------------------------------------------------+
In the following example, the PIU trace facility is started for all the
resources defined in the TPF system.
+--------------------------------------------------------------------------------+
|User: ZNTRP START ALL |
| |
|System: NTRP0002I 14.02.21 PIU TRACE STARTED FOR ALL RESOURCES |
+--------------------------------------------------------------------------------+
In the following example, the ALL parameter is used to stop the PIU trace
facility for all resources in the TPF system. Keep in mind that the PIU
trace facility is not stopped for the PBPB resource or the resources that have
a name ending with the characters AT because these resources were already
being traced when ZNPIU START ALL was entered in the previous example.
+--------------------------------------------------------------------------------+
|User: ZNTRP STOP ALL |
| |
|System: NTRP0004I 14.05.41 PIU TRACE STOPPED FOR ALL RESOURCES |
+--------------------------------------------------------------------------------+
In the following example, the ALLR parameter is used to stop the PIU trace
facility for all resources in the TPF system. In this case, the PIU
trace facility is stopped for the PBPB resource and for the resources that
have a name ending in the characters AT.
+--------------------------------------------------------------------------------+
|User: ZNTRP STOP ALLR |
| |
|System: NTRP0004I 14.07.31 PIU TRACE STOPPED FOR ALL RESOURCES |
+--------------------------------------------------------------------------------+
Information about the resources being traced is displayed in the following
example.
+--------------------------------------------------------------------------------+
|User: ZNTRP DISPLAY |
| |
|System: NTRP0048I 12.31.25 PIU TRACE ACTIVE FOR THE FOLLOWING SELECTED RESOURCES|
| NETID NAME RTP INDEX DEVICE TYPE VRONLY |
| -------- -------- --------- -------------- ------ |
| N42E720 ALS/NCP/CTC YES |
| G623 LU |
| 000001 RTP CONNECTION |
| END OF DISPLAY |
+--------------------------------------------------------------------------------+
The status of the PIU trace facility is displayed in the following
example.
+--------------------------------------------------------------------------------+
|User: ZNTRP DISPLAY OPTIONS |
| |
|System: NTRP0045I 23.23.21 PIU TRACE OPTIONS INFORMATION |
| PIU TRACE IS ACTIVE TO REAL TIME TAPE |
| 200 BYTES OF RU ARE BEING TRACED FOR USER DATA MESSAGES |
| 100 BYTES OF RU ARE BEING TRACED FOR SNA COMMANDS |
| END OF DISPLAY |
+--------------------------------------------------------------------------------+
The size of the RU being stored in the PIU trace table for data messages is
changed to 300 bytes in the following example.
+--------------------------------------------------------------------------------+
|User: ZNTRP RUSZ 300 |
| |
|System: NTRP0013I 23.26.43 TRACING 300 BYTES OF RU FOR USER DATA MESSAGES |
+--------------------------------------------------------------------------------+
Related Information
See TPF ACF/SNA Data Communications Reference for
more information about the PIU trace facility and RTP connections.