Secondary APPC Return Codes

00000000

ap_cnos_accepted: APPC accepts the session lines and responsibility as specified.

00000001

ap_bad_tp_id: The value of tp_id did not match a TP identifier assigned by APPC.

00000002

ap_bad_conv_id: The value of conv_id did not match a conversation identifier assigned by APPC.

00000003

ap_bad_lu_alias: APPC cannot find the specified lu_alias among those defined.

000000C4

ap_rcv_immd_bad_fill (for a basic conversation): The fill parameter was set to an invalid value.

00000004

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

00000005

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.

00000006

ap_invalid_data_segment: The PIP data was longer than the allocated data segment, or the address of the PIP data buffer was wrong.

00000007

ap_cnos_negotiated

APPC accepts the session limits and responsibility as negotiable by the partner LU. Values that can be negotiated are:

plu_mode_session_limit

min_conwinners_source

min_conwinners_target

responsible

drain_target

000000D7

ap_bad_return_status_with_data: The specified rtn_status value was not recognized by APPC.

00000011

ap_bad_conv_type (for a basic conversation): The value specified for conv_type was invalid.

00000012

ap_bad_sync_level: The value specified for sync_level was invalid.

00000013

ap_bad_security: The value specified for security was invalid.

00000014

ap_bad_return_control: The value specified for rtn_ctl was invalid.

00000016

ap_pip_len_incorrect: The value of pip_dlen was greater than 32767.

00000017

ap_no_use_of_snasvcmg (for a mapped conversation): SNASVCMG is not a valid value for mode_name.

00000018

ap_unknown_partner_mode: The value specified for mode_name was invalid.

00000031

ap_confirm_on_sync_level_none: The local TP attempted to use CONFIRM or MC_CONFIRM in a conversation with a synchronization level of AP_NONE. The synchronization level, established by ALLOCATE or MC_ALLOCATE, must be AP_CONFIRM_SYNC_LEVEL.

00000032

ap_confirm_bad_state: The conversation was not in SEND state.

00000033

ap_confirm_not_ll_bdy: The conversation for the local TP was in SEND state, and the local TP did not finish sending a logical record.

00000051

ap_dealloc_bad_type: The dealloc_type parameter was not set to a valid value.

00000052

ap_dealloc_flush_bad_state

The conversation was not in SEND state and the TP attempted to flush the send buffer. This attempt occurred because the value of dealloc_type was AP_FLUSH or because the value of dealloc_type was AP_SYNC_LEVEL and the synchronization level of the conversation was AP_NONE. In either case, the conversation must be in SEND state.

00000053

ap_dealloc_confirm_bad_state: The conversation was not in SEND state, and the TP attempted to flush the send buffer and send a confirmation request.

00000055

ap_dealloc_not_ll_bdy (for a basic conversation): The conversation was in SEND state, and the TP did not finish sending a logical record. The dealloc_type parameter was set to AP_SYNC_LEVEL or AP_FLUSH.

00000057

ap_dealloc_log_ll_wrong: The LL field of the GDS error log variable did not match the actual length of the log data.

00000061

ap_flush_not_send_state: The conversation was not in SEND state.

000000A1

ap_p_to_r_invalid_type: The ptr_type parameter was not set to a valid value.

000000A2

ap_p_to_r_not_ll_bdy: The local TP did not finish sending a logical record.

000000A3

ap_p_to_r_not_send_state: The conversation was not in SEND state.

000000B1

ap_rcv_and_wait_bad_state: The conversation was not in RECEIVE or SEND state when the TP issued this verb.

000000B2

ap_rcv_and_wait_not_ll_bdy (for a basic conversation): The conversation was in SEND state; the TP began but did not finish sending a logical record.

000000B5

ap_rcv_and_wait_bad_fill (for a basic conversation): The fill parameter was set to an invalid value.

000000C1

ap_rcv_immd_bad_state: The conversation was not in RECEIVE state.

000000D1

ap_rcv_and_post_bad_state: The conversation was not in RECEIVE or SEND state when the TP issued this verb.

000000D2

ap_rcv_and_post_not_ll_bdy: The conversation was in SEND state; the TP began but did not finish sending a logical record.

000000D5

ap_rcv_and_post_bad_fill: The fill parameter was set to an invalid value.

000000D6

ap_invalid_semaphore_handle: The address of the RAM semaphore or system semaphore handle was invalid.
Note APPC cannot trap all invalid semaphore handles. If the TP passes a bad RAM semaphore handle, a protection violation results.

000000D7

ap_bad_return_status_with_data: The specified rtn_status value was not recognized by APPC.

000000E1

ap_r_t_s_bad_state: The conversation is not in an allowed state when the TP issued this verb.

000000F1

ap_bad_ll (for a basic conversation): The logical record length field of a logical record contained an invalid value — 0x0000, 0x0001, 0x8000, or 0x8001. See About Transaction Programs for information on logical records.

000000F2

ap_send_data_not_send_state: The local TP issued SEND_DATA or MC_SEND_DATA, but the conversation was not in SEND state.

000000F5

