beautypg.com

Collect the information needed for the build, Specify params as needed, Assemble the planner instructions to the operator – HP Integrity NonStop H-Series User Manual

Page 111: Initiate a build/apply request

background image

Collect the Information Needed for the Build

During the Build request, you must provide 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

Values for all Scheduling, Output, SYSGEN, TSV Locations, and File Placement options. Default
values are provided, but you can specify different values on any of those tabs as needed for
this Build/Apply. You cannot change the TDL locations of OSS files.

Determine the required SYSnn subvolume:

If a system generation is required: you must specify a different SYSnn than the currently running
(active) SYSnn, and then use that subvolume when you apply the new configuration.

CAUTION:

Selecting the active SYSnn when system generation is required will cause the

Apply to stop with errors. To load your system from the current SYSnn, enter a different SYSnn
and then change the SYSnn name after the Apply. See

“Renaming the Managed SYSnn

(Optional)” (page 127)

.

If a system generation is not required: you can specify either the current 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.

Specify PARAMs as Needed

In most cases, you can use the defaults, but if needed, you can specify PARAMs before performing
the Build/Apply. Options include:

To prevent the creation of the software configuration Dial-out Report that is created during a
build of a configuration. By default, this report is placed in the $volume.SYSnn.SWCONFIG
file on the target system. After successful completion, ZPHIRNM copies the report to a new
location to update the date and time of activation. The copy of the report at the target displays
both the Apply date and the Activation date. After successfully updating the dial-out report,
ZPHIRNM generates an EMS event to indicate that the dial-out report is to be sent and the
location of the modified dial-out report. To prevent the creation of that report, you can use the
“NO-ACTIVATION-DIALOUT-REPORT” PARAM, as described in

“PARAM Summary” (page 241)

.

If Safeguard is running on the target system, you can choose to protect the files in your new
configuration with Guardian security instead of Safeguard. See

“IGNORE-SAFEGUARD-PROTECTION” (page 244)

.

See

“PARAM Summary” (page 241)

.

Assemble the Planner Instructions to the Operator

Planner instructions to the operator – instructions to follow when applying the new software on the
target system – can be entered or edited in the “Planner instructions to the operator” field located
on the Main tab of the Install Software window in the NonStop Software Essentials interface. You
cannot access softdocs directly through NonStop Software Essentials, but you can copy and paste
from the softdocs (available in Scout) into the Planner instructions field or the Revision Notes on a
new revision page.

Initiate a Build/Apply Request

Upon creating or editing a new software revision and clicking the Build/Apply button in NonStop
Software Essentials, a work panel is loaded in which you input parameters to create and submit
the Build/Apply request. This window is titled “Install Software - ” followed by the logical target
name and current revision number, then the subtitle “Step 2: Submit a Build/Apply request.

Initiate a Build/Apply Request

111

This manual is related to the following products: