RE: Chaining with a very large file

["Tom Huff" <tehuff@xxxxxxxxxxxxx>]

I am not sure what you mean. 
Yes, I am changing every record, but not at the same time. We are rebadging
the employees one at a time as they come in to get new badges. And compared
to SQL, the programs do fly. There are 600 plus files, and RPG reads all of
them and renumbers the employee in a little over 1 minute. Cant get much
faster that that. That includes the time to call multiple programs (6 as I
recall) each processing about 100 files. I know there are more elegant ways
of doing this, but this is not going to stay in production after everyone is
completed. Consequently, I wrote it as fast as I could.
Thanks
Tom

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Booth Martin
Sent: Wednesday, February 01, 2006 8:58 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: Chaining with a very large file

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