RE: SQLCLI problems: Now we know that the QSQCLI purge is not thecause.

Hi James,

There are a number of OS things that use SQLCLI under the covers:
CPYFRMIMPF
CPYTOIMPF
Some BRMS functions

We had an issue with CPYTOIMPF/CPYFRMIMPF & asked IBM what other parts of the OS used SQLCLI, but they would not tell us. We found out about BRMS because there was an IBM Support document that said not to run some part of BRMS with CPYTOIMPF/CPYFRMIMPF.

Regards,

Kevin Wright
--
LongReach - <http://www.lansa.com/longreach/> Share Files and Folders between IBM i Servers and iPhones/iPads <http://www.lansa.com/longreach/> - Download it for FREE today <http://www.lansa.com/longreach/> from the App Store <http://www.lansa.com/longreach/>

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of James Lampert
Sent: Thursday, 2 February 2012 8:48 AM
To: Midrange Systems Technical Discussion
Subject: Re: SQLCLI problems: Now we know that the QSQCLI purge is not
thecause.


Monnier, Gary wrote:

Is it there right after SQLExecDirect executes?

What does SQLExecDirect return?

If the QSQCLI activation group hasn't been corrupted, then it returns
either SQL_SUCCESS (0), SQL_SUCCESS_WITH_INFO (1), SQL_NO_DATA_FOUND
(100), SQL_ERROR (-1), or SQL_INVALID_HANDLE (-2). None of
which would
indicate that the activation group is on the verge of becoming
corrupted. And if the return code is negative, then my
program spits out
a dump of the SQL statement that caused the error, and some
diagnostics.

If it's been corrupted, it throws an exception instead of
returning, the
job locks up, my program abends, and the QSQCLI activation group dies.

--
JHHL
--
This is the Midrange Systems Technical Discussion
(MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.