Safeguard Management Programming Manual (G06.24+, H06.03+)

Event Management
Safeguard Management Programming Manual—422086-012
8-13
Event-Message Descriptions
The notation used for simple tokens is a shorthand version of the essential information
given in the DDL TOKEN-CODE statement.
With the exception of the ZEMS-TKN-SUBJECT-MARK token and the subject token
listed immediately after it, the order of the tokens shown is not necessarily the order in
which they appear in an event message. The ZEMS-TKN-SUBJECT-MARK token
always immediately precedes the subject token of an event message. For more
information on the subject token, see the EMS Manual.
Following the box, the event-message tokens are described in the same order in which
they appear in the box. However, because HP internal tokens are intended for HP use
only, they are not described.
Descriptions in this section of the simple tokens defined by the Safeguard subsystem
(simple tokens whose symbolic names begin with ZSFG-TKN-) do not identify the
token numbers of the tokens. However, the symbolic names of the token numbers can
be derived from the token names simply by replacing -TKN- with -TNM-. For example,
the token number of the ZSFG-TKN-CURRENTAUDITFILE token is ZSFG-TNM-
CURRENTAUDITFILE.
The box also contains the text version of the event message. The text version of an
event message is available through the EMSTEXT procedure. It contains a standard
header that includes the subsystem name, reporting process, and other information.
The text shown in the box follows this standard header. For further information on the
standard header, refer to the EMS Manual.
When you use the EMSTEXT procedure to get the text version of an event message,
you can request either the display-format version or the console-compatible-format
version, as described in the EMS Manual. For Safeguard event messages, the two
versions are the same (except possibly the standard header). The two versions are
also identical to the corresponding console message.