CoreChecklists
Deployment checklist
What must be in place before a change goes to production.
- Source promoted through the correct path, not copied by hand
- Compiled with production options in the production build
- Load module in the right library, and the STEPLIB in the job points at it
- DB2 packages bound in this environment, in the right collection
- CICS programs defined, and a NEWCOPY planned or automated
- JCL and procedure changes promoted alongside the code
- Copybook changes: every dependent program identified and recompiled
- Scheduler definitions updated if steps, names or dependencies changed
- Back-out plan written AND verified — does the previous version still exist?
- Verification steps defined: what will you check after deployment, and how?
- Someone available to verify after the change window
- Change record approved, with the correct type and window
Stuck on something else?
Ask the community or search the full course.