Abend codes AExx

AEC1
Explanation:

An attempt has been made to use the Command Level Interpreter (CECI) or the Enhanced Master Terminal (CEMT) or an RDO (CEDA, CEDB, CEDC) transaction on a terminal that is not supported.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Use a terminal that is supported by the Command Level Interpreter, Enhanced Master Terminal, or RDO transaction.

Module(s):

DFHECIP, DFHECSP, DFHEMTP, DFHESTP, DFHEOTP, DFHEDAP

AEC2
Explanation:

An attempt has been made to use the Command Level Interpreter (CECI) or the Enhanced Master Terminal (CEMT) or an RDO (CEDA, CEDB, CEDC) transaction on a display terminal of size less than 24 X 80.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Use a display terminal that is supported by the Command Level Interpreter or Enhanced Master Terminal or RDO transaction.

Modules:

DFHECIP, DFHECSP, DFHEMTP, DFHESTP, DFHEOTP, DFHEDAP

AEC7
Explanation:

Language Environment has encountered an unexpected error during the THREAD INITIALIZATION phase while attempting to execute a Language Environment enabled program. The return code received from Language Environment is placed into the field EIBRESP2.

System action:

Message DFHAP1200 is issued and the transaction is abnormally terminated. The program is disabled.

User response:

Refer to the error message or messages issued by Language Environment to determine the cause of the problem.

Modules:

DFHAPLI

AEC8
Explanation:

Language Environment has encountered an unexpected error during the RUNUNIT INITIALIZATION phase while attempting to execute a Language Environment enabled program.

System action:

The return code received from Language Environment is placed into the field EIBRESP2. Message DFHAP1200 is issued and the transaction is abnormally terminated. The program is disabled.

User response:

Refer to the error message or messages issued by Language Environment to determine the cause of the problem.

Modules:

DFHAPLI

AEC9
Explanation:

Language Environment has encountered an unexpected error during the RUNUNIT BEGIN INVOCATION phase while attempting to execute a Language Environment enabled program.

System action:

The return code received from Language Environment is placed into the field EIBRESP2. Message DFHAP1200 is issued and the transaction is abnormally terminated. The program is disabled.

User response:

Refer to the error message or messages issued by Language Environment to determine the cause of the problem.

Modules:

DFHAPLI

AEDA
Explanation:

The CEDF transaction has been started with an invalid start code. This could be the result of attempting to start the execution diagnostic facility (EDF) with EXEC CICS START(CEDF).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Use the transaction dump to determine why the start has failed.

Modules:

DFHEDFX

AEDB
Explanation:

DFHEDFP has been passed an invalid EDFXA. This is an internal CICS error.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS® Problem Determination Guide for guidance on how to proceed.

Modules:

DFHEDFX

AEDC
Explanation:

The program EDF has terminated because a GETMAIN request to the storage manager failed.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Use the transaction dump to determine why the request has failed.

Modules:

DFHEDFX

AEDD
Explanation:

CICS has attempted to attach the EDF task to display the user request but the attach has failed.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Use the transaction dump to determine why the attach has failed.

Modules:

DFHEDFX

AEDE
Explanation:

CICS has suspended the user task to allow the EDF task to complete but an error has occurred while performing the suspend.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Use the transaction dump to determine why the suspend has failed.

Modules:

DFHEDFX

AEDF
Explanation:

CICS has suspended the user task to allow the EDF task to complete. The user task has been purged while suspended, before control was returned from EDF.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

The task was probably purged by the master terminal operator.

Investigate the reason why the task was purged. This may have been in an attempt to clear the system which appeared to be deadlocked for some reason.

Modules:

DFHEDFX

Start of change
AEDG
Explanation:

CICS has suspended the user task to allow the EDF task to complete. The user task has gone away while suspended, before control was returned from EDF.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Use the transaction dump to determine the reason why the task finished before being resumed.

Modules:

DFHEDFX

