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

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.
6. When the Build/Apply completes, activate the new revision.
Build/Apply After Initializing a Host
To perform a Build/Apply after initializing a host system:
1. After running INITENV on the system, use the Target Maintenance Interface (ZPHITMI) to define
an Operator and provide values for System Maintenance and Volume Maintenance.
When defining an Operator decide if the “Request an Audit” permission should be enabled;
it is required to submit a Software Audit request in NonStop Software Essentials.
2. Log on to NonStop Software Essentials as the Host Administrator and owner of the DSM/SCM
database (as defined during INITENV). Add the same user as a Planner using the Manage
Planners link on the NonStop Software Essentials Home page (planner permissions are updated
immediately without having to log in again); then:
3. Define the values for the Host Configuration (this is the same as defining values for the
Configuration Manager Profile in the DSM/SCM Planner Interface).
4. Define the values for the archive and scratch volumes using the Manage Volume Usage link
on the NonStop Software Essentials Home page.
5. Modify both the Physical and Logical Target values under the “Target Maintenance” heading
on the Configuration Revisions page. A single popup dialog is used to define both Physical
and Logical Target values.
6. Receive Software into the archive to be installed on the target.
7. Create new Revision 1 for the target.
Build/Apply After Initializing a Host 135