Welcome
IBM® Workload Scheduler
Welcome to the IBM® Workload Scheduler documentation, where you can find information about how to install, maintain, and use IBM Workload Scheduler. The documentation has been updated for IBM Workload Scheduler Version 10.2.1.
Troubleshooting
Corrupt Symphony recovery
Explains the symptoms of Symphony file corruption and links you to tasks that can recover the file on the master domain manager, fault-tolerant agent, or lower domain manager.
Recovery procedure on a master domain manager
If a Symphony file is corrupt on a master domain manager, there are several ways in which you can regenerate it.
Recover using the logman and ResetPlan commands
The following procedures can also be used to recover a corrupt Symphony file on the master domain manager.
Recovering with the use of the ResetPlan command

Product requirements
This section contains links to the IBM® Workload Scheduler Download Documents, System Requirements, and Release Notes.
Product Library in PDF format
This section contains links to the PDF versions of all the publications provided in IBM Documentation for IBM Workload Automation.
Considerations for GDPR readiness
Overview
Mobile Applications Userʼs Guide
Dynamic Workload Console User's Guide
AI Data Advisor (AIDA) User's Guide
Scheduling Job Integrations with IBM Workload Automation
IBM® Workload Scheduler
Welcome to the IBM® Workload Scheduler documentation, where you can find information about how to install, maintain, and use IBM Workload Scheduler. The documentation has been updated for IBM Workload Scheduler Version 10.2.1.
- Quick Start Guide
- Planning and Installation
- User's Guide and Reference
- Administration Guide
- Scheduling with the Agent for z/OS
- Database Views
- High Availability Cluster Environment
- Troubleshooting
  - Getting started
    Gives an overview of what troubleshooting information is contained in this publication, and where to find troubleshooting information which is not included.
  - Logs and traces
    Provides detailed information about logs and traces, and how to customize them and set the logging and tracing levels.
  - Capturing product data
    Describes the facilities available for data capture in the event of problems occurring. It provides full details of the Data capture utility and the provisions for first failure data capture.
  - In-Flight Trace facility
    Describes the tracing facility for troubleshooting the IBM Workload Scheduler engine. This facility is called In-Flight Trace.
  - Troubleshooting performance
    This refers you to the Administration Guide for the resolution of performance problems.
  - Troubleshooting networks
    Describes how to recover from short-term and long-term network outages and offers solutions to a series of network problems.
  - Troubleshooting engine problems
    Gives solutions to problems that might occur with the modules and programs that comprise the basic scheduling "engine" on the master domain manager.
  - Troubleshooting dynamic workload scheduling
    This section provides information that is useful in identifying and resolving problems with dynamic workload scheduling, including how to tune the job processing rate and how to solve common dynamic scheduling problems.
  - Troubleshooting when automatically adding dynamic agent workstations to the plan
    This section provides information that is useful in identifying and resolving problems in the IBM Workload Scheduler environment when you enable the automatic adding of dynamic agent workstations to the plan.
  - Troubleshooting Dynamic Workload Console
    Describes how to troubleshoot problems with the Dynamic Workload Console related to connections, performance, user access, reports, and others.
  - Troubleshooting workload service assurance
    Gives you troubleshooting information about workload service assurance by explaining how it works and how it exchanges information between the modules. In addition, it provides solutions to common problems.
  - Troubleshooting switch manager
    Provides troubleshooting information about the fault-tolerant switch manager in terms of the event counter, the Ftbox, and link problems. It also provides solutions to some common problems with the backup domain manager.
  - Synchronizing the database with the Symphony file
  - Corrupt Symphony recovery
    Explains the symptoms of Symphony file corruption and links you to tasks that can recover the file on the master domain manager, fault-tolerant agent, or lower domain manager.
    - Recovery procedure on a master domain manager
      If a Symphony file is corrupt on a master domain manager, there are several ways in which you can regenerate it.
      - Recovering using the backup master domain manager
      - Recover using the logman and ResetPlan commands
        The following procedures can also be used to recover a corrupt Symphony file on the master domain manager.
        Recovery procedure using logman
        Describes how to recover from a corrupt Symphony file using the logman command.
        Recovering with the use of the ResetPlan command
      - Recovering the plan from the archived plan
        You can recover a corrupted plan on a master domain manager using the latest archived plan, however; this is possible only if you have performed some configuration steps prior to the occurrence of the file corruption.
    - Recovery procedure on a fault-tolerant agent or lower domain manager
    - Recovery procedure on a fault-tolerant agent with resetFTA
  - Support information
  - Date and time format reference - strftime
- Driving IBM Workload Automation
- Extending IBM Workload Automation
IBM® Z Workload Scheduler
The latest versions of the IBM® Z Workload Scheduler documentation is V10.1. See the related documentation here: HCL Workload Automation for Z v10.1.
Messages and Codes
Glossary
Installing IBM® Workload Scheduler
How to monitor your IBM® Workload Scheduler using the Dynamic Workload Console
How to create your scheduling environment using the Dynamic Workload Console
Notices

Recovering with the use of the ResetPlan command

Perform these steps on the master domain manager:

Set the job "limit" to “0”, using conman or the Dynamic Workload Console.
This prevents jobs from launching.
Shut down all IBM Workload Scheduler processes on the master domain manager.
Run ResetPlan -scratch.
Run JnextPlan, setting the -from and -to parameters to cover the period for which there are still outstanding jobs.
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.
Reset the job "limit" to the previous value. The Symphony file is distributed and production recommences.