End of change
AEDH
Explanation:

An error occurred when CICS called the Program Manager in order to discover details of the user program that has invoked EDF.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Use the transaction dump to determine why the call has failed.

Modules:

DFHEDFX

AED1
Explanation:

This abend is produced as a result of either:

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Use a terminal or device that is properly supported.

Modules:

DFHEDFP, DFHEDFBR

AED2
Explanation:

The program EDF has terminated a task and placed this abend code in the terminated task’s TCA. This occurs because execution of EDF is about to be abnormally terminated. A probable reason for EDF being terminated is that a line, control unit, or a terminal has been put out of service.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Use a terminal that is supported as a display terminal by EDF. A CICS transaction dump of the task terminated with this abend code is available for review.

Modules:

DFHEDFX

AED3
Explanation:

The program EDF has terminated a task and placed this abend code in the terminated task’s TCA. The termination occurs because execution of EDF is about to be abnormally terminated.

One possible cause of an abend in EDF is incorrect data being sent to the terminal by the user task.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

A CICS transaction dump of the terminated task and also a similar dump for EDF, when its termination was abnormally terminated, are available for review.

Modules:

DFHEDFX

AED4
Explanation:

An internal logic error has been detected in EDF module DFHEDFP.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

This indicates a CICS logic error. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHEDFP

AED5
Explanation:

An internal logic error was been detected in EDF. Insufficient dynamic storage was pre-allocated.

System action:

EDF is terminated abnormally with dumps having dump codes CXSP, RMIN, PAGE, LDIN. The user task continues.

User response:

The problem may be avoided by less complex user interactions with EDF. If the problem persists, you may need further assistance. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHEDFD

AED6
Explanation:

An internal logic error was detected in EDF.

System action:

EDF is terminated abnormally with dumps having dump codes CXSP, RMIN, PAGE, LDIN. The user task continues.

User response:

The problem may be avoided by less complex user interactions with EDF. If the problem persists, you may need further assistance. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHEDFU

AED7
Explanation:

The installed definition of the transaction CEDF has a TWA size which is too small.

System action:

CICS abnormally terminates the transaction with a CICS transaction dump.

User response:

If you have an updated copy of the CEDF transaction installed, ensure that you have a TWA size at least as big as the one defined by the IBM supplied definition. If you do not have an updated CEDF you may need further assistance to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHEDFP

AED8
Explanation:

A terminal control error has occurred in DFHEDFX.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHEDFX

AED9
Explanation:

A temporary storage error has occurred in EDF. This could be caused by an input/output error on temporary storage or because temporary storage data is full.

System action:

EDF is abnormally terminated with a CICS transaction dump.

User response:

Investigate the reason for the temporary storage request failure. Ensure that the definition of the temporary storage data set is correct.

See the CICS Problem Determination Guide for further guidance in dealing with temporary storage problems.

Modules:

DFHEDFD

AEIA
Note:

The description of this abend also applies to AEID to AEI9, AEXC, AEXF, AEXG, AEXI to AEXL, AEXV to AEXX, AEX0 to AEX9, AEYA to AEYC, AEYE to AEY3, AEY7, and AEZE to AEZX.

Explanation:

The EXEC interface program issues an abend when an exceptional condition has occurred but the command does not have the RESP option (or NOHANDLE option), or the application program has not executed an EXEC CICS HANDLE CONDITION command for that condition. This will cause DFHEIP to take the system action for the condition in question. In most cases, the system action will be to abend the transaction.

Because of their similar characteristics, the above-named abend codes for the EXEC interface program are described as a group. The codes and their corresponding exceptional conditions are as follows:

