installp Command

Purpose

Installs available software products in a compatible installation package.

Syntax

To Install with Apply Only or with Apply and Commit

installp [ -a | -ac [ -N ] ] [ -eLogFile ] [ -V Number ] [ -dDevice ] [ -b ] [ -S ] [ -B ] [ -D ] [ -I ] [ -p ] [ -Q ] [ -q ] [ -v ] [ -X ] [ -F | -g ] [ -O { [ r ] [ s ] [ u ] } ] [ -tSaveDirectory ] [ -w ] [ -zBlockSize ] { FilesetName [ Level ]... | -f ListFile | all }

To Commit Applied Updates

installp-c [ -eLogFile ] [ -VNumber ] [ -b ] [ -g ] [ -p ] [ -v ] [ -X ] [ -O { [ r ] [ s ] [ u ] } ] [ -w ] { FilesetName [ Level ]... | -f ListFile | all }

To Reject Applied Updates

installp -r [ -eLogFile ] [ -VNumber ] [ -b ] [ -g ] [ -p ] [ -v ] [ -X ] [ -O { [ r ] [ s ] [ u ] } ] [ -w ] { FilesetName [ Level ]... | -f ListFile }

To Deinstall (Remove) Installed Software

installp -u [ -eLogFile ] [ -VNumber ] [ -b ] [ -g ] [ -p ] [ -v ] [ -X ] [ -O { [ r ] [ s ] [ u ] } ] [ -w ] { FilesetName [ Level ]... | -f ListFile }

To Clean Up a Failed Installation:

installp -C [ -b ] [ -eLogFile ]

To List All Installable Software on Media

installp { -l | -L } [ -eLogFile ] [ -d Device ] [ -B ] [ -I ] [ -q ] [ -zBlockSize ] [ -O { [ s ] [ u ] } ]

To List All Customer-Reported Problems Fixed with Software or Display All Supplemental Information

installp { -A|-i } [ -eLogFile ] [ -dDevice ] [ -B ] [ -I ] [ -q ] [ -z BlockSize ] [ -O { [ s ] [ u ] } ] { FilesetName [ Level ]... | -f ListFile | all }

To List Installed Updates That Are Applied But Not Committed

installp -s [ -eLogFile ] [ -O { [ r ] [ s ] [ u ] } ] [ -w ] { FilesetName [ Level ]... | -fListFile | all }

Description

Note: The noclobber option of the Korn or C shell should be unset in the environment from which an installation is performed.

The installp command installs and updates software.

A fileset is the lowest installable base unit. For example, bos.net.tcp.client 4.1.0.0 is a fileset. A fileset update is an update with a different fix ID or maintenance level. For example, bos.net.tcp.client 4.1.0.2 and bos.net.tcp.client 4.1.1.0 are both fileset updates for bos.net.tcp.client 4.1.0.0.

When a base level (fileset) is installed on the system, it is automatically committed. You can remove a fileset regardless of the state (committed, broken, committed with applied updates, committed with committed updates, etc.).

When a fileset update is applied to the system, the update is installed. The current version of that software, at the time of the installation, is saved in a special save directory on the disk so that later you can return to that version if desired. Once a new version of a software product has been applied to the system, that version becomes the currently active version of the software.

Updates that have been applied to the system can be either committed or rejected at a later time. The installp -s command can be used to get a list of applied updates that can be committed or rejected.

When updates are committed with the -c flag, the user is making a commitment to that version of the software product, and the saved files from all previous versions of the software product are removed from the system, thereby making it impossible to return to a previous version of the software product. Software can be committed at the time of installation by using the -ac flags. Note that committing already applied updates does not change the currently active version of a software product. It merely removes saved files for previous versions of the software product.

When a base level is removed with the -u flag, the files that are part of the software product and all its updates are removed from the system. Most cleanup of system configuration information pertaining to the product is also done, but this is dependent on the product and may not always be complete.

