The scheduler uses these important concepts:
Applications
An application is a description of a unit of production work. It includes a list of theoperations (related tasks) associated with that unit of work. For example, a payrollapplication might include a manual task where an operator prepares a job, severalcomputer-processing tasks where programs are run to read a database, updateemployee records, and write payroll information to an output file, and a print taskthat prints pay checks.
Business processing cycles
The scheduler uses business processing cycles, or periods, to calculate when yourapplications should be run. When you create an application, you specify when it should be planned using a run cycle. You can use rule-based run cycles to specifyrun days using rules such as “Third Thursday in July,” or “Every work day inweek 40,” where you select the words from a multiple-choice panel.
Calendars
The scheduler uses calendar information so that applications are not scheduled torun on days when processing resources are not available (for example, Sundaysand holidays). This information is stored in a calendar. The scheduler supportsmultiple calendars for enterprises where different departments have different workdays and free days or when multiple data centers in different states or regions arecontrolled from a single site.
Dependencies
Most data processing activities need to occur in a specific order. Activitiesperformed out of order can create invalid output or corrupt your corporate data.This results in costly reruns, missed deadlines, and dissatisfied customers.In IBM Tivoli Workload Scheduler for z/OS, you can specify dependencies foroperations when a specific processing order is required.
Plans
The scheduler builds operating plans from your descriptions of the productionworkload. First a long-term plan (LTP) is created, which shows (for typically one ortwo months) the applications that should be run each day, and the dependenciesbetween applications. Then a more detailed current plan is created. The currentplan is used by IBM Tivoli Workload Scheduler for z/OS to submit and controloperations.You can simulate the effects of changes to your production workload, calendar, andinstallation, by generating trial plans.
Special resourcesYou can use special resources to represent any type of limited resource, such as tapedrives, communication lines, or a database. A special resource can be used toserialize access to a data set or to limit the number of file transfers on a networklink. The resource does not have to represent a physical object in yourconfiguration, although often it does.
Workstations
The scheduler supports a range of work process types, called workstations, that mapthe processing needs of any task in your production workload. Each workstationsupports one type of activity. This gives you the flexibility to schedule, monitor,and control any data processing activity, including:
- Job setup—both manual and automatic
- Jobs
- Started tasks
- NetView communication
- Print operations
- Manual preprocessing or postprocessing activity.