My customer will do such a move early next year. We happen to have a server that can work with DASD: Clone, Label, Format, Move, ... It can schedule dasd moves in worker machines. You can create as many workers as you want. Our server uses DDR and a couple of REXX execs, the server is based on my RxServer package. Our server knows our DASD naming convention, and has some security check as to avoid moving DASD of a VM system that is not shut down. So you'd need to change some small sections in the REXX code to bypass these checks. When a DASD is moved, it also takes care of relabeling the old volume. You obviously need a running VM system to perform the moves. Maybe you could move some crucial DASDs of your system so that you can IPL and have a CMS.
I can send you the code, but we don't have any real documentation. Kris, IBM Belgium, VM customer support
