Wed, Sep 18, 2002 at 01:50:05PM -0400, Alan Altmark wrote: (Steve Shultz wrote)
> 2) Your storage should be defined to whatever size you want as the minimum > size of the virtual machine to ipl your shared system. I believe it would > be unwise to define it smaller than 64M. Why is this? I've seen VM tell me I didn't have enough memory for a shared CMS segment as well. This question is really because I'm a VM ignoramus, but why do shared segments require more memory? Is it simply that they're mapped into your machine in largish chunks and therefore you lose some R/W storage with every R/O shared segment you define? > When its done, you'll be in CP READ and you or anyone else will be able to > issue "CP IPL system_name" to start up your shared system. One caveat. > Every virtual machine that ipls your shared system must have the same disk > configuration as the system that was saved. That is, the disks must be at > the same addresses and be the same sizes as the virtual machine that > issued SAVELX2. Hmmm. Is this simply a matter of the savesys including a parmfile within it? In which case, could you get around this by, say, defining a small root volume, and then dynamically bringing DASD online in the boot-scripts? Adam
