Patch Management User Guide for HP-UX 11.x Systems (762796-001, March 2014)

◦ Filesets must exist within a product.
◦ Although a patch has a unique name, the names of the filesets contained in a patch match
the corresponding base filesets that they patch.
• Product
◦ A product is a software object that is packaged and distributed for users to acquire and
install.
◦ Products are composed of one or more filesets and might additionally contain one or
more control scripts.
◦ A product can exist either within a bundle or as its own entity.
• Bundle
◦ A bundle is an encapsulation of products into a single software object.
◦ Bundles are, sometimes, optional software objects.
◦ Product objects are included in a bundle by reference only.
◦ If the products within the bundle are all patches, the bundle is known as a patch bundle.
For more information about these software objects, see the Software Distributor Administration
Guide on the HP Business Support Center website at http://www.hp.com/go/sd-docs.
Patch bundles
Patch bundles play an important role in patch management. A patch bundle is a collection of
patches that have been grouped into a single software object to meet a specific need. Many HP-UX
users find that acquiring and installing these bundles, as opposed to acquiring and installing
patches individually, simplifies the patch management process.
Your first encounter with patch bundles might be with the standard HP-UX patch bundles. These
bundles contain patches that HP has assembled to meet a specific need. For example, the basic
purpose of Quality Pack patch bundles is to deliver defect-fix patches for proactive maintenance.
HP releases updated versions of the bundles on a regular schedule and tests them to ensure a high
level of reliability. Using standard HP-UX patch bundles can be a less error-prone and more efficient
way to patch a system than acquiring and installing individual patches. For more information, see
Chapter 6: “What are standard HP-UX patch bundles?” (page 55).
Each patch bundle includes all patch dependencies for the successful installation of all patches
that apply to a system. Additionally, some patch bundles, such as HWEnable11i and FEATURE11i,
deliver patches for the successful installation of product bundles that include I/O driver products,
for example, USB-00. The selection of product bundles with patch dependencies will result in the
automatic selection of required patches from the applicable patch bundle. This automatic selection
of patch dependencies can simplify the management and installation of products or patches with
patch dependencies.
Patch bundles also make it easier for you to determine the current level of patches on a system.
For example, there could be hundreds of individual patches contained in an installed bundle, but
the swlist command lists, by default, only the bundle name rather than each individual patch
contained in the bundle.
For example, if you install March 2013 Quality Pack patch bundles on an HP-UX 11i v3 (B.11.31)
system, you get an output similar to the following:
QPKAPPS B.11.31.1303.391 Applications Patches for HP-UX 11i v3, March 2013
QPKBASE B.11.31.1303.391 Base Quality Pack Bundle for HP-UX 11i v3, March 2013
Patch-related concepts 19