Re: Coupling Facility and z/OS SysPlex LPARs moving to new hardware
It may also be helpful to refer to the "Best practices for updating a
coupling facility" in the z/OS MVS Setting Up a Sysplex guide in the z/OS
Knowledge Center:
[
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaf100/bestprac.htm
]
Procedure 1 is seems to apply to what you're intending to do, at least for
the CF partitions, and it does include all of the commands you would need.
You will probably need to stitch these into a larger task list though, if
what you're doing is moving some partitions from one CPC to another, and
not replacing (aka push/pull) an entire CPC.
Kieron Hinds
Product Owner, IBM Z Platform Evaluation Test, IBM Systems
https://ibm.biz/zPETBlog
From: Arye Shemer
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 02/12/2021 01:44 PM
Subject:[EXTERNAL] Re: Coupling Facility and z/OS SysPlex LPARs moving
to new hardware
Sent by:IBM Mainframe Discussion List
Thank you for a very helpful reply.
Arye Shemer
On Sun, Feb 7, 2021 at 8:43 PM Mark Jacobs <
0224d287a4b1-dmarc-requ...@listserv.ua.edu> wrote:
> Assuming that your active CFRM policy allows structure movement from the
> old CF LPAR(s) to the new, then yes.
>
> Mark Jacobs
>
> Sent from ProtonMail, Swiss-based encrypted email.
>
> GPG Public Key -
>
https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com
>
> ‐‐‐ Original Message ‐‐‐
>
> On Sunday, February 7th, 2021 at 1:34 PM, Arye Shemer <
> aryeshe...@gmail.com> wrote:
>
> > Installation I work with is going to move Coupling Facilities and z/OS
> >
> > LPARs to new hardware.
> >
> > To best of my recollections after defining the IODFs for the new
systems
> >
> > (z15)
> >
> > which should (could) include definitions for old and new systems.system
> >
> > programmers can rely on system commands to remove CF LPAR and activate
> the
> >
> > new one on the new hardware.
> >
> > At last my question,
> >
> > is this assumption correct (using System Commands to remove old and
> >
> > activate new CF LPARs) ?
> >
> > I do not expect a list of commands, just approval (or not) :-)
> >
> > Thank you,
> >
> > Arye.
> >
> >
>
---
> >
> > 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
>
--
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
Re: Coupling Facility and z/OS SysPlex LPARs moving to new hardware
Thank you for a very helpful reply. Arye Shemer On Sun, Feb 7, 2021 at 8:43 PM Mark Jacobs < 0224d287a4b1-dmarc-requ...@listserv.ua.edu> wrote: > Assuming that your active CFRM policy allows structure movement from the > old CF LPAR(s) to the new, then yes. > > Mark Jacobs > > Sent from ProtonMail, Swiss-based encrypted email. > > GPG Public Key - > https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com > > ‐‐‐ Original Message ‐‐‐ > > On Sunday, February 7th, 2021 at 1:34 PM, Arye Shemer < > aryeshe...@gmail.com> wrote: > > > Installation I work with is going to move Coupling Facilities and z/OS > > > > LPARs to new hardware. > > > > To best of my recollections after defining the IODFs for the new systems > > > > (z15) > > > > which should (could) include definitions for old and new systems.system > > > > programmers can rely on system commands to remove CF LPAR and activate > the > > > > new one on the new hardware. > > > > At last my question, > > > > is this assumption correct (using System Commands to remove old and > > > > activate new CF LPARs) ? > > > > I do not expect a list of commands, just approval (or not) :-) > > > > Thank you, > > > > Arye. > > > > > --- > > > > 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 > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Coupling Facility and z/OS SysPlex LPARs moving to new hardware
W dniu 07.02.2021 o 19:34, Arye Shemer pisze: Installation I work with is going to move Coupling Facilities and z/OS LPARs to new hardware. To best of my recollections after defining the IODFs for the new systems (z15) which should (could) include definitions for old and new systems.system programmers can rely on system commands to remove CF LPAR and activate the new one on the new hardware. At last my question, is this assumption correct (using System Commands to remove old and activate new CF LPARs) ? I do not expect a list of commands, just approval (or not) :-) First: you can replace any CPC in a sysplex with no disruption. It covers both z/OS and CF images. However there are several assumptions to be met. In very general: Put new hardware to the server room and connect channels: z/OS images need access to DASD and other devices. CF and z/OS LPARs need sysplex links. Detailed sysplex link connectivity need to be planned, however in general every z/OS LPAR has to be connected to every CF LPAR. Assumption: one sysplex is considered. Reality is usually more complex. Activate new IODF - it should be modified version of your old IODF with addictions of new hardware and channels. Change logical sysplex definitions (policies, GRS, etc.) - that will introduce new logical CF. Also add new z/OS images to the sysplex. It can be done later. Now you have a sysplex with old and new CFs. Then move (rebuild) structures on new CF. As a result you will have new CFs in use and old CFs as dummy. Then you can logically delete old CFs. And then offline the channels and deactivate CF LPARs. For z/OS - you already have new sysplex members on new hardware. Just shutdown old members. Deactivate old z/OS LPARs. Finally you can power down old hardware. Very short description of quite long and complex project. Of course if you can accept outage, the process would be much easier and shorter. :-) HTH -- Radoslaw Skorupka (looking for new job) Lodz, Poland -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Coupling Facility and z/OS SysPlex LPARs moving to new hardware
You will need to define new cf's along with the existing ones in the cfrm policy and activate it before you move. From: IBM Mainframe Discussion List on behalf of Arye Shemer Sent: Sunday, February 7, 2021 1:34:34 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Coupling Facility and z/OS SysPlex LPARs moving to new hardware **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Installation I work with is going to move Coupling Facilities and z/OS LPARs to new hardware. To best of my recollections after defining the IODFs for the new systems (z15) which should (could) include definitions for old and new systems.system programmers can rely on system commands to remove CF LPAR and activate the new one on the new hardware. At last my question, is this assumption correct (using System Commands to remove old and activate new CF LPARs) ? I do not expect a list of commands, just approval (or not) :-) Thank you, Arye. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Coupling Facility and z/OS SysPlex LPARs moving to new hardware
Assuming that your active CFRM policy allows structure movement from the old CF LPAR(s) to the new, then yes. Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com ‐‐‐ Original Message ‐‐‐ On Sunday, February 7th, 2021 at 1:34 PM, Arye Shemer wrote: > Installation I work with is going to move Coupling Facilities and z/OS > > LPARs to new hardware. > > To best of my recollections after defining the IODFs for the new systems > > (z15) > > which should (could) include definitions for old and new systems.system > > programmers can rely on system commands to remove CF LPAR and activate the > > new one on the new hardware. > > At last my question, > > is this assumption correct (using System Commands to remove old and > > activate new CF LPARs) ? > > I do not expect a list of commands, just approval (or not) :-) > > Thank you, > > Arye. > > --- > > 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
