|
|
|
|
In Confirmation Processing, the invoking TP used the MC_SEND_DATA verb to send data and then the MC_CONFIRM verb to request confirmation from the invoked TP. It is possible to use a parameter on the [MC_]SEND_DATA verb to indicate that APPC should also perform the function of the [MC_]CONFIRM verb (or [MC_]DEALLOCATE, [MC_]FLUSH, or [MC_]PREPARE_TO_RECEIVE) after sending the data, instead of having to issue two separate verbs.
Similarly, the invoked TP in Confirmation Processing issued the MC_RECEIVE_AND_WAIT verb twice, first to receive the data and then to receive the status information that the invoking TP requested confirmation. It is possible to use a parameter on any of the [MC_]RECEIVE verbs to indicate that APPC should return status information about the same receive verb as the data, instead of having to issue two separate receive verbs.
Receiving Status Information with Data shows the use of the send type
parameter on MC_SEND_DATA to perform the function of the MC_CONFIRM verb,
and the return status with data
parameter on MC_RECEIVE_AND_WAIT
to receive status information with data. All primary_rc
values can be assumed to be AP_OK unless shown
otherwise.
In 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.
In Receiving Status Information with Data, the third MC_RECEIVE_AND_WAIT verb issued
by the invoked TP has a rtn_status parameter of
|
|
|
 |
|