AppliedModernization42 min

DevOps and CI/CD on z/OS

How mainframe teams move from manual promotion and change windows to Git, automated builds, tests and deployments — and which old ideas map onto which new tools.

What you will be able to do

Explain what CI/CD changes for a mainframe team and what it keeps
Map PDS members, promotion levels and change packages onto Git repositories and branches
Describe how a COBOL program is compiled, tested and deployed by a pipeline
Name the checks a safe production deployment needs on z/OS

Lessons

Why mainframe teams adopt CI/CD
CI/CD means every change is built and tested automatically as soon as it is committed, and released through an automated, repeatable path. Mainframe shops already had disciplined…
Source control: from PDS members to Git
Git stores every version of every file and lets many people work in parallel on branches. Moving mainframe source into Git means turning members into files, sorting out character…
Building COBOL in a pipeline
A pipeline build does exactly what your compile JCL does — precompile, compile, link-edit — but it is started by a commit, runs on a build server that talks to z/OS, and knows…
Automated testing on z/OS
A pipeline is only as safe as its tests. On the mainframe that means unit tests for individual COBOL programs, integration tests against test copies of DB2, CICS and files, and…
Deploying safely to production
Deploying on z/OS means copying the right load modules into the right libraries, binding DB2 packages, and telling CICS to pick up the new versions — in the right order, with…

Track your progress and earn a certificate.
Free account, 90 quiz questions for this subject.

Start this subject