# z/OS Software Product Installation Checklist

Published with SARATH.KB. Adapt every item to the vendor documentation and the target site's change, security and recovery procedures.

## A. Scope and source control

- [ ] Confirm canonical product name, release, PID/FMIDs/components and only the features in scope
- [ ] Record vendor program directory / install guide / release-note revisions and authoritative download source
- [ ] Preserve original package/archive/order evidence and checksum when supplied
- [ ] Classify delivery: SMP/E-managed, non-SMP/E or hybrid
- [ ] Identify supplied jobs/members/scripts that will be customized; preserve untouched originals
- [ ] Define business/application owner, implementation owner and support/vendor contacts

## B. Prerequisite matrix

- [ ] Confirm target z/OS release and hardware/function prerequisites
- [ ] Confirm dependent product/runtime release requirements
- [ ] Receive/review current enhanced HOLDDATA and relevant FIXCAT/required service for IBM SMP/E software
- [ ] Identify prerequisite/co-requisite FMIDs and PTFs
- [ ] Check Java/USS/zFS/storage/database/network/TLS prerequisites
- [ ] Check coexistence or sysplex requirements when multiple systems/releases interact

## C. Site design

- [ ] Map vendor HLQs to site naming/SMS standards
- [ ] Define CSI/global/target/DLIB zones and DDDEFs for SMP/E-managed software
- [ ] Size target/DLIB/runtime/work datasets and zFS including growth/backup policy
- [ ] Define PROCLIB/STC names, symbols and startup/shutdown dependencies
- [ ] Document PARMLIB/subsystem/APF/LINKLIST/LPA/LLA changes and activation method
- [ ] Define RACF STARTED identity, DATASET/general-resource/USS access and certificates/keyrings
- [ ] Define ports/interfaces/DNS/firewall/AT-TLS requirements
- [ ] Define WLM classification, automation, monitoring, logs and health checks
- [ ] Define runtime-library copy/synchronization process if execution does not use SMP/E target libraries

## D. Install / stage

- [ ] Back up or preserve the pre-install state required for rollback
- [ ] For SMP/E: RECEIVE product/service and current HOLDDATA into correct CSI
- [ ] For SMP/E: run APPLY CHECK using the same intended selection/options as implementation
- [ ] Resolve ERROR/SYSTEM/USER HOLDs, requisites, MODID and link-edit problems; document approved BYPASS decisions
- [ ] For SMP/E: APPLY only approved FMIDs/service and review messages plus RC
- [ ] For non-SMP/E: stage/unpack package in controlled path and retain installer logs
- [ ] For non-SMP/E: identify every dataset/file/permission/database change the installer performed
- [ ] Keep vendor code and site configuration separate where product design permits

## E. Integrate and activate

- [ ] Implement RACF/security before first production start
- [ ] Implement PROCLIB/PARMLIB/APF/LINKLIST/LPA/subsystem changes in controlled steps
- [ ] Mount/verify required zFS and ownership/permissions
- [ ] Implement ports/TLS/certificates and verify endpoints
- [ ] Configure automation/WLM/monitoring
- [ ] Start product in dependency order
- [ ] Verify documented product ready/initialization messages and no unresolved WTORs/errors
- [ ] Prove the active runtime uses the intended new libraries/version

## F. Validate and close

- [ ] Run representative functional smoke test
- [ ] Validate all critical product integrations/dependencies
- [ ] Check CPU/storage/I/O/logging baseline and health-check/monitoring state
- [ ] Test documented stop/start or restart path
- [ ] Record installed product release/FMID/service and runtime evidence
- [ ] Record datasets/zFS/STCs/members/ports/security resources in inventory
- [ ] Retain CHECK/APPLY/installer logs and validation evidence
- [ ] Keep tested backout point through stabilization; defer ACCEPT/destructive cleanup according to policy
- [ ] Update recovery/runbook and handover documentation