ap_send_data_confirm_on_sync_none: The type CONFIRM is not permitted for a conversation that was allocated with a sync_level of NONE.

000000F6

ap_send_data_not_ll_bdy (for a basic conversation)

The TP started but did not finish sending a logical record. This occurs only when type is one of the following:

AP_SEND_DATA_CONFIRM

AP_SEND_DATA_DEALLOC_FLUSH

AP_SEND_DATA_DEALLOC_SYNC_LEVEL

AP_SEND_DATA_P_TO_R_FLUSH

AP_SEND_DATA_P_TO_R_SYNC_LEVEL

00000102

ap_send_error_log_ll_wrong (for a basic conversation): The LL field of the error log GDS variable did not match the actual length of the data.

00000103

ap_send_error_bad_type (for a basic conversation): The value of err_type was invalid.

00000105

ap_bad_error_direction: The specified err_dir was not recognized by APPC.

00000150

ap_cnos_implicit_parallel: APPC does not permit a program to change the session limit for a mode other than SNASVCMG mode for the implicit partner template when the template specifies parallel sessions. (The term "template" is used because many of the actual values are yet to be filled in).

00000151

ap_cant_raise_limits: APPC does not permit setting session limits to a nonzero value unless the limits currently are zero.

00000152

ap_autoact_exceeds_sesslim: On the CNOS verb, the value for auto_activate is greater than the value for partner_lu_mode_session_limit.

00000153

ap_all_mode_must_reset: APPC does not permit a nonzero session limit when mode_name_select indicates ALL.

00000154

ap_bad_snasvcmg_limits: Your program specified invalid settings for the partner_lu_mode_session_limit, min_conwinners_source, or min_conwinners_target parameters when mode_name was supplied.

00000155

ap_min_gt_total: The sum of min_conwinners_source and min_conwinners_target specifies a number greater than partner_lu_mode_session_limit.

00000156

ap_mode_closed: The local LU cannot negotiate a nonzero session limit because the local maximum session limit at the partner LU is zero.

00000156

ap_cnos_mode_closed: The local LU cannot negotiate a nonzero session limit because the local maximum session limit at the partner LU is zero.

00000157

ap_cnos_mode_name_reject: The partner LU does not recognize the specified mode name.

00000159

ap_reset_sna_drains: The SNASVCMG mode does not support the drain parameter values.

0000015A

ap_single_not_src_resp: For a single-session CNOS verb, APPC permits only the local (source) LU to be responsible for deactivating sessions.

0000015B

ap_bad_partner_lu_alias: APPC did not recognize the supplied partner_lu_alias.

0000015C

ap_exceeds_max_allowed: Your program issued a CNOS verb, specifying a partner_lu_mode_session_limit number and set_negotiable (NO).

0000015D

ap_change_src_drains: APPC does not permit mode_name_select (ONE) and drain_source (YES) when drain_source (NO) is currently in effect for the specified mode.

0000015E

ap_lu_detached: A command reset the definition of the local LU before the CNOS verb tried to specify the LU.

0000015F

ap_cnos_command_race_reject: The local LU is currently processing a CNOS verb issued by the partner LU.

00000167

ap_snasvcmg_reset_not_allowed: Your local program attempted to issue the CNOS verbs for the mode named SNASVCMG, specifying a session limit of zero.

000001B4

ap_display_info_exceeds_length: The returned DISPLAY information did not fit in the buffer.

000001B5

display_invalid_constant: The value supplied for NUM_SECTIONS or INIT_SEC_LEN is invalid.

00000506

ap_undefined_tp_name: In the configuration file for your application, APPC could not find an invokable TP name matching the value of tp_name.

00000509

ap_allocate_not_pending: APPC did not find an incoming allocate (from the invoking TP) to match the value of tp_name, supplied by RECEIVE_ALLOCATE. RECEIVE_ALLOCATE waited for the incoming allocate and eventually timed out.

00000519

ap_cpsvcmg_mode_not_allowed: The mode named CPSVCMG cannot be specified as the mode_name on the deactivate session verb.

00000525

ap_invalid_process: The process issuing RECEIVE_ALLOCATE was different from the one started by APPC.

080F6051

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

084B6031

ap_trans_pgm_not_avail_retry: The remote LU rejected the allocation request because it was unable to start the requested partner TP. The condition may be temporary, such as a time-out. The reason for the error may be logged on the remote node. Retry the allocation.

084C0000

ap_trans_pgm_not_avail_no_retry: The remote LU rejected the allocation request because it was unable to start the requested partner TP. The condition is permanent. The reason for the error may be logged on the remote node. Do not retry the allocation until the error has been corrected.

10086021

ap_tp_name_not_recognized: The partner LU does not recognize the TP name specified in the allocation request.

10086031

ap_pip_not_allowed: The allocation request specified PIP data, but either the partner TP does not require this data, or the partner LU does not support it.

10086032

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.

10086034

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

10086041

ap_sync_level_not_supported: The partner TP does not support the sync_level (AP_NONE or AP_CONFIRM_SYNC_LEVEL) specified in the allocation request, or the sync_level was not recognized.