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

Development Considerations for System-Level NCL Procedures
Developing System-Level NCL Procedures
17–12 106160 Tandem Computers Incorporated
The following screen shows the results of executing the procedure:
(14:03) --------------------- OPERATOR CONTROL SERVICES ----------------------
PROFILE MSGPROC=ZEX1703N
Full text is NNM0393 MSGPROC PROCESSING ACTIVATED
Word 1 is NNM0393
Word 2 is MSGPROC
Word 3 is PROCESSING
Word 4 is ACTIVATED
Full text is NNM0357 PROFILE HAS CHANGED
Word 1 is NNM0357
Word 2 is PROFILE
Word 3 is HAS
Word 4 is CHANGED
_____________________________________________________________________________
---------- ------------------ NonStop NET/MASTER D30 ---------------- --------
M=>
General Design Features When you write a system-level NCL procedure, it is recommended that you use the
following guidelines:
Write the system-level NCL procedure as a closed loop (by using a DO FOREVER
loop).
Prevent the system-level NCL procedure from terminating.
Ensure that the system-level NCL procedure is short.
Write the System-Level NCL Procedure as a Closed Loop
It is recommended that you write EMSPROC, LOGPROC, and MSGPROC procedures
as closed loops; this ensures that the NCL process executes indefinitely. If a system-
level procedure is not written as a closed loop, a critical system-level message that you
want to intercept and process may pass through to its destination undetected.
Figure 17-1 displays a closed loop. The figure shows that, after a system-level NCL
procedure is executed, execution should continue until the first EMSREAD,
LOGREAD, or MSGREAD verb is encountered. The NCL process should then
suspend processing and wait for the next message.