With ADSM DB Backups, it will only write the info as the "FIRST" file
     on the tape.  Having already performed one "backup db" to that tape
     you must first perform a "delete volhist type=dbb tod=blah" to remove
     that vol from adsm's inventory, then you may write a new version of
     dbbackup to the tape.  CATCH-22... if that is your only working
     dbbackup copy I'm not sure adsm will let you free it.

     This is where the bean counters hate us but break down, spend the
     extra money and have as many tapes as versions (incremental or full)
     that you want to keep of the data base.  I tend to keep 7 copies
     (daily full adsm db backups) on each/all of my adsm environments.

     later,
           Dwight


______________________________ Reply Separator _________________________________
Subject: backup db error
Author:  iap (iap AT TAROM.LOGICNET DOT RO) at unix,mime
Date:    2/15/99 5:36 AM


Hello all,

Here is my situation:

labeled a volume dbbk1
put the ibm 3590 in manual mode
configure a devclass for manual operation
issues backup db type=full devclass..... scratch=no volumenames=dbbk1

Everything works fine until I issues another backup db on the same
volume, both types full and/or incremental.

The server tells me that the volume is already in use.... and asks for a
scratch volume or is cancelling the process.

What do I do wrong?

Thank you


Mihai Iancu