As long as your L2 system doesn't have the disks attached for your z/OS and Linux guests, they will fail to start, so no issues with corruption. However I would probably use NOAUTOLOG just to be safe.
TCPIP will need to be changed, at least the IP address, before starting it up. Defining GRAF and dialing to the guest is the way to go until you modify TCPIP. Not sure what you mean about defining the DASD volumes in the L1 directory. If you are dedicating the devices, then you don't need to specify the volsers. If you are using minidisks (full or partial) then you have to define them for the 2nd level to find them. On Tue, Oct 5, 2010 at 3:28 PM, George Henke/NYLIC < george_he...@newyorklife.com> wrote: > > L2 is a cloned L1 directory except for the volsers in the Directory and CF > Parm files which have all been made unique, ie 540 becoming 54X. > > I plan to ipl as follows: > > system reset > term conmode 3270 > set mach esa > I 125b clear loadparm 009 > > START COLD DRAIN > > To be safe, I suppose I should also add NOAUTO. > > L1 runs 5 z/OS machines and 3 Linuxes. > > They could be corrupted at L1 if I tried to bring them up in L2 at the same > time without GRS, MIM, or some other serialization product. > > I doubt TCPIP will work at L2 without some reconfiguring. > > So I should define some GRAFs and dial them. > > Not sure if my L2 entry in the L1 Directory needs 54XRES, 54XPAG, 54XSPL, > 54XW01, 54XW02 or whether I can just specify the IPL vplume, 54XRES, and CP > finds the rest from the Parm disk. > > > > -- Mark D Pace Senior Systems Engineer Mainline Information Systems
