G06.25 Software Installation and Upgrade Guide

Overview of Installing G06.25
G06.25 Software Installation and Upgrade Guide—529430-001
1-6
Installing the G06.25 RVU Using DSM/SCM
3. Build and apply the new software configuration revision.
The Build process creates an activation package containing all the products listed
in the new software revision. During the Apply process, the activation package is
transferred to the target system, and the new software is placed on the target
system’s subvolumes. When the Apply request is finished, a snapshot is
automatically created and returned to the Host.
4. Activate the new operating system image.
During the Build/Apply phase, DSM/SCM places product files in their target
subvolumes (TSVs) with temporary (fabricated) file names so that the new files do
not conflict with the file names of currently running programs. You run the
ZPHIRNM program on the target system to:
•
Rename the files that currently have actual file names to fabricated names.
These files become obsolete when the new files are renamed.
•
Rename the new files, which have fabricated names, to their actual names.
After ZPHIRNM has completed renaming all OSS and Guardian files, it will run
ZMODGP if it exists in the SYSnn being activated and if:
°
The configuration being activated contains a ZCNFDEFS TSV
°
One or more of the ZcccGP files in the ZCNFDEFS TSV are new or
changed (as compared to the last configuration activated).
If none of the ZcccGP files change, ZMODGP is not run.
ZMODGP is a TACL script that makes changes to the generic-process definitions
in the system configuration database. When you use the ZMODGP script, you do
not need to hard code new generic process definitions directly into the $ZCDB
process (T6586, Configuration Services).