Re: setll, reade question.

Are the operation and sequence number the same thing? You can read all
the records in file 1 for order num 5, for example, and then all the
records from file 2 for order num 5. Or do you want to read one record
from file 1, then one from file 2, etc.. Why do until EOF? Wouldn't it be
until that end of that order number?

Thank you,
Nancy
On Thu, 18 Oct 2012 13:28:43 -0500 Gqcy <gmufasa01@xxxxxxxxx> writes:

we are having a debate here about files with composite keys, and how

SETLL and READE will position...

example:
File 1 key: Order#, Operation#

File 2 key: Order#, Sequence#

however, when I code my loop, I want to read all file 1 records for
that
order, and within that loop I want to read all file 2 records.

we have it coded as:
<<<ORDER# is a field, not a KLIST>>>

ORDER# SETLL File1
ORDER# READE File1
DOU %eof(FILE1)
... ...
ORDER# SETLL File2
ORDER# READE FILE2
DOU %eof(file2)
... ...
ENDDO
ENDDO
HERE IS OUR DEBATE POINT:

some of us are remembering problems with not setting ALL KEY VALUES,

because you may have problems with the remaining key fields not
being
set to *LOVAL...
However, I seem to think that was only when you were using a KLIST
or
something like that...

--
This is the RPG programming on the IBM i / System i (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

____________________________________________________________
Woman is 53 But Looks 25
Mom reveals 1 simple wrinkle trick that has angered doctors...
http://thirdpartyoffers.juno.com/TGL3141/508056ab7055256ab02a2st04vuc