The answer is much more related to your infrastructure than the DB2 DS Member itself. (You can indeed run different DS members on a single LPAR) - we've done it during a DR exercise ) The question is more about do you have shared parmlibs/proclibs/RACF etc. etc. Some other considerations might be the listening ports for DDF (do the DS Members share a port or have unique ports ?) or ZFS file systems ?
Jerry Whitteridge [email protected] Manager Mainframe Systems & HP Non-Stop Albertsons Companies -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Lizette Koehler Sent: Thursday, February 11, 2021 11:40 AM To: [email protected] Subject: EXTERNAL EMAIL: Re: DB2 member to start on different LPAR Unless I am missing something. The point of DB2 Data Sharing is there is a GROUP (Umbrella) that connects multiple DB2 Regions. So if you have 2 or more DB2 Data Sharing regions. One on LPAR1 one on LPAR2 Then if LPAR1 is down, then LPAR2 will take on the DB2 data sharing work. Does that make Sense? Lizette -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Bill Giannelli Sent: Thursday, February 11, 2021 8:46 AM To: [email protected] Subject: Re: DB2 member to start on different LPAR we are being constrained due to operations limitations. We are planning to upgrade our development environment and we need to have the development CICS regions down. Unfortunately operations says they have difficulty going thru all the regions and just stopping development cics. Our CICS regions are connected to only 1 LPAR. So only in order to ease their work they want to just bring down that LPAR with a scheduled IPL. Our primary DB2 member runs on that LPAR. So I wanted to start it on a "non-CICS" LPAR. Bill ---------------------------------------------------------------------- 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 ________________________________ Warning: All e-mail sent to this address will be received by the corporate e-mail system, and is subject to archival and review by someone other than the recipient. This e-mail may contain proprietary information and is intended only for the use of the intended recipient(s). If the reader of this message is not the intended recipient(s), you are notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately. ________________________________ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
