On Friday, 01/30/2009 at 10:27 EST, "Quay, Jonathan (IHG)" <jonathan.q...@ihg.com> wrote: > Which leads to a couple of questions. First, when did IBM start > supporting RES packs with volsers other than the standard ones as > delivered? I seem to remember warnings about not changing them, but may > have missed when that became ok.
We have always supported RES packs with volsers other than the defaults. We simply do not today provide a way to change it during installation. > Second, if one's intent is to run > nearly identical "cloned" VM images across some number of LPARS on some > number of CECs, would there be a simple way to do this from one Master > read-only RES pack containing various CPLOAD modules and system > configuration files, sort of like our z/OS brethren do? Sharing packs across VM partitions isn't the issue here (it has a different set of concerns). I'm talking about duplicate volsers in the *same* partition. The first warning you see about duplicate volsers is when you install the system! From p.12 of the Automated Installation and Service book: "Attention: Make sure any DASD with the labels 540RES, 540SPL, 540PAG, or 540W0n that you are not using for this installation are not attached to your system. Any such DASD may be brought online when you IPL the initial installation system in ?Step 3. Restore the Initial Installation System (IIS)? on page 40. You can remove these DASD now or use the Device Support Facilities to relabel the DASD. If you choose to relabel the DASD, wait until substep 7 on page 13, in which we explain how to use the Device Support Facilities (ICKDSF) to relabel the DASD." Alan Altmark z/VM Development IBM Endicott
