Return and reason codes

Explanation: CELAAUTH Services attempted to obtain library storage. However, memlimit was set to zero, so the call failed.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure the MEMLIMIT setting for this address space is not zero.

Explanation: CELAAUTH Services attempted to obtain library storage, but the call failed.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Increase the MEMLIMIT size for the address space.

Explanation: CELAAUTH Services attempted to obtain the initial stack and heap storage, but the call failed.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Increase the MEMLIMIT size for the address space.

Explanation: When calling CELAAUTH's internal cellpool services to get storage for the runtime options, the service call failed. The module id and function code part of the reason code will help determine exactly where the service call failed.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure there are enough storage resources on the system.

Explanation: CELAAUTH attempted to terminate the preinitialized environment, but the call failed.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure the system is running correctly at the time.

Explanation: CELAAUTH Services transfered control to the LE library, but the Language Environment® library did not get control in the correct key. This is most likely be caused by CELQLIB, the LE 64-bit library, not in an authorized dataset.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure CELQLIB is placed in a dataset that is in the LPALST or LNKLST concatenation.

Explanation: While processing the request, CELAAUTH Services either program checked or abnormally ended, causing the recovery to get control. The recovery successfully recovered from the error, but the request failed because of the program check or abend.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: If return code is #ALRTN_BAD_PARAMETERS, ensure that the parameters are correct on the CELAAUTH call and that the storage for the parameters is in the correct key.

Explanation: On a CELAAUTH call subroutine or call dll subroutine, the enclave should not terminate. However, during this call, the enclave is terminated unexpectedly.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Make sure the called subroutine didn't cause any program checks or abends during its execution.

Explanation: An unhandled condition occurred during enclave initialization or enclave termination.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Contact IBM® with details of the problem scenario.

Explanation: If the return code is #ALRTN_RESOURCE_ERROR, that means there was an error calling the LOAD service. If the return code is #ALRTN_BAD_PARAMETERS, that means CELAAUTH's internal load service is called with bad parameters.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: If return code is #ALRTN_RESOURCE_ERROR, make sure there are enough system resources on the system. If return code is #ALRTN_BAD_PARAMETERS, take a dump when this return code is received, and contact IBM with the dump.

Explanation: If the return code is #ALRTN_RESOURCE_ERROR, that means there was an error calling the DELETE service. If the return code is #ALRTN_BAD_PARAMETERS, that means CELAAUTH's internal delete service is called with bad parameters.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: If return code is #ALRTN_RESOURCE_ERROR, make sure there are enough system resources on the system. If return code is #ALRTN_BAD_PARAMETERS, take a dump when this return code is received, and contact IBM with the dump.

Explanation: On a CELAAUTH call by routine name call, CELAAUTH Services attempted a load of the module based on the routine name. However, the module with that name does not exist, the module load failed.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure the routine name on the CELAAUTH call is correct.

Explanation: On a CELAAUTH call by dll, CELAAUTH Services attempted a load of a dll based on the given dll name. However, the dll with that name does not exist, the dll load failed.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure the dll name on the CELAAUTH call is correct.

Explanation: On a CELAAUTH call by dll subroutine, CELAAUTH Services attempted to query the dll subroutine address. However, either the subroutine is not exported, or it does not exist, the query failed.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure the dll subroutine name on the CELAAUTH call is correct, and the subroutine is exported.

Explanation: New module initialization failed for the module that contains the user routine.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Contact IBM with details of the problem scenario.

Explanation: DLL static initialization failed for the module that contains the user routine.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Contact IBM with details of the problem scenario.

Explanation: The running of C++ static constructors failed for the module that contains the user routine.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Contact IBM with details of the problem scenario.

Explanation: The user routine abended. The routine return code is set to the abend completion code from the SDWA (SDWAABCC). The routine reason code is set to the abend reason code from the SDWA (SDWACRC).

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Use the abend code and reason code to determine the problem.

Explanation: During CELAAUTH initialization, the service attempted to create internal latch sets to be used later. However, the latch set create failed.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure there are enough system resources on the system.

Explanation: The function code in the user parameter list is unknown.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Make sure CELAAUTH Services is called through the CELAAUTH or CELAUTHP macros.

Explanation: CELAAUTH Services failed to get the storage for the central control block for CELAAUTH Services infrastructure.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure there are enough storage resources on the system.

Explanation: CELAAUTH Services attempted to schedule an IRB to the ARO task, but the scheduling of the IRB failed.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure there are enough system resources on the system.

