Classification: Confidential I have set up something similar. I called it a "toggle-plex". (2 LPAR base sysplex in one box).
This was set up as a base sysplex with CTC's for GRS (and VTAM/TCPIP) communication. (yes I did use a DVPIP). PARMLIBs/PROCLIBs/Catalogs were shared. (note there is some work here to enable PARMLIB to be shared successfully). I also included LPAR specific Parmlibs/Proclibs for special cases (e.g. the IBM System Automation upgrade from R4.2 to R4.3). I wrote some automation to handle workload switching. I don’t remember all of the details, but I do remember Autonmation for TCPIP, Batch, and most of the major subsystems. You are running on LPARA and at some point need to perform maintenance. The maintenance is installed on LPARB and LPARB is IPLed. The Automation was executed and the workload on LPARA was drained. When all work on LPARA has ended normally, LPARA was shut down. The next occurrence went from LPARB to LPARA,...... In that particular shop, a "maintenance event" normally consumed 12 hours (or more), between draining the system for IPL, The necessary work and IPL/Restart. The "toggle plex" reduced the maintenance event to 1/2 hour with no observable service interruption for the end-user. One additional benefit is that I could bring up LPARB without affecting LPARA for testing. HTH, -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Laurence Chiu Sent: Friday, April 21, 2023 10:23 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Do you need a coupling facility to implement DVIPA? [CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.] Thanks Timothy for confirming that. We are planning to implement a sysplex where we want a critical application to have high availability without a parallel sysplex. The solution being discussed is to install the application on two LPARs but have it active only one at any time due to dataset sharing issues. But since it has to have a fixed IP, the only way we can see how to do that is to use DVIPA and migrate that fixed IP between whichever LPAR is running the applications. Hopefully that can be achieved with some automation. On Thu, Apr 20, 2023 at 5:20 PM Timothy Sipples <sipp...@sg.ibm.com> wrote: > Here's a quote pulled from an older IBM redbook: > > "Note: Dynamic VIPA and Sysplex Distributor capabilities do not rely > on data stored in structures in the Coupling Facility. Therefore, they > can be implemented using XCF communication without a Coupling Facility > (also called Basic Sysplex connectivity)." > > That's on Page 4 of this redbook: > > https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww. > redbooks.ibm.com%2Fredbooks%2Fpdfs%2Fsg247800.pdf&data=05%7C01%7Callan > .staller%40HCL.COM%7C1b5db1566bb5453e065408db42e0fcaa%7C189de737c93a4f > 5a8b686f4ca9941912%7C0%7C0%7C638177306459112528%7CUnknown%7CTWFpbGZsb3 > d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7 > C3000%7C%7C%7C&sdata=QfavHdwZjkex6jmIQkVTrdYoRR7rw%2BdfQCOlW8oUzes%3D& > reserved=0 > > But I also found this more modern reference in the IBM WebSphere > Application Server for z/OS documentation: > > https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww. > ibm.com%2Fdocs%2Fen%2Fwas-zos%2F9.0.5%3Ftopic%3Dsysplex-distributor&da > ta=05%7C01%7Callan.staller%40HCL.COM%7C1b5db1566bb5453e065408db42e0fca > a%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C638177306459112528%7CUn > known%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haW > wiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GkeNsLIJ9tH0eTvlacInAwUxA0ZglMH > MYzKQzEFhnmE%3D&reserved=0 > > Funny how we carried forward the z/OS 1.2 (and prior) caveat. That bit > of text doesn't seem too important for Version 9.0.5 of WAS for z/OS, does it? > :-) > > ————— > Timothy Sipples > Senior Architect > Digital Assets, Industry Solutions, and Cybersecurity IBM > zSystems/LinuxONE, Asia-Pacific 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 > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: ________________________________ The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ________________________________ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
