× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



There are two considerations here: one is execution speed and the other is
"clarity of purpose". The latter term reflects future programmers' ability
to understand what you're trying to do with SETGT and READPE. Assuming you
have (or can) index the field in question, I suggest MAX(your_field) is the
better option because the intent of the code is clear and satisfies the
"clarity of purpose" directive. The SQL approach also eliminates the
dependence on a DDS physical/logical file key structure.

-reeve

On Tue, Nov 9, 2021 at 10:49 AM Alan Cassidy <cfuture@xxxxxxxxxxx> wrote:

i'm using SQL to get the maximum value for a field meeting key field
WHERE comparisons into an RPG variable.

I'm replacing code that used the SETGT with READPE to find the maximum
value.

I'm wondering which method shows better performance if somebody knows. I
was told once that single-value CHAIN trumps using SQL to get one value
for one composite key. But time has passed and IBM keeps on juicing up
the SQL engine...

-Alan Cassidy

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

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.