Re: EXTERNAL EMAIL: Re: DB2 member to start on different LPAR

2021-02-11 Thread Chris Hoelscher
A few thoughts

This is NOT purely an academic excersize - if an lpar crashed with a DS member 
on it, and the LPAR COULD NOT be immediately restarted. You would NEED to bring 
up the downed member on the remaining LPAR in light mode - to free any locked 
threads - miake sure all the drda ports are defined an ALL potential LPARS 

Chris Hoelscher
Lead Sys DBA 
IBM Global Technical Services on assignmemt to Humana Inc.
T 502.476.2538  or 502.407.7266

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Jerry Whitteridge
Sent: Thursday, February 11, 2021 2:08 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [IBM-MAIN] EXTERNAL EMAIL: Re: DB2 member to start on different 
LPAR

[External Email: Use caution with links and attachments]


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
jerry.whitteri...@albertsons.com
Manager Mainframe Systems & HP Non-Stop
Albertsons Companies

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Lizette Koehler
Sent: Thursday, February 11, 2021 11:40 AM
To: IBM-MAIN@LISTSERV.UA.EDU
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  On Behalf Of 
Bill Giannelli
Sent: Thursday, February 11, 2021 8:46 AM
To: IBM-MAIN@LISTSERV.UA.EDU
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 
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 

 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 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material.  If you receive this 
material/information in error,
please contact the sender and delete or destroy the material/information.

Humana Inc. and its subsidiaries comply with applicable Federal civil rights 
laws and
do not discriminate on the basis of race, color, national origin, ancestry, 
age, disability, sex,
marital status, gender, sexual orientation, gender identity, or religion. 
Humana Inc. and its subsidiaries do not
exclude people or treat them differently because of race, color, national 
origin, ancestry, age,
disability, sex, marital status, gender, sexual orientation, gender identity, 
or religion.

English: ATTENTION: If you do not speak English, language assistance services, 
free
of charge, are available to you. Call 1‐877‐320‐1235 (TTY: 711).

Español (Spanish): ATENCIÓN: Si habla español, tiene a su disposición servicios
gratuitos de asistencia lingüística. Llame al 1‐877‐320‐1235 (TTY: 711).

繁體中文(Chinese):注意:如果您使用繁體中文,您可以免費獲得語言援助
服務。請致電 1‐877‐320‐

Re: EXTERNAL EMAIL: Re: DB2 member to start on different LPAR

2021-02-11 Thread Jerry Whitteridge
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
jerry.whitteri...@albertsons.com
Manager Mainframe Systems & HP Non-Stop
Albertsons Companies

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Lizette Koehler
Sent: Thursday, February 11, 2021 11:40 AM
To: IBM-MAIN@LISTSERV.UA.EDU
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  On Behalf Of 
Bill Giannelli
Sent: Thursday, February 11, 2021 8:46 AM
To: IBM-MAIN@LISTSERV.UA.EDU
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 
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

 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN