EMS Manual

Standard Events
EMS Manual—426909-005
9-17
Detailed Description of Standard Events
name in the token is a group. This style of group naming is consistent with the
second level of support for object template naming used by communication
subsystems internally at HP.
The wild-card format is allowed because it is an established way for naming a group of
objects by certain subsystems. The new token identifier format is allowed because not
all objects use the wild-card naming scheme.
Subsystem developers should use one of these schemes to represent their group
names. Do not proliferate another scheme as it will complicate the design of
management applications. The scheme a subsystem uses should be clearly
documented.
Detailed Description of Standard Events
Information in an event message is represented by EMS tokens. Every event message
contains a set of tokens called common-standard tokens and another set of tokens
called event-specific tokens.
Common-standard tokens are tokens that must be present in all event messages. They
are defined in this section. Some common-standard tokens, which are automatically
provided by EMS when the subsystem or application uses the procedure provided by
EMS (for example, EMSINIT) to build its event buffer, are described in Common-
Standard Tokens That EMS Provides on page 9-18. Other common-standard tokens,
which must be provided by the subsystem or application when it builds the event
buffer, are described in Common-Standard Tokens That Subsystems Provide on
page 9-20.
Event-specific tokens are tokens that are present only in the event of that type. For
standard events, the event-specific tokens are defined in the subsection where that
event is described. For events defined by subsystems (private events), the event-
specific tokens are defined in that subsystem or application.
EMS tokens defined in this section are for the NonStop Kernel only. Each token is
described by this information:

The DDL name of the token and the standard values assigned to the token. The
DDL name is specified as ZSPI-TKN-??? or ZEMS-TKN-??? and is defined in the
standard SPI definition file (ZSPIDDL) or the standard EMS definition file
(ZEMSDDL), respectively.

The DDL name of the token type. The DDL name is specified as ZSPI-TYP-???
and is defined in the standard SPI definition file ZSPIDDL.

The condition under which the token is to be provided. “U” means the token is an
unconditional token and must always be provided. Many unconditional tokens are
automatically generated for you, which means you do not create them using
procedures. Descriptions of the tokens and guidelines for the token generating
procedures indicate if you need to create them.