SNA and SNA/IP implementation on the mainframe

Networking on z/OS

SNA and SNA/IP implementation on the mainframe

Networking on z/OS

Systems Network Architecture (SNA) is a proprietary network architecture developed by IBM.

This section examines IBM's System Network Architecture, including its evolution and its current integration into IP networks.

Systems Network Architecture - basics and implementation
An SNA network implements the IBM proprietary networking architecture. Subarea networking carries out a hierarchical network paradigm. The information about the network resources and the definitions are stored in the mainframe that is located at the top of the hierarchy. The hierarchical structure of the network follows the organizational structure of many enterprises and that's one of the reasons that SNA was accepted and implemented by many enterprises.
SNA Advanced Peer-to-Peer Networking (APPN)
APPN is dynamic in nature and reduces the amount of predefinition required in an SNA subarea network.
SNA/IP implementation
Consolidating SNA onto IP is not a simple task. Each set of SNA components and applications should be evaluated on its own merits, and a solution should be found that best suits the requirements. In some cases a solution is to replace an application or device; in other cases it is to use data link switching (DLSw), SNA switching services (SNASw), branch extender (BEX), Enterprise Extender, or a combination of these.
TN3270 Enhanced
The TN3270E protocol represents the evolution of SNA as it converged into the world of TCP/IP. It is the primary method of connecting end users to mainframe computers. It consists of a character-based data stream. TN3270E connectivity is handled on the mainframe by the TN3270E server. The TN3270E server converts a TN3270E TCP/IP connection to an SNA session. The terminal LU of the SNA session is emulated so that the SNA application functions as though it were connected to a non-programmable 3270 terminal.

Notices | Terms of use | Support | Contact z/OS