Explanation: When CELAAUTH Services terminates a user managed or system managed environment, it checks to see if it should terminate the infrastructure as well. It found that there are still other environments initialized, so it skipped infrastructure termination. This reason code does not necessarily indicate an error, which is why the return code associated with it is #ALRTN_QUALIFIED_SUCCESS. This is only an error if the caller thinks that there shouldn't be any environment still initialized after the call.

System Action: CELAAUTH returns this reason code back to the caller.

Programmer Response: If the caller thinks this is an error, a dump should be taken, and contact IBM with the dump.

Explanation: On a user managed call, the environment token passed in is not valid.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure a valid environment token is passed in.

Explanation: An attempt to call a CELAAUTH service is made; however, CELAAUTH Services infrastructure is not initialized.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure a USERINIT or MNGDINIT call is made successfully before any other CELAAUTH services are called.

Explanation: Due to system restrictions in cross memory environment, CELAAUTH does not support initialization in cross memory environment. Any attempt to do so will receive this reason code back.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure the CELAAUTH initialization call is not made in cross memory environment.

Explanation: While the CELAAUTH Services infrastructure is initialized, no service requests are allowed until the infrastructure is fully initialized. Any attempt to call CELAAUTH while CELAAUTH Services initialization is in progress will result in this error reason code.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Wait a while before try calling CELAAUTH again. If the problem persists, take a dump, and contact IBM with the captured dump.

Explanation: If a system managed environment already exists, any attempt to initialize a system managed environment with the same environment id will result in this reason code.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Make sure the managed init should be done, and the environment id is correct. Or make sure the managed environment is terminated first before trying initialization again.

Explanation: If CELAAUTH Services is in the middle of terminating its infrastructure, any attempt to initialize CELAAUTH Services will result in this reason code.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Wait a while before try calling CELAAUTH Services initialization again. If the problem persists, take a dump, and contact IBM with the captured dump.

Explanation: CELAAUTH Services attempted to allocate a Pause Element Token. However, the allocation failed. This is most likely due to a system resource shortage.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure there are enough system resources on the system.

Explanation: CELAAUTH Services attempted to pause on a Pause Element Token. However, the pause failed. This is most likely due to a system resource shortage.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure there are enough system resources on the system.

Explanation: CELAAUTH Services attempted to release a Pause Element Token. However, the release failed. This is most likely due to a system resource shortage.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure there are enough system resources on the system.

Explanation: CELAAUTH Services attempted to deallocate a Pause Element Token. However, the deallocation failed. This is most likely due to a system resource shortage.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure there are enough system resources on the system.

Explanation: While calling CELAAUTH in a cross memory environment, CELAAUTH Services attempted to locate the ASCB of the primary address space. However, the attempt failed. This is most likely the result of a system error.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure the system is running correctly at the time.

Explanation: During CELAAUTH Services infrastructure initialization, the caller passed in a Resource Owning Task TCB. However, the specified TCB is not valid.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure the correct Resource Owning Task TCB is specified.

Explanation: CELAAUTH Services initialization is not permitted on a task that's above the initiator task. Or CELAAUTH Services initialization is not permitted with a resource owning task that is above the initiator task. This is most likely cause by initializing CELAAUTH Services before the address space is fully initialized.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure the address space is fully initialized, and the resource owning task is not above the initiator task.

Explanation: During CELAAUTH Services infrastructure initialization, CELAAUTH attached a worker task to the CELAAUTH resource owning task. The attach of the worker task failed. This is most likely due to a shortage of system resources.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure there are enough system resource on the system.

Explanation: During CELAAUTH Services infrastructure initialization, CELAAUTH attempted to load the 64bit LE library. However, the load failed.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure CELQLIB is in the library load search path.

Explanation: On a CELAAUTH user managed call or user managed term, the required parameter, environment token, is not specified.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure the environment token is specified on the call.

Explanation: During CELAAUTH user managed call and user managed term, CELAAUTH Services attempted to exclusively lock the user managed environment, but the user managed environment is currently in use. Or during CELAAUTH system managed term, CELAAUTH Services attempted to exclusively lock the system managed environment, but the system managed environment is currently in use. Use the function code part of the reason code to determined the exact cause of this problem.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Wait a while for the environment to get freed up, before trying the service again. If the problem persists, take a dump, and contact IBM with the captured dump.

