HP-UX SNAplus2 R7 APPC Programmer's Guide

APPC Conversation Verbs
MC_REQUEST_TO_SEND and REQUEST_TO_SEND
primary_rc
New state
AP_CONV_FAILURE_RETRY
AP_CONV_FAILURE_NO_RETRY
AP_CONVERSATION_ENDED
Reset
AP_DEALLOC_ABEND
AP_DEALLOC_ABEND_PROG
AP_DEALLOC_ABEND_SVC
AP_DEALLOC_ABEND_TIMER
Reset
AP_DEALLOC_NORMAL
Reset
4.14 MC_REQUEST_TO_SEND and REQUEST_TO_SEND
The MC_REQUEST_TO_SEND or REQUEST_TO_SEND verb notifies the partner TP that the local TP wants to
send data.
Note
This verb can be used only in a half-duplex conversation; it is not valid in a full-duplex
conversation.
4.14.1 Action of the Partner TP
In response to this request, the partner TP can change the conversation to one of the following states:
• Receive state by issuing the [MC_]PREPARE_TO_RECEIVE or [MC_]RECEIVE_AND_WAIT verb
• Pending_Post state by issuing the [MC_]RECEIVE_AND_POST verb
The partner TP can also ignore the request to send.
4.14.2 When the Local TP Can Send Data
The conversation state changes to Send for the local TP when it receives one of the following values through the
what_rcvd parameter of a subsequent receive verb:
•
AP_CONFIRM_SEND, AP_DATA_CONFIRM_SEND
,orAP_DATA_COMPLETE_CONFIRM_SEND
(and replies with
[MC_]CONFIRMED)
•
AP_SEND
The conversation state changes to Send_Pending for the local TP when the local TP receives one of the following
values through the what_rcvd parameter of a subsequent receive verb:
•
AP_DATA_SEND
• AP_DATA_COMPLETE_SEND
The RECEIVE verbs are [MC_]RECEIVE_AND_WAIT, [MC_]RECEIVE_IMMEDIATE, and
[MC_]RECEIVE_AND_POST.
4.14.3 VCB Structure: MC_REQUEST_TO_SEND
UNIX
201