Re: Re[2]: CHGPF Question

[DAsmussen@xxxxxxx]

Buck,

In a message dated 97-09-19 10:25:14 EDT, you write:

>       Why?  LVLCHK(*NO) is just another attribute of a file, like SIZE or 
>  MAXMBRS...  If I create a file with 10 fields, write a hundred programs,
then
>  add an eleventh field to the end, why should I be forced to re-compile all

>  one hundred programs, when I already KNOW that none of them uses the
>  new field?

Errrrrrrr.  LVLCHK is just another attribute like CRTSQLRPG COMMIT(*CHG) is
just like compiling any other program.  Sure your example is fine if taken
literally -- YOU'RE the only one that HAS to know that the file has changed.
 When someone ELSE writes a brand-new program to update the file (or, more
likely, is writing it at the same time), they DO NOT KNOW that you added that
field.

>  I have never given this question much thought before; seeing these
>  quite strong responses against the practise gives me pause...

Well, you should now.  In large system or multiple-developer environments,
LVLCHK is PARAMOUNT in making sure everyone is "on the same page".

IMHO,

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-Mail:  DAsmussen@AOL.COM

"Everywhere is walking distance if you have the time." -- Steven Wright
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---