Dan, I didn't see your post on that, but *I* would be interested in learning more. I think this would be very popular in any shop where both DB2 and MSSQL are in use, which is probably most shops these days.... Where could one find that technical details needed to construct one? I seem to recall that IBM sold documentation (for mucho $$$) describing the DRDA architecture, which is why I never looked seriously into the problem.

I found a document (copyrighted to DEC in 1991) on Microsoft's site that explains some of the differences in the two standards... Of course, this is slanted to make IBMs DRDA seem overly complicated, but it still seems helpful to understand the issues.
http://research.microsoft.com/~gray/papers/sqlaccessvsdrda.pdf

Oh, here something (for z, but I would assume i would be similar)...
http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/topic/com.ibm.db2.doc.drda/dsnudj12.pdf?noframes=true

Ok, I gotta retract my "limited information available" statement above... It seems there's more info than I recalled (though some is a little outdated)...
http://www.redbooks.ibm.com/abstracts/gg244275.html

Most of what I see out there is dated from the mid-90s....

Anyway, if you're serious about this, I might like to learn more.

Thanks,
Eric DeLong

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Dan Kimmel
Sent: Thursday, July 17, 2008 2:09 PM
To: Midrange Systems Technical Discussion
Subject: RE: Accessing MSSQL with SQLCLI



I tried to generate interest in an open-source project to build such a
DRDA connector a couple months ago and got exactly one response. I let
it go for apparent lack of interest.

Dan Kimmel

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DeLong, Eric
Sent: Tuesday, July 15, 2008 5:30 PM
To: Midrange Systems Technical Discussion
Subject: RE: Accessing MSSQL with SQLCLI

I think to use DB2/CLI from the i to access a MS Sequel Server, you must
have a DRDA acces provider installed. This is notoriouly difficult to
do, as there do not seem to many products that can provide this support.
Generally, the standard alternative approach is to use a Java based JDBC
driver (type 3?) to connect to the remote server. Scott Klement has
published several articles covering this.

Eric DeLong

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Joe Giusto II
Sent: Tuesday, July 15, 2008 5:08 PM
To: Midrange-L
Subject: Accessing MSSQL with SQLCLI


can anyone help me with the connection parameters to access the MSSQL
data base using SQLCLI?

i have been searching all day and the only example i found for SQLCLI
was for attaching to another AS400 data base.

in the example i have been trying to work with, i have the following
connect
statement:
rc = SQLConnect(hdbc :
szDSN :
cbDSN :
szUID :
cbUID :
szAuthStr :
cbAuthStr);

cbDSN = SQL_NTS
i have changed szDSN to the name of the data base (which i am able to
access via ms access odbc driver) but i do not know how to tell it the
location (ip
address) of the server that the MSSQL data base resides on.



--
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.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.