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.
If a task times out while waiting for a lock on a record in a coupling facility data table, CICS will issue message DFHFC7130 identifying the key of the locked record and the system and unit of work that owns the lock.
A transaction dump with abend code AFCI is taken when the purged response is detected by DFHFCFR.
User response
In some instances, for example if the transaction was explicitly purged, no further action is necessary.
If using a coupling facility data table, look for any relevant DFHFC7130 messages.
Otherwise examine the exception trace and the AFCI/AFCY transaction dumps to identify the point at which the purge occurred.