SNAX/HLS Application Programming Manual
RECEIVE-CONTROL Verb
SNAX/HLS Verbs
5–62 104707 Tandem Computers Incorporated
MESSAGE–COMPLETE–IND
A value of Y indicates that the current message in the user buffer is a complete
user message (although the message could be truncated if
RC–DATA–TRUNCATED is returned). A value of N can be returned only when using
the LMO feature and indicates that subsequent RECEIVE–DATA verbs retrieves
more elements of the session partner’s message. This field is meaningful only
when your partner’s data is being returned.
DEFINITE–RESPONSE–IND
is a single–character numeric field that indicates the kind of response the partner is
expecting for this request. For those who know SNA, it reflects the setting of the
DR1I and DR2I indicators at the end of the incoming request (that is, end of chain).
If the PROFILE attribute, ENCODE–ERI, is set to TRUE, the setting of the ERI
indicator is also indicated.
A returned value of 0 indicates that no response is needed for the data when
delivered to your program on a subsequent RECEIVE–DATA request.
SNAX/HLS automatically takes care of all responses for messages other than
normal partner data. Thus, a value of 0 indicates that responses, if needed, are
handled.
A returned value of other than 0 can occur only when the
DATA–TYPE–RECEIVED field indicates DT–PARTNER–DATA or FM–header data.
The actual value returned is derived from the DR and ER bits in one of two ways
depending upon whether the ENCODE–ERI attribute has been enabled or
disabled. The particular value has significance only as defined by the application.
It indicates what type of response was requested with the message. If your
PROFILE indicates that SNAX/HLS is handling responses (USER–RESPONSES is
NO), this field is for information only. On the other hand, if USER–RESPONSES is
YES, a value other than 0 in DEFINITE–RESPONSE–IND indicates that
SNAX/HLS expects your application to issue an HLS–RESPOND verb when the
data is delivered to your program on a subsequent RECEIVE–DATA request. If
the original request was an exception–response request, and your application is
controlling responses, you have to issue the HLS–RESPOND verb even though no
response flows to the partner. Table 5-2 reflects the value delivered to this field.