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

Building and Applying a New Configuration
DSM/SCM User’s Guide — 529846-014
9 - 3
FRABIBAB
Build/Apply. You do not need to resolve all discrepancies before accepting them, but
you will have a record of the differences in the software configuration in case of
problems. Before accepting the discrepancies, you can add SPRs or additional
software as needed.
Use the activation package files only to compare 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 delete all logical targets or initialize DSM/SCM.
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.
FRABIBAB
First Real Apply Build, Initial Build Apply Bypass (FRABIBAB) bypasses the
initialization Build/Apply and performs a normal Build/Apply on the target. The
procedure is no different from a normal Build/Apply except that it carries implications
on 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.
File Locations
DSM/SCM places files during an apply in a target subvolume (TSV) or target directory
location (TDL).

Target Subvolume (TSV)
When DSM/SCM places Guardian files during an Apply, and a different version of
the file already exists in the TSV, the file is placed under a temporary name of the
form ZFBccncc. Do not purge these ZFB* files. They are deleted in normal
DSM/SCM processing.
Multiple copies of changed files might be in the TSV at a given time. TSVs might
contain Guardian files under both their actual names and their temporary names,
requiring more disk space for software on target systems. Do not purge these files.
DSM/SCM deletes them when possible.