HP-UX SNAplus2 R7 APPC Programmer's Guide

APPC Conversation Verbs
MC_SEND_ERROR and SEND_ERROR
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.
Parameter Check
If the verb does not execute because of a parameter error, APPC returns the following parameters:
primary_rc
AP_PARAMETER_CHECK
secondary_rc
Possible values are:
AP_BAD_CONV_ID
The value of conv_id did not match a conversation identifier assigned by APPC.
AP_BAD_ERROR_DIRECTION
The value of err_dir was not valid.
AP_BAD_TP_ID
The value of tp_id did not match a TP identifier assigned by APPC.
AP_SEND_ERROR_BAD_TYPE
The value of err_type was not valid.
UNIX
AP_INVALID_FORMAT
The reserved field format was set to a nonzero value.
AP_SYNC_NOT_ALLOWED
The application issued this verb within a callback routine, using the synchronous APPC entry point.
Any verb issued from a callback routine must use the asynchronous entry point.
WINDOWS
AP_INVALID_DATA_SEGMENT
The log data was longer than the allocated data segment, or the address of the log data buffer was
incorrect.
The following secondary_rc value can be returned only on the SEND_ERROR verb:
AP_SEND_ERROR_LOG_LL_WRONG
The LL field of the error log GDS variable did not match the actual length of the data.
State Check
No state check errors occur for this verb.
229