If you use a KLIST you must set all fields within the KLIST before the SETLL - how else would you know where you are starting.
The scenario you pose does not cause issues - you are only using one field and you have set the value of that one field.
Paul
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Gqcy
Sent: Thursday, October 18, 2012 1:29 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: setll, reade question.
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.
midrange.com
