Chapter 13. Introduction to end-to-end scheduling 315
and IBM Tivoli Workload Scheduler for z/OS scheduling
Connector A small program that provides an interface between the
common GUI (Job Scheduling Console) and one or more
scheduling engines. The connector translates to and from
the different “languages” used by the different scheduling
JSS Job Scheduling Services. Essentially a library that is used
by the connectors.
TMF Tivoli Management Framework. Also called just the
13.3 Tivoli Workload Scheduler architecture
Tivoli Workload Scheduler helps you plan every phase of production. During the
processing day, its production control programs manage the production
environment and automate most operator activities. Tivoli Workload Scheduler
prepares jobs for execution, resolves interdependencies, and launches and
tracks each job. Because jobs start running as soon as their dependencies are
satisfied, idle time is minimized and throughput is improved. Jobs never run out
of sequence in Tivoli Workload Scheduler. If a job ends in error, Tivoli Workload
Scheduler handles the recovery process with little or no operator intervention.
Tivoli Workload Scheduler is composed of three major parts:
Tivoli Workload Scheduler engine
The Tivoli Workload Scheduler engine is installed on every non-mainframe
workstation in the scheduling network (UNIX, Windows, and OS/400
computers). When the engine is installed on a workstation, it can be
configured to play a specific role in the scheduling network. For example, the
engine can be configured to be a master domain manager, a domain
manager, or a fault-tolerant agent. In an ordinary Tivoli Workload Scheduler
network, there is a single master domain manager at the top of the network.
However, in an end-to-end scheduling network,
there is no master domain
. Instead, its functions are instead performed by the Tivoli Workload
Scheduler for z/OS engine, installed on a mainframe.
Tivoli Workload Scheduler Connector
The connector “connects” the Job Scheduling Console to Tivoli Workload
Scheduler, routing commands from JSC to the Tivoli Workload Scheduler
engine. In an ordinary Tivoli Workload Scheduler network, the Tivoli Workload
Scheduler Connector is usually installed on the master domain manager. In
an end-to-end scheduling network, there is no master domain manager so the
316 IBM Tivoli Workload Scheduler for z/OS Best Practices
Connector is usually installed on the first-level domain managers. The Tivoli
Workload Scheduler Connector can also be installed on other domain
managers or fault-tolerant agents in the network.
The connector software is installed on top of the Tivoli Management
Framework, which must be configured as a Tivoli Management Region server
or managed node. The connector software cannot be installed on a Tivoli
Management Regions (TMR) endpoint.
Job Scheduling Console (JSC)
JSC is the Java-based graphical user interface for the Tivoli Workload
Scheduler suite. The Job Scheduling Console runs on any machine from
which you want to manage Tivoli Workload Scheduler plan and database
objects. Through the Tivoli Workload Scheduler Connector, it provides the
functions of the command-line programs conman and composer. The Job
Scheduling Console can be installed on a desktop workstation or laptop, as
long as the JSC has a TCP/IP link with the machine running the Tivoli
Workload Scheduler Connector. Using the JSC, operators can schedule and
administer Tivoli Workload Scheduler and Tivoli Workload Scheduler for z/OS
over the network. More on the JSC, including installation, can be found in
Chapter 16, “Using the Job Scheduling Console with Tivoli Workload
Scheduler for z/OS” on page 481.
13.3.1 The Tivoli Workload Scheduler network
A Tivoli Workload Scheduler network is made up of the workstations, or CPUs,
on which jobs and job streams are run.
A Tivoli Workload Scheduler network contains at least one Tivoli Workload
Scheduler domain, the master domain, in which the master domain manager is
the management hub. It is the master domain manager that manages the
databases, and it is from the master domain manager that you define new
objects in the databases. Additional domains can be used to divide a widely
distributed network into smaller, locally managed groups.

Get IBM Tivoli Workload Scheduler for z/OS Best Practices: End-to-end and mainframe scheduling, 2nd Edition now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.