Re: MSSQL Stored Procedures Call

You can use the same blocks to build a better solution (only one JVM Call
):

create a java program that is a permanent job and

open the JDBC connection to MSSQL
read the request dataq (easy with jt400.jar) and receive the arguments and
the key for the answer
call the remote procedure using the arguments
send the result to the response data queue
loop on the data queue ...

you can stop this program by sending a special *END message

the user program sends the request and the key the data to the request
dataqueue
then waits the answer reading the response dataqueue on the key...

Paul




From: Don Brown <DBrown@xxxxxxxxxx>
To: MIDRANGE-L@xxxxxxxxxxxx
Date: 17/03/2016 13:40
Subject: MSSQL Stored Procedures Call
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>





Looking for any suggestions;

I have a call to a stored procedure on a MSSQL server. The function is
used
by multiple users and called multiple times.

My thinking is to create two keyed data queues and a monitor program that
can start the JVM and create the connection to the MSSQL server, then wait
on requests on the data queue. A request is then processed and the result
returned on the second data queue.

Is there a better solution to avoid the overhead of starting the JVM and
initiating the connection to the MSSQL server for each request?

Thank you for any suggestions

Don

Sent from my iPhone