From: "McKown, John" > > What I am trying to accomplish (if there is another way): At DR we are > only set up to allow PRODUCTION data to be restored. Our programmers > have just put in a request that a small number of TEST datasets be > backed up and restored in a DR scenario. We normally do not have enough > DASD during a test to have TEST volumes available. What I was hoping to > do in the STORGRP ACS routine was detect that we were at DR and assign > the PRODUCTION storage group to a TEST request. But only at DR.
Why bother doing anything ???. We only flash Prod pools for DR tests. Any other allocations fail. If data requested isn't in the prod pools it isn't required. Period. Requesters either get authority to have their data in-place in a prod pool in the "real world", or they go without. This was a significant battle early on, but we found all sorts of references in (real) production that shouldn't have been there, and were a potential exposure. Now everone knows the situation - DR is for *prod* testing. In a real DR event, Prod will be activated, and the other environments restored as and when needed. It did make us change some ACS rules in the real world though - e.g. all ISPF profile datasets are now non-migrate, and in a prod (small) pool. Initially the devs were in the test pools - that got awkward when they were needed at DR tests. Shane ... ---------------------------------------------------------------------- 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