When a software product update is rejected with the -r flag, the active version of the software product is changed to the version immediately previous to the rejected update. Files saved for the rejected update and any updates that were applied after it are removed from the system.

A software product that is to be removed from the system can be in any state. Any product updates can be in either the applied or committed state, and they will also be removed.

If a previously interrupted installation leaves any software in a state of either applying or committing, it is necessary to perform cleanup with the -C flag before any further installations will be allowed. Although the installp -C command accepts software product names on the command line without returning an error, an attempt is always made to clean up all products when the -C flag is used. An attempt is made to clean up any incomplete installations by removing those parts that were previously completed. An attempt is also made to return to the previous version of the software product, if one exists, as the currently active version. If this cannot be done, the software product is marked as broken, and unpredictable results can occur if the user attempts to use it. Therefore, it is advisable for the user to reinstall any broken software products or updates.

The -t flag specifies an alternate location for a save directory that holds files being replaced by an update. This option is primarily useful in the following two circumstances.

• You have enough local disk space for saving replaced files but you do not want to permanently expand the root and /usr file systems.

  In this case, you can choose to create a separate file system for the alternate save directory. Once you are satisfied with the updated system and have committed all applied updates, disk space can be retrieved by deleting the save file system.

• If you do not have enough local disk space for saving replaced files but you have access to ample disk space on a remote system, then you can specify a directory that is mounted from a remote file system.

  It is recommended that if a remote file system is used, you should commit the updates as soon as possible. You may want to initiate the installation action as an apply and commit operation with the -ac flags. If you want to apply only in order to retain the capability of rejecting any unwanted updates, then it is highly recommended that you test the newly installed updates as soon as possible and then commit or reject them.

  The following considerations should be taken into account when using an alternate save directory:

• It is recommended that you use the same alternate save location on each invocation of the installp command.
• If an alternate save directory is used for an apply operation, you should make sure that the file system containing that directory remains mounted. It is highly recommended that any necessary mounts be done automatically on a reboot.
• If an alternate save directory is missing on a commit operation, the commit takes place, and a warning is given stating that the save directory could not be deleted. It is then your responsibility to delete the save directories that are no longer used in order to retrieve that disk space.
• If an alternate save directory is missing on reject, the reject operation cannot be done because the saved files are missing. An error is given, and the entire reject operation is cancelled. If the missing save directory is not caused by a temporary situation (for example, the inability to contact a remote directory on the network,) your only options are to commit the updates or leave them in an applied state permanently.
• When doing a system backup, you are responsible for backing up any alternate save directories that do not reside in the root volume group.
• The installation process safeguards users with a remote save directory from the possibility of two different systems using the same remote directory. However, you should use directory pathnames that easily and uniquely identify each user's system. For example, you might add the system's hostname somewhere in the pathname.
• Do not create a mksysb backup of a system with a remote save directory and then try to restore the mksysb image onto a system other than the original. In this case, using a mksysb image to install several like systems causes multiple ownership of the same remote save directory.

The installp -A command can be used to obtain a list of the Authorized Program Analysis Report (APAR) numbers and summaries for all customer-reported problems that are fixed in the specified software package. The installp -i command can be used to display supplemental information contained in files that can be a part of the specified software package.

To list all the software products and updates on the specified installation media, use the installp -l command. The output of the installp command with the -l flag resembles the following:

# Fileset Name             Level                    I/U Q Content
#================================================================
  X11.adt.include          4.1.0.0                  I  N usr
#   AIXwindows Application Development Toolkit Include F
   
  X11.adt.lib              4.1.0.0                  I  N usr
#   AIXwindows Application Development Toolkit Libraries
#
  X11.adt.motif            4.1.0.0                  I  N usr
#   AIXwindows Application Development Toolkit Motif
   
#
  X11.adt.bitmaps          4.1.0.0                  I  N usr
#   AIXwindows Application Development Toolkit Bitmap Fi
   
#
  X11.adt.ext              4.1.0.0                  I  N usr
