Detecting corrupt or invalid indexes ahead of time

[Mike Schwartz]

     Does anybody have a utility that detects a corrupt or invalid index
before a user encounters it?  If filePro can tell me that I have an
"invalid" index when I rebuild it, then can I programmatically examine all
the indexes on a continuous basis in order to determine exactly when an
index went "invalid"? 
 
     One of my customers is running a large filePro 5.0.5D4 system  on SCO
Openserver  5.0.6.  Lately they have been having an occasional problem with
one or more of the indexes getting corrupted.  
 
     The worst problem is that the programs seem to be operating correctly,
but suddenly a user will detect that the correct data isn't getting
returned.  When they get everybody off the system and try to rebuild the
index, the index shows as "invalid", so they have to delete it and re-enter
the fields and lengths to rebuild it from scratch.
 
     I'm not sure what the (filePro) definition of an invalid index is.  Has
filePro determined that the index is the wrong length?  Is there a bit or
byte in the header of the index that filePro sets to "invalid" if it finds a
corrupt area or something else in an index that it doesn't like?  Or is it
the dxmaint program that does a quick read-through of the index, and then
displays it as "invalid" on the menu rebuilding screen?
 
     If the "invalid" flag is something that gets set in the header, could I
run a Unix script to read the headers of all the indexes on the system to
tell us we have an invalid index?
 
Thanks!
 
Mike Schwartz
   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20081105/bf30eae1/attachment-0001.html