Here's the answer to the first half of your question. Disk write operations using CFW (Cache Fast Write) are written into cache but not to the disk. Having CFW operations in progress at the time a HyperSwap occurs can yield unpredictable results since there is no corresponding mirrored cache content in the secondary disk subsystem.
I don't know enough about NVS to comment. Perhaps, others will be so kind as to enlighten us. Terry Traylor charlesSCHWAB TIS Mainframe Storage Management Remedy Queue: tis-hs-mstg (602) 977-5154 WARNING: All email sent to or from this address will be received by the Charles Schwab corporate e-mail system and is subject to archival and review by someone other than the recipient. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Ron Hawkins Sent: Saturday, January 19, 2008 7:14 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: CFW with Syncsort John, I have been told that CFW must be turned off for Hyperswap, but I never understood why. You say that CFW must be written to disk for Hyperswap, but why can all the other writes still be deferred in cache/NVS? Ron > > Hyperswap would be one of those circumstances were you would also want > the > I/O to be written to the disk. In that case you must ensure that CFW is > not > being used. > > John > ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
