RE: Connecting to AS400 from MS SQL Enterprise Manager

Thanks, that did it. For a while I was getting some strange messages, but it 
was because I had set naming to *SYS - have to use *SQL.

And timestamp fields will cause the whole thing to abort.

I also got this to work using the IBMDASQL OLEDB provider - and that will 
handle timestamps. All I specified was that provider for Provider name, the IP 
address of the iSeries in question, and  the security tab to use current 
context. Nice.
-------------- Original message -------------- 

> What that means is 
> 
> Systemname.serialnumber.libiary.file 
> 
> So if you have a system that you can connect to by typing 
> 
> Telnet Vernsiseries 
> 
> And if has the serial number S10952MP 
> 
> And your library is sysibm 
> 
> And your file is sysdummy1 
> 
> Then you would enter 
> 
> Vernsiseries.s10952mp.sysibm.sysdummy1 
> 
> -----Original Message----- 
> From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of 
> vhamberg@xxxxxxxxxxx 
> Sent: Friday, September 30, 2005 1:47 PM 
> To: Midrange Systems Technical Discussion 
> Subject: Re: Connecting to AS400 from MS SQL Enterprise Manager 
> 
> Okay, I have a linked server now - can I execute SELECT statements in 
> Query Analyzer against this? What is the syntax - I admit freely to 
> being a raw newbie in SQL Server - almost. I've looked at the help and 
> see that a 4-part name is needed 
> 
> provider.catalog.schema.object_name 
> 
> What do I put in each place? 
> 
> Thanks 
> Vern