Code Condition
AEIA ERROR
AEID EOF
AEIE EODS
AEIG INBFMH
AEIH ENDINPT
AEII NONVAL
AEIJ NOSTART
AEIK TERMIDERR
AEIL FILENOTFOUND
AEIM NOTFND
AEIN DUPREC
AEIO DUPKEY
AEIP INVREQ
AEIQ IOERR
AEIR NOSPACE
AEIS NOTOPEN
AEIT ENDFILE
AEIU ILLOGIC
AEIV LENGERR
AEIW QZERO
AEIZ ITEMERR
AEI0 PGMIDERR
AEI1 TRANSIDERR
AEI2 ENDDATA
AEI3 INVTSREQ
AEI4 EXPIRED
AEI8 TSIOERR
AEI9 MAPFAIL
AEXC RESIDERR
AEXF ESCERROR
AEXG UOWLNOTFOUND
AEXI TERMERR
AEXJ ROLLEDBACK
AEXK END
AEXL DISABLED
AEXV VOLIDERR
AEXW SUPPRESSED
AEXX TASKIDERR
AEX0 TCIDERR
AEX1 DSNNOTFOUND
AEX2 LOADING
AEX3 MODELIDERR
AEX4 UOWNOTFOUND
AEX5 PARTNERIDERR
AEX6 PROFILEIDERR
AEX7 NETNAMEIDERR
AEX8 LOCKED
AEX9 RECORDBUSY
AEYA INVERRTERM
AEYB INVMPSZ
AEYC IGREQID
AEYE INVLDC
AEYG JIDERR
AEYH QIDERR
AEYJ DSSTAT
AEYK SELNERR
AEYL FUNCERR
AEYM UNEXPIN
AEYN NOPASSBKRD
AEYO NOPASSBKWR
AEYP SEGIDERR
AEYQ SYSIDERR
AEYR ISCINVREQ
AEYT ENVDEFERR
AEYU IGREQCD
AEYV SESSIONERR
AEYX USERIDERR
AEYY NOTALLOC
AEYZ CBIDERR
AEY0 INVEXITREQ
AEY1 INVPARTNSET
AEY2 INVPARTN
AEY3 PARTNFAIL
AEY7 NOTAUTH
AEZE CHANGED
AEZF PROCESSBUSY
AEZG ACTIVITYBUSY
AEZH PROCESSERR
AEZI ACTIVITYERR
AEZJ CONTAINERERR
AEZK EVENTERR
AEZL TOKENERR
AEZM NOTFINISHED
AEZN POOLERR
AEZO TIMERERR
AEZP SYMBOLERR
AEZQ TEMPLATERR
AEZR NOTSUPERUSER
AEZS CSDERR
AEZT DUPRES
AEZU RESUNAVAIL
AEZV CHANNELERR
AEZW CCSIDERR
AEZX TIMEDOUT
Problem determination:

The function code of the command that produced the exceptional response and the response code can be found in the EXEC interface block (EIB). The EIB is part of a larger control block, used by DFHEIP, known as the EXEC interface storage block (EIS). The EIS is addressed by the TCAEISA, which is the system part of the TCA + X'90' The EIB is pointed to from the EIS + X'8'.

The function code may be located at offset X'1B' in the EIB while the response codes may be one of the following at the given offsets:

EIBRCODE
X'1D'
EIBRESP
X'4C'
EIBRESP2
X'50'

The CICS Application Programming Reference gives translations of the encoded functions and their responses.

Analysis: Because these abend codes are directly related to exceptional conditions that can be specified in HANDLE CONDITION commands, the application programmer should decide whether the condition is one that should be handled by the application (for example ENDFILE), or one that requires modifications to the application or CICS tables.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Change the application program either to prevent the condition recurring, to check it by using the RESP option, or to handle the condition when it does occur (by using the EXEC CICS HANDLE CONDITION command). If necessary, use the contents of the EIBRESP2 field or the EIBRCODE in the EIB to assist in determining the cause of the exceptional condition.

Modules:

DFHEIP

AELA
Explanation:

The executing function has been purged before control could be returned.

System action:

The transaction is marked to be abnormally terminated with abend code AELA.

