IBM i (AS/400) OS Upgrade Checklist, Free

0%

0 of 38 items complete

15 critical items still open - these are the highest-risk gaps.

Download checklist:

Planning and compatibility

Record the current release, PTF group levels and hardware modelCRITICALConfirm the target release supports your hardware (check IBM documentation)CRITICALConfirm the target release is supported by your JD Edwards World release levelCRITICALList every third-party product and request vendor confirmation for the target releaseCheck licensed program keys and any software keys tied to release or serial numberCRITICALList installed licensed programs and remove ones no longer usedReview IBM Preventive Service Planning information for the target releaseAgree the outage window with the business and the batch schedule ownersDecide whether to upgrade a test partition firstCRITICAL

Backups and recovery

Run a full system save (SAVSYS) and verify the media or image catalogCRITICALRun SAVSECDTA and SAVCFG before the changeCRITICALRun a full save of data and program libraries including the IFSPrint the current system values, network attributes and TCP/IP configurationDocument the library list and subsystem startup of the JD Edwards World environmentsRecord the disk configuration and ASP layoutWrite a back-out plan and agree who decides to use itCRITICALTest that you can read the backup media on another system if possible

System preparation

Check there is enough free disk space for the upgradeCRITICALApply the required cumulative PTF package and groups for the current releaseRun object conversion planning for programs created on old releasesClean up old journal receivers, spool files and temporary librariesVerify no damaged objects exist (check with the system integrity tools)Order the target release media or download the images in advanceCRITICALMake sure console access and a service tools profile are availableCRITICALConfirm vendor support contacts are reachable during the window

Upgrade window

Notify users, end interactive and batch work, and stop JDE World subsystemsCRITICALEnd subsystems and take the system to restricted state if requiredFollow the IBM instructions for the install of the new release in orderApply PTFs for the target release after the installMonitor progress through the console and record any messagesPerform an IPL and confirm the controlling subsystem started normally

Validation after upgrade

Verify operating system release and installed licensed programsCRITICALCheck QHST and QSYSOPR for errors after the IPLStart the JD Edwards World subsystems and run a sample batch jobCRITICALRun a test of printing, FTP, ODBC and any scheduled interfacesConfirm third-party tools and license keys workRun a post-upgrade save and keep the pre-upgrade save until stableCRITICALHold a review meeting and update the runbook

Aim to complete every critical item before the upgrade window opens. If more than two critical items are open, move the date.

Second pair of eyes on your upgrade plan

Optional: send your plan and we will comment on gaps in the compatibility and back-out sections.

Optional. The tool and every export work without this. No spam.

How to use it

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

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.

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

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

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.

Frequently Asked Questions

How long does an IBM i upgrade take?

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?

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?

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?

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.

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.

Talk to an Expert Explore More Free Tools

Related Tools

Oracle

More Oracle tools

See all

IBM i (AS/400) OS Upgrade Readiness Checklist