Primary APPC Return Codes

0000

ap_ok

The verb executed successfully.

0001

ap_parameter_check

The verb did not execute because of a parameter error.

0002

ap_state_check

The verb did not execute because it was issued in an invalid state.

0003

ap_allocation_error

APPC failed to allocate a conversation. The conversation state is set to RESET.

This code can be returned through a verb issued after ALLOCATE or MC_ALLOCATE.

0005

ap_dealloc_abend (for a mapped conversation)

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

• The partner TP issued MC_DEALLOCATE with dealloc_type set to AP_ABEND.
• The partner TP encountered an ABEND, causing the partner LU to send an MC_DEALLOCATE request.

0006

ap_dealloc_abend_prog (for a basic conversation)

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

• The partner TP issued DEALLOCATE with dealloc_type set to AP_ABEND_PROG.
• The partner TP encountered an ABEND, causing the partner LU to send a DEALLOCATE request.

0007

ap_dealloc_abend_svc (for a basic conversation)

The conversation has been deallocated because the partner TP issued DEALLOCATE with dealloc_type set to AP_ABEND_SVC.

0008

ap_dealloc_abend_timer (for a basic conversation)

The conversation has been deallocated because the partner TP issued DEALLOCATE with dealloc_type set to AP_ABEND_TIMER.

0009

ap_dealloc_normal

The partner TP has deallocated the conversation without requesting confirmation.

000C

ap_prog_error_no_trunc

The partner TP has issued one of the following verbs while the conversation was in SEND state:

• SEND_ERROR with err_type set to AP_PROG
• MC_SEND_ERROR

Data was not truncated.

000F

ap_conv_failure_retry

The conversation was terminated because of a temporary error. Restart the TP to see if the problem occurs again. If it does, the system administrator should examine the error log to determine the cause of the error.

0010

ap_conv_failure_no_retry

The conversation was terminated because of a permanent condition, such as a session protocol error. The system administrator should examine the system error log to determine the cause of the error. Do not retry the conversation until the error has been corrected.

0011

ap_svc_error_no_trunc

While in SEND state, the partner TP (or partner LU) issued SEND_ERROR with err_type set to AP_SVC. Data was not truncated.

0012

ap_prog_error_trunc/ap_svc_error_trunc

In SEND state, after sending an incomplete logical record, the partner TP issued SEND_ERROR. The local TP may have received the first part of the logical record.

0013

ap_svc_error_purging

The partner TP (or partner LU) issued SEND_ERROR with err_type set to AP_SVC while in RECEIVE, PENDING_POST (Microsoft® Windows NT®, Microsoft® Windows® 95, and OS/2 only), CONFIRM, CONFIRM_SEND, or CONFIRM_DEALLOCATE state. Data sent to the partner TP may have been purged.

0014

ap_unsuccessful

No data is immediately available from the partner TP.

0017

ap_cnos_local_race_reject

APPC is currently processing a CNOS verb issued by a local LU.

0018

ap_cnos_partner_lu_reject

The partner LU rejected a CNOS request from the local LU:

0019

ap_conversation_type_mixed

The TP has issued both basic and mapped conversation verbs. Only one type can be issued in a single conversation.

0021

ap_canceled

The local TP issued one of the following verbs, which canceled RECEIVE_AND_POST or MC_RECEIVE_AND_POST:

• DEALLOCATE with dealloc_type set to AP_ABEND_PROG, AP_ABEND_SVC, or AP_ABEND_TIMER
• MC_DEALLOCATE with dealloc_type set to AP_ABEND
• SEND_ERROR or MC_SEND_ERROR
• TP_ENDED

Issuing one of these verbs causes the semaphore to be cleared.

F002

ap_tp_busy

The local TP has issued a call to APPC while APPC was processing another call for the same TP. This can occur if the local TP has multiple threads, and more than one thread is issuing APPC calls using the same tp_id.

F003

ap_comm_subsystem_abended

Indicates one of the following conditions:

• The node used by this conversation encountered an ABEND.
• The connection between the TP and the PU 2.1 node has been broken (a LAN error).
• The SnaBase at the TP's computer encountered an ABEND.

The system administrator should examine the error log to determine the reason for the ABEND.

F004

ap_comm_subsystem_not_loaded

A required component could not be loaded or has terminated while processing the verb. Thus, communication could not take place. Contact the system administrator for corrective action.

F005

ap_conv_busy

There can only be one outstanding conversation verb at a time on any conversation.

F006

ap_thread_blocking

The calling thread is already in a blocking call.

F008

ap_invalid_verb_segment

The VCB extended beyond the end of the data segment.

F011

ap_unexpected_dos_error

The operating system returned an error to APPC while processing an APPC call from the local TP. The operating system return code is returned through the secondary_rc. It appears in Intel byte-swapped order. If the problem persists, consult the system administrator.

F015

ap_stack_too_small

The stack size of the application is too small to execute the verb. Increase the stack size of your application.

F020

ap_invalid_key

The supplied key was incorrect.