The checkpoint and warmstart data has to be on the RES volume, but you specify where those items are to be placed, so it's a simple matter to have the two system's data in different places. The CP Directory can be placed off the RES volume, so it, the spool and the paging can be unique between the two systems. There are several userids to deal with (OPERATOR, OPERATNS, DISKACNT, EREP, TCPIP, ...) but these can all be identified in the SYSTEM CONFIG and point to separate userids. Things like AUTOLOG1 can be made read-only.
I haven't thought of any other large "got'chas" yet, but we'll know soon enough; The intent is to bring up the second LPAR soon, probably after the 14th of May. At that point, anything that bites will draw blood. -- Robert P. Nix Mayo Foundation RO-OC-1-13 200 First Street SW 507-284-0844 Rochester, MN 55905 ----- "In theory, theory and practice are the same, but in practice, theory and practice are different." -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Feller, Paul Sent: Wednesday, May 03, 2006 4:49 PM To: [email protected] Subject: Re: Creating a second zVM 5.1: Spool issue What type of problems would you run into sharing the same SYSRES. I thought there was some "stuff" that was updated on the SYSRES that reflected the state of VM. Ex: Was VM shutdown cleanly. I run two VM lpars, each has its own SYSRES, PAGE and SPOOL. Paul Feller AIT Mainframe Technical Support [EMAIL PROTECTED] (319)-398-7824 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
