×
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.
On 3/10/2017 9:57 AM, Justin Taylor wrote:
I have an internal procedure that reads a table using a SQL cursor. I explicitly close the cursor before returning, but it seems to be keeping a *SHRRD lock on the PF. What's the best way to eliminate this problem?
The best way is to avoid doing things restricted by *SHRRD and that's a
sincere lesson I learnt the hard way. When I start using SQL on a file,
I stop doing things like RGZPFM. What's happening here is a
pseudo-close; the machine is trying to be efficient with future use of
the same SQL statement in the same job.
Depending on how your app is constructed, you can reclaim the activation
group to hard close the cursor. Or you can use ALCOBJ ...
CONFLICT(*RQSRLS) in the job that's needing the *SHRRD, and IBM i will
do the hard close then.
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
