Avatar of superthumper
superthumper asked on

How do I create an AS400 linked server?

I'm trying to create an AS400 linked server on SQL2005.  I have Microsoft's  DB2OLEDB provider installed.
I know how to create a linked server in SQL 2005, i just need to know what to fill in for the parameters when creating the AS400 linked server.

Product Name: ? (no idea)
Data Source: ? (the AS400 server name?)
Provider String: ? (this one I have no clue....)
Catalog: ? (the database name?)




  There's an old question on EE, but the link in the solution is dead.  Has anyone done this and can help?  Thanks.

Any help on the login portion would be very valuable as well

I'm marking this urgent as my client needs me to move 5 tables yesterday :)
Microsoft SQL Server 2005DB2

Avatar of undefined
Last Comment
superthumper

8/22/2022 - Mon
chapmandew

ASKER
superthumper

I need to do it without installing IBM client tools on the server.
chapmandew

Does the article indicate that you have to do that?  Are you able to setup an ODBC connection to the AS400 machine?
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes
Member_2_276102

> I need to do it without installing IBM client tools on the server.

That's like saying you need to access a remote SQL Server database without installing the Microsoft tools/drivers for SQL Server.

In order to access _any_ vendor's remote database, you need to install the tool/driver that that vendor provides (or write your own; I guess I could supply some info for you to contact IBM to obtain their LIPI documentation for their database server...)

Given your circumstances, your choice seems limited to an appropriate JDBC driver. The JTOpen JDBC driver might work:

http://jt400.sourceforge.net/
and some info:
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/rzatz/51/admin/refjdbcdrv.htm

I have no idea how the JDBC driver might interact with the environment you're working within.

Tom
ASKER
superthumper

As I mentioned:  I have Microsoft's  DB2OLEDB provider installed.  I was just looking for the correct parameters to use when creating the linked server.  This is a client machine and THEY don't want to install the client access drivers on the machine.  There are numerous articles out there indicating that people had successfully used the DB2OLEDB provider to connect to an AS400, just not very much documentation on actually setting up the connection.
ASKER CERTIFIED SOLUTION
chapmandew

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
See how we're fighting big data
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
SOLUTION
Log in to continue reading
Log In
Sign up - Free for 7 days
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
ASKER
superthumper

I never did get the DB2OLEDB provider to connect.  I ended up going a different route using the ibm provider - lame solution but needed to get the job done
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
Member_2_276102

superthumper:

Was it SQL 2005 Enterprise (or Developer) edition? Or was it Standard?

I have seen claims from MS engineers that MS DB2OLEDB _can_ work in Standard, but I have never seen one say how nor have I seen a comment from anyone that it did. The comments I saw for MS engineers weren't particularly useful.

I wish I had useful info to pass on. It just doesn't seem to be reasonably available.

Tom
ASKER
superthumper

It was Enterprise.

That was the problem I found with that provider - there were no useful instructions.