Managing Software Changes (G06.24+)

What Is in an SPRNOTE
Managing Software Changes—427169-003
B-4
SPR Requisites
•
No system impact
SPR Requisites
Direct Requisite
A direct requisite is one that is cited in the softdoc addendum of the requiring SPR.
Indirect Requisite
An indirect requisite is a requisite of a requisite.
Conditional Requisite
A conditional requisite is one that is needed only under certain circumstances. For
example, a conditional requisite might be required if:
•
You are using a certain RVU or set of RVUs.
•
You are using a certain product version.
•
You want a particular fix or want to use a certain feature.
If the condition does not apply to your computing environment, you can safely install
the requiring SPR without installing the conditional requisite.
Unconditional Requisite
An unconditional requisite is one that is needed if you use the requisite’s product and
your software configuration does not already contain the needed function.
Primary Requisite
A primary requisite is a requisite that is cited in an SPR softdoc. Usually, the primary
requisite is the first SPR that can be installed to satisfy the requiring SPR’s
dependency. It is possible, though rare, that an earlier restricted SPR that was not
cited because access to it is restricted would satisfy the dependency. It is also possible
that after the release of the requiring SPR, an SPR providing the requisite functionality
is released that logically precedes the cited requisite.
Secondary Requisite
A secondary requisite is an SPR that provides the function of a primary requisite but is
not a primary requisite (it supersedes or accumulates the primary requisite).
Caution. If you install the requiring SPR and need, but do not install, an unconditional
requisite, the system behaves in unpredictable ways, might not be fully functional, or its
operation might be otherwise impaired.