OSI/AS Configuration and Management Manual

Troubleshooting Guide
OSI/AS Configuration and Management Manual—424119-001
8-44
Troubleshooting Example
Now that you know TPDUs were sent and received, you should check the status of the
TSP subdevice in more detail.
Either of the SCF commands
status su $tsp2.#z000022,detail
check su $tsp2.#z000022,detail
displays the following:
The screen shows that the TSP subdevice is enabled for attachment (tcon in progress),
and is waiting for the CR-TPDU. Notice that this screen also gives you the name of the
NSP subdevice.
Step 4: Collect Trace Information Using SCF
In this case there have been no operational errors, which means that the error messages
have not been very helpful. At this point, you can only make guesses about the problem
from the SCF commands. To find out the real nature of the problem, you need a trace.
Since you have narrowed the problem down to the Transport Layer, you can concentrate
on tracing only the TSP process activity. The following SCF command starts the trace:
trace process $tsp2, to tr1
While the trace is on, rerun the application.
OSITS Detailed Status SU \MARS.$TSP2.#Z000022
State........ STARTED StopOpens....... OFF
TC State..... tcon in progress Opens........... 1
TC Substate.. waiting for CR-TPDU Opener Id. 255,017
Opener....... \MARS.$6,190
NSP SU....... \MARS.$X252.#TSP2014
NSP Subsys....... X25AM
FileError........ 0
NSPDSMRetCode.... 0 CreateTime.... 16 Oct 1991, 11:01:10.100
NSPDSMSubCode1... 0 LastOpenTime.. 16 Oct 1991, 11:10:10.100
NSPDSMSubCode2... 0 LastAlterTime.
NSPFSErrorCode... 0 LastCloseTime.
X25ClearCause.... 0
X25DiagCode...... 0
X25DisconReason.. 0 0 0 0
Class....... 2 Checksum.... OFF
DeleteTime.. -1 T-Expedited. OFF
TPDU Format. Normal TPDU Size... 4096
Receive Credit... 4 Sending Credit 4
LocalTSEL........ 4444444402
RemoteTSEL.......
LocalNSAP........ 408333111101
RemoteNSAP.......
LANLocalSNPA.....
LANRemoteSNPA....
X25DestAddr...... 123409 X25Port..... 9