ABEND CICS Code AFCU - AFDC

AFCU

Explanation: A program made a file control request against a file that

is being accessed in VSAM RLS mode. The underlying data set is in lost

locks state.

File control requests are not allowed against a data set that is in lost

locks state.

System Action: The task is abnormally terminated with a CICS

transaction dump.

User Response: Recovery from lost locks is normally automatic. See the

CICS Recovery and Restart Guide for a full explanation of lost locks

recovery. You will not be able to issue any file control requests against this data set until all systems that owned locks at the time of the lock structure failure have completed their lost locks recovery.

See the CICS Recovery and Restart Guide for guidance on how to determine

which CICS systems still have lost locks recovery pending, for

information on commands that allow you to find the work that these systems have outstanding, and on commands that allow you to force a system to

immediately complete lost locks recovery. The commands that force immediate completion of lost locks recovery should only be used as a last resort as they may cause loss of data integrity. It is better to allow the automatic recovery procedures to complete normally.

Modules: DFHEIFC, DFHDMPCA

 

AFCV

Explanation: A request made against a file opened in RLS mode was

unable to acquire a record lock. It waited for the lock, but the wait

time exceeded the maximum wait time applicable to that request.

System Action: The task is abnormally terminated with a CICS

transaction dump.

CICS prints message DFHFC0164 and message DFHFC0165 which identify the

transaction or transactions that were immediately in front of this

transaction in the queue for the lock. Normally this transaction or these

transactions are the owners of the lock, although this is not the case

if a chain of requests for the record has built up.

User Response: Retry the transaction.

If the problem recurs, see messages DFHFC0164 and DFHFC0165 to determine

the transaction that is holding the lock. In most cases the problem lies

with the lock owner rather than the transaction that has failed.

Examples of causes of timeouts are as follows:

The transaction that holds the lock has a design error. For example:

- A conversational transaction updates a recoverable record and

then issues a terminal control read. It does not issue syncpoint (and

therefore does not release the lock) until the end user has responded to the terminal control read. It may therefore hold the lock for a considerable period.

- A transaction updates very many records in recoverable files

before issuing syncpoint. You are recommended to keep the number of

updates made within a unit of work small and to issue frequent syncpoints to ensure that locks are released regularly.

The system in which the lock holder is running is experiencing severe

performance degradation. Investigate the reason for the performance

degradation.

 

There is a deadlock between RLS and another resource manager. For

example one transaction may be holding an RLS lock and waiting for a

lock on a transient data queue. The transaction that times out may hold the

lock on the transient data queue and be waiting for the RLS lock. RLS

can detect deadlocks only when all the locks involved in the deadlock are RLS locks. A deadlock such as this can appear to RLS to be a long wait for a lock and is reported as a time out. Examine the design of the transactions to determine whether resource manager deadlocks can occur.

It may be possible for RLS deadlocks to be reported as RLS timeouts

if VSAM does not perform deadlock detection until after the time out

value for the request occurred. For example, assume that DEADLOCK_TIMEOUT in specified as (15,4) in SYS1.PARMLIB. This means that VSAM does not attempt to detect cross-MVS deadlocks until 4 periods of 15 (that is, 60)

seconds have elapsed. If DTIMOUT was not active for the transaction and

the SIT specified FTIMEOUT=30, the RLS request times out after 30 seconds,

before VSAM has attempted to detect cross-MVS deadlocks. Adjust FTIMEOUT,

DTIMOUT, and DEADLOCK_DETECTION to avoid such effects.

Modules: DFHEIFC, DFHDMPCA

 

AFCW

Explanation: The program issued a file control request against a file

opened in RLS mode. VSAM RLS detected that this request would cause a

deadlock.

This transaction is abended in order to break the deadlock chain.

System Action: The task is abnormally terminated with a CICS

transaction dump.

CICS prints message DFHFC0166 and message DFHFC0167 which identify the

other transactions in the deadlock chain.

User Response: Retry the transaction.

Examine the logic of all the programs involved in the deadlock chain to

determine whether they could be improved to avoid possible sources of

