DSM/SCM User's Guide
Configuring DSM/SCM
DSM/SCM User’s Guide — 529846-014
5 - 25
Configuring a Backup Host System
Location of TCP/IP startup macros
Location of DSM/SCM SQL databases (usually same volume as ZDSMSCM
subvolume)
Location of CONFTEXT file
Location of ZDSMSCM subvolume (must be same on both systems)
2. Initialize the primary host system if needed. This is the normal initialization when
you configure your host system. You do not need to change anything for this
procedure. The primary host does not need to be connected using Expand to its
target or backup host systems.
3. Initialize the backup host system. Initialize the system as a target system,
managed by the primary host. Check that the necessary aspects of the backup
host’s configuration are identical to those of the primary host system.
4. Initialize the target systems. Use INITENV to initialize your other target systems as
needed.
5. Build/Apply the target systems, the backup host system, and any logical targets on
the host system. Update the software configurations on all your systems as
needed.
6. Back up the primary host DSM/SCM environment. After any DSM/SCM operation,
back up all DSM/SCM-related volumes and subvolumes on your primary host. This
ensures that integrity of the current DSM/SCM environment is preserved if the
backup host must become the primary:
a. Create an INPUT file for the BACKUP utility that includes:
$TAPE0, ($SYSTEM.*.*, $volume.REPORT.*, $*.ZPHI*.*,
$volume.ZDSMSCM.*, $volume.XCHINOOK.*, $volume.XPHIHDB.*,
$volume.PATHSCM.*, $volume.SQL.*), not ($SYSTEM.STARTUP.*,
$SYSTEM.ZSYSCONF.*, $SYSTEM.EXPAND.*, $SYSTEM.KMSSWAP.*,
$SYSTEM.LAN4PORT.*, $SYSTEM.ZTMFCONF.*, $SYSTEM.SAFE.*,
$SYSTEM.SAVECONF.*, $SYSTEM.SCFBASE.*, $SYSTEM.ZOSM.*,
$SYSTEM.SCFIN.*, $SYSTEM.SCFTOOLS.*,$SYSTEM.SPOOLER.*,
$SYSTEM.TAPEIOP.*, $SYSTEM.SDISK.*,$SYSTEM.ZSERVICE.*,
$SYSTEM.ZLOG00.*, $SYSTEM.ZLINKMON.*,$SYSTEM.SYS*.* ),
audited, SQLCATALOGS, open, LISTALL
b. Run BACKUP using this INPUT file:
> BACKUP/in input-filename/
7. Move necessary startup files from the primary host to the backup host. Startup files
include those that st
art up processes such as Expand lines, the TCP/IP process,
and so on. You can more easily copy and modify the startup files from the primary
host to the backup host than create startup files for the backup host from scratch.
Because required startup files vary for different system environments, this is only
an example:
a. Create a working subvolume on $SYSTEM to hold the startup files.