RE: Externalizing input and output (record locks; unintended updates)

The trade-off is more programmer effort to keep the logicals organized (I
guess you could have one LF per I-O program), and you still have to deal
with record lock considerations.  7031's get filtered with CODE/400 and it
seems bad programming practice to change a DB data element value unless you
want the new value in the database.

This topic deserves its own FAQ...

Regards,
Reeve

-----Original Message-----
From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]On
Behalf Of Buck Calabro
Sent: Friday, February 01, 2002 6:24 PM
To: rpg400-l@midrange.com
Subject: RE: Externalizing input and output.


Scott wrote:

> 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.

It also offers performance benefits as well.  The wider the record length
passed in to RPG, the longer it will take to process that record.  Also, you
are saved from that inadvertent UPDATE to a field you never intended to
touch.  All of those 7031 messages go away, and only the fields you INTEND
to use are in the code.
  --buck
_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.