AS/400-iSeries Starter Kit

One task you’ll perform at some time on your AS/400 is installing a new release of OS/400 and your IBM licensed program products. The good news is that this process is “a piece of cake” today compared with the effort it required back when IBM first announced and delivered the AS/400 product family. No longer must you IPL the system more than a dozen times to complete the installation. When you load a new operating-system release today, you can have the system perform an automatic installation or you can perform a manual installation — and either method normally requires only one machine IPL.

To prepare you for today’s approach, here’s a step-by-step guide to planning for and installing a new release of OS/400 and new IBM licensed program products. I cover the essential planning tasks you should accomplish before the installation, as well as the installation process itself.

Planning Is Preventive Medicine

Just as planning is important when you install your AS/400 system the first time, planning for the installation of a new release offers the benefits of any preventive medicine — and it’s painless! You’ll no doubt be on a tight upgrade schedule, with little time for unexpected problems. By planning ahead and following the suggestions in this chapter, you can avoid having to tell your manager that the AS/400 will be down longer than expected while you recover the operating system because something was missing or damaged and prevented completing the installation.

Before I describe the specific steps that will ensure a successful system upgrade, there’s one other important preventive measure to note: Unless it’s impossible, you should avoid mixing a hardware upgrade and a software upgrade — don’t perform both tasks at the same time. If a new AS/400 model requires a particular release of OS/400 and that release is compatible with your older hardware, first install the new release on your older hardware, and then upgrade your hardware at another time to avoid compounding any problems you might encounter.

The Planning Checklist

Every good plan needs a checklist, and the list of steps in Figure 1, below, is your guide in this case. You can find a similar list in IBM’s AS/400 Software Installation (SC41-5120).

Because IBM makes minor changes and improvements to the installation process for each release of the operating system, each new release means a new edition of the Software Installation manual. To ensure you have the latest information about installing a new release, you should read this chapter along with the manual. Read the chapter entirely to get a complete overview of the process before performing the items on the checklist. Note: If IBM’s instructions conflict with those given here, follow IBM’s instructions.

Step 1: Is Your Order Complete?

One of the first things you’ll do is check the materials IBM shipped to you to make sure you have all the pieces you need for the installation. As of this writing, you should receive these items:

• distribution media (normally CD-ROM)
• Media Distribution Report
• Read This First
• Memo to Users for OS/400
• AS/400 PTF Shipping Information Letter
• individual product documentation
• AS/400 Software Installation

Don’t underestimate the importance of each of these items.

Examine the CD-ROMs to make sure they’re not physically damaged, and then use the Media Distribution Report to determine whether all listed volumes are actually present. For each item on the CD-ROMs, the Media Distribution Report identifies the version, release, and modification level; licensed program name; feature number (e.g., 5769SS1, 5769RG1); and language feature code. For V4R5, you’ll find the version number listed as V4 (Version 4) in the product name; the release number and modification level are represented as R05M00 (Release 5, Modification Level 0) on the report.

Note that the Media Distribution Report lists only priced features. Some features, such as licensed internal code and base OS/400, are shipped with no additional charge. The report contains no entries for these items, nor does it contain entries for locked products.

The Read This First document is just what it sounds like: a document IBM wants you to read before you install the release, and preferably as soon as possible. This document contains any last-minute information that may not have been available for publication in the Memo to Users for OS/400 or in any manual.

The Memo to Users for OS/400 describes any significant changes in the new release that could affect your programs or system operations. You can use this memo to prepare for changes in the release. You’ll find a specific section pertaining to licensed programs that you have installed or plan to install on your system.

You’ll want to read the AS/400 PTF Shipping Information Letter for instructions on applying the cumulative program temporary fix (PTF) package. You also may receive additional documentation for some individual products; you should review any such documents because they may contain information unique to a product that could affect its installation.

In addition to reviewing the deliverables listed above, you may want to review pertinent information found in the AS/400 Preventive Service Planning Information document. This document lists additional preventive service planning documents you may want to order. To obtain it, order PTF SF98 vrm, where v = version, r = release, and m = modification level for the new release. (For information about PTF ordering options, see Chapter 6, “Introduction to PTFs.”)

After reviewing this information, you should verify not only that you can read the CD-ROMs but also that they contain all necessary features. An automated procedure, Prepare for Install (available through an option on the Work with Licensed Programs panel), greatly simplifies this verification process compared with earlier releases, which involved considerable manual effort.

