Chapter 1. Overview and benefits 21
Manager and notify it of all the changes occurring in their own plans. At the same
time, the agents are not permitted to interfere with the IBM Tivoli Workload
Scheduler for z/OS jobs, since they are viewed as running on the master that is
the only node that is in charge of them.
IBM Tivoli Workload Scheduler for z/OS also allows you to access job streams
and add them to the current plan in IBM Tivoli Workload Scheduler for z/OS. In
addition, you can build dependencies among IBM Tivoli Workload Scheduler for
z/OS job streams and IBM Tivoli Workload Scheduler jobs. From IBM Tivoli
Workload Scheduler for z/OS, you can monitor and control the distributed agents.
In the IBM Tivoli Workload Scheduler for z/OS current plan, you can specify jobs
to run on workstations in the IBM Tivoli Workload Scheduler network. IBM Tivoli
Workload Scheduler for z/OS passes the job information to the Symphony file in
the IBM Tivoli Workload Scheduler for z/OS server, which in turn passes the
Symphony file to the IBM Tivoli Workload Scheduler Domain Managers (DMZ) to
distribute and process. In turn, IBM Tivoli Workload Scheduler reports the status
of running and completed jobs back to the current plan for monitoring in the IBM
Tivoli Workload Scheduler for z/OS engine.
Structure
Figure 1-6 on page 22 shows an end-to-end environment where a IBM Tivoli
Workload Scheduler network is managed by IBM Tivoli Workload Scheduler for
z/OS.