AIX 5L Problem Determination - IBM Redbooks

Note: Before installing a new set of updates, you should consider committing
any previous updates that have not yet been committed.
If you decide to return to the previous version of the software, you must reject the
updated version that was installed. Rejecting a service update deletes the
update from the system and returns the system to its former state. A service
update can only be rejected if it has not yet been committed. Once committed,
there is no way to delete an update except by removing the entire fileset, or by
force-installing the fileset back to a previous level.
When you install a base level fileset, it is automatically committed during
installation. If you want to delete a fileset, it must be removed (as opposed to
rejected) from the system. A fileset is always removed with all of its updates.
To display the installation and update history information for the
bos.sysmgt.trace fileset, use:
# lslpp -h bos.sysmgt.trace
Fileset Level Action Status Date Time
--------------------------------------------------------------------------
Path: /usr/lib/objrepos
bos.sysmgt.trace
4.3.3.0 COMMIT COMPLETE 06/15/00 09:57:28
4.3.3.11 COMMIT COMPLETE 06/16/00 11:19:13
Path: /etc/objrepos
bos.sysmgt.trace
4.3.3.0 COMMIT COMPLETE 06/15/00 09:57:33
4.3.3.11 COMMIT COMPLETE 06/16/00 11:19:14
As shown, the fileset bos.sysmgt.trace was once updated. It is now in the
committed state at the fix level 4.3.3.11.
If something goes wrong during the software installation that causes the
installation to be prematurely canceled or interrupted, a cleanup must be done.
To do this, use smitty maintain_software or use the installp command:
installp -C
Figure 11-1 on page 311 shows how to clean up after an interrupted installation
using SMIT.
310 IBM ^ Certification Study Guide - AIX 5L Problem Determination Tools and Techniques