Abend codes AFxx

AFCB
Explanation:

Module DFHEIFC issued a resource level security check (RSLC) request to module DFHXSRC and received a response other than OK or EXCEPTION.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

Examine the trace to find the exception trace entry created by DFHXSRC at the time of the error. Use this trace entry to determine the cause of the return code from DFHXSRC.

Module(s):

DFHEIFC

AFCC
Explanation:

An internal logic error was detected when calling the file control request processing module DFHFCFR. Either DFHFCFR returned an INVALID response to its caller indicating an error in the caller's parameter list, or DFHFCFR passed back a return code that was not recognized by its caller.

System action:

The transaction is abnormally terminated with a 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.

Module(s):

DFHEIFC, DFHDMPCA

AFCE
Explanation:

A GETMAIN for FFLE storage has failed.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

Retry the failed transaction.

Module(s):

DFHEIFC

AFCF
Explanation:

A deadlock has been detected between two or more tasks issuing file control requests.

System action:

The task that would have entered deadlock is abended with a CICS transaction dump.

User response:

Examine this transaction and other transactions in the system that update the same files to find the cause of the deadlock, then correct the error.

When transactions update several files within the same unit of work, all transactions should update these files in the same order. A transaction that abends AFCF may be retried by specifying RESTART(YES) in the transaction definition and by coding a suitable DFHREST program.

Modules:

DFHEIFC, DFHDMPCA

AFCG
Explanation:

A transaction has issued a sequence of file control requests that would cause the file to deadlock itself. This response arises for different reasons depending upon the file type.

If the file is being accessed in non-RLS mode, the response is caused by the transaction making conflicting requests against the same CI. For example, if the file is being accessed using LSR, a self deadlock will arise when an attempt is made to read a record that is in the same CI as a record that is the subject of a READ UPDATE or WRITE MASSINSERT request issued by the same transaction.

If the file is accessed in RLS mode there is no CI locking, but self deadlock responses can still arise. They are caused by sequences of requests that are either logically meaningless or which cannot be performed by VSAM RLS.

With VSAM RLS the most likely causes of this abend are as follows:

If the file is used to access a coupling facility data table, then self deadlock responses are caused by sequences of requests that are either logically meaningless or which cannot be performed by coupling facility data tables support.

For coupling facility data tables, the most likely cause of this abend is as follows:

System action:

The task that would have entered deadlock is abended with a CICS transaction dump.

User response:

Examine the previous requests made by this transaction against this file to identify the cause of the deadlock, then correct the error. In some cases (particularly when the file is being accessed in RLS mode or is using a coupling facility data table) this abend may indicate a programming error in the program that issued the file control requests.

Modules:

DFHEIFC, DFHDMPCA

AFCH
Explanation:

The transaction has issued a request for a remote shared data table for which it has an active browse, but in the meantime the table has been disabled or closed by the owning CICS system, or the owning CICS system has failed.

System action:

The requesting transaction abends with a transaction dump.

CICS continues normally.

User response:

In the application owning region, take whatever action normally follows the issue of a FORCE request in, or the failure of, the file owning CICS system.

See the CICS Shared Data Tables Guide for further guidance.

Modules:

DFHEIFC

Start of change
AFCI
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, the transaction 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.

System action:

A CICS transaction dump is issued with abend code AFCI. A purged response is returned from DFHFCFR to its caller. The transaction issuing the file control request will eventually issue an AFCY abend with a further transaction dump.

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.

Module:

DFHFCFR

End of change
AFCJ
Explanation:

DFHFCU issued a call to DFHFCFS to open a file. A purged error was returned from DFHFCFS because the task has been waiting for a resource longer than the DTIMEOUT interval specified for the CSFU transaction.

System action:

The task is abnormally terminated with a CICS transaction dump. CICS processing continues.

User response:

Examine the dump to determine the cause of the error. A system dump can be produced by adding the appropriate dump table entry using the CEMT SET TRDUMPCODE command.

Modules:

DFHFCU

AFCK
Explanation:

The transaction issued a file update request (READ UPDATE, WRITE or DELETE) against an RLS mode data set for which a DFSMSdss non-BWO backup was in progress.

System action:

The transaction is abnormally terminated with a CICS transaction dump. CICS processing continues.

User response:

All new file update requests are prohibited when a non-BWO backup is in progress for an RLS mode data set. This restriction is automatically lifted when the backup completes. (A non-BWO backup is any type of backup operation other than a Backup While Open backup.) When the backup has completed, retry the transaction.

Modules:

DFHDMPCA, DFHEIFC

Start of changeAFCLEnd of change
Start of change
Explanation:

During the loading of a Shared Data Table by the CFTL transaction, a call to the CICS Transaction Manager has returned a response (such as DISASTER) after which normal processing could not continue.

End of change
Start of change
System action:

Message DFHFC0949 is issued. Loading of the data table is terminated and CFTL abends.

End of change
Start of change
User response:

Refer to the description of the message for further information and guidance.

