Re: [U2] [UV] File corruption error, but ON ERROR branchnot taken
The suggestion made by Ray using uvbackup as a check of files is the philosophy we have adopted after experiencing this type of corruption. We run this every Saturday night over all our files and email the result reporting any likely problems. We are still discussing this one with IBM. They suggested that fixtool in UV 10.0.14 or later will find more errors than uvbackup. When (if?) we find a solution I'll post the results. IBM have suggested that the initial corruption problem which sent us this way is patched in UV 10.0.17 or later (including 10.1), but they believe that not taking the ON ERROR clause when a blink error is encountered may be a bug. Craig --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
Re: Memo: Re: [U2] [UV] File corruption error, but ON ERROR branchnot taken
I haven't really been following this thread, but have you tried the old trick of performing a full backup of the account using uvbackup, redirecting stdout to /dev/null (or .\NUL for those on Windows) and redirecting stderr to a file in which any corrupted files will be reported? The nice thing about this approach is that, while it abandons a file when corruption is detected, it keeps going with the remaining files. --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
