Re: Record blocking optimization

>Dow Not %EOF(primary)
>     Read primary;
>     Read secondary;
>     // Calc specs
>EndDo;

Not quite. This is the bit the cycle does for you:

Dou %EOF(primary file) and %EOF(all secundary files)
        Read primary file
        Read all secondary files
        Move data of appropriate file into program fields
EndDo

Note that there can be only one primary file, but any number of secondary 
files.
The appropriate file:
- If no match fields are specified, you get all the records of the primary 
file, then all the records of the first secondary file, then the second, 
and so on.
- If match fields are specified, you get the records in the order of the 
match field.

And this is the bit your program has to do:
        Determine from which file you got data
        Execute appropriate code

Typically you would use input indicators to determine the file and fire 
the appropriate subroutine.


>One last question.  There is a possibility that a record might be
>missing from either file, causing the synchronization of the input
>streams to be out of whack.  If this is the case, Can I issue a READ
>op in the calc specs to either file to re-synch the files?

No. The cycle does all the reading. It is possible though to open a file 
more than once, using different names (EXTFILE in RPG or OVRDBF before 
opening) and different attributes.

Joep Beckeringh