NET/MASTER Management Services (MS) Operator's Guide

The Event Message Flow
Operator Control Services (OCS)
4–26 106379 Tandem Computers Incorporated
Unsolicited Message Receipt
The following PROFILE attributes for current OCS session:
PROFILE EMS=YES, NO, INFO, NORM, WARN, or SER
PROFILE MONMSG=YES or NO
PROFILE MSG=YES or NO
PROFILE MSGCODE= message-code
PROFILE MSGPROC= ncl-procedure
PROFILE UNSOL=YES or NO
The level of message filtering programmed into:
The EMSPROC system procedure (see “The Event Message Flow” next)
The MSGPROC procedure (if any) associated with your current OCS window
(see “The Event Message Flow” next)
The Event Message
Flow
Within the local system, NonStop NET/MASTER MS works with the Tandem Event
Management Service (EMS).
Objects in Tandem subsystems generate EMS event messages when events occur that
usually require external resolution. These event messages are sent to an EMS collector
process for storage and distribution. Several EMS collectors can be collecting events
from several sources concurrently.
Both Tandem EMS messages and IBM PPO messages routed to the local system are
passed to a NonStop NET/MASTER NCL procedure referred to as an EMSPROC
procedure. Each NonStop NET/MASTER MS system may have an associated
EMSPROC procedure (configured with the SYSPARMS EMSPROC command) that
intercepts and processes unsolicited messages. The EMSPROC procedure can be
programmed to:
Delete, change, or pass messages
Create new messages
Forward messages to other systems
Respond to specific types of messages and either discard them or change their
attributes before forwarding them on
Note EMSPROC, LOGPROC, and MSGPROC are generic names that refer to the function of the associated
NCL procedures. They may have any legal file name.