RE: Externalizing input and output.

James,

If all your programs access the data through the logicals explicitly listing
the fields then you can change the physical and programs using the logicals
will still work even with LVLCHK(*YES).  This method (all data access
through logicals with explicitly named fields) is a good method to make it
much easier to change database files.  You just create a new version of the
logicals and only change the programs that need to access the new field(s).
I am currently working on a new project and this is how all data access is
being done.

Scott Mildenberger

> -----Original Message-----
> From: James W. Kilgore [mailto:qappdsn@attglobal.net]
> Sent: Friday, February 01, 2002 1:28 AM
> To: rpg400-l@midrange.com
> Subject: Re: Externalizing input and output.
>
>
> Here's another thought, if you don't want to go the SQL route, maybe
> someone has already tried this:  Use logical views explicitly listing
> the fields desired.
> One question though, if you run a CHGPF after adding new fields at the
> end, do you still need LVLCHK(*NO) even though nothing in the logical
> has changed?