Core6 min readLesson 3 of 3
Where modern tooling fits
Most sites are moving mainframe development towards the same tools everyone else uses: source in Git, pipelines that build and deploy, tests that run automatically. Almost all of that runs in USS.
The shape of a modern mainframe pipeline
GitSource in a repository
IDEVS Code or Eclipse with z/OS plugins
BuildCompile and bind on z/OS, driven by a pipeline
TestAutomated unit and integration tests
DeployPromote through environments
- Editors — VS Code and Eclipse-based IDEs connect to z/OS, giving syntax highlighting, code navigation and debugging without a 3270 screen. ISPF remains for the things it is better at.
- Source control — Git repositories, sometimes with a bridge to the traditional change-management product rather than replacing it.
- Build automation — a pipeline submits the compile and bind jobs, collects the results, and fails the build on a bad return code.
- Testing — unit test frameworks for COBOL and PL/I exist, and automated regression suites are increasingly normal.
- APIs — CICS and DB2 exposed as REST services so other systems can call business logic directly.
A realistic honest note
Adoption varies enormously. Some organisations have full continuous integration for mainframe code; others still promote by copying members between libraries with a change ticket. Ask about it in an interview — the answer tells you a great deal about what working there will be like.
What to learn first if this interests you
- Be comfortable in the USS shell — navigation, permissions, redirection, and reading logs.
- Learn how your site builds: which product drives compiles, where load modules land, how binds happen.
- Understand the deployment path end to end, including the approvals. This knowledge is what makes automation possible.
- Get familiar with one z/OS-aware IDE, because it is how new joiners will expect to work.
Common mistakes
Assuming the mainframe cannot do modern practice
It can, and many sites do. The constraint is usually organisational rather than technical.
Bypassing change control because the pipeline is faster
Regulated environments have those controls for a reason. Automate within them, not around them.
What you will see at work
- 'How do you deploy?' is one of the most informative questions you can ask on your first day.
- If your site has no automated testing, building a small regression harness for your own application is high-visibility, high-value work.
- Knowing both the traditional and the modern route is what gets you onto modernisation projects.
Key terms
Check your understanding.
Take this lesson's quiz and save your progress. Free.