SNAX/HLS Diagnosis and Support Manual

SNAX/HLS Log Messages
C–16 104706 Tandem Computers Incorporated
SNAX/HLS Session
Messages
session name : Attempt to send invalid MU, MU = message-unit
[Sense Data = SNA sense data, explanation of SNA sense data]
Cause. This situation can result from an invalid RDT data file. If an internal error in
the HLSRDT program produces an invalid RDT, or if the operator swaps to an invalid
RDT file, this message might result.
Effect. Since HLS does not terminate the session when the above message is sent out
for a Send Check error (HDX-FF direction error), the defective MU is discarded and
the session is terminated immediately.
Recovery. The sense data, if present, reflects the SNA sense data with which the MU is
discarded. Verify that an appropriate RDT is in storage (data using the HLSCOM
PEEK command). If the situation is unclear, you should gather the information
discussed at the beginning of Section 1, “Problem Determination,” and contact your
Tandem analyst.
session name : Invalid MU received, MU = message-unit
[Sense Data = SNA sense data, explanation of SNA sense data]
Cause. A MU that violates the SNA protocols in use on the session has been received.
Effect. The defective MU is discarded, and the session is terminated immediately.
Recovery. The sense data, if present, reflects the SNA sense data with which the MU is
discarded. Analyze the defective MU. If it is an unsupported function on the SNA
session or violates SNA protocol in another way, consult the sending partner.
Otherwise, take a SNAX/HLS trace of the problem and consult your Tandem analyst.
session name : Invalid response received, MU = message-unit
[Sense Data = SNA sense data, explanation of SNA sense data]
Cause. This event message indicates that SNA protocol has been violated. For
example, a request with DR1 was sent out and a response with DR2 was received.
Effect. The defective MU is discarded, and the session is terminated immediately.
Recovery. The sense data, if present, reflects the SNA sense data with which the MU is
discarded. Check the application. If the problem persists, gather the information
discussed at the beginning of Section 1, “Problem Determination,” and contact your
Tandem analyst.