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

Just out of curiosity Mark, what is IBM going to "fix"? There's no fault here, just a longer run time for a query. If IBM were required to create an index for all the various uses of the table functions that users might want/need, there would be so many that it would be unmanageable. Now, IBM might deem this one worthy, but I would not call this a fault. Enter an Idea, sure.

I can see a temporary index being created if there are more than a couple of queries that might use it run all at once, (remove when done) but I would be careful about a permanent object being created over a table function or system table. Too many bad possibilities to consider.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

------ Original Message ------
From "Mark Waterbury" <mark.s.waterbury@xxxxxxxxxxxxx>
To "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxxxxxxxx>
Date 9/9/2022 9:15:20 PM
Subject Re: Index over QSYS/QADBXREF


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

-- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-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 On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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 [javascript protected email address].

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