Change control
The steps a change takes before it reaches the live system: checked, approved, scheduled and able to be undone.
Also written change management, release process
Why it matters. A mistake in live banking code moves real money the wrong way. Change control is what stops it.
Remember
- Every change is described, tested, approved and scheduled.
- Every change has a way to go back.
- Your work moves from DEV to TEST to PROD, never straight to PROD.
The usual mistake
It's a tiny fix. I'll put it in PROD myself.
Small changes break live systems too, and then nobody knows what changed or how to undo it.
Raise the change, test it, get it approved, then release it.
On real z/OS
MF/OS has no change tool. Moving work from DEV to TEST to PROD is done with commands such as TRANSMIT and a release job. Real sites use change management products and tickets, with approvals and back-out plans.
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
- Production supportKeeping live systems running: diagnosing failures, fixing what broke, and getting the service back.
- System programmerThe person who installs, configures, tunes and upgrades the operating system and its subsystems.
- Load moduleThe runnable form of a program, stored in a library, which JCL executes by name.
- PERMITThe command that grants or removes a user or group's access to a protected resource.
- RunbookThe written procedure for operating a system or responding to a known failure, step by step.