IBM Systems Network Architecture

Systems Network Architecture (SNA) is IBM's proprietary networking architecture, created in 1974.[1] It is a complete protocol stack for interconnecting computers and their resources. SNA describes formats and protocols and is, in itself, not a piece of software. The implementation of SNA takes the form of various communications packages, most notably Virtual Telecommunications Access Method (VTAM), the mainframe software package for SNA communications.

History

SNA was made public as part of IBM's "Advanced Function for Communications" announcement in September, 1974, which included the implementation of the SNA/SDLC (Synchronous Data Link Control) protocols on new communications products:

They were supported by IBM 3704/3705 communication controllers and their Network Control Program, and by System/370 and their VTAM and other software such as CICS and IMS. This announcement was followed by another announcement in July, 1975, which introduced the IBM 3760 data entry station, the IBM 3790 communication system, and the new models of the IBM 3270 display system.

SNA was mainly designed by the IBM Systems Development Division laboratory in Research Triangle Park, North Carolina, USA, helped by other laboratories that implemented SNA/SDLC. The details were later made public by IBM's System Reference Library manuals and IBM Systems Journal.

SNA is still used extensively in banks and other financial transaction networks, as well as in many government agencies. While IBM is still providing support for SNA, one of the primary pieces of hardware, the 3745/3746 communications controller, has been withdrawn from the market by IBM. There are an estimated 20,000 of these controllers installed however, and IBM continues to provide hardware maintenance service and microcode features to support users. A robust market of smaller companies continues to provide the 3745/3746, features, parts and service. VTAM is also supported by IBM, as is the IBM Network Control Program (NCP) required by the 3745/3746 controllers.

In 2008 an IBM publication said:

with the popularity and growth of TCP/IP, SNA is changing from being a true network architecture to being what could be termed an "application and application access architecture." In other words, there are many applications that still need to communicate in SNA, but the required SNA protocols are carried over the network by IP.[2]

Objectives of SNA

IBM in the mid-1970s saw itself mainly as a hardware vendor and hence all its innovations in that period aimed to increase hardware sales. SNA's objective was to reduce the costs of operating large numbers of terminals and thus induce customers to develop or expand interactive terminal-based systems as opposed to batch systems. An expansion of interactive terminal-based systems would increase sales of terminals and more importantly of mainframe computers and peripherals - partly because of the simple increase in the volume of work done by the systems and partly because interactive processing requires more computing power per transaction than batch processing.

Hence SNA aimed to reduce the main non-computer costs and other difficulties in operating large networks using earlier communications protocols. The difficulties included:

As a result, running a large number of terminals required a lot more communications lines than the number required today, especially if different types of terminals needed to be supported, or the users wanted to use different types of applications (.e.g. under CICS or TSO) from the same location. In purely financial terms SNA's objectives were to increase customers' spending on terminal-based systems and at the same time to increase IBM's share of that spending, mainly at the expense of the telecommunications companies.

SNA also aimed to overcome a limitation of the architecture which IBM's System/370 mainframes inherited from System/360. Each CPU could connect to at most 16 I/O channels[3] and each channel could handle up to 256 peripherals - i.e. there was a maximum of 4096 peripherals per CPU. At the time when SNA was designed, each communications line counted as a peripheral. Thus the number of terminals with which powerful mainframes could otherwise communicate was limited.

Principal components and technologies

Improvements in computer component technology made it feasible to build terminals that included more powerful communications cards which could operate a single standard communications protocol rather than a very stripped-down protocol which suited only a specific type of terminal. As a result, several multi-layer communications protocols were proposed in the 1970s, of which IBM's SNA and ITU-T's X.25 became dominant later.

The most important elements of SNA include:

Remote terminals (i.e. those connected to the mainframe by telephone lines) and 3705 communications processors would have SDLC-capable communications cards.
This is the precursor of the so called "packet communication" that eventually evolved into today's TCP/IP technology. SDLC itself evolved into HDLC,[6] one of the base technologies for dedicated telecommunication circuits.

Advantages and disadvantages

SNA removed link control from the application program and placed it in the NCP. This had the following advantages and disadvantages:

Advantages

Disadvantages

Network Addressable Units

Network Addressable Units in a SNA network are any components that can be assigned an address and can send and receive information. They are distinguished further as follows:

Logical Unit (LU)

SNA essentially offers transparent communication: equipment specifics that do not impose any constraints onto LU-LU communication. But eventually it serves a purpose to make a distinction between LU types, as the application must take the functionality of the terminal equipment into account (e.g. screen sizes and layout).

Within SNA there are three types of data stream to connect local display terminals and printers; there is SNA Character String (SCS), used for LU1 terminals and for logging on to an SNA network with Unformatted System Services (USS), there is the 3270 data stream mainly used by mainframes such as the System/370 and successors, including the zSeries family, and the 5250 data stream mainly used by minicomputers/servers such as the System/34, System/36, System/38, and AS/400 and its successors, including System i and IBM Power Systems running IBM i.

SNA defines several kinds of devices, called Logical Unit types:[11]

The primary ones in use are LU1, LU2, and LU6.2 (an advanced protocol for application to application conversations).

Physical Unit (PU)

The term 37xx refers to IBM's family of SNA communications controllers. The 3745 supports up to eight high-speed T1 circuits, the 3725 is a large-scale node and front-end processor for a host, and the 3720 is a remote node that functions as a concentrator and router.

SNA over IP

As mainframe-based entities looked for alternatives to their 37XX-based networks, IBM partnered with Cisco in the mid-1990s and together they developed Data Link Switching, or DLSw. DLSw encapsulates SNA packets into IP datagrams, allowing sessions to flow over an IP network. The actual encapsulation and decapsulation takes place in Cisco routers at each end of a DLSw peer connection. At the local, or mainframe site, the router uses Token Ring topology to connect natively to VTAM. At the remote (user) end of the connection, a PU type 2 emulator (such as an SNA gateway server) connects to the peer router via the router's LAN interface. End user terminals are typically PCs with 3270 emulation software that is defined to the SNA gateway. The VTAM/NCP PU type 2 definition becomes a Switched Major Node that can be local to VTAM (without an NCP), and a "Line" connection can be defined using various possible solutions (such as a Token Ring interface on the 3745, a 3172 Lan Channel Station, or a Cisco ESCON-compatible Channel Interface Processor).

Competitors

The proprietary networking architecture for Honeywell Bull mainframes is Distributed Systems Architecture (DSA). Communications package for DSA is VIP. Like SNA, DSA is also no longer supported for client access. Bull mainframes are fitted with Mainway for translating DSA to TCP/IP and VIP devices are replaced by TNVIP Terminal Emulations (GLink, Winsurf). GCOS 8 supports TNVIP SE over TCP/IP. Other architectures are Unisys – formerly Univac – Distributed Computing Architecture (DCA) and – formerly Burroughs – Burroughs Network Architecture (BNA), both largely obsolete by 2012, and the International Computers Limited (ICL) Information Processing Architecture (IPA). DECnet is a suite of network protocols created by Digital Equipment Corporation, originally released in 1975 to connect two PDP-11 minicomputers. It evolved into one of the first peer-to-peer network architectures, thus transforming DEC into a networking powerhouse in the 1980s.

SNA initially aimed at competing with ISO's Open Systems Interconnection, which was an attempt to create a vendor-neutral network architecture that failed due to the problems of "design by committee". OSI systems are very complex, and the many parties involved required extensive flexibilities that hurt the interoperability of OSI systems, which was the prime objective to start with.

After TCP/IP for many years was not considered a serious alternative due to its "nerdy" image, in the 1990s it was discovered as a very attractive alternative: a truly vendor-neutral alternative that fosters true interoperability due to its flexible RFC process of defining standards. TCP/IP is elegant and simple, in contrast to the former network architectures. IBM SNA "APPN", a later development, was in particular extremely complex, ironically with the purpose of making life simpler.

TN3270 (Telnet 3270) is a TCP/IP Telnet variant that supports direct client-server connections to the mainframe using a TN3270 server on the mainframe, and a TN3270 emulation package on the PC at the end user site. This protocol allows existing VTAM applications (CICS, TSO) to run with little or no change from traditional SNA by supportng traditional 3270 terminal protocol over the TCP/IP session. This protocol is widely used to replace legacy SNA connectivity more than DLSw and other SNA replacement technologies.

See also

Notes

  1. (Schatt 1991, p. 227).
  2. IBM Corporation (2008). Networking on z/OS (PDF). p. 31.
  3. devices that acted as DMA controllers for control units, which in turn attached peripherals such as tape and disk drives, printers, card-readers
  4. (Pooch 1983, p. 310).
  5. (Pooch 1983, p. 313).
  6. (Friend 1988, p. 191).
  7. IBM Systems Network Architecture and APPN PU2.1 References Guides
  8. IBM Corporation. "z/OS Communications Server: SNA Network Implementation Guide". IBM Knowledge Center. Retrieved on 3 October 2015.
  9. IBM Corporation. "z/OS Communications Server: SNA Network Implementation Guide". IBM Knowledge Center. Retrieved on 3 October 2015.
  10. IBM Corporation. "z/OS Communications Server: SNA Network Implementation Guide". IBM Knowledge Center. Retrieved on 3 October 2015.
  11. (Schatt 1991, p. 229).
  12. Microsoft. "Physical Unit (PU)". Retrieved September 7, 2012.

References

External links

This article is issued from Wikipedia - version of the Sunday, April 17, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.