Tracker

A tracker is required for every z/OS system in a Tivoli Workload Scheduler for z/OS configuration. The tracker handles the submission of jobs and tasks on the system, and keeps track of the status of the workload. In conjunction with standard interfaces to JES and SMF, Tivoli Workload Scheduler for z/OS records the relevant information about the workload by generating event records. The event records are captured and stored by the tracker. The tracker then communicates event information to the controller for further processing. The log where events are written by the tracker is called the event data set.

Tivoli Workload Scheduler for z/OS address spaces are defined as z/OS subsystems. The routines that run during subsystem initialization establish services that enable event information to be generated and stored in common storage (ECSA) even when an address space is not active.

You can optionally install a Data Store for each JES spool in a system. In a simple JES configuration this would mean one Data Store for each tracker. In systems with shared spools (for example, JES2 MAS), there is a Data Store for each spool, and there are fewer Data Stores than trackers.