RE: When is %EOF not an %EOF

["Christen, Duane J." <dchristen@xxxxxxxxxxxxx>]

This is how I expected the ReadE to work, Thanks Hans. 
As to performance, program correctness and maintainability are ALMOST always
more important, but there are always exceptions to the rule.

Duane


-----Original Message-----
From: Hans Boldt [mailto:boldt@xxxxxxxxxx]
Sent: Monday, September 29, 2003 9:03 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: When is %EOF not an %EOF



READE is different than CHAIN. There are two cases to consider: 
First, when a search argument is specified, READE is more or less 
equivalent to a sequential read followed by a comparison of the key 
of the record read to the search argument. Second, with Factor 1 
blank, or *KEY specified as search argument, a "get next key equal" 
request is sent to the database.

I won't comment on relative performance since it depends on a lot of 
different factors. If performance is important to you (more 
important than, say, program correctness or maintainability), you 
absolutely need to get intimately familiar with some good 
performance measurement tools. No amount of anecdotal evidence or 
hearsay can substitute for rigorous performance analysis using the 
proper tools.

Also, if you're quibbling over 5% or 10% differences, I would 
suggest your priorities are misplaced.

Cheers! Hans



NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named.  Any use, copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via e-mail.