Re: LVLCHK *NO

["Scott Klement" <infosys@xxxxxxxxxxxx>]

Hmmm... so taking this one step further...

What if it only needed to "re-link" the input/output spec info
if the record format has actually changed?

As it stands, each RPG program knows that a record format has changed.
So why not just re-do the external definition for that file when the
record format level doesn't match?

This way, you'd (at least usually) have the speed of the "static
linked" i/o specs, with the flexibility of the "dynamic" approach.

Of course, this would work better if it doesn't need the source code
or the *MODULE objects to "re-link" the file data, since development
is often done on a seperate system...


Jim Langston <jlangston@conexfreight.com> wrote:
> Okay, so the gist of this is, it would take too much time and
>  processor power
> to dynamically link the files, and you think we want the extra check
>  at run time.
>
> The main advantage to dynamic linking is being able to change the
>  underlying
> database structure without having to recompile the program if no log
>  changes
> have taken place, so it is easier to maintain our databases.
>
+---
| 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
+---