Managing Software Changes (G06.24+)

Software Installation Planning
Managing Software Changes—427169-003
4-11
Task 8: Install the Release Version Update and
Additional SPRs
Task 8: Install the Release Version Update and Additional SPRs
See the appropriate installation and migration guides and the README file for release-
specific information on installing new RVUs.
See the DSM/SCM User’s Guide for information on using the DSM/SCM product to
install new RVUs and SPRs.
Install additional SPRs in a timely manner to avoid encountering known problems that
have already been resolved. When you install an SPR, make sure you have all
relevant information accumulated and examined during your review and research
phases. If you plan to install more than one SPR or requisite, verify the order of
installation.
When installing an individual SPR, any steps to be carried out before and after those
associated with DSM/SCM are listed in the “Installation Considerations” section of the
SPR’s softdoc addendum. For example, for some products, it is necessary to save
subsystem configuration files before they are replaced during the installation. On
occasion, microcode of a certain version must be downloaded before the DSM/SCM
steps can occur.
The installation instructions in the “Installation Considerations” section of the softdoc
addendum are relevant only to the SPR being documented. You must use judgment in
composing aggregate instructions to install multiple SPRs simultaneously (whether
dependent on each other or not).
Task 9: Create an SPR Log File
Create an SPR log file to maintain an accurate and current software profile on your
system.
Be sure to document the reasons for your decision to install an SPR. Maintaining an
SPR log file makes it easier to process new SPR information as it becomes available
and is invaluable the next time you plan to move to a new RVU (see Keeping Track of
SPRs on page 3-15).
Caution. Use the DSM/SCM product to properly install an SPR. Using other ways to install HP
NonStop Kernel software (for example, copying files into the SYSnn subvolume) can have
serious consequences later. The DSM/SCM product maintains a database that describes the
software it installs, and bypassing it invalidates its database and can cause subsequent
executions to produce undesirable results.