The panel in Figure 2, below, shows the installation-preparation procedures supported by Prepare for Install. One of the panel’s options compares the programs installed on your system with those on the CD-ROMs, generating a list of preselected programs that will be replaced during installation. You can inspect this list to determine whether you have all the necessary features.

  
                       Prepare for Install
                                                 System:   AS400
 Type option, press Enter.
   1=Select

 Opt     Description
  _      Work with user profiles
  _      Work with licensed programs for target release
  _      Display licensed programs for target release
  _      Work with licensed programs to delete
  _      List licensed programs not found on media
  _      Verify system objects
  _      Estimated storage requirements for system ASP


                                                          Bottom
 F3=Exit   F9=Command line   F10=Display job log   F12=Cancel   
	

To perform this verification, take these steps:

1. Arrange the CD-ROMs in the proper order. Chapter 3 of AS/400 Software Installation contains a table specifying the correct order. You should refer to this table not only for sequencing information but also for any potential special instructions.



2. From the command line, execute the following CHGMSGQ (Change Message Queue) command to put your message queue in break mode:
   

   CHGMSGQ QSYSOPR *BREAK SEV(95)

3. From the command line, execute
   

   GO LICPGM

4. You’ll see the Work with Licensed Programs panel. Select option 5 (Prepare for install), and press Enter.



5. Select the option “Work with licensed programs for target release,” and press Enter.



6. You’ll see the Work with Licensed Programs for Target Release panel. You should



• load the first CD-ROM
• specify 1 (Distribution media) for the Generate list from prompt
• specify the appropriate value for the Optical device prompt
• specify the appropriate value for the Target release prompt
• press Enter

When the system has read the CD-ROM, you’ll receive a message asking you to load the next volume. If you have more CD-ROMs, load the next volume and reply G to the message to continue processing; otherwise, reply X to indicate that all CD-ROMs have been processed.

7. Once you’ve processed all the CD-ROMs, the Work with Licensed Programs for Target Release panel will display a list of the licensed programs that are on the distribution media and installed on your system. Preselected licensed programs (those with a 1 in the option column) indicate that a product on the distribution media can replace a product installed on your system. You can use F11 to display alternate views that provide more detail and use option 5 (Display release-to-release mapping) to see what installed products can be replaced.



8. Press Enter until the Prepare for Install panel appears.



9. Select the option “List licensed programs not found on media,” and press Enter.



10. You’ll see the Licensed Programs Not Found on Media panel. If no products appear in the panel’s list, you have all the media necessary to replace your existing products. If products do appear in the list, you must determine whether they’re necessary. If they’re not, you can delete them (I describe this procedure later when I talk about cleaning up your system). If the products are necessary, you must obtain them before installation. Make sure you didn’t omit any CD-ROMs during the verification process. If you didn’t omit any CD-ROMs, compare your media labels with the product tables in AS/400 Software Installation and check the Media Distribution Report to determine whether the products were shipped (or should have been shipped) with your order.



11.    Exit the procedure.

Step 2: Manual or Automatic?

Before installing the new release, you need to determine whether you’ll perform an automated or a manual installation. The automatic installation process is the recommended method and the one that minimizes the time required for installation. However, if you’re performing any of the tasks listed below, you should use the manual installation process instead.

• adding a disk device using device parity protection, mirrored protection, or user auxiliary storage pools (ASPs)
• changing the primary language that the operating system and programs support (e.g., changing from English to French)
• creating logical partitions during the installation
• using tapes created with the SAVSYS (Save System) command
• changing the environment (AS/400 or System/36), system values, or configuration values. These changes differ from the others listed here because you can make them either during or after the new-release installation. To simplify the installation, it’s best to automatically install the release and then manually make these changes.

The automatic installation will install the new release of the operating system and any currently installed licensed program products.

Step 3: Permanently Apply PTFs

One step that will save you time later is to permanently apply any PTFs that remain temporarily applied on your system. Doing so cleans up the disk space occupied by the temporarily applied PTFs. That disk space may not be much, but now is an opportune time to perform cleanup tasks. For more specific information about applying PTFs, see Chapter 6.

Step 4: Clean Up Your System

In addition to permanently applying PTFs, you should complete several other cleanup procedures. These tasks not only promote overall tidiness but also help ensure you have enough disk space for the installation. Consider these tasks:

