SNAX/HLS Application Programming Manual

HLS-OPEN Verb
SNAX/HLS Verbs
104707 Tandem Computers Incorporated 5–39
SYSTEM–ERROR–CODE
is a modifier to RETURN–CODE:
If RETURN–CODE specifies RC–SYNTAX–ERROR, this identifies the field in error
by counting each field following the REQUEST–FORMAT field. For example, a
value of 1 indicates that the first field following the REQUEST–FORMAT field is
in error.
If RETURN–CODE contains either RC–SEND–CHECK, RC–SESSION–FAILURE,
or RC–REQUEST–REJECT, then this field contains the first 2 bytes of the SNA
sense data. The next two follow in the USER–ERROR–CODE.
If RETURN–CODE contains RC–FILE–ERROR, this field contains the value of
the file-system error code.
If RETURN–CODE contains any value other than those listed above, this field is
undefined and should not be analyzed.
USER–ERROR–CODE
contains the second two bytes of SNA sense data if the SYSTEM-ERROR-CODE
contains the first two bytes of SNA sense data.
RETRY–ACTION–CODE
is a summary indicator that indicates whether an unsuccessful request should be
retried. The value returned here can be installation–defined.
RECOVERY–TAGS
contains the sequence numbers actually in effect by the session partner.
SEND–SEQUENCE–NUMBER contains the session partner’s value for the current
user’s send tag of this session (that is, the message tag of the next message to be
received by the session partner). The intent of this field is to give the user
feedback on situations when sequence verification is negative. If RETURN–CODE
equals RC–VERIFY–FAILURE, then this value indicates what the session partner
expects the value to be.
RCV–SEQUENCE–NUMBER contains the session partner’s value for the current
user’s receive tag of this session (that is, the message tag of the next message to be
sent by the session partner). The intent of this field is to give the user feedback on
situations when sequence verification is negative. If RETURN–CODE equals
RC–VERIFY–FAILURE, then this value indicates what the session partner expects
the value to be.
APPLICATION–NAME
contains the PLU name that was specified on the BIND that started the session.
This name may be different from the name you specified in the
APPLICATION–NAME field of the request for a secondary LU.