NET/MASTER Network Control Language (NCL) Reference Manual

EMSALERT
Verbs
3–50 106126 Tandem Computers Incorporated
EMSALERT The EMSALERT verb generates an Event Management Service (EMS) event message
from an NCL procedure and sends it to the EMSPROC NCL procedure. The message
is always marked as originating from the local system.
You use this verb in an NCL procedure to generate event messages and feed them to
the standard event processing points. These points can be in the local system or in
single or multiple connected systems using Inter-System Routing (ISR).
Note Because EMSALERT (as distinct from EMSSEND) does not pass any messages through the default
Tandem NonStop Kernel event collector ($0), no SPI tokens are added to those created by the initiator of
EMSALERT. However, if you use the keywords TEXT, SSID, and EVENTNUM, NCL places
information in specially created SPI tokens and in the MDO variable &$EMS.TEXT. NCL places a prefix
sssnnnn in &$EMS.TEXT where sss is the subsystem identifier and nnnn is the event number, and
this prefix is followed by the text of the message. For a full discussion of EMSALERT, refer to the
NonStop NET/MASTER NCL Programmer's Guide.
Depending on the delivery operand specified, the message is queued to the local
EMSPROC NCL process, if it is active. The EMSPROC NCL process may then delete
the message or alter the destination of the message.
An EMSPROC NCL procedure is a system-level NCL process that intercepts and
processes messages from the EMS subsystem. An EMSPROC NCL procedure uses
special message-handling verbs beginning with the letters EMS.
EMSALERT [ ALL |
DOMAIN= domainid |
LINK= linkname |
LOCAL |
REMOTE ]
MDO= mdo-name |
{ TEXT= event-text
SSID= owner.number.version
EVENTNUM= nnnnn }
ALL
specifies that the EMSALERT message is to be delivered to the local system
(through EMSPROC, if active) and to all connected systems.
DOMAIN= domainid
specifies that the EMSALERT message is to be delivered to the connected system
with the specified domainid .