Cheri,

  Perhaps you want to look into this. Simply allocate and format your new
DB volumes and
log files and define them. Then issue the delete dbvolume command. This
will move the data
off of the volume that you are deleting onto other available volumes in the
data base. You
can use the del logvolume command in the same way. I have used this method
under both
V2 and V3 ADSM on MVS and OS/390. We do not use mirroring here so I am not
sure what
impact this process would have on that. The delete commands can be found in
the ADSM
Admin. Guide. This process avoids server down time and because it runs as a
process
provides you with the ability top cancel and restart the delete as needed.
Feel free to
contact me via e-mail at Brian_Nick AT PHL DOT com or you can call me at
(860)403-2281.

 Hope this helps.

Brian Nick
Advisory Systems Analyst Storage Solutions
Phoenix Home Life Mutual Ins. Co.
100 Bright Meadow Blvd.
Enfield CT. 06082





Cheri Howard <Cheri_Howard AT AAL DOT ORG> on 10/15/98 02:13:14 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Subject:  Moving and reconfiguring the ADSM DB




We have an MVS V2 server.  We would like to move our ADSM DB and logs to
different  DASD volumes.   At the same time, we'd like to reconfigure our
DB files from 6-2301 MB files to 15-1001 MB files.  We're also going to
rename them from DB1-DB6 to DB10-DB24.  Below are the steps I'm planning on
taking.  However, I'm not 100% comfortable that I'm doing this correctly.
I'd appreciate any input - Thanks!

   Allocate new DB, log and mirror files with new naming standard and new
   size.
   Do a full backup of the ADSM DB.  Also do 'q db f=d' and 'q log f=d'
   Shut down ADSM.
   Run DSMSERV INSTALL to initialize new DB10-12 and the logs to ADSM. (Can
   only do DB10-13 due to jcl exec parm keyword length limitation of 100
   bytes).  It's my understanding you do not have to run DSMFMT on these
   new files....DSMSERV INSTALL will format and extend the DB for you?
   Run DSMFMT on the DB 10-12 mirror files.
   Run DSMFMT on DB13-24 and mirrors 13-24.
   Start ADSM server.
   Define DB volumes 13-24 to ADSM.
   Issue q db f=d to determine maximum extension size available.  Then
   extend DB by that amount.
   Shut down ADSM.
   Run DSMSERV RESTORE TODATE=TODAY to restore the DB from the most recent
   backup.  Will the DB restore OK to the newly named, newly sized files?
   Or will it have a problem because the backup contains the old named, old
   sized files?
   Start the ADSM server.
   Issue 'DEFINE DBCOPY ...........' commands to define the mirrors to
   ADSM.