# EOS & z/OS Compatibility Assessment Checklist

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

## A. Discover and normalize

- [ ] Obtain current software inventory from available discovery sources
- [ ] Retain raw discovered product/component names
- [ ] Map feature/component/FMID to canonical lifecycle-managed product
- [ ] Record vendor and product identifier where available
- [ ] Resolve duplicate/historic entries and system scope

## B. Prove installed version

- [ ] Query SMP/E CSI/FMIDs for SMP/E-managed software
- [ ] Use product VERSION/STATUS command when available
- [ ] Check active startup messages/job logs
- [ ] Check runtime load-library path and module/version evidence when needed
- [ ] Check USS manifest/properties/build evidence for USS/Java products
- [ ] Use asset-discovery/TADz-style reports as discovery evidence, not unquestioned truth
- [ ] Record evidence source and evidence date for the chosen installed release
- [ ] Mark conflicts/unknowns for manual resolution

## C. Lifecycle evidence

- [ ] Find authoritative vendor lifecycle/support source
- [ ] Record GA date where relevant
- [ ] Record end of standard support/EOS separately from end of marketing
- [ ] Record extended/sustaining support availability and limitations
- [ ] Record latest GA/supported release
- [ ] Store source URL/document and verification date
- [ ] If no public lifecycle date exists, mark unconfirmed/vendor validation required rather than guessing

## D. Target z/OS release compatibility

- [ ] Define target z/OS release
- [ ] Check vendor/IBM supported product-release table or compatibility matrix
- [ ] Identify minimum product release for target z/OS
- [ ] Check dependent Java/Db2/CICS/MQ/runtime requirements
- [ ] Check sysplex/coexistence restrictions
- [ ] Distinguish release-level support from service-level prerequisites

## E. Required service

- [ ] Receive current enhanced HOLDDATA for IBM SMP/E environments
- [ ] Identify relevant IBM.TargetSystem-RequiredService FIXCAT
- [ ] Identify relevant IBM.Coexistence FIXCAT where applicable
- [ ] Review IBM.ProductInstall-RequiredService where installing a target product
- [ ] Run REPORT MISSINGFIX against each relevant CSI/zone
- [ ] Review current IBM preventive-service/PSP replacement guidance, Red Alerts/security information and vendor service notes
- [ ] Record exact PTF/FIXCAT/vendor-service requirement with evidence

## F. Remediation roadmap

- [ ] Classify current / upgrade available / EOS approaching / EOS passed / target-zOS incompatible / service required / evidence incomplete
- [ ] Assign owner and next action
- [ ] Set target product release/service
- [ ] Sequence by dependency order
- [ ] Prioritize unsupported and near-EOS business-critical products
- [ ] Track vendor-contact actions for unpublished information
- [ ] Schedule periodic lifecycle/source re-verification