Batch processing
Work that runs in bulk, with nobody watching, usually overnight.
Also written batch, batch job, overnight batch
Why it matters. While customers sleep, batch jobs settle the day: payments, interest, statements. Most of the bank's heavy work is batch.
See it
By handYou type a command and watch it happen. One thing at a time.
BatchThe work is written down and handed over. The machine runs it on its own, often overnight.
Remember
- Batch work is collected up and run in one go. No one waits at a screen.
- The other way to work is online: a person sends a request and waits for the answer.
- You hand a job in with SUBMIT. The job runs on its own and leaves its output in the spool.
The usual mistake
Waiting at the screen for a batch job to answer you
A batch job does not talk to you. It runs on its own and leaves its results for you to read.
Submit it, keep the job number, and read the output when it ends
On real z/OS
Mainframe101 sim: a job you submit starts at once and runs in the simulator. A real system queues it by class and priority, and it can wait for an initiator or for a TYPRUN=HOLD release.
Where can I practise Batch processing?
Right here, at ZedBank. You take a junior job at a simulated bank and use Batch processing in real work, with Zed beside you. There's nothing to install.
Start at ZedBankRelated
- JCLJob Control Language: the language used to tell the mainframe what programs to run, in what order, and with what files.
- JobA unit of batch work submitted to the system, made up of one or more steps that run in order.
- Online transaction processingHandling many small pieces of work in real time while someone waits: a card payment, a balance check, a seat booking.
- Return codeA number a program leaves behind saying how it went. Zero for clean, higher numbers for warnings and failures.
- Batch windowThe period, usually overnight, in which batch work has to finish before the business needs the systems back.