Richard It's an interesting point you raise about CRC checking. I debated this extensively with IBM support in the course of the PMR. The CRC checking on storage pool data only gives you a way of checking for corruption after it has occurred - eg through auditing volumes.
This would have left me no better off as auditing the volumes without CRC data enabled showed the corruption anyway. The CRC checking would only have made a difference if the meta data (ITSM frame data) was intact but the user data (contents of bitfiles) was corrupt. What I wanted was a way of detecting the corruption at the time it occurred. I have received excellent explanations why this is not possible from a TSM point of view if the OS or drive do not report an error. The only alternative is to do a read-after-write, but this is prohibitive from a performance point-of-view. We've had nothing like it since, but I must say it shook my confidence for a long while afterwards. Regards Neil Schofield Yorkshire Water Services Ltd. Let us know when you're moving house on-line at www.yorkshirewater.com YORKSHIRE WATER - WINNER OF THE UTILITY OF THE YEAR AWARD The information in this e-mail is confidential and may also be legally privileged. The contents are intended for recipient only and are subject to the legal notice available at http://www.keldagroup.com/email.htm Yorkshire Water Services Limited Registered Office Western House Halifax Road Bradford BD6 2SZ Registered in England and Wales No 2366682
