Runbook
A written, step-by-step guide for running a system or handling a known failure.
Also written operations manual, procedure
Why it matters. At three in the morning you follow the page. You don't have to work it out.
Remember
- For each known failure it says how to spot it, what it means, what to do and who to call.
- Follow it in order.
- If a step is wrong, fix the runbook afterwards.
The usual mistake
I know the fix already, so I'll skip the runbook.
The page may hold a step you forgot, and the next person needs to see what was done.
Follow the page. Then correct it if it was wrong.
On real z/OS
MF/OS has no runbook tool. A real runbook is a document, or a page in an operations wiki, held outside z/OS.
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
- OperatorThe person who watches the running systems, responds to messages, and starts, stops and recovers work.
- Production supportKeeping live systems running: diagnosing failures, fixing what broke, and getting the service back.
- Batch schedulerSoftware that submits production jobs automatically in the right order, at the right time, based on what has already succeeded.
- Change controlThe process every change goes through before reaching production: reviewed, approved, scheduled and reversible.
- Batch windowThe period, usually overnight, in which batch work has to finish before the business needs the systems back.