I've run into the same issue alot.  It's just a TSM limitation.
TSM is not smart enough to reorder any queue based on tape availability.

IE, if proc 1 is using tape 1,
and proc 2 needs data from tapes 1-5,
TSM won't do 2-5 while waiting for access to 1.
It'll simply go into media wait.

happens all the time, which is generally why admin schedules and such like
to be serialized.

Multiple threads of the same type, well, not much you can do there.

On 06.02.27 at 13:38 mark.stapleton AT USBANK DOT COM wrote:

Date: Mon, 27 Feb 2006 13:38:57 -0600
From: Mark Stapleton <mark.stapleton AT USBANK DOT COM>
Reply-To: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Multiprocess Offsite Reclamation Pointless???

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 02/27/2006
11:55:42 AM:

Has anyone out there tried the new 5.3 multi-threaded reclamation
process for offsite copypools?

In both cases, within a few minutes of processing, all the reclamation
processes for this pool are competing for the same input volume, so one
process continues and the others stall with media wait.

The documentation doesn't say to not use the parameter for offsite copy
pools, so I'm wondering if this is a bug or working as designed.  If
working as designed, then it is pointless for offsite pools.

Well, not exactly. As is mentioned by others, using this for offsite pool
reclamation with collocated primary tape pools will minimize the tape
volume contention (but may increase the number of tape mounts).

But hey! if you run any three tape processes, and they all need data off
the same volume, there's going to be contention no matter how you slice
it.

--
Mark Stapleton (mark.stapleton AT usbank DOT com)
US Bank
MR Backup and Recovery Management
Office 262.790.3190
------------------------------------------------------------------------------
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.
==============================================================================