• Delete PTF save files and cover letters. To delete these items, you’ll use command DLTPTF. Typically, you’ll issue this command only for products 5769999 (licensed internal code) and 5769SS1 (OS/400).



• Delete unnecessary spooled files, and reclaim associated storage. Check all output queues for unnecessary spooled files. A prime candidate for housing unnecessary spooled files is output queue QEZJOBLOG. After deleting these spooled files, reclaim spool storage using command RCLSPLSTG.



• Have each user delete any unnecessary objects he or she owns. You’d be surprised just how much storage some users can unnecessarily consume. If at all possible, have users perform a bit of personal housekeeping by deleting spooled files and owned objects they no longer need.



• Delete unnecessary licensed programs or optional parts. Some licensed programs may be unnecessary for reasons such as lack of support at the target release. To review candidates for deletion, you can use the Prepare for Install panel’s “Work with licensed programs to delete” option. To reach this option, display menu LICPGM (GO LICPGM) and select option 5 (Prepare for install). The “Work with licensed programs to delete” option preselects licensed programs to delete. You can use F11 (Display reasons) to determine why licensed programs are selected for deletion.


I rarely see a system that doesn’t contain unused licensed programs or licensed program parts. For instance, it’s not uncommon to see systems with many unused language dictionaries or unnecessary double-byte character set options. Prepare for Install’s “Work with licensed programs to delete” option won’t preselect such unnecessary options because they are valid options. If for any reason you’re unable to use this procedure to delete licensed programs, you can use option 12 (Delete licensed programs) from menu LICPGM.


• Delete unnecessary user profiles. It’s rarely necessary to delete user profiles as part of installation cleanup, but if this action is appropriate in your environment, consider taking care of it now. The Prepare for install option on menu LICPGM also offers procedures for cleaning up user profiles.



• Use the automatic cleanup options in Operational Assistant. These options provide a general method for tidying your system on a periodic basis.

Step 5: Is There Enough Room?

Once you’ve cleaned up your system, you should verify that you have enough storage to complete the installation. Like most installation-related tasks today, this one is much easier than in earlier releases.

To determine whether you have adequate storage, perform these steps:

1. From the command line, execute

   GO LICPGM

2. You’ll see the Work with Licensed Programs panel. Select option 5 (Prepare for install), and press Enter.



3. Select the option “Estimated storage requirements for system ASP,” and press Enter.



4. You’ll see the Estimated Storage Requirements for System ASP panel. At the Additional storage required prompt, enter storage requirements for any additional software (e.g., third-party vendor software) that you’ll be installing. Include storage requirements only for software that will be stored in the system ASP. Press Enter to continue.



5. You’ll see the second Estimated Storage Requirements for System ASP panel. This panel displays information you can use to determine whether enough storage is available. Compare the value shown for “Storage required to install target release” with the value shown for “Current supported system capacity.” If the value for “Current supported system capacity” is greater than the value for “Storage required to install target release,” you can continue with the installation. Otherwise, you must make additional storage available by removing items from your system or by adding DASD to your system.



6. Exit the procedure.

If you make changes to your system that affect the available storage, you should repeat these steps.

Step 6: Document System Changes

When you load a new release of the operating system, all IBM-supplied objects are replaced on the system. The installation procedure saves any changes you’ve made in libraries QUSRSYS (e.g., message queues, output queues) and QGPL (e.g., subsystem descriptions, job queue descriptions, other work management–related objects). However, any changes you make to objects in library QSYS are lost because all those objects are replaced.

To minimize the possible loss of modified system objects, you should document any changes you make to these objects so that you can reimplement them after installing the new release. I strongly suggest maintaining a CL program that contains code to reinstate customized changes, such as command defaults; you can then execute this program with each release update.

When possible, implement these customizations in a user-created library rather than in QSYS. Although the installation won’t replace the user-created library’s contents, you should regenerate the custom objects it contains to avoid potential problems. Such problems might occur, for example, if IBM adds a parameter to a command. Unless you duplicate the new command and then apply your customization, you’ll be operating with an outdated command structure. In some cases, this difference could be critical. The CL program that customizes IBM-shipped objects should therefore first duplicate each object (when appropriate) and then change the newly created copy.

Step 7: Get the Latest Fixes

Normally, some time passes between the time you order and receive a new release and the date when you actually install it. During this elapsed time, PTFs to the operating system and licensed program products usually become available. To ensure you have the latest of these PTFs during installation, order PTFs for the new release the week before you install the release.

