SNAX/HLS Management Programming Manual

Event Message Descriptions
Event Management
8–16 104708 Tandem Computers Incorporated
ZEMS–TKN–SUBJECT–MARK
serves to mark the token that follows it in the event message buffer as the subject
of the event message. In this message, the subject token is
ZCOM–TKN–SUBJ–SESS.
ZCOM–TKN–SUBJ–SESS
is the name of the session that is the subject of this event message, as described in
Section 6, “Common Definitions.” The value of this token corresponds to the
value <1> in the text message.
ZSPI–TKN–MANAGER
is the name of the SNAX/HLS process.
ZEMS–TKN–EMPHASIS
contains the value ZSPI–VAL–TRUE, indicating that this is a potentially critical
event.
ZEMS–TKN–CONSOLE–PRINT
contains the value ZSPI–VAL–TRUE. This token is described in the Event
Management Service (EMS) Manual.
(ZEMS–TKN–) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID
are standard EMS tokens described in the Event Management Service (EMS) Manual.
ZHLS–TKN–MU
contains the value of the message unit that caused the event. This token is
described in Section 6, “Common Definitions.” The value of this token
corresponds to the value <3> in the text message.
ZHLS–TKN–MUT
conveys the printable representation of the information carried in the token
ZHLS–TKN–MU.
Cause. An invalid response has been received. This event message indicates that SNA
protocol has been violated. For example, a request with DR1 was sent but a response
with DR2 was received.
Effect. The defective MU is discarded, and the session is terminated immediately.
Recovery. Inspect the MU and determine if one of the following is true:
There is an error in the request unit format.
The MU represents an RU type not support by SNAX/HLS.
The MU violates state protocols.
The MU is a type of session error.