<damnthetopedos> Are we not smart enough to deal with such things? GRS special processing, hardware reserves, MIM..or for sysprogs.. just being careful?
Should some restraint be exercised? Sure.. but let's not act like we are just another server without ways to do just about anything ( some more advisable than others ) we want!! </damnthetopedos> Rob Schramm On Mon, Jun 4, 2018, 7:05 PM Lizette Koehler <stars...@mindspring.com> wrote: > If you were not aware there is a RACF list that this question might also > be posted to > > To join, if you have not done so > > RACF http://www.listserv.uga.edu/archives/racf-l.html > > > A side comment, I would not allow DASD Sharing between plexes. Within > members of a PLEX, yes. Between Plexes, no > > Especially if there are any PDS/E datasets. Very dangerous. > > Could you not use some sort of transfer process (Connect Direct, FTP, etc) > to move data between the environments? > > > Lizette > > > > -----Original Message----- > > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > Behalf Of > > Todd Burrell > > Sent: Monday, June 04, 2018 3:27 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: RACF protection of a volume > > > > Hopefully this is not a stupid question - but is it possibly via RACF > (maybe > > with DASDVOL) to allow a particular system to have only read access to a > DASD > > volume? We have a need to possibly vary some devices onto a system in > one > > plex while it is being updated on another plex, so we would like to > ensure > > the one system cannot update the volume. > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Rob Schramm ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
