SNAX/HLS Diagnosis and Support Manual

SNAX/HLS Log Messages
C–18 104706 Tandem Computers Incorporated
session name : (-RSP) received, MU = message-unit, explanation
of SNA sense codes in RSP MU
Cause. Typically, negative responses indicate either a mismatch of session-partner
specifications (an incorrect profile specified to SNAX/HLS), protocol violations by the
partner, or internal SNAX/HLS errors.
There are two circumstances that are likely to cause this situation:
The profile specified in a BIND or INIT-SELF record was incompatible with the
device or gateway application.
The IBM subsystem or device was configured incorrectly.
Effect. If the session is being established, the establishment fails. If data traffic is
active, the negative response is delivered to the application. This message is intended
to provide an audit trail.
Recovery. You should obtain both SNAX/HLS and SNAX/HLS Tandem SNA access
method (for example, SNAX/XF or SNAX/CDF) traces of the problem (see Section 1,
"Problem Determination") and call your Tandem analyst.
For additional information, refer to the Tandem SNA access method documentation.
session name : (-RSP) sent, MU = message-unit, explanation of
SNA sense codes in RSP MU
Cause. Typically, a negative response indicates either a mismatch of session-partner
specifications (an incorrect profile specified to SNAX/HLS), protocol violations by the
session partner, or internal SNAX/HLS errors. Of course, negative responses might be
perfectly normal if so dictated by the application-level protocol.
Effect. If the session is being established, the establishment fails. If data traffic is
active, the negative response is sent to the partner. This message is intended to
provide an audit trail.
Recovery. If the negative response is expected and is a frequent occurrence, you are
advised to disable the publication of this message. (For more information on
controlling the message file, refer to the SNAX/HLS Configuration and Control Manual.)
If the negative response is not expected, you might have to perform error analysis by
obtaining SNAX/HLS and Tandem SNA access method (for example, SNAX/XF or
SNAX/CDF) traces of the problem and call your Tandem analyst. This message can
be avoided if care is taken in the planning of SNAX/HLS sessions.
For additional information, refer to the Tandem SNA access method documentation.