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

Evaluating Software Changes
Managing Software Changes—427169-005
3-10
Researching Conditional Requisites
choose it because it fixes another defect that you conclude presents a risk in your
environment.
Conversely, if the installation of a superseding SPR requires a system load or
subsystem interruption but installation of the minimum requisite does not, installing
the minimum requisite might be a better choice.
5. Evaluate the benefits versus the risks of installing the SPR (and its requisites),
such as:
•
The installation impact (minimal or requiring a subsystem interruption or
system load)
•
The probability of encountering a defect the SPR fixes
•
Whether a superseding SPR contains additional beneficial new features
•
The size of the requisite set
•
The amount of change in the SPR and requisites that provides little or no
benefit in your configuration
Researching Conditional Requisites
Although SPRs that have conditional requisites are not common, you might
occasionally encounter them.
One example of a conditional requisite is an SPR that might be needed only if you
need a certain feature or fix. As another example, perhaps different requisites for the
same product are needed, depending on the RVU or product version you are using. In
such cases, results displayed by Scout for NonStop Servers can be misleading or, in
rare cases, incorrect. As a precaution, always review the softdocs of the SPRs you are
requesting to see if any of the requisites are conditional, especially whenever Scout
displays more than one requisite for the same product number for a given SPR. If a
requisite is conditional, you should determine whether the condition applies in your
environment. If not, you can ignore that requisite.
If a conditional requisite you ignore itself has needed requisites, you cannot
necessarily ignore them, too. Scout might not have analyzed an SPR further down the
requisite tree because the SPR was already determined to be one needed for your
RVU by the conditional requisite you are ignoring. If this is the case, you can ignore an
ignored conditional requisite’s needed requisite only if you can ignore all SPRs that
need it.
Note that every requisite SPR has an implied condition–it is needed only if you use the
product. Therefore, while you can ignore cited requisites for products you do not use,
this condition is never explicitly stated in a softdoc and is not one to which the term
conditional requisite alludes.
Note also that Scout’s requisite analysis requires that the SPRs be installed on the
specified RVU as it is currently delivered. Two situations might require you to install
requisites that differ from those Scout selects, even though its analysis is correct: