RE: Slow respond time when file change to open with update&Add

["Lim Hock-Chai" <Lim.Hock-Chai@xxxxxxxx>]

After copied those data to our test system, here is the result.

1) Ran for 33 mins (420 secs of processing unit time): Input file opened as (IF 
K), Outfile (UF A).  (Chain, update if found else write)
2) Ran for 9 mins ( 365 secs of processing unit time): Input file opened as (IF 
 ), outfile (UF A) Unique.  (Chain and update if write failed)
3) Ran for 7 mins ( 307 secs of processing unit time): Input file opened as (IF 
 ), outfile (O   ). (Write only)


Seems like the unique key method does help.

Thanks everybody.


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Haas, Matt
Sent: Wednesday, April 28, 2004 4:50 PM

Another variation on this is to create a unique key on the output file and 
always write to it. When the write fails with a duplicate, you can do your 
chain and update. If you're doing mostly adds, this should speed things up. If 
you're doing mainly updates, this will probably be slower since it's adding 
another I/O operation on updates.

Matt