DYNDISP has been around for many years. The primary use/need is the case where two sysplexes share a CF engine. Once upon a long time ago, all CMOS engines were very slow, so it was common to have a lot of them. A sandbox sysplex--which we have long been blessed to own--would not be entitled to very many CF MIPS. It was easy in the early days to give a sandbox exclusive use of one or two slow CF engines.
As time went by, all CMOS engines including CFs got way bigger, faster--and more expensive. To the point, in the mind of many customers, where even a single engine was had to justify for a sysprog plaything. So sharing an engine between, say, Development and sandbox made more sense. But because of the way CFCC code works, engine sharing was discouraged by IBM. Then came DYNDISP, which made sharing less unreasonable. In our configuration, the sandbox is set for dynamic dispatch, which deprecates sandbox performance at the expense of Development but still allows the sandbox to lumber along. Meanwhile, because of its preferred status, Development also gets what it needs. If you have a similar configuration, I recommend DYNDISP or its younger descendant 'thin interrupts', which appears to improve sharers' performance even more. If you do not share CF engines among sysplexes, then you don't need DYNDISP or thin interrupts. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile [email protected] [email protected] > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Nathan Astle > Sent: Wednesday, January 13, 2016 09:49 AM > To: [email protected] > Subject: [Bulk] DYNDISP in XCF > > Hi > > Are there in group who have enabled DYNDISP in coupling facility ? > > What advantages are enabling this feature ? > > Any comments or thoughts ? > > Nathan ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
