[[https://www.revelation.com/|Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community]]


==== GROUP FORMAT ERRORS (GFE's) (AREV Specific) ====
=== At 17 NOV 1997 09:42:20AM Dina Meyer wrote: ===
 
{{tag>"AREV Specific"}}
 
<QUOTE>
Is there a quick way to find out which files have GFE's without having to analyze all of them one at a time.  We have had occasions when the server has crashed, causing one or more open files to get GFE's.  We have a large user base, so it is impossible to figure what everyone was doing when the server crashed.  This means that we have to analyze every file, which takes a considerable amount of time.




</QUOTE>
----

=== At 17 NOV 1997 02:11PM Victor Engel wrote:  ===

<QUOTE>The quick answer is no. However, there is another answer.



You could do a directory listing on the DOS level to get a list of candidates (files recently modified). Then run LH Verify on these. The manual work involved (unless you design a utility) may exceed the extra processing time consumed by performing LH Verify on the entire volume(s).

</QUOTE>

----

=== At 24 NOV 1997 10:47AM Jeff Warvel wrote:  ===

<QUOTE>We use an approach where we have workstations

report to us when they encounter a GFE. That may

not help you as it sounds like you want to verify

all files immediately after a server crash.



We basically hook the routine that reports a GFE

(i can give specifics if you want). Then we have 

that intermediate routine record and report File,

group, record ID, etc. to a DOS file that can be

checked by the system manager.



Jeff

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=154B5048BB8E27AA852565520050C7BF|View this thread on the  forum...]]