>  Due to a total reorganizing of the AIX machine running our ADSM server
>  the data base
>  file(s) (dbvolume,vol_hist and dev_conf) have been moved from one
>  location (disk) to
>  another.
>
>  I've updated the configuration file (dsmserv.opt) to reflect the new
path
>  to the DEVConfig and
>  VOLUMEHistory files but cannot figure how to specify the changed
location
>  of the dbvolume.
>
>  When starting the server it keeps looking for the dbvolume file(s) in
the
>  old location(s), and
>  it appears to me that the path to these files are defined in the
>  VOLUMEHistory files.
>
>  Is there a quick way to tell the server that the path to the dbvolume(s)
>  have changed or do I need
>  to go through a procedure of creating new dbvolume(s), copying stuff
>  over, and deleting old one(s) ?
>
>  I have not done anything else than moving the location of the files.

We only use the dsmserv.dsk file to find ONE data base or recovery log
volume.
The rest of the volumes are located through a structure in the first 1M
that is
added to each of the data base and recovery log volumes.  If for some
reason you can not put the volumes back where they were you can try
making a symbolic link to them from the old name to the new place, but
I would recommend allocating new volumes and then deleting the old
data base and recovery log volumes to move the data to the new volumes.
Make sure the deletes are done inside ADSM so ADSM can move the data
from the old volumes to the new volumes.  See DELETE LOGVOLUME and
DELETE DBVOLUME commands.  I do not recommend running the
server for an extended time with the symbolic links to the data base
and recovery log volumes since I do not know if this can lead to
future problems.

David Bohm
ADSM server development