×
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.
I gave up on doing that without a WHERE. When I looked for an exact table and schema, it finished in 0.027 seconds.
-----Original Message-----
From: Matt Olson [mailto:Matt.Olson@xxxxxxxx]
Sent: Friday, June 28, 2019 1:57 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Finding offending RPG program causing locks on files
We are getting away from platform specific SQL code and have moved on to ORM's rather then thousands of lines of SQL spread throughout our programs. Injecting a platform specific code into hundreds of methods to track something that the database platform should be doing is not a path I want to explore.
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?
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.
midrange.com
