Operator
The person who watches the running systems, answers messages, and starts, stops and recovers work.
Also written systems operator, console operator
Why it matters. When something needs a decision at three in the morning, the operator makes the first call.
Remember
- Operators watch the consoles, where the system reports what is happening.
- Software handles the known messages. A person handles the unusual ones.
- They follow the runbook.
The usual mistake
Everything is automatic, so operators aren't needed.
Automation handles known messages. A new problem needs a person to decide.
Automation does the routine work. Operators handle what it can't.
On real z/OS
MF/OS has the console commands an operator uses (START, STOP, DISPLAY), but not a live console. There are no operator replies to wait for, no automation product, and no other people's work to watch.
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 schedulerSoftware that submits production jobs automatically in the right order, at the right time, based on what has already succeeded.
- Batch windowThe period, usually overnight, in which batch work has to finish before the business needs the systems back.
- Started taskA long-running program that the system starts and leaves running, rather than a job that runs once and finishes.
- RunbookThe written procedure for operating a system or responding to a known failure, step by step.
- Production supportKeeping live systems running: diagnosing failures, fixing what broke, and getting the service back.