The magic you are looking for is called AnyNet. AnyNet encapsulates the
SNA packets inside TCP/IP packets. This way you can maintain your
network as all TCP/IP, including routing data, but still have the SNA
functionality you desire, i.e. device names.

AnyNet is a little bit slower than TCP/IP alone, but it probably won't
be noticed by a user. The only place it might really be noticed is
during a file download.

If you are using an Ethernet LAN, there is a change that needs to be
made to the LAN line description on the 400. I'm not sure what the
setting is, but I know it has to do with maximum packet size. If I
recall correctly, this has been documented fairly well in V4R1, but I'm
not sure about the earlier releases. Anybody else have that info?

Good luck!

David Boring
Systems Engineer
MCI Systemhouse
Direct: (562) 809-5460

>Date: Wed, 10 Dec 97 15:11:00 PST
>From: "Goins, Kirk      : CO IR" <KGoins@EMAIL.LHS.ORG>
>Subject: TCP/IP and NAMED Devices
>Does V3R2 TCP/IP support named devices? In many of our applications required 
>that we route data to a specific device by name. That name is setup in a 
>table(s). So getting a new device(qpadevxxxx) etc everytime you won't work. 
>Can we do this with 3.2? or is it only on the RISC versions?
>Kirk Goins - Systems Administrator
>Legacy Health Systems
>Portland, Or 
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "".
| To unsubscribe from this list send email to
| Questions should be directed to the list owner/operator:

This thread ...


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

This mailing list archive is Copyright 1997-2019 by 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].