RE: Level Check

The files in TESTDATA and PRODDATA were different from the files over which the 
program was compiled a year ago.  The number of fields changed, the size of 
several fields changed.  The file went from 861 long to 1006 long.  The program 
was compiled with LEVELCHK *YES.

sigh ...

¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»§«¤»¥« 
Mary Kern 
Director of Information Services 
University of Toledo Foundation 
2801 W Bancroft St Mail Stop 319
Toledo, OH 43606
Voice: (419) 530-7730 (800) 640-0147 
Fax: 419-530-2895 
Email: Mary.kern4@xxxxxxxxxxx
Progress isn't made by early risers. It's made by lazy men
trying to find easier ways to do something. 
       Robert Heinlein (1907 - 1988), Time Enough For Love
¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»§«¤»¥« 


-----Original Message-----
From: Fisher, Don [mailto:Dfisher@xxxxxxxxxxxxxxxxx] 
Sent: Wednesday, March 17, 2004 3:30 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Level Check


If I understand correctly, you compiled a program over a file in TESTDATA and 
then executed it over a file with the same name in PRODDATA, correct?  

Was there any difference between the files in TESTDATA and PRODDATA other than 
the library?  If not, then this behavior is correct and expected. Level checks 
only occur when a program is executed over a file that contains a material 
difference from the file over which the program was compiled.  A material 
difference is considered to be one of the following:

Different number of fields, 
Fields with different names, and
Fields with identical names but different attributes, such as being character 
instead of numeric.

A different record format name may also be considered in that list, but I'm not 
certain. 

The final criterion for issuing a level check is the file has to be compiled 
with LVLCHK(*YES) or an OVRDBF command has to be issued to that effect. 

Donald R. Fisher, III
Project Manager
Roomstore Furniture Company
(804) 784-7600 extension 2124
DFisher@xxxxxxxxxxxxx

<clip>
He said definitely a program compiled over testdata will not look at the 
proddata file for a level check AND since I was running it over proddata, the 
program would not even check the file over which it was compiled.

But I am here to tell you ... it happened. I did not get a level check and I 
can reproduce it. <clip>