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

STOPSCM
The STOPSCM program stops DSM/SCM:
Starting DSM/SCM
Before using the NonStop Software Essentials interface or CNFGINFO:
1. Check that you are logged on using the super ID (255,255) or the DSM/SCM user ID.
NOTE: You must be a member of a super-user group to start TMF.
2. Check that ZDSMSCM is the current subvolume.
> VOLUME $volume.ZDSMSCM
$volume
is the volume where the ZDSMSCM subvolume is located.
NOTE: If you are using multiple logical targets on a system, always start DSM/SCM from
the first ZDSMSCM subvolume installed on the target system, from which INITENV was run,
to ensure that the correct installation files are used. You can also run STOPSCM from the same
ZDSMSCM subvolume if DSM/SCM has finished processing all of its tasks.
3. If a TMF process is not running, start it:
NOTE: For Steps 2 and 3, if you are unsure if TMF or DSM/SCM is running, enter the
provided commands. If they are already running, they continue to run unaffected.
> TMFCOM START TMF
4. Run STARTSCM:
> RUN STARTSCM
Stopping DSM/SCM
You must stop DSM/SCM before:
• Running INITENV
• Moving a DSM/SCM database
• Running ZPHIRNM
To stop DSM/SCM:
1. If the Planner Interface is running, a connection error might appear after you stop DSM/SCM.
To avoid this error, log off the Planner Interface before stopping DSM/SCM.
2. Check that you are logged on as the super ID (255,255) or the DSM/SCM user ID.
3. Check that ZDSMSCM is the current subvolume. At a TACL prompt, enter:
> VOLUME $volume.ZDSMSCM
4. Run STOPSCM:
> RUN STOPSCM
Stopping All Applications
Before running ZPHIRNM or stopping the system, you must stop all applications, including
DSM/SCM and TMF:
Starting and Stopping DSM/SCM 39