HP-UX SNAplus2 CPI-C Programmer's Guide (June 2003)

Common Return Codes
Return Codes from Any Partner Program
Appendix A 333
Return Codes from Any Partner Program
The following return codes can occur with any partner program. (Other
return codes, which can only occur when the partner program is not a
CPI-C program, are listed separately.)
CM_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.
CM_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.
CM_CALL_NOT_SUPPORTED This return code is used only in Java CPI-C
applications.
The application used a CPI-C function that is defined
in the Java CPI-C class but is not supported.
CM_CONVERSATION_TYPE_MISMATCH The partner LU or program does not
support the conversation type (basic or mapped)
specified in the allocation request.
CM_DEALLOCATED_ABEND The conversation has been deallocated for one
of the following reasons:
• The partner program has issued the Deallocate call
with the deallocate type set to
CM_DEALLOCATE_ABEND. If the conversation is in
Receive state for the partner program when this
call is issued by the local program, data sent by the
local program and not yet received by the partner
program is purged.
• The partner program has terminated normally but
did not deallocate the conversation before
terminating.