×
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.
Alan Campin wrote:
I am having problems with clears being able to clear members and
I have traced the problem back to the SQL statements in a service
program.
If the cursor is supposed to be closed but the lock & open remain
on the file.mbr, then it may be pseudo-closed cursor. If so, then
if the request to WRKJOB OPTION(*RUNA) /* or is it *DFNA? */ shows a
/small/ Default Wait value, then try CLRPFM after CHGJOB DFTWAIT(30)
to give time for the holding job(s) to effect their close activity.
It appears that I was not closing an SQL cursor after I was done
with it.
Even a CLOSE will not ensure avoiding a pseudo-close by the SQL
database feature. The SQL might choose to pseudo-close instead of
full-close, with the expectation the same cursor is simply going to
be opened again; e.g. as when open\close pair is in a coded loop.
<<SNIP *ENDMOD stuff>>
Now the fun part is that when I run it in test I don't see the
cursor open after it returns.
The open/close cycle must be repeated for the statement to have
the pseudo-close feature activate.
Regards, Chuck
This mailing list archive is Copyright 1997-2025 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
