We're alo under the PLSC gun, and I can "top" Skips words: >"sharing very little besides the couple data sets" All we are sharing are the three volumes with the couple data sets.
Depending on what 'surprised even us' means :-), we were rudely surprised a few times when we got bitten by the very different naming conventions for DAE for instance (which you cannot 'unshare'), by SA/390 talking to each other via XCF despite differently named groups in the parms, and most recently by RRS, or rather the interaction between DB2, RRS and LOGR, and logstream offload for RRS log streams on a connected system which is NOT the one that *should* have done the offload. Unfortunately RRS does not tolerate a 'corrupted' log stream the way operlog does... Did you know for instance that SDSF will connect to operlog no matter if hardcopy was ever set to operlog on that system? I sure didn't, and someone apparently has operlog hardcoded in the SDSF ISPF profile member on the systems that are not supposed to use operlog. Which fairly regularly gets us an offload in the wrong sms constructs, and hence a corrupted operlog log stream. The only good thing from a technical point of view that I can see is that we finally got around to cleaning up the RNLs before we merged the two plexes. And it only took more than a year to get that cleanup rolled out to another sysplex, too! :-) Regards, Barbara Nitz -- Sensationsangebot nur bis 30.11: GMX FreeDSL - Telefonanschluss + DSL für nur 16,37 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a ---------------------------------------------------------------------- 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
