DSM/Tape Catalog User's Guide

Database Design of DSM/TC
DSM/Tape Catalog User’s Guide — 520233-008
9 - 4
Moving the Volume and File Catalogs to Another
Volume
7. Move the catalog by duplicating the DSM/TC catalog tables (substitute your
subvolume names for those in this example):
DUP $VOL1.DSMCAT.* WHERE SQL AND FILECODE = 900
, MAP NAMES $VOL1.DSMCAT.* TO $VOL2.DSMCAT2.*
, CATALOGS $VOL2.DSMCAT2 FOR $VOL2.DSMCAT2.*
, INDEXES IMPLICIT
, VIEWS IMPLICIT
, SAVEALL;
8. Update the DSM/TC map table.
This requires use of licensed SQLCI2 procedures as documented in the SQL/MP
Installation and Management Guide. The simple procedure is:
a. Use FUP to license SQLCI2:
FUP LICENSE $SYSTEM.SYSTEM.SQLCI2
b. Update the map table that was located in step 1 to reflect the new subvolume
location (substitute your subvolume names):
UPDATE $SYSTEM.SQL.MAP SET GUARDIANLOCATION = &
"\NODE.$VOL2.DSMCAT2"
WHERE GUARDIANLOCATION = "\NODE.$VOL1.DSMCAT”
The strings in quotations marks must be entirely uppercase and fully qualified
with your node name.
9. Resume catalog usage:
a. If you temporarily renamed MEDIADBM in step 5d, restore the renamed
MEDIADBM to its original $SYSTEM.SYSnn.MEDIADBM location.
b. Verify that DSM/TC has the new catalog location:
MEDIACOM INFO VOLCAT|FILECAT *
c. Resume tape activities.
d. If you licensed SQLCI2 in step 8, revoke it:
FUP REVOKE $SYSTEM.SYSTEM.SQLCI2
10. Remove the old catalog:
SQLCI PURGE *.*.* FROM CATALOG $VOL1.DSMCAT;
DROP CATALOG $VOL1.DSMCAT;
You can defer this step for as long as you want for fallback or recovery purposes.
Guidelines

SQLCI operations require the use of licensed SQLCI2 procedures, thus requiring
access to SUPER.SUPER to FUP LICENSE $SYSTEM.SYSTEM.SQLCI2 or to
SUPER.* to honor the DEFINE that instructs SQLCI to use an alternate (already