HP-UX SNAplus2 R7 APPC Programmer's Guide

Concepts
Sending and Receiving Status with Data (half-duplex)
Table 1–3 Receiving Status Information with Data
Invoking TP Flow Invoked TP
TP_STARTED
MC_ALLOCATE
MC_SEND_DATA (type =
AP_SEND_DATA_CONFIRM
)
—>
RECEIVE_ALLOCATE
MC_RECEIVE_AND_WAIT (rtn_status =
NO)(what_rcvd=
AP_DATA_COMPLETE
)
MC_RECEIVE_AND_WAIT (rtn_status =
NO)
(what_rcvd =
AP_CONFIRM_WHAT_RECEIVED)
MC_CONFIRMED
<—
MC_SEND_DATA (type =
AP_NONE)
MC_CONFIRM
—>
MC_RECEIVE_AND_WAIT (rtn_status =
YES)(what_rcvd =
AP_DATA_COMPLETE_CONFIRM
)
MC_CONFIRMED
<—
MC_DEALLOCATE
TP_ENDED
—>
MC_RECEIVE_AND_WAIT (primary_rc =
AP_DEALLOC_NORMAL)
TP_ENDED
1.4.1 Sending Status Information with Data
In Table 1–3, Receiving Status Information with Data, the first MC_SEND_DATA verb issued by the invoking
TP has a send type of
AP_SEND_DATA_CONFIRM. This indicates that APPC should perform the function of the
MC_CONFIRM verb after sending the data. Instead of CONFIRM, the [MC_]SEND_DATA verb can also perform
the function of [MC_]FLUSH, [MC_]DEALLOCATE, or [MC_]PREPARE_TO_RECEIVE, or can specify (as for
the second MC_SEND_DATA verb in the example) that no additional function is to be performed.
1.4.2 Receiving Status Information with Data
In Table 1–3, Receiving Status Information with Data, the third MC_RECEIVE_AND_WAIT verb issued by the
invoked TP has a rtn_status parameter of AP_YES. This indicates that, if data followed by status information is
28