IBM Systems Network Architecture

From Wikipedia, the free encyclopedia

Systems Network Architecture (SNA) is IBM's proprietary networking architecture created in 1974. It is a complete protocol stack for interconnecting computers and their resources. SNA describes the protocol and is, in itself, not actually a program. The implementation of SNA takes the form of various communications packages, most notably VTAM which is the mainframe package for SNA communcations. 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 marketing by the IBM Corporation. However, there are an estimated 20,000 of these controllers installed 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. The VTAM telecommunications access method is also supported by IBM, as is the IBM Network Control Program (NCP) required by the 3745/3746 controllers.

1 Advantages and Disadvantages
- 1.1 Advantages
- 1.2 Disadvantages
2 Logical Unit Types
3 External links

[edit] Advantages and Disadvantages

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

[edit] Advantages

Localization of problems in the telecommunications network was easier because a relatively small amount of software actually dealt with communication links. There was a single error reporting system.
Adding communication capability to an application program was much easier because the formidable area of link control software which typically requires interrupt processors and software timers was relegated to system software and NCP.

[edit] Disadvantages

Connection to non-SNA networks was difficult. An application which needed access to some communication scheme which was not supported in the current version of SNA faced obstacles. Before IBM included X.25 support (NPSI) in SNA, connecting to an X.25 network would have been awkward. Conversion between X.25 and SNA protocols could have been provided either by NCP software modifications or by an external protocol converter.

At first glance, SNA networks appear to be very expensive in comparison to TCP/IP networks. For small networks, this may be true, but as the complexity of a large routed network grows, the SNA structure provides a cheaper path. [Evidence??? I dont belive this nor have I experienced that case]

[edit] Logical Unit Types

SNA defines several kinds of devices, identifying each group with a Logical Unit grouping. LU0 provides for undefined devices, or build your own protocol. LU1 devices are printers. LU2 devices are dumb terminals. LU3 devices are printers using 3270 protocols. LU4 devices are batch terminals. LU5 has never been defined. LU6 provides for protocols between two applications. LU7 provides for sessions with 5250 terminals. The primary ones in use are LU1, LU2, and LU6.2 (an advanced protocol for application to application conversations).

Within SNA there are two types of datastream to connect local terminals and printers; there is the 3270 datastream mainly used by mainframes (zSeries family) and the 5250 datastream mainly used by minicomputers/servers such as the S/36, S/38, and AS/400 (now the iSeries).

Starting from version 5.2 of OS/400, SNA for client-access is no longer supported.

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.