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

The NCL Process Identifier (NCL ID)
Executing NCL Procedures
8–16 106160 Tandem Computers Incorporated
If NonStop NET/MASTER MS cannot find the NCL procedure using the active and
the retain lists, it tries to load the NCL procedure from disk. It uses the default or
customized search path to search, beginning from the user procedure library.
If NonStop NET/MASTER MS finds the NCL procedure, it automatically compiles
and executes it. NonStop NET/MASTER MS also uses the settings of the SYSPARMS
NCLPRSHR command to determine what to do with the procedure after it has found
it.
If NonStop NET/MASTER MS cannot find the NCL procedure using the default or
customized search path, it reports that the NCL procedure cannot be found.
The NCL Process
Identifier (NCL ID)
NonStop NET/MASTER MS automatically assigns every NCL procedure a unique
number when it begins execution. When an NCL procedure begins execution it is
called an NCL process; the number, therefore, is called its NCL process identifier
(NCL ID).
The NCL ID is used to uniquely identify a certain NCL process. This is usually when
the NCL process is to be the target of a NonStop NET/MASTER MS command. An
NCL ID is a six-digit number from 1 through 999999. The NCL ID allows individual
NCL processes to be identified even when NCL processes are executing the same NCL
procedure.
NCL procedures that are executed using the START command are allocated an NCL
ID immediately because these NCL procedures begin execution immediately. NCL
procedures that are executed using the EXEC command or submitted for execution at
a particular time or frequency are allocated an NCL ID when they begin execution.
An NCL process can obtain its own NCL ID by using the &SYS.NCLID system
variable.
NonStop NET/MASTER MS commands that can specify an NCL ID, by using the ID
operand, include the DEBUG, FLUSH, GO, INTQ, SHOW NCL, and SHOW PAUSE
commands.
Note The default authority level of the ID operand is 2. You require an authority level of at least 2 if you want to
use the ID operand to target an NCL process that you do not own.
The FLUSH and SHOW NCL commands are discussed later in this section. The
DEBUG commands are discussed in Section 9, “Debugging an NCL Process.” The GO
and SHOW PAUSE commands are briefly described later in this section and in
Section 13, “Interaction With Users and Terminals.” The INTQ command is described
in Section 16, “Environments and Command Processing.”
The syntax of every command is described in the NonStop NET/MASTER MS Command
Reference Manual.