Jeff,

There is a file in /opt/IBMadsm-s/bin called dsmserv.dsk.  Look at that
file.  That will tell you all of the database and recovery log volumes that
ADSM is using.  Then, using your favorite UNIX commands, make sure all of
these files are where they are supposed to be as indicated.  If there not,
then you have found your problem.

If all of the files are where they are supposed to be and are the correct
size, then one of them may be corrupted.  To recover, you will need to do a
dsmserv restore db.  This presumes you have three things: a good database
backup tape, the volhist.out file and the devconfig.out file.  These files
are only created if you specified them in the dsmserv.opt file.  I don't
know why these aren't automatically created like all the other servers
(Hint to engineering) but they are not for this implementation of ADSM
server.

If you don't have a db backup, you can start over by deinstalling ADSM,
deleting everything in /bin/ and starting again.  If you have a backup, but
not the files, then you can still do a restore, but you must create the
devconfig.out file.  This file helps dsmserv define the devclass, library,
drive and slot configuration.  You can dummy this up yourself if you want.
 Not having a volhist file is harder.  I think there is a way to have
dsmserv look at all the tapes in the robot to find one with a db backup on
it.  Slow, but will work.

Kelly J. Lipp
Storage Solutions Specialists, Inc.
www.storsol.com
lipp AT storsol DOT com
(719)531-5926