NET/MASTER Management Services (MS) Operator's Guide

Performing a Test Compilation on an NCL Procedure
Automating Operations Tasks With NCL Procedures
10–6 106379 Tandem Computers Incorporated
The equates and function key definitions set by this procedure allow you to:
Type “SM” followed by a message in the OCS command line. For example:
SM SHUTDOWN in 10 minutes. Please log off.
Then press the SF13 function key to append your name to the end of the message
and send it to all operators with PROFILE MSG=YES and/or PROFILE
UNSOL=YES.
Press the SF14 function key to find out when everyone is logged off.
Route commands to NM1EAS by entering NY followed by the command string,
and to NM2WES by entering LA followed by the command string.
Performing a Test
Compilation on an
NCL Procedure
Perform a test compilation on an NCL procedure to check the syntax of the procedure
without executing it. It is good practice to perform a test compilation of any NCL
procedure you write before you attempt to execute it.
To perform test compilations of NCL procedure source files, use either:
The Compile option in Edit Services (see Section 9, “Using Edit Services”).
The NCLCHECK command in OCS or the Command Entry facility (refer to the
description of NCLCHECK in the NonStop NET/MASTER MS Command Reference
Manual).
Note Using the NCLCHECK command in the Command Entry facility gives you the option of printing your
compilation results if you have many errors.
The advantage of performing a test compilation in Edit Services is that you can list the
errors in the Edit Services Compile Report, correct them, and recompile the program
without leaving Edit Services.
A test compilation can detect three types of mistakes. From least to most severe, these
are:
A warning, which is a mistake that would not stop an NCL process from
executing but may cause it to execute unpredictably.
An error, which is a mistake that would cause an NCL process to stop executing.
A fatal error, which is a mistake that causes compilation to stop.
A test compilation does not check the logic of an NCL procedure. Thus, a successful
compilation does not guarantee that the NCL procedure will execute as expected. Use
the DEBUG command to detect errors in logic. The complete syntax of the DEBUG
command is described in the NonStop NET/MASTER MS Command Reference Manual.