Production support
The team that fixes the live system when something breaks.
Also written application support, L2 support
Why it matters. When a job ends with an error at night, they read the output, find the step and get the service back.
Remember
- Read what the system reported before you do anything.
- Decide: rerun, fix the data, or change the code.
- Write down what happened for the next person.
The usual mistake
Run the job again straight away.
If you don't know why it failed, it may fail again, or make the problem worse.
Read the output, find the failing step, then decide what to do.
On real z/OS
MF/OS has no on-call process, paging or incident tooling. You read job output and fix the cause, but nobody else's service depends on it.
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
- AbendAn abnormal end: a program stopping in an uncontrolled way rather than finishing and reporting a result.
- Return codeA number a program leaves behind saying how it went. Zero for clean, higher numbers for warnings and failures.
- SDSFThe tool for looking at what jobs are running, what has finished, and what output they produced.
- Batch windowThe period, usually overnight, in which batch work has to finish before the business needs the systems back.
- Mainframe application developerThe person who writes and changes the business programs: COBOL, JCL, SQL and the logic that runs the organisation.
- OperatorThe person who watches the running systems, responds to messages, and starts, stops and recovers work.