Obtain the latest cumulative PTF package and appropriate group packages. Of the group packages, you should at least order the HIPER group package. (IBM releases HIPER, or High-Impact PERvasive, PTFs regularly — often daily — as necessary to correct high-risk problems.) For more information about ordering PTFs, see Chapter 6.

Step 8: Save Your System

Just before installing the new release (either on installation day or the day before), you should save your system. To be safe, I recommend performing a complete system save (option 21 from the SAVE menu), but this isn’t a requirement. I advise performing at least these two types of saves:

• SAVSYS — saves OS/400 and configuration and security information

• SAVLIB LIB(*IBM) — saves all IBM product libraries

It’s also wise to schedule the installation so that it immediately follows your normally scheduled backup of data and programs. This approach guarantees that you have a current copy of all your most critical information in case any problems with the new installation require you to reinstall the old data and programs.

Installation-Day Tasks

Once you’ve completed step 8, you’re nearly ready to start installing the new AS/400 release. The remaining steps (9 through 12) are best performed on the day of the installation (if they apply in your environment). They, together with the installation process itself, are the focus of the remainder of this chapter. (If you’ll be using a tape drive on installation day, see “Installing from Tape?” (below) for some additional tips.)

Step 9: Resolve Pending Operations

First, if your system participates in a network and runs applications that use two-phase commit support, you should resolve any pending database resynchronizations before starting the installation. Two-phase commit support, used when an application updates database files on more than one system, ensures that the databases remain synchronized.

To determine whether your system uses two-phase commit support, issue the following WRKCMTDFN (Work with Commitment Definitions) command:

WRKCMTDFN JOB(*ALL) STATUS(*RESYNC)

If the system responds with a message indicating that no commitment definitions are active, you need do nothing further. Because the typical AS/400 environment isn’t concerned with two-phase commit support, I don’t provide details about database resynchronization here. For this information, refer to AS/400 Software Installation (SC41-5120).

Next, if your system has a 3995 optical library, check for and resolve any held optical files — that is, files that haven’t yet been successfully written to media. Use the WRKHLDOPTF (Work with Held Optical Files) command to check for such files and either save or release the files.

Step 10: Shut Down the INS

If your system has an active Integrated Netfinity Server for AS/400 (INS), the installation may fail. You should therefore deactivate this server before starting the installation. To do so, access the Network Server Administration menu (GO NWSADM) and select option 3.

Step 11: Verify System Integrity

You should also verify the integrity of system objects required by the installation process. Among the requirements for the installation process are

• System distribution directory entries must exist for user profiles QSECOFR and QLPINSTALL.
• Database cross-reference files can’t be in error.
• User profile QSECOFR can’t contain secondary language libraries or alternate initial menus.

To verify the integrity of these objects, you can use the Prepare for install option on menu LICPGM. This option adds user profiles QSECOFR and QLPINSTALL to the system distribution directory if necessary and checks for errors in the database cross-reference files. To use the option, follow these steps:

1. From the command line, execute command GO LICPGM.



2. The Work with Licensed Programs panel will appear. Select option 5 (Prepare for install), and press Enter.



3. From the resulting panel (Figure 3, below), select the Verify system objects option, and press Enter.



4. If errors exist in the database cross-reference files, the system will issue message “CPI3DA3 Database cross-reference files are in error.” Follow the instructions provided by this message to resolve the errors before continuing.



5. Exit the procedure.

                   Prepare for Install
                                                 System:   AS400
 Type option, press Enter.
   1=Select

 Opt     Description
  _      Work with user profiles
  _      Work with licensed programs for target release
  _      Display licensed programs for target release
  _      Work with licensed programs to delete
  _      List licensed programs not found on media
  _      Verify system objects
  _      Estimated storage requirements for system ASP






                                                           Bottom
 F3=Exit   F9=Command line   F10=Display job log   F12=Cancel	

A couple of items remain to check before you’re finished with this step. If you’re operating in the System/36 environment, check to see whether user profile QSECOFR has a menu or program specified. If so, you must remove the menu or program from the user profile before installing licensed programs.

Also, user profile QSECOFR can’t have a secondary language library (named QSYS29 xx) at a previous release in its library list when you install a new release. If QSECOFR has an initial program, ensure that the program doesn’t add a secondary language library to the system library list.

Step 12: Check System Values

