Parts and their relationships

Tivoli Workload Scheduler for z/OS consists of a base product, the agent, and a number of features. You need the base product to track your workload. Hereafter, you see the agent referred to as the tracker and the engine referred to as the controller. One z/OS system in your complex is designated the controlling system and runs the controller feature. Only one controller feature is required, even when you want to start standby controllers on other z/OS systems in a sysplex.

You can control work running in non-z/OS operating environments from a central controller.

To do this, you need the appropriate fault-tolerant workstation and end-to-end enabler feature on the controlling system of the scheduler. See the Tivoli® Workload Scheduler for z/OS®: Planning and Installation Guide for a list of supported operating environments.

You can also control the workload in other operating environments using the end-to-end scheduling functions provided in IBM® Tivoli Workload Scheduler for z/OS and in IBM Tivoli Workload Scheduler.

Additionally, national language features let you see the Tivoli Workload Scheduler for z/OS ISPF dialogs in the language of your choice. These languages are available:

The rest of this section describes the tracker and controller, their relationship, and how you can configure them.