You can also show the filesets that a given patch has superseded. These superseded filesets will be listed whether or not they are installed on a system. This is done by using the swlist command to list the supersedes attribute of the patch. Note that the first patch of any particular patch supersession chain does not have a supersedes attribute. In the following example, patch PHSS_28681 is shown to supersede patches PHSS_27875, PHSS_26498, and PHSS_25201. (The output has been reformatted to improve readability.)
swlist
For example:
$ swlist -l fileset -a supersedes PHSS_28681
#Initializing...
#Contacting target "some_system"...
#Target: some_system:/
#
# PHSS_28681
Advanced topic: supersession and the patch_state attribute
When a superseding patch is applied to a system, the superseded patch (if there was one) remains on the system but is not active. Only the top patch of the chain is in the active (applied) state. For more information about patch state, see “Patch state” (page 19).
You can use the following swlist command to show the patch_state attribute for patch patch_id:
swlist -a patch_state -x show_superseded_patches=true patch_id
It is important to note that the availability of a newer, superseding patch does not preclude the use of the older patch. Depending on the circumstances, a superseded patch might be a better choice than the patch superseding it. Older patches have had more exposure to varied,
Because
Patch supersession chains can be more complex than the one shown in Figure
28