3 - Implementing TCP/IP in an SNA Environment

Abstract

This chapter examines the implementation of TCP/IP in an SNA environment. The need to communicate is very dynamic and often cannot be predefined. Technology is moving so swiftly and requires such large R&D investments that technology companies must specialize in only one or a few areas if they hope to compete. Systems Network Architecture, or SNA, was announced in 1974 as a way to link IBM host computers, communication equipment, and peripheral devices such as terminals and printers into comprehensive, efficient, stable, and secure computer networks. While Transmission Control Protocol/Internet Protocol, or TCP/IP was developed by a joint effort between several agencies of the U.S. government joined with major universities and corporate researchers. The TCP/IP protocol provided a relatively simple means to network computers and devices from various vendors. There is not one industry trend that can be highlighted as the implementation strategy of choice. Often, implementation decisions regarding the TCP/IP internet are driven by the investment in, and architecture of, the existing SNA network. Also, many companies find themselves with dual SNA and TCP/IP networks; this is usually because of history and not intentional design. Corporations inevitably investigate the possibility of consolidating traffic from both networks onto one physical network with peer characteristics. As companies move toward integrating SNA and TCP/IP networks, network management is a key issue.