>>You are also going to lose the ability to share these as well: In fact, don't try to share anything. Build a large wall between the sysplexes, which can only be crossed by an FTP or similar application.
>Lastly, you don’t mention it, but your comments lead me to believe that you >might be expecting to share the same CF lpars. You need separate CF's for DEV >vs >PROD as well. _ However, you don't need exta ICF's. You can run your DEV CFs shared on the CPs or shared with your Prod CFs on the ICFs. Both configurations have their performance pro's and con's, it depends on your needs. Kees. ________________________________________________________________ Dave Jousma Assistant Vice President, Mainframe Engineering david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jaco Kruger Sent: Tuesday, February 17, 2015 3:58 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Parallel Sysplex split Good morning, Currently, the Production Parallel Sysplex environment consist of all the Development and Production LPARs, which is distributed across 2 mainframes. Each mainframe contains a Production Coupling Facility(CF) LPAR. We will remove the Development LPARs from the Production Sysplex and add it to a new Development Sysplex. The following components are shared between Development and Production environments - DASD - All the z/OS volumes are accessible from all LPARs. Only volumes pertaining to an specific environment is ONLINE, e.g. only Production related volumes are ONLINE in the Production environment. - There is a number of volumes that is shared between the Development and Production environment - ECS - GRS - I/O gen - WLM - ZFS The following components are not shared between Development and Production environments - CATALOG - Each environment has its own Master Catalog - There is some User Catalogs that are being shared between the Development and Production environment - JES2 - DFSMS - DFSMShsm - DFSMSrmm - VSAM/RLS The Control data set are shared The CF lock structure is shared The CF cache structures are unique - RACF - TCP/IP - VTAM We have reviewed the different components, performed the required cleanups and setup documentation with proposed actions. We do however have some questions - What are the gotchas that we need to look out for ? - What will be the best approach to initialize the VSAM/RLS environment in the new Development Sysplex environment ? - Once the Development LPARs have been shut down, do we need to perform any task on the Production Sysplex environment to ensure that the IPL of the Development environment into the Development Sysplex will not cause any problems for the Production Sysplex ? - We found little information regarding the split of a Parallel Sysplex. We used the redbook Merging Systems into a Sysplex as a reference, although it does not contain information regarding the split of a Sysplex. Is there any documentation available that has more information ? Regards Jaco Kruger ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN 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 ******************************************************** 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 ******************************************************** ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
