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

What Is in an SPR Note
Managing Software Changes—427169-005
B-3
SID Fields
Changes Introduced in the SPR
This section categorizes and summarizes each change introduced in the SPR. The
number next to the description of the fix or feature corresponds to the number of
the description of the fix or feature in the SPR’s softdoc. The categories include:
•
Consider using this SPR to avoid possible outage <list of problems>.
•
Consider using this SPR to avoid <list of problems>.
•
Consider using this SPR to obtain <list of changed or new behavior>.
•
Consider using this SPR to obtain features <list of features>.
Installation Impact
Indicates what you have to do to install this SPR and all of its requisites (not just
the SPR itself); for example, whether you will have to system load your system or
whether a subsystem might have to be stopped and then restarted. The installation
impact field can have these values:
•
System load
•
System load due to unconditional requisite
Installation of the SPR itself does not require a system load, but the SPR has a
primary unconditional requisite SPR (either direct or indirect) that requires a
system load and that is not already present in any of the RVUs with which the
requiring SPR can be used.
•
Possible system load depending on current software configuration
Installation of the SPR itself does not require a system load, but the SPR has
either:
°
A primary unconditional requisite, either direct or indirect, that requires a
system load and is present in some, but not all, of the RVUs with which the
requiring SPR can be used.
°
A primary conditional requisite, either direct or indirect, that requires a
system load (regardless of whether it is present in none or some of the
RVUs with which the requiring SPR can be used).
•
Subsystem interruption
•
Interruption due to unconditional requisite
•
Possible subsystem interruption depending on current software configuration
•
Minimal
•
No system impact