Restarting a member with conditions

Some installations use conditional restart to bypass a long active UR backout, such as might occur when a long-running batch job fails without having issued interim commits. In data sharing environments, this use of conditional restart is not recommended.

It is safer and provides better availability to reroute work to another member or to postpone backout processing rather than suffer the total outage necessary for a conditional restart.

If you do perform conditional restart, you need to stop all members of the group except the one that is conditionally restarting to ensure that applications on those other members do not change the data that is not locked by the restarting member.

You might, in unusual circumstances, choose to make inconsistent data available for use without recovering it. This might be the case for certain test groups, for example, where data consistency is not important.