-----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Frank Swarbrick Sent: Wednesday, August 05, 2009 12:40 PM To: [email protected] Subject: DASD: to share or not to share
As part of our migration to z/OS from z/VSE we have started a discussion on what DASD, if any, should be shared between our production z/OS LPAR and our development z/OS LPAR. For what it's worth, on VSE here is what we have right now... <SNIPPAGE> Theoretically I can see this possibility, but is it really a concern? What do others do for: 1) System executables 2) System parameter libraries 3) Applications executables 4) Application data I should note that this is not the case of an uneducated manager trying to make technical decisions. But he is from the "distributed systems" world, and even though he's worked here for 15+ years, much of that as CIO over both distributed and mainframe systems, he still has a bit of a "distributed systems" mindset. In that world they don't share "system" or "application" data at all (or very little). But to me that doesn't mean that it's wrong in the mainframe world. Thoughts? <SNIPPAGE> First: Stop thinking VSE and its catalog system. Second: You have a security system (well, I would think you are running one, and probably RACF). Allow the system to put data sets where the system wants/needs based on esoterics and SMS. Let the security system control who can access which data set and if that is read, write, destroy, update, control, twist, fold, spindle or mutilate. Put into LNKLST what needs to be in LNKLST. Define to VLF what needs to be defined there. Now, system executables will be determined by IPL and the PARMS used for that IPL (so if you change o/s levels, and the like...). Application executables and application data should be more or less under the control of the applications people. Production should be under control of production control (or whatever you call that function), and systems stuff should be under the control of the systems programmers. BECAUSE mainframes are not BUS CENTRIC (those open platforms seem to have this characteristic), there should not be problems with executables being shared between systems. After all, once LPA is loaded, you aren't going to read the base libraries until you IPL again. It is in Central Memory or it is on a non-shared PAGE data set. Think of LNKLST elements in roughly the same way thanks to LLA and VLF. Again, stop thinking VSE and tell your CIO to stop thinking 10,000 chickens trying to deliver the mail. Regards, Steve Thompson -- Opinions expressed by this poster do not necessarily reflect those held by the poster's employer. -- ---------------------------------------------------------------------- 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
