File Reads

[VENU YAMAJALA <venu_yamajala@xxxxxxxxxxxx>]

Hi All,

Recently we wrote a DateAging application. The application uses multi
threading. Each data file in the user library is aged simultaneously as
independeng aging jobs. We used this to enhancethe performance. Earlier version
was only single thread where the application used to age one datafile at a
time. Although we gained a lot of improvement with the new design, we still are
facing some difficulties particularly with files of bigger size.

We have this application written in ILE and we are having different modules to
do different tasks, we have service pgms, binding directories...all that stuff.
We have compiles the main program as

CRTBNDRPG with OPTIMIZE(*BASIC).

We are still facing some performance problems. A data file of 1 million records
is taking more than 15 hrs to complete the job. Is there anything to do with
this OPTIMIZE(*BASIC). I read in the ILE manuals that there will be significant
improvements if we change this to OPTIMIZE(*FULL). But I dont know what
improvements it is referring. The majority of time is wasted in the I/O of the
datafile. How is this OPTIMIZE parameter going to influence the data file I/O??
The manual says that there will be significant improvements with
OPTIMIZE(*FULL) but there will be some problems also. What are these
difficulties??

We are also thinking of chaning the record blocking factor for the data file.
That is, before calling our RPG program, we will do a OVRDBF of the datafile
with NBRRCDS as say 10000. Will there be any improvements and what are the
possible problems we will face if we change the NBRRCDS parameter?

Any ideas or thoughts,. Thanx in advance for any help.

Rgds
Venu


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---