Re: Expensive op codes

>  1) Functionally, one way READE works differently is that the data does
not
> populate the input fields if the key is not equal.  Code has to be
> generated for that.

Now that's interesting. It sounds like an explanation of why READE is
faster.

>
> 2)  When the EOF indicator comes on, this is considered an "error"
> condition to that opcode.  I/O error conditions tend to be expensive.

Hmm. That's true. What we don't know from Dave's test is how many "level
breaks" there were. If the key was equal for all million+ records, would the
time be comparable to the READ/compare?

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


__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com

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