Managing production scheduling activities with IBM Workload Scheduler

Each time a new production plan is generated, IBM Workload Scheduler selects the job streams that run in the time window specified for the plan, and carries forward uncompleted job streams from the previous production plan. All the required information is written in a file, named Symphony, which is continually updated while processing to indicate work completed, work in progress, and work to be done. The IBM Workload Scheduler conman (Console Manager) command-line program is used to manage the information in the Symphony file. The conman command-line program can be used to:
  • Start and stop IBM Workload Scheduler control processes.
  • Display the status of jobs and job streams.
  • Alter priorities and dependencies.
  • Alter the job fence and job limits.
  • Rerun jobs.
  • Cancel jobs and job streams.
  • Submit new jobs and job streams.
  • Reply to prompts.
  • Link and unlink workstations in the IBM Workload Scheduler network.
  • Modify the number of available resources.
Starting with version 9.1, all of the plan information written to the Symphony file is then replicated to the database. Various monitoring operations requested from the Dynamic Workload Console access the database, rather than the Symphony file, resulting in quicker response times and overall performance. The following operations requested from the Dynamic Workload Console access information from the database:
  • Monitoring jobs and job streams
  • Refreshing job and job stream monitoring views
  • Monitoring workstations
  • Monitoring resources, files, prompts
  • Running baseline reports
  • Displaying the plan in a graphical view
  • Displaying the job stream in a graphical view
Note: This feature does not work with DB2 JDBC driver type = 2. IBM Workload Scheduler is supplied with JDBC driver type 4