User response:

Investigate the reason the task was purged. It was purged either by the master terminal operator, or as a result of a deadlock timeout.

If the task was purged by the master terminal operator, this may have been in an attempt to clear the system which appeared to be deadlocked for some reason.

If the task was timed out automatically as a result of the DTIMOUT value being exceeded, this may be due to insufficient main storage being available for the number of tasks in the system. If the amount of main storage cannot be increased then the number of tasks in the system should be reduced to avoid short-on-storage situations. Another possibility would be to increase the value of the DTIMOUT option for the transaction.

Modules:

DFHETL

AELB
Explanation:

The executing function has been purged before control could be returned.

System action:

The transaction is marked to be abnormally terminated with abend code AELB.

User response:

Investigate the reason the task was purged. It was purged either by the master terminal operator, or as a result of a deadlock timeout.

If the task was purged by the master terminal operator, this may have been in an attempt to clear the system which appeared to be deadlocked for some reason.

If the task was timed out automatically as a result of the DTIMOUT value being exceeded, this may be due to insufficient main storage being available for the number of tasks in the system. If the amount of main storage cannot be increased then the number of tasks in the system should be reduced to avoid short-on-storage situations. Another possibility would be to increase the value of the DTIMOUT option for the transaction.

Modules:

DFHEGL

AEMA
Explanation:

An error (INVALID or DISASTER response) has occurred on a call to the application (AP) domain when a request for set user exit active could not be serviced.

System action:

The task is abnormally terminated. The domain that detected the original error issues a console message and might provide an exception trace, and depending on the options specified in the dump table, a system dump.

User response:

See the associated console message for further guidance.

Modules:

DFHUEM

AEMB
Explanation:

An error (INVALID or DISASTER response) has occurred on a call to the loader (LD) domain. The domain that detected the original error will have provided an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump (depending on the options in the dump table).

User response:

See the related message from the domain that detected the original error.

Modules:

DFHUEM

AEMP
Explanation:

The task was purged before a set active request to the application (AP) domain was able to complete successfully. The domain that first detected the purged condition may provide an exception trace.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Investigate why the task was purged. This is either as a result of a purge from the master terminal operator via the CEMT transaction, or by the task being timed out after waiting for longer than the DTIMOUT (deadlock timeout) value specified for the transaction.

If the master terminal operator purged the task, this may have been in an attempt to clear the system which appeared to be deadlocked for some reason.

If the task was timed out automatically as a result of the DTIMOUT value being exceeded, this may be due to insufficient main storage being available for the number of tasks in the system. If the amount of main storage cannot be increased, reduce the number of tasks in the system to avoid short-on-storage situations. Another possibility is to increase the value of the DTIMOUT option for the transaction.

Modules:

DFHUEM

AEMQ
Explanation:

The task was purged before an IDENTIFY_PROGRAM request to the loader (LD) domain was able to complete successfully. The domain that first detected the purged condition provides an exception trace.

System action:

The task is abnormally terminated with a CICS transaction dump (depending on the options in the dump table).

User response:

Investigate why the task was purged. This is either as a result of a purge from the master terminal operator via the CEMT transaction, or by the task being timed out after waiting for longer than the DTIMOUT (deadlock timeout) value specified for the transaction.

If the master terminal operator purged the task, this may have been in an attempt to clear the system which appeared to be deadlocked for some reason.

If the task was timed out automatically as a result of the DTIMOUT value being exceeded, this may be due to insufficient main storage being available for the number of tasks in the system. If the amount of main storage cannot be increased, reduce the number of tasks in the system to avoid short-on-storage situations. Another possibility is to increase the value of the DTIMOUT option for the transaction.

Modules:

DFHUEM

AETA
Explanation:

A CICS transaction has issued a non-CICS command via an application "stub" (an expansion of a DFHRMCAL macro). Program DFHERM has determined that the exit has been disabled since the previous DFHRMCAL request was issued from the transaction.

