I do not see any gain from the proposed configuration, however, my thoughts are:
As I interpret the proposed configuration, you would be processing a total of 3 lpars (production, scheduling, and z/VM). I do not see any unsolvable issues of a configuration nature, with sharing between z/OS guest images and non-guest images. I do, however, see potential performance issues (all solvable) within that configuration. What about z/VM maintenance? Think about a z/VM sandbox LPAR. You did not specify what level of z/VM is to be used. If z/VM with Single System Image (?) is installed, z/VM allows live guest migration. i.e. guests can be moved from One VM image to another without interruption. IIRC this is available w/z/VM 6.3 and later. Certain conditions apply. YMMV. HTH, Disclaimer. I am *NOT* a z/VM expert, although I have some familiarity with the capabilities. Your IBM/IBM partner tech rep should be able to correct anything above that is incorrect. <snip> Currently, we are running 6 LPARs - 2 sandbox LPARs , an applicaton/test LPAR, a certification LPAR, a production LPAR and a scheduling LPAR. The sandbox LPARs run under separate monoplexes and separate MASs. The remaining LPARs run under a Base Sysplex and the same MAS. The configuration in question would have the 2 sandbox LPARs, the application/test LPAR and the certification LPAR run as guests under z/VM. The production and scheduling LPARs would still run as separate LPARs but the same MAS. Can the current Base Sysplex and MAS still be used with 2 members running native and the other two runnng as guests under z/VM? Would we need a second MAS? I would also think that there would be extra overhead with PRSM deciding which LPAR gets resources and if it is the z/VM LPAR, then z/VM deciding which guest gets the resources. Seems like a duplication of effort. Then, of course, would JES2 tolerate this as well? </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