End of change
Modules:

Start of changeDFHDTLXEnd of change

AFCM
Explanation:

During the loading of a data table by the CFTL transaction, an abend was detected, or a domain call returned a response (such as DISASTER) after which normal processing could not continue.

System action:

A message is issued (one of DFHFC0945, DFHFC0946, or DFHFC0947). Loading of the data table is terminated and CFTL abends.

User response:

If this abend is produced as a result of an abend during loading, message DFHFC0945 is issued. If it is a result of a domain call failure, depending on which domain the failure was returned by, one of the messages DFHFC0946 or DFHFC0947 is issued. Refer to the description of the message for further information and guidance.

Modules:

DFHDTLX

AFCN
Explanation:

The transaction issued a file request that caused file control to attempt to create a journal record but the record was too large for the journal buffer to accommodate. This indicates that a journal referenced in the file definition is using an MVS logstream, which in turn, is using a coupling facility structure which has been defined with a MAXBUFSIZE parameter less than the recommended 64000.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Redefine the coupling facility structure that the logstream is using with a MAXBUFSIZE parameter of 64000. The journal in error can be the forward recovery log or the journal used for auto-archiving. If the module that detected the error is DFHDMPCA, the error is associated with a journal referenced in the definition of the CSD (DFHCSD).

Modules:

DFHDMPCA, DFHEIFC

Start of change
AFCO
Explanation:

An attempt was made to attach a transaction specifying DFHDTLX as the program to be given control, but the transaction was not internally attached by CICS.

DFHDTLX is for use by CICS system transaction CFTL. This loads a Shared Data Table.

System action:

The transaction is abnormally terminated. CICS processing continues.

User response:

Establish why an attempt was made to attach CFTL illegally, or why a transaction definition specified DFHDTLX as the program to be given control.

Modules:

DFHDTLX

End of change
AFCR
Explanation:

The program issued a file control request against a file opened in RLS mode. While executing this request, CICS detected that the SMSVSAM server address space had failed.

System action:

The task is abnormally terminated with a CICS transaction dump.

CICS disables all further RLS accesses and initiates error recovery.

User response:

Retry the transaction when the server is available again

If the SMSVSAM server fails, it should normally automatically restart itself as quickly as possible. If this does not happen, consult the VSAM documentation which provides further guidance on debugging problems in the SMSVSAM server.

Modules:

DFHEIFC, DFHDMPCA

AFCS
Explanation:

The program issued a file control request against a file opened in RLS mode. VSAM was unable to perform this request because the SMSVSAM server address space was inactive.

However, if an offsite restart is being performed (that is, OFFSITE=YES was specified as a system initialization override), this transaction abend is also issued even if the SMSVSAM server address space is active. This is because RLS access is not allowed during an offsite restart for any RLS file control requests other than those issued by transactions which have been attached by CICS to perform RLS recovery work.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Retry the transaction when the server is available again.

If the SMSVSAM server fails, it should normally automatically restart itself as quickly as possible. If this does not happen, consult the VSAM documentation which provides further guidance on debugging problems in the SMSVSAM server.

If an offsite restart is being performed, retry the transaction after RLS recovery has been completed when RLS access by user transactions is allowed again.

Modules:

DFHEIFC, DFHDMPCA

AFCT
Explanation:

The program has made a file control request against a file opened in RLS mode. The SMSVSAM server has been recycled since an earlier RLS request from the same unit of work. The same unit of work cannot issue requests against two different instances of the SMSVSAM server. Note that this abend will occur even if the earlier request was not successful.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Resubmit the transaction.

Modules:

DFHEIFC, DFHDMPCA

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(s) DFHFC0165 or DFHFC0175 which identify the transaction(s) or Transactional VSAM unit(s) of recovery that were immediately in front of this transaction in the queue for the lock. Normally these transaction(s) or Transactional VSAM unit(s) of recovery 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 or DFHFC0175 to determine the transaction or Transactional VSAM unit of recovery that is holding the lock. In most cases the problem lies with the lock owner rather than the transaction that has failed.

Examples of reasons why CICS transactions may cause a timeout:

DFHFC0175 messages identify Transactional VSAM units of recovery owning an RLS lock. If a Transactional VSAM application is the lock owner it should be investigated to determine why it is holding the lock. Some of the above considerations will be similar for Transactional VSAM applications.

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(s) DFHFC0167 or DFHFC0177 which identify the other transactions or Transactional VSAM units of recovery 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.

Start of changeA transaction dump with abend code AFCI is taken when the purged response is detected by DFHFCFR.End of change

User response:

In some instances, for example if the transaction was explicitly purged, no further action is necessary.

Start of changeOtherwise examine the exception trace and the AFCI or AFCY transaction dumps to identify the point at which the purge occurred.End of change

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.

Modules:

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.

Modules:

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.

Modules:

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. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

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. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHFCQT

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. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

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.

Modules:

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.

Modules:

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.

Modules:

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

[[ Contents Previous Page | Next Page Index ]]