SNAX/HLS Configuration and Control Manual

Objects and Attributes
Using the HLSRDT Utility
104705 Tandem Computers Incorporated 4-33
MAX-REQUESTS
This PROFILE attribute has the value type integer . The default value is 2.
MAX-REQUESTS specifies the maximum number of verbs that can be queued by the
application at any one time. The recommended value of 2 is based upon a
permanently queued read-type verb and a second send-type verb. Larger values are
unusual. The value must be positive.
The main function of this value is to prevent one application thread from dominating
the memory resources of SNAX/HLS.
OMIT-MODEM-WAIT
This PROFILE attribute has the value type yesno . The default value is NO.
OMIT-MODEM-WAIT specifies whether or not the delay at session initiation for an
operative line should be omitted. This option, if specified as NO, causes
OPEN-SESSION (and HLS-OPEN) verbs to delay indefinitely until the line is
operative. The operative condition of the line is indicated by SNAX/XF or
SNAX/CDF when the CONTROL-11 completes.
When this option is specified as YES, the delay is omitted. The YES option allows the
application program to detect inoperative lines, whereas the NO option does not allow
detection of inoperative lines.
OPEN-MODE
This PROFILE attribute has the possible keywords ACQUIRE or ACCEPT. The
default value is ACQUIRE.
OPEN-MODE specifies whether the sessions are to be initiated by this side
(ACQUIRE) or the other side (ACCEPT). The partner that is the acquirer of the session
is the first to act when establishing a session. Primary acquire half sessions begin by
sending a BIND; secondary acquire half sessions begin by sending an INIT-SELF.
As a direct consequence of this fact, accept sessions in general should be initiated
before the acquire session begins session establishment.
PIPELINE-LU-IND
This PROFILE attribute has the value type yesno . The default value is NO.
PIPELINE-LU-IND specifies whether the half session can be accessed by more than
one application thread. Unfortunately, due to limitations in the SCOBOLX server
interface, SNAX/HLS can distinguish one application thread from another only if they
run in different instances of the TCP program. When two threads reside in the same
instance of the TCP program, and both access the same half session, SNAX/HLS is
unable to distinguish that there are really two application threads. This form of
pipelining cannot be prevented.
When sessions are established by application programs, the correct value of this
indicator must appear in the request that allocates the session. This is provided as a
sanity check.