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

Identifying Messages From a Remote System
Developing System-Level NCL Procedures
106160 Tandem Computers Incorporated 17–27
Identifying Messages
From a Remote
System
When EMSPROC at your local NonStop NET/MASTER MS system receives an event
message from a remote NonStop NET/MASTER MS system, you can easily identify
the node that generated the message by using the domain ID at the beginning of the
message.
However, when EMSPROC at your local NonStop NET/MASTER MS system receives
an event message from a remote system that is not running NonStop NET/MASTER
MS, the message does not have a domain ID (because there is no remote NonStop
NET/MASTER MS system to create one).
In this case, you can still identify the source of the message by obtaining the value of
the &$EMS.SPI.TANDEM.ZEMS_TKN_NODENAME (or
&$EMS.SPI.TANDEM.ZEMS_TKN_CRTPID) MDO variable. After obtaining this
value, you can ensure that OCS operators can recognize the source of the message by
prefixing the value to the &$EMS.TEXT MDO variable before the text is displayed at
an OCS window.
The following code segment explicitly prefixes the name of the Tandem node that
generated the message to the text of the message:
…
&$EMS.TEXT = &$EMS.SPI.TANDEM.ZEMS_TKN_NODENAME || “ ” || &$EMS.TEXT
…
The following code segment places the name of the process that generated the message
(including the Tandem node name) in the &$EMS.PREFIX.MSGTEXT MDO variable:
IF LEFT(&$ems.spi.tandem.zems_tkn_crtpid, 1) == "\" THEN
&$ems.prefix.msgtext =,
"["SUBWORD(&$ems.spi.tandem.zems_tkn_crtpid,1,1)"]"
ELSE
&$ems.prefix.msgtext =,
"["&$ems.spi.tandem.zems_tkn_nodename"." ||,
SUBWORD(&$ems.spi.tandem.zems_tkn_crtpid,1,1)"]"
The result is that the node name is prefixed to the message when the message is
displayed on an OCS window. (If the value of PROFILE PREFSYS is equal to YES, the
NonStop NET/MASTER MS domain ID is also prefixed to the message when the
message is displayed.)