|
Probably most shops are this way, and it is hard to get away from in an
existing databse, but you can get essentially the same level of
independence with RLA as you can using SQL. Instead of reading the
physical, use LFs and explicitly specify the fields in the LF. You can
then change the underlying physical and no program need to be recompiled.
However, I personally find explicit field specification in SQL (SELECT
fieldname, fieldname, as opposed to SELECT *) to be easier.
Sam
On 11/18/2010 6:32 PM, Alan Campin wrote:
When you use RLA, unless you externalize your I/O somehow (which almostno
one know how to do and won't use it even if you did), you are bringingthe
entire record into the program which in effect, locks the table tochange.
recompile
That means the next time you need to change the table you have to
every program that uses it and very quickly no wants to recompile 500--
programs so they start creating extension tables or reusing fields or god
knows what.
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.