DFHFC0555    applid One or more data sets are in lost locks status. CICS will perform lost locks recovery.

Explanation

CICS had one or more data sets open in RLS access mode at the time of a failure of the coupling facility lock structure from which SMSVSAM was not able to recover transparently. As a result, the RLS locks held by CICS for those data sets have been lost.

SMSVSAM has informed CICS that one or more data sets are in a lost locks state with respect to this CICS. CICS must therefore perform lost locks recovery for those data sets.

This can occur on a CICS warm or emergency restart, and on a dynamic RLS restart. On a CICS cold or initial start, if there are any data sets with lost locks status, that status is cleared with respect to this CICS.

System action

The data sets with lost locks status are marked as being unavailable for general use. Units of work that attempt to access such data sets abend with an AFCU abend code.

CICS performs lost locks recovery for the data sets. For each data set, lost locks recovery involves waiting until all units of work that had made uncommitted updates to the data set have completed. These units of work are allowed to access the data set, in order to perform their recovery. When CICS has completed lost locks recovery for a data set, it reports this fact to SMSVSAM. When all CICS regions that had been accessing the data set have completed their lost locks recovery, then the data set is made available for general use again. Note that a data set becomes available for general use as soon as its lost locks recovery has been completed; it does not have to wait for all data sets to be recovered.

CICS takes the following actions to expedite lost locks recovery:

  • Backout-failed and commit-failed units of work are driven for retry

  • On a dynamic RLS restart, inflight transactions that had updated the data set are purged (on a warm or emergency restart, inflight units of work are automatically backed out).

User response

Lost locks recovery normally completes automatically without requiring any action from the user. However, if there are shunted units of work which had updated a data set with lost locks status, these prevent lost locks recovery from completing until they are resolved. Use the INQUIRE UOWDSNFAIL command to investigate these shunted units of work.

If lost locks recovery appears to be taking a long time, you can compare the output obtained by issuing the IDCAMS SHCDS LISTSUBSYS(ALL) command at different intervals, to determine what progress has been made.

See the Administering recovery and restart information for guidance on resolving shunted units of work which hold RLS retained locks.

Module

DFHFCRR

XMEOUT parameters/Message inserts

  1. applid

Destination

Console



DFHFC0555.html | Timestamp icon Last updated: Sunday, 4 June 2017