Martin Packer writes: >And you should avoid - if at all possible - having CF LPARs >sharing ICF processors (unless you really don't care about performance).
I think this prior wisdom has been very recently tempered (at least), specifically with the introduction of Coupling Thin Interrupts (DYNDISP=THIN) in CFLEVEL 19 on zEC12/zBC12 machines. More information is available here: https://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102400 >You can't share a CF LPAR between sysplexes. Importantly, you can have differences in which LPARs participate in which particular CF-supported services within a Sysplex. For example, if you have LPARs A, B, and C in a Sysplex it's quite possible (and common) for A and B to take advantage of DB2 data sharing but not C, and A and C to take advantage of IMSplex but not B (for example). You don't have to configure everything perfectly orthogonally within the Sysplex, and frequently you don't. Said another way, just because a particular z/OS LPAR is a member of a particular Sysplex doesn't mean that LPAR has to use many of the services on offer. The service (or services) that z/OS LPAR use(s) could even be non-substantial, trivial. -------------------------------------------------------------------------------------------------------- Timothy Sipples IT Architect Executive, zEnterprise Industry Solutions, AP/GCG/MEA -------------------------------------------------------------------------------------------------------- E-Mail: [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
