Hello Brian, We used to do that too back when we still had CA-1. If I recall correctly we had some special filenames in the exit that were allowed to be written in DR. So my first idea with RMM was the same, but the only thing I think we can do with the RMM exits is to prevent scratchruns from scratching the tapes...
Erik. On Wed, 31 Mar 2010 10:29:08 -0500, Brian Peterson <[email protected]> wrote: >Back when we had a VTS, we also had this same need. I used TMSUX2A and >TMSUX2F to disallow writes to the production tapes in the shared library >during DR tests. DR was only allowed to write to its own special range of >tapes. I'm glad to hear this feature is now available in CA-1 directly >without needing these exits. We don't have VTS anymore, and our new tape >solution has a hardware read-only capability, so we don't need the CA-1 >exits anymore. > >Brian > >On Wed, 31 Mar 2010 05:55:31 -0400, Jousma, David wrote: > >>Erik, >> >>What tape management system are you using? I ask because we had a need >>for this same functionality. We run CA-1, and asked CA for this >>feature, and Russ and his crew were able to deliver that function via a >>DAR request. I'm thinking that the ptf's are now GA. >> >>In short CA1 now provides a way to mark certain tape ranges as READONLY >>for the exact purposes you mention. >> >>_________________________________________________________________ >>Dave Jousma > >---------------------------------------------------------------------- >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
