You can also choose very selectively whether particular LPARs participate in particular Sysplex-related services.
For example, let's suppose you have 4 LPARs named (not so creatively) LPARA, LPARB, LPARC, and LPARD. And let's suppose that those 4 LPARs are sharing one common Coupling Facility LPAR (and an associated ICF, let's say). That means they're part of the same (low level) Sysplex. But each LPAR can be running different middleware and operating system services linked together in different ways in the Sysplex. For example: LPARA, LPARC, and LPARD are running DB2 data sharing together, but LPARC does not even have DB2 installed so it doesn't participate. LPARC and LPARD are running MQ and enjoying some MQ shared queues together; LPARA is also running MQ but standalone (not accessing the shared queue); LPARB isn't running MQ at all. LPARA, LPARB, LPARC, and LPARD are all linked together with the System Logger. LPARB and LPARC are configured in an IMSplex, but LPARA and LPARD are not.... ....and so on. You can have many, many varieties of logical clusters by service, with varying numbers of participating LPARs. And that's very common to do. So you have an enormous amount of flexibility. - - - - - Timothy Sipples Resident Enterprise Architect STG Value Creation & Complex Deals Team IBM Growth Markets (Based in Singapore) E-Mail: [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
