Re: RPG Cross-Platform to SQL Server

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 12/16/2016 10:52:52
AM:

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 12/16/2016 02:37:40
AM:

Stored procedure support was made for a customer, who needed it for
Oracle.
The diffrence between Oracle and MS SQL is, that MS SQL doesn't

support

inout parameters (and at the moment ArdGate expects all parameters to

be

inout).

It is true that MS SQL Server doesn't support the INOUT keyword,

but a stored procedure parameter declared with the OUTPUT keyword can
still be used as an INPUT parameter by default. We have already proved
this here that this works. So, I don't know why either ARDGATE or the
SourceForge MS driver would have a problem calling a MS SQL stored
procedure with one parameter which is both input and output capable.

Now, I will say that MS SQL Server doesn't use the CALL keyword
for invoking stored procedures. Rather, it uses the EXEC keyword -- but I
still have to specify the CALL keyword from an embedded SQL point of view.
Is this the real source of the issue?

Sincerely,

Dave Clark