Microsoft SNA Server
SNA Server offers broad API support to all popular desktop operating systems, including MS-DOS, Windows for Workgroups, Windows 95, Windows NT, and OS/2.
Figure 11.2 How SNA Server connects clients to host computers - MS-DOS-based desktops can connect to AS/400s via SNA Server using IBM PC Support/400 or third-party emulators over IPX/SPX, NetBEUI, and TCP/IP. Application programming interfaces include APPC and ODBC/DRDA. EHLLAPI is supported by third-party emulators.
- Windows for Workgroups clients are supported using IPX/SPX, TCP/IP, Banyan VINES IP, and NetBEUI. AS/400 connectivity via SNA Server is fully compatible with EHNAPPC and supports the full range of Client Access/400 functions, including shared folders, virtual print, and file transfer. The SNA Server SDK includes APIs for APPC and CPI-C. EHLLAPI is supported by third-party emulators. Each copy of SNA Server includes a single license to a Windows ODBC/DRDA driver for providing host data access to IBM DB2/400.
- Windows 95 and Windows NT clients can connect to AS/400s via SNA Server using third-party products over IPX/SPX, TCP/IP, Banyan VINES IP, and NetBEUI. Supported APIs include APPC, CPI-C, and AFTP. The Win32 SNA client comes with an ODBC/DRDA driver. EHLLAPI is supported by third-party emulators. Additionally, the SNA client for Windows NT supports 16-bit Windows-based applications through a thunking layer that maps the 16-bit SNA APIs to native 32-bit SNA APIs.
- OS/2 desktops can connect to AS/400s via SNA Server using third-party products over NetBEUI and TCP/IP.
Lesson Summary
Microsoft System Network Architecture APIs create a standard interface between PC networks and IBM mainframes and AS/400s. The SNA APIs standardize a corporation's method for host connectivity and eliminate compatibility issues.
SNA Server offers API support to popular desktop operating systems, including MS-DOS, Windows for Workgroups, Windows 95, Windows NT, and OS/2.