The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main as well.
[EMAIL PROTECTED] (David Boyes) writes: > Put bluntly, see my other note on using CMSDDR. Getting a 1 pack VM > system up on the Flex box works MUCH better, CMSDDR understands CMS file > structure so you can just pass images of the volumes over, and as long > as you restore the entire volumes, z/OS won't even know it happened. > > Useful note: when you FTP the CMSDDR output files between the VM system > on the Flex box and the new system, use TYPE E, MODE B before you do the > PUT or GET in the FTP session. This tells the FTP server on the other > end to preserve character set and file parameters, so you won't have to > worry about it. > > Also, keep in mind that your Flex system can create AWSTAPE format > files, and that CMS has a AWSTAPE pipe stage that can feed that to CMS > utilities. If you're worried about licensing for VM on the Flex box, I > think VM/370 (which IBM does not complain about usage) will run CMSDDR. > > I'll have to look into creating a IPLable system image for people in > your situation. Shouldn't be too hard. ... for other topic drift ... in current virtualization genre there is a lot being made of "virtual appliance" ... somewhat akin to what we use to call service virtual machines .... but also gaining a lot of cross-over with a system image that can be quickly and trivially deployed ... usually for very specific purposes. In the security genre, such images can also trivially go *poof* (and any compromises, possibly because of an internet connection, evaporates at the same time). ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
