SNA Link/iX Node Managers Guide (30291-90009)

Chapter 6 165
MPE Commands
SNACONTROL TRACEON
contents; no warning is issued. If you specify an
existing file that NMS already has open to record
tracing (even if it is recording events from a different
subsystem), NMS will record trace events for this
subsystem to the file in addition to the events that it is
currently recording. This allows you to record tracing
events from several subsystems to a single file.
Default: NMTC
nnnn .PUB.SYS, where nnnn is a number
from 0000 through 9999 and is incremented each time a
new file is created.
LUName Required. The name of the LU for which SNA
Transport intrinsic tracing is to be turned on. The
name can be up to eight alphanumeric characters long;
the first character must be alphabetic.
NOTE Activate SNA Transport intrinsic tracing with this command only when
recommended by your Hewlett-Packard support contact.
NumRecords The file size, in units of 128-word records, for link-level
tracing.
Range: 1-32767 (integer)
Default: 1024
Description
SNACONTROL TRACEON turns on link-level tracing (with the LINKTRACE
parameter), SNA Transport intrinsic tracing (with the INTRINSIC
parameter), and SNA Transport node tracing (with the NODETRACE
parameter). Note that SNA Transport node tracing is also turned on
with SNACONTROL START. Tracing is described in Chapter 5 , “SNA Link
Troubleshooting,” of this manual. You can use intrinsic tracing to verify
SNA Transport procedure calls. For an SDLC link, you can use
link-level tracing to verify data passed between SNA and the SDLC
link driver and between the link driver and the PSI card.
Examples SNACONTROL TRACEON;NODE=IBMNODE;LINKTRACE
Partial (the default) link-level tracing is to be started for all LUs on
node IBMNODE. The trace data is to be written to the default trace file.
SNACONTROL TRACEON;LINKTRACE=FULL,TF01
;INTRINSIC=LU02
Full link-level tracing is to be started for the only active SNA node, and
the trace data is to be written to file TF01. Also, intrinsic tracing is to
be started for LU02 on the node and that trace data is to be written to
the default trace file. Note that if more than one node was active, this
command would not be valid: A list of configured nodes would be