SNAX/HLS Diagnosis and Support Manual

SNAX/HLS Return Codes
Return and Error Codes
104706 Tandem Computers Incorporated A–11
21 RC-NOTIFICATION
Cause. A previous SEND-DATA request (or a send portion of a
SEND-AND-RECEIVE-DATA request) has been acknowledged by the session partner
and the SEND-DATA request in question indicated notification.
Effect. The program can infer that the session partner has accepted and understood the
indicated request. The particular request is identified by the RECOVERY-TAGS
values returned in the reply.
Recovery. Not applicable.
22 RC-REQUEST-REJECT
Cause. The session partner has rejected a request because the request violated
protocol, was not understandable, or could not be executed.
Effect. The session partner rejected the request.
Recovery. The RECOVERY-TAGS field of the verb reply identify the request that has
been rejected. The SYSTEM-ERROR-CODE and USER-ERROR-CODE fields of the
reply contain SNA sense codes giving the reason for the rejection. These sense codes
should be examined and their values used to determine recovery actions.
23 RC-PROFILE-NOT-FOUND
Cause. The OPEN-SESSION or HLS-ALLOCATE request specified the name of a
PROFILE not present in the RDT used to start SNAX/HLS.
Effect. The verb request is rejected.
Recovery. This may be a naming or a configuration error. Once you have verified that
the correct name is used in the verb request, use the PEEK command of HLSCOM to
verify that the correct RDT object is in use by the SNAX/HLS process.