On Tue, 13 May 2008 14:42:12 -0700, Skip Robinson wrote: >As I said in a previous post, we've previously experienced this problem >only in DR testing where the mirroring connection is brutally interrupted >on purpose. In the case of CEC upgrade/replacement, all systems would be >shut down cleanly before hardware work begins. > >How about, just before V XCF,OFF, the SETXCF commands are issued to expunge >the troublesome--mostly DB2--structures in advance? The advantage of doing >it beforehand would be that IPLs on new hardware would then be >straightforward. This matters a lot to automation, which wants to start up >everything in a big rush. We, too, experienced this problem in DR testing. I chose to recreate the problem - and FIX it - during our z9-to-z10 upgrade since we would then have the opportunity to establish a working DR method and document it for all (of us) to see. We are still using our CFRM file from 2005. (Sysplex is relatively new to this site.) My DR view is that that "clean shutdowns" are for whimps. Perfect the error recovery path and skip everything else. Dual path is often inefficient in computer logic and it is also inefficient in human processes. It is simply amazing how that shift in viewponit can open up a lot of possibilities. (For one thing, system shutdown can be blazingly fast. Startup doesn't have to be a daily disaster if you've planned ahead.) Think of how much your automation logic would change for the better if it was ALWAYS working from the viewpoint of recovery. -- Tom Schmidt (That last paragraph should provoke some fun discussion.)
---------------------------------------------------------------------- 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
