Abend Code CICS da AEC1 a AEZQ

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.

Modules: 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

 

AEC3

Explanation:  An unsuccessful attempt has been made to call VS COBOL II

to initialize a thread (for the first VS COBOL II program in a CICS

transaction).

System Action:  The transaction is abnormally terminated. The program is

disabled.

User Response:  Check your library setup to ensure that all of the VS

COBOL II interface modules are present.

Module:  DFHAPLI

 

AEC4

Explanation:  An unsuccessful attempt has been made to call VS COBOL II

to initialize a run-unit (for any VS COBOL II program in a CICS

transaction).

System Action:  The transaction is abnormally terminated. The program is

disabled.

User Response:  Check your library setup to ensure that all of the VS

COBOL II interface modules are present.

Module:  DFHAPLI

 

AEC5

Explanation:  An unexpected error has been encountered by C/370 during

the THREAD INITIALIZATION phase while attempting to execute a C language

program.

System Action:  The return code received from C/370 is placed into the

field EIBRESP2; then the transaction is abnormally terminated. The

program is disabled.

User Response:  Refer to the error message(s) provided by C/370 to

determine the cause of the problem.

Module:  DFHAPLI

 

 

 

AEC6

Explanation:  An unexpected error has been encountered by C/370 during

the RUNUNIT INITIALIZATION phase while attempting to execute a C language

program.

System Action:  The return code received from C/370 is placed into the

field EIBRESP2; then the transaction is abnormally terminated. The

program is disabled.

User Response:  Refer to the error message(s) provided by C/370 to

determine the cause of the problem.

Module:  DFHAPLI

 

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.

Module:  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.

Module:  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.

Module:  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.

Module:  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 Part 4 of the CICS Problem Determination Guide for guidance

on how to proceed.

Module:  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.

Module:  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.

Module:  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.

Module:  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.

Module:  DFHEDFX

 

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.

Module:  DFHEDFX

 

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.

Module:  DFHEDFX

 

AED1

Explanation:  This abend is produced as a result of either:

An attempt to use the execution diagnostic facility (EDF) on an

unsupported terminal.

Using the temporary storage browse transaction (CEBR) on an unsupported device, or    An attempt to initiate the temporary storage browse transaction

(CEBR) with a non-terminal principal facility.

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.

Module:  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.

Module:  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 Part 4 of the CICS Problem

Determination Guide for guidance on how to proceed.

Module:  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. You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module:  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. You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module:  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. You need further assistance

from IBM to resolve this problem. See Part 4 of the CICS Problem Determination

Guide for guidance on how to proceed.

Module:  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 Part 4 of the CICS Problem Determination Guide for guidance

on how to proceed.

Module:  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.

Module:  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 AEZQ.

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.

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.

Module:  DFHEIP

 

AEID

Explanation:  EOF 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.

Module:  DFHEIP

 

AEIE

Explanation:  EODS 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.

Module:  DFHEIP

 

AEIG

Explanation:  INBFMH 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.

Module:  DFHEIP

 

AEIH

Explanation:  ENDINPT 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.

Module:  DFHEIP

 

AEII

Explanation:  NONVAL 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.

Module:  DFHEIP

 

AEIJ

Explanation:  NOSTART 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.

Module:  DFHEIP

 

AEIK

Explanation:  TERMIDERR 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.

Module:  DFHEIP

 

AEIL

Explanation:  FILENOTFOUND 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.

Module:  DFHEIP

 

 

 

 

 

 

AEIM

Explanation:  NOTFND 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.

Module:  DFHEIP

 

AEIN

Explanation:  DUPREC 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.

Module:  DFHEIP

 

AEIO

Explanation:  DUPKEY 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.

Module:  DFHEIP

 

AEIP

Explanation:  INVREQ 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.

Module:  DFHEIP

 

AEIQ

Explanation:  IOERR 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.

Module:  DFHEIP

 

AEIR

Explanation:  NOSPACE 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.

Module:  DFHEIP

 

 

 

 

 

 

