"Barbara Nitz" <nitz-...@gmx.net> wrote in message news:<listserv%201004070427419325.0...@bama.ua.edu>... > >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 Saying "don't ask", is asking for being asked ;-) 'too much work' can be anyting, one day or one month. And too much for what? Isn't it the basics of a sysplex that 'all' resources are shared, possibly with some exceptions, but not the other way round? I think you have a legal case for wanting shared dasd resources. It is of course possible that the individual SMS configurations have become so complex that it is a huge job to simplify and merge them. Here I am simplifying our SMS configuration, merging all kinds of subpools, that were some kind of legitimate in the past, but not now anymore. Moreover, I have almost realized mirrored SMS configs, so I can change an SMS configuration on our Testsysplex and move it unmodified to our Prodsysplex, like we do with software. It makes life a lot easier. Kees. ******************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ******************************************************** ---------------------------------------------------------------------- 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
