>For SADMP, I would still aim to mirror all DASD and have separate volumes >prepared for SADMP usage on the primary and SADMP usage on the secondary >side. Set up separate procedures for starting it depending on whether you >are running on the primary or on the secondary DASD (you always need to be >aware of where your DASD currently is!). If you hardcode only a primary >device number for SADMP, what do you use when your primary DASD is really >hosed?
We're not big enough that this would be a concern. And we're not a GDPS customer, either. We also don't have enough spare DASD to have them lay around doing nothing - twice. As it was, I had a hard enough time to get one set per sysplex (we have 7, including 3 monoplexes) We have one controller per side where everything is behind, and if that is hosed, we deal with lots of other problems. Given that I always say 'Ich nix hardware' (meaning I have no idea what hardware configs are all about) I am not even sure we would be able to switch to the mirror without the hardware people 'separating' the mirrors first, which means no one can access the DASD, anyway. Which also means that we would have lots of xcf wait stated systems, I think. In such a situation, no one would agree to an sadump, anyway. :-) That no one except me really cares about. :-( Best regards, Barbara -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail ---------------------------------------------------------------------- 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
