NET/MASTER Network Control Language (NCL) Programmer's Guide

Tracing System-Level Messages
Developing System-Level NCL Procedures
17–30 106160 Tandem Computers Incorporated
If you do not specify the name of a trace file, the trace file name is created from the
default system name, the installation volume of NonStop NET/MASTER MS, the user
ID of the user starting the trace, the process character of NonStop NET/MASTER MS,
and the trace ID.
The following command starts a trace using the parameter settings in the TPL:
TRACE START
Assume that the system name is \SYS1, the installation volume name of NonStop
NET/MASTER MS is $DATA9, the user ID of the user starting the trace is NMTJN, the
process character of NonStop NET/MASTER MS is U, and this is the first trace you
have started. The following trace file is created:
\SYS1.$DATA9.NMTJN.UTR00001
Step 4. Sending Messages to the System-Level NCL Procedure
The fourth step in tracing system-level messages is to either wait for appropriate
messages to arrive at the system-level NCL procedure, or to use a message generator
to send messages to the system-level NCL procedure. The following NCL procedure
is designed to send a message to an OCS window. Type the following NCL
procedure, calling it ZEX1720N:
zex1720n: PROCEDURE
SAY &1
END zex1720n
The text of the message is entered as the first parameter.
After typing the NCL procedure, use the following command to send a message to the
OCS window:
START ZEX1720N AAAAA
The message AAAAA is sent to the OCS window. Using the criteria specified by the
preceding TRACE trace-spec command, the trace file should contain this message.
Step 5. Stopping the Trace
After using the message generator to send messages, the fifth step in tracing
system-level messages is to stop the trace. You must specify the trace ID to uniquely
identify the trace you want to stop. The following command stops the trace with a
trace ID of 1:
TRACE STOP=1
You can use the SHOW TRACE command to determine the trace ID of a trace.