Installation and Upgrade Guide

Resuming Normal Operations
G06.24 Software Installation and Upgrade Guide528593-005
12-11
Start DSM/SCM
Start DSM/SCM
1. Run the STARTSCM macro from the ZDSM/SCM subvolume to start DSM/SCM:
> RUN STARTSCM
These messages appear:
Because the $ZHOME reliable home-term process is not an interactive process
and is always paused, no action is necessary.
2. Press Enter to have STARTSCM run the IP6031 TACL macro automatically. This
step takes several minutes.
Reset and Start the Mirror System Disk (If
Necessary)
This procedure is necessary only if you are migrating from a pre-G06.06 RVU to the
G06.24 RVU and had to replace the disk system load bootstrap program, as described
in Section 6, Replacing the Disk Bootstrap Microcode (Pre-G06.06).
After you have verified that the new disk bootstrap program is functional, reset and
start the unchanged mirror system disk (which is in the STOPPED state, substate
HARDDOWN) by using the SCF RESET and START commands. The SCF RESET
command moves the disk into the STOPPED state, substate DOWN, from which it can
be started.
8> startscm
DSM/SCM Process Startup Function - STARTSCM - T6031D46 - (31MAR2003)
Copyright Hewlett Packard Development Company L.P. 1993-2003
NOTICE: * If the hometerm chosen during INITENV, $zhome,
* is not currently in a paused state, STARTSCM and DSM/SCM
* server processes may hang indefinitely. Be sure this
* hometerm has been paused!
PATHWAY CONTROL FILE DATED: 21 APR 2003, 03:52:16
$Z03N: WARN - *1079* SERVER CB-001, NO STATIC SERVERS DEFINED
$Z03N: WARN - *1079* SERVER IS-001, NO STATIC SERVERS DEFINED
$Z03N: WARN - *1079* SERVER MISERVER, NO STATIC SERVERS DEFINED
$Z03N: SERVER OM-001, STARTED
$Z03N: SERVER SM-001, STARTED
$Z03N: SERVER SM-T-001, STARTED
$Z03N: SERVER T9154-HELP-SERV, STARTED
$Z03N: WARN - *1079* SERVER TA-001, NO STATIC SERVERS DEFINED
$Z03N: WARN - *1079* SERVER TISERVER, NO STATIC SERVERS DEFINED
$Z03N: WARN - *1079* SERVER US-001, NO STATIC SERVERS DEFINED
$Z03N: TCP TCP-H, STARTED
$Z03N: TCP TCP-T, STARTED
Caution. If you updated the disk boot code, you downed the mirrored disk. Revive the
mirrored disk as soon as possible after performing a system load. Failure to do so, can cause
data loss.