LHVERIFY VOC broke (AREV Specific)
At 12 JUN 1998 05:24:49PM Barbara Carson wrote:
A subroutine that has been used forever suddenly disappeared from the VOC. I cataloged the 'missing' subroutine and the program calling it worked okay. I read here the problem could be a corrupted VOC file so I typed in LHVERIFY VOC at the TCL and it broke. I received the error:
'RTP9' Line 1. B10 Variable has not been assigned a value. Zero used.
Line 1 'RTP9' broke because a run time error was encountered.
When I tried to LHVERIFY a data table I got the same error.
HELP!
At 13 JUN 1998 04:08PM Aaron Kaplan wrote:
LHVERFIY shouldn't be cataloged.
The VOC entry should read
VERB1
SYSOBJ (OR VERBS)
V21
At 14 JUN 1998 11:03PM J. Shaefer wrote:
Which AREV version are you using? If you are using 3.1, I believe the command is VERIFYLH. You might also want to try the FIXLH command.
At 15 JUN 1998 09:34AM Barbara Carson wrote:
Thanks J.,
VERIFYLH was the correct command. Unfortunately it didn't highlight any problems in the VOC so I'm still puzzled as to why we're losing cataloged subroutines.
At 15 JUN 1998 10:12AM J. Shaefer wrote:
You've got me quite puzzled. Did you try FIXLH ?
At 15 JUN 1998 10:20AM Barbara Carson wrote:
Yes I did try FIXLH. Everything appears normal at this time though FIXLH didn't point to any errors???? When I find $ASCII_BFSC I will attempt to catalog it and see if the error occurs again.
Thanks again.
At 15 JUN 1998 11:07AM Matt Sorrell wrote:
Barbara,
Are you sure that your volumes are attaching correctly? It could also be a bad spot on your hard drive. I've seen that happen too.
Also, much as I hate to say it, your SYSOBJ could be corrupted. If that's the case, the only option is to restore from backup.
Hope that helps,
Matt Sorrell
P.S. You can run verifylh on sysobj, but DON'T run fixlh on sysobj. I learned that hard way about that.