AEIS

Explanation:  NOTOPEN 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.

Module:  DFHEIP

 

AEIT

Explanation:  ENDFILE 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.

Module:  DFHEIP

 

AEIU

Explanation:  ILLOGIC 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.

Module:  DFHEIP

 

AEIV

Explanation:  LENGERR 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.

Module:  DFHEIP

 

AEIW

Explanation:  QZERO 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.

Module:  DFHEIP

 

AEIZ

Explanation:  ITEMERR 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.

Module:  DFHEIP

 

 

 

 

 

 

AEI0

Explanation:  PGMIDERR 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.

Module:  DFHEIP

 

AEI1

Explanation:  TRANSIDERR 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.

Module:  DFHEIP

 

AEI2

Explanation:  ENDDATA 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.

Module:  DFHEIP

 

AEI3

Explanation:  INVTSREQ 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.

Module:  DFHEIP

 

AEI4

Explanation:  EXPIRED 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.

Module:  DFHEIP

 

AEI8

Explanation:  TSIOERR 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.

Module:  DFHEIP

 

 

 

 

 

 

AEI9

Explanation:  MAPFAIL 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.

Module:  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.

Module:  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.

Module:  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.

Module:  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.

Module:  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.

Module:  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

Module:  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.

Module:  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.

Module:  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.

Module:  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.

Module:  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.

Module:  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.

Module:  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 Part 4 of the CICS Problem Determination Guide for guidance

on how to proceed.

Module:  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 Part 4 of the CICS Problem Determination Guide for guidance

on how to proceed.

Module:  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 Part 4 of the CICS Problem Determination Guide for guidance

on how to proceed.

Module:  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 Part 4 of the CICS Problem Determination Guide for guidance

on how to proceed.

Module:  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 Part 4 of the CICS Problem Determination Guide for guidance

on how to proceed.

Module:  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 Part 4 of the CICS Problem Determination Guide for guidance

on how to proceed.

Module:  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 Part 4 of the CICS Problem Determination Guide for guidance

on how to proceed.

Module:  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 Part 4 of the CICS Problem Determination Guide for guidance

on how to proceed.

Module:  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 Part 4 of the CICS Problem Determination Guide for guidance

on how to proceed.

Module:  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 Part 4 of the CICS Problem Determination Guide for guidance

on how to proceed.

Module:  DFHRMSY

 

AEXC

Explanation:  RESIDERR 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.

Module:  DFHEIP

 

AEXF

Explanation:  ESCERROR 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.

Module:  DFHEIP

 

AEXG

Explanation:  UOWLNOTFOUND 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.

Module:  DFHEIP

AEXI

Explanation:  TERMERR 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.

Module:  DFHEIP

 

AEXJ

Explanation:  ROLLEDBACK 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.

Module:  DFHEIP

 

AEXK

Explanation:  END 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.

Module:  DFHEIP

 

AEXL

Explanation:  DISABLED 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.

Module:  DFHEIP

 

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

 

 

 

 

 

 

 

 

 

AEXV

Explanation:  VOLIDERR 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.

Module:  DFHEIP

 

AEXW

Explanation:  SUPPRESSED 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.

Module:  DFHEIP

 

AEXX

Explanation:  TASKIDERR 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.

Module:  DFHEIP

 

AEXY

Explanation:  The executing transaction has been purged before control

could be returned.

This can arise when the transaction is purged while

   A CICS command was being processed

   The transaction was waiting to be dispatched

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: DFHACP, DFHBEP, DFHBREX, DFHBRIC, DFHBRMS, DFHBRSP, DFHBRTC,

DFHBSTS, DFHBSTZO, DFHD2CC, DFHD2EX1, DFHD2EX2,

DFHD2STR, DFHEDCP, DFHEDFP, DFHEDI, DFHEEI, DFHEGL, DFHEICRE, DFHEIDEF,

DFHEIDEL, DFHEIINS, DFHEIIC, DFHEIP, DFHEIPA,

