Expand Management Programming Manual

EVENT MANAGEMENT
Event-Message Descriptions
Within each event-message description, there is a box that lists
all the tokens that can appear in the event message. Header
tokens are listed here, because an application can filter event
messages on header tokens as well as on other tokens. These
tokens are divided into four categories:
1. Unconditional tokens (tokens that are always present in the
event message).
2. Conditional tokens (tokens that might be present in the event
message).
3. Volatile tokens (those that are subject to change from
release to release).
4. Tandem internal tokens (those intended for Tandem use only).
If none of the tokens in an event message fall into a particular
category, that category does not appear in the box.
The order in which tokens are presented in the token sections
of the syntax box is arbitrary, except that the token ZEMS-TKN-
SUBJECT-MARK always immediately precedes the subject token of an
event message. For more information on the subject token, refer
to the Event Management Service (EMS) Manual .
The box also contains a portion of the text version of the event
message. The text version of an event message is available
through the EMSTEXT procedure, and it contains a standard header
that includes the date, time, system name, and other information.
(For further information on the standard header, refer to the
Event Management Service (EMS) Manual .) The text shown in the
box follows this standard header.
When you use the EMSTEXT procedure to get the text version of an
event message, you request either the display-format version or
the console-compatible-format version, as described in the Event
Management Service (EMS) Manual . In the case of EXPAND event
messages, there is no difference between the two versions (except
possibly the standard header), and the two versions are also
identical to the corresponding console message.
The notation used in the box for simple tokens is a shorthand
version of the essential information given in the DDL TOKEN-CODE
statement.
Following the box, the event-message tokens are described in the
same order in which they appeared in the box. However, because
Tandem internal tokens are intended for Tandem use only, they are
not described.
8-5