After the Base Operating System (BOS) is installed, you may want to install optional software or service updates. This chapter discusses software installation and applying service updates, but does not discuss committing service updates after installation. For information on committing, rejecting, and removing software after installation, refer to "Maintaining Optional Software" and "Optional Software Installation and Update Concepts".
For information on cleaning up after an interrupted software installation, refer to "Cleaning Up Optional Software and Service Updates".
"Compatibility between AIX Version 3.2 and AIX Version 4.3" discusses compatibility between the two release levels and lists the compatibility software for machines running mixed levels of AIX. It is recommended that you install this compatibility software if you did not perform a Migration Installation.
Information about individual software products is available in HTML format and is not included in this book. To view the software products information:
Optionally installed software includes the following:
Optional Software Products. An optional software product is software that is not automatically installed on your system when you install BOS.
Service Updates. A service update is software that corrects a defect in or adds new function to the BOS or an optional software product.
Service updates are organized by filesets. Filesets are sets of files that are part of the same optional software product. Some products are not organized as fileset updates. Such products can only be updated by installing a newer version.
For more information on updating software, see "Optional Software Installation and Update Concepts".
If your system is not equipped with a CD-ROM drive, install the hardware diagnostics bundle from your installation media to enable concurrent hardware diagnostics.
If your system is equipped with a CD-ROM drive, use the diag command to run concurrent diagnostics from the diagnostics CD-ROM. Run diagnostics in the standalone mode by booting from the diagnostics CD-ROM.
Software is selected for installation if it is in the bundle you choose and on the installation media. Normally, software requiring a license is only selected if you have the license for that software. The Web-based System Manager Software application and the SMIT Custom Install tool do, however, allow you to install software requiring a license even if you do not have a license. You will not be able to run this software, however, until you have obtained the license.
Software products include those shipped with AIX and those purchased separately. Each software product can contain separately installable units. The following explains how software products are organized:
|Licensed Program||A licensed program (also known as product) is a complete software product including all packages associated with that licensed program. For example, bos (the Base Operating System) is a licensed program.|
|Package||A group of separately installable units that provide a set of related functions. For example, bos.net is a package.|
|Fileset||An individually installable option. Filesets provide a specific function. For example, bos.net.nfs.client 188.8.131.52 is a fileset.|
|Fileset Update||An individually installable update. Fileset updates either enhance or correct a defect in a previously installed fileset. For example, bos.net.nfs.client 184.108.40.206 is a fileset update.|
A collection of packages, products, or individual filesets that suit a specific purpose, such as providing personal productivity software or software for a client machine in a network environment. A set of bundles is provided with BOS which contain a specific set of optional software. The Web-based System Manager Software application and the SMIT Install application look for bundles in /usr/sys/inst.data/sys_bundles and in /usr/sys/inst.data/user_bundles. The sys_bundles location is typically reserved for system-defined bundles (those which come with AIX). The user_bundles directory is where users can create their own bundle files.
The bundle definition file name must end in .bnd, since the AIX install interfaces which process bundles recognize only bundle files that end in .bnd. Use any editor to create bundle files, which can contain comments and fileset names. Lines beginning with "#" are recognized as comments and are ignored by the bundle processing code. When you have completed your list of filesets, save the file and make sure the file has the appropriate read permission. Invoking a bundle install interface displays your bundle without the .bnd extension.
AIX documentation is not automatically installed when you install BOS or a predefined bundle. The documentation is contained on two CD-ROMs, AIX Version 4.3 Base Documentation CD and AIX Version 4.3 Extended Documentation CD. For information about installing AIX documentation and the documentation search service, see "Installing and Configuring the Documentation Search Service and Installing AIX Documentation".
The following are examples of the predefined bundles:
Note: Some system bundles may refer to installation images that may be spread across multiple media. If you see errors that filesets could not be found on the media you are using, insert another media and retry the bundle install. For example, the Client Bundle may contain a web browser package that is contained on another media. Another example might be filesets or packages that are located on the AIX 4.3 Bonus Pack CD-ROM media. Refer to the bundle files on the system for information about the location of images that are not on the AIX Version 4.3 media. The information is in: /usr/sys/inst.data/sys_bundles.
The following bundle appears only if there was not enough disk space available to complete a Migration Installation during the BOS installation process:
If you are migrating AIX Version 3.2 programs, a BOS Migration Installation only migrates those optional software products that run on BOS Version 4.3. If you are migrating AIX Version 4.1 or 4.2 programs and there is a newer level of a previously installed fileset on the installation media, a BOS Migration Installation attempts to install the newer level. Any previously installed products that can be run on BOS Version 4.3 will not be altered during the Migration Installation. In cases where a BOS Migration Installation does "migrate" a product, it does so by running the installp command to install the latest version of that product at the base level. After installation, the product is in the committed state, and the previous version of the product is deleted from the system.
When the latest base level of a product is installed (whether it is installed by the user or through a Migration Installation), the user configuration files from the previous version of the product are saved. In some cases you may need to compare the previous configuration files with the new ones and resolve any differences.