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 approval, and with a fast way back.
What a deploy actually does
- Copy load modules from the artifact into the target load library.
- Bind the DB2 packages for any changed programs that use SQL.
- Tell CICS to load the new copy, for example with
CEMT SET PROGRAM(PAYCALC) PHASEIN, so new transactions use the new version. - Update batch JCL or PROCs if they changed.
- Record what was deployed, when, by which pipeline run, and who approved it.
Deployment tools such as IBM UrbanCode Deploy or IBM Wazi Deploy, or scripts built on Zowe CLI, perform these steps from a manifest, so they happen the same way every time and in every environment.
CEMT SET PROGRAM(PAYCALC) PHASEIN STATUS: RESULTS - OVERTYPE TO MODIFY Prog(PAYCALC ) Leng(0000041232) Cob Pro Ena Pri NORMAL
Gates before production
- All tests in earlier stages passed for this exact artifact.
- An approver signs off in the pipeline tool, which records the approval.
- The deploy runs inside the agreed change window if your site still uses one.
- Monitoring is watched for the first runs: batch return codes, CICS abends, response times.
Order matters
If a change adds a DB2 column, the database change must be in place before the program that reads it. If a copybook layout changes, every program and file that shares it must move together. Good pipelines deploy related changes as one package and stop if any step fails.
Common mistakes
The new load module is in the library, but CICS keeps running the old copy in memory until NEWCOPY or PHASEIN is issued.
The program fails as soon as it references a column that does not exist yet. Deploy schema changes first.
A backout that has never been tried fails at the worst time. Rehearse it in a test environment.
What you will see at work
- On deploy night you may be watching SDSF and CICS logs while the pipeline runs — automation does not remove the need to check.
- Change records often link directly to the pipeline run, giving auditors the commits, tests and approvals in one place.
- If a deploy partly fails, stop and roll back the whole package rather than fixing pieces by hand.
Key terms
Check your understanding.
Take this lesson's quiz and save your progress. Free.