Re: SQL Connection Issue

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 09/13/2017
03:16:56 PM:

could you provide a little bit more info. It seems to be aliitle bit
confiúsing to me. As far as I understood, you are trying the following:
- you have a connection to MS SQL via ArdGate
- you are calling a stored procedure from DB2/400, running on MS SQL
- this procedure is calling a stored procedure sitting on DB2/400 via

ODBC

- this is working the first time and failing at the second shot
- you have a log utility, running on AS/400 trying to write something to

the

local database
- Conect reset is failing
- logging is failing too, if you are running your logging SRVPGM in a

named

ACTGRP of its own

Is this, what you are doing and how it works?

I'm sorry you got the impression that ARDGATE is involved -- when
it is not. These are the sequence of events:

- A network user invokes a network application that uses MS SQL Server as
its back end
- On user request of a function, MS SQL Server initiates an ODBC
connection to the IBMi by calling a stored procedure on the IBMi
- The first time, the stored procedure reads from and writes to the local
database with no problems and returns the expected results
- The user requests the same function again with potentially changed
parameters (but in our tests we are using exactly the same parameters)
- MS SQL Server reuses the existing ODBC connection to again call the same
stored procedure but with the potentially changed parameters
- This time the stored procedure fails when it tries to read from a local
table to get some information -- trapping the error
- Thus, the standard SQL error routine is invoked and it fails when it
tries to prepare a statement to record diagnostic and message information
concerning the above failure


Sincerely,

Dave Clark