Your next step is to check and set certain system values. Remove from system values QSYSLIBL (System Library List) and QUSRLIBL (User Library List) any licensed program libraries and any secondary language libraries (QSYS29xx). Do not remove library QSYS, QUSRSYS, QGPL, or QTEMP from either of these system values.

In addition, set system value QALWOBJRST (Allow Object Restore) to *ALL. Once the installation is complete, reset the QALWOBJRST value to ensure system security.

Ready, Set, Go!

With the planning behind you, you’re ready to install your new release! The rest of this chapter provides basic instructions for the automatic installation procedure, which is the recommended method. If you must use the manual method (based on the criteria stated in planning step 2), see AS/400 Software Installation for detailed instructions about this process.

When you perform an automatic installation of a new release of the operating system and licensed program products, the process retains the current operating environment (AS/400 or System/36), system values, and configuration while replacing these items:

• IBM licensed internal code
• OS/400 operating system
• licensed programs and optional parts of licensed programs currently installed on your system
• language feature code on the distribution media that’s installed as the primary language on the system

If, during the installation process, the System Attention light on the control panel appears, you should refer to Chapter 5 of AS/400 Software Installation for a list of system reference codes (SRCs) and instructions about how to continue. The only exception is if the attention light comes on and the SRC begins with A6. The A6 codes indicate that the system is waiting for you to do something, such as reply to a message or make a device ready.

To install the new release, take the following steps.

Step 1. Arrange the CD-ROMs in the order you’ll use them.

Step 2. Load the CD-ROM that contains the licensed internal code. Wait for the CD-ROM In-Use indicator to go out.

Step 3. At the control panel, set the mode to Normal.

Step 4. Execute the following PWRDWNSYS (Power Down System) command:

PWRDWNSYS *IMMED RESTART(*YES) IPLSRC(D)

This command will start an IPL process. Note that SRC codes will continue to appear in the display area of the control panel.

Step 5. You’ll see the Licensed Internal Code – Status panel. Upon 100 percent completion of the install, the display may be blank for approximately five minutes and the IPL in Progress panel may appear. You needn’t respond to any of these panels.

Step 6. Load the next volume when prompted to do so. You’ll receive this prompt several times during the installation process. After loading the volume, you must respond to the prompt to continue processing. The response value you specify depends on whether you have more volumes to process: A response of G instructs the installation process to continue with the next volume, and a response of X indicates that no more volumes exist.

Step 7. Next, the installation process loads the operating system followed by licensed programs. During this process, you may see panels with status information. One of these panels, Licensed Internal Code IPL in Progress, lists several IPL steps, some of which can take a long time (two hours or more). The amount of time needed depends on the amount of recovery your system requires. As the installation process proceeds, you needn’t respond to the status information panels you see.

Once all your CD-ROMs have been read, be prepared to wait for quite some time while the installation process continues. The process is hands-free until the Sign On panel appears.

Step 8. When installation is complete, you’ll see the Sign On panel. If you receive the message “Automatic installation not complete,” you should sign on using the QSECOFR user profile and refer to Appendix A, “Recovery Procedures,” in AS/400 Software Installation for instructions about how to proceed. If the automatic installation process was completed normally, sign on using user profile QSECOFR and continue by verifying the installation, loading additional products, loading PTFs, and updating software license keys.

Verify the installation. To verify the installation, execute the GO LICPGM command. On the Work with Licensed Programs display, choose option 50 (Display log for messages). The Display Install History panel (Figure 4, below) will appear. Press Enter on this panel, and scan the messages found on the History Log Contents display. If any messages indicate a failure or a partially installed product, refer to “Recovery Procedures” in AS/400 Software Installation.

                      Display Install History

 Type choices, press Enter.

   Start date . . . . . .   07/17/00   MM/DD/YY

   Start time . . . . . .   09:32:35   HH:MM:SS

   Output . . . . . . . .   *______    *, *PRINT







 F3=Exit   F12=Cancel
 (C) COPYRIGHT IBM CORP. 1980, 1998.
	

Next, verify the status and check the compatibility of the installed licensed programs. To do so, use option 10 (Display licensed programs) from menu LICPGM to display the release and installed status values of the licensed programs. A status of *COMPATIBLE indicates a licensed program is ready to use. If you see a different status value for any licensed program, refer to the “Installed Status Values” section of Appendix E in AS/400 Software Installation.

