Mainframe application developer
The person who writes and changes the programs that do the bank's work: COBOL, JCL and SQL.
Also written COBOL developer, application programmer
Why it matters. They keep the calculations, payments and statements correct.
Remember
- Most of the day is reading code that already runs.
- Before you change a rule, find out what else uses the same data.
- Test in DEV and TEST. A change reaches PROD only through change control.
The usual mistake
A developer writes new programs all day.
Most of the work is reading and changing programs that have run for years.
Understand the old program first, then change it carefully.
On real z/OS
MF/OS doesn't model a team, source control or a debugger such as Debug Tool. You write, compile and run programs yourself.
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
- COBOLThe programming language most business logic on the mainframe is written in. Verbose by design, and still running the world's payments.
- JCLJob Control Language: the language used to tell the mainframe what programs to run, in what order, and with what files.
- CICSThe transaction manager that runs online mainframe applications, and the software behind a great many screens bank staff use.
- DB2 for z/OSIBM's relational database on the mainframe, where a great deal of the world's banking and insurance data is stored.
- Legacy systemAn older system still doing essential work. On the mainframe, usually code that has been correct and running for decades.
- Production supportKeeping live systems running: diagnosing failures, fixing what broke, and getting the service back.