Hello,
yes, this is working as designed and explained in
apar IC15925. One way to easily circumvent this
is to use a FILE stgpool instead of a DISK stgpool.
That should work just fine.
Regards,
-----------------------------------------------------------------
Rejean Larivee
Rejean Larivee
IBM TSM/ADSM Level 2 Support




                      Bill Boyer
                      <bill.boyer@VERIZ        To:       ADSM-L AT VM.MARIST 
DOT EDU
                      ON.NET>                  cc:
                      Sent by: "ADSM:          Subject:  Re: Slow Reclamation 
from disk
                      Dist Stor
                      Manager"
                      <[email protected]
                      .EDU>


                      06/26/2002 12:55
                      PM
                      Please respond to
                      "ADSM: Dist Stor
                      Manager"





When the primary location of a file is in a primary DISK random access
storage pool, then this is "working as designed." (That's the answer we got
from Tivoli)  In this case the reclamation task processes 1 file at a time
per transaction. When the primary storage pool is a SEQUENTIAL media
(either
tape or FILE) then the files are batched up by the
MOVEBATCHSIZE/MOVESIZETHRESH parameters. Move the files to a SEQENTIAL
primary pool before running reclamation.

Bill Boyer
DSS, INc.