EMS Manual

Standard Events
EMS Manual—426909-005
9-11
Underlying Philosophy of Standard Events

Information about the subsystem or application reporting the message—a
subsystem identifier (SSID), process identifiers, and other relevant information
about the creator of the message. Some information is conditional; for example
batch job ID. Standard events contain a batch job ID token only if the object is part
of a batch job (has a job ID).
The SSID uniquely identifies the subsystem or application that defines and
generates the event message. Information in the event message usually requires
the SSID for interpretation unless it is standard event information. In that case, the
information is unique across all subsystems and applications and does not require
the SSID for interpretation.

Information about the subject of the event message—objects selected by
subsystems and applications, such as the name or names of objects that the event
reports on, that are the subjects of their events.

Information about the condition reported in the event message—an event number
that uniquely identifies the message within the subsystem or application and
indicates what happened to what object in the subsystem, and an event type that
uniquely identifies the type of message in the system and indicates what happened
in the subsystem. The event type is either explicitly defined in this section or
implicitly assumed by default, and provides a quick indication of the conditions
reported in the system.

Information about the actual incident — details about the occurrence and its
environment.
Information in an event message is represented by EMS tokens. An EMS token
describes the type, length, and value of a piece of information. An EMS template is
associated with an event message, but not as tokens in the event message, to provide
instructions for the display of the event message.
Certain event messages, like the Object Unavailable event, contain information about
their cause, effect, and recovery. This information is also provided in an EMS template.
This section defines only the minimal set of tokens needed in a standard event to
support a management function. It standardizes all token use except for the objects in
a subsystem and the error or diagnostic information in describing the fault (that is,
information specific to a subsystem that cannot be standardized). Standard events—
and the standard templates defined with them—provide a minimal but common
environment where a management application can make the same assumptions
across all subsystems and applications regarding a management function. Standard
events do not completely define all possible situations in the system reported in the
event. Subsystems and applications should provide additional information in these
events that can help operators better understand the subsystem conditions that these
events report.
This section discusses some important underlying concepts of standard events. For
details of a standard event, see Detailed Description of Standard Events on page 9-17.
For details about the display of a standard event, see Description of Standard EMS
Templates on page 9-34.