SNAX/HLS Management Programming Manual

Subsystem Processes That Report Events
Event Management
8–2 104708 Tandem Computers Incorporated
Subsystem Processes
That Report Events
SNAX/HLS generates event messages for events that involve objects under its control.
Table 8–1 lists the SNAX/HLS event messages.
Table 8–1. SNAX/HLS Event Messages
Event Number Symbolic Name (ZHLS–EVT–) Description
1 BAD–RDT–DEV RDT must be a disk file.
2 BUF–OVERLOAD SNAX/HLS buffer overload.
3 CUST–ERR Customization routine error.
4 INV–MU–RECVED Invalid MU received.
5 INV–MU–SENT Tried to send invalid MU.
6 INV–RSP–RECVED Invalid response received.
7 NEG–RSP–RECVED Negative response received.
8 NEG–RSP–SENT Negative response sent.
9 NO–MEM–FOR–RU No memory available for MU.
10 OLD–RDT–VSN Back–level RDT database.
11 RECV–DATA–OVERRUN Receive data queue is too large.
12 TOO–MANY–POCBS–LUS Allocation of too much memory implied.
13 Reserved.
14 UNEXP–PR–RECVED An unexpected pacing response was received.
Potentially Critical
Events
Events reported by the SNAX/HLS subsystem are divided into two classes: potentially
critical events and noncritical events. Potentially critical events are those for which the
consequences could be serious, such as the loss of a session or the termination of the
SNAX/HLS process. Noncritical events are less serious events that are likely handled
by well–written application programs, such as the sending or receiving of a negative
response.
To determine whether an event message reports a potentially critical event, examine
the value of the event message token ZEMS–TKN–EMPHASIS. If the value is
ZSPI–VAL–TRUE, the event message reports a potentially critical event. If the value is
ZSPI–VAL–FALSE, the event is not critical.