from my experience...there is no such thing as a one-time shot...they
usually end up in production...even with conversions...you'll likely reuse
the code again when it's time for another upgrade, etc.
Thanks,
Tommy Holden
"DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
12/19/2007 03:24 PM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
To
"RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
cc
Subject
RE: RPG Cycle (was Multi-Occurring DS)
Is that going to be a one-time conversion? By all means, write whatever
you want. But please do not put that code into "Production"..... One
time conversions would seem to be a special case, perhaps.
If it is NOT a one time conversion, my first thought would be SQL.
Set-based operations are SQL's bailiwick. Again, in my opinion, SQL
allows me to clearly express my intent. No need for a ride on the
cycle....
Eric
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of James Lampert
Sent: Wednesday, December 19, 2007 4:11 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: RPG Cycle (was Multi-Occurring DS)
Armbruster, Tom wrote:
Eric,
I agree with your methodology. With a normalized database,
appropriately keyed files and valid logic, there should never be a
reason to read every record in a file.
. . . Unless you need to perform some operation on every single record.
Or you need to make a decision on whether the operation is appropriate
based on some criterion other than a key.
midrange.com
