DSM/SCM Quick Reference Guide

Managing DSM/SCM
DSM/SCM Quick Reference Guide—529847-005
6-2
Renaming a DSM/SCM Managed Volume
4. Edit the PATHCOOL file to point to the $ newvol .PATHSCM and the
\ system .$ newvol .ZDSMSCM.PATHMAIN.
5. Replace all occurrences of $ oldvol .ZDSMSCM with $ newvol .ZDSMSCM in the
PATHTARG or PATHHOST file.
6. Run PATHCOLD from $ newvol .ZDSMSCM to create $ newvol .PATHSCM.*.
7. Run STARTSCM from $ newvol .ZDSMSCM.
8. Give ownership of the CBEXE program to the super ID (255,255).
9. Set the PROGID of the CBEXE program to the super ID (255,255).
10. Give ownership of the TAEXE program to the super ID (255,255).
11. Set the PROGID of the TAEXE program to the super ID (255,255).
Renaming a DSM/SCM Managed Volume
1. Rename $ OLDVOL to $ NEWNAME.
2. Run Verify Database. (See Verifying a Target System Database on page 6-3.)
3. Create an independent snapshot and transfer it to the host. (See Creating a
Snapshot of a Target System on page 6-4.)
Moving a DSM/SCM Database
1. Stop all servers through PATHCOM and all processes running from PHIHDBMG
(PHITDBMG for a target database).
2. On the Maintenance Interface main menu, enter 6 (Database Relocation) in the
Selection Number field; then press F1.
DSM/SCM displays the Database Relocation screen.
3. Enter the name of the volume where the database currently resides.
4. Enter the name of the new volume for the database; then press F1.
The move can take a while. The Maintenance Interface waits for the compile to
finish. No other DSM/SCM activities can be performed while the compile is in
progress.
5. Run STOPSCM.
6. Run STARTSCM.
Note. If $DATA00 is a scratch volume, Verify Database stops in a restartable state. If
$DATA00 is an archive volume, after successful completion of Verify Database,
update the volume usage information using the Target and Host Maintenance
Interface. For details, see the
DSM/SCM User’s Guide .