Checklist: Completing the i5/OS installation

 

Use this checklist to complete the i5/OS® installation processes.

  1. If you still have default passwords for your service tools user IDs, change them now. For information on service tools user IDs, see Change service tools user IDs and passwords .

  2. Remove the media volume when the installation is complete. If your media is tape, wait for the tape to rewind completely.

  3. If you have any IBM® or non-IBM products with special installation instructions, install these products now. Check the product's documentation, and follow any special instructions.

  4. For logical partitions only: Attention: For System i™ 8xx and earlier models, do not perform the next step (step 5) to install the cumulative PTF package until after you are aware of the unique PTF installation considerations involved on a system with logical partitions. You could potentially lose data. Refer to the topic Install fixes on systems with logical partitions to understand how to install the cumulative PTF package on a system with logical partitions.

  5. Install the most current cumulative PTF package. (This package should have been ordered a week or two before your installation.) Use the instructions in the PTF Shipping Information Letter. Then return here and continue with the next step.

    If you do not install the cumulative PTF package now, perform an IPL and let the Initialize System (INZSYS) process complete. Before you do, set the IPL type to B (or the IPL type you use for everyday operation) and then set the mode selection to Normal. Initialize System (INZSYS) recovery has more information on INZSYS.

  6. Apply any PTF groups that you have ordered. For more information on PTF groups, refer to Ensuring you have the latest information. To apply PTF groups, refer to the cover letter and instructions for the program temporary fix (PTF). For general information on applying PTFs, go to Install fixes .

  7. If your IBM System i5™ or IBM eServer™ i5 system is operating as a service partition and your system is not being managed by a Hardware Management Console, you might be required to perform a server IPL. A server IPL is an IPL whereby all logical partitions on the system are shut down at the same time. This allows, for example, a new level of the server firmware to be activated on the system.

    You might be required to perform a server IPL after you apply or remove a PTF on the service partition if that PTF affects the server firmware portion of the Licensed Internal Code. You also might be required to perform a server IPL after you upgrade or install a new level of the Licensed Internal Code on the service partition.

    • To find out if do a server IPL, type DSPPTF 5722999 on the i5/OS control language (CL) command line and press Enter. If a server IPL is required, message CPD35F8 Server IPL required is shown at the bottom of the display.

    • To find out if your system is operating as a service partition, type DSPPTF 5729999 on the CL command line and press Enter. If your system is operating as a service partition, the IPL Source field indicates the copy of the server firmware that was used on the previous server IPL.

    When shutting down your service partition for eServer i5 models, reference codes D6xx430B or D6xx430A could be displayed for an extended amount of time. The xx should increment periodically and is a normal part of processing when server firmware code is being updated. Allow the system to complete the processing. Do not interrupt this process.

  8. Look for messages in the install history log that indicate the status of the Initialize System (INZSYS) process:

    1. Type GO LICPGM and press Enter.

    2. Type 50 (Display log) on the Work with Licensed Programs display, and press Enter.

    3. The Display Install History display appears. Press Enter.

    The Display History Log Contents display appears. If you do not see either of the following messages on the display, wait a few minutes and select option 50 again. Find the message Initialize System (INZSYS) started. After this message appears, wait for a period of time and look for the Initialize System (INZSYS) processing completed successfully message (CPC37A9). If you do not see message CPC37A9 on the display, go to Initialize System (INZSYS) recovery to determine the problem.

  9. If you used image catalogs to perform your installation, you might want to remove all installation images from your system. To delete the catalog and all the optical images (image files)...
    DLTIMGCLG IMGCLG(mycatalog) KEEP(*NO)

  10. If you used image catalogs to perform your installation and you previously used the Start ASP Balance (STRASPBAL) command to end the allocation of storage for the load-source disk unit, enter the following command to resume the allocation of storage for the load-source disk unit.
    STRASPBAL TYPE(*RSMALC) UNIT(1) 
    STRASPBAL TYPE(*CAPACITY) ASP(1) TIMLMT(*NOMAX)

  11. Install software license keys for your operating system and keyed products. Use the Work with License Information (WRKLICINF) command to display the installed keyed products to add license key data. For specific instructions, go to Add license key information .

    After updating the license key information, return here and continue with the next step.

  12. After you complete the installation process and before you make the system available to all users, set the usage limit for the software-license managed products. These products are listed on the Proof of Entitlement (POE), invoice, or other documents that you have received with your software order. For products that have a usage limit, you set the usage limit with the Work with License Information (WRKLICINF) command.

    To set your usage limit, do the following:

    1. Type WRKLICINF and press Enter.

    2. On the Work with License Information display, press F11 (Display Usage Information). The usage limit number on each product that is listed on the POE, invoice, or other documents must match the usage limit number on the Work with License Information display for the associated product.

    3. Move the cursor to the line that contains the product name whose usage limit is to be updated.

    4. Type 2 (Change) and press Enter.

    5. When the Change License Information display is shown, update the usage limit prompt with the usage limit shown on the POE. In addition, update the threshold prompt with either *CALC or *USGLMT. Do not leave the threshold set to zero.

      If message CPA9E1B [Usage limit increase must be authorized. Press help before replying (C G).] is sent, respond by typing G.

    6. If the POE lists more products than the Work with License Information display, set the usage limits after you install those products.

  13. If you have installed the product 5722-VI1, Content Manager, you can use the product. However, perform post-installation commands. For more information, refer to the Post Installation section in the product document IBM ImagePlus® VisualInfo™ for AS/400®: Planning and Installation Guide, GC34-4585.

  14. If you have not already verified the compatibility of your licensed programs with the operating system, do this now. Use LICPGM menu option 10, Display installed licensed programs. If *COMPATIBLE is not listed next to a licensed program, then go to Installed status values and determine how to proceed.

  15. If you changed any other system value such as for example security level (QSECURITY) during your installation, change it back now.

  16. If you changed the scan control (QSCANFSCTL) system value to minimize future scanning of some objects that are restored before you installed your licensed programs, remove the *NOPOSTRST specification from this system value.

  17. Some of the tasks in this topic require that you change the QSYSOPR severity code filter to 95. If you do not want to continue with this level or you want to change the delivery notification, type CHGMSGQ QSYSOPR DLVRY(xx) SEV(yy) where xx indicates the delivery notification and yy indicates the severity code that you want to use. The system defaults are DLVRY(*HOLD) SEV(0).

  18. Save your system using your normal save procedures. Refer to the instructions in the Backing up your system topic . Make sure that the Initialize System (INZSYS) process is complete before you save your system.

    Before you start a save operation, use the Work with Active Jobs (WRKACTJOB) command to check the status of QDCPOBJx jobs. These jobs decompress objects. There could be more than one QDCPOBJx job. You can start your save operation if these jobs are in an inactive state. If you put the system in a restricted state by ending subsystems, the QDCPOBJx jobs become inactive. The jobs will restart when the system is not in a restricted state. For more information about decompressing objects, see Compressed objects and storage space.

  19. If you plan to install and use the i5/OS Information Center either from a workstation or the system, refer to the CD-ROMs that come with your software order. Find iSeries Information Center, SK3T-4091. This package also includes the PDF versions of System i manuals. For the installation instructions, see the readme.txt file.

  20. If you have installed IBM eServer iSeries™ Access Family products, you might have other tasks that complete. You can find further information about installing iSeries Access Family products in the following sources:

  21. You might have installed licensed programs that require additional installation steps on PCs, or you might have programs that install on PCs through an iSeries Access Family function. If you have products such as this, complete your PC installation by using the instructions for the product.

  22. If you have a System i integration with BladeCenter® and System x™ that you stopped before you began the installation process, restart it now.

    1. Type GO NWSADM on the CL command line. The Network Server Administration display appears.

    2. Select option 2, Start a network server.

  23. If you installed 5722-TC1, TCP/IP Utilities, go to the topic TCP/IP setup for advanced configuration and setup information.

  24. If you have customized an IBM-supplied program (for example, QSTRUP in library QSYS) in a previous release, make sure that you re-create this program to run correctly in the new release.

  25. If you have duplicated any IBM-supplied objects, you might want to make new duplicates after you install the release. This allows you to take advantage of functions added in the new release. Examples of objects that you might duplicate include the following:

    • Message text descriptions

    • Commands

    • Command defaults

You have completed your installation.

 

Parent topic:

Installing i5/OS and related software on a new system or logical partition