× 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.



Shannon -

SETLL does NOT move any data or clear any buffers - it simply positions the file cursor to be ahead of the record containing the key value specified in the KLIST.

So, as far as efficiency goes, I'd say that the first example which uses SETLL (except using %EQUAL instead of %FOUND) will be much more efficient than using the CHAIN operation code, since CHAIN does perform I/O and if a record is not found it clears the buffer area.

- sjl

----- Original Message ----- From: "Shannon O'Donnell" <shannon.odonnell@xxxxxxxxxxxxxx>
To: "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
Sent: Wednesday, February 28, 2007 1:27 PM
Subject: CHAIN Versus SETLL and READ When Data Needed


I posed this question on MCPressOnline the other day but I would like to
get more opinions on it so I'll post it here too.   A shop-standard
hangs in the balance.



  Assume that you have an RPG program that has logic such that you need
to first see if some data is in a file, based on a key, and then if so,
you do something with that data.



  Further assume that this file has a complex key with three fields.



   The program logic is such that you check the maximum number of keys
for a match down to the minimum number of keys



    Like this:



             Key1    Klist

                         Kfld              Fld1

                         Kfld              Fld2

                         Kfld              Fld3



             Key2     Klist

                         Kfld              Fld1

                         Kfld              Fld2



             Key3     Klist

                          Kfld             Fld1





  Which one of these logic blocks is most efficient?



  Key1   Setll   file

      If    %FOUND(file)

              Key1   READE file

                      Use Fields

      Else

         Key2    Setll  File

           If   %FOUND(file)

                    Key2 Use Fields

          Else

            Key3  Setll File

                 If   %FOUND(file)

                    Key3 READE file

              Endif

           Endif

         Endif







OR....



              KEY1  Chain file

                         If       %FOUND(file)

                             Use fields

                        Else

             KEY2   Chain  file

                         If      %FOUND(file)

                             Use Fields

                         Else

             KEY3   Chain file

                         If   %FOUND(file)

                            Use Fields

                        Endif

                        Endif

                        Endif





My opinion is that the CHAIN is more efficient from both a
coding/maintenance standpoint and from an I/O standpoint, but I'm open
to opinions.











--
This is the RPG programming on the AS400 / 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.




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.