deadlock. See the CICS Application Programming Guide for guidance on how to write programs that avoid deadlocks.

Modules: DFHEIFC, DFHDMPCA

 

AFCY

Explanation: The transaction issued a file request resulting in a call

to the main file control program (DFHFCFR). During the processing of the

request the transaction was purged (that is, was the subject of an explicit PURGE or FORCEPURGE request, was timed out, or was selected by CICS for

termination in an attempt to alleviate an SOS condition). A "purged" response was returned from DFHFCFR to its caller.

System Action: The task is abnormally terminated with a CICS

transaction dump.

Exception trace entries are made between the point at which the purge is

detected and the issuing of the abend.

User Response: In some instances, for example if the transaction was

explicitly purged, no further action is necessary.

Otherwise examine the exception trace and the transaction dump to

identify the point at which the purge occurred.

Modules: DFHDMPCA, DFHEIFC

 

AFCZ

Explanation: The transaction issued a file request resulting in a call

to the main file control program (DFHFCFR). A "disastrous error"

response was returned from DFHFCFR to its caller.

System Action: At the time the error is detected, CICS writes a message

to the console, records an exception trace entry, and takes a system

dump. The trace and dump identify the point of error.

Subsequently, the task is abnormally terminated with a CICS transaction

dump.

User Response: The system programmer should use the trace and dumps to

determine what the error is, and why it has occurred.

Modules: DFHDMPCA, DFHEIFC

 

AFC0

Explanation: An attempt has been made to update a file after file

control restart failed.

System Action: The transaction is abnormally terminated with a

transaction dump.

User Response: Determine the cause of the failure in file control

restart. Restart CICS.

Modules: DFHEIFC, DFHDMPCA

 

AFC2

Explanation: DFHFCU issued a call to DFHFCFS to open a file. A

disastrous error was returned from DFHFCFS.

System Action: The task is abnormally terminated with a CICS

transaction dump.

At the time the disastrous error is detected, CICS writes a message to

the console, records an exception trace entry and takes a system dump.

CICS processing continues.

User Response: The system programmer should examine the trace, the

system dump and any related CICS messages to identify the cause of the

error.

Module: DFHFCU

 

AFC7

Explanation: The CICS definition file (CSD) manager (DFHDMPCA) issued a

request to DFHFCFS to enable, open or close the DFHCSD file. A "disastrous

error" response was returned from DFHFCFS to DFHDMPCA.

System Action: The task is abnormally terminated with a CICS

transaction dump.

At the time the disastrous error is detected, CICS writes a message to

the console, records an exception trace entry and takes a system dump.

CICS processing continues.

User Response: The system programmer should examine the trace, the

system dump and any related CICS messages to identify the cause of the

error.

Module: DFHDMPCA

 

AFDA

Explanation: An attempt was made to attach a transaction specifying

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

internally attached by CICS.

DFHFCQT is for use by CICS system transactions CFQS and CFQR. These

provide 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: The transaction is abnormally terminated. CICS

processing continues.

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

CFQS or CFQR, or why a transaction definition specified DFHFCQT as the

program to be given control.

Module: DFHFCQT

 

AFDB

Explanation: An attempt was made by CICS to internally attach a

transaction specifying DFHFCQT as the program to be given control, and

the transaction id was other than CFQS or CFQR.

DFHFCQT is for use by CICS system transactions CFQS and CFQR. These

provide 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: The transaction is abnormally terminated with a CICS

transaction dump. CICS processing continues but it is probable that VSAM

RLS data set quiesce support has been lost.

User Response: Restart CICS. If the problem reoccurs, 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

 

AFDC

Explanation: CICS system transaction CFQS 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.

CFQS provides support for the initiation of VSAM RLS data set quiesce

and unquiesce operations.

System Action: CFQS is abnormally terminated with a CICS transaction

dump. CFQS is reattached and CICS processing continues.

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

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

VSAM RLS data set quiesce initiation support is lost. If this support is

required, CICS must be restarted.

If it is not possible to restore VSAM RLS quiesce initiation 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