Thanks to everyone. I'm going to recommend to management that we don't go down this path, and use a more reasonable one.
Our new owners are closing our division, which includes shutting down the mainframe environment for most things. One or two applications need to have a mainframe home for a while after everything else is shutdown, hence research on whether it's feasible to begin a system split prior to everything else being shut down. Mark Jacobs Elardus Engelbrecht wrote on 8/30/18 2:35 AM: Mark Jacobs - Listserv wrote: We're in a parallel sysplex, sharing most everything, and need to begin planning activities to remove one system from the sysplex, while continuing to use it to run a subset of our current workload. Why? You lose many benefits of being in a SysPlex, but do you have workload/performance problems? Do you have applications being migrated off mainframe? Alternative. Create a NEW Sysplex and build up your new LPAR inside it. Some of the things we need to consider are; If you want to move a LPAR off the Sysplex, consider isolating and duplicate everything. * PDS/e Sharing * Catalogs (we're ECS shared now) No sharing of catalogs. Just that unless you like taking risks. * Shared DASD You can share DASD and its contents, but just make sure allocation/deletion of datasets are limited/restricted. Say you create a dsn A.B.C in one Sysplex, then you cannot delete it in other Sysplex or LPAR outside the original Sysplex. * RACF Database Sharing (Sysplex Enabled) Do not share RACF DB outside a Sysplex. Turn of sharing completely and only enable that for remaining LPARs inside the Sysplex. You will need a separate ICHRDSNT module for each LPAR. Also, consider separate naming standards for each LPAR inside/outside your Sysplex. * JES2 Checkpoint in CF You have enough volsers for all the duplicate datasets? You need a set of Checkpoint for each unshared JES2 datasets. The same goes for HSM/SMS/SMF/Automation software/Tape Management system/etc. * ZFS File Systems? (This system is not in a shared OMVS Environment) Consider creating the zFS for each LPAR without sharing of course. I'd like people to shoot things at me that I might have missed while I keep on looking myself. Good luck. You will need it. Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu<mailto:lists...@listserv.ua.edu> with the message: INFO IBM-MAIN Please be alert for any emails that may ask you for login information or directs you to login via a link. If you believe this message is a phish or aren't sure whether this message is trustworthy, please send the original message as an attachment to 'phish...@meredith.com<mailto:phish...@meredith.com>'. -- Mark Jacobs Time Customer Service Global Technology Services The standard you walk past is the standard you accept. Lt. Gen. David Morrison This electronic message, including any attachments, may contain proprietary, confidential or privileged information for the sole use of the intended recipient(s). You are hereby notified that any unauthorized disclosure, copying, distribution, or use of this message is prohibited. If you have received this message in error, please immediately notify the sender by reply e-mail and delete it. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
