After the Base Operating System (BOS) is installed, you might want to install optional software or service updates. This chapter includes information on the following topics:
# lssrc -s cdromdThe cdromd daemon can interfere with scripts, applications, or instructions which attempt to mount the CD or DVD device without first checking to see if the device is already enabled. A resource or device busy error occurs in such a condition. Use the cdumount or cdeject command to unmount the device. Then mount the device as specified in the program or instructions. Alternatively, use the cdcheck -m or mount command to determine the current mount point of the device. For further information, see the cdromd command documentation in the AIX 5L Version 5.2 Commands Reference.
The installation code allows for this automatic mounting. If cdromd is enabled and the mkcd command is run, the CD-R or DVD-RAM is ejected after the image is completed. If you do not want to have the media ejected, then the cdromd daemon should be put in the inoperative state with the following command:
# stopsrc -s cdromd
Optionally installable software includes:
Software products can be divided into the following categories:
| Licensed Program | A licensed program (also known as a 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. An example of a fileset is bos.net.nfs.client 5.1. For more information on fileset packaging, see Fileset Installation Packaging. |
| Fileset Update | An individually installable update. Fileset updates either enhance or correct a defect in a previously installed fileset. |
| Bundle | 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 that contain a specific set of optional software. For more information on bundle packaging, see Bundle Packaging. |
A product can be composed of several packages, which in turn can be composed of different filesets. A product might be installed in its entirety, or only certain packages or filesets for the product might be installed. Software products are subdivided in this way, because many software products are large and have many pieces that can be used independently. Dividing a product into separately installable filesets allows you to install only those filesets you need.
You can install all the filesets included in a package or the entire product, or you can install only selected filesets, especially if you have limited hard disk space on your system.
The product name and level number identify a software product. The format for a software product level in AIX 5.2 is as follows:
versionnumber.releasenumber.modificationlevel.fixlevel
Each field in the software product identification is defined as follows:
For example, 05.01.0000.0000 is a software product level number, and 05.01.0000.0032 is a software product update level. It is not necessary to include the leading zeroes in the version, release, modification level, and fix level fields of the level. Level 05.01.0000.0000 can also be written as 5.1.0.0.
The types of software licensing that can be implemented in the software purchase are run-time licensing and acceptance of software license agreements. Normally, software requiring run-time licenses is only selected for installation when you have a license to use that software. Although the Web-based System Manager and System Management Interface Tool (SMIT) allow you to install licensed software even if you do not own a license, you might be prevented from using the newly installed software until you have obtained the appropriate license.
Accepting software license agreements requires that the license agreement be accepted as part of the installation process. If software installed as part of your BOS installation requires accepting a software license agreement, you cannot exit the Configuration Assistant (or the Installation Assistant for non-graphics consoles) until the license agreement has been accepted. You can view as well as accept the license agreement. The BOS installation can be customized to automatically accept software licenses. Refer to Customized BOS Installations for more information.
For optional software installation, you can preview the license agreements on the installation media using the smit license_on_media fast path or the installp -El command. During the installation process, you can use the menu item to accept the software license, or you can use the installp command with the -Y flag. To view accepted license agreements on a system, you can use the SMIT smit installed_license fast path or the lslpp -E command. To view licenses using the Web-based System Manager, type wsm to start the application, and select Software. When a product is uninstalled, the license agreement acceptance is changed to the inactive state. If the product is reinstalled, you will not be prompted to reaccept the license agreement.
After completing the prerequisites in the next section, your next step is deciding whether to install software with the Web-based System Manager or with SMIT. Descriptions of both applications are included in this chapter.
Before you install optional software and service updates, refer to the specific instructions that accompany your installation media. If you ever need to reinstall your system, refer to the installation media instructions.
Note: For information about developing software products that are installed using the installp command, refer to Packaging Software for Installation in AIX 5L Version 5.2 General Programming Concepts: Writing and Debugging Programs.
If either of the following conditions apply to you, go to the referenced section. Otherwise, continue with the procedures in this chapter.
Before installing optional software or service updates, complete the following prerequisites:
# unlinkbasecd # umount /infocd
Optional software products and service updates can be installed using system management tools provided with the operating system. The following sections provide a brief description of the procedures:
To view the files as they are being installed, do the following:
The graphics interface provides access to Web-based System Manager options for installing the following:
The Web-based System Manager allows you to install software, as well as to change the system's default install settings and specify other options. By default, the Web-based System Manager applies and commits any software updates you are installing. However, you can change this default setting and have the software updates applied only.
Note: Base software applications are always committed. If a previous version of the software is installed, it cannot be saved.
The following installation paths are available in SMIT:
Note: If a problem occurs during the installation of optional software that causes the installation process to halt abnormally, you might have to complete a cleanup procedure to remove the partially installed software from the system before attempting to reinstall it. If the system instructs you to do a cleanup, go to Cleaning Up Optional Software Products and Service Updates.
This section describes the system activity and actions that you must take after the installation process has begun.
Note: The system might prompt you to insert the volume of the installation media, with a message similar to the following:Mount volume 2 on /dev/cd0. Press the Enter key to continue.When this message displays, insert the specified media and press Enter.
When the installation finishes, the Command: status field on the COMMAND STATUS screen changes to OK or failed. OK indicates that the installation ran to completion, although some filesets may not have installed successfully. The failed status means that there was a problem with the installation. Although a preview installation always finishes with an OK status, always check the summaries.
For information about error messages, refer to Acting on System and Error Messages.
If you need to install again and you have AIX BOS multivolume media, insert volume 1 of the AIX product CDs. Press F3 to return to the previous screen, then restart the installation. See Acting on System and Error Messages for information about bosboot command errors that may occur while the installation program is running, and about recovery procedures for these errors.
If you have additional software to install from a different installation media, remove the media that is in that drive and insert the new media.
Press F3 (or Esc+3) to return to the previous screen and continue installing the software product or service update.
# shutdown -Fr
The install_all_updates command updates installed system software to the latest level that is on the media and verifies the current recommended maintenance level. The install_all_updates command will not install any filesets that are present on the media, but not installed on the system, unless these filesets are installed as requisites of other selected filesets. For installp images, all installp requisites are enforced.
The following example shows how to install all installp updates on device /dev/cd0 and to verify the current recommended maintenance level,:
# install_all_updates -d /dev/cd0
For more information on the install_all_updates command, refer to the AIX 5L Version 5.2 Commands Reference.
During and after installation, the following major maintenance actions can be taken with optional software products and service updates. Optional software and service updates can be:
Whether a particular action can be taken depends on whether the action is being applied to the entire software product, or only to a service update that has had a previous action taken on it.
You can perform these actions using either the Web-based System Manager or the System Management Interface Tool (SMIT) or by using commands directly from the command line. The following sections briefly describe how to do each action using Web-based System Manager, SMIT, or a command. Both Web-based System Manager and SMIT provide online help to guide you through each process.
When installing a service update, it can be left in the applied state. In this state, the former version of that software product is saved in the /usr/lpp/PackageName directory. Service Updates in the applied state allow you to restore the former version of the software without having to reinstall it.
Only service updates can be placed in the applied state. In contrast, after you install an entire software product, the product is left in the committed state. Software products in the committed state do not save the previous version of the software, because two versions of the same software product cannot be installed at the same time.
Committing a service update removes the previous version of a product from the system, which conserves disk space. After a software product or update has been committed, it cannot be deleted from the system except by removing the entire software product (the base level product and all of its updates) or by force-installing it back to a previous level. To do a force-installation, you must have the base level of the fileset available on media.
Although applying and committing a service update are considered separate actions, both can be accomplished while installing the update. In fact, the default action under Web-based System Manager and SMIT is to both apply and commit the service update during installation. This default can be changed to just apply the update.
You can list all service updates in the applied state by selecting List Installed Software -> Updates in Applied State from the Software menu.
You can list all service updates in the applied state by typing smit list_installed on the command line.
You can list all service updates in the applied state by typing installp -s on the command line.
When you reject an applied service update, the update files are removed from the system and the previous version of the software is restored. Only service updates in the applied state can be rejected. You can use the Web-based System Manager or SMIT to reject applied service updates.
When you remove a software product, that product's files are removed from the system and the Software Vital Product Data information is changed to indicate that the product is removed. The remove process also attempts to restore the system's configuration to its previous state, although this is dependent on the product and might not always be complete. After a product is removed, no version of that product remains running on the system.
Use the Web-based System Manager or SMIT to remove software products. In either application, if you set the Remove dependent software? field to yes, any requisite software (software that is dependent on the product you are removing) is also removed, unless it is required by other software on your system.
The Copy Software Bundle to Hard Disk for Future Installation option allows you to copy a software bundle from a specified source to a location on your local system.
Installation software bundles include the following:
Note: This procedure applies only to the update or installation of optional software products. If your AIX 5.2 BOS installation was unsuccessful, see Accessing a System That Does Not Boot for more information.
This section describes how to clean up software products and service updates after an interrupted installation. The cleanup procedure attempts to delete items that were partially installed or left in an incomplete state. For example, after an update is interrupted, the lslpp -l command might report the update status as APPLYING rather than APPLIED.
The cleanup procedure attempts to revert the update to its previous state. For example, when cleaning up an update that was interrupted in the COMMITTING state, the cleanup procedure attempts to return the update to its APPLIED state.
If the interruption occurs during the initial state of an installation, then the cleanup procedure attempts to delete the installation entirely and restore the previous version of the product (if there is one). When the previous version is restored, it becomes the active version. When the previous version cannot be restored, the software is listed by the lslpp -l command as BROKEN.
When the product is deleted or BROKEN, you can attempt to reinstall the software. Any product in the BROKEN state cannot be cleaned up; it can only be reinstalled or removed.
The system automatically initiates a cleanup when an installation fails or is interrupted. Normally, you must initiate a cleanup procedure if the system shuts down or loses power during an installation or if the installation process terminates abnormally. Occasionally, you are prompted to reboot (restart) the system after running the cleanup procedure.
If you get a message indicating that no products were found that could be cleaned up, you may have executed the cleanup procedure when it was not needed. Try your installation again.
If you get a message indicating that you need to clean up a failed installation, contact your point of sale for assistance.
The lppmgr command is used to manage an existing installp image source. The lppmgr command performs the following functions on an existing installp image source (also known as an lpp_source resource in the NIM environment):
By default, lppmgr lists all images filtered by the preceding routines. The -r flag can be used to remove the filtered images and the -m flag can be used to move the images to another location.
The lppmgr command is not intended to replace bffcreate, install anything, or work with installed filesets. It is also not intended to address any issues other than those mentioned. Before using the -X flag, you should have a good understanding of NIM, system images (known as SIMAGES in NIM), and the workings of a NIM lpp_source resource.
To list all duplicate and conflicting updates in the /myimages image source directory, type:
# lppmgr -d /myimages -u
To remove all duplicate and conflicting updates in the /myimages image source directory, type:
# lppmgr -d /myimages -u -r
For more information on the lppmgr command, refer to the AIX 5L Version 5.2 Commands Reference.
The Software Service Management menu generates comparison reports to manage filesets installed on a system, filesets contained in a repository, and filesets available from the IBM eServer pSeries support Web site. The Software Service Management menu also provides a way for you to clean up and rename software images in a repository. The following options are available:
You can perform these actions using either the SMIT service_software fast path or by using commands directly from the command line. The following sections briefly describe how to do each action using SMIT or a command.
The Comparison Reports menu allows you to generate several comparison reports to verify that the filesets for a particular fix or preventive maintenance package are installed by comparing filesets installed on a system to another source. This source could be a fix repository, such as an lpp_source or a directory of fixes, or a downloaded list from the IBM eServer pSeries support Web site.
If you want to verify that your lpp_source is up to date, you can also compare a fix repository to a downloaded list.
You can perform these actions in the SMIT compare_report fast path or using the compare_report command available from the command line.
The Compare Installed Software to Fix Repository menu allows you to compare the filesets installed on a system to a fix repository. The following report lists are generated:
The Compare Installed Software to Fix Repository option is available using the SMIT instofix_compare fast path or the compare_report command with the following options:
compare_report -s -i FixDir {[ -l ] [ -h ] [ -m ] [ -n ]} \
[ -t ReportDir -Z | -v ]
The Compare Installed Software to List of Available Updates menu allows you to compare the filesets installed on a system to a downloaded list of available updates from the IBM eServer pSeries service Website. The following report lists are generated:
The Compare Installed Software to List of Available Updates option is available using the SMIT instolist_compare fast path or the compare_report command with the following options:
compare_report -s -r ServiceReport {[ -l ] [ -h ]} [ -t ReportDir -Z | -v ]
The Compare Fix Repository to List of Available Updates menu allows you to compare the filesets in a fix repository, such as a fix directory or lpp_source, to a downloaded list of available updates from the IBM eServer pSeries service Web site. The report list that is generated contains information on filesets in the fix directory that are back-level from latest (lowerthanlatest2.rpt).
The Compare Fix Repository to List of Available Updates option is available using the SMIT fixtolist_compare fast path or the compare_report command with the following options:
compare_report -i FixDir -r ServiceReport [ -t ReportDir -Z | -v ]
You can also compare a list of installed software on a base system to another system. This option allows you to compare the filesets installed on a system to another system. The lslpp -Lc output from one system is saved to a file and compared to the lslpp -Lc output from another system. The following report lists are generated:
To compare a list of installed software on a base system to another system use the compare_report command with the following options:
compare_report -b BaseList -o OtherList {[ -l ] [ -h ] [ -m ] [ -n ]} [ -t ReportDir -Z | -v ]
The Rename Software Images in Repository option allows you to rename updates that have FIX ID numbers for names to more meaningful fileset names like those generated when updates are copied to hard disk for future installation. This action renames all filesets in the indicated directory with the same format. This option is available using the SMIT rename_software fast path.
You can also use the bffcreate command to rename software images in a directory. To rename software images in a directory using the bffcreate command, use the -c flag and the -d flag for the directory containing the filesets. For example, to rename filesets in the /usr/sys/inst.images directory, type:
# /usr/sbin/bffcreate -cd /usr/sys/inst.images
You can also create a log file containing a mapping between the old names and new names using the -s logfile option, as shown in the following example:
# /usr/sbin/bffcreate -cd /usr/sys/inst.images -s /usr/sys/inst.images/names.log
This example creates a /usr/sys/inst.images/names.log file that contains content formatted as follows:
old_fileset_name:new_fileset_name
This option is also available in SMIT Rename Software Images in Repository menu as the LOG software name changes (location of log file) option.
The Clean Up Software Images in Repository option allows you to remove unneeded or duplicate software images from a local software-image repository. You can remove duplicate software, superseded updates, and language software:
This option is available using the SMIT cleanup_software fast path.
Some products that are distributed for installation on AIX are packaged and installed with InstallShield Multi-Platform (ISMP). Unlike installp or RPM installations which only provide non-prompted or silent installations of a product, ISMP packaged products provide both interactive and silent interfaces for installation and uninstallation of a product.
Similar to products packaged and installed with installp and RPM, ISMP packaged products can be installed using the AIX system management tools, including SMIT and Web-based System Manager. These tools use the geninstall command to install or uninstall products that are packaged and installed with installp, RPM, or ISMP. As expected, the geninstall command can be used directly to install, list, or uninstall ISMP packaged products.
For instructions for installing or uninstalling a specific product packaged and installed with ISMP, consult the product's documentation.
This section provides information on the following topics:
You install an ISMP product using SMIT, Web-based System Manager, the geninstall command, or the files provided by the product's devloper.
By default, ISMP product installations launched through SMIT will be silent or nonprompted installations. To perform an interactive installation, use the Web-based System Manager, the geninstall command, or the instructions provided with the product documentation.
Although SMIT has a preview option, this option is not available for ISMP installations. If you select the preview option, a message instructs you to launch an interactive installation using Web-based System Manager or the command line, which allows you to view the preinstallation summary panel before completing the product installation.
/usr/sbin/geninstall -d /usr/sys/inst.images MyProductOR
/usr/sbin/geninstall -d /usr/sys/inst.images J:MyProduct
Use the J: prefix to inform the geninstall command that the product is an ISMP package. The geninstallcommand recognizes the ismp/ppc subdirectory, just as it recognizes RPMS/ppc for RPM packages and installp/ppc for installp packages, so it is only necessary to pass the /usr/sys/inst.images base directory. You can also use the directory that contains the installation files. In this example, specify the directory as follows:
/usr/sbin/geninstall -d /usr/sys/inst.images/ismp/ppc/MyProduct J:MyProduct
If you want to launch a silent or nonprompted installation with geninstall, include the -Z flag:
/usr/sbin/geninstall -d /usr/sys/inst.images -Z J:MyProduct
For more information about silent installations, see Silent Installations and Using Response Files.
.
You uninstall an ISMP product using SMIT, Web-based System Manager, the geninstall command, or the files provided by the product's developer.
By default, uninstallation processes performed in SMIT are silent or nonprompted. To perform an interactive uninstallation, use Web-based System Manager, the geninstall command, or the instructions provided with the product documentation.
In SMIT, the preview option is not available for the ISMP product uninstallation procedure. If you attempt to preview the uninstallation, a message instructs you to launch an interactive uninstallation using Web-based System Manager or the command line. This will allow you to view the pre-uinstallation summary panel before completing the product uninstallation.
/usr/sbin/geninstall -u MyProductOR
/usr/sbin/geninstall -u J:MyProduct
To speed processing, use the J: prefix to inform the geninstall command that you are uninstalling an ISMP packaged product..
To perform a silent or nonprompted uninstallation with the geninstall command use the -Z flag, as follows:
/usr/sbin/geninstall -Zu J:MyProduct
The section provides information on how to perform silent installations and uninstallations for ISMP packaged products using response files.
A response file contains predetermined responses for an installation or uninstallation. To use response files with ISMP products, the following methods are available:
To create the /tmp/MyProduct/response.template response file template for the MyProduct product using the product installation files in the /usr/sys/inst.images/ismp/ppc/MyProduct/ directory, do the following:
/usr/sbin/geninstall -d /usr/sys/inst.images -T /tmp/MyProduct/response.template J:MyProduct
The /tmp/MyProduct/response.template response file that is generated is similar to the following:
####################################################################### # # InstallShield Options File Template # # Wizard name: Setup # Wizard source: setup.jar # Created on: Tue Jun 25 10:59:55 CDT 2002 # Created by: InstallShield Options File Generator # # This file can be used to create an options file (i.e., response file) for the # wizard "Setup". Options files are used with "-options" on the command line to # modify wizard settings. # # The settings that can be specified for the wizard are listed below. To use # this template, follow these steps: # # 1. Enable a setting below by removing leading '###' characters from the # line (search for '###' to find settings you can change). # # 2. Specify a value for a setting by replacing the characters <value>. # Read each settings documentation for information on how to specify its # value. # # 3. Save the changes to the file. # # 4. To use the options file with the wizard, specify -options <filename> # as a command line argument to the wizard, where <filename> is the name # of this options file. # ##################################################################### ##################################################################### # # My Product Install Location # # The install location of the product. Specify a valid directory into which the # product should be installed. If the directory contains spaces, enclose it in # double-quotes. For example, to install the product to C:\Program Files\My # Product, use # # -P installLocation="C:\Program Files\My Product" # ### -P installLocation=<value>
Although the preceding is a simple example, products often have many user-configurable options that might be set in the response file. Each of these options is presented in the template with an explanation of the expected value for that option.
To record the /tmp/MyProduct/response.file response file with the MyProduct and the product installation files in the /usr/sys/inst.images/ismp/ppc/MyProduct/ directory, do the following:
/usr/sbin/geninstall -d /usr/sys/inst.images -E /tmp/MyProduct/response.file J:MyProduct
This starts the interactive installation or uninstallation wizard. It is necessary to run the wizard to completion to succesfully create the response file recording. When completed, a message similar to the following displays:
Options record mode enabled - run the wizard to completion to create the options file response.file
The resulting file /tmp/MyProduct/response.file is similar to the following:
################################################################ # # InstallShield Options File # # Wizard name: Setup # Wizard source: setup.jar # Created on: Tue Jun 25 11:05:34 CDT 2002 # Created by: InstallShield Options File Generator # # This file contains values that were specified during a recent execution of # Setup. It can be used to configure Setup with the options specified below when # the wizard is run with the "-options" command line option. Read each setting's # documentation for information on how to change its value. # # A common use of an options file is to run the wizard in silent mode. This lets # the options file author specify wizard settings without having to run the # wizard in graphical or console mode. To use this options file for silent mode # execution, use the following command line arguments when running the wizard: # # -options "record.txt" -silent # ################################################################################ ################################################################################ # # My Product Install Location # # The install location of the product. Specify a valid directory into which the # product should be installed. If the directory contains spaces, enclose it in # double-quotes. For example, to install the product to C:\Program Files\My # Product, use # # -P installLocation="C:\Program Files\My Product" # -P installLocation="/opt/MyProduct"
The -P installLocation value has been filled in according to the response given while running the wizard. In the preceding example, the /opt/MyProduct directory was specified as the installation location in the wizard. The response.file file generated by this action can be used directly to launch a silent installation with the chosen install location.
/usr/sbin/geninstall -Zd /usr/sys/inst.images \ -R /usr/sys/inst.images/ismp/ppc/MyProduct/response.file J:MyProduct
You can also use a response file for an uninstallation, as follows:
/usr/sbin/geninstall -u -R /usr/sys/inst.images/ismp/ppc/MyProduct/response.file J:MyProduct