NET/MASTER Management Services (MS) System Management Guide

Processing Event Messages
Managing Event Messages
115414 NonStop NET/MASTER MS System Management Guide 8–9
Using an EMSPROC
Procedure
The EMSPROC procedure is a system-level NCL procedure that receives unsolicited
messages from an EMS consumer distributor. As an NCL procedure, the EMSPROC
procedure can be enhanced to apply any NCL feature to message filtration and
processing. You can use a customized EMSPROC procedure to perform many tasks,
such as automating responses to event messages. The following tasks represent some
of the purposes for which an NCL programmer can create an EMSPROC procedure:
Message filtration—The EMSPROC procedure can either suppress EMS messages
altogether or forward select messages to other destinations within NonStop
NET/MASTER MS. You can filter messages according to any criteria you specify,
such as the following:
Subsystem
Message number
Any Subsystem Programmatic Interface (SPI) token in the message
Messages filtered by the EMSPROC procedure are completely removed from
further processing by the LOGPROC procedure or the MSGPROC procedures.
Counting messages—If you prefer to know only the number of occurrences of an
event, as opposed to seeing every instance of its associated message, you can
direct the EMSPROC procedure to increment a counter each time it receives a
designated event during a specified interval.
Message routing—Primarily used for remote systems. You can route some or all
event messages to another system on which NonStop NET/MASTER MS is
running.
Automating recovery—An EMSPROC procedure can pass an event message to
another NCL procedure that initiates a recovery procedure for the problem about
which the message was reported.
Refer to the NonStop NET/MASTER NCL Programmer’s Guide for an explanation of how
to write and modify an EMSPROC procedure.
Note The EMSPROC procedure runs in either an EM or NC process. If the process in which the EMSPROC
procedure is running fails, event messages are resent from slightly before the last message processed
before the failure. Therefore, the customized EMSPROC procedure must cater for receiving some
duplicate event messages when restarted after failure.
Use the EMSPROC operand of the SYSPARMS command to load or flush an
EMSPROC procedure. Specify EMSPROC as the name of an NCL procedure. For
example, to load an EMSPROC procedure named EMSPROC1, issue the following
command:
SYSPARMS EMSPROC=EMSPROC1
The command enables you to change an EMSPROC procedure without losing or
failing to process any event messages. Suppose, for example, that your active