Installation and Upgrade Guide

Overview of Installing G06.24
G06.24 Software Installation and Upgrade Guide—528593-005
1-6
Managing Microcode and Firmware
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.
Managing Microcode and Firmware
You must ensure all microcode and firmware within your system is managed properly,
updating it as necessary when new versions become available. Failure to do so can
result in a wide range of system problems, from intermittent faults to partial or complete
system outages.
Updating Disk and Tape Bootstrap Microcode
When you perform a system load, a disk or tape bootstrap microcode file is used by
the system during its startup process. You must use the SCF program to update these
files as new versions become available.
The SCF CONTROL DISK, REPLACEBOOT command converts a work file
(SYSDISC) containing the new disk bootstrap loader and controller microcode to a
special format and then writes it into space reserved for bootstrap microcode on the
system disk.
Note. Always check Scout for the most recent updateable firmware.