Sign up for the ITPro Today newsletter
Stay on top of the IT universe with commentary, news analysis, how-to's, and tips delivered to your inbox daily.
SNA Server 2.11
To the feature set that is already provided, SNA Server release 2.11 has seven add-ons.
Michael Otey
August 31, 1995
1 Min Read
SNA Server 2.11
At the March 13th SNA Server conference, Microsoft announced the next release of SNA Server. Release 2.11 is expected to ship this summer. It's more an evolutionary than a revolutionary step. To the feature set that's already provided, SNA Server release 2.11 adds:
Support for Windows NT 3.51 (and the PowerPC): Keeps SNA Server current with the latest NT Server network operating system and adds support for the new PowerPC systems.
Support for a twinaxial connection to the AS/400: Allows SNA Server to be used with AS/400s that do not currently support a LAN attachment. The twinaxial connection runs at about 1MB/second and supports 512 sessions/card. Each SNA Server system can suppport two twinaxial adapter cards.
Direct support for the EHNAPPC API: Allows existing Windows applications that conform to the EHNAPPC API specs to run unchanged without additional middleware. (EHNAPPC is an IBM API used to facilitiate Windows-to-AS/400 communications. It provides a subset of APPC functionality. By including it with SNA Server, Microsoft enables client PCs to run ODBC and access AS/400 databases.)
Full support for CA/400 shared folders: Enhances the limited support.
A one-license copy of StarWare's ODBC driver: Enables access to host data through the SNA Server gateway. Microsoft is bundling a one-license copy of the StarWare ODBC driver with each copy of SNA Server. This driver accesses host data through DRDA (Distributed Relational Database Architecture). Additional licenses are available from StarWare.
RAS (Remote Access Service) over SNA: Enables an SNA Server system to be remotely administered across an SNA network.
A new concurrent licensing option: Allows you to license SNA Server by the number of active users instead of on a per-client basis.
About the Author(s)
You May Also Like
