EMS Manual

Standard Events
EMS Manual—426909-005
9-12
Event Numbers
Subsystems determine the objects to report in an event. However, this section
recommends some commonly used schemes for naming objects in events. Use one of
these schemes to name your objects to minimize the amount of subsystem-specific
knowledge a management application needs to learn.
For the requirements and the naming schemes for objects represented by a single
group name, see Object Name for a Group of Objects on page 9-16. Group name is
particularly important for subsystems that have many objects that could be affected by
a single condition in the system. Group name lets the subsystem report a single event
for all these objects instead of a single event for each of these objects.
Event Numbers
Every event message has an event number. The event number together with the
subsystem ID (SSID) uniquely identifies an event message in a NonStop Kernel
network, which lets management applications quickly identify the action needed for a
particular object in the system. Design the event number to identify the subject type
and condition within a subsystem or application. Subject type is the type of the object
specified in the event subject, such as an X.25 line. The condition is the situation being
reported for the event subject. For example, an object is unavailable.
For example, if an application has two object types: A and B, and both are reporting
these conditions: object unavailable, object available, and object crossed usage
threshold, the application will have six unique event numbers, one for each of these
incidents:

Event reporting object type A crossed usage threshold

Event reporting object type A unavailable

Event reporting object type A available

Event reporting object type B crossed usage threshold

Event reporting object type B unavailable

Event reporting object type B available
An event number is associated with a set of tokens. The tokens that will be present are
the tokens specified as unconditional when the event is defined. Using the event
number and SSID information lets management applications predict the tokens in an
event.
Event Types
Each standard event has a unique event type—the standard event type—specified by
the Standard Content Type token. The event type identifies the condition, such as
object unavailable, and the tokens in the event. Because these tokens are defined
here, they are unique across all subsystems and applications and can be interpreted
without the specific knowledge of the subsystem or application.