Managing Software Changes (G06.24+)

Evaluating Software Changes
Managing Software Changes—427169-003
3-5
Evaluating SPR Introduction Documents (SIDs)
Evaluating SPR Introduction Documents (SIDs)
SPR Introduction Document
An SPR Introduction Document (SID) summarizes the fixes and features introduced in
an SPR. SIDs also highlight fixes that correct defects that could conceivably cause an
outage, even under very unlikely conditions, including defects that do not warrant an
Outage Prevention Notification.
An SID is helpful in determining the applicability of an SPR for your particular
computing environment. However, it does not supply all the information needed if you
decide you cannot ignore the SPR. In that case, you should also review the SPR’s
softdoc in detail.
SIDs are published in Software Revision Notifications through ExpressNotice, are
included as part of SPRNOTEs, and are viewable through Scout for NonStop Servers.
How to Read an SID
SIDs contain the following information (for a more detailed description, see SID Fields
on page B-2):
•
The SPR ID, access, and product name.
•
A list of the RVUs with which you can use this SPR as of the specified date. Unless
listed, the SPR is not usable with RVUs shipped prior to that date.
•
The number of fixes and features introduced in the SPR.
•
An overall assessment of the benefits of installing the SPR.
•
Brief descriptions of the changes introduced in the SPR, categorized by use:
°
Consider using this SPR to avoid possible outage <list of defects>
°
Consider using this SPR to avoid <list of defects>
°
Consider using this SPR to obtain <list of changed or new behavior>
°
Consider using this SPR to obtain features <list of features>
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.
•
Information about 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.