Vern...

Database volumes are tracked in the volume history file.  ADSM v2
will ensure that database backup volumes (as recorded in the volume
history file) are not loaded as scratch volumes.  You can free
up db volumes for scratch by deleting old volume history file
records using the DELETE VOLHISTORY command.  Until now, adsm
has not provided a way to do more than this (eg, expire and rotate
adsm database backup volumes)....but this week we are introducing
the Disaster Recovery Manager feature of adsm (DRM....affectionately
called the DisasteR Master)....DRM, among other things, will
allow you to place expiration dates for adsm database backup
volumes..and will track those volumes, as well as copy storage
pool backup volumes.

thanks...greg tevis


>I have ADSM V2R1 installed, and I just set up an Administrative Command
>Schedule that does a "backup db type=full".  The backup has now used all
>the scratch tapes, as intended, but I fail to see any way to expire the
>tapes so that I can use them over.  A logical way would have been to have
>an expiration period on the backup command, but there is none.  How does
>one go about keeping track of which scratch tape is used for what?  And
>then, how do I tell ADSM that a particular backup tape is no longer needed
>so that it may be used again?