You don't even have to do that much work.  Just allocate the new volumes,
extend the database to incorporate the new volumes and issue the delete
volume command on the volumes you want to get rid of.  ADSM will move the
data to the available (new) volumes and delete the old ones.  From the
Administrator's Guide:

 "Note: You cannot delete volumes if there is not enough free space
for the server to move existing data from the volume being deleted to other
physical volumes in the database or recovery log.

In our example, you determined that you can delete the four 24MB volumes from
the database. You have reduced the database by 96MB. To delete 301 through
304 from the database, enter:


     delete dbvolume 301
     delete dbvolume 302
     delete dbvolume 303
     delete dbvolume 304


ADSM moves data from the volumes being deleted to available space on other
volumes, as shown in Figure 71. "

I've always thought this was one of the greatest features of ADSM.




ADSM-L AT VM.MARIST DOT EDU on 10/21/99 01:18:45 PM
Please respond to ADSM-L AT VM.MARIST DOT EDU @ INTERNET
To: ADSM-L AT VM.MARIST DOT EDU @ INTERNET
cc:
Subject: Re: Moving the ADSM database and transaction logs

You can mirror each DB volume on to a new disk, then delete the old volume.



At 01:54 PM 10/21/99 -0400, you wrote:
>Hi:
>
>We are adding disk and want to allocate our ADSM database fresh on the new
disks. What do I need to do to move the ADSM database and log files and
retain current data?
>
>Larry Clark
>NYS Thruway Authority
>
Fred Johanson
System Administrator, ADSM
S.E.A.
University of Chicago
773-702-8464