RE: Optimizing File I-O in RPG IV/ I-Series

Maybe you're already doing this: Skip the update statement for records whose
data hasn't actually been changed.

Rick Weber  |  TOYS 'Я' US International 

-----Original Message-----
From: Jim Wiant [mailto:Jim.Wiant@xxxxxxxxxxxxxxxx] 
Sent: Tuesday, November 22, 2005 7:18 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Optimizing File I-O in RPG IV/ I-Series

We have a series of programs that update files for assorted maintenance.
The time these programs are taking is becoming excessive.

In most cases, the RPG code is very simple.

Key     SETLL                   file
Key     READE                   file
        (Do until EOF)
        UPDATE          record
Key     READE                   file
        END DO

I don't see how the code can get might tighter. Is there any reasonable
compiling options/ CL overrides, etc. that could improve such a routine
when it
needs to process a large number of records? We're not opposed to
changing code, but if just a few H spec changes and/or compiling options
could gain
us a bit of performance, it would help us out.

I've tried a few of the basics (OPTIMIZE(*FULL), NoDEBUGIO, etc.) but
didn't see much of a change in my benchmarks.

Thanks for any help

Jim Wiant


Once a job is fouled up, anything done to improve it makes it worse. 
Finagle 


This message has been sent from Foodstuffs (Auckland) Limited
("Foodstuffs").

The information contained in this message and or attachments 
is intended only for the person or entity to which it is 
addressed and may contain confidential and/or privileged 
material. Any review, retransmission, dissemination or other 
use of, or taking of any action in reliance upon, this 
information by persons or entities other than the intended 
recipient is prohibited. If you received this in error, 
please contact the sender and delete the material from any 
system and destroy any copies.

The views and opinions expressed in this message may be those
of the individual and not necessarily those of Foodstuffs, 
and are not given or endorsed by it.

Please note that this communication does not designate an 
information system for the purposes of the Electronic 
Transactions Act 2002.