Cics Abend
Cics Abend
AEXU -
During execution of an EXEC CICS command, a NOTPOSS condition has been raised on encountering an
invalid parameter. This is probably caused by a previous storage overlay.
AEXY -
The executing transaction has been purged before control could be returned.
AEXZ –
A command has failed due to a serious failure in a CICS component (resource manager).
AEYD –
A transaction has requested that CICS access a storage area that the transaction itself could not access.
This occurred when an invalid storage area was passed to CICS as an output parameter on an EXEC CICS
command.
AEY9 –
One of the following:
An EXEC CICS command has been issued that is not supported by the EXEC interface program
DFHEIP.
A transaction has issued an EXEC CICS command which is supported in principle by the EXEC
interface program DFHEIP, but for which the prerequisite function has not been included in the current
CICS start-up.
A non-CICS command has been issued via an application "stub" (expansion of a DFHRMCAL macro),
and the program DFHERM has detected that the necessary non-CICS support is not available.
An attempt has been made to use remote resources, but the local SYSID has been specified in an
EXEC CICS command, or vice versa.
AEZA –
A transaction has been defined with a TASKDATALOC(ANY), but the programs within the transaction
are running amode 24. The exec interface program is therefore is unable to access the TCA for the
application. Furthermore, any reference to the EIB would cause the transaction to fail with an OC4
protection exception.
AEZB –
A transaction has been defined with a TASKDATALOC(ANY), and the application is attempting to call
a task related user exit. However the task related user exit has been link edited AMODE 24 and enabled
with the LINKEDITMODE option, thereby directing CICS to invoke it in AMODE 24. An AMODE 24
task related user exit cannot run when the calling application is running with TASKDATALOC(ANY), as
this would cause a protection exception, or a storage overwrite.
AEZC -
A transaction has been defined with a TASKDATALOC(ANY), but a program within the transaction is
defined to run AMODE 24. CICS cannot invoke the AMODE 24 program when the transaction is running
with TASKDATALOC(ANY), as this would cause a protection exception, or a storage overwrite.
AEZD –
An attempt has been made to run a program defined as EXECKEY(USER) as part of a transaction defined
as TASKDATAKEY(CICS). These attributes are incompatible and the transaction is abended. This
incompatibility could occur as a result of the program definition being auto installed. See the CICS
Customization Guide and the CICS Resource Definition Guide for more information about
program auto install.