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

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 :)

The solution is to switch SQL CLI to "Server Mode". In server mode, the SQL CLI submits your SQL statements to an SQL server job instead of running them locally, and that makes it possible to have multiple connections.

There's an attribute SQL_ATTR_SERVER_MODE that you use to set this.

Not sure if this is a good answer or not, but maybe it'll point you in the right direction!



James Lampert wrote:

I have 2 programs that have the following SQLConnect call

SQL_SUCCESS = SQLConnect( hdbc:'*LOCAL'
:SQL_NTS :*null
:SQL_NTS :*null:SQL_NTS)

where "hdbc" is declared as "10I 0 inz"

Either program works fine by itself, but when I run both programs in the same job, only the SQLConnect in the first program executed works. The other program fails at that point, with an SQL0950:

Message . . . . : Relational database not in relational database directory.
Cause . . . . . : A request for relational database was made. However the relational database name was not found in the relational database directory.

Clearly, the two calls are fighting with each other.

Why, and what do I do about it?