Re: Synch/Asynch was Re: Expensive op codes

>Thanks John! Basicall the problem is blocking. The synchronous opcodes
don't
>do it, the others do. One minor note on the following paragraph - doesn't
>READ, even if for input only, have to use the Index Object if the File spec
>says it's keyed?

>> The READ(for input only) doesn't concern itself with having to read the
>> Index Object for what it wants,   It goes straight to the data space.
>> Reading the data space consecutively.    Blocking is used.  The default
>>size
>> used to be 4K, (as seen on a compiler message QRG7086 ?).

Yes,  Thanks I was tired and didn't notice it until I re-read it this
morning.   No K in the Fspec.
So the additional job is to have records physically in order.   But you can
still
block the move from "Memory" to  the "PAG"'s ODP  using SEQONLY(*YES nnn).

John Carr  


+---
| 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
+---