EMS Manual
Standard Events
EMS Manual—426909-005
9-38
Extensions to Standard Events
32:ZSPI-TKN-NEXTTOKEN, TOKENHEADING
33:ZSPI-TKN-NEXTTOKEN, TOKENVALUE
Extensions to Standard Events
Subsystem developers can make these extensions:
Enhance the meaning of standard events
Subsystem developers should provide extra tokens to a standard event if these
tokens help describe the conditions reported by the subsystem. Subsystem
developers could, but are not required to, extend the standard template to display
these tokens.
Enhance the meaning of standard management functions
Subsystem developers could define their own EMS events and templates to enrich
a management function defined in this section.
Support management functions not in this section
Subsystem developers could specify their own EMS events and templates to
support management functions, like job accounting, that are not defined in this
section.
The tokens, events, and management functions defined by subsystems should not
impact the existing management applications and should not require other subsystems
or applications to change. The additions should only provide value-added functions to
those defined here.
General Guidelines
The tokens added to a standard event must not change the meaning of the
standard event.
The content of subsystem-defined events should be derived using the procedures
described in Section 10, Generating Standard Events
. They must support a well-
defined management function and have the same assumptions as the standard
events described in this section.
If the tokens, events, and management functions defined by subsystems or
applications are of general interest and could benefit other subsystems or
applications, submit your additions for incorporation in this standard by sending
requests through your HP account analysts.