Best practice is to not share what you can't protect. MIM, GRS ring, etc., can help, but sharing of PDSE or Unix files can lead to data corruption even with serialization, and sharing between security domains might not only lead to compromisng data but to legal issues, both civil and criminal. If you're a financial or medical facility, involve the legal staff in any decision of sharing data between sysplexes.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Gord Neill [[email protected]] Sent: Thursday, November 24, 2022 3:54 PM To: [email protected] Subject: To share or not to share DASD G'day all, I've been having discussions with a small shop (single mainframe, 3 separate LPARs, no Sysplex) regarding best practices for DASD sharing. Their view is to share all DASD volumes across their 3 LPARs (Prod/Dev/Test) so their developers/sysprogs can get access to current datasets, but in order to do that, they'll need to use GRS Ring or MIM with the associated overhead. I don't know of any other serialization products, and since this is not a Sysplex environment, they can't use GRS Star. I suggested the idea of no GRS, keeping most DASD volumes isolated to each LPAR, with a "shared string" available to all LPARs for copying datasets, but it was not well received. Just curious as to how other shops are handling this. TIA! Gord Neill | Senior I/T Consultant | GlassHouse Systems ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
