EMS Manual

Standard Events
EMS Manual—426909-005
9-4
Object State Monitoring Functions
and display these tokens for the human operator according to the EMS template
provided for the event.
You define an EMS template for each standard event so that information is
presented consistently to operators. Subsystem and application developers are
expected to use these standard templates for their standard events.
With each event, EMS event viewers also display advisory text—additional text
which is defined by the subsystems and applications that generate the event, and
which contains:

Probable cause of the condition reported in the event

Effect on the system from the condition reported in the event

Recovery actions the operator can take to correct or bypass the condition
reported in the event

Event text for the human operator should be easily translated to other languages.
Standard events should not contain tokens with text for the human operators. All
text for human operators should be defined using EMS templates. Standard
templates make translation easier because there are far fewer templates to
translate.
Object State Monitoring Functions
Monitoring the state changes of objects is often used by problem management
applications to help detect, isolate, and sometimes diagnose hardware and software
failures. Object-state-monitoring products such as Distributed Systems Management
Solutions (DSMS), service tools used by customer engineers, and automated operator
products such as Programmable Network Administrator (PNA), rely on events to
provide the state change information for objects. These management applications
need to know:

When an object becomes available for use
An object is available when it is supplying the service it was designed to provide at
any level of performance, quality, or response time; specifically, when the operator
has enabled the object for use and all the underlying services that the object
depends on are available for use. Objects from another subsystem or the operating
system could supply these services. For example, a SNAX/XF LU needs the
SNAX/XF LINE to be available before it can become available, or the object must
have enough memory before it can run. Report the Object Available event when
the object enters this state.

When an object becomes unavailable for use
An object is unavailable when it cannot supply the service it was designed to
provide at any performance level, quality, or response time; specifically, when the
operator has disabled the object for use or the underlying services that the object
depends on are not available. Report the Object Unavailable event when the object