Recovering with the use of the ResetPlan command

Perform these steps on the master domain manager:
  1. Run planman showinfo and save the output. The information you obtain from the command will be used when running the JnextPlan command in the subsequent steps. For more information, see Retrieving the production plan information.
  2. Shut down all IBM Workload Scheduler processes on the master domain manager.
  3. Run ResetPlan.
  4. If scheduling cannot be resumed, run ResetPlan -scratch. Be aware that running ResetPlan with the -scratch option deletes the preproduction plan. For more information, see Resetting the production plan.
  5. Run JnextPlan, specifying the timezone of the master domain manager and setting the -to parameter to the start-of-day value. Set the -from parameter to cover the period for which there are still outstanding jobs. Note that based on the setting of the -from parameter, the amount of jobs to be recovered might be very high. For more information about JnextPlan, see JnextPlan.
  6. Check the created plan and ensure that you want to run all the instances it contains, deleting those that you do not want to run.
  7. Increase the job limit on all workstations. This is necessary because the ResetPlan command sets all job limits to 0.
  8. The Symphony file is distributed and production recommences.
Note:
    • The status of the jobs and the job streams after you run the recovery procedure is reset to HOLD or READY.
    • Some IBM® Workload Scheduler events that were triggered before applying the recovery procedure, might be triggered again after the recovery procedure has completed. This limitation concerns those events that are not managed through a message queue, for example, UNTIL, DEADLINE, and MAXDUR.
    • Jobs in USERJOBS Job Stream are not subject to resource controlling. As a result, affected resources should be adjusted and attended manually.
    • Prompts in the recovered plan might have a prompt number different from the prompt number in the original plan. To prevent mismatches, prompt reply events are not recovered.