SNAX/HLS Management Programming Manual

Event Message Descriptions
Event Management
104708 Tandem Computers Incorporated 8–17
To help isolate the problem, run a SNAX/HLS trace for that session in which the MU
was received.
To aid in discovering the cause of the violation, the SNA sense codes may be located
with the help of the definition of the ZHLS–TKN–MU token in Section 6, “Common
Definitions.”
ZCMK-TKN-SNAERR
If present, it conveys the SNA sense data (2 bytes) with which the request RU was
rejected. The value of this token corresponds to the value <4> in the text message.
Value <2> in the text message is a prose of the sense data.