Actually, when reuse comes into play, the tape goes PENDING.   Like this:
FILLING -> FULL -> EMPTY -> PENDING -> deleted (scratch).
I have reuse set to 0 for our "local" pools, and 2 for copy pools.  This
one was in a local pool, so it should have been deleted as soon as it
became EMPTY, but it wasn't.

BTW, I don't think I ever mentioned that we have over 1000 tapes, and
normally have up to 15 tapes a day going back into the scratch pool.  I've
never seen a tape hang in the EMPTY status like this one did.

Robin Sharpe
Berlex Laboratories



                    Farren Minns
                    <fminns@WILEY
                    .CO.UK>       To:    ADSM-L AT VM.MARIST DOT EDU
                                  cc:    (bcc: Robin Sharpe/WA/USR/SHG)
                    09/03/01      Subject:
                    09:26 AM             Re: Cannot delete tape in empty 
status... media state is
                    Please               incorrect - UPDATE
                    respond to
                    "ADSM: Dist
                    Stor Manager"







Erm, I'm not sure if this has been said before, but I thought that a tape
in a state of 'empty' would remain that way until the re-use delay period
had passed after which time it would become a vault-retrieve or scratch
volume. That could be why your tape went from 'empty' to being used without
you seeing it.

I'm pretty new to all this though, so it's just me thinking aloud.

Thanks

Farren