RE: Calling a java stored procedure from SQL server

Right, I understand... However, the term "stored procedure" indicates
the use of SQL to invoke an external program. In our world, anything
SQL means DB2...

I think you found the best approach, using web services for this...

Hth,
Eric DeLong

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren
Sent: Monday, April 06, 2009 4:21 PM
To: Midrange Systems Technical Discussion
Subject: Re: Calling a java stored procedure from SQL server

Actually, the OP (me) just wanted to call a java stored procedure on the

i. DB2 wasn't involved, unless it needed to be. The Java program
accessed DB2 data but the DB was secondary. I just wanted to know how
to invoke the Java program on the i from MSSQL

I ended up taking the web services route, which I am still working
through, because the web services gave me a few more "open" options.

Pete

DeLong, Eric wrote:

I thought so too... Last time I looked for it, all links and

references

went to dead sites....

Additionally, I thought MSSQL server operated as a DRDA "client"

only...

Meaning that they could connect to DB2 as a DRDA client, but DB2 could
not connect to SQL server..... This in fact seems to be appropriate

for

the OP, as they want MSSQL to connect to DB2.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Friday, April 03, 2009 2:50 PM
To: Midrange Systems Technical Discussion
Subject: Re: Calling a java stored procedure from SQL server

I was under the impression that Host Integration Server (HIS) formerly
known as SNA Server had to be involved to give MS it's DRDA Client
functionality.

I could be wrong however...

Charles

On Fri, Apr 3, 2009 at 3:13 PM, Dan Kimmel <dkimmel@xxxxxxxxxxxxxxx>
wrote:

It's a linked server entry with DRDA. I'm afraid I haven't done one

for

years so don't know where the documents might be. The IBM OLEDB/ODBC
drivers use DRDA host anyway, so it might not make much difference.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
lgoodbar@xxxxxxxxxxxxxx
Sent: Friday, April 03, 2009 12:30 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Calling a java stored procedure from SQL server

So you're saying I don't need to add a linked server entry (and
associated OLEDB/ODBC driver) to access i5/OS DB2 data? Where can I
learn more?

Assuming here I'm on the MS SQL Server and want to run queries

against

DB2.

--Loyd



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dan Kimmel
Sent: Friday, April 03, 2009 12:20 PM
To: Midrange Systems Technical Discussion
Subject: RE: Calling a java stored procedure from SQL server

From the beginning, as far as I know. However, it only supports DRDA

as

a host; it cannot be a client. So you can't ADDRDBDIRE on your i and
reference MSSQL.

There may be an install option to get it.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jason Abreu
Sent: Friday, April 03, 2009 11:58 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Calling a java stored procedure from SQL server

When did MSSQL Server start supporting DRDA?


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing

list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take

a

moment to review the archives at

http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.