Explanation: The runtime option string passed in during initialization or call is too long.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Make sure the runtime options string length in the parameter list correctly reflect the length of the runtime option string. And the length of the runtime option string doesn't exceed the limit.

Explanation: During a CELAAUTH user call or user term, the environment token specified belonged to a previous instance of the environment. This means the environment was terminated before this call was made, the environment token no longer refers to a valid environment.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure the correct environment token is specified.

Explanation: During a CELAAUTH user call or managed call, the routine token specified is not valid.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure the correct routine token is specified.

Explanation: During a CELAAUTH user call or manage call, the routine token specified belonged to a previous instance of the environment. This means the environment that this routine token belonged to was terminated before this call was made, the routine token no longer refers to a valid environment.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure the correct routine token is specified.

Explanation: During a CELAAUTH user call, the routine token specified doesn't belonged to the environment specified by the environment token.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure the correct routine token and environment token are specified.

Explanation: On a call main or call sub, the module loaded does not contain a main or a fetchable subroutine.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure the load module specified in the routine name field contains either a main or a fetchable routine.

Explanation: On a call main or call sub, the routine name length specified in the parameter is not valid.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure the correct routine name length is specified.

Explanation: On a call dll sub, the routine name length specified in the parameter is not valid.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure the correct routine name length is specified.

Explanation: When calling CELAAUTH Services internal cellpool services to get storage for the runtime options, the service call failed.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure there are enough storage resources on the system.

Explanation: When calling CELAAUTH Services internal cellpool services to get storage for a group of runtime options, the service call failed.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure there are enough storage resources on the system.

Explanation: When calling CELAAUTH Services internal cellpool services to get storage for an environment information control block, the service call failed.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure there are enough storage resources on the system.

Explanation: When calling CELAAUTH Services internal cellpool services to get storage for a group of environment information control blocks, the service call failed.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure there are enough storage resources on the system.

Explanation: When calling CELAAUTH Services internal cellpool service to get the storage for an Authorized Environment Definition Table, the called service failed.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure there are enough storage resources on the system.

Explanation: When calling CELAAUTH Services internal cellpool services to create the internal cellpools, the create failed.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure there are enough storage resources on the system.

Explanation: When calling CELAAUTH Services internal cellpool services to get the storage for a System Managed control block, the called service failed.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure there are enough storage resources on the system.

Explanation: The init/incr/max environment numbers mismatch. There are 3 possibilities: 1) init = max and the incr ^= 0 2) init < max and the incr = 0 3) init > max

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Make sure the specified init/incr/max values in the AEDT are correct.

Explanation: The RTO length specified in the AEDT is non-zero, while the RTO string in the AEDT is zero.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Make sure the RTO length and the RTO string are correct.

Explanation: The user didn't specify any environment types in the parameter list on a CELAUTH(MNGDINIT) call.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Make sure at least one AEDE entry is defined in the AEDT.

Explanation: A set of environments with the managed environment ID specified on a CELAAUTH REQUEST(MNGDCALL) or REQUEST(MNGDTERM) could not be located.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure that a set of environments for this managed environment ID has been created using CELAAUTH REQUEST(MNGDINIT).

Explanation: The requested environment set is not in a state in which it can be used by the current call. This probably indicates that the environment set is in the process of being terminated.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure that no attempt is made to use an environment set while it is being terminated.

Explanation: Storage could not be obtained for a routine information control block.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Examine the information from the cell pool services call to determine the error.

Explanation: The requested environment set could not be properly unlocked.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Contact IBM with details of the problem scenario.

Explanation: The managed environment id is invalid. Specify a valid env id.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Make sure the managed environment id not zero.

Explanation: All existing environments within the requested environment type are in use, and no more environments can be created because the maximum number has been reached.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: If this reason code occurs frequently, consider increasing the maximum number of environments within the environment type entry (field AEDE_MAX in macro CEEAEDT).

Explanation: The requested routine was successfully called. However, while attempting to create additional environments for the current environment type, one or more environments could not be created.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Examine the additional error information to determine the error.

Explanation: CELAAUTH Services attempted to use the routine token provided by the caller on a CELAAUTH REQUEST(USERCALL/MNGDCALL). A failure occurred while accessing this token.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure that a valid routine token has been provided on the CELAAUTH call.

Explanation: While attempting to copy the AEDE number from the user passed in parameter list using the caller's key, CELAAUTH Services failed.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure that a valid AEDT is specified on the CELAAUTH call.

