OSI/TS Configuration and Management Manual

Performing Monitoring and Troubleshooting Guide
OSI/TS Configuration and Management Manual424831-001
4-19
Troubleshooting Example
ptrace from tr1
starts the PTrace trace formatter on the trace located in the file TR1 and displays the
following:
You should next set up the select mask and the filters for the trace. Since you already
know that the incoming connect TPDU was refused within TSP, you need be interested
only in the Layer 4 activity. Use the following PTrace commands to select all the
appropriate trace records:
select l4; filter l4sm; statetables $system.zosits.os4smt;
filter l4services
record all
The first trace record found is displayed as follows:
Record #30 indicates that the T-CONNECT attach has enabled the Transport Layer to
accept an incoming CR-TPDU.
Records #32 and #38 indicate that the state machine has enabled the Network Layer to
establish a connection.
Record #66 shows the incoming CR-TPDU. The attributes include the TSAP IDs
(TSELs), TPDU size, and other parameters.
Trace of: \MARS.$TSP2, Type (55,4).
Ptrace Data File: $DIAG.MYSTUFF.TR1
Trace started: 10/10/91 10:32:00.570714
First trace entry: 10/10/91 10:32:00.139621
Last trace entry: 10/10/91 18:07:26.297123
Trace entry size limit: 1008
10/10/91 15:28:51.078456 >7000.123456 #30 T-Primitive
T-CON attach BufLen: 0 Addr: 1932172 SU: #Z000022
10/10/91 15:28:52.083120 >7000.020000 #32 L4 SM
TCB: 1 Class: 2 S4^CO2^CLOSED
:E4^CO2^TS^CONNATT =>A4^MONITOR^NCON SU: #Z000022
10/10/91 15:28:52.102712 >7000.010000 #38 L4 SM
TCB: 1 Class: 2 S4^CO2^CLOSED3
:E4^CO2^NC^AVAILABLE^OPENING =>A4^WAIT^FOR^CR^TPDU
SU: #Z000022
10/10/91 15:28:52.219646 >000.048340 #66 L4 TPDU IN
CR-TPDU CDT: 4 Dst: 0 Src: 1 Class: 2 Ext-Frmt: NO Exp-Flwctl:
YES
Calling TSAP:(hex) 3231 30 Called TSAP:(hex) 3031 32 TPDU
Size:4096
Version: 1 Option:N-expedited(NO) Option:Receive Conf(NO)
Option:No Checksum(NO) Option:T-Expedited(YES)
10/10/91 15:28:52.344972 >000.125326 #70 L4 SM
DR-TPDU Dst:1 Src: 0 Reason: No S-Entity