Functional comparison with IBM Workload Scheduler

The following is a list of additional functionality that is available in the end-to-end with fault tolerance capabilities configuration when compared with a native IBM Workload Scheduler environment:
  • Security can be handled by RACF®.
  • Special (global) resources are available also to the fault-tolerant workstations.
  • In use and Waiting queues are available for resources.
  • The capability to take advantage of the IBM Z Workload Scheduler program interface (PIF) and of the batch command interface to automate workload management is extended to fault-tolerant workstations.
  • More powerful periods, calendars, and run cycles are supported.
  • Use of variable tables for variable substitution also for job streams involving fault-tolerant workstations.
  • Operator Instructions.
  • ETT on z/OS® jobs, data sets, resources.
  • Edit JCL, Job setup (only for centralized jobs).
The following is a list of native IBM Workload Scheduler functionality that is not supported in the end-to-end with fault tolerance capabilities configuration:
  • The following conman commands are not supported:
    • adddep
    • altpri
    • cancel
    • deldep
    • release
    • rerun
    • submit docommand
  • Elapsed daily plans (Symphony) are not archived, and it is not possible to choose and work with a past plan.
  • Workstation classes are not supported.
  • The workstation ignore attribute is not implemented for fault-tolerant workstations. Because of this limitation, together with a lack of support for availability intervals, you cannot take workstations temporarily out of the IBM Workload Scheduler network, unless the workstations are deleted or renamed.
  • Prompts, as defined in native IBM Workload Scheduler, do not exist in the end-to-end with fault tolerance capabilities configuration.
  • The limit attribute for job streams is not supported.
  • The until time dependency provided in IBM Workload Scheduler is not mapped exactly to the deadline-time concept provided in end-to-end scheduling with fault tolerance capabilities. In particular, the onuntil actions provided by IBM Workload Scheduler are more powerful and granular than their equivalent in the end-to-end with fault tolerance capabilities environment.
  • Passwords of IBM Workload Scheduler users on Windows™ are not encrypted when scheduling end-to-end with fault tolerance capabilities. They are kept in clear text in the end-to-end partitioned data sets (that can be placed under RACF® security).
  • File dependencies are provided with a different mechanism in end-to-end with fault tolerance capabilities. The concept of files and files dependencies provided in IBM Workload Scheduler is simulated by using a job running the filewatch utility and setting a dependency on that particular job.
  • In end-to-end scheduling with fault tolerance capabilities, you can change the priority of a job stream, but not of individual jobs.
  • The cancel command for jobs and job streams is mapped to the delete function in end-to-end.