Tracing is an interpretive diagnostic technique that provides
data for analysis, and can be done at many levels. SNA link tracing
is done at the lowest level and at an intermediate level (see the SNA
Link Services Reference Manual, or the SNA
Link/XL Node Manager's Guide). SNA NRJE tracing
is at the highest level, and is controlled through MPE commands
or NRJE commands (see Chapter 6 “Commands” of this manual).
The tracing facility for SNA NRJE performs two types of tracing: intrinsic
tracing and LU tracing.
Intrinsic Tracing |
 |
Intrinsic tracing records NRJE intrinsics called by NRJE users
or invoked through NRJE commands. Intrinsic trace records are created after
successful completion of the intrinsic. If the intrinsic fails,
only the Result array parameter is traced. Intrinsic tracing is turned
on with the NRJECONTROL START or NRJECONTROL TRACEON MPE command, or with the STARTWS or TRACEON NRJE command. It is turned off with the NRJECONTROL TRACEOFF MPE command or the TRACEOFF NRJE command. Intrinsic tracing goes to a disk file.
The trace file name can be specified as an argument to any of the
commands used to start tracing. Naming the file this way allows
the contents of the file to be overwritten each time a new trace
is started. (No warning is issued.) Or you can let the default name
be assigned: NMTCnnnn.PUB.SYS, where nnnn is a number from 0000 through 9999.
The trace file can be formatted through the NMDUMP utility. Using NMDUMP for SNA NRJE is described
later in this chapter. More detailed information about NMDUMP is
contained in the SNA Link Services Reference Manual (for
MPE V) and in Using the Node Management Services Utilities (for
MPE XL).
LU Tracing |
|
You should use LU tracing only under the recommendation of
an HP service representative.
LU tracing records NRJE internal program events. Most modules
are traced during LU tracing. LU tracing for a workstation can be
initially turned on only when the workstation is started. After
that, it can be turned off or on as long as the workstation is active.
LU tracing is turned on with the NRJECONTROL START or (once the workstation is active) NRJECONTROL TRACEON MPE command, or with the STARTWS or (once the workstation is active) TRACEON NRJE command. It is turned off with the NRJECONTROL STOP or NRJECONTROL TRACEOFF MPE command, or the STOPWS or TRACEOFF NRJE command. LU tracing goes to a disk file. The trace
file name can be specified as an argument to any of the commands
used to start tracing. Naming the file this way allows the contents
of the file to be overwritten each time a new trace is started (no
warning is issued). Or you can let the default name be assigned: NMTCnnnn.PUB.SYS, where nnnn is a number from 0000 through 9999.
The trace file can be formatted through the NMDUMP utility. Using NMDUMP for SNA NRJE is described
later in this chapter. More detailed information about NMDUMP is
contained in the SNA Link Services Reference Manual (for
MPE V) and in Using the Node Management Services Utilities (for
MPE XL).
|
| |
|
 | NOTE: Although the format of the default trace file name is
the same for all types of tracing, the same default file name will
not be assigned for more than one trace. This is because the default
trace file name is automatically assigned in numerical order. For
example, suppose the last default trace file name assigned was NMTC0004.PUB.SYS. If you started SNA Transport intrinsic tracing,
and did not specify a trace file name, the default name NMTC0005.PUB.SYS would be assigned. Then, if you started SNA NRJE
intrinsic tracing without specifying a trace file name, the default
name NMTC0006.PUB.SYS would be assigned. Finally, if you started NRJE
LU tracing, and did not specify a file name, the default name NMTC0007.PUB.SYS would be assigned. Remember, this applies only when you are using the default
file-naming scheme. |
|
| |
|
