Managing Software Changes (G06.25+, H06.03+, J06.03+)

Release Management Overview
Managing Software Changes—427169-005
1-5
Software Product Revisions (SPRs)
unrestricted access. In rare situations, a defect repair will work correctly only under
certain conditions, and access is therefore restricted.
A restricted SPR that supersedes an unrestricted SPR contains all the features
and fixes present in that SPR. If you do not need a fix specific to the restricted
SPR, you can install the superseded unrestricted SPR.
Superseded SPRs
When one SPR supersedes another, the superseding SPR contains all of the features
and fixes (except for those that HP has officially withdrawn) found in the superseded
SPR (both SPRs are for the same product version).
These fixes and features include all functions that make a superseded SPR a requisite
of another SPR. Thus, a superseding SPR that is found to be suitable for installation in
all other respects can replace a cited requisite that it supersedes.
The softdoc describing an SPR lists superseded SPRs in alphabetic order (for
example, AAE, AAH, AAP, AAS). In some cases, only the last 20 superseded SPRs
are listed. You can use Scout for NonStop Servers to download superseded SPRs, and
view superseding and superseded SPRs for a product version. Note that superseding
does not imply anything about the relationship between SPRs such as:
•
Access
A restricted SPR can supersede an unrestricted SPR.
•
Obtainability
Superseded SPRs are obtainable, and the most current SPR usable with your
software configuration might be superseded.
•
Status (recalled, withdrawn, and obsolete SPRs can be superseded)
There might be no active SPR available for a product version. The most current
SPR could be a restricted, withdrawn, or recalled SPR.
•
Applicability to the same RVU
Superseding does not imply that an SPR is a suitable replacement for an SPR it
supersedes that you have already installed. Several other factors should be
considered when determining whether an SPR is a suitable replacement in a
specific software configuration:
°
Is the SPR applicable with the installed RVU? A superseding SPR might not be
applicable everywhere, or even anywhere, the superseded SPR is applicable.
°
Is the SPR usable with other SPRs on the RVU (occasionally, opposing
requisites might preclude using an SPR that would otherwise be usable)?
°
Is the perceived risk that using the SPR might introduce or uncover new
problems sufficiently low?