Re: Why define files internally (was: What bugs you about KLISTs in RPG IV?)

["Joep Beckeringh" <joepb@xxxxxx>]

>Why do define all your files internally?


Because:

a) We like to see in our sources what fields are used in the program;

b) We don't like to get all the fields when often we only need a few;

c) We hate to have level checks when fields are added to a file.

Ad a) and b):  We would be much happier if we could specify the fields we DO
want (as is possible in the output specifications), instead of kludgily
renaming the fields we DON'T want.

Ad c):  We build and maintain a number of software packages and most of our
customers have some custom built modifications and extensions.  Often these
extensions need added data base fields.  When using externally defined
fields, this would lead to extra logicals, excluding the additions, to
satisfy the standard programs.  (The first new package we built after
migrating from the S/36 to the AS/400 was externally defined first, but
after a few years we decided to revert to internal definitions).

Joep Beckeringh
Pantheon Automatisering B.V.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
* be directed to the list owner / operator: david@midrange.com          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *