DSM/SCM User's Guide

Troubleshooting
DSM/SCM User’s Guide — 529846-014
13 - 5
Volume Management Troubleshooting
Volume Management Troubleshooting
Alternate System Volume Troubleshooting
When you create multiple logical targets, or when you are running out of space on the
current $SYSTEM, you can create an alternate system volume for new SYSnn
subvolumes. When you create an alternate system volume:

$SYSTEM must be the permanent name, not the alternate name, for the alternate
volume to be loadable.

If you load the system that is currently running on a disk whose primary and
alternate volume names are the same (that is, $SYSTEM) on a disk having
different primary and alternate volume names (that is, $SYSTEM and $ALTNAME
respectively), you cannot see the $SYSTEM ($SYSTEM) disk. Instead, change the
alternate name of the $SYSTEM disk from $SYSTEM to something else. and load
the system on $SYSTEM ($ALTNAME). Then the disk comes up as its alternate
name.

To perform a system load from alternate system volumes (that is, use multiple
logical targets), the ZDSMSCM subvolume must be located on a volume other than
$SYSTEM or any alternate system volume.

After you rename a primary or alternate volume:
1. Verify the database.
2. Receive the snapshot before carrying out any other DSM/SCM activity.

After you rename an archive volume or a scratch volume:
1. Verify the database.
2. Update the volume usage information using the ZPHITMI and ZPHIHMI (See
Updating Target Volume Usage (ZPHITMI and ZPHIHMI) on page 17-12.)

The HELPSRVO file in ZDSMSCM is from the Pathmaker product.
A HELPSRVO file from PATHMAKR is distributed with DSM/SCM into the
ZDSMSCM TSV for Help services in the Pathway Requestor
s. This file has the
VPROC of the level of Pathmaker used to generate the DSM/SCM Requestors,
and must not be used to infer the level of Pathmaker actually installed on your
system.