# IBM i (AS/400) OS Upgrade Readiness Checklist > Source: https://netray.co/tools/ibm-i-os-upgrade-readiness-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A grouped checklist covering planning, backup, compatibility, the upgrade weekend and validation for an IBM i operating system upgrade. ## Category oracle ## Erp Oracle JD Edwards World ## Audience - IBM i administrator - IT manager - JDE World technical lead ## Tool **Kind:** checklist **Groups:** #### Planning and compatibility **Items:** **Text:** Record the current release, PTF group levels and hardware model **Critical:** true **Text:** Confirm the target release supports your hardware (check IBM documentation) **Critical:** true **Text:** Confirm the target release is supported by your JD Edwards World release level **Critical:** true List every third-party product and request vendor confirmation for the target release **Text:** Check licensed program keys and any software keys tied to release or serial number **Critical:** true List installed licensed programs and remove ones no longer used Review IBM Preventive Service Planning information for the target release Agree the outage window with the business and the batch schedule owners **Text:** Decide whether to upgrade a test partition first **Critical:** true #### Backups and recovery **Items:** **Text:** Run a full system save (SAVSYS) and verify the media or image catalog **Critical:** true **Text:** Run SAVSECDTA and SAVCFG before the change **Critical:** true Run a full save of data and program libraries including the IFS Print the current system values, network attributes and TCP/IP configuration Document the library list and subsystem startup of the JD Edwards World environments Record the disk configuration and ASP layout **Text:** Write a back-out plan and agree who decides to use it **Critical:** true Test that you can read the backup media on another system if possible #### System preparation **Items:** **Text:** Check there is enough free disk space for the upgrade **Critical:** true Apply the required cumulative PTF package and groups for the current release Run object conversion planning for programs created on old releases Clean up old journal receivers, spool files and temporary libraries Verify no damaged objects exist (check with the system integrity tools) **Text:** Order the target release media or download the images in advance **Critical:** true **Text:** Make sure console access and a service tools profile are available **Critical:** true Confirm vendor support contacts are reachable during the window #### Upgrade window **Items:** **Text:** Notify users, end interactive and batch work, and stop JDE World subsystems **Critical:** true End subsystems and take the system to restricted state if required Follow the IBM instructions for the install of the new release in order Apply PTFs for the target release after the install Monitor progress through the console and record any messages Perform an IPL and confirm the controlling subsystem started normally #### Validation after upgrade **Items:** **Text:** Verify operating system release and installed licensed programs **Critical:** true Check QHST and QSYSOPR for errors after the IPL **Text:** Start the JD Edwards World subsystems and run a sample batch job **Critical:** true Run a test of printing, FTP, ODBC and any scheduled interfaces Confirm third-party tools and license keys work **Text:** Run a post-upgrade save and keep the pre-upgrade save until stable **Critical:** true Hold a review meeting and update the runbook **Scoring Note:** Aim to complete every critical item before the upgrade window opens. If more than two critical items are open, move the date. ## Content **Intro:** An IBM i release upgrade rarely fails because of the installation itself. It fails on missing keys, unsupported third-party software, no usable backup or a weak back-out plan. This checklist walks through the full sequence. **Sections:** #### How to use it **Body:** Tick items off as you go and use the critical flags to decide whether you are ready. Export the list to PDF for the change record or to Excel to assign owners and dates. Work through planning and compatibility several weeks ahead, because vendor answers and key requests take the longest. Preparation and backups come in the last two weeks, and the upgrade window group is used on the day. #### What usually blocks an upgrade **Body:** Third-party license keys are the most common surprise. Some products tie keys to the system serial number and release, so a new release needs a new key before the upgrade. The second is software that is no longer supported on the target release, including old JD Edwards World add-ons and in-house programs that call removed APIs. The third is not enough disk space for the upgrade. **Bullets:** - License keys tied to release - Vendor support for the target release - Free disk space - Hardware support for the target release #### Testing on a separate partition **Body:** If you have a development or disaster recovery partition, upgrade it first and run the nightly batch cycle, month end jobs and interfaces there. Defects found there cost hours, defects found in production cost days. Without a test partition, at least restore a copy of key libraries to a spare system and run the main batch jobs against it. #### Common mistakes **Body:** Skipping the full system save because the data libraries were saved nightly leaves you unable to recover the operating system. Deleting the pre-upgrade save too soon removes your rollback. Changing too many things in one weekend, such as new hardware, a new release and a JDE World update, makes problems hard to isolate. Do one major change at a time where possible. **Cta:** If you are planning a move off IBM i or a larger JD Edwards World modernization, Netray can help with data extraction and private AI on top of the existing data. **Faq:** #### How long does an IBM i upgrade take? **Answer:** It depends on the system size, the release jump and the media. Many shops plan a full weekend including backups, installation, PTFs and validation. A test partition run will give you the real timing for your environment, so measure it there. #### Can I skip releases? **Answer:** IBM documents which direct upgrade paths are supported for each release. Some jumps are supported and some need an intermediate step. Check the IBM upgrade documentation for your current and target release before you plan. #### Do I need a new JD Edwards World version for a new IBM i release? **Answer:** Not always, but you must confirm the combination is supported. Check the vendor support matrix for your World release level and the target IBM i release, and ask the vendor in writing if the documentation is unclear. #### What should I keep after the upgrade? **Answer:** Keep the pre-upgrade full system save and the configuration printouts until the system has run a full business cycle including month end without issues. Then follow your own retention policy for old backups. ## Search terms ibm i upgrade checklist, as400 os upgrade checklist, ibm i release upgrade planning, ibm i 7.5 upgrade, as400 PTF upgrade steps, jde world ibm i upgrade, ibm i upgrade backup, as400 upgrade test plan --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json