Resolving retained locks and preserving data integrity

Unless prevented by time constraints, you are recommended to resolve retained locks by using the INQUIRE UOWDSNFAIL command and retrying shunted UOWs.

About this task

Procedure

  1. Use the INQUIRE UOWDSNFAIL command to find out which failed component has caused the UOW to have retained locks for this data set.
  2. If a unit of work that has been shunted with a CAUSE of DATASET and a REASON of DELEXITERROR, enable a suitable global user exit program at the XFCLDEL (logical delete) global user exit point and then issue a SET DSNAME ACTION(RETRY) command to retry the backout and drive the global user exit.
  3. If a unit of work that has been shunted with a CAUSE of CONNECTION, use the SYSID and NETNAME returned by INQUIRE UOWDSNFAIL to find out what has caused the indoubt condition and correct the failure, after which automatic resynchronization should allow the unit of work to complete, either by being backed out or by committing the changes.
  4. If a unit of work has been shunted with a different CAUSE and REASON, review the descriptions of these values in the INQUIRE UOWDSNFAIL command to determine what action to take to allow the shunted unit of work to complete.


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