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 <[email protected]> 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://www.redbooks.ibm.com/redbooks/pdfs/sg247800.pdf > > But I also found this more modern reference in the IBM WebSphere > Application Server for z/OS documentation: > > https://www.ibm.com/docs/en/was-zos/9.0.5?topic=sysplex-distributor > > 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 > [email protected] > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
