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



"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 06/28/2019
02:57:07 PM:
It looks like this link is more likely something I would want. I
wonder if the that lock detection thing is what the
QSYS2.RECORD_LOCK_INFO view is doing under the covers. Unfortunately
when I issue the following SQL it never returns any data. Been
running for about over 3 minutes now without returning lock details:

SELECT * FROM QSYS2.RECORD_LOCK_INFO

Is anyone able to successfully execute that SQL statement?


RECORD_LOCK_INFO is a user-defined table function. So, you must
wrap it with the SQL TABLE() function (and probably add some parameters).


Sincerely,

Dave Clark

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.