RE: LVLCHK *NO

>1) Am I correct in my understanding of LVLCHK *NO?

Yes.

>2) If the file definition HAS changed but the program has NOT been
>recompiled, what file definition is the program running against, and what
>results can be expected? 

The program is running against the file definition as it was when it was
compiled. You will get unpredictable results.

>3) What would be the most likely reason a third party vendor would use
>LVLCHK *NO?

The third party vendor has no confidence in the integrity of his package.

Dave Kahn
Johnson & Johnson International (Ethicon) France
Phone : +33 1 55 00 3180
Email :  dkahn1@jnjfr.jnj.com (work)
           dkahn@cix.co.uk      (home)


-----Message d'origine-----
De: Bill Graziano [mailto:Bill.Graziano@besi.com]
Date: 30 September 1999 16:25
À: 'RPG400-L@midrange.com'
Objet: LVLCHK *NO


I use a third party software package where the physical files are compiled
with the record level check field set to *NO (LVLCHK *NO).
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---