It doesn't make practical sense to expect a rename to move a dataset from one volume or pool to another. Think of the response time for small datasets and the huge time for that multi-volume database container file that you decide to rename for some insane purpose. Letting the ACS routine change MGMTCLAS allows from the asynchronous dfdss job or some future dfhsm migrate/recall to move the dataset. You could ask for an automatic asynchronous dfhsm action or fdrabr or whoever's product.
Dave Gibney [EMAIL PROTECTED] System Programmer (509) 335-7359 Information Technology Washington State University Pullman, WA 99164-1222 > > > Brian, > > > > A long time ago (10+ years) we tried to get IBM (via GUIDE req) to > > redrive the ACS routines when a rename occurred. It was rejected, > > IIRC not even a comment was given. > > > > We (IIRC) sent it back and asked for a reason. I think IBM never did > > respond . I think after all is said and done IBM won't budge on this > > and I sort of see their point (to a point). IBM just didn't want to > > write an application that would do it . I think IBM's hidden message > > was it was up to the installation to fire off a dfdss job once a day > > to mov e stuff back to the "proper" pool. > > > > ED > > Ed, > > z/OS 1.6 does redrive management class ACS routines on a RENAME. But > none of the others. I know because I just tested it with a WRITE > statement in each ACS routine with the ACSENVIR being output. I then > renamed a dataset and only saw the MGMTCLAS message come out. > > -- > John McKown > Senior Systems Programmer > HealthMarkets > Keeping the Promise of Affordable Coverage > Administrative Services Group > Information Technology > ---------------------------------------------------------------------- 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
