HP-UX SNAplus2 R7 APPC Programmer's Guide

APPC Conversation Verbs
MC_RECEIVE_AND_POST and RECEIVE_AND_POST
4.10.6 Returned Parameters
After the verb executes, APPC returns parameters to indicate whether the execution was successful and, if not, to
indicate the reason the execution was not successful.
When this verb is issued, it returns immediately with a primary_rc which indicates whether or not the verb was
issued successfully. The only returned parameters which are valid at this stage are primary_rc, secondary_rc (if the
primary_rc is not
AP_OK), and rts_rcvd. The possible primary_rc and secondary_rc values are as described later in
this section.
If this primary_rc is
AP_OK, the verb has successfully begun to receive data asynchronously. When the verb has
completed (either because it has successfully received data or because it was terminated by a conversation error),
APPC calls the supplied callback routine. At this point, the returned parameters are as shown below. The primary_rc
and secondary_rc parameters will now have new values indicating whether or not data was received successfully,
and should be examined again.
Successful Execution
If the verb executes successfully, APPC returns the following parameters:
primary_rc
AP_OK
what_rcvd
Status information received with the incoming data.
The next action taken by the TP will usually depend on the value of this parameter. For more information,
see Section 4.9.2, The what_rcvd Parameter.
Possible values are:
AP_CONFIRM_DEALLOCATE
The partner TP has issued the [MC_]DEALLOCATE verb with dealloc_type set to AP_SYNC_LEVEL,
and the conversation’s synchronization level, established by the [MC_]ALLOCATE verb, is
AP_CONFIRM_SYNC_LEVEL.
AP_CONFIRM_SEND
The partner TP has issued the [MC_]PREPARE_TO_RECEIVE verb with ptr_type set
to AP_SYNC_LEVEL, and the conversation’s synchronization level, established by the
[MC_]ALLOCATE verb, is AP_CONFIRM_SYNC_LEVEL.
AP_CONFIRM_WHAT_RECEIVED
The partner TP has issued the [MC_]CONFIRM verb.
AP_DATA
This value can be returned by the basic-conversation RECEIVE_AND_POST if the fill parameter is set
to AP_BUFFER; it is not applicable to MC_RECEIVE_AND_POST.
The local TP received data until max_len or end of data was reached.
AP_DATA_COMPLETE
For MC_RECEIVE_AND_POST, this value indicates that the local TP has received a complete data
record or the last part of a data record. For RECEIVE_AND_POST with the fill parameter set to
AP_LL, this value indicates that the local TP has received a complete logical record or the end of a
logical record.
AP_DATA_INCOMPLETE
164