7.3 Items to Be Aware of When Upgrading to IBM i 7.3 – Part 2

This is part 2 of a 4 part series on the new IBM i 7.3 Upgrade. Links to the rest of the series are listed a the bottom of this article.

things to know before you upgrade to IBM i 7.33. Increase the Licensed Internal Code space

If you are upgrading from 7.1 to 7.3 you need to increase the Licensed Internal Code space on the load source disk.  All server models with IBM i 7.1 or earlier releases require more reserved storage before IBM i 7.2 or 7.3 can be installed. Your upgrade will stop during the installation if you do not allocate the additional space.

You can do this by issuing the GO LICPGM on the command line, selecting option 5 on the menu to Prepare for upgrade, and then selecting the option to increase License Internal Code space.  Remember, your load source will need to be at least 70GB for a physical disk drive and 35GB for a virtual disk drive.

4. Required PTFs

While I think it goes without saying that you should always get to the latest PTFs on the release you are upgrading from before starting your upgrade, this release of IBM i 7.3 is no different.  As you plan for your IBM 7.3 installation or upgrade ensure that you review the “Required PTFs for upgrading to IBM 7.3” topic within the IBM i and Related Software section of the IBM developerWorks® wiki.

To review the “Required PTFs for upgrading to IBM i 7.3”, go to this wiki and select Updates and PTFs.

If you are upgrading from IBM i 7.1 for example, you need to load and apply certain PTFs to be able to accept online software agreements. If you are using image catalogs to upgrade from either IBM i 7.1 or IBM i 7.2 certain PTFs are required. Both of these preparation steps are included in the Installing, Upgrading, or Deleting IBM i Guide. You always want all the IBM i fixes that have resolved known problems installed before you start the upgrade.

This was Part 2 of a four part series. See the following posts below:

Upgrade_Assessment

Leave a Reply

Your email address will not be published. Required fields are marked *