>Was Barbara saying that other mechanisms than HSM were used to migrate >data sets? If so, then we can consider some sort of "rules" parameter.
I was talking about the time when our ISV data sets in APFlist were not SMS-managed. My RACFadmin used to complain a lot about apf datasets being migrated (command migration). This year we have converted to SMS, so this behaviour has stopped (more or less). I just did the same test the others did and got (predictably) the same ARC rc/rsn everyone else had *except* in the case where an APF-auth SMS dataset was only APF-auth'd on one system in the sysplex, not the other. From the other system the command migration went through without a hitch. Given that HC doesn't have XCF communication, but HSM definitely does - I thing in a sysplex HSM should prevent migration by first making sure the dataset in not in APF on *any* system in the sysplex. >Now the second case of not using SMS but a volser works as far as APF is >concerned but DFSMShsm does not recognize it and WILL migrate it. As you indicated, the APF-EXISTS health check recognizes this (had a lengthy discussion with a colleague who used volser on an SMS-managed dataset and was muttering about the HC). In this case, I think that CSV should not allow an SMS-managed dataset into APF when it is specified via volser (given that HC recognizes this as a bad practise!) The question is: *Can* CSV recognize that the data set is SMS managed when it does the IPL progxx-members? Best regards, Barbara -- Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten Browser-Versionen downloaden: http://www.gmx.net/de/go/browser ---------------------------------------------------------------------- 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
