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