Who works in mainframe operations
A mainframe runs around the clock, so a team watches it around the clock. Operators run the system and the console, schedulers run the batch, production support fixes application failures, systems programmers own the platform, and incident, problem and change managers keep it all coordinated.
A system that never closes
Banks, insurers, airlines and governments run their core systems on z/OS 24 hours a day. The operations command center (also called the operations bridge or data center operations) is the team, and often the room, that watches those systems, runs the work and responds when something goes wrong.
The roles
| Role | Owns | Typical work |
|---|---|---|
| Operator | The running system and its consoles | Answering console messages, starting and stopping subsystems, IPLs, watching alerts, first response |
| Scheduler / batch operator | The batch schedule | Running the batch night, handling job failures, restarts and the critical path |
| Production support (L2) | Application failures | Diagnosing abends and data problems, fixing and rerunning, working with developers |
| Systems programmer | z/OS and its products | Configuration, maintenance, IPL planning, deep platform problems; on call for operations |
| Incident manager | Major incidents | Running the bridge call, communications, decisions and timelines |
| Change and problem managers | Change and root cause processes | Approving changes, tracking root causes to a fix |
| Service desk (L1) | User contact | Logging tickets, password resets and simple requests, routing the rest |
Shifts and coverage
- Operations usually works in shifts, such as three eight-hour shifts or two twelve-hour shifts, so someone is always at the console.
- Some organisations use follow-the-sun teams in different countries, handing over as each region's working day ends.
- Specialists such as systems programmers and application developers are not always on site; they are reached through an on-call rota.
Which role owns z/OS configuration and maintenance, and is on call for operations? (two words)
Show a hint
Often shortened to sysprog.
Show the solution
The systems programmer.
Common mistakes
Most of the job is watching, judging and communicating. Commands are the small part.
Each role owns specific things. Operators restore service by the run book and involve the owner; they do not change applications or system configuration themselves.
Users contact the service desk first. Keep it informed during incidents so users get consistent answers.
What you will see at work
- Entry-level mainframe jobs are often in operations, and many systems programmers and production support engineers started as operators.
- Job titles vary: 'operations analyst', 'command center analyst', 'batch scheduler', 'production control'. The work in the table is what matters.
- Operations teams are measured on availability, batch deadlines met, and how quickly incidents are detected and restored.
Key terms
Check your understanding.
Take this lesson's quiz and save your progress. Free.