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

Development Considerations for System-Level NCL Procedures
Developing System-Level NCL Procedures
106160 Tandem Computers Incorporated 17–19
The following screen shows the steps you should use:
(15:27) --------------------- OPERATOR CONTROL SERVICES ---------------------
PROFILE MSGPROC=MPROC2 <-- Loads MSGPROC
NNM0393 MSGPROC PROCESSING ACTIVATED
NNM0357 PROFILE HAS CHANGED
MSGPROC starting
PROFILE MSGPROC=FLUSH <-- Flushes MSGPROC
NNM2202 MSGPROC FLUSHED
NNM0357 PROFILE HAS CHANGED
SHOW PRELOAD=MPROC2 <-- On retain list?
NNM1050 NAME STATUS USERS REFCNT STMTS NCLBUF LIBRARY AGEUSE
NNM1051 MPROC2 RETAINED 0 1 21 2 JOHNNCLS 1
NNM0999 *END*
SYSPARMS UNLOAD=MPROC2,$DATA2.JOHNNCLS <-- Yes, so unload
NNM1057 UNLOAD OF MPROC2,$DATA2.JOHNNCLS ACCEPTED
SHOW PRELOAD=MPROC2 <-- Confirmation
NNM1052 NO NCL PROCEDURES PRELOADED OR AUTO-SHARED
PROFILE MSGPROC=MPROC3 <-- Load new MSGPROC
NNM0393 MSGPROC PROCESSING ACTIVATED
NNM0357 PROFILE HAS CHANGED
MSGPROC starting
_____________________________________________________________________________
---------- ------------------ NonStop NET/MASTER D30 ---------------- --------
M=>
Note While you are testing new versions of MSGPROC, you can ensure that you always use the latest version
by changing your operator profile so that test mode is on. The following command ensures that you
always use the latest version of MSGPROC during testing:
PROFILE NCLTEST=YES
See Section 8, “Executing NCL Procedures,” for more information on the active and
retain lists.
Identifying Messages From
System-Level NCL
Procedures
All messages from the EMSPROC NCL procedure are displayed at the terminals of
monitor-class users. These messages are prefixed with the E monitor prefix (rather
than the M monitor prefix, which normally prefixes monitor-class messages).
All messages from the LOGPROC NCL procedure are displayed at the terminals of
monitor class users. These messages are prefixed with the L monitor prefix (rather
than the M monitor prefix, which normally prefixes monitor class messages).
Note Messages from the LOGPROC NCL procedure itself go directly to the activity log; they do not go to
LOGPROC for processing. This ensures that no opportunity exists for a recursive processing loop.
If a user ID is defined as having a MSGPROC NCL procedure, all messages destined for the user's OCS
window are directed to MSGPROC for processing except messages from MSGPROC itself. This ensures
that no opportunity exists for a recursive processing loop.