Re: Chaining with a very large file

[Booth Martin <booth@xxxxxxxxxxxx>]

Here's where I get boo'ed.

You are changing every record.  Two choices come to mind:

1)Is there anyway to get away from using keyed files?  There is no 
requirement that processing be in employee number order.  Removing the K 
makes these programs fly.

2)If you must use keys to keep things in synch then update/primary with 
update secondary on the other five files, and then use Matching Records. 
 This also makes a program fly.



Tom Huff wrote:
> The last time I tested this, RPG using SETLL & read loop with a test in the
> loop beat SQL by a factor of 10. I am changing all the records in an HR
> system one employee at a time. The employee number is being changed from
> SocSec to a generated number. There are about 600 files and each employee
> has anywhere from 25 to 25000 records. SQL takes an average of 8.5 minutes
> and RPG takes an average of 1 minute. 
> The total number of records to change was too large to run over a weekend so
> we broke it down to one employee submitted when the new employee badge is
> made.
> The programming in SQL was shorter but the RPG was MUCH FASTER.
> I wrote a log file of the number of records changed and the elapsed time
> using both methods. We are changing about 250000 employees. 
> Sorry to burst SQL's bubble, but it can not hold a candle to RPG.
> Thanks
> Tom