SNAX/HLS Configuration and Control Manual

Objects and Attributes
Using the HLSRDT Utility
4–32 104705 Tandem Computers Incorporated
FORCE-RTS
This PROFILE attribute has the value type yesno . The default is NO.
FORCE-RTS affects the behavior of the REQUEST-SEND-STATE verb, detailed in the
SNAX/HLS Application Programming Manual.
If the attribute has the value YES, an SNA SIG request with signal code %H0001 is sent
whenever the REQUEST-SEND-STATE verb request is issued, regardless of the state
of the normal SNA session flows.
If the attribute has the value NO, then the REQUEST-SEND-STATE verb only causes
the SIG request to be sent if the local session partner does not 'currently' have the right
to send on the normal SNA flow.
HS-POLARITY
This PROFILE attribute has the possible keywords PRIMARY or SECONDARY. The
default value is SECONDARY.
HS-POLARITY specifies whether the sessions created by this PROFILE are primary or
secondary sessions. A value of PRIMARY implies a primary session; a value of
SECONDARY implies a secondary session.
INIT-NAME
This PROFILE attribute has the value type name-8 . The default value is blanks.
INIT-NAME specifies the name of an INIT object that contains the INIT-SELF image.
This name is required only for SECONDARY-ACQUIRE sessions. If present, the name
referenced here must correspond to one of the INIT images in the set of available INIT
images when the SAVE command is issued.
LMO
This PROFILE attribute has the value type yesno . The default value is NO.
LMO specifies the initial setting for the large message option. This option can,
however, be modified by the application program. This option, if selected as YES,
implies that the application manages parts of messages rather than complete messages.
It further implies that no part of a message can be longer than the MAX-RU value for
the associated direction.
In general, this option should be employed only when individual messages (that is,
SNA chains) are longer than 30,720 bytes, or are longer than the available buffer space
in the application program. Furthermore, if LMO is used and FM headers are also
used, the RU sizes must be sufficient to include all FM-header data in one RU.