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

Debugging an NCL Process From Start to Finish
Debugging an NCL Process
106160 Tandem Computers Incorporated 9–65
Step-by-Step Debugging of
the NCL Process
The following steps show one possible sequence you can use to debug the ZEX0904N
NCL process.
Step 1
Define local equate commands and function keys that abbreviate lengthy DEBUG
commands, as discussed earlier in this section.
Step 2
Start the debug session by using the DEBUG START command, as shown in the
following screen. A message on the OCS window indicates that the new NCL process
will be suspended.
Execute the ZEX0904N NCL procedure by using the START command and observe the
results, as shown in the following screen. The ZEX0904N NCL process is suspended at
statement 1, line 1.
In this example, the NCL ID of 670 is also the default NCL ID, and so the DEBUG SET
command is not essential: it is shown for the general case. All subsequent DEBUG
commands refer to the NCL process with the NCL ID of 670.
(06:47) --------------------- OPERATOR CONTROL SERVICES ----------------------
DEBUG START
NNM1949 NEW NCL WILL BE SUSPENDED IN THE TARGET ENVIRONMENT
START ZEX0904N 02 2020
NNM1901 NCL 000670 DEBUG SESSION INITIATED
NNM1902 NCL 000670 SUSPENDED AT ZEX0904N.1 LINE 1
DEBUG SET ID=670
NNM1091 DEFAULT NCLID SET TO 000670
_____________________________________________________________________________
---------- ------------------ NonStop NET/MASTER D30 ---------------- --------
M=>