I’m not sure what the problem is with removing active CPs. At the start of a CBU window, extra CPs are made available in the hardware. If a system is newly IPLed at that point, it will see all available CPs defined in the Image profile. If a system is already running when CBU is activated, additional CPs must be configured online by MVS command.
At the end of a CBU window, an LPAR may be deactivated if desired, or the extra CPs may simply be configured offline by MVS command, at which point the OS will no longer 'see' the removal of CBU CPs. This is fully dynamic. There is (only?) one clue in the OS that CBU has been started or stopped. WLM issues a message about a capacity change upon either adding or removing CP(s). That message should be highlighted in everyone's automation and broadcast in some way because it can also occur in the case of a hardware problem. We once had an internal cooling problem that caused CPU degradation in the box. We got the same WLM message. Likewise storage may be configured on or offline dynamically if and only if it has been defined at IPL as RECONFIGURABLE. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jon Butler Sent: Thursday, May 12, 2016 7:34 AM To: [email protected] Subject: (External):Re: Dynamic CPU ADD to a z/OS lpar You can add CPs or memory to an active LPAR, but you can't take either away without stopping the LPAR. You don't want more CPs assigned than you (or PR/SM) can use...it's just overhead. In fact, unused CPs will be "parked" on newer CECs when underutilized ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
