Choosing data availability over data integrity
There may be times when you cannot resolve all the retained locks correctly, either because you cannot easily remedy the situations preventing the changes from being committed, or because of insufficient time.
About this task
In such a situation, you can still release the locks, using the SET DSNAME command, although in most cases you will lose some data integrity.
- By backing out or committing the changes according to the COMMIT or BACKOUT option on UOWACTION.
- By backing out or committing the changes according to the indoubt ACTION attribute specified on the transaction resource definition (when you specify the FORCE option on UOWACTION).
When the unit of work completes, the locks are released. If the action chosen is backout (either by explicitly specifying BACKOUT or as a result of the FORCE option), diagnostic information is written to the CSFL transient data queue. Therefore BACKOUT is normally the best option, because you can use the diagnostic information to correct the data if backout was the wrong decision. Diagnostic messages DFHFC3004 and DFHFC3010 are issued for each backed-out update. Choose COMMIT for the units of work only if you know this is the decision that would be communicated by the coordinator when resynchronization takes place following reconnection.
- Releases any locks held against this data set by shunted units of work (other than indoubt failures)
- Discards the log records that represent the uncommitted changes made to the data set by those units of work
- Writes diagnostic information to the CSFL transient data queue for each discarded log record.
If a data set has both indoubt-failed and other (backout- or commit-) failed units of work, deal with the indoubt UOWs first, using SET DSNAME UOWACTION, because this might result in other failures which can then be cleared by the SET DSNAME RESETLOCKS command.