Re: BLOCK(*YES) questions

[Dan <dbcerpg@xxxxxxxxx>]

--- Barbara Morris <bmorris@xxxxxxxxxx> wrote:
> BLOCK(*YES) doesn't affect the order of the records; it's basically a
> performance thing, to reduce the number of times the program has to go
> to data management to get or put the records.  If the file is being read
> keyed (as yours is), the blocks will contain records in keyed order.  If
> you didn't have the K, the blocks would contain records in rrn order.

So, physically, records by key can be all over the file, but BLOCK(*YES) on a
keyed file puts them in the buffer in key sequence.  If the system has to jump
all over the disk to build this buffer, is there really any time savings?

Another question:  Does the RPG program get control of the buffer after the
first record is put in the buffer by the system, or does the RPG program wait
until the system fills the buffer?

This is an eye-opener.  A colleague told me today that the BLOCK keyword for
the F-spec has been around since v3r7!  That one must have flew underneath my
radar when it came out.

__________________________________
Do you Yahoo!?
Get better spam protection with Yahoo! Mail.
http://antispam.yahoo.com/tools