You may only want to set it off for specific volumes. For example, if you are a heavy SFS user, you probably still want it turned on for your pool servers.
Speaking of that, the solution for the problem of dealing with VSWITCHs looks amazingly like VCTCA support. Are we close to being able to do ISFC over a VCTCA on a guest that is coupled to a CP owned VCTCA? Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:ib...@listserv.uark.edu] On Behalf Of James Stracka (DHL US) > Sent: Monday, February 23, 2009 9:26 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: Second level VM systems > > To prevent the MDC problem on 2nd level we issue: SET > MDCACHE SYSTEM OFF > > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:ib...@listserv.uark.edu] On Behalf Of Tom Duerbusch > Sent: Friday, February 20, 2009 4:04 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: Second level VM systems > > For second level VM: > > > 2. LPAR requires dedicated packs. > Second level VM can use dedicated packs and/or minidisks > from the 1st level system. > (the only dedicated disk space you need for a second level VM > system is the CP areas. All CMS minidisks can > be shared in R/O mode and you only need to replicate the > CMS disks that you intend to update. Beware of > MDC when you share CMS disks in R/O mode on the second level > system) >
