HP-UX SNAplus2 R7 APPC Programmer's Guide

APPC Conversation Verbs
MC_PREPARE_TO_RECEIVE and PREPARE_TO_RECEIVE
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_P_TO_R_INVALID_FOR_FDX
The local TP attempted to use the [MC_]PREPARE_TO_RECEIVE verb in a full-duplex conversation.
This verb can be used only in a half-duplex conversation.
AP_P_TO_R_INVALID_TYPE
The ptr_type parameter was not set to a valid value.
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.
State Check
If the conversation is in the wrong state when the TP issues this verb, APPC returns the following parameters:
primary_rc
AP_STATE_CHECK
secondary_rc
Possible values are:
AP_P_TO_R_NOT_LL_BDY
(Returned for basic-conversation PREPARE_TO_RECEIVE only) The local TP did not finish sending
a logical record.
AP_P_TO_R_NOT_SEND_STATE
The conversation was not in Send or Send_Pending state.
Other Conditions
If the verb does not execute because other conditions exist, APPC returns primary return codes (and, if applicable,
secondary return codes). For information about these return codes, see Appendix B, Common Return Codes.
Possible return codes are:
primary_rc
AP_ALLOCATION_ERROR
secondary_rc
AP_ALLOCATION_FAILURE_NO_RETRY
AP_ALLOCATION_FAILURE_RETRY
AP_CONVERSATION_TYPE_MISMATCH
AP_PIP_NOT_ALLOWED
AP_PIP_NOT_SPECIFIED_CORRECTLY
AP_SECURITY_NOT_VALID
AP_SYNC_LEVEL_NOT_SUPPORTED
AP_TP_NAME_NOT_RECOGNIZED
AP_TRANS_PGM_NOT_AVAIL_NO_RETRY
AP_TRANS_PGM_NOT_AVAIL_RETRY
AP_SEC_BAD_PROTOCOL_VIOLATION
155