Re: Simon Coulter's post, and %EOF

I kind of liked (was it RNF7086 or RNS7086) at the bottom of my compile 
listing.  "RPG handles blocking for the file."  Rather nice to have all 
this done automatically, isn't it?  Sometimes it makes you wish that they 
came out with Primary files in a later release.  This way all the people 
would think they are the greatest thing since sliced bread.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




"Booth Martin" <Booth@xxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
09/30/2003 10:42 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
<midrange-l@xxxxxxxxxxxx>, <joepluta@xxxxxxxxxxxxxxxxx>
cc

Subject
Simon Coulter's post, and %EOF






"The secret is blocking. Fixing the I/O is the single best thing you can
do to fix performance problems (presuming there are no physical
constraints like insufficient main storage, or a gutless processor)".
 
 
 Joe, I am curious.  I do not know how to do the kind of testing you did 
on
the read/reade issue, but I am curious enough about the effects of adding
BLOCK(*YES) to the file's F-spec to ask if by any chance you saved your
testing program?  If so, could you add BLOCK(*YES) to the F-spec for the
READ version, and retest?  It is my contention that the performance boost
will flabbergast you.

                                            or not.

Thank you for your consideration.

---------------------------------------------------------
Booth Martin http://www.MartinVT.com
Booth@xxxxxxxxxxxx
---------------------------------------------------------
 

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.