Exclusive control deadlock
In non-RLS mode, without some means of avoiding it, a task could wait on itself for exclusive control of a VSAM control interval. If this was allowed to happen, the task would be deadlocked, and neither able to release exclusive control or reacquire it.
Similarly, a task could be made to wait on another task that has exclusive or shared control of a VSAM control interval. If this second task was, itself, waiting for exclusive control of a resource of which the first task has exclusive or shared control, then both tasks would be deadlocked.
CICS® however, provides a mechanism to avoid exclusive control deadlock. If a task is waiting on resource type FCXCSUSP or FCXDSUSP and causing a task to wait (either itself or another task), causing a deadlock, the task abends either with abend code AFCF or AFCG at the time that it makes the request for exclusive control.
- A task that abends with abend code AFCF would have been waiting for exclusive control of a VSAM control interval of which another task has shared or exclusive control.
- A task that abends with abend code AFCG would have been waiting for exclusive control of a VSAM control interval of which it has shared control.
See Transaction abend codes for more information about these abend codes.
To resolve the problem, you must determine which program caused the potential deadlock. Find out which programs are associated with the abending task, and attempt to find the one in error. It is likely to be one that provides successive browse and update facilities. When you have found the programs associated with the task, see How tasks can become deadlocked waiting for exclusive control for guidance about finding how the error might have occurred.
For further details on the redispatch of CICS tasks that were waiting for VSAM exclusive control of a control interval to become available, see File control operations.