Common Return Codes

This section describes the return codes for CPI-C calls. The return codes are listed in integer order.

Call-specific return codes are described for the individual calls in CPI-C Calls.

0

cm_ok: The call executed successfully.

1

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 retry the allocation until the error has been corrected.

2

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.

3

cm_conversation_type_mismatch: The partner LU or program does not support the conversation type (basic or mapped) specified in the allocation request.

5

cm_pip_not_specified_correctly: The allocation request was rejected by a non-CPI-C LU 6.2 TP. The partner program requires one or more PIP data variables, which are not supported by CPI-C.

6

cm_security_not_valid: The user identifier or password specified in the allocation request was not accepted by the partner LU.

8

cm_sync_lvl_not_supported_pgm: The partner program does not support the synchronization level specified in the allocation request.

9

cm_tpn_not_recognized: The partner LU does not recognize the program name specified in the allocation request.

10

cm_tp_not_available_no_retry: The partner LU cannot start the program specified in the allocation request because of a permanent condition. The reason for the error may be logged on the remote node. Do not retry the allocation until the error has been corrected.

11

cm_tp_not_available_retry: The partner LU cannot start the program specified in the allocation request because of a temporary condition. The reason for the error may be logged on the remote node. Retry the allocation.

17

cm_deallocated_abend

The conversation has been deallocated for one of the following reasons:

The remote program issued Deallocate with the type parameter set to CM_DEALLOCATE_ABEND. If the conversation for the remote program was in receive state when the call was issued, information sent by the local program and not yet received by the remote program is purged.
The partner program terminated normally but did not deallocate the conversation before terminating.

18

cm_deallocated_normal

This return code does not indicate an error.

The partner program issued the Deallocate call with deallocate_type set to one of the following:

CM_DEALLOCATE_FLUSH.
CM_DEALLOCATE_SYNC_LEVEL with the synchronization level of the conversation specified as CM_NONE.

19

cm_parameter_error: The local program specified an invalid argument in one of its parameters.

20

cm_product_specific_error: A product-specific error occurred and has been logged in the product's error log.

21

cm_program_error_no_trunc: While in SEND state or in SEND-PENDING state with the error direction set to CM_SEND_ERROR, the partner program issued Send_Error. Data was not truncated.

22

cm_program_error_purging

One of the following occurred:

While in RECEIVE or CONFIRM state, the partner program issued Send_Error. Data sent but not yet received is purged.
While in SEND-PENDING state with the error direction set to CM_RECEIVE_ERROR, the partner program issued Send_Error. Data was not purged.

23

cm_program_error_trunc (for a basic conversation): In SEND state, before finishing sending a complete logical record, the partner program issued Send_Error. The local program may have received the first part of the logical record through a Receive call.

24

cm_program_parameter_check: A parameter or the address of a variable is invalid. For details, see individual calls in CPI-C Calls.

25

cm_program_state_check: The call was not issued in an allowed conversation state. For details, see individual calls in CPI-C Calls.

26

cm_resource_failure_no_retry

One of the following occurred:

The conversation was terminated prematurely because of a permanent condition. Do not retry until the error has been corrected.
The partner program did not deallocate the conversation before terminating normally.

27

cm_resource_failure_retry: The conversation was terminated prematurely because of a temporary condition, such as modem failure. Retry the conversation.

28

cm_unsuccessful: The verb issued by the local program was not executed successfully.

30

cm_deallocated_abend_svc

The conversation has been deallocated for one of the following reasons:

The partner program issued Deallocate with the type parameter set to ABEND_SVC.
The partner program did not deallocate the conversation before terminating.

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.

31

cm_deallocated_abend_timer: The conversation has been deallocated because the partner program issued Deallocate with the type parameter set to ABEND_TIMER. 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.

32

cm_svc_error_no_trunc (for a basic conversation): While in SEND state, the partner program or partner LU issued Send_Error with the type parameter set to SVC. Data was not truncated.

33

cm_svc_error_purging: While in SEND state, the partner program or partner LU issued Send_Error with the type parameter set to SVC. Data sent to the partner program may have been purged.

34

cm_svc_error_trunc (for a basic conversation): While in RECEIVE or CONFIRM state, the partner program or partner LU issued Send_Error with the type parameter set to SVC before it finished sending a complete logical record. The local program may have received the first part of the logical record.

35

cm_operation_not_accepted: A previous operation on this conversation is incomplete.

36

cm_system_event: This error code is not used by Microsoft® SNA Server.

37

cm_operation_incomplete: The operation has not completed and is still in progress. The program can issue Wait_For_Conversation to await the completion of the operation, or Cancel_Conversation to cancel the operation and conversation. If Specify_Windows_Handle has been called, the application should wait for notification by a windows message and not call Wait_For_Conversation.