A "NEXT" storage pool can only be a sequential access storage pool. So you can 
not migrate back to the disk pool once you have migrated to the file device 
class pool.

You could try migrating to the file device class pool with one very large file. 
 Then run a move data on that file with the reconstruct=yes parm which will 
reclaim the aggregates on the move.

I'm not sure if you were on the Technical Exchange this week on TSM Disk Only 
solutions but there are reasons not to use large disk pools alone.  There were 
also some tips on how best to setup storage pools using file device classes.

I will send you a pdf of the Technical Excahnge directly.

Stefan Holzwarth <stefan.holzwarth AT ADAC DOT DE> wrote:
We plan to move TSM from MVS to Windows2003 using only disk storage at 2
CX700 storage systems.

At the moment we discuss whether to use disk and/or file pools.

Since disk is much easier to handle and to use we look for a mechanism to
address the aggregates problem on disk only.

The idea is to have a kind of reclamation pool of type file to handle the
problem:
Large Disk pool --- move vol ----> Small File pool with immediate
reclamation ---> migration by high/lo watermark --> back to large disk pool

The problem now is to have an idea of what disk volumes should be moved. I
do not know any statistic that shows me which volumes should be reorganized.

Any idea?

Kind regards
Stefan Holzwarth


---------------------------------
Do you Yahoo!?
 Yahoo! Mail - now with 250MB free storage. Learn more.