This has not been my experience.  In fact its quite the opposite.
(I am using 3.7.2 but was on 3.1.2.20 as well.)

I can reclamate onsite-tapepools with one drive and a FILE area.
For offsite-Copypools I change the rec to 20 every weekend and it
reads ever onsite tape to recreate about 20-30 offsite-copypools.
It takes 36-48 hours.  and is Tape to Tape.  (3590 carts)
Of course this is also due to the fact I use Collocation on the onsite
tapepool and not use collocation on the offsite copypool.

               joe.f.

It sure would be nice if IBM/Tivoli could rework the code to allow
COPYPOOL reclamation to 'dump' to a disk area until full and then
write it out to a new copypool tape.  (with the assumption that you
used a disk FILE area as large as your largest capacity tape>)





Joseph A Faracchio,  Systems Programmer, UC Berkeley
Private mail on any topic should be directed to :
   joef AT socrates.berkeley DOT edu

On Fri, 4 May 2001, Jon Milliren wrote:

> Hi all,
>
>         I have a copy storage pool with 8 offsite volumes. 3 of these volumes
> have reached over 40% reclaimable space, so I decided to run a reclaim.
> I did this by updating the copy storage pools reclamation threshold to
> 40.
>
>         I expected reclaim to run, but nothing happened at all. The copy
> storage pool tape library is automated, with one drive. I am using TSM
> 3.7.3 for Solaris. Do I need to create a reclaim storage pool, or use
> the MOVE DATA command? Or is this me setting the reclaim threshold
> incorrectly?
>
>         I didn't expect any problems becuase this was a copy pool, and reading
> the admin guide led me to believe that since I was reclaiming offsite
> volumes, lack of multiple mount points wouldn't affect reclaim.
>
> Thanks,
>
> Jon
> --
> Jon Milliren
> Systems Administrator
> University of Pittsburgh
> Office of Institutional Advancement
>
> jon.milliren AT ia.pitt DOT edu
> (412) 624-2727 office
> (412) 292-2070 mobile
>