GFE's on Revelation G (AREV Specific)
At 21 JUL 2000 04:57:52PM Mike Dettle wrote:
Hi Everyone,
I am a PICK consultant that has worked on many flavors of PICK (AP, R83, PRIME, Ultimate, Universe, Unidata . . ). I have done everything from writing applications, converting (Prime, R83, Ultimate) to Unidata/Universe, etc.
Recently I have been asked to help support a company on Revelation G that has lost its two managers (30 some years of experience at this company).
My immediate issues are:
What is the best way to fix GFE's on this older version of Revelation. I have tried the RECOVER.LINK with the (F)ix option for the link files but this does not seem to work. Any ideas anyone? Are there any utilities I could purchase?
How hard is it to convert? I am sure we would have to go from Revelation G to Advanced Revelation and work our way up to OpenInsight.
Any help would be appreciated.
Mike Dettle
At 22 JUL 2000 12:51AM Don Bakke wrote:
Mike,
If you need immediate and direct help or if you want to contact companies which make their living by converting older applications to AREV or OpenInsight then click on the Developer Network button on the left edge of this page and seek out the Consultants listing. Ideally you will want to find a company that is local or can make a visit to your site affordable. Barring that there are many who will work remotely.
The only way we try to fix GFE's in Rev/G tables is to make a new table, copy all the rows from the bad table to the new table, and then rename the new table to the original name. There may be other ways but we got tired of trying to master them. Type HELP CREATE-FILE and HELP RENAME-FILE at the TCL prompt for guidance.
dbakke@srpcs.com
At 22 JUL 2000 02:16PM Warren wrote:
There were several versions of RECOVER.LINK floating around as Dick Weldon tinkered with this quite a bit.
I seem to recall ads for a company that offered GFE fixes in some of the Cosmos publications but I'd have to unearth these from under numerous strata of stuff-I-should-throw-out-but-can't-get-myself-to-do-it-because-you-never-know-when-it-will-be-useful or just too da** lazy.
Could it have been John Gunther's Bucks vs Bytes?
I'm not sure if Dick Weldon is still with Boeing. Perhaps RTI or someone who frequents this board has a later copy?
But as Don Bakke suggests, usually the best way is to try to copy to another file. Good luck, LINK files can easily get trashed beyond all recovery.
GFE=Gone For Ever
At 24 JUL 2000 03:36PM CT Savell wrote:
Mike,
As someone who has to fix GFE's about once a month for one of our RevG clients, I must agree with Don's and Warren's advice and don't screw with the repair utilities to do this but rather just create a new file copy as much of the data as you can into the new file from the old one and say a quite prayer for those poor soles that didn't make it.
The steps are as follows
1) Create a new file in the data volume where all the other data is stored using CREATE-FILE.
2) Attach the data volume so the new file will be recognized using ATTACH.
3) Copy the data records from the old bad file to the new file using
COPY BADFILE * TO:(GOODFILE. Make sure to say 'I'gnore to the prompts that you will get that there is a GFE. This message will occur for every bad spot in the file.
4) You might want to also copy the dictionaries from the BADFILE to the GOODFILE with:
COPY DICT BADFILE * (O) TO:(DICT GOODFILE
5) Now you can either delete the BADFILE with DELETE-FILE or clear the file with CLEAR-FILE (this often works). I suggest deleting the file as this is the safest route.
6) If you deleted the file you can now move a copy of the GOODFILE to the filename BADFILE in the correct volume.
MOVE GOODFILE TO: BADFILE
(If you decided to clear the file you should copy the records from GOODFILE back into BADFILE using the COPY command as shown in 4 above.)
Tom
5)
At 27 JUL 2000 10:21AM Don Miller - C3 Inc. wrote:
As a precaution (and to make things go quicker), you can do the following:
COPY OLDFILE * TO:(NEWFILE (follow CT's ignore errors suggestion)
If the DICT to OLDFILE is OK then leave it alone …
Get the DOS filename for OLDFILE and the DOS filename for NEWFILE
Shell out to DOS
REN DOSFILENAMEFOROLDFILE.LNK DOSFILENAMEFOROLDFILE.LNZ (this will save a copy for you)
REN DOSFIILENAMENEWFILE.LNK DOSFILENAMEFOROLDFILE.LNK. This will give the new file the same entry as the old.
Grab any old LNK filename and copy it to the same name as the NewFile had in DOS. This will prevent attach error later
Get back into REV and delete NEWFILE.
My reason for this is that sometimes MOVE fails and leaves you between a rock and a really hard place ..
Don Miller
C3 Inc.