When to Use a Warm Start

A warm start is less severe than a cold start, but you should use a hot start if possible. A warm start is required for the following situations:

After a failure that cannot be corrected by a hot start
To make changes to the initialization stream and put the new initialization values into effect.

Warm start processing reads the initialization stream. Since it does so, a warm start can change the global-local relationship defined between nodes. If a warm start is to change the global-local relationship, you should make sure that the work queue is empty before stopping and warm-starting BDT. Any errors found in the initialization stream will be treated as they are during a cold start.

Jobs that were active when BDT came down are interrupted. BDT will either restart these jobs or dispose of them according to their failure option. Jobs on the work queue are not affected unless the global-local relationship between nodes is redefined by the warm start. In this case the fate of jobs on the work queue is unpredictable.

All of the changes you made to jobs by issuing commands (such as MODIFY) will remain in effect.