10+ years ago, I used LVLCHK(*NO) quite often with no ill-effects as long as you add the new fields to the end of the record format.
My understanding is that files listed in F-Specs as an externally describe will create "pseudo" I-Specs at compile time for fields of the file's record format that are actually used. The program will continue to use those specifications until the program is re-compiled. If you made changes to an existing field or place new fields in the middle of the format, you will run into problems. Programs that are not re-compiled will treat the file with its last known pseudo record format "I-Specs".
You can freely use "I-Specs" that do not have all the fields of the record format listed. In fact, externally described files only create pseudo I-Specs for the fields that is actually used by the program. In Debug, you cannot view fields of a record format that are not used in the program because their "I-Spec" were never created.
I do not recommend LVLCHK(*NO), but as long as you understands the risks, you shouldn't have any issues.
Rich
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Dave
Sent: Friday, January 29, 2021 6:11 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: LVLCHK(*NO)
Hi,
I was rather surprised to discover that in my current shop, it is a regular practice to use files in this way, thus avoiding (sometimes) the need to recompile some of the programs sources where they are declared.
I’ve just modified such a file, placing a couple of new fields at the end of the DDS. The program seems to function normally. But what happens exactly when the program reads the file ? Surely, the memory pointing to the new data somewhere is modified. Where is it and how can one be sure there can be no ill effects ?
Thanks !
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
