Resource types FCXCSUSP, FCXDSUSP, FCXCPROT, and FCXDPROT - VSAM exclusive control waits

If your task is waiting on resource type FCXCSUSP, FCXDSUSP, FCXCPROT, or FCXDPROT, it means that it cannot get exclusive control of a VSAM control interval at the present time. Another task already has shared or exclusive control of the control interval, so your task is suspended pending the release of that control interval.

An exclusive control wait on these resource types occurs in CICS, unlike the similar wait on FCIOWAIT, which occurs in VSAM. See Resource type FCIOWAIT - wait for VSAM I/O (non-RLS).

FCXCPROT or FCXDPROT waits indicate that VSAM has detected an error in the base cluster, AIX, or upgrade set. In these cases, it is not advisable to purge the requests because the data set can be lift in an inconsistent state. Purge other tasks involved in the wait to allow CICS to retry the VSAM requests for those tasks with FCXCPROT and FCXDPROT waits.

Unlike the FCXCSUSP and FCXDSUSP types, tasks waiting with a resource type of FCXCPROT or FCXDPROT will not be purged if the are suspended for longer than their DTIMOUT value.

The CICS monitoring facility provides performance data for the exclusive control wait time for each user task. The performance data field 426, FCXCWTT, in the DFHFILE group, shows the elapsed time in which the task waited for exclusive control. If you find that exclusive control conflicts occur too often in your system, consider changing the programming logic so that applications are less likely to have exclusive control for long periods.

Waiting on this resource can occur only for files accessed in non-RLS mode.

The possibility that a task is deadlocked, waiting on itself or another task for release of the control interval, is dealt with in the next section.



dfhs120.html | Timestamp icon Last updated: Monday, 5 June 2017