Are you are creating the new dbvols on the same disks or on new disks? If
you are moving them to new disks, what about doing it this way. I have done
this twice when I had to move my database off of a disk that needed to be
replaced because of errors.

        - Allocate new DB, log and mirror files with new naming standard and
new size.
        - dsmfmt the new devices.
        - define the dbvols and mirrors to the adsm server (define dbvol
...)
        - extend the DB by 15Gb (all at once or one disk at a time).
        - move the data off of your old db devices by using the "del dbvol
..." command. This command will move the data to another dbvol before
deleting the volume. Just do this to volumes db1 - db6 and you are then
done. No downtime.

        If you are having to put the new DBvols on the same disks, then the
way you have outlined below looks like it should work.

        Ben

        -----Original Message-----
        From:   Cheri Howard [SMTP:Cheri_Howard AT AAL DOT ORG]
        Sent:   Thursday, October 15, 1998 12:13 PM
        To:     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.