SNAX/HLS Configuration and Control Manual

Step 3. Planning Session BINDs
Planning the SNAX/HLS Environment
104705 Tandem Computers Incorporated 2–9
Definite-response chains—require each message to request explicit
acknowledgement. This means message delivery and acceptance can be known to
the message sender. Normally, a SNAX/HLS application uses immediate-request
mode and definite-response chains if verb completion is to be construed as
acceptance by the session partner.
Definite-response or exception-response chains —allow the application to select either
definite or exception responses on a message-by-message basis using the
notification attribute (that is, the NOTIFY-IND field).
In the BIND message, this attribute is indicated in byte 4, bits 2 and 3 for the primary
half-session, and in byte 5, bits 2 and 3 for the secondary half-session. In HLSRDT, this
attribute is specified by the BIND attributes PRI-CHAIN-PROTOCOL and
SEC-CHAIN-PROTOCOL, respectively, where: NONE corresponds to 0 in the BIND
message, EXCEPTION corresponds to 1 in the BIND message, DEFINITE corresponds
to 2 in the BIND message, and ANY corresponds to 3 in the BIND message.
Two-Phase Commit
This attribute is not interpreted by SNAX/HLS.
In the BIND message, this attribute is indicated in byte 4, bit 4 for the primary half-
session, and in byte 5, bit 4 for the secondary half-session. In HLSRDT, this attribute is
specified by the BIND attributes PRI-TWO-PHASE-COMMIT and
SEC-TWO-PHASE-COMMIT, respectively, where: NO corresponds to 0 in the BIND
message and YES corresponds to 1 in the BIND message.
Compression Indicator
This attribute specifies whether data compression will be used. This attribute is
typically used on LU-type 1 (RJE) sessions. This attribute is not interpreted by
SNAX/HLS.
In the BIND message, this attribute is indicated in byte 4, bit 6 for the primary half-
session, and in byte 5, bit 6 for the secondary half-session. In HLSRDT, this attribute is
specified by the BIND attributes PRI-COMPRESSION-IND and
SEC-COMPRESSION-IND, respectively, where: NO corresponds to 0 in the BIND
message and YES corresponds to 1 in the BIND message.
Send End Bracket Indicator
This attribute specifies whether the half-session can end a bracket (transaction or unit
of work). If neither the primary nor the secondary half-session select this attribute,
brackets are not used by the session.
In the BIND message, this attribute is indicated in byte 4, bit 7 for the primary
half-session, and in byte 5, bit 7 for the secondary half-session. In HLSRDT, this
attribute is specified by the BIND attributes PRI-EB-SEND and SEC-EB-SEND,
respectively, where: NO corresponds to 0 in the BIND message and YES corresponds
to 1 in the BIND message.