This reminds me that I've always thought that IBM should document a clear warning in the UV manuals about that the:
A) backup B) moving C) copying D) renaming E) deletion Of any UniVerse hashed file - especially dynamic files (type 30) - using any non-UV utilities *can* cause serious problems if improperly used/done, including lost of data and/or data corruption. Backups performed with any utility other than uvbackup need to be done with no users accessing the files being backed-up. Of course, in the real world almost no one uses "uvbackup". :-) Most people find this out the hard way. Of course, having it in the manuals doesn't mean that anyone will read it. ;-) Regards, David -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stephen O'Neal Sent: Thursday, May 17, 2007 10:11 AM To: u2-users@listserver.u2ug.org Subject: [U2] [UV] Every UV Shop needs to read Jeff's note on: Nice SET.INDEX enhancement The COPYing of files and the failure to perform the set SET.INDEX command after the copy, has caused numerous system failures. (One site failed just last week.) Jeff Fitzgerald's excellent e-mail is a must be read by all UV shops. You may wish to consider changing every index you have on your system to RELATIVE.PATH, just to avoid the problem in the future (should you copy a file). I propose that you should CHANGE your STANDARD OPERATING PROCEDURES immediately to increase stability. In addition, all applications development personnel should be educated to implement this for every new index added. ------- 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/
