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

Loading the System
DSM/SCM User’s Guide — 529846-014
12 - 3
Stopping the System by Halting the Processors
Stopping the System by Halting the
Processors
The method you use to halt the processors varies depending on the type of system.
For more information, refer to the OSM online help.
This example describes halting the processors on a NonStop system:
1. Check that DSM/SCM, all other user applications, TMF, and all other subsystems
are stopped, and that the spooler is drained.
2. Log on to OSM Low-Level Link.
3. On the Low-Level Link toolbar, click Processor Status.
4. Shift-click to select all of the running processors.
5. From the Processor Actions list, select Halt.
6. Click Perform Action.
7. Click OK to dismiss the confirmation dialog box and initiate the action.
Loading the System
The method you use to load the system varies depending on the type of system. For
more information, refer to the OSM online help.
Normally, you would load the system from the current system configuration file. When
backing out a revision on an Integrity NonStop system or NonStop S-series system,
you should load the system from a saved system configuration file.
Running PATHCOLD
If Pathway requires a cold start of PATHMONs after you migrate to a new RVU,
STARTSCM fails when you bring up DSM/SCM on the new RVU. You get a Pathway
error indicating a cold start is required. In this case, run STOPSCM, PATHCOLD, and
STARTSCM from the ZDSMSCM subvolume.
If you must cold start PATHMON when migrating from one RVU to another:
1. If the target database is on another system, check that the line handler to that
system is up and accessible first.
2. Run PATHCOLD from the original ZDSMSCM subvolume.
Note. If you perform a DSM/SCM Build/Apply activity that uses an OSBUILD without a
PUBLIC DLL build (DSM/SCM builds the public DLL only if it is needed), timestamp
mismatch warnings are displayed during Cold load. You may ignore these warning
messages. If desired, you can perform a new Build/Apply activity with FORCE-PUBLIC-
DLL-BUILD parameter.