Oh my, hashed it has been...
The database access is crazy fast and there is almost is no difference.
I am sure I will be corrected, but as I understand it:
If you are just validating the existence of your key fields the SETLL/%EQUAL
is faster,
If after the SETLL you are going to turn around and do a READE, because you
need the data from a field not in your keylist, just do the CHAIN and be
done with it.
Charlie
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Vinay Gavankar
Sent: Monday, October 14, 2013 12:44 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: CHAIN vs SETLL/READE
Hi,
I know this has probably been hashed a lot of times, but which of this is
more efficient?
Doing a direct Chain or a SETLL and if %EQUAL doing a READE
I am accessing on a full unique key, but performing this millions of times
in a batch program.
Most of the times the record WILL be found.
Thanks
Vinay
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (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
