It has been my experience that, if  primary tape pool maxscratch value is
set greater than tapes used when reclamation kicks off, it mounts a brand
new scratch tapes.  I suspect that there is some logical reason how tapes
are reclaimed ... such as why not taking already used tape.  However I have
had success  by lowering the maxscratch count less than tapes used will
allow TSM not to use new scratch tapes but use already used tapes.

Now, if one is using collocation, I tried to think of a reason why one
would starting reclamation.  My experience shows that since any gain of
tapes by performing  reclamation of collocation pool is short lived because
TSM will shortly attempt to use new scratch tapes.

Sung Y. Lee


"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 11/28/2005
09:21:45 AM:

> I recently migrated our Windows 2K3 TSM server from 5.2.1.3 to 5.3.2.0
> and since then, it seems that whenever I kick off space reclamation for
> my primary tape storage pools, it eats up scratch tapes, instead of
> freeing them up.  Is there a reason for this?  I understand that
> occasionally TSM will need a scratch tape to combine other tapes, but it
> should then free those other tapes up and return them to the scratch
> pool.  I've checked the reuse delay on the storage pools, and they are
> set to 0, so I know that isn't the problem.
>
>
> Mel Dennis