I understand that using a DDS LF in your Query may have been a good practice in the past. For example, with IIM being the table, IIML01 may be a LF with not only an index but also record selection. In our case, "Active" records only.
And while you want to replace your DDS LF's with SQL indexes you would like to continue that "one stop shopping". I don't think that's possible.
Some may say that you should query against the table and it would then use that index. However would it really? Wouldn't it rather use an index with an index not just over your "key" but shouldn't the index also include your "where" clause? So your index would have your active record id column, then any key, or order by, columns. That index would not work for existing code using RPG RLA. So it would have to be in addition to. And you would still query the table or a view when using sql.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2022 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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.