IBM Mainframe Forum

How to solve AFCY abends

Once was enough.......
Did you bother to look the abend up?
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.
How to solve, do not PURGE or FORCEPURGE the transaction and make sure that you do not run SOS.
Need more information? Then please supply more information.

Thanks for yr reply .
One of the file caused this problem during peak hr txns .
How to change the properties of that file to handle large volume of file read/update requests.
IS ci size of that file need to be changed .
For e.g the file was defined with 1000,500 and multi volume , how to fine tune the properties of that file .

vanathiravi wrote:One of the file caused this problem during peak hr txns.

Why was the transaction PURGEd or FORCEPURGEd?

Hello,

I suspect there is a code issue as much as there is a problem with "that file". It may be worth a look at control interval issues, but i've been more successful improving inefficient code. Do you know how many ci/ca splits are happening?

If you post the DEFINE for the file in question and the definition of any alternate index entries, we may be able to see something.

Do you have or can you get some statistics on what activity is going on against the file when the resource shortage(s) occur? Is the problem "window" caused by one or a few transactions or does the problem include many transaction id's?

Here is a link that may provide you some ideas on things to look for in yor file/transactions.
http://www-306.ibm.com/software/tivoli/features/ccr2/ccr2-2004-06/features-vsam.html