HP-UX SNAplus2 R7 APPC Programmer's Guide

APPC Conversation Verbs
MC_SEND_EXPEDITED_DATA and SEND_EXPEDITED_DATA
Address of the buffer containing the data to be put in the local LU’s send buffer.
4.18.4 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.
Successful Execution
If the verb executes successfully, APPC returns the following parameters:
primary_rc
AP_OK
rts_rcvd
Request-to-send-received indicator. This parameter applies only in a half-duplex conversation; it is not used
in a full-duplex conversation.
Possible values are:
AP_YES
The partner TP has issued an [MC_]REQUEST_TO_SEND verb, which requests that the local TP
change the conversation to Receive state. To change to Receive state, the local TP can use the
[MC_]PREPARE_TO_RECEIVE, [MC_]RECEIVE_AND_WAIT, or [MC_]RECEIVE_AND_POST
verb.
AP_NO
The partner TP has not issued the [MC_]REQUEST_TO_SEND verb.
expd_rcvd
Expedited data indicator.
Possible values are:
AP_YES
The partner TP has sent expedited data that the local TP has not yet received. To receive this data, the
local TP can use the [MC_]RECEIVE_EXPEDITED_DATA verb.
This indicator can be set on a number of APPC verbs. It continues to be set on subsequent verbs until
the local TP issues the [MC_]RECEIVE_EXPEDITED_DATA verb to receive the data.
AP_NO
There is no expedited data waiting to be received.
Unsuccessful Execution
If the verb does not execute successfully, APPC returns a primary return code parameter to indicate the type of
error and a secondary return code parameter to provide specific details about the reason for unsuccessful execution.
Expedited Data Not Supported
If the verb does not execute because the remote LU does not support expedited data, APPC returns the following
parameter:
primary_rc
AP_EXPD_NOT_SUPPORTED_BY_LU
Conversation Deallocated
If the partner TP has deallocated the conversation, APPC returns the following value:
235