13 performing an initialization build/apply, Build/apply after initializing a target – HP Integrity NonStop H-Series User Manual
Page 134
13 Performing an Initialization Build/Apply
After you reinitialize a system (as described in
“Reinitializing DSM/SCM” (page 70)
), it is generally
advisable to perform an initialization Build/Apply before you perform a normal (primary)
Build/Apply of an RVU, SPR, or other software on any host or target system on which DSM/SCM
has been newly configured.
This section describes the steps that differ from those described in
when performing a:
•
“Build/Apply After Initializing a Target” (page 134)
•
“Build/Apply After Initializing a Host” (page 135)
Build/Apply After Initializing a Target
To perform a Build/Apply after initializing a target system:
1.
After running INITENV on the system, use the Target Maintenance Interface (ZPHITMI) to
configure system attributes on the target side of DSM/SCM, such as defining an Operator
and specifying a Scratch volume.
NOTE:
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.
Add a new Physical and Logical Target using the Configuration Revisions link on the NonStop
Software Essentials Home page. From the Configuration Revisions page, modify both the
Physical and Logical Target values by clicking the Modify button under the “Target
Maintenance” heading. A single popup dialog is used to define both Physical and Logical
Target values.
3.
Receive Software into the archive to be installed on the target.
4.
Create new Revision 1 for the target.
5.
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.
134
Performing an Initialization Build/Apply