We are using NT. In your example, issuing the command move data B will
move all data from B, and ADSM should automatically select vol. C.
If you use move data C, adsm will select vol b.
ADSM attempts to fill volumes, so it will select the most full available
volume in the storage pool.
To force the use of a scratch, you can change access to all filling
volumes in the storage pool to access=unavilable (except for the vol.
you are moving from) With no active volume available, ADSM will use a
scratch.


Matthew Warren wrote:
>
> Hello all,
>
>         I have some questions regarding MOVE DATA commands.
>
> Imagine I have 3 tape volumes.
>
> B       60% full.
> C       10% full.
> D       0%  full. (Any scratch)
>
> Is it possible to movedata from B to D then C to D and end up with B & C at 
> 0% and D at 70% thereby emulating space reclamation?
>
> OR
>
> Does ADSM always ask for a new scratch tape when a move data is performed so 
> I will end up with
>
> (Assuming movedata for b is done THEN movedata for C)
>
> B       0%  full
> C       0%  full
> D       60% full
> E       10% full
>
> Basically, Is it possible to do any kind of space reclaim using on or offsite 
> move data cammonds?
>
> I dont think so, but a colleague of mine does. If the argument settles in my 
> favour I'll buy you a virtual pint!
>
> Matthew Warren.
> BT Open Systems Storage Managment.
>
> mwarren AT osmf.bt.co DOT uk