HP-UX SNAplus2 R7 APPC Programmer's Guide

APPC Conversation Verbs
MC_RECEIVE_AND_WAIT and RECEIVE_AND_WAIT
The following primary return codes are returned by the RECEIVE_AND_WAIT verb:
primary_rc
AP_DEALLOC_ABEND_PROG
AP_DEALLOC_ABEND_SVC
AP_DEALLOC_ABEND_TIMER
AP_SVC_ERROR_NO_TRUNC
AP_SVC_ERROR_PURGING
AP_SVC_ERROR_TRUNC
APPC does not return secondary return codes with these primary return codes.
4.11.7 State When Issued
The TP can issue the [MC_]RECEIVE_AND_WAIT verb when the conversation is in Receive, Send, or
Send_Pending state.
Issuing the Verb in Send State (half-duplex conversation only)
Issuing the [MC_]RECEIVE_AND_WAIT verb while the conversation is in Send state has the following effects:
• The local LU sends the information in its send buffer and a SEND indicator to the partner TP.
• The conversation changes to Receive state; the local TP waits to receive information from the partner TP.
4.11.8 State Change
WINDOWS
When the verb is issued to the asynchronous entry point, the conversation changes state twice. On the initial
return of the verb, if the primary_rc is
AP_OK, the conversation changes to Pending_Post state. After APPC
indicates completion of the verb, the state changes as described below. For more information about the
actions that the application can take in Pending_Post state, see Section 4.10, MC_RECEIVE_AND_POST and
RECEIVE_AND_POST.
The state change after the [MC_]RECEIVE_AND_WAIT verb depends on the value of the following:
• The primary_rc parameter
• The what_rcvd parameter
The possible state changes are summarized in the following tables.
what_rcvd parameter
New state
AP_CONFIRM_WHAT_RECEIVED
AP_DATA_CONFIRM
AP_DATA_COMPLETE_CONFIRM
Confirm
AP_CONFIRM_DEALLOCATE
AP_DATA_CONFIRM_DEALLOCATE
AP_DATA_COMPLETE_CONFIRM_DEALL
Confirm_Deallocate
AP_CONFIRM_SEND
AP_DATA_CONFIRM_SEND
AP_DATA_COMPLETE_CONFIRM_SEND
Confirm_Send
AP_DATA
AP_DATA_COMPLETE
AP_DATA_INCOMPLETE
Receive (half-duplex conversation) or no change (full-duplex
conversation)
183