Yes, I thought of Thin Interrupts, but considered them a bit new for a first-pass answer of the question.
I'd be interested in knowing any early customer experiences with Thin Interrupts, especially if response time numbers are being measured. (And yes I read the IBM Thin Interrupts paper many months ago now.) One other thing "container size" might come into play here: You CAN'T have a CF in more than one Sysplex. You CAN have a CF with structures from more than one e.g. DB2 Data Sharing Group. Very frequently done. And I agree with Tim's comments on orthogonality: Again, frequently observed. Cheers, Martin Martin Packer, zChampion, Principal Systems Investigator, Worldwide Banking Center of Excellence, IBM +44-7802-245-584 email: martin_pac...@uk.ibm.com Twitter / Facebook IDs: MartinPacker Blog: https://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker From: Timothy Sipples <sipp...@sg.ibm.com> To: IBM-MAIN@LISTSERV.UA.EDU Date: 01/09/2014 03:17 Subject: Re: Question regarding sharing of CF Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> 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: sipp...@sg.ibm.com ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
