×
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.
First, I got rid of the named activation group experiment, and went back
to *CALLER, since in this case, *CALLER, being a mixed-language ILE
program, is already in an ILE activation group.
I set up a *PSSR, that (if an indicator is set, which I set just before
the SQLExecDirect call, then clear immediately after) attempts to free
the statement handle, disconnect, free the connection handle, free the
environment handle, then call the *INZSR that reinitializes the handles
and connection.
And I have (E) extenders on all the CALLPs to close out the connection
and handles, and "IF %ERROR" blocks spitting out messages if they fail.
They all throw exceptions, as does the SQLAlcEnv call in *INZSR. (And
despite my efforts, this manages to somehow throw the program into an
exception tightloop.)
It sounds more and more certain that *something* that the customer has
wedged in via an exit program is corrupting SQLCLI.
I already know that SQLCLI has a problem with multiple programs having
active connections to *LOCAL in the same job, although I forget the
exact details.
--
JHHL
As an Amazon Associate we earn from qualifying purchases.
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
