>We've had multiple discussions on this list about slow copy pool
>reclamations; a common culprit is a cached disk pool, which forces TSM
>to use the copies of files still existing in your disk pool, but only
>*one at a time*, rather than the batched file moves that take place from
>a primary tape pool volumes to copy tape pool volumes.

This was a TSM 4.2 issue, fixed by APAR IC34386, wherein the the MOVEBatchsize
and MOVESizethresh options were not being honored for reclamation of a
cache-enabled disk storage pool.  So this should not be a factor.

  Richard Sims, BU