Batch scheduler
Software that runs the nightly jobs for you, in the right order, at the right time.
Also written job scheduler, workload scheduler, CA-7
Why it matters. Hundreds of jobs depend on each other. No person can start them by hand at three in the morning without a mistake.
Remember
- A job runs only after the jobs it depends on have ended well.
- Calendars decide which jobs run on which days, such as month end.
- When a job fails, the scheduler stops the chain and tells someone.
The usual mistake
Starting nightly jobs by hand, in the order you remember
One job in the wrong order can read a file that is not ready yet.
Let the scheduler run them in the order of their dependencies
On real z/OS
MF/OS has no scheduler. You submit jobs by hand. Real sites use products such as IBM Z Workload Scheduler, CA-7 or Control-M to run job networks by calendar and dependency, and to restart after a failure.
Where can I learn this hands-on?
Right here, at ZedBank. You take a junior job at a simulated bank and learn each part of the work by doing it, with Zed beside you. There's nothing to install.
Start at ZedBankRelated
- Batch windowThe period, usually overnight, in which batch work has to finish before the business needs the systems back.
- JobA unit of batch work submitted to the system, made up of one or more steps that run in order.
- Batch processingRunning work in bulk, without anyone watching, usually on a schedule. The overnight run that settles a day of transactions.
- OperatorThe person who watches the running systems, responds to messages, and starts, stops and recovers work.
- Return codeA number a program leaves behind saying how it went. Zero for clean, higher numbers for warnings and failures.
- Production supportKeeping live systems running: diagnosing failures, fixing what broke, and getting the service back.
- Generation data groupA set of datasets holding successive versions of the same file, so today's copy, yesterday's and last week's all exist under one name.