installp Command

Purpose

Installs available software products in a compatible installation package.

Syntax

To Install with Apply Only or with Apply and Commit

installp [ -R path ] [ -a | -a -c [ -N ] ] [ -e LogFile ] [ -V Number ] [ -d Device ] [ -E ] [ -Y ] [ -b ] [ -S ] [ -B ] [ -D ] [  -I ] [ -p ] [ -Q ] [ -q ] [  -v ] [  -X ] [ -F | -g ] [ -O { [ r ] [ s ] [ u ] } ] [ -t  SaveDirectory ] [ -w ] [ -z BlockSize ] { FilesetName [ Level ]... | -f ListFile | all }

To Commit Applied Updates

installp [ -R path ] -c [ -e LogFile ] [ -V Number ] [ -b ] [  -g ] [ -p ] [  -v ] [ -X ] [ -O { [ r ] [ s ] [ u ] } ] [ -w ] { FilesetName [ Level ]... | -f ListFile | all }

To Reject Applied Updates

installp [ -R path ] -r [ -e LogFile ] [ -V Number ] [ -b ] [ -g ] [ -p ] [ -v ] [ -X ] [ -O { [ r ] [ s ] [ u ] } ] [ -w ] { FilesetName [ Level ]... | -f ListFile }

To Deinstall (Remove) Installed Software

installp [ -R path ] -u [ -e LogFile ] [ -V Number ] [ -b ] [ -g ] [ -p ] [ -v ] [ -X ] [ -O { [ r ] [ s ] [ u ] } ] [ -w ] { FilesetName [ Level ]... | -f ListFile }

To Clean Up a Failed Installation

installp [ -R  path ] -C [ -b ] [ -e LogFile ]

To List All Installable Software on Media

installp { -l | -L } [ -e LogFile ] [ -d  Device ] [ -B ] [  -I ] [ -q ] [-E ] [ -z BlockSize ] [ -O { [ s ] [ u ] } ]

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

