Lists installed software products.
lslpp { -d | -E | -f | -h | -i | -l | -L | -p } [ -a] [ -c] [ -J ] [ -q ] [ -I ] [ -O { [ r ] [ s ] [ u ] } ] [ FilesetName ... | -b File | all ]
lslpp -w [ -c ] [ -q ] [ -O { [ r ] [ s ] [ u ] } ] [ FileName ... | all ]
lslpp -S [A|O]
lslpp -e
The lslpp command displays information about installed filesets or fileset updates. The FilesetName parameter is the name of a software product. The File parameter specifies a bundle file to use as a fileset list.
When only the -l (lowercase L) flag is entered, the lslpp command displays the latest installed level of the fileset specified for formatted filesets. The base level fileset is displayed for formatted filesets. When the -a flag is entered along with the -l flag, the lslpp command displays information about all installed filesets for the FilesetName specified. The -I (uppercase i) flag combined with the -l (lowercase L) flag specifies that the output from the lslpp command should be limited to base level filesets.
The lslpp command and the compare_report command both show information about interim fixes installed on the system. The lslpp -L or lslpp -Lc command and the lslpp -e command must be run by root. Any interim fix information returned is used by the compare_report command. The information includes an interim fix label and a level value. The interim fix label is the equivalent of a fileset name, and its level is based on the time (YY.MM.DD.HHMMSS, where YY is the year, MM is the month, DD is the day, HH is the hour, MM is the minute, and SS is the second) in which the interim fix was packaged. If a non-root user runs these commands, only software products and levels are returned, and interim fix information is not included.
The -d, -f, -h, -i, -l (lowercase L), -L, and -p flags request different types of output reports.
The -a, -c, -J, and -q flags specify the amount and format of the information that is displayed in the report.
The -O flag specifies that data is to come from a specified part of the fileset. The part may be the root part, -Or, the share part, -Os, or the usr part, -Ou.
The default value for the FilesetName parameter is all, which displays information about all installed software products. Pattern matching characters, such as * (asterisk) and ? (question mark), are valid in the FilesetName parameter. You don't have to enclose these characters in '' (single quotation marks). However, using single quotation marks prevents you from searching the contents of your present directory.
Much of the output from the lslpp command is understandable without an explanation. Other fields contain data that needs to be defined. The following sections define terms used in several of the output fields.
The state field in the lslpp output gives the state of the fileset on your system. It can have the following values:
| State | Definition |
|---|---|
| APPLIED | The specified fileset is installed on the system. The APPLIED state means that the fileset can be rejected with the installp command and the previous level of the fileset restored. This state is only valid for Version 4 fileset updates and 3.2 migrated filesets. |
| APPLYING | An attempt was made to apply the specified fileset, but it did not complete successfully, and cleanup was not performed. |
| BROKEN | The specified fileset or fileset update is broken and should be reinstalled before being used. |
| COMMITTED | The specified fileset is installed on the system. The COMMITTED state means that a commitment has been made to this level of the software. A committed fileset update cannot be rejected, but a committed fileset base level and its updates (regardless of state) can be removed or deinstalled by the installp command. |
| EFIX LOCKED | The specified fileset was installed successfully and locked by the interim fix (interim fix) manager. |
| OBSOLETE | The specified fileset was installed with an earlier version of the operating system but has been replaced by a repackaged (renamed) newer version. Some of the files that belonged to this fileset have been replaced by versions from the repackaged fileset. |
| COMMITTING | An attempt was made to commit the specified fileset, but it did not complete successfully, and cleanup was not performed. |
| REJECTING | An attempt was made to reject the specified fileset, but it did not complete successfully, and cleanup was not performed. |
The action field in the lslpp output identifies the installation action that was taken for the fileset. The following values may be found in this field:
| Action | Definition |
|---|---|
| APPLY | An attempt was made to apply the specified fileset. |
| CLEANUP | An attempt was made to perform cleanup for the specified fileset. |
| COMMIT | An attempt was made to commit the specified fileset. |
| REJECT | An attempt was made to reject the specified fileset. |
The status field in the lslpp output identifies the resultant status in the history of installation actions. The following values may be found in this field:
| Status | Definition |
|---|---|
| BROKEN | The fileset was left in a broken state after the specified action. |
| CANCELED | The specified action was canceled before it completed. |
| COMPLETE | The commitment of the fileset has completed successfully. |
You must specify one of the mutually exclusive flags: -d, -e, -E, -f, -h, -i, -l, -L, -p, -S, and -w.
lslpp -l "bos.rte.*"lslpp -La bos.rte.filesystemlslpp -ha 'bos.net.*'lslpp -f bos.rte.lvmlslpp -w /usr/sbin/installpOutput similar to the following displays:
File Fileset
Type
-----------------------------------------------------------------
/usr/sbin/installp bos.rte.install File
lslpp -w "*installp*"Output similar to the following displays:
File Fileset
Type
-----------------------------------------------------------------
/usr/sbin/installp bos.rte.install File
/usr/clvm/sbin/linstallpv prpq.clvm File
/usr/lpp/bos.sysmgt/nim/methods/c_installp
bos.sysmgt.nim.client File
lslpp -wlslpp -L cdrecordlslpp -L -b Serveror:
lslpp -L -b /usr/sys/inst.data/sys_bundles/Server.bnd| /etc/objrepos/history | Specifies installation and update history information of all software products on the root. |
| /usr/lib/objrepos/history | Specifies installation and update history information of all software products on the /usr file system. |
| /usr/share/lib/objrepos/history | Specifies installation and update history information of all software products on the /usr/share file system. |
| /etc/objrepos/lpp | Specifies installation information of all software products on the root. |
| /usr/lib/objrepos/lpp | Specifies installation information of all software products on the /usr file system. |
| /usr/share/lib/objrepos/lpp | Specifies installation information of all software products on the /usr/share file system. |
| /etc/objrepos/product | Specifies installation and update information of all software products on the root. |
| /usr/lib/objrepos/product | Specifies installation and update information of all software products on the /usr file system. |
| /usr/share/lib/objrepos/product | Specifies installation and update information of all the software products on the /usr/share file system. |
| /etc/objrepos/inventory | Specifies names and locations of files in a software product on the root. |
| /usr/lib/objrepos/inventory | Specifies names and locations of files in a software product on the /usr file system. |
| /usr/share/lib/objrepos/inventory | Specifies names and locations of files in a software product on the /usr/share file system. |
| /usr/sys/inst.data/sys_bundles/ and /usr/sys/inst.data/user_bundles/ | Known locations for bundle files. Bundle files should have a .bnd extension. |
来自 “ ITPUB博客 ” ,链接:https://blog.itpub.net/9225895/viewspace-1027654/ ,如需转载,请注明出处,否则将追究法律责任。