System action:

The task is abnormally terminated with a transaction dump

User response:

Notify your system programmer.

Modules:

DFHERM

AETC
Explanation:

A CICS transaction has issued a non-CICS command via an application "stub" (an expansion of a DFHRMCAL macro). However, the task-related user exit (TRUE) is not known to program manager.

System action:

The task is abnormally terminated with a transaction dump

User response:

Ensure that the TRUE as identified to the DFHRMCAL macro has been correctly defined to CICS.

Modules:

DFHERM

AETF
Explanation:

The task was purged before a request to the storage manager (SM) domain was able to complete successfully. The domain that first detected the purged condition will have provided an exception trace.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Investigate why the task was purged. This is either as a result of a purge from the master terminal operator via the CEMT transaction, or by the task being timed out after waiting for longer than the DTIMOUT (deadlock timeout) value specified for the transaction.

If the master terminal operator purged the task, this may have been in an attempt to clear the system which appeared to be deadlocked for some reason.

If the task was timed out automatically as a result of the DTIMOUT value being exceeded, this may be due to insufficient main storage being available for the number of tasks in the system. If the amount of main storage cannot be increased, reduce the number of tasks in the system to avoid short-on-storage situations. Another possibility is to increase the value of the DTIMOUT option for the transaction.

Modules:

DFHERM

