OSI/AS Configuration and Management Manual

Troubleshooting Guide
OSI/AS Configuration and Management Manual—424119-001
8-30
Troubleshooting Example
Step 4: Collect Trace Information Using SCF
In this case, the error messages have not been very helpful, and 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. Use a command like the following to start the trace:
trace process $tap1, to tracefil, recsize 1000
While the trace is on, try again to establish a connection from the remote side.
After recording the problem, be sure to stop the trace. Use a command like the
following:
trace process $tap1,stop
Step 5: Analyze the Trace Using PTrace
The SCF command
ptrace from tracefil
starts the PTrace trace formatter on the trace located in the file TRACEFIL and displays
the following:
The PTrace command
log to logptr
names a file to store both your PTrace commands and the output, and displays the
following:
Next, set up the select mask and the filters to do a quick scan of the trace. Since you
already know that the incoming connect SPDU was refused within TAPS, you need only
focus on the Layer 5 activity.
The PTrace command
select l5
displays the following:
Trace of: \MARS.$TAP1, Type (55,5).
Ptrace Data File: $DIAG.MYSTUFF.TRACEFIL
Trace started: 10/16/91 13:38:53.02
First trace entry: 10/16/91 13:38:53.02
Last trace entry: 10/16/91 13:40:44.25
Trace file is an extended format.
Trace entry size limit: 1008
Ptrace Log File: $DIAG.MYSTUFF.LOGPTR
Ptrace Select Key: L5