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

Sending a Message to an NCL Process When it Is Started
Environments and Command Processing
16–62 106160 Tandem Computers Incorporated
4. Type the second NCL procedure as shown, calling it ZEX1625N:
zex1625n: PROCEDURE
/* Started by EMSPROC for simple automation. */
/* This asynchronous NCL process is started */
/* by the START verb to handle an Expand */
/* message, which reports line problems. */
CONTROL NOENDMSG
&line = &$prm.spi.&($prm.spi.tandem.zems_tkn_subject_mark)
INTCMD "OPSYS START EXPAND LINE "&line
INTREAD
/* You would normally add some checking here */
/* to determine whether the line is started. */
WRITE LOG=YES INTENS=HIGH,
DATA="EXPAND LINE "&line" STARTED BY EMSPROC"
END zex1625n
5. Copy ZEX1625N to the user procedure library owned by BMON. (You can
determine the name of this library by looking at the user ID definition record for
BMON in User ID Management Services (UMS).)
6. Type the third NCL procedure as shown, calling it ZEX1626N:
zex1626n: PROCEDURE
/* Started by EMSPROC for simple automation. */
/* This asynchronous NCL process is started */
/* by the START verb to handle a SNAX/XF */
/* message, which reports line problems. */
CONTROL NOENDMSG
&line = &$prm.spi.&($prm.spi.tandem.zems_tkn_subject_mark)
INTCMD "OPSYS START SNAX LINE "&line
INTREAD
/* You would normally add some checking here */
/* to determine whether the line is started. */
WRITE LOG=YES INTENS=HIGH,
DATA="SNAX LINE "&line" STARTED BY EMSPROC"
END zex1626n
7. Copy ZEX1626N to the user procedure library owned by BMON.