DFHEIPRT, DFHEIPSE, DFHEIPSH, DFHEIQDE, DFHEIQDN, DFHEIQDS, DFHEIQDU,

DFHEIQD2, DFHEIQIR, DFHEIQMS, DFHEIQMT, DFHEIQPF,

DFHEIQPN, DFHEIQRQ, DFHEIQSA, DFHEIQSC, DFHEIQSJ, DFHEIQSK, DFHEIQSL,

DFHEIQSM, DFHEIQSP, DFHEIQSQ, DFHEIQST, DFHEIQSX,

DFHEIQTM, DFHEIQTR, DFHEIQTS, DFHEIQUE, DFHEIQVT, DFHEIUOW, DFHEKC,

DFHEMS, DFHEOP, DFHEPC, DFHERM, DFHESC, DFHESE,

DFHESN, DFHETC, DFHETL, DFHETRX, DFHPCPC2, DFHTACP, DFHTFP, DFHTIEM,

DFHUEM, DFHWBTC, DFHXMBR, DFHXTP, DFHZATS, DFHZNCA,

DFHZNCE, DFHZTSP, DFHZXQO, DFHZXST

 

 

 

 

 

 

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: DFHACP, DFHBEP, DFHBREX, DFHBRIC, DFHBRMS, DFHBRSP, DFHBRTC,

DFHBSTS, DFHBSTZO, DFHCDKRN, DFHEDCP, DFHEDFP,

 

DFHEDI, DFHEEI, DFHEGL, DFHEIACQ, DFHEICRE, DFHEICRE, DFHEIDEF,

DFHEIDEL, DFHEIINS, DFHEIIC, DFHEIP, DFHEIPA, DFHEIPRT,

 

DFHEIPSE, DFHEIPSH, DFHEIQDE, DFHEIQDN, DFHEIQDS, DFHEIQDU, DFHEIQD2,

DFHEIQIR, DFHEIQMS, DFHEIQMT, DFHEIQPF, DFHEIQPN,

 

DFHEIQRQ, DFHEIQSA, DFHEIQSC, DFHEIQSJ, DFHEIQSK, DFHEIQSL, DFHEIQSM,

DFHEIQSP, DFHEIQSQ, DFHEIQST, DFHEIQSX, DFHEIQSY,

 

DFHEIQTM, DFHEIQTR, DFHEIQTS, DFHEIQUE, DFHEIQVT, DFHEIUOW, DFHEKC,

DFHEMS, DFHEOP, DFHEPC, DFHESC, DFHESE, DFHESN,

 

DFHETC, DFHETL, DFHETRX, DFHFCFL, DFHPCPC2, DFHSJIN, DFHTACP, DFHTFP,

DFHTIEM, DFHUEH, DFHUEM, DFHWBTC, DFHXMBR, DFHXTP,

 

DFHZATS, DFHZNCA, DFHZNCE, DFHZTSP, DFHZXQO, DFHZXST

 

AEX0

Explanation:  TCIDERR 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.

Module:  DFHEIP

 

AEX1

Explanation:  DSNNOTFOUND 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.

Module:  DFHEIP

 

 

 

AEX2

Explanation:  LOADING 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.

Module:  DFHEIP

 

AEX3

Explanation:  MODELIDERR 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.

Module:  DFHEIP

 

AEX4

Explanation:  UOWNOTFOUND 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.

Module:  DFHEIP

 

AEX5

Explanation:  PARTNERIDERR 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.

Module:  DFHEIP

 

AEX6

Explanation:  PROFILEIDERR 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.

Module:  DFHEIP

 

AEX7

Explanation:  NETNAMEIDERR 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.

Module:  DFHEIP

 

 

 

 

 

 

AEX8

Explanation:  LOCKED 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.

Module:  DFHEIP

 

AEX9

Explanation:  RECORDBUSY 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.

Module:  DFHEIP

 

AEYA

Explanation:  INVERRTERM 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.

Module:  DFHEIP

 

AEYB

Explanation:  INVMPSZ 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.

