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

At 16 SEP 1998 03:41:57PM Matt Sorrell wrote:

Occasionally in some of our stores, when we run a verifylh we get an error that TABLE MGA_LINK not available for verify. MGA_LINK is our application name. The message does not provide the name of the actual table that is 'missing', nor does it provide the DOS file name.

We can generally find which table is missing because it has a 0 byte LK file, but this is not always the case.

Is there anyway through code that I can determine which table is missing? Where does VERIFYLH get the list of tables to process and in which order to process them?

Any help would be greatly appreciated.

Matt Sorrell


At 16 SEP 1998 06:52PM Michael Slack wrote:

Sorry, I can't help with your main question. I'm assuming AREV 3.12. But as for were VERIFYLH gets the list of talbe names, if you aren't providing them, then it's getting them form REVMEDIA. That is the way I've always read the VERIFYLH explanation in the Reference manual (page 282).

If you store your results, you can go back and create some TCL reports on the SYSLHVERIFY table (where the VERIFYLH data is stored). Or you can have VERIFYLH redisplay the information by using one of the options.

Michael Slack


At 17 SEP 1998 10:20AM Aaron Kaplan wrote:

It's pulled from the REVMEDIA file. You can attach and validate the file sizes yourself using the real name.

Where are all the 0 byte LK files coming from?

[email protected]

Sprezzatura, Inc.

www.sprezzatura.com_zz.jpg


At 17 SEP 1998 11:31AM Matt Sorrell wrote:

Aaron,

We don't get the 0 byte LK's very often. It's a VERY sporadic problem, generally associated with a major network problem such as a bad net card, bad port on the concentrator, power problems etc.

We're not that concerend about the 0 byte LK's.

I'm just trying to figure out a code solution to determining which table is failing the verify.

Can I access REVMEDIA through code, testing the tables in the order that VERIFYLH does?

Matt


At 17 SEP 1998 01:11PM Aaron Kaplan wrote:

Sure. Easiest way is something like

<code>

Perform "SETALIAS VOLUME SYSPROG REVMEDIA REVMEDIA"
Open "REVMEDIA" to hRevmedia else error
Perform "SELECT REVMEDIA"
Perform "SAVELIST LHSTUFF"
FileNames=XLATE( "SYSLISTS", "LHSTUFF", '', 'X' )
MoreFiles=1
Loop While MoreFile
   Remove FileName from FileNames setting More
   Read MediaRec from hRevmedia, FileName else error
   DosName=MediaRec : ".LK"
   FileInfo=Dir( DosName )
   If FileInfo then
     * Verify with direct call to LH_VERIFY_SUB, command line
     * or add to list and perform at once at end
   End
Repeat

</code>

[email protected]

Sprezzatura, Inc.

www.sprezzatura.com_zz.jpg


At 16 NOV 1998 04:36PM Joe Smith wrote:

  • third_party_content/community/commentary/forums_nonworks/681cd9a1fef05fc785256681006c3611.txt
  • Last modified: 2024/01/04 21:00
  • by 127.0.0.1