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

> VOLUME $volume.ZDSMSCM
> RUN STOPSCM
b. Stop all other applications.
c. Stop TMF:
> TMFCOM STOP TMF
2. SCF CONTROL DISK $SYSnn-volume-name, REPLACEBOOT
SYSnn-volume-name.SYSnn.SYSDISC
This step is required only for NonStop S-series systems with major operating system or hardware
changes. Integrity NonStop systems do not contain a bootstrap program on the system disk,
so this step is not applicable.
REPLACEBOOT converts a work file (SYSDISC) containing the new disk bootstrap loader and
controller microcode to a special format and writes it to space reserved for bootstrap microcode
on the system disk (usually $SYSTEM).
For more information on running REPLACEBOOT, see the SCF Reference Manual for the
Storage Subsystem.
3.
Update FIRMWARE.
Run OSM to check firmware and perform firmware updates.
product-number product-name includes firmware changes.
This step is necessary for products with firmware changes. Some products contain firmware
that is automatically updated when the device is restarted or when the system is loaded. If
needed, use OSM to update the new firmware. The instructions include a list of the products
with firmware changes.
NOTE: Because the procedure for updating firmware varies for different RVUs, refer to the
release documentation for your RVU for the exact procedure if a firmware update is necessary.
If the host has not yet received a snapshot from the target system, DSM/SCM cannot determine
if any products have firmware changes, and this message appears:
Firmware changes cannot be determined; a snapshot has not been received.
For more information on using OSM, see the online help available within each application.
4.
RUN ZDSMSCM.ZPHIRNM SYSnn
Run ZPHIRNM to change the temporary names of the new product files to their actual names,
as explained in
Chapter 10: “Renaming Product Files Using ZPHIRNM” .
5. Run merge_whatis if ZPHIRNM indicates it is needed.
If this configuration includes OSS files that DSM/SCM manages and ZPHIRNM indicates that
you need to run merge_whatis after ZPHIRNM finishes, see the merge_whatis(8) reference
page either online or in the Open System Services Shell and Utilities Reference Manual.
6. Check for $0 EMS messages.
Correct any errors indicated in the $0 EMS messages.
Do not proceed until this step has been successfully completed.
Check the EMS message log to ensure that all DSM/SCM functions on the target system
finished successfully.
7. If you are not currently running target
then a coldload will be required.
or
Coldload is required.
If the target for which new software is being installed is not the currently running target, load
the system from the SYSnn subvolume for that target in order to run the new software. The
second instruction is included if a system load is required even though the target is already
running.
Example: Planner Instructions to Operator 121