|
I use a third party software package where the physical files are compiled with the record level check field set to *NO (LVLCHK *NO). I was raised to believe that this is NOT the preferred setting for this parameter, because it helps keep the programs and files they were compiled against "in sync". In other words, if the file definition changes and the program is not recompiled, a runtime error will result. This will then alert the programmer of the problem. The issue I that I believe exists is to the custom rpg applications that we have written in the past that use these files. We are preparing to do a version upgrade. Some of the file definitions have changed. If I do not recompile the custom programs using the new file descriptions, I believe that I will not get a runtime error. 1) Am I correct in my understanding of LVLCHK *NO? 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? 3) What would be the most likely reason a third party vendor would use LVLCHK *NO? Thanks in advance for your time (and knowledge) Bill Graziano +--- | 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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.