Bill, Why are you wanting to do that?
A DB2 Data sharing environment has a DB2 Start on each lpar that shares the Same DB2 information. If you have 4 LPARs, you would have one DB2 Data Sharing region on the LPARs you want. For example: I have a group name of DBP2, but I have 3 DB2 regions (DBP1, DBP2, DBP3) running on LPARs on LPAR1, LPAR2, LPAR3 I so long as the user is coming into one of those DB2 systems, it has access to the DBP2 group functions. So user A can be running on LPAR1 in DBP1 User B can be running on LPAR3 on DPB3 Batch DB2 job could be running on LPAR2 on DPB3 All of these activities would be for the GROUP DBP2. I am not sure why you want to change the DB2 members for the various LPARs. If DB2 Data Sharing is set up, you should only need to shut down or start up the appropriate DB2 region. Can you provide more details on what problem you are trying to solve? Lizette -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Bill Giannelli Sent: Thursday, February 11, 2021 3:18 AM To: [email protected] Subject: DB2 member to start on different LPAR We have DB2 data sharing and I have a need to start DB2 members on any LPAR. Aside from RACF definitions, is the only other item I need in place is the SSID symbol in SYS1.PARMLIB(IEFSSNxx) ? thanks 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
