Re: Need ideas to reduce open/close in RPG program

I'll throw out my .02...

Two options:
1) remove some of the flexibility. Have the RPG program open all 15 files
and leave them open. You could take advantage of RPG's new ability to pass
pointer's to a file so that you can continue to do the "work" with just one
file. See
http://www.itjungle.com/fhg/fhg032112-story01.html?cm_mc_uid=81101823313814495136640&cm_mc_sid_50200000=1450101117

Alternatively, you could build an RPG Open access handler that opened all
15 files and did the I/O as needed. That's probably a harder solution.

2) Re-architect, consolidate all 15 files into one _new_ file. The new
file would have one additional field that indicates which file it would
have been in. You could even replace the 15 existing files with LF's build
over the new physical. You can just select the records that would have
been in each file.

Charles

On Fri, Dec 11, 2015 at 6:42 PM, Vinay Gavankar <vinaygav@xxxxxxxxx> wrote:

Hi,

We have a program which receives some values thru Data Queue read and it
updates a file with the values received.

The problem is that there are multiple copies of the file it needs to
update.

Let us say it is updating FILEA, so that is what is in the compiled code.

On the system there are currently 15 files which are exact copies of this
file. They have a different file name, but the the same record format name,
field names etc.

The program reads a 'control' file, which has the names of these 15 files.
For every file, it does an OVRDBF of FILEA to the actual file name, Opens
the file, updates/writes the record, and then Closes the File.

The system was built for 'flexibility' years back, when they started with 2
or 3 files. It is flexible, in the sense it did not need a code change as
the files being updated grew from 3 to 15.

This is a very 'busy' program, meaning it is constantly receiving data thru
the data queue. Actually there are multiple copies of this program running
simultaneously receiving data from the same data queue and all of them are
pretty busy.

Now they are finding that all these open/closes are seriously impacting the
CPU usage.

An architectural change is obviously indicated, but that would take time to
implement.

As usual, they are looking for a 'short term', quick and dirty fix (to be
implemented in 2 weeks) to eliminate these open/close.

The only thing we could think of was to define the current 15 files
separately in the program and then update them as needed, losing all
flexibility.

Any other ideas or suggestions would be greatly appreciated.

TIA
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.