Re: Externalizing input and output.

["James W. Kilgore" <qappdsn@xxxxxxxxxxxxx>]

Scott,

I've wondered about this ever since IBM introduced the CHGPF command.
It does allow for an alternative strategy.  And with shared indexes
doesn't take up much disk space.
I'm willing to bet that the 80/20 rule applies to most applications (80%
of the programs only need 20% of the data)
Thanks.

Scott Mildenberger wrote:
>
> 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.