I would recommend one additional refinement. After updating the
device class, list filling volumes on the E drive and change those
volumes to read-only. This will prevent TSM from using the filling
volumes as output volumes for 'move data' processes.

You might have to wait for TSM to finish using some of the filling
volumes. Our TSM server (6.2.2.0 under zSeries Linux) will not
let us make a sequential disk volume read-only while the volume is
in use, even if the volume is only being used for input.

Thomas Denier
Thomas Jefferson University Hospital

-----Tim Brown wrote: -----

>Say you have a file based storage pool, with the devclass coded as
>
>D:\DEVT_PRIM,E:\DEVT_PRIM
>
>Over time they accumulate a number of .bfs files in each and then
>due
>to application retirement or other circumstances you don't need all
>the space that this consumes. Is there a way to move the bfs files
>from E:\DEVT_PRIM to D:\DEVT_PRIM
>
>Can you update the DEVC to just D:\DEVT_PRIM and then use MOVE DATA
>to
>move the .bfs files from E:\DEVT_PRIM to D:\DEVT_PRIM