Explanation: While attempting to copy the AEDT from the user passed in parameter list using the caller's key, CELAAUTH Services failed.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure that a valid AEDT is specified on the CELAAUTH call.

Explanation: While attempting to store the environment token into the user passed parameter list, CELAAUTH Services failed.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure that the environment token storage passed in on the CELAAUTH call is valid.

Explanation: While attempting to copy the runtime option strings from user passed in parameter list using the caller's key, CELAAUTH Services failed.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure that a valid runtime option string is specified on the CELAAUTH call.

Explanation: While attempting to copy the routine name from the user parameter list, a failure occurred.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure that a valid routine name is specified on the CELAAUTH call.

Explanation: While attempting to copy the DLL routine name from the user parameter list, a failure occurred.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure that a valid DLL routine name is specified on the CELAAUTH call.

Explanation: CELAAUTH Services attempted to use the environment token provided by the caller on a CELAAUTH REQUEST(USERCALL). A failure occurred while accessing this token.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure that a valid environment token has been provided on the CELAAUTH call.

Explanation: CELAAUTH Services attempted to attach the worker task using an IRB. The IRB failed while attempting the ATTACH. while accessing this token.

System Action: A dump is taken to capture diagnostic information. CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Examine the dump to determine the reason for the ATTACH failure. If the failure does not appear to be the fault of the user's environment, contact IBM with the captured dump.

Explanation: CELAAUTH Services attempted to allocate an additional stack frame but the expansion overflowed the maximum boundary of the entire stack.

System Action: An abend of 4088 is generated, a dump should be captured.

Programmer Response: Contact IBM with the captured dump.

Explanation: CELAAUTH Services attempted to access the user parameter list, but a failure occurred.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Ensure that the parameter list is allocated in storage that is accessible to the caller.

Explanation: CELAAUTH Services attempted to access its module table, but a failure occurred.

System Action: The reason code is returned back to the Language Environment load service.

Programmer Response: Contact IBM with details of the problem scenario.

Explanation: CELAAUTH Services attempted to access the user-provided module entrypoint, but a failure occurred.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: If RTNADDR was specified, ensure that the address that is provided is the CELQSTRT entrypoint for the routine. If RTNNAME was specified, ensure that the entrypoint for the corresponding load module is CELQSTRT.

Explanation: While the caller is waiting for the worker task to process a request, the worker task is terminated, and the worker task resource manager got control, and released the caller from waiting.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup. This reason is most likely caused by an earlier error.

Programmer Response: When this reason code is detected, the caller should exit its code as soon as possible, and let CELAAUTH Services do the necessary cleanup.

Explanation: When calling CELAAUTH Services internal cellpool services to destroy the internal cellpools, the destroy failed.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Contact IBM with details of the problem scenario.

Explanation: During worker task resource manager processing, it terminated the address space because there are still units of work using the worker task resources.

System Action: A dump with 4094 completion code and this reason code is generated.

Programmer Response: Contact IBM with the captured dump.

Explanation: CELAAUTH Services failed to determine its state. This could be caused by other unknown system errors, and/or because of storage overlays.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: If the system appears to be running fine, take a dump, and contact IBM support with the dump taken.

Explanation: The AEDT_EDENUM value did not match the value used when the set of system managed environments was initialized. The AEDT specified for a MNGDUPDT request must contain the same number of environment definition entries (AEDE) as the AEDT that was used for the MNGDINIT request.

System Action: CELAAUTH returns this reason code back to the caller, after cleanup.

Programmer Response: Make sure the AEDT_EDENUM value in the AEDT is correct.

Explanation: The AEDE_MAX value specified for at least one AEDE was less than the value currently in effect. The maximum number of environments can only be increased. The AEDE_MAX value must be greater than the value specified for the MNGDINIT request and any previous MNGDUPDT requests.

System Action: CELAAUTH returns this reason code to the caller after cleanup. When the return code is #ALRTN_QUALIFIED_SUCCESS, the requests of other AEDE entries containing AEDE_MAX values greater than the value currently in effect are honored.

Programmer Response: Make sure the AEDE_MAX value in each AEDE is correct.

Explanation: The AEDE_MAX value for every AEDE was either zero or the value currently in effect. No updates were performed. The maximum number of environments can only be increased. The AEDE_MAX value must be greater than the value specified for the MNGDINIT request and any previous MNGDUPDT requests for at least one AEDE.

System Action: CELAAUTH returns this reason code to the caller after cleanup.

Programmer Response: Make sure the AEDE_MAX value in each AEDE is correct.