Re: SQL CLI HELP! I've got 2 SQLConnect calls fighting with each other -- MIDRANGE-L

× 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.

Scott Klement wrote:

I don't know why you're getting an SQL0950... I would've expected an SQL0842, so everything I say in this message may be completely wrong... however:

SQL CLI can only have one connection active in an interactive job.. (Err... this restriction may only apply to the local database, I don't know?) but the point is, if you already have one active connection, and try to create another one, the second one will fail with SQL0842. Which sounds like it matches your description of the problem -- except for the SQL0950 part :)

Thanks, Scott. You are truly a giant among AS/400 programmers.

Hmm. The older of the two programs doesn't do an SQLFreeStm, SQLDisconn, SQLFreeCon, or SQLFreeEnv after making the SQLExecDirect call, because when it was written, no conflicts were expected.

How much tear-down do I need to do in the older program, to make it stop fighting with the newer one? Understandably, I would kind of like to leave as much active as possible between calls, for the best response time.

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.