Software Distributor Administration Guide for HP-UX 11i

Managing Patches
Patch Management Tasks and Examples
Chapter 5180
These rules govern patch removal and rollback:
Using swremove to remove the base fileset of a patch fileset also
removes all patches to that fileset.
Files saved for rollback are also removed when the base fileset to
which they apply is updated or removed from the system.
Removal of a patch automatically rolls back the saved files, unless:
You set the patch_save_files option to false at the time you
installed the patches.
You also remove or update the base fileset.
You performed a swmodify operation on the patch with the
patch_commit option set to true.
You cannot roll back an installed patch that has been superseded
unless you first roll back the superseding patch.
SD performs disk space analysis (DSA) on the save area in the same
way it performs DSA on regular file locations.
To save disk space when you are certain a patch operates correctly, you
may wish to commit the patch by removing the rollback files saved by the
patch_save_files option.
To commit a patch, invoke swmodify on the patch with the
-x patch_commit=true option. (The default value is false.)
For example, to commit the patch PHKL_1234 and remove its
corresponding rollback files:
swmodify -x patch_commit=true PHLK_1234
NOTE NOTE: When you commit a patch and remove its rollback files, all
patches that are superseded by this patch are also committed.