You can do these preparatory activities days or a few weeks before you schedule the installation of the new release on your system. Allow ample time for
completing these activities. The activities are:
1. The Beginning Tasks (Table 10 on page 20) 2. Order and Apply PTFs (Table 11 on page 21)
3. Choose the Manual or Automatic Installation Process (Table 12 on page 22) 4. Use Prepare for Install (Table 13 on page 22)
5. Additional Considerations (Table 14 on page 23) 6. The Ending Tasks (Table 15 on page 23)
Check off the tasks as you complete them so you do not overlook any of them.
This section includes more information about each task, starting at the page indicated. Also, the appendices provide useful general information.
For logical partitions only
If you are setting up logical partitions, you will need to plan in advance of your installation for a basic
understanding of logical partitions and for your software and hardware requirements. Refer to the articles about logical partitions in the AS/400 Information Center, SK3T-2027, within the System Administration, Availability and Maintenance topic. You also can view this information on the Internet at: http://www.as400.ibm.com/infocenter.
Additionally, refer to the articles at the Logical Partitioning Web site: http://www.as400.ibm.com/lpar. For a brief description within this book, read “About Logical Partitions” on page 220.
For a system with logical partitions, you must load the relevant PTFs on each secondary partition, then set them for apply delay. Power down all secondary partitions. Go to the primary partition, load the relevant PTFs and apply them. Then perform an initial program load (IPL) of the primary partition (a full system IPL).
You may have different PTFs for different licensed programs on different partitions. If a PTF is related to a logical partition, all partitions must have that PTF. Otherwise, you may have some different PTFs for Licensed Internal Code on different partitions. You may have some different PTFs for OS/400 on different partitions. However, you must have Licensed Internal Code and OS/400 at V4R4M0 or newer on all partitions. For directions to do this correctly, use the article Managing Logical Partitions in the AS/400 Information Center, mentioned above.
Table 10. Beginning Tasks
Beginning Tasks (detailed information starting on page 24)
Tasks More Information
__ 1. Review Memo to Users and order PSP and PTF documents.
Review the Memo to Users for potential incompatibilities with V4R5M0 software. Also order additional planning documents that you may need to use. Refer to “Locate and Review Information” on page 24.
__ 2. Verify your software order and license keys.
Verify that you received all of the software you ordered. Refer to “Verifying Your Software Order” on page 27. Also, ensure that you have software license keys for any keyed products that you have ordered and intend to install.
__ 3. Change system values to avoid errors before installing or deleting software or PTFs, or when recovering your system.
Change any system values as needed for the planning or installation process. Refer to “Setting System Values Before Installing” on page 32.
__ 4. Move IBM-supplied product libraries to system ASP or delete duplicated IBM-supplied product libraries.
Refer to “Moved or duplicated IBM-supplied product libraries” on page 33.
__ 5. For 3995 optical library users, save or release held optical files.
If you use a 3995 optical library, check for and resolve any held optical files.
Refer to“3995 Optical Library Users” on page 34.
__ 6. If you are migrating to a newer Client Access package, or you plan to delete or replace Client Access products, ensure that there are not any user-created subdirectories.
If any user-created subdirectories exist, the install or delete operation may fail. You can use the WRKLNK command to remove all user-created subdirectories for these products.
__ 7. If you use OS/400 Advanced 36, 5769SS1 option 20, you mustmigrate your System Support Programs (SSP) programs and data before installing V4R5M0.
V4R5M0 does not support 5769SS1 (OS/400) option 20. It is deleted when you install V4R5M0. IBM recommends migrating your SSP programs and data to either OS/400 System/36 Environment or native OS/400. Normal SSP utilities can be used to save libraries, files and folders from the SSP to tape or diskette. Then the AS/400 Migration Assistant can be used to restore the libraries, files, and folders to the System/36 Environment on OS/400.
The following information describes this process in greater detail:
v Informational authorized program analysis report (APAR) II09900 v SC41-4151-00 OS/400 System/36 Migration Assistant V3R6 v SC41-4152-00 System/36 Migration Planning V3R6
__ 8. If you use OS/400 Lotus Notes Enhanced Integration, 5769SS1 (OS/400) option 24, you must migrate your data before installing V4R5M0.
V4R4M0 and newer releases do not support OS/400 option 24. It is deleted when you install V4R5M0. IBM recommends migrating your data to Lotus Domino for AS/400. For detailed instructions about how to migrate your data, refer to the topic″Migrating to Lotus Domino for AS/400″ at following Internet location:
http://www.as400.ibm.com/techstudio
Table 10. Beginning Tasks (continued)
Beginning Tasks (detailed information starting on page 24)
__ 9. If you have Integration for NetWare, 57xx-SA3, or OS/2 Warp Server for AS/400, 57xx-XZ1, you must migrate your data.
Attention!Once you install OS/400 V4R5M0, OS/400 Integration for Novell NetWare (5769-SA3), will no longer work. You cannot use Restore License Program to load a previous release of this product onto an AS/400 with V4R5M0 or later version of the operating system. To avoid losing data that depends on this product, migrate that data from your server to an accessible location before upgrading to V4R5M0.
You must migrate to an alternative product before the end of service dates for Integration for NetWare (57xx-SA3) and OS/2 Warp Server for AS/400 (57xx-XZ1). These products will be deleted when you upgrade to V4R5M0.
Refer to the Novell Support Life Cycle Product Forecast for information regarding their end of support dates for Novell NetWare 4.1 on the Internet:
http://support.novell.com/lifecycle/forecast.htm
For assistance in migrating your data to AS/400 Netserver, refer to the AS/400 redbook SG24-5196, Advantage AS/400 NetServer. For alternative ideas to help migrate your data, see information APAR II11689. Alternative products that you can use are AS/400 Netserver, which uses Server Message Block (SMB) or AS/400 Integration for Windows Server on an Integrated Netfinity Server.
You may choose to migrate to an external PC server. IBM still supports AS/400 Netware Enhanced Integration on remote PC servers. For more information about AS/400 and Netware, refer to:
http://www.as400.ibm.com/netware
Table 11. Order and apply program temporary fixes (PTFs)
Order and apply PTFs (detailed information starting on page 34)
Tasks More Information
__ 1. Permanently apply any temporarily applied PTFs.
Permanently apply any PTFs that are temporarily applied to your system.
Apply any required Client Access PTFs. Refer to “Permanently Apply Program Temporary Fixes (PTFs)” on page 34.
__ 2. Order and apply PTFs for network interoperability. Skip this task if you do not have AS/400s operating in a network.
Read “Evaluate Release-Level Interoperability” on page 35, and order and apply PTFs for network interoperability, if you use your system in a network.
__ 3. Apply the Installation Preparation PTFs if you are installing from V4R1. Skip this task if you are not upgrading from a V4R1 system.
If you are upgrading from V4R1M0, apply the Installation Preparation PTFs that are required before installing V4R5M0. Refer to “Preparation Program Temporary Fixes Required Before Installing V4R5M0 Software” on page 37.
__ 4. Order the cumulative PTF package. Skip this task if you have recently received your V4R5M0 software upgrade.
If several weeks have passed since you received your software distribution media, check to see if you have the latest cumulative PTF package for V4R5M0. You should also get the latest HIPER PTFs. Refer to “Ordering the Current Cumulative PTF Package” on page 38.
Table 11. Order and apply program temporary fixes (PTFs) (continued) Order and apply PTFs (detailed information starting on page 34)
__ 5. If you have this product installed, 5769-WSV Integration for Windows Server, then you must use the Level Check command to upgrade your server to the current level. Skip this task if you do not have 5769-WSV Integration for Windows Server installed.
When you install a new version of AS/400 Integration for Windows Server, you need to upgrade all your existing Windows servers to that level. This requires first applying the latest cumulative PTF package. (See the previous task to determine whether you have the latest cumulative PTF package.) Then, you must perform a level check. This must be done before installing a new release of the product, 5769-WSV Integration for Windows Server. If your server is not up to the current level code when you perform the Level Check command, the PTFs will be automatically applied.
To use the Level Check command you must be a Windows server
administrator. For instructions to perform the Level Check command, refer to the section “Installing upgrades to Windows servers when you upgrade AS/400 Integration for Windows Server” in Chapter 3 of the book AS/400 Integration for Windows Server - Setup, SC41-5439. Or refer to the Information Center topic and follow these links (in order): Network Operating Systems;
Windows Server on AS/400; Installation and configuration of AS/400 Integration for Windows Server; Upgrading Windows servers on AS/400.
__ 6. Order group PTFs.
When new PTFs affecting a system software function become available, group PTFs are dynamically updated. Find a list of the group PTFs and order them. For a description of group PTFs and ordering information, refer to “Ordering Group PTFs” on page 39.
Table 12. Choose the Manual or Automatic Installation Process
Choose the Manual or Automatic Installation Process
If you are replacing a release of software, choose which installation procedure you will use. Refer to “Choosing Manual or Automatic Installation” on page 40. Skip this task if you are installing software on a new system, installing additional licensed programs or secondary languages, or changing your primary language.
Table 13. Use Prepare for Install
Use Prepare for Install (detailed information starting on page 40)
Tasks More Information
__ 1. Create and customize an installation list. Skip this task if you are not using automatic installation.
Refer to “Creating and Customizing an Installation List” on page 40.
__ 2. Merge additional licensed programs into your installation list. Perform this task only when you have already created an installation list (as in the previous task) and only when you have additional licensed programs to add to the list.
Skip this task if you are not using automatic installation.
Refer to “Merging Additional Licensed Programs into the Installation List”
on page 44.
__ 3. Clean up your system. Clean your system of items you no longer use. You should do this before you estimate your storage requirements. Refer to “Cleaning Up Your System Storage Space” on page 45.
Table 13. Use Prepare for Install (continued)
Use Prepare for Install (detailed information starting on page 40)
__ 4. Evaluate your disk storage needs.
Determine if you have adequate storage to install the new software. Refer to
“Evaluating Your Disk Storage Needs” on page 47.
__ 5. Verify the integrity of system objects.
Verify the integrity of system objects that are needed by the installation process. Refer to “Verifying the Integrity of System Objects” on page 49.
Table 14. Additional Considerations
Additional Considerations (detailed information starting on page 50)
Tasks More Information
__ 1. Estimate the installation time. Estimate the amount of time you need to install this release of software.
Refer to “Estimating Installation Time” on page 50.
__ 2. Gather performance information.
Gather performance information about your current system to use as a checkpoint for future comparison. Refer to “Gathering Performance Information” on page 51.
__ 3. Use the Softcopy Library. Skip this task if you are not using the Softcopy Library.
If you are planning to use the AS/400 softcopy library CD-ROM, refer to
“Prepare to Install Softcopy Information” on page 52.
__ 4. Plan for national language support.
If you are changing the primary language of the system or adding a secondary language, refer to “Planning for National Language Support” on page 53.
__ 5. Identify changes to IBM-supplied objects.
If you have made changes to IBM-supplied objects, you need to identify the changes and take appropriate action. Some job description and subsystem customizations can be kept. Refer to “Identifying Changes to IBM-Supplied Objects” on page 55.
__ 6. Basic system hardware considerations.
Ensure that you know how to operate any hardware devices which you will be using during the upgrade. Refer to “Basic System Hardware
Considerations” on page 57.
Table 15. Ending Tasks
Ending Tasks (detailed information starting on page 60)
Tasks More Information
__ 1. Ensuring two-phase commit integrity.
If your system participates in a network, resolve any database
resynchronizations that are pending. Refer to “Ensuring Two-Phase Commit Integrity” on page 60.
__ 2. Stop the Integrated Netfinity Server.
If your system has an active Integrated Netfinity Server for AS/400, deactivate it during the installation process. Refer to “Stopping the
Integrated Netfinity Server for AS/400 and Ending Application Servers” on page 61.
__ 3. Remove tapes from tape drives, if you are using optical media.
Remove other unnecessary media.
If you are using optical media, remove all extraneous tape media from the tape drives before installation.
Prior to performing a full system IPL, remove all unnecessary media from devices that are attached as possible source-D IPL devices. If you have any secondary logical partitions and intend to perform only a secondary
partition IPL, then this applies only to that partition. However, if you intend to perform a full system IPL (primary partition IPL), then this applies to
Table 15. Ending Tasks (continued)
Ending Tasks (detailed information starting on page 60)
__ 4. Save your system. Save the system to ensure that you can perform a recovery if needed. For detailed instructions to save your entire system, refer to″Details: Saving everything″ in the Information Center. See “Prerequisite and Related Information” on page xii for locating the Information Center. Or, refer to
″Using Save menu option 21″ in the book Backup and Recovery, SC41-5304.
Also, for a brief discussion, refer to “Notes About Saving your System” on page 62 in this book.
When you have completed these planning tasks, you will be ready to start your installation.