Hi Richard,

I've been investigating a little bit further and found the following solution.
As this problem onyl arises when your library is too small to keep all primary
data for reclamation it is very likely that you can't do a backup stgpool to
multiple tapes.
So if you have always only one copy stgpool tape FILLING then my solution works 
like:

Create a list of copy stgpool tapes with Pct. Reclaimable Space > threshold 
using
a skript (mine is written in REXX) that tells you if a file spans to or from 
this tape.
Looks like:

000039 COPY_STGPOOL_NAME  98.8%  Span_to
000163 COPY_STGPOOL_NAME  98.6%  Span_from
000028 COPY_STGPOOL_NAME  87.6%  Span_to Span_from

Then you create a list of copy stgpool tapes ordered by Date_Last_Written

...
000015                  2005-11-30 18:10:13
000039                  2006-01-03 06:00:44
...
000163                  2006-07-24 09:27:33
000026                  2006-07-26 04:39:55
...
000066                  2006-12-19 12:33:11
000028                  2006-12-20 07:02:50
000152                  2006-12-21 05:52:37

After joining this two lists you need the following tapes for the move data

Tape 000015 and 000039
Tape 000163 and 000026
Tape 000066, 000028 and 000152

If anyone would like to get my REXX Script just drop me a note.

Thomas Rupp

-----Ursprüngliche Nachricht-----
Von: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] Im Auftrag 
von Richard Sims
Gesendet: Samstag, 27. Jänner 2007 15:43
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: Re: [ADSM-L] MOVE DATA for COPY STGPOOL - Which tape is next?


Hello, Thomas -

I explored segment spanning at one time, to see if there was any
ready way of identifying the span-from or span-to volume via standard
commands or Select, and concluded that there wasn't.  The only
recourse is to perform MOVe Data and then see what further volume TSM
requests.

   Richard Sims         http://people.bu.edu/rbs/ADSM.QuickFacts