AETG
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the storage manager (SM) domain. The domain that detected the original error will have provided an exception trace, a console message and, possibly, a system dump (depending on the options specified in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

See the related message produced by the domain that detected the original error.

Modules:

DFHERM

AETH
Explanation:

The task was purged before a request to the storage manager (SM) domain was able to complete successfully. The domain that first detected the purged condition will have provided an exception trace.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Investigate why the task was purged. This is either as a result of a purge from the master terminal operator via the CEMT transaction, or by the task being timed out after waiting for longer than the DTIMOUT (deadlock timeout) value specified for the transaction.

If the master terminal operator purged the task, this may have been in an attempt to clear the system which appeared to be deadlocked for some reason.

If the task was timed out automatically as a result of the DTIMOUT value being exceeded, this may be due to insufficient main storage being available for the number of tasks in the system. If the amount of main storage cannot be increased, reduce the number of tasks in the system to avoid short-on-storage situations. Another possibility is to increase the value of the DTIMOUT option for the transaction.

Modules:

DFHERM

AETI
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the storage manager (SM) domain. The domain that detected the original error will have provided an exception trace, a console message and, possibly, a system dump (depending on the options specified in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

See the related message produced by the domain that detected the original error.

Modules:

DFHERM

AETJ
Explanation:

An error (EXCEPTION, DISASTER, INVALID, KERNERROR or PURGED) has occurred on an ADD_LINK call to the recovery manager (RM) domain. For errors other than EXCEPTION, the RM domain provides an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

For all errors, DFHERM provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHERM

AETK
Explanation:

An error (EXCEPTION, DISASTER, INVALID, KERNERROR or PURGED) has occurred on an SET_LINK call to the recovery manager (RM) domain. For errors other than EXCEPTION, the RM domain provides an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

For all errors, DFHERM provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHERM

AETL
Explanation:

An error (EXCEPTION, DISASTER, INVALID, KERNERROR or PURGED) has occurred on an SET_UOW call to the recovery manager (RM) domain. For errors other than EXCEPTION, the RM domain provides an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

For all errors, DFHERM provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHERM

AETM
Explanation:

An error (EXCEPTION, DISASTER, INVALID, KERNERROR, or PURGED) has occurred on an INQUIRE_TRANSACTION call to the transaction manager (XM) domain. For errors other than EXCEPTION, the XM domain provides an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

For all errors, DFHRMSY provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHRMSY

AETN
Explanation:

An EXCEPTION response with an unexpected reason occurred on an INITITIATE_RECOVERY call to recovery manager (RM) domain. DFHRMSY provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHRMSY

AETO
Explanation:

An error (DISASTER, INVALID, KERNERROR, or PURGED) has occurred on an INITIATE_RECOVERY call to the recovery manager (RM) domain. The RM domain provides an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

DFHRMSY also provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHRMSY

AETP
Explanation:

An error (EXCEPTION, DISASTER, INVALID, KERNERROR, or PURGED) has occurred on an TERMINATE_RECOVERY call to recovery manager (RM) domain. For errors other than EXCEPTION, the RM domain provides an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

For all errors, DFHRMSY provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHRMSY

AETQ
Explanation:

An EXCEPTION response with an unexpected reason occurred on an INQUIRE_UOW call to the recovery manager (RM) domain. DFHRMSY provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHRMSY

AETR
Explanation:

An error (DISASTER, INVALID, KERNERROR, or PURGED) has occurred on an INQUIRE_UOW call to the recovery manager (RM) domain. The RM domain provides an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

DFHRMSY also provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHRMSY

AETS
Explanation:

An error (EXCEPTION, DISASTER, INVALID, KERNERROR, or PURGED) has occurred on an INQUIRE_STARTUP call to recovery manager (RM) domain. For errors other than EXCEPTION, the RM domain provides an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

For all errors, DFHRMSY provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHRMSY

AEXU
Explanation:

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.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Refer to abend AEIA for an explanation of how to determine the function code of the CICS command that caused the abend.

It is not possible to set an EXEC CICS HANDLE CONDITION for NOTPOSS.

The system programmer should investigate the cause of the storage overlay.

Modules:

DFHEIDTI, DFHEIQDS, DFHEIQSA, DFHEIQSC, DFHEIQSM, DFHEIQSP DFHEIQST, DFHEIQSX

AEXY
Explanation:

The executing transaction has been purged before control could be returned.

This can arise when the transaction is purged while

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Contact your system programmer to determine why the transaction has been purged.

Modules:

Start of changeDFHACP, DFHBEP, DFHBREX, DFHBRIC, DFHBRMS, DFHBRSP, DFHBRTC, DFHBSTS, DFHBSTZO, DFHD2CC, DFHD2EX1, DFHD2EX2, DFHD2STR, DFHEDCP, DFHEDFP, DFHEDI, DFHEEI, DFHEGL, DFHEICRE, DFHEIDEF, DFHEIDEL, DFHEIINS, DFHEIIC, DFHEIP, DFHEIPA, DFHEIPI, DFHEIPRT, DFHEIPSE, DFHEIPSH, DFHEIQDE, DFHEIQDN, DFHEIQDS, DFHEIQDU, DFHEIQD2, DFHEIQEJ, DFHEIQIR, DFHEIQMS, DFHEIQMT, DFHEIQPF, DFHEIQPI, DFHEIQPN, DFHEIQRQ, DFHEIQSA, DFHEIQSC, DFHEIQSJ, DFHEIQSK, DFHEIQSL, DFHEIQSM, DFHEIQSP, DFHEIQSQ, DFHEIQST, DFHEIQSX, DFHEIQSY, DFHEIQTM, DFHEIQTR, DFHEIQTS, DFHEIQUE, DFHEIQVT, DFHEIQWB, DFHEIQWR, DFHEIUOW, DFHEIWB, DFHEKC, DFHEMS, DFHEOP, DFHEPC, DFHERM, DFHESC, DFHESE, DFHESN, DFHETC, DFHETL, DFHETRX, DFHTACP, DFHTFP, DFHTIEM, DFHUEM, DFHWBTC, DFHXMBR, DFHXTP, DFHZATS, DFHZNCA, DFHZNCE, DFHZTSP, DFHZXQO, DFHZXSTEnd of change

AEXZ
Explanation:

A command has failed due to a serious failure in a CICS component (resource manager).

System action:

The transaction is abnormally terminated with abend code AEXZ. CICS takes a transaction dump, unless module DFHDUIO is not loaded.

User response:

Use the transaction dump to determine the cause of the failure. For further assistance, or if module DFHDUIO is not loaded and no transaction dump is available, contact your system programmer.

Modules:

Start of changeDFHACP, DFHBEP, DFHBREX, DFHBRIC, DFHBRMS, DFHBRSP, DFHBRTC, DFHBSTS, DFHBSTZO, DFHCDKRN, DFHEDCP, DFHEDFP, DFHEDI, DFHEEI, DFHEGL, DFHEIACQ, DFHEICRE, DFHEICRE, DFHEIDEF, DFHEIDEL, DFHEIINS, DFHEIIC, DFHEIP, DFHEIPA, DFHEIPI, DFHEIPRT, DFHEIPSE, DFHEIPSH, DFHEIQDE, DFHEIQDN, DFHEIQDS, DFHEIQDU, DFHEIQD2, DFHEIQEJ, DFHEIQIR, DFHEIQMS, DFHEIQMT, DFHEIQPF, DFHEIQPI, DFHEIQPN, DFHEIQRQ, DFHEIQSA, DFHEIQSC, DFHEIQSJ, DFHEIQSK, DFHEIQSL, DFHEIQSM, DFHEIQSP, DFHEIQSQ, DFHEIQST, DFHEIQSX, DFHEIQSY, DFHEIQTM, DFHEIQTR, DFHEIQTS, DFHEIQUE, DFHEIQVT, DFHEIQWB, DFHEIQWR, DFHEIUOW, DFHEIWB, DFHEKC, DFHEMS, DFHEOP, DFHEPC, DFHESC, DFHESE, DFHESN, DFHETC, DFHETL, DFHETRX, DFHFCFL, DFHSJIN, DFHTACP, DFHTFP, DFHTIEM, DFHUEH, DFHUEM, DFHWBTC, DFHXMBR, DFHXTP, DFHZATS, DFHZNCA, DFHZNCE, DFHZTSP, DFHZXQO, DFHZXSTEnd of change

AEYD
Explanation:

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.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Examine the trace to find the exception trace entry created by DFHEISR and then identify the parameter in error. If the abend is handled, EXEC CICS ASSIGN ASRASTG, ASRAKEY, ASRASPC, and ASRAREGS give additional information about the abend. At the time of the abend, register 2 points to the storage area at fault.

Change one or more of the following:

Modules:

DFHSRP

AEYF
Explanation:

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 on a PUT CONTAINER or a GET CONTAINER command. The error can occur when:

A common cause of this error is specifying the address of a halfword area in the FLENGTH parameter, which expects a fullword area. This error can arise when a program which previously used commareas, which have halfword lengths, has been modified to use containers which have fullword lengths.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Examine the trace to find the entry trace entry created by DFHEISR and then identify the parameter in error. If the abend is handled, EXEC CICS ASSIGN ASRASTG, ASRAKEY, ASRASPC, and ASRAREGS give additional information about the abend. At the time of the abend, register 2 points to the storage area at fault.

You will most likely need to do the following:

You may also need to consider changing one or more of the following:

Modules:

DFHSRP

AEY6
Explanation:

Internal logic error in DFHUEM. This arises when using EXITALL to DISABLE an exit program from all exit points for which it has been enabled. The entire user exit table has been scanned and all associations of the program have been found. But the activation count for the program in its exit program block indicates there should be more associations (for example, the activation count has not been reduced to zero). The user exit table and associated control blocks (EPBs and EPLs) are out of step and have probably been corrupted.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHUEM

AEY8
Explanation:

No DSA was found on the chain while trying to free dynamic storage for an assembler language program using an EXEC CICS command.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Ensure that the DFHEIENT, DFHEISTG, and DFHEIEND macro invocations are correctly positioned and retry. If the error persists, you will need further assistance. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHEIP

AEY9
Explanation:

One of the following:

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Check that the sysid specified and the resource names were correct. If not, notify the system programmer. Either the command (or an application stub) has become corrupted, or the unavailable function needs to be generated (CICS command), ENABLEd (non-CICS command), or exceptionally the non-CICS support has suffered damage and is attempting to withdraw itself from the CICS system.

Modules:

DFHEIP, DFHEEI

AEZA
Explanation:

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.

System action:

The transaction is abnormally terminated.

User response:

Either redefine and install a new definition for the transaction with TASKDATALOC(BELOW), or relink the programs as amode 31.

Modules:

DFHEIP

AEZB
Explanation:

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 linkedited 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.

System action:

The transaction is abnormally terminated.

User response:

Either redefine and install a new definition for the transaction with TASKDATALOC(BELOW), or modify the task related user exit so that it is invoked in AMODE 31.

Modules:

DFHERM

AEZC
Explanation:

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.

System action:

The transaction is abnormally terminated.

User response:

Either redefine and install a new definition for the transaction with TASKDATALOC(BELOW), or relink the program as AMODE 31.

Modules:

DFHAPLI

AEZD
Explanation:

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 autoinstalled. See the CICS Customization Guide and the CICS Resource Definition Guide for more information about program autoinstall.

System action:

The transaction is abnormally terminated. Message DFHAP1226 will show the incompatible program and transaction.

User response:

Redefine and install a new definition either for the transaction with TASKDATAKEY(USER), or for the program with EXECKEY(CICS).

If this abend occurs when running a CICS transaction, a possible cause is that you are not using the CICS-supplied definition for the program. If you are using your own copies of CICS-supplied program definitions, they must be defined as EXECKEY(CICS).

Modules:

DFHAPLI

Start of change
AEZE
Explanation:

CHANGED condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Modules:

DFHEIP

End of change
Start of change
AEZF
Explanation:

PROCESSBUSY condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Modules:

DFHEIP

End of change
Start of change
AEZG
Explanation:

ACTIVITYBUSY condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Modules:

DFHEIP

End of change
Start of change
AEZH
Explanation:

PROCESSERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Modules:

DFHEIP

End of change
Start of change
AEZI
Explanation:

ACTIVITYERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Modules:

DFHEIP

End of change
Start of change
AEZJ
Explanation:

CONTAINERERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Modules:

DFHEIP

End of change
Start of change
AEZK
Explanation:

EVENTERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Modules:

DFHEIP

End of change
Start of change
AEZL
Explanation:

TOKENERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Modules:

DFHEIP

End of change
Start of change
AEZM
Explanation:

NOTFINISHED condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Modules:

DFHEIP

End of change
Start of change
AEZN
Explanation:

POOLERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Modules:

DFHEIP

End of change
Start of change
AEZO
Explanation:

TIMERERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Modules:

DFHEIP

End of change
Start of change
AEZP
Explanation:

SYMBOLERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Modules:

DFHEIP

End of change
Start of change
AEZQ
Explanation:

TEMPLATERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Modules:

DFHEIP

End of change
Start of change
AEZR
Explanation:

NOTSUPERUSER condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Modules:

DFHEIP

End of change
Start of change
AEZS
Explanation:

CSDERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Modules:

DFHEIP

End of change
Start of change
AEZT
Explanation:

DUPRES condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Modules:

DFHEIP

End of change
Start of change
AEZU
Explanation:

RESUNAVAIL condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Modules:

DFHEIP

End of change
Start of change
AEZV
Explanation:

CHANNELERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Modules:

DFHEIP

End of change
Start of change
AEZW
Explanation:

CCSIDERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Modules:

DFHEIP

End of change
Start of change
AEZX
Explanation:

TIMEDOUT condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Modules:

DFHEIP

End of change [[ Contents Previous Page | Next Page Index ]]