MODULE 13 · MAINFRAME INTERNALS AND CAPSTONE · 10/10

Next steps: getting hired

10 min10 XPReading

You can now read and write batch COBOL the way it's done in production: fixed-format source, copybooks, sequential and indexed files, sorting, control-break reports, subprograms, JCL, and data at the byte level. That's the core of most junior mainframe developer roles. Here's how to turn it into a job.

What employers test

Interviews for junior COBOL roles are rarely algorithm puzzles. Expect:

  • Read this program. You're given a page of COBOL and asked what it does, what it outputs, or where the bug is. Practise by reading the solutions in this course line by line and predicting their output.
  • Data definitions. "How many bytes is PIC S9(7)V99 COMP-3?" "What does X'00012D' hold?" "What's the difference between COMP and COMP-3?" You've done all of these.
  • Abends. "What is a S0C7 and how would you find the cause?" "What does S806 mean?" Answer with the workflow: the message, the statement, the field, the data.
  • JCL. Read a job: what runs, in what order, what COND=(4,LT) does, what happens to a &&TEMP dataset.
  • Batch concepts. Control breaks, match-merge of two sorted files, checkpoint and restart, why the file must be sorted first.
  • SQL basics for Db2 roles: SELECT ... INTO, cursors, SQLCODE +100 and -811.

Talking about your experience

You don't have mainframe job experience yet, so describe what you built, precisely:

"I wrote a claims end-of-day batch program in COBOL: copybook-defined records, a policy table loaded and searched with SEARCH ALL, NUMERIC validation feeding a reject file with reason codes, excess and limit pricing, and a region control-break report. It ran as a three-step job with DFSORT, my program with a PARM run date, and a print step conditioned on the return code."

Specific nouns (copybook, reject file, control break, return code, DFSORT) tell an interviewer you understand how batch really works. Keep your capstone and challenge solutions somewhere you can show them.

What to learn next

  • z/OS and ISPF. Get hands-on with a real mainframe: the ISPF editor, browsing datasets with HEX ON, submitting JCL and reading output in SDSF. IBM Z Xplore gives you a free account on a real IBM Z system with guided challenges from beginner to advanced, and completing them earns digital badges that employers recognise.
  • Zowe. The open-source way to use z/OS from VS Code and the command line. Many shops now edit COBOL and submit jobs from VS Code with Zowe Explorer, so it's a strong résumé line.
  • Db2 for z/OS. SQL embedded in COBOL, cursors, DCLGEN, BIND. Most batch systems have Db2 somewhere.
  • CICS. Pseudo-conversational programming, BMS maps, COMMAREAs and channels. Needed for online-transaction roles.
  • The rest of the toolchain. Source control (Endevor or Git), schedulers (IBM Workload Scheduler, Control-M), File Manager or File-AID, and a debugger such as IBM z/OS Debugger.

Where the jobs are

Banks, insurers, government agencies, airlines, retailers and the consultancies that serve them. Search for "COBOL developer", "mainframe developer", "z/OS application developer" and "mainframe graduate programme". Many large employers and IBM partners run paid trainee programmes that assume little more than what you've learned here. Apply to those as well as to regular junior roles.

On the job

Your first months will be mostly reading: existing programs, job streams and copybooks. Ask for the system's batch schedule and walk one nightly job from input to report. Understanding one flow end-to-end makes every later change easier, and it's exactly what you've practised in this module.

Create a free account to track your progress.