>2. No. What configuration do you have in mind here? You can't have SMS >dasd in 2 SMS's, non-SMS dasd is in no SMS at all. What is being >'shared' then? We now have truly split our sysplexes, but we had issues >with LOGR datasets when our 2 sysplexes shared the same Dasd with 1 SMS >configuration.
Didn't I say not to ask? :-) Yes, I know I am told that I cannot have SMS managed DASD in two SMSs. Check another of my rants (I believe last year in conjunction with a question about sysplex setup), to which Mark replied: "But it works fine for our dump pool (shared across SMSplexes and SYSPLEXes) and LOGR pool (obviously sysplex in scope, but shared across SMSplexes)." So that means in my book that SMS-managed DASD *can* be shared between two SMSs. Not recommended, probably not really supported, but there we go. What I need to have accessible from all systems in the sysplex (share) is a number of volumes that can contain LOGR offload data sets from two subplexes that otherwise know nothing about it each other (in theory). I am also told that it is 'too much work' to make it one SMS config for the full sysplex. And I cannot validate that statement - not my area. Regards, Barbara ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
