DSM/SCM User's Guide

Configuring DSM/SCM
DSM/SCM User’s Guide — 529846-014
5 - 30
Reinitializing DSM/SCM

Check that the Planner Interface is pointing to the CONFTEXT file for the
backup host system, not for the original primary host.

Purge the ZMP99999 file from $SYSTEM.SYSTEM.
The backup host system is successfully converted to serve as the primary host system.
Treat it as the primary host system for future DSM/SCM operations.
Reinitializing DSM/SCM
Reinitializing erases all information in the host database, target database, and archive.
It does not affect the installed software unless you choose a full activation package
instead of an initialization package. When you reinitialize DSM/SCM, INITENV purges
old DSM/SCM files to clean up the system.
Task 1: Run INITENV to Reinitialize
1. Log on to your system as the DSM/SCM user ID. For example:
> logon 255.255
password:
2. Make ZDSMSCM the current subvolume:
> VOLUME $volume.ZDSMSCM
3. Check that TMF is running:
> TMFCOM START TMF
4. Check that DSM/SCM is not running:
> RUN STOPSCM
For more information, see Starting and Stopping DSM/SCM on page 2-2.
5. Run INITENV:
> RUN INITENV
Use this checklist as a quick guide to reinitialize a host or physical target system.
The right column provides common entries and actions to perform for a NonS
top
system that is network connected, uses Winsock, and has the ZDSMSCM
subvolume located on $DSMSCM. For more information, see Configuring a Host or
Target System on page 5-2.
Note. After you reinitialize a host that has associated physical targets, you also need to
separately reinitialize each target system.