GFE'S (AREV Specific)
At 07 DEC 1998 03:54:17AM Mike Balchin wrote:
Running AREV 3.12 with NLM on Novell 4.11
Lately have been getting GFE'S.
Restored appropriate file from a back-up calling it XXXA.
Within AREV, renamed original (with the gfe's) to XXXB, then renamed restored version to the correct name.
To check all was OK I ran verifylh on both the newly restored file and the renamed original. BOTH passed with no errors.
OIt would appear that renaming the file with the GFE's clears the problem!!.
Any ideas
Thanks
At 07 DEC 1998 04:11PM Steve Smith wrote:
Flag all AREV files -T to turn transaction tracking off, and see if this helps. Als ensure that every file has a valid owner.
Steve
At 07 DEC 1998 09:58PM Chris Vaughan wrote:
There are hard GFE's and soft ones. Seems yours may have been a soft one.
Just because the workstations copy of a file frame looks like crap does not necessarily mean it is corrupt on the actual magnetic media.
It could have been corrupted during read transmission (network problem), by memory problems on the workstation or any one of a host of other gremlins..
A hard GFE is best verified by inspecting the same frame through some independent means (ie from another workstation).