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

Overview of System-Level NCL Procedures
Developing System-Level NCL Procedures
106160 Tandem Computers Incorporated 17–5
Automatic Restart of EMSPROC and LOGPROC
If a Guardian process that controls a background processing environment should fail,
the Guardian process is recreated and EMSPROC and LOGPROC are restarted
automatically by NonStop NET/MASTER MS. NCL processes started by EMSPROC
or LOGPROC (or other NCL processes executing in the background processing
environment) are not restarted automatically. For further information on the
automatic restart of NCL procedures in a background environment, see the subsection
called “Executing Persistent NCL” in Section 16, “Environments and Command
Processing.”
MSGPROC NCL
Procedures
The function of a MSGPROC NCL procedure is to intercept and process messages
destined for an Operator Control Services (OCS) window. A MSGPROC NCL
procedure runs under the control of the user with whom the MSGPROC NCL
procedure is associated. It has access to all the messages sent to the OCS window
under which it is executing (except messages generated from the MSGPROC NCL
procedure itself).
There may be many different MSGPROC procedures executing concurrently in
NonStop NET/MASTER MS. Every user operating in OCS may have none, one, or
two associated MSGPROC procedures—one associated with each OCS window.
Every MSGPROC in NonStop NET/MASTER MS may be the same or completely
different, to suit the requirements of each operator. Virtual users, such as the
Background Monitor and the Background Logger, and users from remote systems can
also have an associated MSGPROC NCL procedure to process messages.
MSGPROC as a System-Level NCL Procedure
Just as the LOGPROC NCL procedure is the only procedure in the system that can
review the messages flowing to the activity log, so a MSGPROC procedure is the only
procedure that can review and process the message traffic to a particular OCS
window. For this reason, MSGPROC is classified as a system-level procedure, even
though there may be many active MSGPROC processes in a NonStop NET/MASTER
MS system, on behalf of many different OCS windows.
Defining a MSGPROC NCL Procedure
The name of a user's MSGPROC procedure is normally defined in the user ID
definition for the user. If so, it is part of the NonStop NET/MASTER MS profile for
that user. Only one MSGPROC procedure can be defined in the user ID definition; if
defined, it is is automatically executed when the user enters OCS.
In OCS, a user with sufficient authority can use the PROFILE MSGPROC command to
specify a MSGPROC procedure for each window. The name specified does not have
to be MSGPROC. If it is not MSGPROC, however, it is still referred to as MSGPROC
or as a MSGPROC procedure. You can also use the PROFILE MSGPROC command to
flush a MSGPROC NCL procedure. The following command defines a MSGPROC
procedure called MSGPROCA:
PROFILE MSGPROC=MSGPROCA