Dead on. At point of failure, files that are closed are perfect, but the files that are open are unusable. How can you tell which is which?
The DASD Redbooks are very clear. There is no free lunch. Mirroring is an excellent solution for a number of potential problems. But not all. HTH and good luck. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Skip Robinson Sent: Thursday, June 16, 2005 11:17 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: DASD and Mirroring ... My own view is that DASD-to-DASD solutions are all prone to data inconsistency in the case of abrupt failure. Unless meticulous care is taken to put all consistency-dependent data within the scope of a single hardware realm, however that's defined by a particular architecture, then sudden and catastrophic loss of connection might well degenerate into the sort of haphazard chaotic recover-by-backup FUBAR that mirroring is supposed to have rendered obsolete in the first place. ---------------------------------------------------------------------- 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
