I'd have to disagree with your final assessment. MVS systems don't have spool, checkpoint, paging on the sysres either, and sharing the sysres, or being able to dump/restore it intact, tremendously reduces the amount of effort to roll updated sysres volumes across many systems. Why can't/shouldn't the same savings be possible on VM?
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Wednesday, May 03, 2006 6:23 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. As long as you move ALL CP-owned areas (warm start, ckpt, dir, page, spool) off the SYSRES, it's completely sharable. You shouldn't share page areas, because they're volatile to the individual system, shared spool requires some careful coordination (ie. CSE), and warm start/ckpt/dir are also specific to a system. There's not as much value to sharing a res volume on VM as there is on z/OS. ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
