Scott, Are you still with a company that uses FAST? If so, it does a good job of checking file integrity and doesn't interfere with other users.
COUNT will find gross errors, FILE.STAT is a little better, but these kinds of utilities can miss problems such as a large record with a flink / blink problem several buffers along the chain. HTH, Jeff Fitzgerald Fitzgerald & Long, Inc. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, September 11, 2007 9:20 AM To: u2-Users Subject: [U2] [UV] checking files for corruption Hi all, UV 10.1.8 What is the best way to verify the integrity of a file while users are accessing (if possible at all)? I see that fixtool will set an exclusive file lock when executing without any options. If I understand correctly, the -start and -stop options will scan the file setting group locks. Would it work to set -start to 1 and -stop to the last group in the file? If so, how do I tell what the last group of the file is? Thanks in advance, Scott Thompson ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/