Naveed Mustafa wrote:
>
> Hi there,
>
> Some volumes within the copy storage pools are marked with STATUS=Pending.
> The administrator's reference guide suggests that the data from the volume
> has been deleted but the time specified in the REUSEDELAY parameter in the
> DEFINE STGPOOL command has not elapsed.  I have setup the REUSEDELAY
> parameter to 10 years.  Is there a way that I can reassign these Pending
> volumes back to the scratch pool?  Is that a good idea to do?  Would this
> cause problems within the copypool?

The REUSEDELAY is designed to prevent a sequence of events like the
following:

ADSM database is backed up
Reclamation moves contents of tape A to tape B
Tape A is rewritten with new files
ADSM database suffers catastrophic failure
ADSM database is restored from backup mentioned above

After this sequence of events the database will have certain files
recorded as being on tape A even though the files have actually
been overwritten. Avoiding this situation calls for a REUSEDELAY
value which matches the retention period for backups of the ADSM
database (typically from a few days to a couple of weeks). As far
as I know, no useful purpose is served by setting REUSEDELAY to a
value dramatically larger than the retention period for database
backups.