Module:  DFHEIP

 

AEYC

Explanation:  IGREQID 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.

Module:  DFHEIP

 

 

 

 

 

 

 

 

 

 

 

 

 

 

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 additionalinformation 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:

   Correct the code in error in the transaction issuing the EXEC CICS

command in order to supply a valid storage area.

   If storage protection is active, change the EXECKEY on the CEDA

definition for the program that issued the EXEC CICS command from USER

to CICS.

   If storage protection is active, change the TASKDATAKEY attributes on

the transaction definition from CICS to USER.

   If transaction isolation is active, change the ISOLATE attribute on

the transaction definition from YES to NO.

Module:  DFHSRP

 

AEYE

Explanation:  INVLDC 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.

Module:  DFHEIP

 

AEYG

Explanation:  JIDERR 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.

Module:  DFHEIP

 

AEYH

Explanation:  QIDERR 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.

Module:  DFHEIP

 

 

 

 

 

 

AEYJ

Explanation:  DSSTAT 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.

Module:  DFHEIP

 

AEYK

Explanation:  SELNERR 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.

Module:  DFHEIP

 

AEYL

Explanation:  FUNCERR 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.

Module:  DFHEIP

 

AEYM

Explanation:  UNEXPIN 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.

Module:  DFHEIP

 

AEYN

Explanation:  NOPASSBKRD 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.

Module:  DFHEIP

 

AEYO

Explanation:  NOPASSBKWR 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.

Module:  DFHEIP

 

 

 

 

 

 

AEYP

Explanation:  SEGIDERR 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.

Module:  DFHEIP

 

AEYQ

Explanation:  SYSIDERR 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.

Module:  DFHEIP

 

AEYR

Explanation:  ISCINVREQ 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.

Module:  DFHEIP

 

AEYT

Explanation:  ENVDEFERR 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.

Module:  DFHEIP

 

AEYU

Explanation:  IGREQCD 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.

Module:  DFHEIP

 

AEYV

Explanation:  SESSIONERR 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.

Module:  DFHEIP

 

 

 

 

 

 

AEYX

Explanation:  USERIDERR 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.

Module:  DFHEIP

 

AEYY

Explanation:  NOTALLOC 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.

Module:  DFHEIP

 

AEYZ

Explanation:  CBIDERR 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.

Module:  DFHEIP

 

AEY0

Explanation:  INVEXITREQ 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.

Module:  DFHEIP

 

AEY1

Explanation:  INVPARTNSET 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.

Module:  DFHEIP

 

AEY2

Explanation:  INVPARTN 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.

Module:  DFHEIP

 

 

 

 

 

 

AEY3

Explanation:  PARTNFAIL 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.

Module:  DFHEIP

 

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 Part 4 of the CICS Problem Determination Guide for guidance

on how to proceed.

Module:  DFHUEM

 

AEY7

Explanation:  NOTAUTH 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.

Module:  DFHEIP

 

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. You need further assistance from IBM to resolve

this problem. See Part 4 of the CICS Problem Determination Guide for

guidance on how to proceed.

Module:  DFHEIP

 

 

 

 

 

 

 

 

 

 

AEY9

Explanation:  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.

   An attempt has been made to use remote resources, but ISC is not

supported.

   An EXEC CICS command contains an invalid AID or CONDITION identifier.

This indicates that the EXEC CICS command has become corrupted.

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.

Module:  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.

Module:  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.

Module:  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.

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

Module:  DFHAPLI

 

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.

Module:  DFHEIP

 

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.

Module:  DFHEIP

 

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.

Module:  DFHEIP

 

 

 

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.

Module:  DFHEIP

 

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.

Module:  DFHEIP

 

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.

Module:  DFHEIP

 

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.

Module:  DFHEIP

 

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.

Module:  DFHEIP

 

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.

Module:  DFHEIP

 

 

 

 

 

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.

Module:  DFHEIP

 

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.

Module:  DFHEIP

 

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.

Module:  DFHEIP

 

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.

Module:  DFHEIP