Patch Management User Guide for HP-UX 11.x Systems (5900-3011, April 2013)

Table Of Contents
PHSS_26619.AGRM,fa=HP-UX_B.11.11_32/64
PHSS_26622.AGRM,fa=HP-UX_B.11.11_32/64
PHSS_26638.AGRM,fa=HP-UX_B.11.11_32/64
PHSS_29169.AGRM,fa=HP-UX_B.11.11_32/64
PHSS_29183.AGRM,fa=HP-UX_B.11.11_32/64
For more information see the Software Distributor Administration Guide on the HP Business Support
Center website at http://www.hp.com/go/sd-docs.
Supersession
Supersession is the process of replacing an earlier patch with a new patch. A new patch supersedes
all previous patches for its particular patch chain. Upon installation of the new (superseding) patch,
its files replace files of the patches being superseded. Patches for HP-UX products are always
cumulative. Each new patch contains all aspects of all its preceding patches.
A series of patches form a supersession chain. A supersession chain includes the following:
The nonpatch software product being patched.
Each patch that fixes the nonpatch software product.
Each patch that fixes the patches.
Figure 1 shows a simple, hypothetical supersession chain in which a product has been superseded
by PHXX_31937, which in turn has been superseded by PHXX_32384, which has been superseded
by PHXX_43826. In general, patch numbers increase along a patch supersession chain.
Figure 1 Patch Supersession Chain in a Patch Family
The cumulative nature of a patch allows it to satisfy all dependencies on all patches it supersedes.
The converse is not true, however. A superseded patch will not satisfy a dependency on a
superseding patch. For more information about dependencies, see “Patch dependencies (page 32).
You can determine which patches a given patch supersedes by viewing either the patch's patch
details page or the patch's patch text file. See the Supersedes field for more information.
Ancestors and supersession 27