EMS Manual

EMS Definitions
EMS Manual—426909-005
14-7
Definitions of EMS Tokens in the Event Message
Header
ZEMS-TKN-CONTENT-USER
(type enum; shared) identifies the type of a subsystem-
defined event. Standard enumerated values are:
ZEMS-VAL-NULL (default)
ZEMS-VAL-DATA-TRACE
ZEMS-VAL-DATA-DEBUG
ZEMS-VAL-DATA-DIAGNOSTIC
Subsystems can add their own values but they must be
greater than or equal to ZEMS-VAL-MIN-USER-VALUE.
If an event is defined by a subsystem and contains trace,
program debug, or diagnostic information for problems in
a production environment, this token must be present to
indicate the type of information conveyed by the event.
Otherwise this token should not be present, or its value
must be ZEMS-VAL-NULL.
This token can co-exist with the “Standard Content Type”
ZEMS-TKN-CONTENT-STANDARD token described
earlier. When both type tokens are present, it indicates
the event contains tokens for the standard event and for
the subsystem-defined event. This usually means the
event was a private event defined by the subsystem
initially and then enhanced subsequently—by adding
other tokens—to become a standard event.
Note. Be careful when you use the ZEMS-TKN-NODENUM, ZEMS-TKN-CPU, ZEMS-TKN-
PIN, ZEMS-TKN-PROC-DESC, and ZEMS-TKN-USERID tokens. These tokens do not reflect
the reporting process if event text is written to $0 through a call to the WRITE procedure.
Instead, these tokens reflect $0 because $0 creates the event message from the event text.
To get information about the reporting process, pass the ZEMS-TKN-XSENDERID and
XSENDERID-PD tokens to the EMSGET (or EMSGETTKN) procedure. For more information,
see the descriptions of XSENDERID and XSENDERID-PD in Definitions of EMS Special
Token Codes on page 14-8.
The header tokens ZEMS-TKN-PROC-DESC, ZEMS-TKN-CPU, ZEMS-TKN-PIN, and ZEMS-
TKN-NODENUM are related. Updating any of these four tokens does not automatically update
the other three tokens. You must ensure that changes to these four tokens are consistent.