installp { -A| -i } [ -e LogFile ] [ -d Device ] [ -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 [ -e LogFile ] [ -O { [ r ] [ s ] [ u ] } ] [ -w ] { FilesetName [ Level ]... | -f ListFile | all }

To List Platform Specific Installable Software on Media

installp { -l | -L } { -M Platform } [ -e LogFile ] [ -d Device ] [ -B ] [ -I ] [ -q ] [ -z BlockSize ] [ -O { [ s ] [ u ] } ]

To validate signature of the software

installp -G -d Device { FilesetName [ Level ]... | -f ListFile | all }

Description

Notes:

The noclobber option of the Korn or C shell must be unset in the environment from which an installation is performed.
Update all can be accomplished with smitty or with install_all_updates command.

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 image with a different modification level or a different fix 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 (such as committed, broken, committed with applied updates, and committed with committed updates).

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

Updates that are applied to the system can be either committed or rejected later. 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. The saved files from all previous versions of the software product are removed from the system, 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.

Notes:

Committing the 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.
The signature verification is performed during the package installation. The verification is based on the level of digital signature verification policy.

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 that pertains to the product is also done, but the cleanup depends on the product and might not always be complete.

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

A software product that is to be removed from the system can be in any state. Product updates can be in either the applied or committed state, and they are also 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 are 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 the software product cannot be returned to the previous version, 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 that are replaced by an update. This option is primarily useful in the following two circumstances.

If 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. When you are satisfied with the updated system and all the applied updates are committed, disk space can be retrieved by deleting the save file system.
You do not have enough local disk space for saving replaced files but you have access to ample disk space on a remote system. In this case, you can specify a directory that is mounted from a remote file system.
If a remote file system is used, commit the updates as soon as possible. You might want to initiate the installation action as an apply and commit operation with the -ac flags. If you want to apply only to be able to reject unwanted updates, then test the newly installed updates as soon as possible and then commit or reject them.

Take into account the following considerations 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, make sure that the file system that contains 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, a warning is given stating that the save directory could not be deleted. In this case, you must delete the saved 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 canceled. 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, ensure that you back up any alternate save directories that do not reside in the root volume group.
The installation process safeguards the users with a remote save directory from the possibility of two different systems by using the same remote directory. However, use directory path names that easily and uniquely identify each user's system. For example, you can add the system's host name in the path name.
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, by using a mksysb image to install several like systems causes multiple ownerships 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 that is 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 following output resembles the output of the installp command with the -l flag:

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

The field descriptions are as follows:

Table 1. Description of the `installp -l` command output file fields
Item	Description
Fileset Name	Name of the fileset to be installed.
`Level`	Level of the fileset to be installed.
`I/U`	The type of package to which the fileset belongs. The fileset can belong to an installation package or to one of several types of update packages. The following list describes the different package types: I Indicates an installation package. S Indicates a single update. SR Indicates a required update. Whenever the installp command encounters a required update, the input list is automatically changed to include the required update. SF Indicates a required update. Whenever the installp command encounters a required update, the update is automatically included in the input list. Reserved for updates to the installp fileset. M Indicates a maintenance or technology package. This package type is a packaging update that contains only a list of other updates to be applied. This package delivers no files. ML Indicates an update package that identifies a new maintenance or technology level for the product. This package type is a cumulative set of all updates since the previous product level.
`Q`	Quiescent (quiet) column. The following list describes the values of the `Q` column. Y: Indicates that the running processes can be affected by the installation of this fileset. Refer to the documentation supplied with the software product. N: Indicates that the running processes are not affected by the installation of this fileset. B: Indicates bosboot and quiescent. b: Indicates bosboot and not quiescent.
`Content`	The following list describes the content column fields: usr, root /usr and root file systems (AIX 3.2 and later) usr /usr file system only (AIX 3.2 and later) share /usr/share file system only (AIX 3.2 and later)

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 output:

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 field descriptions are as follows:

Table 2. Description of the `installp -S` command output file fields
Item	Description
Name	Name of the installed software product fileset.
Part	The part of the fileset.
ROOT	The root file system
SHARE	/usr/share file system
USR	/usr file system.
Level	The level of the installed software product option.
State	The state of the installed software product option.

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

By using the keyword all, which indicates that all software that is contained on the specified installation media is to be installed.
By using a list of software product names, which indicates the software to be installed. Each of the software product names can optionally be followed by a level.
By using the -f flag followed by a file name, where each line in the file is an entry that contains the name of the software product, 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 ~, `, ', \, ", $, ^, &, ( ), |, {}, [], <>, and ? special characters in file names. If a file name contains any of these characters, the 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 that are 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.

Table 3. `Level` parameter format description
Item	Description
`vv`	The `vv` field is a numeric field of 1 to 2 digits that represents the version number.
`rr`	The `rr` field is a numeric field of 1 to 2 digits that represents the release number.
`mmmm`	The `mmmm` field is a numeric field of 1 to 4 digits that represents the modification level. Modification level is also called maintenance level or technology level.
`ffff`	The `ffff` field is a numeric field of 1 to 4 digits that represents the fix level.

If a user is installing an installation package from installation media that contains only installation packages, it is not necessary to specify the level. More than one installation package of the software product with different levels do not often exist on the same installation medium. However, 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 by using the -I flag or only update packages by using the -B flag. 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.

You can use the following example to install TCP/IP and one of its updates that are both contained in the /usr/sys/inst.images directory.

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

Note: If there are duplicate filesets at the same level, installp uses 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, make sure 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. The following example is an example summary report for the previous installp command:

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.
The installp command cannot install a mkinstallp package or bff image that is larger than 2 GB. An alternative is to break the bff image into multiple packages that are less than 2 GB.
If an attempt is made to update a fileset that is locked by the interim fix manager (the emgr command), a notice is displayed indicating the filesets that are locked. The lslpp command shows that any locked filesets are in the EFIXLOCKED state.
If an attempt is made to update a fileset that has an installed build date more recent than the build date of the selected fileset, a message is displayed.

Summary Report Values

The summary report identifies the name of the product option and the part of the product. Other information that is 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 is requested of the installp command. The following values are displayed in this column:

Table 4. Event values
Event	Definition
APPLY	An attempt was made to apply the specified fileset.
COMMIT	An attempt was made to commit the specified fileset update.
REJECT	An attempt was made to reject the specified fileset update.
CLEANUP	An attempt was made to perform cleanup for the specified fileset.
DEINSTALL	An attempt was made to remove the specified fileset.

Result Values

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

Table 5. Result values
Result	Definition
SUCCESS	The specified action succeeded.
FAILED	The specified action failed.
CANCELLED	Although preinstallation checking passed for the specified option, it was necessary to cancel the specified action before it was begun. Interrupting the installation process with Ctrl+c can sometimes cause a canceled action, although, in general, a Ctrl+c interrupt causes unpredictable results.

Flags

Table 6. Flags
Item	Description
-A	Displays the APAR number and summary of all customer-reported problems that are fixed in the specified software package. No installation is attempted.
-a	Applies one or more software products or updates. This flag is the default action. This flag can be used with the -c flag to apply and commit a software product update when installed.
-b	Prevents the system from performing a bosboot when one is needed.
-B	Indicates that the requested action must be limited to software updates.
-C	Cleans up after an interrupted installation and attempts to remove all incomplete pieces of the previous installation. Cleanup must be performed whenever any software product or update is in a state of either `applying` or `committing` and can be run manually as needed. For compatibility with an earlier version, other flags and parameters can be accepted with `installp -C`, but are ignored because all necessary cleanup is attempted.
-c	Commits all specified updates that are applied but not committed. When an update is committed, all other software products that it depends on must also be committed (unless they are already in the committed state). The specified software product depends on any software product that is a prerequisite or corequisite of the specified product. If the requisite software products are not in the committed state, the commit fails and error messages are displayed. The -g flag can be used to automatically commit requisite software product updates.
-D	Deletes the installation image file after the software product or update is successfully installed. When the -g flag is specified, the installation image files for any products that are automatically included are also deleted. This flag is valid only with the -a or -ac flags and is not valid with the -Or flag. This flag is also only valid when the device is a directory and an installation image file on the system where the installation is taking place.
-d `Device`	Specifies where the installation media can be found. The installation media can be a hardware device such as tape or diskette, it can be a directory that contains installation images, or it can be the installation image file itself. When the installation media is a product tape or Corrective Service tape, specify the tape device as no-rewind-on-close and no-retension-on-open. For example, /dev/rmt0.1 for a high-density tape, or /dev/rmt0.5 for a low-density tape. Use the options specified by the tape supplier. The default device is /dev/rfd0.
-e `LogFile`	Enables event logging. The -e flag enables the user to append certain parts of the installp command output to the file specified by the `LogFile` variable. By default the output of the installp command goes to stdout and stderr, unless SMIT or VSM is used, in which case the output goes to the smit.log. The `LogFile` variable must specify an existing, writable file, and the file system in which the file resides must have enough space to store the log. The log file does not wrap. Not all output is appended. Copyright information is still displayed to the user. Error messages are displayed on the screen and are sent to the file specified by the `LogFile` variable. A results summary of the installp command invocation is also displayed on the screen and sent to the `LogFile`. This flag is primarily used by NIM and BOS install to limit the output that is shown to the user, but keep useful information for later retrieval.
-E	Displays software license agreements. This flag is only valid with the -a or -l flags. If the -E flag is specified with the -a flag, a new section is displayed showing the pending license agreements that are associated with the selected filesets. If the -E flag is specified with the -l flag, output is displayed showing the license agreements that are associated with all filesets on the media.
-F	This option can be used to force the installation of a software product even if there exists a previously installed version of the software product that is the same as or newer than the version that is currently installed. The -F flag is not valid with update packages or the -g flag. When you use the -F flag, the -I flag is implicit.
-f `ListFile`	Reads the names of the software products from `ListFile`. If `ListFile` is a `-` (dash), it reads the list of names from the standard input. Software fileset names, optionally followed by a level, must be one per line of text, and any text that follows the second set of white spaces or tabs on a line is ignored. Output from the installp -l command is suitable for input to this flag.
-G	Validates the signature of the installation packages of one or more software products or updates. Note: This feature is available only with the installp command. This feature is not supported with other higher-level commands or operations such as the geninstall command or the `NIM cust` operation.
-g	When used to install or commit, this flag automatically installs or commits any software products or updates that are requisites of the specified software product. When used to remove or reject software, this flag automatically removes or rejects dependents of the specified software. The -g flag is not valid when used with the -F flag. Note: This flag also automatically pulls in a superseding update present on the media if the specified update is not present. This flag causes the newest update to be installed for a specified fileset, when there are multiple superseding updates for the same fileset on the installation media.
-I	Indicates that the requested action must be limited to base level filesets.
-i	Displays on standard output the lpp.instr, lpp.doc, lpp.README, and README files on the installation media for the software product, if they exist. This flag can take a significant amount of time for many filesets.
-J	This flag is used when the installp command is executed from the System Management Interface Tool (SMIT) menus.
-l	Lists all the software products and their separate installable options that are contained on the installation media to standard output. No installation occurs. The -l flag is not valid with the -Or flag.
-L	Displays the contents of the media by looking at the table of contents (TOC) and displaying the information in colon-separated output. This flag is used by smit and vsm to list the contents of the media. The format provided: `package:fileset:v.r.m.f:PTF:enter the following command:state:supersede:\ sup_ptf:sup_state:latest_sup:quiesce:Descr:\ netls_vendor_id:netls_prod_id:netls_prod_ver:relocatable:build date`
-M`Platform`	Specifies the `Platform` value. Any of the following values can be used to list the installable software packages: R Specifies POWER processor-based platform packages only. N Specifies neutral packages, that is, packages that are not restricted to the POWER processor-based platform. A Specifies all packages.
-N	Overrides saving of existing files that are replaced when installing or updating. This flag is valid only with the -ac flags. If there is a failure in the system during the installation, there is no recovery of replaced files when this flag is used.
-O{[r][s][u]}	Installs the specified part of the software product. The r indicates the / (root) part that is to be installed. The s indicates the /usr/share part that is to be installed. The u indicates the /usr part that is to be installed. The -O flag is not needed with standard systems because without this flag all the parts are installed by default. This flag is needed for use with the installation of diskless or dataless workstations and is designed for use by the nim command. The -Or option is not valid with the -d or -l flags.
-p	Performs a preview of an action by running all preinstallation checks for the specified action. This flag is only valid with apply, commit, reject, and remove operations (-a, -c, -r, and -u flags).
-Q	Suppresses errors and warnings that concerns products that fail to install due to instrequisites.
-q	Specifies quiet mode, which suppresses the prompt for the device, except for media volume change.
-r	Rejects all specified software updates that are applied but not committed. When a software update is rejected any other software product that depends on it (that is, those software products that have the specified software product as a requisite) must also be rejected. The -g flag can be used to reject automatically dependent software updates. The keyword `all` is not valid with the reject flag (-r).
-R `path`	Indicates a user-specified installation location.
-s	Lists information about all software products and updates that are applied but not committed. This list comprises the software that is available to be either committed or rejected.
-S	Suppresses multiple volume processing when the installation device is a CD-ROM. Installation from a CD_ROM is always treated as a single volume, even if the CD-ROM contains information for a multiple-volume CD set. This same suppression of multiple volume processing is performed if the `INU_SINGLE_CD` environment is set.
-t `SaveDirectory`	Specifies an alternate save directory location for files that are replaced by an update. The -t flag is only valid with an `apply` or an `apply/commit` operation for updates. This flag is not valid with the -N flag. The -t flag is useful when there is insufficient space in the default file systems (`/` and `/usr`) or when it is undesirable to permanently expand these file systems. It might be desirable for the specified directory to be a remote file system. A remote file system must have ample space because the installp command cannot expand remote file systems.
-u	Removes the specified software product and any of its installed updates from the system. The product can be in either the committed or broken state. Any software products that are dependent on the specified product must also be explicitly included in the input list unless the -g flag is also specified. Removal of any bos.rte fileset is never permitted.
-v	Verifies that all installed files in the fileset have the correct checksum value after the installation. Installed files are always verified for correct file size after installation. Use this flag after network or remote device installations. If any errors are reported, it might be necessary to install the software product again. Postinstallation requisite consistency checks are also started by this flag.
-V `Number`	Specifies the verbose option that provides four levels of detail for preinstallation output. The valid values for the `Number` parameter are 2, 3, or 4. The default level of verbosity, without the use of the -V flag, prints an alphabetically ordered list of FAILURES, WARNINGS, and SUCCESSES from preinstallation processing. Requisite failures are reported with emphasis on the real cause of the failure. Extraneous requisites for failed filesets are not displayed. The preinstallation output is modified by levels 2 through 4 according to the following description: 2 Prints alphabetically ordered list of FAILURES and WARNINGS. Requisite failures are displayed with additional information that describes requisite relationships between selected filesets and the requisites that cause them to fail. Failing requisites that are suppressed under `Level 1` are displayed. Preinstallation SUCCESSES are displayed in the order in which they are processed. 3 Level 3 is the same as Level 2, with the exception that more requisite information is displayed for SUCCESSES. 4 Level 4 is the same as Level 3 for SUCCESSES and WARNINGS. Requisite failures are displayed in a format that depicts detailed requisite relationships. Note: If verbosity level 2 or higher is used, the files that are restored on to the system is shown in the output. Make sure that your `/` (root) file system does not become full when the /smit.log becomes large (if smit is used to run installp command) as this will make installp command's output much more verbose.
-w	Does not wildcard `FilesetName`. Use this flag from smit so it installs only the fileset that is chosen and not the filesets that match. For example, if you choose foo.rte fileset, then the foo.rte.bar fileset is not automatically pulled in, as it would be by default, without the -w flag.
-X	Attempts to expand any file systems where there is insufficient space to do the installation. This option expands file systems based on current available space and size estimates that are provided by the software product package. It is possible to exhaust available disk space during an installation even if the -X flag is specified, especially if other files are created or expanded in the same file systems during an installation. Also, any remote file systems cannot be expanded.
-Y	Agrees to the required software license agreements for software to be installed. This flag is only valid with the -a flag.
-z `BlockSize`	Indicates in bytes the block size of the installation media. The default value of Size is 512.
`FilesetName`	The `FilesetName` field specifies the name of the software product to be installed and can specify either an entire software product or any separately installable filesets within the software product. This option can be used to specify the name of a fileset or fileset update.
`Level`	The `Level` field indicates the level of the software product or update that is to be installed and is of the form `vv.rr.mmmm.ffff`. If a fileset update has an additional fix ID (also know as ptf ID), that ID must also be specified in the Level as in `vv.rr.mmmm.ffff.ppppppp`.

Exit Status

Table 7. Exit Status
Item	Description
0 (zero)	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 is already installed).
nonzero	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.
Note:
If the Trusted Execution (TE) policy is turned on along with the TSD_LOCK policy or the TSD_FILE_LOCK policy, the installp command fails. To continue with the installation, manually turn off the TSD_LOCK policy or the TSD_FILE_LOCK policy. The installp command runs successfully with TE policies if the TSD_LOCK policy or the TSD_FILE_LOCK policy is not turned on.
RBAC users: Attention RBAC users: This command can perform privileged operations. Only privileged users can run privileged operations. For more information about authorizations and privileges, see Privileged Command Database in Security. For a list of privileges and the authorizations that are associated with this command, see the lssecattr command or the getcmdattr subcommand.

Examples

To list all software products and installable options that are contained on an installation cartridge tape, enter the following command:
```
installp -L -d /dev/rmt0.1
```
To list all customer-reported problems fixed by all software products on an installation tape, enter the following command:
```
installp -A -d /dev/rmt0.1 all
```
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 the following command:
```
installp -aX -d/usr/sys/inst.images bos.net
```
To reinstall and commit the NFS software product option that is already installed on the system at the same level (from tape), enter the following command:
```
installp -acF -d/dev/rmt0.1 bos.net.nfs.client 4.1.0.0
```
To install (apply only) certain updates that are contained on the diskette for the TCP/IP software product, enter the following command:
```
installp -a bos.net.tcp.client 4.1.0.2 bos.net.tcp.server 4.1.0.1
```
To remove a fileset that is named bos.net.tcp.server, enter the following command:
```
installp -u bos.net.tcp.server
```
To specify an alternate storage directory on a remote file system for a BOSNET TCP/IP update with -t/temp_space, enter the following command: .
```
mount Server_Name:/Save_Area /temp_space
   
installp -a -t /temp_space/My_Hostname  \ 
bosnet.nfs.client 4.1.1.0
```
The save directory becomes /temp_space/My_Hostname/usr/lpp/bos.net/bos.net.nfs.client/4.1.1.0.save.
To capture a log file of all output from the installp command, use the script command 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.
To preview the installation of the bos.net.tcp.client fileset from the CD by using the installp command, enter the following command:
```
 installp -pacgXd /dev/cd0 bos.net.tcp.client
```
To install TCP/IP and one of its updates that is contained in the /usr/sys/inst.images, use the installp command as in the following example.
A summary report is given at the end of the installp command output that lists the status of each of the software products that were to be installed. The following example is an example summary report for the previous installp command:
```
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 they make up the records in the installp.summary file.
To list software products (located in the /usr/sys/inst.images directory) that are installable on POWER processor-based machines, enter the following command:
```
installp -l -MR -d /usr/sys/inst.images
```
To update all filesets from a CD that are installed on the system, enter the following command:
```
lslpp -lc | awk -F ":" '{print $2}' | tail -n +2 > /tmp/lslpp
installp -agXd /dev/cd0 -e /tmp/install.log -f /tmp/lslpp
```
where the -e logs the output to the /tmp/install.log file.
To validate the signature of all the filesets that are included in the bos.net software package, enter the following command:
```
installp -Gd /usr/sys/inst.images bos.net
```
The bos.net software package is located in the /usr/sys/inst.images directory.

Files

Table 8. Files
Item	Description
/dev/rfd0	Specifies the default restore device.
/dev/rmt`n`	Specifies the raw streaming tape interface.
/usr/sys/inst.images directory	Contains files in backup format for use in installing or updating a complete set or subset of software products.