HP 3000 Manuals HP 3000 Manuals
SNACONTROL TRACEON
Turns on link-level tracing, SNA Transport intrinsic tracing, and SNA
Transport node tracing.
Syntax
SNACONTROL TRACEON;NODE=NodeName
[;LINKTRACE[=[TraceType][,TraceFile]]]
[;INTRINSIC=LUName[,TraceFile]]
[;NODETRACE[=TraceFile]]
[;TFILESIZE=NumRecords]
Use
SNACONTROL TRACEON can be issued from a session, a job, a program, or in
break. Pressing [BREAK] has no effect on this command.
Parameters
NodeName Conditionally required. The name of the active SNA
node for which you want to turn tracing on. The name
can be up to eight alphanumeric characters long; the
first character must be alphabetic.
If only one SNA node is active, this parameter is
optional: If you do not include it, the specified
tracing for the active node is turned on. If more
than one node is active, this parameter is required:
If you do not include it, an error message is
displayed and no tracing is started.
TraceType The kind of link-level tracing to be started:
* FULL = Full line tracing: All of the bytes of
each link frame are traced.
* PARTIAL = Partial line tracing: Only the
first 16 bytes of each link frame are traced.
Default: PARTIAL
TraceFile The name of the disk file that is to contain the
trace data. This must be a valid MPE file name or
fully qualified MPE file reference. Standard MPE
file naming conventions apply.
If you specify a file that does not exist, NMS builds
a new one and opens it to record tracing. If you
specify an existing file that NMS does not currently
have open to record tracing, NMS will overwrite the
file's previous 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: NMTCnnnn.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 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 displayed, and the command would have to be reissued with the
proper NODE=NodeName parameter included.
SNACONTROL TRACEON;LINKTRACE=,TF01
Partial (the default) link-level tracing is to be started for the only
active SNA node, and the trace data is to be written to the file TF01.
Note that if more than one node was active, this command would not be
valid: A list of configured nodes would be displayed, and the command
would have to be reissued with the proper NODE=NodeName parameter
included.
SNACONTROL TRACEON;LINKTRACE=;INTRINSIC=LU02
This command is not valid because the equal sign is specified with the
LINKTRACE parameter, but no values are specified after it (the equal sign
should be included only if one or both of the values after it are
specified); an error would occur.