Nacho, EMC made this kinda work by providing a utility that would allow the microcode to change the contents of your volumes - specifically to update the last reference date. This is redundant now as MVS will tolerate the error when last ref date cannot be updated.
I used this facility with SRDF and Shadowimage on Open (distributed) and Mainframe systems. It works in some cases, but these volumes are read only from only one direction. Databases and reporting programs really don't like it when the contents of a file start to change under their feet. It's a bit like defining volumes as non-shared, and then sharing them. Ron > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Yera Fachal, Ignacio > Sent: Thursday, 23 February 2006 7:37 PM > To: IBM-MAIN@BAMA.UA.EDU > Subject: Re: Mount DASD as read-only > > We have read only dasd volumes. > > We have a EMC's Symmetrix DASD cabinet with SRDF's remote copy. What we > have > online as read only is the destination volume of the remote copy witch is > read-only for MVS. So, if we dont want to allow a partition to be able to > write to a specific volume, we vary online the "destination" device. > > > Best regards. > > Nacho Yera Fachal > > > ---------------------------------------------------------------------- > 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 ---------------------------------------------------------------------- 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
