The issues listed in the original post plus those suggested by others are potentially *very* serious. I have to ask what benefits are expected that would justify the risk. Surely sysplex overhead alone would not be worth damaging a catalog for example. Whose idea is this?
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Scott Barry Sent: Wednesday, August 29, 2018 1:08 PM To: [email protected] Subject: (External):Re: Un-Sysplex a zOS System On Wed, 29 Aug 2018 13:57:14 -0400, Mark Jacobs - Listserv <[email protected]> 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. > >Some of the things we need to consider are; > > * PDS/e Sharing > * Catalogs (we're ECS shared now) > * Shared DASD > * RACF Database Sharing (Sysplex Enabled) > * JES2 Checkpoint in CF > * ZFS File Systems? (This system is not in a shared OMVS Environment) > >I'd like people to shoot things at me that I might have missed while I keep on >looking myself. > >TIA, > >Mark Jacobs >Time Customer Service Could be a consideration to review/verify - software (contractual language) licensing, also previous-condition with "shared" system dependency, then no longer accessible after un-Sysplex? Scott Barry SBBWorks, Inc. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
