CICS Abend Code da AFDD a AICJ

 

 

 

AFDD

Explanation: CICS system transaction CFQR has failed due to a serious

error. An attempt will be made to reattach the transaction. CICS

messages should indicate the cause of the error.

CFQR provides support for VSAM RLS data set quiesce and unquiesce

operations, DFSMSdss BWO and non-BWO backups, and certain other data set

related operations.

System Action: CFQR is abnormally terminated with a CICS transaction

dump. CFQR is reattached and CICS processing continues.

User Response: Check Transient Data Queue CSFL for message DFHFC6028,

indicating that the reattach of CFQR was successful. If the reattach fails,

VSAM RLS data set quiesce support is lost. If this happens, CICS must be

restarted.

If it is not possible to restore VSAM RLS quiesce support, a more severe

error is indicated. In this case, you will need assistance from IBM. 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: DFHFCQT

 

AFDE

Explanation: An attempt was made to attach a transaction specifying

DFHFCRD as the program to be given control, but the transaction was not

internally attached by CICS.

DFHFCRD is for use by CICS system transaction CSFR. This provides

support for error recovery after a failure of the SMSVSAM server.

System Action: The transaction is abnormally terminated. CICS

processing continues.

User Response: Establish why an attempt was made to illegally attach

CSFR, or why a transaction definition specified DFHFCRD as the program

to be given control.

Module: DFHFCRD

 

AFDF

Explanation: An attempt was made to attach a transaction specifying

DFHFCOR as the program to be given control, but the transaction was not

internally attached by CICS.

DFHFCOR is for use by CICS system transaction CFOR. This provides part

of the RLS offsite recovery support.

System Action: The transaction is abnormally terminated. CICS

processing continues.

User Response: Establish why an attempt was made to illegally attach

CFOR, or why a transaction definition specified DFHFCOR as the program

to be given control.

Module: DFHFCOR

 

 

 

 

 

 

 

 

AFDG

Explanation: CICS system transaction CFOR has failed due to a serious

error. CICS messages should indicate the cause of the error.

DFHFCOR provides part of the RLS offsite recovery support.

This abend indicates that this CICS system has completed its RLS offsite

recovery, but an error occurred either in attempting to issue message

DFHFC0575D which reports this fact, or in attempting to process the

reply to message DFHFC0575D.

System Action: CFOR is abnormally terminated with a CICS transaction

dump. CICS processing continues.

User Response: If you are using an automated procedure to check for and

reply to message DFHFC0575D, then you should shut this CICS down and

restart it specifying OFFSITE=YES again. If you are using manual

procedures to check for completion of all RLS offsite recovery and to

reply to message DFHFC0575D then you can "tick" this CICS off the list of systems which have completed their recovery, but you must ensure that it is not restarted with OFFSITE=NO until all other CICS systems have completed their RLS offsite recovery. Also note that until the system is restarted, RLS access will not be allowed by this system.

Module: DFHFCOR

 

AFDH

Explanation: VSAM has returned a response indicating that the RLS lock

structure in the coupling facility is full. VSAM RLS is unable to create

any new locks.

This abend code is usually issued from various CICS systems residing

within the same sysplex.

System Action: The transaction which issued the VSAM RLS request is

abnormally terminated with a CICS transaction dump. CICS processing

continues.

User Response: Allocate a larger VSAM RLS lock structure and rebuild

the RLS structure into the new larger structure. See OS/390 MVS Setting

up a Sysplex, (GC28-1779) and DFSMS/MVS DFSMSdfp Storage Administration

Reference, (SC26-4920) for further details on creating RLS lock

structures and rebuilding lock structures.

Modules: DFHEIFC, DFHDMPCA

 

AGMA

Explanation: An attempt to initiate the good morning message

transaction was made without specifying a termid for it to be displayed.

System Action: The transaction is abnormally terminated with a CICS

transaction dump.

User Response: Use the dump to determine how the attempt to start the

transaction was made. Ensure that no EXEC CICS STARTs are made for the

good morning message transaction where no termid is specified.

Module: DFHGMM

 

 

 

 

 

 

 

AICA

Explanation: A task has been executing for longer than the runaway time

interval (defined by the ICVR operand on the system initialization table

macro,DFHSIT) without giving up control. The runaway task condition indicates a possible loop in the application.

System Action: The task is terminated with an AICA transaction dump.

User Response: See the CICS Problem Determination Guide for guidance on

dealing with loops.

Module: DFHSRP

 

AICB

Explanation: A RETRIEVE WAIT request has been reissued in system shutdown.

System Action: The task is abnormally terminated with a CICS

transaction dump.

User Response: None

Module: DFHICP

 

AICC

Explanation: An incorrect response was returned from a timer (TI)

domain request.

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.

Modules: DFHTAJP, DFHICP

 

AICD

Explanation: A incorrect response was returned from a kernel (KE)

domain request.

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

 

AICE

Explanation: An incorrect response was returned from a dispatcher (DS)

domain request (other than AICG).

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

 

 

 

 

 

 

AICF

Explanation: An incorrect response was returned from a transaction

manager (TM) domain request.

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

 

AICG

Explanation: A PURGED response was returned from a dispatcher domain

(DS) request, with a reason code of TASK_CANCEL. TASK_CANCEL was returned as the transaction had been explicitly cancelled.

System Action: The task is abnormally terminated with a CICS

transaction dump.

User Response: Notify your system programmer to determine why the task

has been purged.

Module: DFHICP

 

AICH

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: DFHICP, DFHEIIC

 

AICJ

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