EMS Manual

EMS Definitions
EMS Manual—426909-005
14-9
Definitions of EMS Data-Portion Tokens
Definitions of EMS Data-Portion Tokens
These data-portion tokens occur frequently in event messages:
ZEMS-TKN-SUBJECT-MARK
(type mark; shared) marks the token that follows it in the
event-message buffer as a subject of the event message.
An event message can have several subjects but must
have at least one. The token code of ZEMS-TKN-
SUBJECT-MARK is shared by all subsystems.
For a description of how to find event message subjects,
see the description of the ZEMS-TKN-SUBJECT token in
Definitions of EMS Special Token Codes
on page 14-8.
ZEMS-TKN-LDEV
(type uint; nonshared) is the logical device number of
the subsystem process that reported the event.
ZEMS-TKN-LDEVNAME
(type fname32; shared) is the logical device name of the
subsystem process that reported the event. The file name
is in the internal format that includes the name of the
system (node).
ZEMS-TKN-LDEVNUMBER
(type int2; shared) is the logical device number of the
subsystem process that reported the event.
ZEMS-TKN-TEXT
(type string; nonshared) is the displayable text
describing the event.
ZEMS-TKN-ACTION-ID
(type int; nonshared) is a number that identifies a
particular action-event message, distinguishing it from all
other outstanding action-event messages that have the
same subject, subsystem ID, and system number. All four
values—values of the subject token and of the ZEMS-
TKN-ACTION-ID, ZEMS-TKN-SYSTEM, and ZSPI-TKN-
SSID tokens—are necessary to specify an action event
uniquely.
ZEMS-TKN-ACTION-
NEEDED
(type Boolean; nonshared) is a flag. The value TRUE
means that this message is a request for action; the value
FALSE means that this message is a notification that the
action taken is now complete. Whether ACTION-
NEEDED is TRUE or FALSE, the ZEMS-TKN-ACTION-ID
token identifies the particular request, numbering the
request uniquely for a specified subject, subsystem ID,
and system number.
Note. Be careful when you retrieve ZEMS-TKN-ACTION-ID, ZEMS-TKN-ACTION-NEEDED,
and other EMS tokens that are not shared with other subsystems. For example, to call
EMSGETTKN with ZEMS-TKN-ACTION-ID when the default subsystem ID is not EMS, you
must specify ZEMS-VAL-SSID, the subsystem ID for EMS. Similarly, to refer to ZEMS-TKN-
ACTION-ID or ZEMS-TKN-ACTION-NEEDED in a filter specification from a place where the
default subsystem ID is not EMS, you must qualify the token name by the subsystem ID for
EMS.