SNAX/HLS Application Programming Manual

SEND-DATA Verb
SNAX/HLS Verbs
5–98 104707 Tandem Computers Incorporated
SEND-DATA Verb This verb requests SNAX/HLS to transmit the contents of the user–data field. The
operation of this verb depends on the current setting of the LMO PROFILE attribute.
If the current value of LMO is NO, then SNAX/HLS divides the message into an SNA
chain of MAXRU bytes each (except the last element of the chain). See the SNAX/HLS
Configuration and Control Manual for a discussion of the MAXRU field in the PROFILE.
If the current value of LMO is YES, the request is sent as a single SNA chain element.
SNAX/HLS controls setting the begin–chain indicator. The user controls end–of–chain
with the MESSAGE–COMPLETE–IND indicator. Setting MESSAGE–COMPLETE–IND
to Y causes SNAX/HLS to end the chain and request the appropriate response.
If LARGE–MESSAGE–OPTION is used, the user must be aware of certain constraints
enforced by the formal SNA protocol. These are outlined below:
The length of each message element sent cannot exceed the BIND–specified
MAXRU length. A violation produces the error code
RC–REQUEST–EXCEEDS–MAXRU, and no data is sent.
SNAX/HLS controls the setting of the beginning–of–chain indicator for you. It is
set on that message element following an element that indicated
MESSAGE–COMPLETE–IND is Y, or the first element sent.
Setting the END–TRANSACTION–IND to Y is legal only on the first element of a
chain. A violation produces the error code RC–SEND–CHECK with the SNA sense
code of %H4004.
Setting FORMATTED–DATA–IND to Y is legal only on the first element of a chain.
Any violation is ignored.
Setting PREPARE–TO–RECEIVE–IND to Y is valid only when accompanied by
MESSAGE–COMPLETE–IND. Any violation is ignored.
NOTIFY–IND is valid only when accompanied by the
MESSAGE–COMPLETE–IND. Any violation is ignored.
For those readers familiar with SNA, the use of NOTIFY–IND requires that a definite
response be requested from your partner. This, in turn, is allowed only on those
protocols that use either definite–response chains, or definite or exception response
chains. In the latter case, the use of NOTIFY–IND forces the SNAX/HLS server to
request a definite response, whereas normally exception responses are used. Table 5-4
summarizes the protocols used.