HP-UX SNAplus2 R7 APPC Programmer's Guide

Appendix BCommon Return Codes
AppendixB Common Return Codes
This appendix describes the primary return codes (and, if applicable, secondary return codes) that are common to
several APPC verbs.
Verb-specific return codes are described in the documentation for the individual verbs.
Common return codes are described in the following sections.
B.1 AP_ALLOCATION_ERROR
The primary and secondary return codes are:
primary_rc
AP_ALLOCATION_ERROR
APPC has failed to allocate a conversation. The conversation state is set to RESET. This code may be
returned through a verb issued after [MC_]ALLOCATE.
secondary_rc
Possible values are:
AP_ALLOCATION_FAILURE_NO_RETRY
The conversation cannot be allocated because of a permanent condition, such as a configuration error
or session protocol error. To determine the error, the System Administrator should examine the error
log file. Do not attempt to retry the allocation until the error has been corrected.
AP_ALLOCATION_FAILURE_RETRY
The conversation could not be allocated because of a temporary condition, such as a link failure. The
reason for the failure is logged in the system error log. Retry the allocation, preferably after a timeout
to allow the condition to clear.
AP_CONVERSATION_TYPE_MISMATCH
The partner LU or TP does not support the conversation type (basic or mapped) specified in the allocation
request.
AP_PIP_NOT_ALLOWED
The allocation request specified PIP data, but the partner TP did not accept it. This may be because
the partner TP does not require this data, because it is using an APPC implementation which does not
support receiving PIP data, or because the partner is a CPI-C application (CPI-C does not support PIP
data).
AP_PIP_NOT_SPECIFIED_CORRECTLY
The partner TP requires PIP data; but the allocation request specified either no PIP data or an incorrect
number of parameters.
AP_SECURITY_NOT_VALID
The user ID or password specified in the allocation request was not accepted by the partner LU.
AP_SYNC_LEVEL_NOT_SUPPORTED
The partner TP does not support the
sync_level (AP_NONE, AP_CONFIRM_SYNC_LEVEL,or
AP_SYNCPT) specified in the allocation request, or the sync_level was not recognized.
AP_TP_NAME_NOT_RECOGNIZED
The partner LU does not recognize the TP name specified in the allocation request.
279