Recovering the Symphony file using the logman command

Describes how to recover from a corrupt Symphony file using the logman command.

Perform these steps on the master domain manager:
  1. Set the job "limit" to “0” on all the workstations by using conman, the Dynamic Workload Console. If you are using conman, run the following command: 
    conman "limit cpu=@!@;0;noask"

    This command prevents jobs from launching.

  2. Shut down all IBM Workload Scheduler processes on the master domain manager.
  3. Run logman -prod to update the preproduction plan with the information for the job streams that are in COMPLETE state.
  4. Run planman showinfo and check for the first incomplete job stream instance.
  5. Run ResetPlan.
  6. Run JnextPlan, setting the -from parameter to the start time of the first incomplete job stream instance in the preproduction plan (acquired from the output of planman showinfo) and the -to parameter to the end date of your plan (or to the following day). Only incomplete job stream instances will be included in the new Symphony file. If the instance of the first incomplete job stream is very old the new plan creation can take a long time. The incomplete jobs and job streams that are created again with the JnextPlan -from parameter are those present in the database when the command is run.
  7. Check the created plan and verify that all the jobs and job streams in the plan have the correct status.
  8. Ensure that you want to run all the instances in the plan, deleting those that you do not want to run.
  9. All the submitted job streams are not carried forward. Resubmit them.
  10. Reset the job "limit" to its previous value. The Symphony file is distributed and production starts again.
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.