Load additional products. You’re now ready to load any additional licensed programs and secondary languages. Return to the Work with Licensed Programs menu, and select option 11 (Install licensed programs). You’ll see the Install Licensed Programs display that appears in Figure 5, below. The installation steps for loading additional products are similar to the steps you’ve already taken. Select a licensed program to install, and continue. If you don’t see a desired product in the list, follow the specific instructions delivered with the distribution media containing the new product.

                 Install Licensed Programs
                                                System:   AS400
 Type options, press Enter.
   1=Install

         Licensed  Installed
 Option  Program   Status       Description
   _     5769SS1   *COMPATIBLE  OS/400 - Library QGPL
   _     5769SS1   *COMPATIBLE  OS/400 - Library QUSRSYS
   _     5769SS1   *COMPATIBLE  OS/400 - Extended Base Support
   _     5769SS1   *COMPATIBLE  OS/400 - Online Information
   _     5769SS1   *COMPATIBLE  OS/400 - Extended Base Directory Support
   _     5769SS1                OS/400 - S/36 and S/38 Migration
   _     5769SS1                OS/400 - System/36 Environment
   _     5769SS1                OS/400 - System/38 Environment
   _     5769SS1   *COMPATIBLE  OS/400 - Example Tools Library
   _     5769SS1   *COMPATIBLE  OS/400 - AFP Compatibility Fonts
   _     5769SS1   *COMPATIBLE  OS/400 - *PRV CL Compiler Support
   _     5769SS1                OS/400 - S/36 Migration Assistant
   _     5769SS1   *COMPATIBLE  OS/400 - Host Servers
                                                             More...
 F3=Exit   F11=Display release   F12=Cancel   F19=Display trademarks

 (C) COPYRIGHT IBM CORP. 1980, 1998.

Load PTFs. Next, install the cumulative PTF package (either the one that arrived with the new release or a new one you ordered, as suggested in the planning steps above). The shipping letter that accompanies the PTF tape will have specific instructions about how to install the PTF package.

Note: To complete the installation process, you must install a cumulative PTF package or perform an IPL. An IPL is required to start the Initialize System (INZSYS) process (the INZSYS process can take two hours or more on some systems, but for most systems it’s completed in a few minutes.) In addition to installing a cumulative PTF package, you should install any group PTFs you have — particularly the HIPER, or High-Impact PERvasive, PTFs group package. (For information about installing PTFs, see Chapter 6.)

After the IPL is completed, sign on as QSECOFR and check the install history (using option 50 on menu LICPGM) for status messages relating to the INZSYS process. You should look for a message indicating that INZSYS has started or a message indicating its completion. If you see neither message, wait a few minutes and try option 50 again. Continue checking the install history until you see the message indicating INZSYS completion. If the message doesn’t appear in a reasonable amount of time, refer to the “INZSYS Recovery Information” section of Appendix A in AS/400 Software Installation.

Update software license keys. To install software license keys, use the WRKLICINF (Work with License Information) command. For each product, update the license key and the usage limit to match the usage limit you ordered. The license information is part of the upgrade media. You must install license keys within 70 days of your release installation.

Step 9. The installation of your new release is now complete! The only thing left to do before restarting production activities is to perform another SAVSYS to save the new release and the new IBM program products. Just think how much trouble it would be if you had a disk crash soon after loading the new release and, with no current SAVSYS, were forced to restore the old release and repeat the installation process. To make sure you don’t suffer this fate, perform the SAVSYS and the SAVLIB LIB(*IBM) operations now.

Before starting the save, determine whether system jobs that decompress objects are running. You should start your save only if these jobs are in an inactive state. To make this determination, use the WRKACTJOB (Work with Active Jobs) command and check the status of QDCPOBJx jobs (more than one may exist). You can ensure these jobs are inactive by placing the system in restricted state. Don’t worry — the QDCPOBJ I. x jobs will become active again when the system is no longer in restricted state.

Final Advice

The only risk you take when installing a new release is not being prepared for failure. It’s rare that a new-release installation must be aborted midway through, but it does happen. If you take the precautions mentioned in the planning suggestions and turn to “Recovery Procedures” in AS/400 Software Installation in the event of trouble, you won’t find yourself losing anything but time should you encounter an unrecoverable error. For the most part, installing new releases is only an inconvenience in time.

This chapter is excerpted from a new edition of Wayne Madden’s Starter Kit for the AS/400, to be published in the spring of 2001 by NEWS/400 Books.

Gary Guthrie is a technical editor for iSeries NEWS. You can reach him by e-mail at gguthrie@iseriesnetwork.com.