Changing SYSPLEX name
Jousma, David
A hypothetical question. What are the major implications of changing
the sysplex name? What are the gotcha's?
Assumptions:
- a fairly large parallel sysplex with > 15 participating lpars
- 60+ terabytes of DASD, mostly SMS managed
- SMSPLEX same scope as SYSPLEX
- Sysplex restart needed(all systems down at once)
- Re-allocation of various system datasets with sysplex name as a
qualifier
- New CF policies
As I mention, at this point it is a hypothetical question, so please
don't hammer me with "why would you want to do that?" type questions.
We have some business reasons why this may be needed, but I cannot
discuss that in this forum.
Thanks in advance for feedback.
_________________________________________________________________
Dave Jousma
Assistant Vice President, Mainframe Services
david....@53.com
1830 East Paris, Grand Rapids, MI 49546 MD RSCB1G
p 616.653.8429
f 616.653.8497
This e-mail transmission contains information that is confidential and may be privileged.
It is intended only for the addressee(s) named above. If you receive this e-mail in error,
please do not read, copy or disseminate it in any manner. If you are not the intended
recipient, any disclosure, copying, distribution or use of the contents of this information
is prohibited. Please reply to the message immediately by informing the sender that the
message was misdirected. After replying, please erase it from your computer system. Your
assistance in correcting this error is appreciated.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to list...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Edward Jaffe
> A hypothetical question. What are the major implications of changing
> the sysplex name? What are the gotcha's?
>
We've renamed sysplexes more than once. IIRC, the biggest hassle was
having to rename/recreate all of the data sets with &SYSPLEX in their name.
I assume it's obvious that you'll need a sysplex cold start. Rolling IPL
won't do it...
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
edj...@phoenixsoftware.com
http://www.phoenixsoftware.com/
Barbara Nitz
>the sysplex name? What are the gotcha's?
>- a fairly large parallel sysplex with > 15 participating lpars
>- 60+ terabytes of DASD, mostly SMS managed
>- SMSPLEX same scope as SYSPLEX
>- Sysplex restart needed(all systems down at once)
>- Re-allocation of various system datasets with sysplex name as a
>qualifier
>- New CF policies
The biggest gotcha (in my opinion) is that you have to define all new couple
data sets - the sysplex name is in all of them, not just in the CFRM CDS. You
will do a real cold start on freshly formatted datasets. Come to think of that -
I am not sure how to handle the LOGR CDS if you cannot cold start the log
stream. (We did not have that problem.)
In addition, you don't get a 'test' in the sense that you can do things before
all systems are taken down. Changing &sysplex (and possibly the related
symbols derived from &sysplex) everywhere in the data set names is hard
work. In our case, it wasn't just 'system data sets'. Some of those need the
historical data that were in them, written right until the system was taken
down.
Regards, Barbara Nitz
Vernooij, CP - SPLXM
"Barbara Nitz" <nitz...@GMX.NET> wrote in message
news:<LISTSERV%20091125013...@BAMA.UA.EDU>...
I can recommend a (completely separated) Test-Sysplex for this and other
potentially dangerous changes (SMS config, GDPS, Sysplex CDSs, catalog
modifications/recoverytests etc...). We are very happy to have one.
Kees.
**********************************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain
confidential and privileged material intended for the addressee
only. If you are not the addressee, you are notified that no part
of the e-mail or any attachment may be disclosed, copied or
distributed, and that any other action related to this e-mail or
attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately
by return e-mail, and delete this message.
Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries
and/or its employees shall not be liable for the incorrect or
incomplete transmission of this e-mail or any attachments, nor
responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
Dutch Airlines) is registered in Amstelveen, The Netherlands, with
registered number 33014286
**********************************************************************
Jousma, David
Yes, a sysplex cold-start is assumed.
But, I still have this nagging idea in my head though that SMS
controlled volumes have sysplex name on them somewhere. We do have a
separate plex up at times for early z/OS upgrade testing(not up right
now), and I seem to recall that if I try to write data across sysplex
boundaries, I get SMS error messages that the volume is owned by another
plex, and the write fails. Even though the "old" plex name and the
"new" plex name would not have active systems at the same time, wouldn't
the affect be the same? Wouldn't allocations to SMS disk after the
sysplex rename, and subsequent restart fail?
Does this sound familiar?
_________________________________________________________________
Dave Jousma
Assistant Vice President, Mainframe Services
david....@53.com
1830 East Paris, Grand Rapids, MI 49546 MD RSCB1G
p 616.653.8429
f 616.653.8497
This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated.
----------------------------------------------------------------------
John Kington
Regards,
John
513-723-7527
john.k...@convergys.com
>But, I still have this nagging idea in my head though that SMS
>controlled volumes have sysplex name on them somewhere.
Are you using system (names) or system group(s) in your SMS configuration? Your system group name needs to match the SYSPLEX name.
Regards,
John
513-723-7527
john.k...@convergys.com
Jousma, David
Thanks, for bringing this up. Here is a screenshot from ISMF:
CDS Name . : ACTIVE
CDS Status : VALID
Description : PRODUCTION SYSTEMS BASE CONFIGURATION
==> . . . . :
Default Management Class : Default Device Geometry :
Default Unit . . . . . . : DISK Bytes/track . . . . . : 56664
Tracks/cylinder . . . : 15
DS Separation Profile :
System: TOL2
Sysgrp: CINPLEX CINTPLEX
Yes, we do specify sysgrp. So the production plex is CINPLEX and has
99.9% of the DASD ownership, CINTPLEX is my sometimes up testing
sysplex. CINPLEX would be the name that changes to something else. So
are you saying if I added "newPLEX" to the SYSGRP list, then I
would/should be good? No, volume conversions necessary?
And of course, I would assume that if we are doing any IF/THEN/ELSE
logic in the ACS routines with SYSGRP name, we would also have to
account for that(not sure there is, I'm not the storage team)?
_________________________________________________________________
Dave Jousma
Assistant Vice President, Mainframe Services
david....@53.com
1830 East Paris, Grand Rapids, MI 49546 MD RSCB1G
p 616.653.8429
f 616.653.8497
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-...@bama.ua.edu] On
Behalf Of John Kington
Sent: Wednesday, November 25, 2009 8:33 AM
To: IBM-...@bama.ua.edu
Subject: Re: Changing SYSPLEX name
David
Regards,
John
513-723-7527
john.k...@convergys.com
>But, I still have this nagging idea in my head though that SMS
>controlled volumes have sysplex name on them somewhere.
Are you using system (names) or system group(s) in your SMS
configuration? Your system group name needs to match the SYSPLEX name.
This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated.
----------------------------------------------------------------------
Erik Janssen
I've did this one time, even though it was only a monoplex system. Apart from
the responses I've seen so far:
- I believe you need to recreate / reformat your RMF datasets.
- We did initial start of cics regions (because of redefining logstreams?)
- Perhaps some rexx / clists doing things based on your sysplex name ?
- Check RACF profiles (even though I cannot remember anything in there with
sysplex name)
- Remember to save/reload your WLM policy since you have to redefine the
WLM cds aswell
- switch your logrec to sys1.logrec if you have it to writing to logstream so
that you can first redefine your logrec logstream.
- If you have TWS check for special resources that have sysplex name
- If you use system automation check the policies for use of the sysplex name.
Regards,
Erik.
On Tue, 24 Nov 2009 15:52:39 -0500, Jousma, David
<David....@53.COM> wrote:
>All,
>
>A hypothetical question. What are the major implications of changing
>the sysplex name? What are the gotcha's?
----------------------------------------------------------------------
Mark Zelden
>All,
>
>A hypothetical question. What are the major implications of changing
>the sysplex name? What are the gotcha's?
>
>Assumptions:
>
>- a fairly large parallel sysplex with > 15 participating lpars
>- 60+ terabytes of DASD, mostly SMS managed
>- SMSPLEX same scope as SYSPLEX
>- Sysplex restart needed(all systems down at once)
>- Re-allocation of various system datasets with sysplex name as a
>qualifier
>- New CF policies
>
>As I mention, at this point it is a hypothetical question, so please
>don't hammer me with "why would you want to do that?" type questions.
>We have some business reasons why this may be needed, but I cannot
>discuss that in this forum.
>
Ed and Barbara already commented on some "gotcha's". In a production
environment I would think the biggest issue would be related to logstreams
as Barbara suggested. You can't carry them forward from the old sysplex
to the new sysplex, so you better get any data you need from them
prior to the change and your application better be able to handle a
cold start for its logstream(s). So even if you are just using OPERLOG
and LOGREC and you want that data, dump them prior to the change.
RRS shouldn't be an issue if you come down clean.
Even though this is a hypothetical question, if you are looking for the
actual steps that I did when I renamed a sandbox sysplex, I posted them
on February 28, 2008. It didn't include Ed's step of renaming data sets
with the sysplex name in it because there were none in the sandbox
LPAR because it was a monoplex. I supposed in addition to renaming
data sets that may reference the sysplex name, you also have to make
sure any STC JCL doesn't have the sysplex name hard coded and the
same with parms (hopefully they all use the &SYSPLEX symbol).
Re: Is there a __simple__ way to change the name of a SYSPLEX?
http://bama.ua.edu/cgi-bin/wa?A2=ind0802&L=ibm-main&D=1&O=D&P=233932
Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:mark....@zurichna.com
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html
Mark Zelden
>Thanks Ed, Kees, and Barbara for your responses.
>
>Yes, a sysplex cold-start is assumed.
>
>But, I still have this nagging idea in my head though that SMS
>controlled volumes have sysplex name on them somewhere. We do have a
>separate plex up at times for early z/OS upgrade testing(not up right
>now), and I seem to recall that if I try to write data across sysplex
>boundaries, I get SMS error messages that the volume is owned by another
>plex, and the write fails. Even though the "old" plex name and the
>"new" plex name would not have active systems at the same time, wouldn't
>the affect be the same? Wouldn't allocations to SMS disk after the
>sysplex rename, and subsequent restart fail?
>
>Does this sound familiar?
>
THat just means the volume is not defined to SMS in the plex you are in.
The message you are seeing is probably "home grown" from the ACS
routines.
But you bring up another consideration. If you were to rename your
sysplex, you need to check the SMS base configuration to see if it is
being done by LPAR name (SYSTEM) or SYSPLEX name (SYSGRP) or
a combination. If it is being done by sysplex, you want to add the
new name prior to changing the sysplex name. I've had to go through
this when renaming an LPAR (which is actually worse than renaming
a sysplex).
John Kington
>Yes, we do specify sysgrp. So the production plex is CINPLEX and has
>99.9% of the DASD ownership, CINTPLEX is my sometimes up testing
>sysplex. CINPLEX would be the name that changes to something else. So
>are you saying if I added "newPLEX" to the SYSGRP list, then I
>would/should be good? No, volume conversions necessary?
I am not sure since I never used system group and now work in a different area. My replacement is on vacation so I can't look over his shoulder at the panels but I thought you had to specify the system names in the group. According to the docs, there is a rename option and I think that may be the way to go.
>And of course, I would assume that if we are doing any IF/THEN/ELSE
>logic in the ACS routines with SYSGRP name, we would also have to
>account for that(not sure there is, I'm not the storage team)?
If the old sysplex name and new sysplex name are similar, any test could be modifed to use a pattern. If not, you could always use a filter list.
Regards,
John
513-723-7527
john.k...@convergys.com
Vernooij, CP - SPLXM
"Jousma, David" <David....@53.COM> wrote in message
news:A90766B5039C59409110...@s1flokydce2k322.dm0001.inf
o53.com...
> Thanks Ed, Kees, and Barbara for your responses.
>
> Yes, a sysplex cold-start is assumed.
>
> But, I still have this nagging idea in my head though that SMS
> controlled volumes have sysplex name on them somewhere. We do have a
> separate plex up at times for early z/OS upgrade testing(not up right
> now), and I seem to recall that if I try to write data across sysplex
> boundaries, I get SMS error messages that the volume is owned by
another
> plex, and the write fails. Even though the "old" plex name and the
> "new" plex name would not have active systems at the same time,
wouldn't
> the affect be the same? Wouldn't allocations to SMS disk after the
> sysplex rename, and subsequent restart fail?
>
> Does this sound familiar?
>
>
I don't think so, SMSplex boundaries are not necesserally the same as
Sysplex boundaries. We had 2 Sysplexes share the same Dasd in 1 SMSplex
and never had problems with it. Maybe if the volumes belong to another
SMSplex, one could see your situation, so I would look more to SMS- than
Sysplex-parameters.
Kees.
**********************************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain
confidential and privileged material intended for the addressee
only. If you are not the addressee, you are notified that no part
of the e-mail or any attachment may be disclosed, copied or
distributed, and that any other action related to this e-mail or
attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately
by return e-mail, and delete this message.
Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries
and/or its employees shall not be liable for the incorrect or
incomplete transmission of this e-mail or any attachments, nor
responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
Dutch Airlines) is registered in Amstelveen, The Netherlands, with
registered number 33014286
**********************************************************************
----------------------------------------------------------------------
Steve Comstock
> All,
>
> A hypothetical question. What are the major implications of changing
> the sysplex name? What are the gotcha's?
>
> Assumptions:
>
> - a fairly large parallel sysplex with > 15 participating lpars
> - 60+ terabytes of DASD, mostly SMS managed
> - SMSPLEX same scope as SYSPLEX
> - Sysplex restart needed(all systems down at once)
> - Re-allocation of various system datasets with sysplex name as a
> qualifier
> - New CF policies
>
> As I mention, at this point it is a hypothetical question, so please
> don't hammer me with "why would you want to do that?" type questions.
> We have some business reasons why this may be needed, but I cannot
> discuss that in this forum.
>
> Thanks in advance for feedback.
> _________________________________________________________________
> Dave Jousma
> Assistant Vice President, Mainframe Services
> david....@53.com
> 1830 East Paris, Grand Rapids, MI 49546 MD RSCB1G
> p 616.653.8429
> f 616.653.8497
>
David,
I just received your post this morning (9 February 2010), but it
is dated 24 November 2009. Is this an old issue or is there
something in your email client that set the date wrong?
--
Kind regards,
-Steve Comstock
The Trainer's Friend, Inc.
303-393-8716
http://www.trainersfriend.com
z/OS Application development made easier
* Our classes include
+ How things work
+ Programming examples with realistic applications
+ Starter / skeleton code
+ Complete working programs
+ Useful utilities and subroutines
+ Tips and techniques
Ask me about our new, reduced rates for purchasing our course materials
for use by your own trainers or Subject Matter Experts (SMEs).
Jousma, David
November.
_________________________________________________________________
Dave Jousma
Assistant Vice President, Mainframe Services
david....@53.com
1830 East Paris, Grand Rapids, MI 49546 MD RSCB1G
p 616.653.8429
f 616.653.8497
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-...@bama.ua.edu] On
Behalf Of Steve Comstock
Sent: Tuesday, February 09, 2010 7:17 AM
To: IBM-...@bama.ua.edu
Subject: Re: Changing SYSPLEX name
David,
--
This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated.
----------------------------------------------------------------------
Steve Comstock
> I think it is your email client. I really did send this back in
> November.
Uh oh. Thanks, I'll have to investigate.
--
Kind regards,
-Steve Comstock
The Trainer's Friend, Inc.
303-393-8716
http://www.trainersfriend.com
z/OS Application development made easier
* Our classes include
+ How things work
+ Programming examples with realistic applications
+ Starter / skeleton code
+ Complete working programs
+ Useful utilities and subroutines
+ Tips and techniques
Ask me about our new, reduced rates for purchasing our course materials
for use by your own trainers or Subject Matter Experts (SMEs).
----------------------------------------------------------------------