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

Common Return Codes
Return Codes from Any Partner Program
Appendix A336
CM_PRODUCT_SPECIFIC_ERROR When CPI-C generates a
CM_PRODUCT_SPECIFIC_ERROR returncode, it makes an
entry in the log file indicating the cause of the error
and any action required. Refer to the SNAplus2
Administration Guide for more information about
interpreting these messages.
CM_PROGRAM_ERROR_NO_TRUNC The partner program has issued the
Send_Error call while in Send state or in Send-Pending
state with the error direction set to CM_SEND_ERROR.
Data was not truncated.
CM_PROGRAM_ERROR_PURGING One of the following conditions has
occurred:
• The partner program issued the Send_Error call
while in Receive or Confirm state. Data sent but
not yet received is purged.
• The partner program has issued the Send_Error
call while in Send-Pending state with the error
direction set to CM_RECEIVE_ERROR. Data was not
purged.
CM_PROGRAM_ERROR_TRUNC The partner program in a basic conversation
has issued a Send_Error call while in Send state,
before finishing sending a complete logical record. The
local program may have received the first part of the
logical record through a Receive call.
CM_PROGRAM_PARAMETER_CHECK The program supplied a parameter that
is not valid to the call. For details, see individual calls
in Chapter 3, “CPI-C Calls.”.
CM_PROGRAM_STATE_CHECK The call issued is not allowed in the current
conversation state, or is not appropriate because of the
current setting of a conversation characteristic. For
details, see individual calls in Chapter 3, “CPI-C
Calls.”.
CM_RESOURCE_FAILURE_NO_RETRY One of the following conditions has
occurred:
• The conversation was terminated prematurely
because of a permanent condition. Do not attempt
to retry until the error has been corrected.