SNAX/HLS Configuration and Control Manual

Objects and Attributes
Using the HLSRDT Utility
104705 Tandem Computers Incorporated 4-43
PRI-SEND-PACING-SIZE specifies the size of the primary send pacing window. It is
used only by the primary partner and only when two-stage pacing is selected for this
flow. Otherwise, SEC-RECV-PACING-SIZE is used.
PRI-SEND-STAGING
This BIND attribute has the value type yesno . It specifies single or two stage pacing
for the primary-to-secondary normal SNA flow. The default value of NO specifies
single stage pacing.
PRI-TWO-PHASE-COMMIT
This BIND attribute has the value type yesno . The default value is NO.
PRI-TWO-PHASE-COMMIT specifies whether two-phase commit is used for the
synchronization point protocol. This value is defined only for TS-Profile 4. This field
is not currently interpreted by SNAX/HLS.
SEC-CHAIN-PROTOCOL
This BIND attribute has the possible keywords NONE, DEFINITE, EXCEPTION, or ANY.
The default is EXCEPTION.
SEC-CHAIN-PROTOCOL specifies what type of response chains will be issued by the
secondary half session. See the discussion above under the topic
PRI-CHAIN-PROTOCOL for details.
SEC-CHAIN-USE
This BIND attribute has the possible keywords SINGLE-RU or MULTIPLE-RU. The
default is MULTIPLE-RU.
SEC-CHAIN-USE specifies whether the secondary half session will send multi-element
chains. If this field is specified as SINGLE-RU and HS-POLARITY is SECONDARY, the
size of messages sent by the secondary is limited to the SEC-MAX-RU value, and
SEND-DATA message sizes must be no larger than this size.
SEC-COMPRESSION-IND
This BIND attribute has the value type yesno . The default value is NO.
SEC-COMPRESSION-IND specifies whether data compression will be used in
messages sent by the secondary half session. See the discussion above for
PRI-COMPRESSION-IND.
SEC-EB-SEND
This BIND attribute has the value type yesno . The default value is NO.
SEC-EB-SEND specifies whether the secondary half session is allowed to send end
brackets. If neither the primary nor the secondary have this field enabled, indicating
that neither can send end-brackets, then no brackets are used in the protocol. For most
situations, only the primary half session can send end brackets.