HP Integrity NonStop H-Series - Manual (Page 182)

Building and Applying a New Configuration
DSM/SCM User’s Guide — 529846-014
9 - 5
1. Check If Additional Disk Space Is Required
1. Check If Additional Disk Space Is Required
Before performing a Build/Apply, check the amount of additional disk space you might
need on the volume for new and changed files. For example, if your past configurations
normally take about 1500 megabytes of disk space and your new configuration has few
changes, you might need only 20 megabytes of additional free disk space (total disk
space of 1520 megabytes) to process that Apply.
2. Check That the Spooler Is Active
Check that the spooler is active if you are installing a SUT.
3. Collect the Information Needed for the Build
During the Build request, you must provide DSM/SCM with the information needed to
build the configuration revision and activate the software:

The new SYSnn if required

Planner instructions to the operator at the target system

Defaults are provided for all scheduling, output and TSV locations, system
generation, and file placement options. However, you can specify different values
for these options as needed for this Build/Apply. You cannot change the TDL
locations of OSS files.
Determine the Required SYSnn Subvolume
If system generation is required, you must specify a SYSnn subvolume that is not
currently running (active). Otherwise, you can specify the current SYSnn. subvolume.
System Generation Is Required
If DSM/SCM indicates that system generation is required, you must specify a different
SYSnn than the current SYSnn. Specify a subvolume that is not in use (not on the list)
and use it when you apply the new configuration.
System Generation Is Not Required
You can specify either the same SYSnn or a different SYSnn. However, specifying a
different SYSnn subvolume when system generation is not required might require a
system load that would otherwise be unnecessary.
Caution. Selecting the same SYSnn when system generation is required will cause the Apply
to stop with errors. To load your system from the same SYSnn, enter a different SYSnn and
then change the SYSnn name after the Apply. See
Renaming the Managed SYSnn (Optional)
on page 12-2.