NET/MASTER Management Services (MS) System Management Guide

Sending Event Messages from NCL to EMS
Managing Event Messages
8–10 115414 NonStop NET/MASTER MS System Management Guide
EMSPROC procedure is named EMSPROC1 and you want to replace the procedure
with another named EMSPROC2. If you enter the following command
SYSPARMS EMSPROC=EMSPROC2
without first flushing EMSPROC1, neither events being processed nor events queued
for processing are lost.
To flush the current EMSPROC procedure, issue the following command:
SYSPARMS EMSPROC=FLUSH
The default value of the EMSPROC operand is FLUSH.
Flushing the EMSPROC procedure results in the default message processing described
in “Processing Event Messages” earlier in this section.
Sending Event
Messages From NCL
to EMS
NonStop NET/MASTER MS sends its own EMS event messages to the $0 collector
process. Any NCL procedure, such as the EMSPROC procedure, can send event
messages to an alternate collector by using the EMSSEND verb. The verb enables an
NCL procedure to send messages to an EMS log file other than that used by the
primary collector, for example.
Use the EMSCOLLPNM operand to specify the name of the collector process to which
the EMSPROC procedure sends event messages. Specify EMSCOLLPNM as a valid
process name. The following example specifies an EMS collector process name of
$EMSC:
SYSPARMS EMSCOLLPNM=$EMSC
The default value is $0, and you can specify only one collector process.
NonStop NET/MASTER MS assumes that the EMS collector process is executing
when it attempts to use the collector process.
Note All event messages generated by NonStop NET/MASTER MS itself, as opposed to messages sent by the
EMSSEND verb, are sent to the $0 collector process, regardless of the EMSCOLLPNM operand setting.
Use the EMSCOLL command to start or stop the transmission of event messages from
NonStop NET/MASTER MS to the EMS collector process specified by the
EMSCOLLPNM operand of the SYSPARMS command. For example, to begin sending
messages to the configured event collector process, issue the following command:
EMSCOLL START
To stop the transmission of event messages to the collector process, issue this
command:
EMSCOLL STOP
When you stop the transmission of event messages, the messages are discarded as they
arrive, until the EMSCOLL START command is issued. NonStop NET/MASTER MS
sends a message to its activity log and to all monitor-class terminals when a user issues
the EMSCOLL START and EMSCOLL STOP commands.