Software Distributor Administration Guide for HP-UX 11i

Managing Patches
Patch Management Tasks and Examples
Chapter 5 171
Patch Management Tasks and Examples
installing copying, interactive patch management, removal, rollback,
committing patches, verifying patches
Installing Patches
Installation of patch products follows the same rules as any other SD
installation. The key difference is that patch selection and mechanisms
let you select only the patches that meet specified criteria. Selection
mechanisms for patches are:
•The category_tag attribute and corresponding category objects.
•The patch_filter, patch_match_target, and
autoselect_patches options.
When you install a patch, SD updates the applied_patches attribute of
the fileset that has been patched and updates the INFO file information
to include the patched file’s attributes. Also (if the patch_save_files
option is set to true), files that would be overwritten are stored in a
special save area in the IPD.
When a patch is installed, by default it has the patch_state of applied.
When the patch is committed (rollback files are removed) or it has been
installed without saving rollback files, it has the state of committed.
When the patch is superseded, the patch_state is set to superseded,
and the superseded_by attribute is set to the
software_specification
of the superseding patch fileset.
If a patch is both committed and superseded, its patch_state is set to
committed/superseded.
Installing Patches in Same Session as Base Product
If you select a non-patch fileset for installation and patch filesets for that
base fileset exist in the same source depot, all applicable patches are
selected by default as long as the autoselect_patches option is set to
its default value of true. The following rules also apply:
• Automatic patch software selections are filtered as defined by the
patch_filter option.