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

Getting Started With NCL Procedures
An NCL Tutorial
3–10 106160 Tandem Computers Incorporated
Step 6
Check for mistakes after the test compilation by looking at the message line that
appears at the top of the Edit Services selection list screen, as shown in the following
screen:
------------------------- Edit Services : Selection List ----------------------
File Spec:
Subvolume: $DATA9.MYNCLLIB
T=Test a panel S/B=Browse C=Compile D=Delete E=Edit
*END* 0 ERRORS 0 WARNINGS
Filename Code EOF Last Modification Owner RWEP
HELLO1 101 2132 11-NOV-1994 11:03:11 100,21 CCCC
F3=Exit F7=Prev F8=Next F11=Error List
There are three types of mistakes that can result from a test compilation. From least to
most severe these are warnings, errors, and fatal errors.
Note A test compilation does not check the logic of an NCL procedure. Accordingly, if a test compilation is
successful, it does not guarantee that the NCL procedure will execute as expected. You can use the
DEBUG commands, discussed in Section 9, “Debugging an NCL Process,” to detect errors in logic. The
complete syntax of the DEBUG commands is described in the NonStop NET/MASTER MS Command
Reference Manual.
Successful Test Compilation. If you typed the HELLO1 NCL procedure exactly as shown
earlier in this section, then you will have 0 errors and 0 warnings. This means that you
have made no syntax errors; the test compilation was successful. If the test
compilation was successful, go to Step 7.
Unsuccessful Test Compilation. If you made a mistake typing the HELLO1 NCL
procedure, then you will have some errors or some warnings. This means that you
have made some syntax errors; the test compilation was unsuccessful. If the test
compilation was unsuccessful, go to Step 11.