Patch Management User Guide for HP-UX 11.x Systems

The following list describes a subset of available attributes:
• ancestor
— Applies to filesets.
— Identifies the fileset that must be on the system for the patch to be installable.
• category_tag
— Applies to products or filesets.
— Provides a label for a fileset or product. Several tags are defined during patch creation;
users can create others with the swmodify command.
— See “Category tags” (page 20).
• is_patch
— Applies to both patch products and filesets.
— When set to true, is_patch enables patch behavior.
• is_reboot
— Applies to filesets.
— When set to true, is_reboot indicates that installation of the fileset will cause the
system to reboot.
• patch_state
— Applies to patch filesets.
— Records the condition of patches.
— See “Patch state” (page 19).
• readme
— Applies to products.
— Contains the patch's original text file.
• software_spec
— Applies to bundles, products, or filesets.
— Contains the fully qualified identifier for the bundle, product, or fileset. Uniquely
identifies a specific instance of a software object.
• state
— Applies to filesets.
— Provides useful information about the installation state of software.
— See “State” (page 20).
• supersedes
— Applies to patch filesets.
— Lists all prior filesets that a patch fileset supersedes.
— See “Ancestors and supersession” (page 25).
• superseded_by
— Applies to patch filesets.
— Records the software specification of the fileset that superseded the fileset on a given
system. This attribute is set only for installed patch filesets, and never in software depots.
— See “Ancestors and supersession” (page 25).
You can show these attributes with the swlist command using the -a attribute argument,
replacing attribute with one of the previously listed attributes. For more information about
the swlist command, see “Which patches are on a system?” (page 21).
30 HP-UX patch overview