(Mentioned this in a previous post.) We replaced two CECs recently. Once everything was running, we discovered that the two-member sandbox was running horribly. Unusable really. Turned out to be configuration. We had copied CEC, LPAR, and Load profiles from old to new boxes. But there is no exportable 'profile' to govern shared CF, i.e. no DYNDISP. Hence we were running with the default DYNDISP OFF. We set DYNDISP to THIN INTERRUPT via CF command, and suddenly all was well again. Night and day.
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ed Jaffe Sent: Tuesday, January 29, 2019 11:29 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Internal Coupling Channel on z13 On 1/29/2019 10:07 PM, Brian Westerman wrote: > No, just one single CP, no specialty processors are available. We have two CF LPARs (CF01 and CF02) sharing a single ICF engine. From both CF consoles I see: 2019029 22:56:50 => display dyndisp 2019029 22:56:50 CF0512I Dynamic CF Dispatching is THINinterrupts. Right now things are pretty quiet on the system and from my z13s monitoring dashboard, I am seeing our ICF only 1% utilized with THIN interrupts. When I change to DYNDISP ON instead of DYNDISP THIN, I still see only 1% utilized. Of course, when I switch to DYNDISP OFF utilization jumps to 100%. DYNDISP THIN should be more responsive and less CPU hungry than DYNDISP ON, but I can't really tell the difference with my simple test. Both seem pretty thrifty. -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
