SNAX/XF and SNAX/APN Configuration and Management Manual

SCF Commands for SNAX/XF and SNAX/APN
SNAX/XF and SNAX/APN Configuration and Management Manual—425836-006
13-145
TRACE Command
modem problem, an SDLC protocol violation, or a CLIP or controller problem), then
SELECT ALL is recommended.
WRAP
The use of this option is recommended in most situations. If you do not specify WRAP,
tracing will stop when the disk trace file becomes full. This condition is not usually
desirable, because it is likely that the trace will stop before the problem is captured.
Examples of Trace Commands for LINE Objects
The following examples illustrate the use of the TRACE command to trace SNAX/XF
and SNAX/APN lines.
The command below starts a line trace specifying that the trace collector is not to be
used, and that trace records are to be wrapped in the disk file when the file becomes
full:
->TRACE LINE $SNAP1, TO $BETA.WORK.TRCEDATA, NOCOLL, WRAP, &
->PAGES 4
The following command stops the previously specified trace:
->TRACE LINE $SNAP1, STOP
The following command starts a trace of the SDLC data, PIUs, and BIUs for all objects
on a line:
->TRACE LINE $SNAP2, TO $BETA.WORK.TRCEDATA, &
->SELECT (L2DATA, PIU, BIU)
The following command starts a trace of the BIUs for all LUs on a line:
->TRACE LINE $SNAP1, TO $BETA.WORK.TRCEDATA, LUSELECT ALL, &
->SELECT BIU
The following command is equivalent to the commands above:
->TRACE LINE $SNAP1, TO $BETA.WORK.TRCEDATA, SELECT BIU
The following command starts a selective trace of the SDLC data and PIUs for a
specific PU:
->TRACE LINE $SNAP2, TO $BETA.WORK.TRCEDATA, PUSELECT #PU6, &
->SELECT (L2DATA, PIU)
The following command starts a selective trace of the SDLC data, PIUs, and BIUs for a
specific PU and three specific LUs:
->TRACE LINE $SNAP2, TO $BETA.WORK.TRCEDATA, PUSELECT #PU4, &
->LUSELECT (#LU1, #LU2, #LU3), SELECT (L2DATA, PIU, BIU)