#   AIXwindows Application Development Toolkit for X Ext
#
  X11.adt.imake            4.1.0.0                  I  N usr
#   AIXwindows Application Development Toolkit imake
#
  X11.apps.rte             4.1.0.0                  I  N usr
#   AIXwindows Runtime Configuration Applications
#
  X11.apps.msmit           4.1.0.0                  I  N usr
#   AIXwindows msmit Application

The fields have the following meanings:

Output from the installp -s command, which is used to get a list of applied software fileset updates and updates that are available to be either committed or rejected, resembles the following:

Installp Status
---------------
Name                       Part    Level                     State
--------------------------------------------------------------------
bos.net.tcp.client         USR     4.1.0.2                   APPLIED
bos.net.tcp.client         ROOT    4.1.0.2                   APPLIED
bos.rte.commands           USR     4.1.0.1                   APPLIED
bos.rte.misc_cmds          USR     4.1.0.1                   APPLIED
bos.rte.tty                USR     4.1.0.1                   APPLIED

The fields have the following meanings:

The software products and updates to be installed can be identified in one of three ways:

• by the keyword all, which indicates that all software contained on the specified installation media is to be installed
• by a list of software product names (each of which can optionally be followed by a level) that indicates the software to be installed
• by the -f flag followed by a file name, where each line in the file is an entry containing a software product name, optionally followed by a level, or is a comment line that begins with a # and is ignored

  Note: The installp program uses the sysck command to verify files after restoring them. The sysck command does not recognize the following special characters in file names: ~, `, ', \, ", $, ^, &, ( ), |, {}, [], <>, and ?. If a file name contains one of these characters, installation fails.

The FilesetName parameter can be used to specify an entire software product or any separately installable filesets within the software package. For example, bos.net is the name of a software package, and the separately installable filesets within that software package are bos.net.ncs.client, bos.net.nfs.client, and bos.net.tcp.client. If the user specifies bos.net for the FilesetName parameter, then all of the separately installable filesets listed are installed. If the user specifies bos.net.tcp.client for the FilesetName parameter, then only that fileset is installed.

The Level parameter indicates the level of the software product or update that is to be installed. The Level parameter is of the form vv.rr.mmmm.ffff.ppppppppp where:

If a user is installing an installation package from installation media that contains only installation packages it is not usually necessary to specify the level. More than one software product installation package with different levels does not often exist on the same installation medium, but when this does occur installp installs the specified software product at the latest software product level when Level is not specified with FilesetName. For installation media that contain either update packages only or contain both installation and update packages, all applicable update packages that are present on the installation media for the specified FilesetName are also installed when Level is not specified. For installation media that contain both installation and update packages the user can request the installation of only installation packages or only update packages by specifying the -I or -B flags, respectively. If the user wants to install only some of the updates on the installation medium for a specific software product both FilesetName and Level for each of the updates to be installed for that software product must be specified.

An example of what might be entered to install TCP/IP and one of its updates that are both contained in the /usr/sys/inst.images directory would be the following:

installp -a -d/usr/sys/inst.images bos.net.tcp.client 4.1.0.0
bos.net.tcp.client 4.1.0.2

Note: In the event that there are duplicate filesets at the same level, installp will use the first one that it finds in the install table of contents ( .toc ). This situation can occur when bffcreate is used to extract images from different media to the same installation directory. For this reason, care should be taken to ensure that update images are not extracted to the same directory as base level images for the same fileset at the same level.

A summary report is given at the end of the installp output that lists the status of each of the software products that were to be installed. An example summary report for the previous installp command follows:

Installp Summary
----------------
Name                    Level        Part        Event        Result
--------------------------------------------------------------------
bos.net.tcp.client      4.1.0.0      USR        APPLY        SUCCESS
bos.net.tcp.client      4.1.0.0      ROOT       APPLY        SUCCESS
bos.net.tcp.client      4.1.0.2      USR        APPLY        SUCCESS

Note: If a previously installed level of a fileset update is in the broken state, the -acgN flags must be used when that fileset update is installed again.

Summary Report Values

The summary report identifies the name of the product option and the part of the product. Other information given includes the requested action (event) and the result of that action.

Event Values

The Event column of the summary report identifies the action that has been requested of the installp command. The following values may be found in this column:

Result Values

The Result column of the summary report gives the result of installp performing the requested action. It can have the following values:

Flags

package:fileset:v.r.m.f:PTF:type:state:supersede:\
sup_ptf:sup_state:latest_sup:quiesce:Descr:\
netls_vendor_id:netls_prod_id:netls_prod_ver 

Return Values

A zero (0) return value indicates that all attempted installations were successful, or that no processing was required for the requested action on the requested filesets (for example, if a requested fileset was already installed).

A nonzero return value indicates that some part of the installation was not successful.

A summary report is given at the end of the installp output that lists the status of each of the software products that were to be installed. For those software products that could not be installed or whose installation failed, the user can search for the cause in the more detailed information that is continually displayed from the installp command during the installation process.

Security

Privilege Control: Only the root user can run this command.

Auditing Events:

Examples

1. To list all software products and installable options contained on an installation cartridge tape, enter:

   installp -L -d /dev/rmt0.1

2. To list all customer-reported problems fixed by all software products on an installation tape, enter:

   installp -A -d /dev/rmt0.1 all

3. To install (automatically committed) all filesets within the bos.net software package (located in the /usr/sys/inst.images directory) and expand file systems if necessary, enter:

   installp -aX -d/usr/sys/inst.images bos.net

4. To reinstall and commit the NFS software product option that is already installed on the system at the same level (from tape), enter:

   installp -acF -d/dev/rmt0.1 bos.net.nfs.client 4.1.0.0

5. To install (apply only) certain updates that are contained on diskette for the TCP/IP software product, enter:

   installp -a bos.net.tcp.client 4.1.0.2 bos.net.tcp.server 4.1.0.1

6. To remove a fileset named bos.net.tcp.server, enter:

   installp -u bos.net.tcp.server

7. To specify an alternate storage directory on a remote file system for a BOSNET TCP/IP update with -t/temp_space, see the following example: the save directory becomes /temp_space/My_Hostname/usr/lpp/bos.net/bos.net.nfs.client/4.1.1.0.save.

   mount Server_Name:/Save_Area /temp_space
      
   installp -a -t /temp_space/My_Hostname  \ 
   bosnet.nfs.client 4.1.1.0

8. In order to capture a log file of all output from the installp command, the script command can be used as in the following example. Output is written to the typescript file in the current directory.

   script
   installp ...
   <Ctrl>d

   or

   installp ... 2>&1 | tee /tmp/inst.out

   In the second example, output is written to the screen and a copy is saved.
9. To preview (without performing) the installation of the Application Developer bundle of software using the installp command, enter:

   installp -pacgXd /dev/rmt0.1 -f /usr/sys/inst.data/sys_bundles \
   /App_Dev.bnd

10. To install TCP/IP and one of its updates that are both contained in the /usr/sys/inst.images, enter:

    A summary report is given at the end of the installp output that lists the status of each of the software products that were to be installed. An example summary report for the previous installp command follows:

    Installp Summary
    ----------------
    Name                 Level        Part       Event        Result
    -----------------------------------------------------------------
    bos.net.tcp.client   4.1.0.0      USR        APPLY        SUCCESS
    bos.net.tcp.client   4.1.0.0      ROOT       APPLY        SUCCESS
    bos.net.tcp.client   4.1.0.2      USR        APPLY        SUCCESS

    Note: This summary is also saved in /var/adm/sw/installp.summary until the next installp invocation. The header file inuerr.h in the /usr/include directory describes the fields making up the records in the installp.summary file.

Files

Related Information

The bffcreate command, inudocm command, inutoc command, lppchk command, lslpp command, sysck command.