EMS Manual

Standard Events
EMS Manual—426909-005
9-3
Requirements for Standard Events
Requirements for Standard Events
These events are designed to support requirements from known existing management
applications running on NonStop systems. These requirements should be satisfied for
future enhancements to these standard events. The requirements are:

Each standard event supports a well-defined management function or operation.
Events without a clear purpose should not be defined. This table shows
management functions and the type of events that support them:

Standard events support the batch environment.
Standard events contain a batch job ID token only if the object is part of a batch job
(has a job ID). Batchjob ID is a conditional token.

Standard events drive automation.
All standard events should contain sufficient information to perform the intended
management function. The information must have the same syntax and semantics,
whenever possible, across all subsystems and applications. This makes writing
management applications easier for the intended management function or
operation.

Standard events avoid generating a deluge of events by a single system condition.
Subsystems and applications that have many objects that a single system
condition could affect should be able to generate one event for all these objects,
instead of one event for each object. Standard events let subsystems define a
group name that represents all their objects of the same type or let them specify
multiple objects in the event.
A subsystem that has many objects that a single system condition could affect
should not generate one event for each object. The potential volume for such
events is too high.

Standard events are presented to the human operator in a consistent manner.
Information in EMS events is represented by EMS tokens. Tokens are designed for
programs, not for human operators. EMS event viewers, such as ViewPoint, format
Management Function or Operation
Supporting Standard Event
Type
More
Information
Object state monitoring Object Unavailable
Object Available
Object Other State Change
9-4
Reactive problem management Object Unavailable 9-5
Proactive problem management Usage Threshold
Transient Fault
9-8
Production requests requiring operator
attention
Operator Attention Needed
Operator Attention Completed
9-9