×
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 have seen this in cases where one program that invokes SQLCLI calls another program that also invokes SQLCLI. As soon as the called (second cli app) finishes, SQL runs a CLEANUP routine that closes open cursors and so forth. When caller (first CLI program) tries to access its open cursors, it crashes.
I think it has to do with CLI changing the SQLCA defined for the job. Second CLI mangles the job's SQLCA, forcing the cleanup...
-Eric DeLong
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James Lampert
Sent: Thursday, January 26, 2012 10:52 AM
To: Midrange Systems Technical Discussion
Subject: SQLCLI problems: handles evidently being invalidated
As I mentioned in my thread on activation groups, there is evidence that
somehow, the session, connection, and/or statement handles are being
invalidated outside of calls to SQLCLI.
Does anybody know what could cause this, or how to detect it before it
blows up in the user's face?
--
JHHL
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: SQLCLI problems: Now we know that the QSQCLI activation group is getting purged . . ., (continued)
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
