HP-UX SNAplus2 R7 APPC Programmer's Guide

APPC Conversation Verbs
MC_RECEIVE_AND_POST and RECEIVE_AND_POST
4.10.7 State When Issued
The TP can issue [MC_]RECEIVE_AND_POST when the conversation is in Receive, Send, or Send_Pending state.
Issuing the Verb in Send State
Issuing the [MC_]RECEIVE_AND_POST 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 Pending_Post state; the local TP is ready to receive information from the partner
TP asynchronously.
4.10.8 State Change
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 calls the callback routine or clears the semaphore to indicate completion
of the verb, the state changes as described in this section.
The state change on completion of [MC_]RECEIVE_AND_POST depends on the value of the following:
• The primary_rc parameter
• The what_rcvd parameter if primary_rc is
AP_OK
The table that follows summarizes the possible state changes that can occur when primary_rc is
AP_OK:
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
AP_SEND
Send
AP_DATA_SEND
AP_DATA_COMPLETE_SEND
Send_ Pending
The table that follows summarizes the possible state changes that can occur when primary_rc is not
AP_OK:
primary_rc
New state
AP_PARAMETER_CHECK
AP_STATE_CHECK
AP_CONVERSATION_TYPE_MIXED
No change (these return codes can only occur as
the first return code, not as the second return code)
AP_INVALID_VERB
AP_INVALID_VERB_SEGMENT
No change
AP_STACK_TOO_SMALL
AP_TP_BUSY
AP_UNEXPECTED_DOS_ERROR
No change
170