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 firstname.lastname@example.org.
Since you are using an IBM supplied table function, or view, or whatever, (QSYS2.RECORD_LOCK_INFO), open a "PMR" or "case" with IBM Support to report this as a problem, and suggest that IBM should "fix" this.
All the best,
Mark S. Waterbury
On Friday, September 9, 2022 at 10:19:50 AM EDT, Justin Taylor <jtaylor.0ab@xxxxxxxxx> wrote:
VE is recommending an index over QSYS/QADBXREF. The query in question is using QSYS2.RECORD_LOCK_INFO. I've never seen an index recommended over a QSYS table before. Is it a bad idea to create indexes over QSYS tables (they'd be in a diff schema of course).
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2023 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.