HP-UX SNAplus2 R7 APPC Programmer's Guide

APPC Conversation Verbs
MC_DEALLOCATE and DEALLOCATE
AP_OK
expd_rcvd
Expedited data indicator. This parameter is used only in full-duplex conversations, where the TP can continue
to receive expedited data after successfully issuing [MC_]DEALLOCATE.
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.
In a half-duplex conversation, this parameter is always set to
AP_NO, because the conversation ends when the
[MC_]DEALLOCATE verb completes successfully and so the local TP cannot receive any further expedited
data.
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_TP_ID
The value of tp_id did not match a TP identifier assigned by APPC.
AP_DEALLOC_BAD_TYPE
The dealloc_type parameter was not set to a valid value.
AP_DEALLOC_LOG_LL_WRONG
(Returned for basic-conversation DEALLOCATE only) The LL field of the GDS error log variable did
not match the actual length of the log data, or the value of the log_dlen parameter was incorrect.
UNIX
AP_INVALID_FORMAT
The format byte was set to a value that was not valid.
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
135