SNAX/HLS Application Programming Manual

SEND-DATA-Verb
SNAX/HLS Verbs
5–102 104707 Tandem Computers Incorporated
Formatted messages permit the exchange of binary or other unusual data. They
frequently convey control information. Consult the component description of
your partner to determine exactly when and where formatted data is used. When
using LMO and translation, the entire FMH must be contained in the first buffer.
NOTIFY–IND.
A NOTIFY–IND value of Y requests SNAX/HLS to queue a message (in a
SEND–DATA–REPLY format) on the session’s queue to indicate successful
reception of this message by the session partner.
When NOTIFY–IND is set to Y, operating in the immediate request mode causes
the SEND–DATA verb to be delayed until an acknowledgement is received. It
thus permits exact synchronization between the partners.
However, if your session is operating in delayed request mode, a form of
processing dictated by the BIND image, the SEND–DATA verb is not delayed.
Instead, when the notification arrives from your partner, a data element is queued
to your session indicating a SEND–DATA completion with RETURN–CODE of
RC–NOTIFICATION or RC–REQUEST–REJECT. In other words, when a positive
SNA response is received from the session partner, a message with
RETURN–CODE is RC–NOTIFICATION is queued on the user’s receive queue (such
positive responses are normally not placed on the users queue).
If the LMO option is enabled, and the MESSAGE–COMPLETE–IND is N, you must
specify N for the NOTIFY–IND option.
MESSAGE–COMPLETE–IND.
If the LMO option is not currently enabled, this field is ignored. Think of it being
assumed Y.
If the LMO option is currently enabled, a value of Y indicates that the current
message in the user buffer is the end of the user message. For those familiar with
SNA, this causes an end–chain indicator to be set on the message. (The value in
this field must be less than, or equal to, the maximum RU size that can be
transmitted. This value is defined in the SNA BIND.)
If the indicator equals N, then SNAX/HLS transmits the user buffer as either a
first–in–chain or middle–in–chain, as appropriate. The
PREPARE–TO–RECEIVE–IND, END–TRANSACTION–IND, and NOTIFY–IND fields
must all contain N.
RESERVED–FOR–FUTURE–USE
is reserved.
USER–DATA–LENGTH
is the length (in bytes) of the message to transmit to the session partner. The valid
range is 0 to 30,720 bytes.