HP-UX SNAplus2 R7 APPC Programmer's Guide

APPC Conversation Verbs
MC_REQUEST_TO_SEND and REQUEST_TO_SEND
primary_rc
AP_COMM_SUBSYSTEM_ABENDED
AP_CONVERSATION_TYPE_MIXED
AP_INVALID_VERB
AP_TP_BUSY
AP_UNEXPECTED_SYSTEM_ERROR
WINDOWS
AP_COMM_SUBSYSTEM_NOT_LOADED
AP_STACK_TOO_SMALL
AP_INVALID_VERB_SEGMENT
APPC does not return secondary return codes with these primary return codes.
4.14.9 State When Issued
The conversation can be in any of the following states when the TP issues this verb:
• Receive
• Confirm
• Pending_Post
4.14.10 State Change
The conversation state does not change for this verb.
4.14.11 Receiving Request-to-Send Notification
The request-to-send notification is received by the partner program through the rts_rcvd parameter of the following
verbs:
• [MC]CONFIRM
• [MC_]RECEIVE_AND_POST
• [MC_]RECEIVE_AND_WAIT
• [MC_]RECEIVE_IMMEDIATE
• [MC_]SEND_DATA
• [MC_]SEND_ERROR
It is also indicated by a primary_rc of
AP_OK on the [MC_]TEST_RTS verb, or by a callback on the
[MC_]TEST_RTS_AND_POST verb.
Request-to-send notification is sent to the partner TP immediately; APPC does not wait until the send buffer fills up
or is flushed. Consequently, the request-to-send notification may arrive out of sequence. For example, if the local TP
is in Send state and issues the [MC_]PREPARE_TO_RECEIVE verb followed by the [MC_]REQUEST_TO_SEND
verb, the partner TP, in Receive state, may receive the request-to-send notification before it receives the send
notification. For this reason, request-to-send notification can be reported to a TP on a receive verb.
205