SNAX/HLS Management Programming Manual

Event Message Descriptions
Event Management
8–4 104708 Tandem Computers Incorporated
The box also contains the text version of the event message, which can be obtained by
using the EMSTEXT procedure. When you use the EMSTEXT procedure to get the text
version of an event message, you request either the display format or the console–
compatible format, as described in the Event Management Service (EMS) Manual. In the
case of most SNAX/HLS event messages, there is no difference between the two
versions. 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.
1: ZHLS–EVT–BAD–RDT–DEV
This event occurs whenever an attempt is made to load a resource defintion table
(RDT) file from a device other than disk.
Unconditional Tokens
ZSPI–TKN–SSID token–type ZSPI–TYP SSID.
ZEMS–TKN–EVENTNUMBER token–type ZSPI–TYP–ENUM.
ZEMS–TKN–SUBJECT–MARK token–type ZSPI–TYP–MARK.
ZCOM–TKN–SUBJ–PROC token–type ZSPI–TYP–STRING.
ZSPI–TKN–MANAGER token–type ZSPI–TYP–FNAME32.
ZEMS–TKN–EMPHASIS token–type ZSPI–TYP–BOOLEAN.
ZEMS–TKN–CONSOLE–PRINT token–type ZSPI–TYP–BOOLEAN.
ZEMS–TKN–CPU token–type ZSPI–TYP–UINT.
ZEMS–TKN–CRTPID token–type ZSPI–TYP–CRTPID.
ZEMS–TKN–GENTIME token–type ZSPI–TYP–TIMESTAMP.
ZEMS–TKN–LOGTIME token–type ZSPI–TYP–TIMESTAMP.
ZEMS–TKN–PIN token–type ZSPI–TYP–UINT.
ZEMS–TKN–SYSTEM token–type ZSPI–TYP–UINT.
ZEMS–TKN–USERID token–type ZSPI–TYP–BYTE–PAIR.
ZCMK–TKN–XFNAME token–type ZSPI–TYP–STRING.
Event–Message Text
<1>: RDT must be a disk file, file = <2>