NonStop Operating System Event Management Programming Manual

HP NonStop Operating System Event Management Programming Manual—520372-020
2-1
2 Header and Common Tokens
Operating system component event messages consist of common header tokens and
a common set of nonheader message tokens. This section describes the tokens that
are common to all operating system component event messages:

Event-Message Header Tokens on page 2-1

Common Tokens on page 2-3
This section also summarizes Subsystem Programmatic Interface (SPI) Standard
Token Types on page 2-5.
Event-Message Header Tokens
Every EMS event message has a header section consisting of a common set of header
tokens. Header tokens are either ZSPI- tokens (standard SPI tokens) or ZEMS- tokens
(standard EMS tokens).
Table 2-1. Common Event-Message Header Tokens (page1of2)
Header Token Token Type What Token Specifies
ZSPI-TKN-MAX-FIELD-VERSION ZSPI-TYP-UINT Latest software RVU
associated with a field in an
extensible structured token
in the event message
ZSPI-TKN-SSID ZSPI-TYP-SSID Subsystem ID of the system
component or subsystem
that generated the event
message
ZSPI-TKN-USEDLEN ZSPI-TYP-UINT Number of bytes used in the
event-message buffer
ZEMS-TKN-CPU ZSPI-TYP-UINT Processor number of the
system component or
subsystem that generated
the event message
ZEMS-TKN-EMPHASIS ZSPI-TYP-BOOLEAN Emphasis flag (see
Potentially Critical or
Noncritical Event
Designation on page 1-4)
ZEMS-TKN-EVENTNUMBER ZSPI-TYP-INT Event number for the event
message
ZEMS-TKN-GENTIME ZSPI-TYP-TIMESTAMP Timestamp for when the
event message was
generated