Connecting to AS400 across WAN?

[Peter A. Schott]

I'm trying to set up an HIS server to access our AS400 server across a WAN
link. We currently use Rumba to access the AS400 using TCP/IP. I probably
don't understand the whole concept, but I figured that I would be able to set
up a link to the server using that TCP/IP address and similar configuration
information. Is this possible or does the HIS server have to be installed on
the same subnet as the AS400?

I'd appreciate the help. I'm pretty new to this and we need to find another
way to access the server because Rumba can't work when you try to use it
through a service.

Thanks.

-Pete Schott

[Contention Loser]

I guess the question is which of the features are you trying to use. Many of
the features can work directly over TCP/IP such as COMTI, the data
providers, etc, etc...

The gateway piece, however, only works over SNA so you'll either have to
have it on the same subnet or bridge DLC accross your WAN (not really a good
option). Most people put the server on the same subnet and then have the
clients out on the WAN which can connect over TCP/IP to the server. Or you
can have an HIS server in the branch office connect to a central HIS server
over TCP/IP. So there are a couple of different ways to set this up.

What functionality of HIS are you trying to use specifically and then I
could give you more details...

CL

"Peter A. Schott" <psc...@firstcityfunding.com> wrote in message
news:m6kibtcgjk1j30i9u...@4ax.com...

[Peter A. Schott]

We're mainly trying to get remote access via the OLEDB driver for AS400.
Unfortunately, this branch never heard of DB2 or any other real database
platform, making it really difficult to tie in to our servers. We tried the
Rumba ODBC driver, but that requires an interactive session from what I can
tell. We want to be able to pull the data across without anyone being logged
in, meaning Rumba is out.

I kind of figured that the answer was going to be putting it on the same
subnet, but was hoping that we would have to seeing that Rumba communicates
using TCP/IP. If there's any way to set up the server so that an OLEDB
connection can be made without having to install the HIS server at the site,
that would be great. Our sites are too far apart to make that easy.

Thanks.

-Pete Schott

[Contention Loser]

Yes, the OLE DB Provider for DB2 and the OLE DB Provider for AS/400 and VSAM
(both of which connect to AS/400's, but are for different data types) can
both connect directly over TCP/IP to the AS/400, so you can put it anywhere
on your network you like as long as it has TCP/IP access to the host.

If it's a server, than you'll have to install the HIS server package, but
just install the data integration stuff. You don't need the sna application
support if you're just using the OLE DB Providers.

CL

"Peter A. Schott" <psc...@firstcityfunding.com> wrote in message

news:hf0kbt0frieu4i55p...@4ax.com...

[Peter A. Schott]

Well, I tried that, but was unable to get it to work - parameters incorrect or
something along those lines. It looks like I need to create one of the UDL
files to access the server, but when I try that I am never able to get it to
connect.

Am I thinking along the correct lines here or am I way off base? I looked
through the docs, but really can't find anything that looks worthwhile as far
as creating this connection.

Do I need to set up a server to allow clients to use OLEDB? I couldn't manage
to get the setup right there, either. I'm going through the online help, but
I'm drawing blanks everywhere so far.

I really appreciate your help. It seems like these groups are pretty dead
except for these posts.

[Contention Loser]

If it's direct TCP/IP then you don't need a server, just the OLE DB
Provider. You would have to post the error message for me to try and be of
more help as to why it's not working.

One general tip is that you could get a portping utility (MS finally decided
to include one on the new HIS resource kit CD) and make sure you can ping
the IP address and port number that you configured for the provider. At
least you'd know that TCP/IP was working.

Then I would say you would want to make sure the correct listeners are
running on the AS/400 system. See the following KB article:

Q246706 Errors Generated if TCP/IP DDM Server on AS/400 Not Started
http://support.microsoft.com/support/kb/articles/q246/7/06.asp

Also, the RUMBA driver might talk to a different listener on the host, so
just because it's working doesn't mean the right stuff is running for the
Microsoft OLE DB Providers to work. (Also, RUMBA has a couple of different
flavors of ODBC drivers)

After that, I'd have to see a specific error to know any more.

And yes, it is a bit lonely up here on these newsgroups isn't it? Also, if
anyone knows of any other SNA related newsgroups, please let me know...

CL

"Peter A. Schott" <psc...@firstcityfunding.com> wrote in message

news:33ekbtgs2qe16uoj4...@4ax.com...

[Peter A. Schott]

Okay,
I just installed the client piece on my system and tried to configure a
TCP/IP connection to the other side. No luck there, it wants to browse SNA
domains and similar. It tries to do that twice each time I try to connect
from the UDL file and then quits.

Never mind, I figured out what was the above - now I get a new error:

"The partner LU does not recognize the TP name."

I started up the terminal emulation (5250 client), plugged in the TCP/IP
address, and went straight in. When I try to use the UDL, I get errors and
I'm just not sure where to go from here. Any ideas? This seems like an AS400
config thing now, but I really don't know for sure.

Thanks for all of your help. I really appreciate it.