Parallel Sysplex

SUBSCRIBE DB2-L Muthuraj

Parallel Sysplex
Hi All,

In our shop, We have two MVS Parallel sysplexes each consisting of 2 LPARs
(Total 4 LPARS). We have DB2 Datasharing Group consisting of 4 members in
each MVS sysplex. DB2 Datasharing group name, Member names , Datasets names
for Catalogs, BSDS, Active and Archive logs are same in both sysplexes.
Application object names (viz. DB, Tables, Underlying Datasets ) are
distinct in the two systems.

MVS team is planning to merge two sysplexes into one sysplex. We are stuck
at DB2 !! How do we alter names of DB2 Datasharing group and members to
avoid conflict with the another DB2 Group ?

For DB2, we could think about below methods: have identified two methods of
doing it.

Method 1:

We will keep only one Group DBXG from LPAR1 and 2 (or LPAR3 and 4) and
Migrate DB2 objects from other LPARs. Here there will be a lot of outage and
application DBA's involvement as we have to recreate the objects, unload &
load data and binds. There might be some memory constraints considering
additional workload coming in.

Method 2:

We will keep two datasharing groups DBXG and DBYG. We will have to rename
one of the existing the datasharing group.
Not sure if renaming datasharing group name is possible. Application team
may have to change the datasharing Group name that they have been using in
the jobs.


If anyone has prior experience or any suggestions on these methods, please
let us know. I would like to know the pros/cons of each method.

Regards,
Muthu

______________________________________________________________________

* IDUG 2009 Denver, CO, USA * May 11-15, 2009 * http://IDUG.ORG/lsNA *
______________________________________________________________________



The IDUG DB2-L Listserv is only part of your membership in IDUG. The DB2-L list archives, FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

Leslie

Re: Parallel Sysplex
(in response to SUBSCRIBE DB2-L Muthuraj)
Hi
Merge is as it says Merge .. data from one to the other and your option 1
covers that.

Option 2 - yes you can do it.

You need of course to ensure that the vsam datasets are renamed, iefssn
updated etc to reflect the new member names ... and so on and so forth. But
as for a BSDS point of view you can actually modify the BSDS by way of a
byte by byte update that will change the group name form one group to
another.

I used to do this for system copies, where we copied production to quality
assurance and everything was renamed ... top to bottom.

Of course you must ensure all structures are there as well ... and procs to
support the new db2 names etc etc ... that is all standard stuff.

What you are doing is really just the same as a system copy .. there are
redbooks on this I believe.

Regards

Leslie

-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On Behalf
Of SUBSCRIBE DB2-L Muthuraj
Sent: 11 December 2008 17:02
To: [login to unmask email]
Subject: [DB2-L] Parallel Sysplex

Hi All,

In our shop, We have two MVS Parallel sysplexes each consisting of 2 LPARs
(Total 4 LPARS). We have DB2 Datasharing Group consisting of 4 members in
each MVS sysplex. DB2 Datasharing group name, Member names , Datasets names
for Catalogs, BSDS, Active and Archive logs are same in both sysplexes.
Application object names (viz. DB, Tables, Underlying Datasets ) are
distinct in the two systems.

MVS team is planning to merge two sysplexes into one sysplex. We are stuck
at DB2 !! How do we alter names of DB2 Datasharing group and members to
avoid conflict with the another DB2 Group ?

For DB2, we could think about below methods: have identified two methods of
doing it.

Method 1:

We will keep only one Group DBXG from LPAR1 and 2 (or LPAR3 and 4) and
Migrate DB2 objects from other LPARs. Here there will be a lot of outage and
application DBA's involvement as we have to recreate the objects, unload &
load data and binds. There might be some memory constraints considering
additional workload coming in.

Method 2:

We will keep two datasharing groups DBXG and DBYG. We will have to rename
one of the existing the datasharing group.
Not sure if renaming datasharing group name is possible. Application team
may have to change the datasharing Group name that they have been using in
the jobs.


If anyone has prior experience or any suggestions on these methods, please
let us know. I would like to know the pros/cons of each method.

Regards,
Muthu

______________________________________________________________________

* IDUG 2009 Denver, CO, USA * May 11-15, 2009 * http://IDUG.ORG/lsNA *
______________________________________________________________________



The IDUG DB2-L Listserv is only part of your membership in IDUG. The DB2-L
list archives, FAQ, and delivery preferences are at
http://www.idug.org/lsidug under the Listserv tab. While at the site, you
can also access the IDUG Online Learning Center, Tech Library and Code
Place, see the latest IDUG conference information and much more. If you
have not yet signed up for Basic Membership in IDUG, available at no cost,
click on Member Services at http://www.idug.org/lsms

______________________________________________________________________

* IDUG 2009 Denver, CO, USA * May 11-15, 2009 * http://IDUG.ORG/lsNA *
______________________________________________________________________



The IDUG DB2-L Listserv is only part of your membership in IDUG. The DB2-L list archives, FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

SUBSCRIBE DB2-L Muthuraj

Re: Parallel Sysplex
(in response to Leslie)
Hi Leslie,
I have read some redbook which talks about renaming the member and the std
procedure to be followed. But I have had a question about renaming the
datasharing group name. As far as I know, DSNJU003 doesnt provide any option
to change the datasharing group name in BSDS. then i was thiknking of using
IDCAMS, replace the old datasharing group name with new one, or create a new
subsystem with new datasharing group name,use that BSDS to create the BSDS
for the old datasharing group. in this case, i might loose the logs and
all...after all these, I have some question.datasharing group name used in
started tasks,zparms,HLQ of Catalog and Directory can be changed.BSDS also
can be changed as you mentioned. But are these only components which have
datasharing group name?

Please help and advise any books.

Regards,
Muthu

______________________________________________________________________

* IDUG 2009 Denver, CO, USA * May 11-15, 2009 * http://IDUG.ORG/lsNA *
______________________________________________________________________



The IDUG DB2-L Listserv is only part of your membership in IDUG. The DB2-L list archives, FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms