I should also respond to this part: Radoslaw Skorupka wrote: >...for availability reasons one should avoid having CF >and z/OS LPAR on the same hardware, which means....
That's not phrased as IBM would phase it, and it's not correct as written. Even when there's some merit in physically separating the CF, the physical separation need only be between that CF and the particular z/OS Parallel Sysplex it serves. Having other z/OS LPARs, even LPARs that are participating in other Parallel Sysplexes, on the same machine as the CF is consistent with IBM's recommendations here. David Raften has published a whitepaper (updated in May, 2018) that explains the various CF configuration options. The direct link to the current edition is here: https://public.dhe.ibm.com/common/ssi/ecm/zs/en/zsw01971usen/zsw01971usen-.pdf If you're reading this post substantially later than July, 2018, then please check first to see whether there's yet another updated edition. David discusses what I just described, the "Logical Stand-Alone CF" configuration, starting on page 9 of that whitepaper. Just because something has merit doesn't automatically mean it has merit for the next available increment of resources (budget, effort, etc.) I always try to approach business risk reduction holistically, in end-to-end business service terms starting with the most critical business services. If adopting a stand-alone CF configuration is the highest, next best use of available resources within that end-to-end service context, great. And isn't it wonderful how much flexibility you have with these technologies, to craft (and re-craft) the most appropriate configurations for the desired business outcomes? -------------------------------------------------------------------------------------------------------- Timothy Sipples IT Architect Executive, Industry Solutions, IBM Z & LinuxONE, Multi-Geography E-Mail: [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
