The biggest problem is that TSM doesn't sort reclaimable tapes prior to
assigning them to threads.  Your best efficiency is to reclaim the most
empty tapes first.

You could use something like this:
UPD STG FOOBAR1 RECLAIM=95 RECLAIMPR=5
Wait a while
UPD STG FOOBAR1 RECLAIM=90 RECLAIMPR=5
Wait a while
UPD STG FOOBAR1 RECLAIM=85 RECLAIMPR=5

Technically, 5.3.0.0 also has a RECLAIM STG command; however, there are
defects in it that can cause hangs and other problems at 5.3 base.

-Josh


On 06.04.07 at 10:47 Ashok.Vats AT FTB.CA DOT GOV wrote:

Date: Fri, 7 Apr 2006 10:47:43 -0700
From: Vats.Ashok <Ashok.Vats AT FTB.CA DOT GOV>
Reply-To: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Reclamation process

We are running TSM 5.3.0.0 ser ver on AIX 5.3.0 with 10 LTO drives in a 3584 
library. We have 10 lto storage pools ( sequential) we always have two  prime 
stg tape pools in the library and we rotate 3 offsite tape pools on weekly 
basis. We are always very low on the Scratch tape we run reclamation using TSM 
admin. schedule. Would like to optimize to take full advantage of 10 drives and 
also if TSMers would like to share any  BKM ( Best known methods) for 
reclamation process implementation. Each pool is roughly 100 tapes.

Thanks
Ashok