OSI/TS Configuration and Management Manual

Performing Monitoring and Troubleshooting Guide
OSI/TS Configuration and Management Manual—424831-001
4-13
Trace and Trace Analysis
STATS SERVICE $TSP1.*
The following command displays information on the TPDUs transferred through a
specific subdevice:
STATS SU $TSP2.#Z000001
Trace and Trace Analysis
The following PTrace commands are highly useful for obtaining Transport Layer
information. The order of the items roughly follows a top-down troubleshooting
method.
Attach requests from an application (to wait for an incoming call) are CONTROL or
WRITEREAD calls to a TSP subdevice, with the MCW (message control word) set to
signify a specific operation.
You can use the following command to display these calls:
SELECT MSG; FILTER MSGSYS
The screen returned displays the file-system call information. An MCW of %H8000
(bottom line) sets the TSP to accept an incoming T-CONNECT, as follows:
The following command displays the file-system calls from a specific subdevice:
SELECT MSG; MSGSU #Z000006
Errors are returned by the TSP process when the TSP subdevice detects an error. The
following command finds a specific error, such as error 140:
FIND FE: 140
The following screen is an example of a typical received error 140:
The following command displays the transport state machine:
SELECT L4; FILTER L4SM; STATETABLES OS4SMT
The following command lists the Transport Layer primitives traced by the TSP process:
17:11:52:920 >000.010 #17 Msg IO
WRITEREAD Req Tag: 1 File: 4 Syncid: 1 Wrlen: 2 Rdlen: 34 SU:
#Z000006
P1: -32768
000: 8000
17:11:53:810 >000.000 #63 Msg IO
WRITEREAD Res Tag: 1 Replylen: 2 FE: 140 SU: #Z000006