Re: DB2/390 as a linked server in a MS SQL Server
January 8, 2002 01:20 PM
(in response to Luciano Jardim)
I have used a linked server from SQL Server to DB2 OS390 (V5) for
purposes. If you go to Enterprise Manager, expand the server,
security, then expand linked servers. Right click on linked
click new linked server. Make the linked server name the LOCATION
DB2 (in our system this is the LOCATION parameter used by
look in the MSTR job and do a find on LOCATION to get the value).
the General tab, enter in the ODBC name (defined as a data source
Connect) in the data source field and sysibm in the catalog field.
the Security tab enter a mainframe userid and password under "be
this security context"). Under the server options, check the data
box. Click OK to add the linked server.
If you click on the linked server name, you will see a list of the
and views on OS390.
Assuming all that works, here is the strange part. The only query I
get to work is using the OPENQUERY syntax:
select * from openquery(, 'select * from <db2
AND I also ran into conversion problems with the OLE interface, so
select from sysibm.systables for example you will see a conversion
Because of the restrictions, I abandoned this method of accessing
YMMV, standard disclaimers apply, use at your own risk, yadda yadda
From: Jardim, Luciano [mailto:[login to unmask email]
Sent: Tuesday, January 08, 2002 12:53 PM
To: [login to unmask email]
Subject: DB2/390 as a linked server in a MS SQL Server
Has anyone successfully defined a DB2/390 as a linked server in a
Server using DB2 Connect? I am having problems to determine the
connection string and the necessary setup in the DB2 Connect.
I have DB2/390 V6, DB2 Connect V7, and MS SQL Server 2000.
Any help is very welcome.
[login to unmask email]