Is there a __simple__ way to change the name of a SYSPLEX?
I am reading, but have no real experience. I have a single member sysplex right now. I need to split it into two z/OS images, in a basic sysplex. Due to stupidity on my part, I named the sysplex the same as the sysname. I would now like to change the name of the sysplex to something like PROD1. I don't see a simple way to do this. It appears, to me, that I'm going to need to create new couple datasets with the new sysplex name, IPL my system with then, then reinstall the existing definations (WLM, and LOGR right now) into the new couple datasets. This is going to be a bother due to the screams when I take any kind of "extended" outage (like more than 30 minutes). -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Is there a __simple__ way to change the name of a SYSPLEX?
Never had to do this myself, but: Why not create the "second" image in the "new" sysplex and populate your CDS's in the "new" sysplex". Migrate work to the "second" image in the "new" sysplex and then put the "current" image into the "new" sysplex with an IPL. I would expect this to be a minimal outage (< 30 min) and it *might* even be possible dynamically with SETXCF COUPLE commands. I will defer to others on this list if they have experience that contradicts this assumption (or the fine manual says this can't be done). HTH, I am reading, but have no real experience. I have a single member sysplex right now. I need to split it into two z/OS images, in a basic sysplex. Due to stupidity on my part, I named the sysplex the same as the sysname. I would now like to change the name of the sysplex to something like PROD1. I don't see a simple way to do this. It appears, to me, that I'm going to need to create new couple datasets with the new sysplex name, IPL my system with then, then reinstall the existing definations (WLM, and LOGR right now) into the new couple datasets. This is going to be a bother due to the screams when I take any kind of "extended" outage (like more than 30 minutes). -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Is there a __simple__ way to change the name of a SYSPLEX?
Not, nice but IMHO feasible: leave the names unchanged. Create second system with new name. You will have SYSPROD and SYSPRO2 belongind to sysplex SYSPROD. -- Radoslaw Skorupka Lodz, Poland -- BRE Bank SA ul. Senatorska 18 00-950 Warszawa www.brebank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237 NIP: 526-021-50-88 Wedug stanu na dzie 01.01.2008 r. kapita zakadowy BRE Banku SA wynosi 118.642.672 zote i zosta w caoci wpacony. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Is there a __simple__ way to change the name of a SYSPLEX?
> -Original Message- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Staller, Allan > Sent: Thursday, February 28, 2008 1:06 PM > To: IBM-MAIN@BAMA.UA.EDU > Subject: Re: Is there a __simple__ way to change the name of > a SYSPLEX? > > > Never had to do this myself, but: > > Why not create the "second" image in the "new" sysplex and > populate your > CDS's in the "new" sysplex". > Migrate work to the "second" image in the "new" sysplex and > then put the > "current" image into the "new" sysplex with an IPL. > > I would expect this to be a minimal outage (< 30 min) and it *might* > even be possible dynamically with SETXCF COUPLE commands. I will defer > to others on this list if they have experience that contradicts this > assumption (or the fine manual says this can't be done). > > HTH, Allan, Very good idea! I can IPL my new z/OS image to set up and initialize the couple datasets, then modify the PARMLIB on my current image to point to them and just do an IPL. Should be good to go. I wish that whatever it is that is gumming up my brain would go away. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Is there a __simple__ way to change the name of a SYSPLEX?
On Thu, 28 Feb 2008 12:47:41 -0600, McKown, John <[EMAIL PROTECTED]> wrote: >I am reading, but have no real experience. I have a single member >sysplex right now. I need to split it into two z/OS images, in a basic >sysplex. Due to stupidity on my part, I named the sysplex the same as >the sysname. I would now like to change the name of the sysplex to >something like PROD1. I don't see a simple way to do this. It appears, >to me, that I'm going to need to create new couple datasets with the new >sysplex name, IPL my system with then, then reinstall the existing >definations (WLM, and LOGR right now) into the new couple datasets. This >is going to be a bother due to the screams when I take any kind of >"extended" outage (like more than 30 minutes). > Someone named a sandbox LPAR plex the same as production (prior to my time here). It was causing a problem with some monitoring software so I was asked to rename it a couple of years ago. Simple? I think it was fairly simple. There was no extended outage, just and IPL and re-define of logstreams after I came up under the new sysplex name. Everthing else was staged prior to IPL. Note that none of the old logstreams were needed. Here are the notes for exactly what I did: 1) Defined / formatted new XCF, WLM, and LOGR couple data sets using new data set and sysplex names 2) Extracted / Saved current WLM policy into a PDS prior to IPL 3) Deleted CICS logstreams (DASDONLY) prior to IPL. 4) Stopped RRS and deleted RRS logstreams (DASDONLY) just prior to IPL 5) Saved copy of COUPL00 parmlib member as COUPLE0@, updated COUPL00 with new data set names and sysplex name prior to IPL 6) IPLed to pick up new couple data set names and sysplex name 7) Import WLM policy from saved data set and activated the policy 8) Define RRS logstreams 9) Started RRS 10) Define CICS logstreams HTH, Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Is there a __simple__ way to change the name of a SYSPLEX?
>Here are the notes for exactly what I did: >1) Defined / formatted new XCF, WLM, and LOGR couple data sets using new data set and sysplex names >2) Extracted / Saved current WLM policy into a PDS prior to IPL >3) Deleted CICS logstreams (DASDONLY) prior to IPL. >4) Stopped RRS and deleted RRS logstreams (DASDONLY) just prior to IPL >5) Saved copy of COUPL00 parmlib member as COUPLE0@, updated COUPL00 with new data set names and sysplex name prior to IPL >6) IPLed to pick up new couple data set names and sysplex name >7) Import WLM policy from saved data set and activated the policy >8) Define RRS logstreams >9) Started RRS >10) Define CICS logstreams We just did this on our sandbox system, so to add to Mark's notes: - Remember to update LOADxx if you specify SYSPLEX there - We did not delete any of the existing logstreams - in case we had to IPL back with the old name - We don't "own" the CICS logstreams, the CICS guys here define them, but the neat thing is, you only have to define a couple of "model" logstreams, and CICS does the rest - If you shut down CICS and DB2 (RRS user) cleanly, you should not need any of the data therein. In fact, they ought not be any. - If you have OPERLOG/LOGREC in logstreams, you'll want to extract the last of the data before shutting down your existing monoplex and IPLing into the new sysplex. - XCF/XES issues a series of WTORs for new sysplex initialization, but they are pretty straightforward. Just read and verify before reply. Regards, Art Gutowski Ford Motor Company Dearborn, MI [EMAIL PROTECTED] -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
