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

8. Build and Apply the revision – when prompted to “Indicate Type of Build/Apply,” choose one
of the following methods, as appropriate:
•
Build an Initialization Activation Package to synchronize the host and target database
and apply NONE of the files to the target – this process compares and synchronizes the
host database with what is actually on a target system. It does not apply activation
package files or modify the software configuration on the target system; therefore, you
cannot migrate to a new RVU using an Initialization Activation Package.
A discrepancy report shows the differences between the currently running software and
the new Revision 1 in the host database. You must evaluate the report to determine which
discrepancies need to be resolved and which are acceptable. After you have added SPRs
or additional software to resolve the discrepancies deemed necessary, and are satisfied
that the remaining discrepancies will not cause operational problems, you can perform
a full Build/Apply. You will have a record of the discrepancies that you accepted, in case
of unforeseen problems later.
Compare the activation package against target file names to determine if discrepancies
exist between what is listed in the software revision and what is actually on the target
system. This lets DSM/SCM establish a baseline of what files are on the system so that
it can send only changes on subsequent Applies.
On the first Build/Apply after applying an initialization package, DSM/SCM always
runs the system generation program to ensure the host system has an OSIMAGE that
corresponds to what is on the target system.
You can run an Initialization Build/Apply only once on a physical target system. To run
another, you must start over completely, starting with running INITENV on the target
system.
To see which files are different when you start managing OSS files, you must perform a
regular Build/Apply and run ZPHIRNM in Preview mode. If you are starting to manage
OSS files with DSM/SCM, an Initialization Build/Apply is not necessary. You cannot run
an Initialization Build/Apply when you start managing OSS files on a target that is
managed by DSM/SCM.
• Send a Full Activation Package to the target system and apply ALL files in the configuration
revision to the target.
Also called a FRABIBAB, or First Real Apply Build, Initial Build Apply Bypass, the process
is the same as a normal Build/Apply on the target except that it carries implications for
your system configuration such as this file ownership issue. To perform FRABIBAB, the
DSM/SCM user ID must be the super ID (255,255). Otherwise, you might not be able
to start DSM/SCM after the system load.
A full activation package may be chosen because it is faster to migrate the target system
to a new software revision and you may not want a revision that matches the current
software running on the target. Also, if the full activation package contains a configuration
similar to the existing configuration on the target, the time might be greatly reduced by
file adoption. Any existing files that match new files are adopted, rather than reinstalled,
reducing installation time.
Existing files that are not adopted are renamed and available only if you back out to the
prior revision. NonStop Software Essentials manages only the files in this full activation
package. It does not manage any existing files that were not adopted. Also, if the new
and existing configurations are not similar, check that enough disk space is available on
the system to place what is effectively a second complete software configuration on your
system.
Although the normal backout is not available after a FRABIBAB, a ZPHIRNM backout is
available and provides the same capability.
9. When the Build/Apply completes, activate the new revision.
136 Performing an Initialization Build/Apply