Explanation
An unexpected condition occurred during the running
of
Language Environment condition
management.
- Reason code
- Explanation
- X'01' (1)
- A GOTO was made by an enablement routine.
- X'02' (2)
- Invalid return code from a language-specific event handler was
received during enablement processing.
- X'03' (3)
- Language Environment condition
management detected an implicit movement of the resume cursor. Either
a GOTO or move resume cursor should have been used for resumption
in a different stack frame.
- X'04' (4)
- Invalid return code from a language-specific event handler was
received.
- X'05' (5)
- A program check was detected while Language Environment condition
manager was in control.
- X'06' (6)
- A request to resume the application was not accepted. The Language Environment condition
manager does not accept resumption requests with conditions, such
as abends.
- X'07' (7)
- Invalid return code from a language-specific event handler was
received during stack frame processing.
- X'08' (8)
- CEESGL callable service was attempting to signal a new condition.
A control information block could not be allocated for that condition.
- X'09' (9)
- The CEEHDLR routine returned with an invalid feedback code.
- X'0A' (10)
- The Language Environment library
was unable to find a free control information block for a new condition.
This is a critical error.
- X'0B' (11)
- The error count specified in the ERRCOUNT run-time option has
been exceeded.
- X'0C' (12)
- Language Environment signaled
a condition that could not be resumed. After a resume took place, Language Environment again
attempted to terminate by signaling an imminent termination. Another
resume was attempted and caused an abend.
- X'0D' (13)
- An invalid return code from the Debug Tool was received.
- X'0E' (14)
- An invalid attempt to populate an ISI with qualifying data was
detected.
- X'0F' (15)
- A condition token other than CEE000 was returned from a member
event handler. The feedback token resulted from a new condition being
raised.
- X'10' (16)
- A request to extend stack storage could not be honored. A fixed-size
stack might currently be in use.
- X'11' (17)
- A request for library stack storage could not be completed.
- X'12' (18)
- Stack storage was requested when storage management services were
not available.
- X'13' (19)
- A request to extend stack storage could not be honored.
- X'14' (20)
- After being informed of a new condition, the condition handler
indicated an unrecoverable error.
- X'15' (21)
- The maximum depth of condition nesting specified in the DEPTHCONDLMT
run-time option was exceeded.
- X'16' (22)
- The resume point was invalid.
- X'17' (23)
- BXITA requested ABEND.
- X'18' (24)
- ABEND without LIBVEC layer.
- X'19' (25)
- A CIBH pointer was expected in HCOM_CIBH=0, but the field contained
0.
- X'1A' (26)
- A PCQ pointer was expected in HCOM_PCQ=0, but the field contained
0.
- X'1B' (27)
- No matching PCIBH was found because there was a logic error or
the Language Environment is
corrupted.
- X'1C' (28)
- No storage was available for PCIBH.
- X'1D' (29)
- No storage was available for QDATA.
- X'1E' (30)
- No storage was available for SigRetData.
- X'1F' (31)
- An internal call to the MVS™ function
BPX1SPM was not successful.
- X'20' (32)
- An internal call to the MVS function
BPX1PTR was not successful.
- X'21' (33)
- An internal call to the MVS function
BPX1SPB was not successful.
- X'22' (34)
- CSRL16J tried unsuccessfully to return to the interrupt point
for the signal delivery.
- X'23' (35)
- There was a logic error in Sig safing or the Language Environment is corrupted.
- X'24' (36)
- There was an internal logic error or the Language Environment is corrupted.
- X'25' (37)
- The alternate signal stack supplied by the application is full.
Automatic expansion is not available for alternal signal stacks.
- X'26' (38)
- CEERSN_EMTYCIBH. No Language Environment condition
information block (CIB) was found to be in use.
- X'28' (40)
- CEERSN_NOCIBH. The chain of Language Environment condition
information blocks (CIB) is empty.
- X'29' (41)
- The BPX1SIA callable service failed when Language Environment was trying
to generate a signal.
- X'2A' (42)
- An Internal error occurred in Language Environment® condition
management when the OS/390® CSRL16J
service failed to resume the interrupted program. The return code
from CSRL16J is loaded into register 8 at the time the ABEND is declared.
See z/OS MVS Programming: Assembler Services Reference ABE-HSP for
a description of these return codes.
- X'2B' (43)
- An Internal error occurred in Language Environment condition
management when the RP instruction failed to resume the interrupted
program.
- X'2C' (44)
- The DBX user (or other user of BPX1PTR or PTRACE) tried to resume
the application after a program check using an invalid value in register
4 or 13. When altering the resume registers after a program check
using DBX, make sure that register 4 or 13 points to a valid stack
frame for the current thread.
- X'2D' (45)
- An Internal error occurred in Language Environment condition
management when trying to resume an application with an unknown DSA
address in register 4 or 13.
- X'2E' (46)
- An internal error occurred in Language Environment when
the ESTAE service was unable to establish the ESTAE routine required
by the Quick Freeze Exit Routine. The return code from ESTAE (in register
15) is loaded into register 8 at the time the ABEND is declared, and
the reason code from ESTAE (in register 10) is loaded into register
9. See z/OS MVS Programming: Assembler Services Reference ABE-HSP
for a description of these return codes.
- X'2F' (47)
- ESTAE 0 MACRO failed in CEEOPQEX
- X'30' (48)
- HCOM_SAVED_REG14 was 0 when CEEOSIGR got control
- X'31' (49)
- HCOM_SAVED_REG7 was 0 when CEEOSIGX/Y got control
- X'32' (50)
- HCOM_SAVED_REG7 was 0 when CEEOSIGZ got control
- X'35' (53)
- An internal call to the MVS function
BPX1SPM was not successful. BPX1SPM failed because it was called
on the wrong RB (request block) or in the wrong RB state. This error
can happen if the Language
Environment ESPIE routine gets control after a program check
occurs on a different RB than Language Environment is using
(for example, an application does a LINK SVC to another program that
then takes a program check). Applications that can program check
or ABEND on non-Language Environment RBs need to establish their own
ESPIE/ESTAE to make sure the Language Environment ESPIE or
ESTAE do not get control on an unexpected RB.
- X'37' (55)
- A program check occurred while accessing the field pointed to
by the CEECAA_SAVSTACK_ASYNC field in the CAA (or the CEELCA_SAVSTACK_ASYNC
field in the LCA for AMODE 64 applications).
- X'38' (56)
- A reserve stack is required.
- X'39' (57)
- An error occurred during the handling phase of the condition manager.
Language Environment was
unable to fetch the load module that runs C++ destructors. This error
may occur if there is a shortage of available storage.
System action
Programmer response
If this abend was caused by a user-written
condition handler, check the return codes provided to Language Environment condition
manager.
Another source of this problem can be the use of CEEMRCR
with a type_of_move '1' done for a condition handler
that is invoked for another condition handler.