 |
| AS/400 Solutions >Twinax Connectivity > SNA Gateways vs TCP/IP Gateways |
|
 |
|
|
| |
Are you sure you need an SNA Gateway? We think we have a better solution for you.
Here are the Pros & Cons of MPTN (AnyNet) vs TCP IP...
|
| |
History of AnyNet |
| |
AnyNet implements the Multi Protocol Transport Networking (MPTN) architecture, introduced by IBM (Raleigh, NC) in 1992. AnyNet enables communication protocols such as SNA to connect across various other network types such as: SNA (APPC) over TCP/IP; SNA (APPC) over IPX; and more. It was first supported in OS/400 V3R1.
SNA is not a routable protocol, but when used with AnyNet remote users were able to use standard TCP/IP or IPX routers to connect to AS/400s and 3270 IBM Systems. NetSoft, with their NS/Router for AS/400, was one of the first manufacturers to use this method. |
| |
|
| |
Problem Areas with AnyNet |
| |
As users started to adopt AnyNet, flaws began to appear, particularly when large amounts of data
needed to be transported. Typical problems included disconnecting sessions and slow performance. These problems were not readily apparent on local networks; they were much more prevalent when the timing between the host and device is delayed. In recent tests we tried to establish a
connection across the Internet. We were able to get a session started using a PC with the NS/Router, however within three minutes of working with this session it disconnected. We also tried connecting with a remote controller, which used the same protocol. We were able to vary on the
controller, however the terminals on the controller never established a connection. |
| |
|
| |
TCP/IP Makes its Entrance |
| |
In recent years IBM has focused their development on TN5250. With the arrival of V4R2 (and later
PTFs to support older versions) IBM supported TN5250e and TN3270e. This enhanced TCP/IP support enabled the AS/400 and 3270 hosts to support device naming and SCS printer support. For the first time, users could really take advantage of native TCP/IP support on these hosts. IPDS was also supported directly with TCP/IP using PPD/PPR (a special protocol developed for this specific purpose). Recent versions of Client Access (Client Access Express) contain support for native TCP/IP only, providing proof that IBM’s direction is to provide better support for native TCP/IP on these host computers. |
| |
|
| |
Advantages of TCP/IP |
| |
Because TN5250 and TN3270 use native support on the system, they do not require as many CPU
cycles to make use of it. TN5250e and TN3270e do not have the timing limitations that AnyNet has, therefore these protocols can be used over the Internet with no problem. IBM has realized this and that is one of the reasons that Client Access Express supports SSL encryption, to enable users who want to connect using the Internet a way to do so without encountering security issues. Recent tests show that IPDS printing takes three times the number of TCP/IP packets to print the same document
via AnyNet than via native TCP/IP. Imagine the effect on the performance of a 56K frame relay circuit supporting a number of IPDS printers using AnyNet! |
| |
|
| |
Conclusion |
| |
Since the introduction of AnyNet in 1992 we have seen desktops adopt and then abandon AnyNet in
favor of TN5250e. Isn’t it logical to expect that remote controllers will follow suit? IBM, Perle and NLynx manufactured remote controllers that use AnyNet. IBM withdrew its 5494 controller at the end of 1999, and now both Perle and NLynx are developing TN5250 controllers of their own. BOS
clearly leads the field with its e-Twin@ x Controller, since it is based on the very stable and BOSâNOVA TCP/IP TN5250e engine, which has been installed and working on hundreds well-tested of thousands PCs during the last three years. For experience and state-of-the-art technology, choose BOScom. |
| |
|
| |
For more information about BOScom's e-Twin@x Controller, visit
www.e-twinaxcontroller.com. |
| |
|
| |
|
