Copyright: Installation Guide
Citation: Installation Guide


Microsoft SNA Server Master Table of Contents
Microsoft SNA Server

Master Table of Contents

	SNA Server Enhancements Guide
	SNA Server Installation Guide
	SNA Server Administration Guide
	Managing Microsoft SNA Server
	SNA Server Planning Guide
	SNA Server TN3270 Service
	3270/5250 Applet User's Guide
	SNA Server Reference
	SNA Server Glossary
	APPC Programmer's Guide
	CPI-C Programmer's Guide
	LUA Programmer's Guide
	SNA Device Interface Specification
	3270 Emulator Interface Specification
	Comprehensive Index


Installation Guide Contents
Microsoft SNA Server

Installation Guide

Contents

Before You Begin

Microsoft Support Services

Accessibility for People with Disabilities

Chapter 1	Overview

Chapter 2	Installing SNA Servers

Chapter 3	Installing SNA Server Clients

Chapter 4	Upgrading to SNA Server Version 2.1

List of Figures


Installation Guide Contents
Microsoft SNA Server

Installation Guide

Contents

Before You Begin

How to Use This Guide

Document Conventions

Common Abbreviations

Finding Further Information

Microsoft Support Services

Accessibility for People with Disabilities

Chapter 1	Overview

Chapter 2	Installing SNA Servers

Chapter 3	Installing SNA Server Clients

Chapter 4	Upgrading to SNA Server Version 2.1

List of Figures


Installation Guide Contents
Microsoft SNA Server

Installation Guide

Contents

Before You Begin

Microsoft Support Services

The Microsoft Support Network

Product Support Within the United States and Canada

Other Microsoft Services

Product Support Worldwide

Accessibility for People with Disabilities

Chapter 1	Overview

Chapter 2	Installing SNA Servers

Chapter 3	Installing SNA Server Clients

Chapter 4	Upgrading to SNA Server Version 2.1

List of Figures


Installation Guide Contents
Microsoft SNA Server

Installation Guide

Contents

Before You Begin

Microsoft Support Services

Accessibility for People with Disabilities

Microsoft Services for People Who Are Deaf or Hard-of-Hearing

Access Pack for Microsoft Windows NT

Keyboard Layouts for Single-Handed Users

Microsoft Documentation on Audiocassettes, Floppy Disks, and CD-ROMs

Products for People Who Are Blind or Have Low Vision

Customizing Windows NT

Getting More Information

Chapter 1	Overview

Chapter 2	Installing SNA Servers

Chapter 3	Installing SNA Server Clients

Chapter 4	Upgrading to SNA Server Version 2.1

List of Figures


Installation Guide Contents
Microsoft SNA Server

Installation Guide

Contents

Before You Begin

Microsoft Support Services

Accessibility for People with Disabilities

Chapter 1	Overview

Overview of SNA Server

New Features with This Release

Contents of the CD

Planning SNA Server Domains

File System Choices and Security

Overview of SNA Server Installation

System Requirements

SNA Server

SNA Server Clients Running Windows NT

SNA Server Clients Running Windows Version 3.x

SNA Server Clients Running MS-DOS

SNA Server Clients Running OS/2

SNA Server Clients on Macintosh Computers

Adapter Support

Windows-Based SNA Support

Chapter 2	Installing SNA Servers

Chapter 3	Installing SNA Server Clients

Chapter 4	Upgrading to SNA Server Version 2.1

List of Figures


Installation Guide Contents
Microsoft SNA Server

Installation Guide

Contents

Before You Begin

Microsoft Support Services

Accessibility for People with Disabilities

Chapter 1	Overview

Chapter 2	Installing SNA Servers

Using SNA Server Setup

Setup Versus SNA Server Admin

Creating a Share for Installing Clients Across the Network

Using Dialog Boxes

SNA Server Components

Components Installed by Setup

Components Available Through Independent Vendors

Twinax and Channel Link Services

Sponsor Connections

File System Choices and Security

Starting the SNA Server Setup Program

Recording Identifying Information

Specifying the Installation Path

Selecting Client/Server Protocols

Specifying the Network Domain Name

Specifying the StreetTalk Group Name on a Banyan VINES Network

Selecting the Server Role

Installing a Link Service

Installing Other Link Services

Configuring a Link Service

Avoiding Interrupt or Address Conflicts Between Adapters

SDLC Adapter Notes

IBM Token Ring Adapter Notes

Configuring a DLC 802.2 Link Service

Installing SNA Servers in an Ethernet LAN with Routers

Configuring an SDLC Link Service

Requirements for Using Server-Stored Numbers

Command String Examples

Notes on the Barr SDLC Link Service

Configuring an X.25 Link Service

Guidelines for Assigning Channel Numbers

Configuring a DFT Link Service

Completing Setup

Installing SNA Servers in an IP Routed Network

Preparing an SNA Server to Support Macintosh Clients

Modifying or Removing SNA Servers

Adding or Removing a Link Service

Changing the Server Role

Changing Client/Server Protocol Selections

Removing SNA Server

Chapter 3	Installing SNA Server Clients

Chapter 4	Upgrading to SNA Server Version 2.1

List of Figures


Installation Guide Contents
Microsoft SNA Server

Installation Guide

Contents

Before You Begin

Microsoft Support Services

Accessibility for People with Disabilities

Chapter 1	Overview

Chapter 2	Installing SNA Servers

Chapter 3	Installing SNA Server Clients

Clients in Relation to the Domain of Servers

Information Needed for Client Setup

Client Installation and the Network

Making Client Installation Available Over the Network

Client Installation from Floppy Disks

Installing Clients

Installing a Windows NT-Based Client

Installing a Client Running Windows Version 3.x

Installing Windows-Based Client Software to Run Locally

Installing Windows-Based Client Software to Run from a Network Share

Removing a Windows-Based Client that Runs from a Network Share

Maximum Network Connections on Clients Using LAN Manager

Installing an MS-DOS  Based Client

PC Support Router Replacement

Using the Default LUs Specified in the PC Support Configuration

PC Support Used with Windows for Workgroups

Installing an OS/2 Client

Modifying Clients

Removing SNA Server Clients

Chapter 4	Upgrading to SNA Server Version 2.1

List of Figures


Installation Guide Contents
Microsoft SNA Server

Installation Guide

Contents

Before You Begin

Microsoft Support Services

Accessibility for People with Disabilities

Chapter 1	Overview

Chapter 2	Installing SNA Servers

Chapter 3	Installing SNA Server Clients

Chapter 4	Upgrading to SNA Server Version 2.1

Upgrading from Comm Server 1.x

Advantages of Upgrading Comm Server 1.x Clients

Steps for Upgrading from Comm Server 1.x

Copying Files for the Comm Server 1.x 3270 Emulator

Using the MS-DOS  Based Comm Server 1.x 3270 Emulator with Client Software

Upgrading from SNA Server Version 2.0

Upgrading a Domain of SNA Servers from Version 2.0

List of Figures


Installation Guide Contents
Microsoft SNA Server

Installation Guide

Contents

Before You Begin

Microsoft Support Services

Accessibility for People with Disabilities

Chapter 1	Overview

Chapter 2	Installing SNA Servers

Chapter 3	Installing SNA Server Clients

Chapter 4	Upgrading to SNA Server Version 2.1

List of Figures

SNA Server Architectural Overview

Centralized Plan

Noncentralized Plan

Installation Path Dialog Box

Select Client/Server Protocols Dialog Box

Network Domain Name Dialog Box

Change SNA Server Role Dialog Box

Link Service Installation Dialog Box

Link Service Import Dialog Box

SNA Server DLC Connection

Link Service Configuration Dialog Box

SNA Server SDLC Link Service

SNA Server X.25 Link Service

SNA Server DFT Link Service

Adapter Base Address Dialog Box

SNA Server Setup Finished Dialog Box

Setup Options Dialog Box

Installation Path Dialog Box

Select Client/Server Protocols Dialog Box

SNA Client Mode Dialog Box

SNA Server Location Dialog Box

Setup Options Dialog Box


Before You Begin
1 of 5

Before You Begin

The Microsoft SNA Server Installation Guide contains instructions for installing Microsoft [image] SNA Server (SNA Server). This guide assumes some background knowledge of both the Microsoft Windows NT [image] operating system and IBM [image] Systems Network Architecture (SNA), as well as a working knowledge of client/server environments.


How to Use This Guide
Before You Begin	2 of 5

How to Use This Guide

This manual contains the following chapters and covers the following topics:

Chapter 1, "Overview"

Provides an overview of SNA Server, introduces the SNA Server Setup program, and describes the system requirements for using SNA Server. Also provides information about planning the domain(s) in which you will install SNA servers.

Chapter 2, "Installing SNA Servers"

Describes how to install SNA servers, and how to install and configure four types of link services: 802.2 (DLC), SDLC, X.25, and DFT. In addition, tells how to modify or remove SNA Server software.

Chapter 3, "Installing SNA Server Clients"

Describes how to install, modify, or remove software for clients using the Windows NT, Windows [image] version 3.x, MS-DOS [image], or IBM OS/2 [image] operating systems.

Chapter 4, "Upgrading to SNA Server Version 2.1"

Describes the process of upgrading from Comm Server 1.x or SNA Server 2.0, and provides procedures for using the MS-DOS –based Comm Server 1.x 3270 emulator through a connection on an SNA server.


Document Conventions
Before You Begin	3 of 5

Document Conventions

Throughout this manual, the following conventions distinguish elements of text.

Convention	Purpose
bold	Indicates syntax items that must be typed exactly as shown.
italic	Indicates variables.
monospace	Represents examples and program code.
SMALL CAPS	Represent return values and key names, such as CTRL.
UPPERCASE	Represents filenames, paths, volumes, array and structure names, values, and conversation states.
[brackets]	Enclose optional items in syntax statements.
{braces}	Enclose required items in syntax statements.
| (vertical bar)	Stands for OR and separates items in syntax statements.
... (ellipsis)	Indicates that the preceding syntax item can be repeated. If a punctuation mark precedes the ellipsis, you must include the punctuation when repeating the item.
X'nnnn'	Indicates hexadecimal digits.


Common Abbreviations
Before You Begin	4 of 5

Common Abbreviations

The following is an alphabetical list of common abbreviations used in this manual.

Abbreviation	Description
API	Application Programming Interface
APPC	Advanced Program-to-Program Communications
ASCII	American Standard Code for Information Interchange
CPI-C	Common Programming Interface for Communications
CSV	Common Service Verb
CTS	Clear to Send
DCA	Digital Communications Associates, Inc.
DFT	distributed function terminal
DLC	data link control
DSR	Data Set Ready
DTR	Data Terminal Ready
EBCDIC	Extended Binary Coded Decimal Interchange Code
K	kilobyte
LAN	local area network
LU	logical unit
LUA	conventional Logical Unit Application programming interface
MB	megabyte
NCP	Network Control Panel
NRZ	nonreturn to zero
NRZI	nonreturn to zero inverted
NUA	Network User Address
PC	personal computer
PU	physical unit
PVC	permanent virtual circuit
QLLC	qualified logical link control
RU	request/response unit
RUI	Request Unit Interface
SAA	System Application Architecture
SAP	service access point
SDLC	Synchronous Data Link Control
SLI	Session Level Interface
SNA	Systems Network Architecture
SVC	switched virtual circuit
TP	transaction program
VTAM	Virtual Telecommunications Access Method
WAN	wide area network


Finding Further Information
Before You Begin	5 of 5

Finding Further Information

For more information about SNA Server, see the following manuals:

Microsoft SNA Server Administration Guide

Microsoft SNA Server Reference

For more information about SNA and about 3270 information display systems, see the following manuals (titles followed by an asterisk [*] are available in the SNA Server Software Development Kit):

Microsoft SNA Server LUA Programmer's Guide*

IBM 3270 Information Display System: 3274 Control Unit Description and Programmer's Guide

IBM 3270 Information Display System: Color and Programmed Symbols

IBM 3270 Information Display System: 3274 Control Unit Display Station: Operator's Guide

IBM Systems Network Architecture: Technical Overview

IBM Systems Network Architecture: Concepts and Products

IBM Advanced Communications Function Products Installation Guide

IBM Installation and Resource Definition

IBM 9370 LAN Token Ring Support

IBM SNA Format and Protocol Reference Manual: Architectural Logic

For background information about LU 6.2, Advanced Program-to-Program Communications (APPC), and/or the Common Programming Interface for Communications (CPI-C), see the following manuals (titles followed by an asterisk [*] are available in the SNA Server Software Development Kit):

Microsoft SNA Server APPC Programmer's Guide*

Microsoft SNA Server CPI-C Programmer's Guide*

IBM Systems Network Architecture: Introduction to APPC

IBM Systems Network Architecture: Transaction Programmer's Reference Manual for LU Type 6.2

IBM SNA: Format and Protocol Reference Manual: Architecture Logic for LU Type 6.2

IBM SNA: Formats

IBM SNA: Technical Overview

IBM SNA: ACF/VTAM Programming for LU Type 6.2


Microsoft Support Services
1 of 4

Microsoft Support Services

If you have a question about Microsoft SNA Server, first look in the product documentation or consult online Help. You can also find late-breaking updates and technical information in the README file that came with the Microsoft SNA Server compact disc. If you cannot find the answer, contact the Microsoft Product Support Services.

Outside the United States and Canada, contact Microsoft Product Support Services at the Microsoft subsidiary office that serves your area. For information about Microsoft subsidiary offices, see “Product Support Worldwide” later in this section.


The Microsoft Support Network
Microsoft Support Services	2 of 4

The Microsoft Support Network

The Microsoft Support Network, where available, offers high-quality technical support options that allow you to get what you need: the right answers right now.

Services vary outside the United States and Canada. The Microsoft Support Network is subject to Microsoft’s then-current prices, terms, and conditions, and is subject to change without notice.


Product Support Within the United States and Canada
Microsoft Support Services	3 of 4

Product Support Within the United States and Canada

In the United States and Canada, the following support options are available through the Microsoft Support Network:

Information Services

No-cost and low-cost electronic information services are available 24 hours a day, 7 days a week, including holidays.

Microsoft FastTips

(800) 9364400 on a touch-tone telephone. Receive automated answers to common technical problems, and access popular articles from the Microsoft Knowledge Base, all delivered by recording or fax.

Microsoft Download Service

Access, via modem, sample programs, device drivers, patches, software updates, and programming aids (1200, 2400, or 9600 baud; no parity; 8 data bits; 1 stop bit). In the United States, call (206) 9366735. In Canada, call (905) 5073022.

Internet

Access the Microsoft Knowledge Base and Software Library. The Microsoft World Wide Web site is located at http://www.microsoft.com. The Microsoft Gopher site is located at gopher.microsoft.com. The Microsoft FTP site is located at ftp.microsoft.com and can be accessed via anonymous logon.

CompuServe [image] and America Online

Access the Microsoft Knowledge Base, the Microsoft Software Library, and participate in MS forums. On CompuServe, at any ! prompt, type go mskb to access the Microsoft Knowledge Base, go msl to access the Microsoft Software Library, and GO Microsoft to access the Microsoft forums. To access the Microsoft Knowledge Base on America Online, type GOTO MICROSOFT in the America Online client application.

Priority Support

The Microsoft Support Network offers priority telephone access to Microsoft support engineers 24 hours a day, 7 days a week, excluding holidays.

In the United States, call (900) 5552100; $150 (U.S.) per incident. Charges appear on your telephone bill.

In the United States, call (800) 9365900, at $150 (U.S.) per incident, billed to your VISA card, MasterCard, or American Express card.

In Canada, call (800) 6687975 for more information.

Text Telephone

Microsoft text telephone (TT/TDD) services are available for the deaf or hard-of-hearing. In the United States, using a TT/TDD modem, dial (206) 6354948 between 6:00 A.M. and 6:00 P.M. Pacific time, Monday through Friday, excluding holidays. In Canada, using a TT/TDD modem, dial (905) 5689641 between 8:00 A.M. and 8:00 P.M. Eastern time, Monday through Friday, excluding holidays.

Other Support Options

The Microsoft Support Network offers annual fee-based support plans. For information, in the United States, call the Microsoft Support Network Sales Group at (800) 9363500 between 6:00 A.M. and 6:00 P.M. Pacific time, Monday through Friday, excluding holidays. In Canada, call (800) 5639048 between 8:30 A.M. and 6:30 P.M. Eastern time, Monday through Friday, excluding holidays. Technical support is not available through these sales numbers.

Other Microsoft Services

Microsoft Authorized Support Centers

Microsoft Authorized Support Centers (ASCs) are a select group of strategic support providers who offer high quality customized support services that span the complete systems life cycle of planning, implementation and maintenance of your multivendor environment. Services include: on-site support, integration and implementation services, help desk services, hardware support, development resources, and others. Choosing an ASC allows you to work with one vendor for all of your technical support and service needs. You can also combine ASC services with your in-house help desk or Microsoft support service option to best fit your information technology support needs.

For more information on the ASC program, in the U.S. call (800) 9363500 between 6:00 A.M. and 6:00 P.M. Pacific time, Monday through Friday, excluding holidays. In Canada, call (800) 5639048 between 8:00 A.M. and 8:00 P.M. Eastern time, Monday through Friday, excluding holidays.

Microsoft Solution Providers Program

Microsoft Solution Providers are independent developers, consultants, and systems analysts that offer fee-based technical training and support, industry knowledge, objective advice, and a range of value-added services to companies of all sizes. Solution Providers work with organizations to help implement computing systems that take advantage of today’s powerful new technologies.

For the name of a Microsoft Solution Provider near you, in the U.S. call (800) 4269400 between 6:30 A.M. and 5:30 P.M. Pacific time, Monday through Friday, excluding holidays. In Canada, call (800) 5639048 between 8:00 A.M. and 8:00 P.M. Eastern time, Monday through Friday, excluding holidays.

Microsoft TechNet

Microsoft TechNet is the front-line resource for fast, complete answers to technical questions on Microsoft systems and desktop products. Information available on TechNet ranges from crucial data on client-server and workgroup computing, systems platforms, and database products, to the latest on support for Microsoft Windows and Macintosh-based applications. As a TechNet user you receive:

Twelve monthly compact discs containing the Microsoft Knowledge Base, Microsoft operating systems product resource kits, customer solutions, key Microsoft conference session notes, and other valuable information.

Twelve monthly supplemental (drivers and patches) compact discs containing the Microsoft Software Library.

A dedicated Microsoft TechNet forum on CompuServe (GO TECHNET)

WinCIM, a Windows-based application for accessing CompuServe

A 20% discount on Microsoft Press books

For more information about Microsoft TechNet, in the United States and Canada, call (800) 3442121, between 7:00 A.M. and 7:00 P.M. Central time, Monday through Friday. Outside the U.S. and Canada, contact your Microsoft Subsidiary, or call (303) 6840914.


Product Product Support Worldwide
Microsoft Support Services	4 of 4

Product Support Worldwide

If you are outside the United States and have a question about a Microsoft product, first:

Consult the documentation and other printed information included with your product.

Check online Help.

Check the README files that come with your product disks. These files provide general information that became available after the books in the product package were published.

Consult electronic options such as CompuServe forums or bulletin boards, if available.

If you cannot find a solution, you can receive information on how to obtain product support by contacting the Microsoft subsidiary office that serves your country.

Calling a Microsoft Subsidiary Office

When you call, you should be at your computer and have the appropriate product documentation at hand. Be prepared to give the following information:

The version number of Microsoft product that you are using.

The type of hardware that you are using, including network hardware, if applicable.

The operating system that you are using.

The exact wording of any messages that appeared on your screen.

A description of what happened and what you were doing when the problem occurred.

A description of how you tried to solve the problem.

If there is no Microsoft office in your country, please contact the establishment from which you purchased your Microsoft product.


Accessibility for People with Disabilities
1 of 8

Accessibility for People with Disabilities

Microsoft is committed to making its products and services easier for everyone to use. This section provides information about the following products and services, which make Microsoft Windows NT and Microsoft SNA Server more accessible for people with disabilities:

Microsoft services for people who are deaf or hard-of-hearing

Access Pack for Microsoft Windows NT, a software utility that makes using Microsoft Windows NT easier for people with motion or hearing disabilities

Keyboard layouts designed for people who type with one hand or a wand

Microsoft software documentation on audiocassettes, floppy disks, and CD-ROMs

Products for people who are blind or have low vision

Hints for customizing Microsoft Windows NT

Other products and services for people with disabilities

Note

The information in this section applies only to users who purchased Windows NT Workstation or Windows NT Server in the United States. If you purchased Windows NT Workstation or Windows NT Server outside the United States, your Windows NT package contains a subsidiary information card listing Microsoft support services telephone numbers and addresses. You can contact your subsidiary to find out whether or not the type of products and services described in this section are available in your area.


Microsoft Services for People Who Are Deaf or Hard-of-Hearing
Accessibility for People with Disabilities	2 of 8

Microsoft Services for People Who Are Deaf or Hard-of-Hearing

Through a text telephone (TT/TDD) service, Microsoft provides people who are deaf or hard-of-hearing with complete access to Microsoft product and customer services.

You can contact the Microsoft Sales and Information Center on a text telephone by dialing (800) 892-5234 between 6:30 a.m. and 5:30 p.m. Pacific time. For technical assistance in the United States, you can contact Microsoft Support Network on a text telephone at (206) 635-4948 between 6:00 A.M. and 6:00 P.M. Pacific time, Monday through Friday, excluding holidays. In Canada, dial (905) 568-9641 between 8:00 A.M. and 8:00 P.M. Eastern time, Monday through Friday, excluding holidays. Microsoft support services are subject to Microsoft prices, terms, and conditions in place at the time the service is used.


Access Pack for Microsoft Windows NT
Accessibility for People with Disabilities	3 of 8

Access Pack for Microsoft Windows NT

Microsoft distributes Access Pack for Microsoft Windows NT, which provides people with motion or hearing disabilities better access to computers running Microsoft Windows NT. Access Pack for Microsoft Windows NT contains several features that:

Allow single-finger typing of SHIFT, CTRL, and ALT key combinations.

Ignore accidental keystrokes.

Adjust the rate at which a character is repeated when you hold down a key, or turn off character repeating entirely.

Prevent extra characters if you unintentionally press a key more than once.

Enable you to control the mouse cursor by using the keyboard.

Enable you to control the computer keyboard and mouse by using an alternate input device.

Provide a visual cue when the computer beeps or makes other sounds.

Access Pack for Microsoft Windows NT is included in the Microsoft Application Note WNO789. If you have a modem, you can download this application note as file WNO789.EXE, which is a self-extracting archive file, from the following network services:

CompuServe

GEnie

Microsoft OnLine

Microsoft Download Service (MSDL), which you can reach by calling (206) 936-MSDL (936-6735) any time except between 1:00 A.M. and 2:30 A.M. Pacific time. Use the following communications settings:

For this setting	Specify
Baud rate	1200, 2400, or 9600
Parity	None
Data bits	8
Stop bits	1
Various user-group bulletin boards (such as the bulletin-board services on the Association of PC User Groups network)

The Internet FTP Server FTP.MICROSOFT.COM in /SOFTLIB/MSLFILES

People within the United States who do not have a modem can order the Access Pack for Microsoft Windows NT on disks by calling the Microsoft Sales and Information Center at (800) 426-9400 (voice) or (800) 892-5234 (text telephone). In Canada, you can call (905) 568-3503 or (905) 568-9641 (text telephone).


Keyboard Layouts for Single-Handed Users
Accessibility for People with Disabilities	4 of 8

Keyboard Layouts for Single-Handed Users

Microsoft distributes Dvorak keyboard layouts that make the most frequently typed characters on a keyboard more accessible to people who have difficulty using the standard “QWERTY” layout. There are three Dvorak layouts: one for two-handed users, one for people who type with their left hand only, and one for people who type with their right hand only. The left-handed or right-handed keyboard layouts can also be used by people who type with a single finger or a wand. You do not need to purchase any special equipment to use these features.

Microsoft Windows NT already supports the two-handed Dvorak layout, which can be useful for coping with or avoiding types of repetitive-motion injuries associated with typing. To get this layout, choose the International option in Control Panel. The two layouts for people who type with one hand are distributed as Microsoft Application Note GA0650. This application note is also contained in file GA0650.ZIP on most network services or GA0650.EXE on the Microsoft Download Service. For instructions on obtaining this application note, see the preceding section, “Access Pack for Microsoft Windows NT.”


Microsoft Documentation on Audiocassettes, Floppy Disks, and CD-ROMs
Accessibility for People with Disabilities	5 of 8

Microsoft Documentation on Audiocassettes, Floppy Disks, and CD-ROMs

People who have difficulty reading or handling printed documentation can obtain most Microsoft publications from Recording for the Blind, Inc. Recording for the Blind distributes these documents to registered members of their distribution service either on audiocassettes or on floppy disks. The Recording for the Blind collection contains more than 80,000 titles, including Microsoft product documentation and books from Microsoft Press. You can contact Recording for the Blind at the following address or phone numbers:

Recording for the Blind, Inc. 20 Roszel Road Princeton, NJ 08540	Phone : Phone outside the U.S.: Fax:	(800) 221-4792  (609) 452-0606  (609) 987-8116
Many of the Windows NT version 3.5 documents are also available on a CD-ROM that comes with the package.


Products for People Who Are Blind or Have Low Vision
Accessibility for People with Disabilities	6 of 8

Products for People Who Are Blind or Have Low Vision

There are products available to help people who are blind or have low vision to use Microsoft Windows NT. For people with low vision, there are screen-enlargement utilities and, for people who cannot use visual information, there are screen readers that provide alternative output by synthesized voice or refreshable Braille displays. In addition, people with low vision can customize the Microsoft Windows NT display to suit their needs.

For more information on the various products available, see “Getting More Information,” later in this section. For more information about customizing Microsoft Windows NT for people with low vision, see the next topic, “Customizing Windows NT.”


Customizing Windows NT
Accessibility for People with Disabilities	7 of 8

Customizing Windows NT

There are many ways you can adjust the appearance and behavior of Microsoft Windows NT to suit varying vision and motor abilities without requiring any additional software or hardware. These include ways to adjust the appearance as well as the behavior of the mouse and keyboard. The specific methods available depend on which version of the operating system you are using. Application notes are available describing the specific methods available for each version of the Windows NT operating system and for the other related Windows operating systems.

See the appropriate application note for information related to customizing your operating system for people with disabilities. For information on obtaining application notes, see “Access Pack for Microsoft Windows NT,” earlier in this section.

Operating system	Application note number
Microsoft Windows 3.0	WW0786
Microsoft Windows 3.1	WW0787
Microsoft Windows for Workgroups 3.1	WG0788
Microsoft Windows NT 3.1 and 3.5	WN0789


Getting More Information
Accessibility for People with Disabilities	8 of 8

Getting More Information

For more information on Microsoft products and services for people with disabilities, contact the Microsoft Sales and Information Center at (800) 426-9400 (voice) or (800) 892-5234 (text telephone).

The Trace R&D Center at the University of Wisconsin–Madison produces a book and a compact disc that describe products that help people with disabilities use computers. The book, titled Trace ResourceBook, provides descriptions and photographs of about 2,000 products. The compact disc, titled CO-NET CD, provides a database of more than 18,000 products and other information for people with disabilities. It is issued twice a year.

You can contact the Trace R&D Center at the following address or telephone numbers:

Trace R&D Center S-151 Waisman Center 1500 Highland Avenue Madison, WI 53705-2280	Voice telephone: Text telephone: Fax:	(608) 263-2309  (608) 263-5408  (608) 262-8848
For general information and recommendations on how computers can help specific people, you should consult a trained evaluator who can best match your needs with the available solutions. An assistive technology program in your area will provide referrals to programs and services that are available to you. To locate the assistive technology program nearest you, you can contact:

National Information System  Center for Developmental  Disabilities Benson Building University of South Carolina Columbia, SC 29208	Voice/text telephone outside South Carolina: Voice/text telephone inside South Carolina: Voice/text telephone outside the U.S.: Fax:	(800) 922-9234, ext. 301  (800) 922-1107   (803) 777-6222  (803) 777-6058


Overview
Chapter 1	1 of 16

Overview

Microsoft [image] SNA Server combines client-server architecture with the power and productivity of the Windows NT [image] Server. By using SNA Server, you can establish connections with remote computers, such as IBM [image] mainframes, AS/400 [image] (s), or other PCs, within an IBM Systems Network Architecture (SNA) network. SNA Server can be used for 3270 terminal emulation, 5250 terminal emulation, APPC, CPI-C, communication using LUA, and/or communication involving downstream systems.


Overview of SNA Server
Overview	2 of 16

Overview of SNA Server

SNA Server allows you to communicate with remote computers from a single computer running the Windows NT operating system. By using SNA Server, you can access mainframes and minicomputers using IBM SNA protocols. SNA is a collection of rules that brings uniformity to communications systems and the ways they interact. These rules define various functions that allow information to be transferred from one computer to another, and presented in a form that is usable by the receiving computer.

SNA Server uses an advanced client-server architecture to distribute the communications processing, maximizing the power of individual computers and the host. Client computers use the local area network (LAN) to connect to one or more SNA servers using standard LAN protocols. The SNA servers provide shared links to host computers using SNA protocols. By carrying the heaviest workloads, SNA servers reduce the storage and processing requirements on client computers.

SNA Server enables you to establish connections with multiple host or peer computers at the same time, using any combination of the following:

802.2: Token Ring or Ethernet connections via IBM 37x5 front-end processors or 3x74 cluster controllers.

Synchronous Data Link Control (SDLC): Leased or switched telephone line connections.

X.25/QLLC: Public or private packet-switched X.25 connections, using qualified logical link control (QLLC).

Distributed function terminal (DFT): Coaxial or twisted-pair connections using IBM 3x74 cluster controllers.

Channel: Connections that provide direct channel attachment to a mainframe.

Twinax: Twinaxial connections to an AS/400.

SNA Server supports most communications adapters, cabling, wiring, modems, and controllers. The following figure gives an overview of the various client and server components in SNA Server architecture.

SNA Server Architectural Overview


New Features with This Release
Overview	3 of 16

New Features with This Release

This version of SNA Server includes:

Increased numbers of clients and sessions supported. As many as 2,000 clients and 10,000 sessions can be supported per server.

Improved performance, both within SNA Server, and when used with Windows NT Server version 3.5. Note that SNA Server version 2.1 can be used with version 3.1 of Windows NT, but the greatest performance gains are seen when used with version 3.5 of Windows NT.

Support for the MIPS [image] platform with server and client software.

Support for the Digital Alpha AXP [image] with server and client software.

Support for native TCP/IP for clients running Windows [image] version 3.x or Windows NT.

Support  for Banyan [image] VINES [image] for clients running MS-DOS [image], Windows version 3.x, or Windows NT.

Support for the AppleTalk [image] for Macintosh [image] clients.

Support for TN3270 servers.

A TN3270 server is available from OpenConnect Systems as an add-on product to SNA Server. For contact information on OpenConnect Systems, see the SNA Server Companion Product Catalog, ISVCATAL.DOC, in the \COLLATRL directory on the SNA Server CD. Updates to this catalog are distributed on the Microsoft TechNet CD and posted on the MSSNA CompuServe [image] forum.

Support for TN3270 servers allows any TN3270 client, such as a UNIX [image] workstation, to connect using the TN3270 protocol to SNA Server, which in turn connects to the host through standard SNA protocols.

A bundled 3270 Applet for MS-DOS – based clients; this applet was developed for Microsoft by Attachmate.

Note that all applets included with SNA Server are licensed for one user per server. This is intended to be an "administrator license only," to be used only for evaluating, administering, and supporting SNA Server. For production use, Microsoft recommends 3270 and 5250 emulators from independent software vendors. For a full list and contact information, see the SNA Server Companion Product Catalog, ISVCATAL.DOC, in the \COLLATRL directory on the SNA Server CD. Updates to this catalog are distributed on the Microsoft TechNet CD and posted on the MSSNA CompuServe forum.

Bundled drivers for a number of third-party SNA adapters.

Support for adapters from Attachmate, Barr Systems, Digital Communications Associates, and Microgate is now included in the product.

Support for Channel-attached and Twinax connections.

Device drivers and link services for these connection types will be available from independent software vendors. For a full list and contact information, see the SNA Server Companion Product Catalog, ISVCATAL.DOC, in the \COLLATRL directory on the SNA Server CD. Updates to this catalog are distributed on the Microsoft TechNet CD and posted on the MSSNA CompuServe forum.

Support for SNA servers across IP routers.

SNA servers communicate with each other using mailslot broadcast messages to the domain. On a TCP/IP wide area network (WAN), mailslots are NetBIOS multicast (broadcast) messages, which typically are not propagated across IP routers. With a new dialog box, SNA servers can be configured to propagate such messages across IP routed networks to all Windows NT Server domain controllers (primary and backup) in the domain.

To allow full communication between SNA servers across an IP routed network, set up the SNA servers on computers running Windows NT Advanced Server or Windows NT Server, and make these servers primary or backup domain controllers. Then start SNA Server Admin and, from the Options menu, choose Server Broadcasts. The resulting dialog box allows you to select an option marked "Route Server Broadcasts over IP routers." For more information, see the Microsoft SNA Server Administration Guide.

Enhanced 16-bit client software that can run on Windows NT. When the 16bit software (client software for the Windows operating system version 3.1) is installed on a computer running Windows NT version 3.5, emulators written for Windows version 3.x can be used on that computer. (In contrast, when the client software for Windows NT is installed, only 32bit emulators can be used on that computer. The two types of client software should not be installed on the same computer at the same time.)

Increases in session limits ( > 1000 ) for modes for Advanced Program-to-Program Communications (APPC).

Improvements to the SNA Server Administration program (SNA Server Admin) and to the command-line interface (snacfg), making these interfaces more powerful and flexible than before.

Improvements to security, so that administration privileges can be controlled through SNA Server Admin.

Enhancement of the tracing utility, snatrace, so that it can be used remotely.

Improvement of error reporting in the 3270 and 5250 Applets.

Improvements in the handling of Admin messages and APPC Attach Manager requests. Mailslots are no longer used for these messages and requests, resulting in faster, more reliable delivery.

An increase in the speed of validation of 3270 LUs at the server.

Improvements in event logging; events are now logged in the background.

Reductions in memory overhead.

Addition of connection retry counters and timeouts, to allow finer tuning of server performance.

Addition of Help files for the APIs.


Contents of the CD
Overview	4 of 16

Contents of the CD

The CD in the SNA Server version 2.1 package includes the following software and directories:

Software for SNA servers, clients, and drivers, including bundled software for  adapter drivers. Setup files allow easy installation of software from the CD.

I386\DISKS directory. This contains the directory structure and all the files for either 3.5-inch or 5.25-inch disks, for installing SNA Server on a computer with an Intel processor. (For a computer with an Alpha AXP or MIPS processor, install from the CD or across the network, not from a floppy disk.)

DOCS directory. This contains a README.TXT file with printing instructions for all the documents in the subdirectories under DOCS. The documents are  provided in Microsoft Word for Windows (version 2.0) format as well as in PostScript format.

DOCS\FONTS directory. This contains printer and screen fonts; instructions for installing the fonts are in the README.TXT file in the DOCS directory.

DOCS\SERVER directory. Subdirectories of this directory contain electronic versions of the printed documents for administrators and users, which can be ordered in hard copy from Microsoft:

Microsoft SNA Server Installation Guide

Microsoft SNA Server Administration Guide

Microsoft SNA Server Reference

Microsoft SNA Server 3270/5250 Applet User's Guide

In the DOCS\SERVER directory is a README.TXT file with printing instructions. The documents are provided in Word for Windows (version 2.0) format and PostScript format, and can also be viewed as Help files.

DOCS\SDK directory. Subdirectories of this directory contain electronic versions of the following printed documents for programmers:

Microsoft SNA Server APPC Programmer's Guide

Microsoft SNA Server CPI-C Programmer's Guide

Microsoft SNA Server LUA Programmer's Guide

SNA Device Interface Specification

3270 Emulator Interface Specification

In the DOCS\SDK directory is a README.TXT file with printing instructions. The documents are provided in Word for Windows (version 2.0) format and PostScript format, and can also be viewed as Help files.

DOCS\WINSNA directory. Subdirectories of this directory contain electronic versions of the following specifications for independent software vendors (ISVs). The specifications can also be viewed as Help files:

Windows APPC Specification

Windows CPI-C Specification

Windows CSV Specification

Windows HLLAPI Specification

Windows LUA Specification

In the DOCS\WINSNA directory is a README.TXT file with printing instructions. The documents are provided in Word for Windows (version 2.0) format as well as PostScript format.

SDK directory. This contains the following software development files:

Header and library files for all SNA Server APIs and interfaces (see the preceding list of programmer's guides).

Sample code and sample TPs.

Information about the sample code is included in appendixes in the programmer's guides for the APIs.

In the SDK\HELP directory, Help files for the Windows specifications named in the preceding list. The Help files are called WINAPPC.HLP, WINCPIC.HLP, WINCSV.HLP, WHLLAPI.HLP, and WINLUA.HLP.

Note that there is no special SDK version of the product (as each product CD contains all the SDK materials).

COLLATRL directory. This contains the following files and subdirectories:

COLLATRL directory itself: Contains the SNA Server Technical Data Sheet, DATASHET.DOC, and the SNA Server Companion Product Catalog, ISVCATAL.DOC (in PostScript format and Word for Windows version 2.0 format). Updates to this catalog are distributed on the Microsoft TechNet CD and posted on the MSSNA CompuServe forum.

COLLATRL\INSDTRAK: Contains files for the Microsoft SNA Server Inside Track training. Many of the files are in Microsoft PowerPoint [image] version 3.0 format. The PowerPoint version 3.0 viewer is included. The files are described in AGENDA.DOC (in Word for Windows version 2.0 format).

COLLATRL\3RDPARTY: Contains ISV product information, including a description of the OpenConnect Systems TN3270 server, TN3270.DOC (in PostScript format and Word for Windows version 2.0 format).

COLLATRL\PRESS: Contains press releases about the SNA Server product.


Planning SNA Server Domains
Overview	5 of 16

Planning SNA Server Domains

One of the basic decisions to make when planning SNA Server domains is whether the SNA servers should be centralized in one place or distributed across business locations. If centralized, the SNA servers are generally placed in a single domain near the host, AS/400, or other system that they provide connections to. If distributed, the SNA servers are spread out across multiple LAN domains, with each domain containing one or more servers and the clients that use that server.

The centralized plan is shown in the following figure.

Centralized Plan

With the centralized approach, all servers and clients are on the same wide area network (WAN), whether they are located in the same building or across the country, and use only one networking protocol, such as TCP/IP, to connect through the network. The advantages of the centralized approach are that all the servers are located in one place for ease of administration, and the same WAN environment can be used for other purposes, such as SQL Server, mail, and printer and file sharing.

The noncentralized plan is shown in the following figure.

Noncentralized Plan

The advantages of the noncentralized approach are that it is already used in many places and therefore does not require major changes, it uses smaller domains that may be easier to configure, and it can use smaller servers.

For more information on network planning issues, see your Windows NT product documentation.


File System Choices and Security
Overview	6 of 16

Planning SNA Server Domains

File System Choices and Security

In order to establish good security for SNA servers in a domain, you need to control access to the SNA Server configuration file. To do this, be sure to install the SNA Server software on a Windows NT file system (NTFS) partition. With NTFS, permissions can be assigned on a file-by-file basis; with the file allocation table (FAT) file system or the high-performance file system (HPFS), this is not possible. Installing the SNA Server software on an NTFS partition is especially important with the primary SNA server, the server that contains the main copy of the configuration file (used by all SNA servers in the domain).

After installation, use the Security menu in SNA Server Admin to create appropriate levels of administrative permission for users and groups in the domain. For more information, see the Microsoft SNA Server Administration Guide.


Overview of SNA Server Installation
Overview	7 of 16

Overview of SNA Server Installation

To install SNA Server, do the following in the order given

1.	Install drivers and adapters using the Windows NT Control Panel.

2.	Install networking protocols using the Windows NT Control Panel (for example, data link control — DLC — for LAN).

3.	Install SNA server(s).

4.	Install SNA Server client(s).

Note

Before using the SNA Server Setup program, be sure to read the SNA Server README File.


System Requirements
Overview	8 of 16

System Requirements

The SNA Server system requirements for servers and clients are as follows. Downstream clients have different requirements, since they do not need SNA Server client components. For downstream clients, the RAM requirement is the actual memory taken by the 3270 emulator or other downstream application.


SNA Server
Overview	9 of 16

System Requirements

SNA Server

An SNA server (version 2.1) requires the following:

For the operating system, Windows NT Advanced Server version 3.1 or Windows NT Server version 3.5.

For network software and protocols, one or more of the following:

Microsoft networking (the network software included in Windows NT).

NWLink or equivalent IPX/SPX services.

Microsoft TCP/IP or equivalent Win32 [image] Windows Sockets version 1.1 interface.

Banyan Enterprise Client version 5.52 for Windows NT.

Services for Macintosh.

Minimum of 20 megabytes (MB) of total system RAM (recommended).

This value is 4 MB above the required minimum for Windows NT Advanced Server or Windows NT Server. Microsoft highly recommends that the server be equipped with enough RAM for optimal performance and for situations where loads are heavy.

Minimum of 11 MB free hard-disk space.

Network adapter.

Supported SNA communications adapter(s).


SNA Server Clients Running Windows NT
Overview	10 of 16

System Requirements

SNA Server Clients Running Windows NT

An SNA Server client running Windows NT requires the following:

For the operating system, Windows NT Advanced Server version 3.1, Windows NT version 3.1, Windows NT Server version 3.5, or Windows NT Workstation version 3.5.

For network software and protocols, one or more of the following:

Microsoft networking (the network software included in Windows NT).

NWLink or equivalent IPX/SPX services.

Microsoft TCP/IP or equivalent Win32 Windows Sockets version 1.1 interface.

Banyan Enterprise Client version 5.52 for Windows NT.

Minimum of 14 MB of total system RAM (recommended).

This is 2 MB above the required minimum for Windows NT or Windows NT Workstation.

Minimum of 7 MB free hard-disk space.

Network adapter.


SNA Server Clients Running Windows Version 3.x
Overview	11 of 16

System Requirements

SNA Server Clients Running Windows Version 3.x

An SNA Server client running Windows version 3.x requires the following:

For the operating system, Windows for Workgroups or Windows version 3.x

For network software and protocols, one or more of the following:

The network software included in Windows for Workgroups

LAN Manager version 2.x

Novell NetWare (IPX.COM) version 3.10 or later, or any ODI driver

Microsoft TCP/IP or equivalent Windows Sockets version 1.1 interface

Banyan VINES version 5.52

Minimum of 4 MB of total system RAM (recommended)

Minimum of 4 MB free hard-disk space

Network adapter

Actual RAM occupancy is shown in the following table:

Software on SNA Server client running Windows version 3.x		RAM occupancy
3270 Applet		525K
5250 Applet		490K
3270 and 5250 Applet loaded at the same time		830K
Base support for ISV 5250 emulator		185K
Base support for ISV 3270 emulator		185K
Base support for APPC, CPI-C, LUA, or CSV application		185K
The preceding numbers represent actual RAM used when loaded.

"Base support" does not include the application itself or the SNA Server API dynamic-link libraries (DLLs) loaded by the application.


SNA Server Clients Running MS-DOS
Overview	12 of 16

System Requirements

SNA Server Clients Running MS-DOS

An SNA Server client running MS-DOS [image] requires the following:

MS-DOS operating system version 3.2 or later

LAN Manager version 2.x, Novell NetWare (IPX.COM) version 3.10 or later, or Banyan VINES version 5.52

Minimum of 640 kilobytes (K) of total system RAM (recommended)

Minimum of 2.2 MB free hard-disk space

Network adapter

Actual RAM occupancy is shown in the following table:

Software on SNA Server client running MS-DOS		RAM occupancy
Base support for IBM PC Support functions		100K
Base support for ISV 3270 emulator		50K
Base support for APPC, LUA-RUI, or CSV application		50K
The preceding numbers represent actual RAM used when loaded.

"Base support" does not include the application itself or the SNA Server API dynamic-link libraries (DLLs) loaded by the application.


SNA Server Clients Running OS/2
Overview	13 of 16

System Requirements

SNA Server Clients Running OS/2

An SNA Server client running OS/2 [image] requires the following:

OS/2 operating system version 1.21 or later

Minimum of 8 MB of total system RAM (recommended)

Minimum of 1 MB free hard-disk space

Network adapter


SNA Server Clients on Macintosh Computers
Overview	14 of 16

System Requirements

SNA Server Clients on Macintosh Computers

An SNA Server client on a Macintosh computer requires the following:

System 6.0.2 or later and Finder version 6.0 or later (System 7.0 and Finder 7.0 can be used).

Standard Macintosh platform with AppleTalk access.

Emulator software and any hardware or additional software required for that emulator. For information about emulator software for the Macintosh, see the SNA Server Companion Product Catalog, ISVCATAL.DOC, in the \COLLATRL directory on the SNA Server CD.


Adapter Support
Overview	15 of 16

Adapter Support

SNA Server supports the full complement of Windows NT-based adapters. The following is a partial list of adapters supported by SNA Server. Other adapters are available from third-party vendors.

Any Windows NT NDIS-compliant Token Ring or Ethernet device driver, using Windows NT 802.2 DLC transport protocol

Attachmate SDLC

Barr Systems T1-SYNC (for SDLC)

DCA [image] IRMA (for DFT)

DCA ISCA (for SDLC and X.25)

Microgate MGx, Microgate DSA, Microgate USA (for SDLC  and X.25)

IBM SDLC

IBM MCPA

IBM MPA/A

IBM DFT

IBM 3270 Connection A,B

IBM 3278/9 Advanced Emulation adapter

Any driver developed through the SNADIS interface


Windows-Based SNA Support
Overview	16 of 16

Windows-Based SNA Support

SNA Server supports the following APIs:

Windows APPC version 1.0 for developing applications that communicate peer-to-peer with other APPC applications.

Windows CPI-C version 1.0 for developing applications that communicate peer-to-peer with IBM System Application Architecture (SAA [image]) applications.

Windows Common Service Verb (CSV) version 1.0 for developing applications that enable tracing of application programming interface (API) calls and communicate with NetView [image].

Windows conventional Logical Unit Application programming interface (LUA) version 1.0 for developing applications (using LUA Request Unit Interface [RUI] or LUA Session Level Interface [SLI] APIs) that need direct access to SNA LU 0, 1, 2, and 3 data streams.


Installing SNA Servers
Chapter 2	1 of 33

Installing SNA Servers

The SNA Server Setup program (Setup) installs SNA Server, using the information you provide in various dialog boxes. Once the initial files are installed, you add and configure the link services for your SNA server. Setup creates a configuration file on the primary SNA server and on any backup servers that you install, and stores link service information in these files. (The connections and other items that you configure with the SNA Server Administration program — SNA Server Admin — will also be stored in the configuration files.)

When you are finished, Setup gives you the option of either exiting the program, or continuing directly to SNA Server Admin to configure connections and LUs for your SNA server(s).

This chapter can help you:

Understand the software components that are part of SNA servers and clients.

Install SNA servers and the link services that they need.

Modify or remove link services.

Modify SNA servers so they can support Macintosh clients.

Modify SNA servers so they can communicate across IP routers.

Remove SNA servers.

For information about compatibility between SNA Server version 2.1, SNA Server version 2.0, and Comm Server version 1.x, see Chapter 4, "Upgrading to SNA Server Version 2.1." For information about installing SNA Server clients, see Chapter 3, "Installing SNA Server Clients."


Using SNA Server Setup
Installing SNA Servers	2 of 33

Using SNA Server Setup

Setup is a graphical interface that allows you to:

Install, configure, and remove SNA Server.

Install, configure, and remove link services.

Note that SNA Server Setup is the only interface that should be used for removing SNA Server device drivers, such as the IBM SDLC driver and link service. Do not use the Network option of the Windows NT Control Panel to remove such drivers; doing so may cause unexpected system events. To correct such a situation, remove and reinstall SNA Server, using SNA Server Setup.

Install, configure, and remove SNA Server client software.

Setup presents various dialog boxes that you use to provide information about your configuration. If you are installing SNA Server for the first time, you make selections and enter information for your SNA Server installation and your link service(s). Setup copies files, configures the system, and installs the necessary services.

If you have already installed SNA Server, Setup presents dialog boxes for adding, removing, or configuring new link services, or for modifying or removing SNA Server.

To use Setup, you must be logged on as an Administrator on the Windows NT Server, because Setup requires the ability to access the Windows NT Registry. For information about the Administrator account and the Administrators group, see your Windows NT product documentation.


Setup Versus SNA Server Admin
Installing SNA Servers	3 of 33

Using SNA Server Setup

Setup Versus SNA Server Admin

After you have used Setup to install SNA Server and the link services, you use SNA Server Admin to configure connections and LUs. Later, if you need to change or create additional link services, you must use Setup again to configure these link services.

For an introduction to SNA Server configuration and for forms that you can use to gather configuration information, see the Microsoft SNA Server Administration Guide. You can also use the comprehensive Help system that exists for both Setup and SNA Server Admin.


Creating a Share for Installing Clients Across the Network
Installing SNA Servers	4 of 33

Using SNA Server Setup

Creating a Share for Installing Clients Across the Network

After one or more SNA servers are installed, they can be used to allow installation of SNA Server clients across the network. SNA Server clients that are Intel [image] -based can also be installed from a floppy disk. For information about creating a network share from which you can install clients, see Chapter 3, "Installing SNA Server Clients."


Using Dialog Boxes
Installing SNA Servers	5 of 33

Using Dialog Boxes

Setup consists of a set of dialog boxes presented in a predetermined order. Dialog boxes are special windows displayed to solicit a response from the user. The user must provide a response before the program can continue. Exactly which dialog boxes you see and how they are presented is determined by several factors. First, Setup determines whether this is your first installation of SNA Server. If so, Setup presents a set of dialog boxes that help you to configure your system from the beginning.

If you have already installed SNA Server, Setup presents the Setup Options dialog box. This dialog box allows you to add, configure, or remove link services, change the SNA server role for the domain, configure client/server protocols, or remove SNA Server. For more information on modifying SNA Server, see "Modifying or Removing SNA Servers," later in this chapter.

As you use Setup, you will notice pop-up windows that appear while Setup is processing information. These windows require no response; they provide information only. They disappear when processing is complete.

The following table provides a summary of the command buttons. Not all command buttons appear in every dialog box.

Button	Action
Continue	Processes the information in the dialog box.
Exit	Cancels the information in the dialog box.
Back	Returns you to the previous dialog box.
Help	Displays online help for the dialog box you are currently using.
For more information about using dialog boxes, see the Microsoft SNA Server Administration Guide or your Windows NT product documentation.


SNA Server Components
Installing SNA Servers	6 of 33

SNA Server Components

An SNA Server installation contains the following components:

SnaBase

SnaBase is the fundamental component in an SNA Server network. It must be running before any other SNA component can start. It is the “eyes” and “ears” into the domain of servers. At installation, SnaBase is the only SNA Server component that is automatically started when the server is restarted. (Optionally, you can use the Control Panel to change the startup type of other services to Automatic.)

SnaBase serves two purposes. On a client, it builds a list of available services in the domain. On a server, in addition to building a list of available services in the domain, it broadcasts the list of services provided by that server. It provides a mechanism for the remote administrator to control or configure the SNA Server resources in the domain.

SnaBase coordinates SNA servers according to the roles that you assign them in the domain: primary, backup, and member. The primary server holds the main copy of the SNA Server configuration file, which is an essential file for the functioning of SNA Server. Backup servers, if you choose to have them, store copies of the configuration file, and SnaBase allows one of these copies to be loaded if the primary server stops functioning. Member servers do not store copies of the configuration file. For more information about server roles, see "Selecting the Server Role," later in this chapter.

SnaServer

The SnaServer component is the physical unit (PU) 2.1 node within SNA servers. The SnaServer interacts with clients and other nodes on the SNA network.

Clients

SNA Server clients are computers that connect to the SNA network through SNA servers. SNA Server clients include computers running the following operating systems: Windows NT version 3.1 or 3.5, Windows version 3.x, MS-DOS, and OS/2.

Link Services

Link services are the software component of SNA Server that communicates with the device driver for a particular communication adapter (DLC 802.2, SDLC, X.25, DFT, Channel, or Twinax). Link services define the protocol used between the SNA Server software and the communications adapters in a computer. Link services are written to the SNADIS interface.

NetView components

The NetView components allow alerts and console commands to be passed back and forth between SNA Server and a host. The NetView components include SnaNMVT, NVAlert, and NVRunCmd. SnaNMVT routes NetView alerts back and forth between an SNA server and a host, and provides basic support to NVAlert and NVRunCmd. NVAlert allows you to specify NetView alerts that would not otherwise be forwarded. NVRunCmd allows commands that are typed at a host console to be run on an SNA server.

SNA Gateway

An SNA gateway is an application that emulates an IBM cluster controller or peer node in order to allow communications between a network of clients and one or more SNA hosts or peers.

SNA Adapter

An SNA adapter or “card” is the hardware supporting one or more SNA connections.

SNA Connection

An SNA connection is a single connection at the SNA data link level representing a single SNA PU to the host.


Components Installed by Setup
Installing SNA Servers	7 of 33

SNA Server Components

Components Installed by Setup

Setup installs the following software components on an SNA server:

SnaBase

SnaServer

NetView components: SnaNMVT, NVRunCmd, and NVAlert

Link services available on the Setup CD or disks or available through third-party vendors

Setup creates an NVAlert configuration file, NVALERT.INI, in the SYSTEM subdirectory of the SNA Server root directory. To control the NVAlert service, modify the NVALERT.INI file to specify the Windows NT-based alerts that you want forwarded to the host. For more information on using NVAlert and NVRunCmd, including modifying the NVALERT.INI file, see the Microsoft SNA Server Administration Guide.

Of the components listed in this section, only SnaBase is automatically started when the Windows NT system is started. To start any other service automatically, use the Control Panel to configure the startup type for the service, as described in your Windows NT documentation.


Components Available Through Independent Vendors
Installing SNA Servers	8 of 33

SNA Server Components

Components Available Through Independent Vendors

Independent vendors offer a number of link services not included in SNA Server Setup itself, and offer many kinds of hardware for use with SNA Server. For information about these vendors and the products they offer, see the SNA Server Companion Product Catalog, ISVCATAL.DOC, in the \COLLATRL directory on the SNA Server CD. Updates to this catalog are distributed on the Microsoft TechNet CD and posted on the MSSNA CompuServe forum.

Twinax and Channel Link Services

Microsoft SNA Server now supports Twinax and Channel connections. However, link services for these connection types are not included in SNA Server Setup, but must be obtained from other vendors. (Setup has a built-in mechanism to allow you to install link services from independent vendors, as described in “Installing Other Link Services,” later in this chapter.) Vendors who supply link services for Twinax or Channel adapters are listed in the SNA Server Companion Product Catalog, ISVCATAL.DOC, in the \COLLATRL directory on the SNA Server CD.


Sponsor Connections
Installing SNA Servers	9 of 33

Sponsor Connections

SNA servers exist within the context of a Windows NT domain, and SNA Server clients connect to this domain through sponsor connections. For clients, sponsor connections, together with the SnaBase, act as the “eyes” and “ears” into the server domain.

The first thing that a client must do in order to communicate with the SNA network is to establish a sponsor connection to an SNA server. All the information from SNA servers, which is shared between the servers through connectionless datagram broadcasts, is propagated to the clients through sponsor connections.

The following are examples of data that flow over sponsor connections:

Configuration data

APPC attach messages

Directory services

Event logging


File System Choices and Security
Installing SNA Servers	10 of 33

Sponsor Connections

File System Choices and Security

In order to establish good security for SNA servers in a domain, you need to control access to the SNA Server configuration file. To do this, be sure to install the SNA Server software on an NTFS partition. With NTFS, permissions can be assigned on a file-by-file basis; with the FAT file system or HPFS, this is not possible. Installing the SNA Server software on an NTFS partition is especially important with the primary SNA server, the server that contains the main copy of the configuration file (used by all SNA servers in the domain).

After installation, use the Security menu in SNA Server Admin to create appropriate levels of administrative permission for users and groups in the domain. For more information, see the Microsoft SNA Server Administration Guide.


Starting the SNA Server Setup Program
Installing SNA Servers	11 of 33

Starting the SNA Server Setup Program

This section tells how to start the SNA Server Setup program from the SNA Server CD or from floppy disks. It also tells how to create a set of installation floppy disks from the SNA Server CD.

The instructions in this chapter tell how to install SNA servers. For information about installing SNA Server clients, see Chapter 3, "Installing SNA Server Clients."

To start Setup

1.	Insert either the SNA Server CD or the first installation disk into an appropriate drive.

2.	In File Manager or at the command prompt, change to the drive containing the CD or floppy disk.

3.	If using floppy disks (usable on Intel-based systems only), skip to the next step. If using the SNA Server CD, change to the appropriate directory:

For an Intel processor, change to the \I386 directory.

For a MIPS processor, change to the \MIPS directory.

For a Digital Alpha AXP processor, change to the \ALPHA directory.

4.	Start Setup:

To start Setup from File Manager, double-click on SETUP.EXE.

To start Setup from the command prompt, type

setup

A welcome to SNA Server Setup dialog box appears.

Note

Choose the Help button to get assistance any time you are using a dialog box. When you do, Setup displays a text box explaining the choices you have at that point and the procedure to complete the dialog box.

5.	Choose the Continue button.

If you are installing from floppy disks, the Server/Client Selection dialog box appears; choose the Server button.

To continue with installation, see "Recording Identifying Information," later in this chapter.

The following procedure tells how to use the SNA Server CD to create floppy disks for installing SNA servers. For information about creating floppy disks for installing SNA Server clients, see Chapter 3, "Installing SNA Server Clients."

To use the SNA Server CD to create floppy disks for installing SNA servers

1.	Obtain six blank, high-density, formatted 5.25inch or 3.5inch disks.

2.	Insert the SNA Server CD into the CD-ROM drive.

3.	In File Manager or at the command prompt, change to the drive containing the CD.4.	Change to the \I386\DISKS directory on the CD.

4.	Change to the \I386\DISKS directory on the CD.

5.	Insert a floppy disk in an appropriate drive.

6.	Copy all files and subdirectories from the DISK1 directory on the CD into the root directory of the floppy disk.

7.	Remove the floppy disk.

8.	Repeat steps 5 – 7 to copy the remaining subdirectories to additional floppy disks. These directories are DISK2, DISK3, DISK4, DISK5, and DISK6.


Recording Identifying Information
Installing SNA Servers	12 of 33

Recording Identifying Information

You can record identifying information in your SNA Server software.

To record identifying information in SNA Server software

1.	Start SNA Server Setup, as described in the previous section.

The Software Licensing dialog box appears.

2.	In the box marked Your name, type your name.

3.	Optionally, in the box marked Company name, type your company's name.

4.	In the box marked Product ID, type the product identification number, available on the inside back cover of this installation guide.

By entering the Product ID (PID), you make it available for display through the SNA Server version number utility, snaver, so that if you call for product support, you can readily identify your software when requested.

5.	Choose the Continue button.

The Confirm License Information dialog box appears.

6.	If you want to change the names you entered, choose the Back button, retype the names, and then choose the Continue button.

7.	In the Confirm License Information dialog box, choose the OK button.

The Installation Path dialog box, shown in the next section, appears.


Specifying the Installation Path
Installing SNA Servers	13 of 33

Specifying the Installation Path

You can use the default installation path offered by Setup (C:\SNA), or change the path.

Note

In order to establish good security for SNA servers in a domain, you need to control access to the SNA Server configuration file. To do this, be sure to install the SNA Server software on an NTFS partition. With NTFS, unlike other file systems, permissions can be assigned on a file-by-file basis.

After installation, use the dialog boxes accessed from the Security menu in SNA Server Admin to create appropriate levels of administrative permission for users and groups in the domain. For more information, see the Microsoft SNA Server Administration Guide.

To accept the default path

1.	Complete the procedures in the previous sections.

The dialog box shown in Figure 2.1 appears.

Figure 2.1    Installation Path Dialog Box

2.	In the Installation Path dialog box, choose the Continue button.

Setup copies the files needed by SNA Server and creates the Registry entries for all subservices.

The Select Client/Server Protocols dialog box, shown in the next section, appears.

To change the installation path

1.	Complete the procedures in the previous sections.

2.	In the Installation Path dialog box, shown in Figure 2.1, delete the default path in the Install to box.

3.	In the Install to box, type the full path for the new destination.

It is best to specify an empty directory, so that Setup will not inadvertently overwrite a file needed by another program when it installs the SNA Server files.

4.	Choose the Continue button.

Setup copies the files needed by SNA Server and creates the Registry entries for all subservices.

The Select Client/Server Protocols dialog box, shown in the next section, appears.


Selecting Client/Server Protocols
Installing SNA Servers	14 of 33

Selecting Client/Server Protocols

If Setup detects more than one client/server protocol on your computer, you must specify which protocols you are using.

To select client/server protocols

1.	Complete the procedures in the previous sections.

If there is more than one client/server protocol on your computer, the dialog box shown in Figure 2.2 appears. Otherwise, the dialog box shown in Figure 2.3 appears.

Figure 2.2    Select Client/Server Protocols Dialog Box

Note

You will only see the Select Client/Server Protocols dialog box if there is more than one client/server protocol on your computer. Otherwise, go to “Selecting the Server Role,” later in this chapter.

2.	In the Select Client/Server Protocols dialog box, select one, several, or all of the check boxes:

Microsoft Networking (Named Pipes)

Novell [image] NetWare [image] (IPX/SPX)

Banyan VINES

TCP/IP

AppleTalk

If the system you are installing on does not include one or several of the client/server protocols, the corresponding check boxes are unavailable.

3.	Choose the Continue button.

If you did not select Microsoft Networking (Named Pipes), the Network Domain Name dialog box, shown in the next section, appears.

If you selected Microsoft Networking (Named Pipes), the Change SNA Server Role dialog box, shown in Figure 2.4, appears; continue with “Selecting the Server Role,” later in this chapter.


Specifying the Network Domain Name
Installing SNA Servers	15 of 33

Selecting Client/Server Protocols

Specifying the Network Domain Name

If you did not select Microsoft Networking (Named Pipes) as one of your client/server protocols, you must specify the name of the network domain. If your operating system is Banyan VINES (and not Microsoft Networking), you must also specify the Banyan StreetTalk [image] group name.

To specify the domain name

1.	Complete the procedures in the previous sections.

If you did not select Microsoft Networking (Named Pipes) in the Select Client/Server Protocols dialog box, a dialog box similar to the one shown in Figure 2.3 appears.

Figure 2.3    Network Domain Name Dialog Box

2.	In the appropriate box, type the network domain name.

For a TCP/IP network, you can specify the name in any of several forms:

The domain name used in the Windows NT domain.

The host name plus the TCP domain name. This is an example:

host1.location.com

If you use a name in this form, you must also configure the computer to map from the name to an IP address. This can be done with the Domain Name System (DNS) resolver or by adding an appropriate entry to a file called HOSTS. For information about either of these, see your TCP/IP documentation.

The IP address. This is an example:

11.123.45.67

3.	Choose the Continue button.

If you are using Banyan VINES (and not Microsoft Networking), the StreetTalk Group Name dialog box appears.

Otherwise, the Change SNA Server Role dialog box, shown in Figure 2.4, appears; continue with “Selecting the Server Role,” later in this chapter.

Specifying the StreetTalk Group Name on a Banyan VINES Network

When you install SNA Server software on a computer for which the networking software is Banyan VINES (and not Microsoft Networking), SNA Server Setup creates a StreetTalk name by combining information stored on the Banyan VINES network with information you type into dialog boxes in Setup. In order to run SNA Server Setup on such a computer, you must be logged on to the VINES network (the BAN.EXE program allows you to do this) and you must have administrative rights.

A StreetTalk name consists of three parts, identifying the item, group, and organization, with an @ sign between the parts: item@group@organization. For the first part (item), SNA Server Setup automatically uses the local computer name. The last two parts together (group@organization) are called the StreetTalk group name. SNA Server Setup allows you to type this two-part group name into the StreetTalk Group Name dialog box. If you leave this box blank, Setup uses the group name of the user currently logged on in the Banyan VINES network.

After you type the necessary names into Setup, SNA Server establishes communication on the Banyan VINES network; in Banyan VINES terminology, SNA Server creates a PC-based service through which it is represented to the Banyan VINES network. After this is accomplished, SNA Server creates a StreetTalk list, using the domain name that you typed into the Network Domain Name dialog box. All the SNA servers in a particular Windows NT domain add their names to the list on each of the servers; this identifies all the SNA servers to each other. Clients also use this list to locate the servers in their group.

It is essential that all the servers and clients that will work together have the same StreetTalk group name. This ensures that clients will be able to locate SNA servers.

To specify the StreetTalk group name

1.	Complete the procedures in the previous sections.

If you are using Banyan VINES (and not Microsoft Networking), the StreetTalk Group Name dialog box appears.

2.	In the Group Name box, type the StreetTalk group name. Type an @ sign between the two parts of the name.

If you leave this box blank, Setup uses the group name of the user currently logged on in the Banyan VINES network.

If you type the group name into the dialog box, type the same name for all the servers and clients. If you use the default, make sure that the group name of the user logged on in the Banyan VINES network during installation of SNA Server is always the same group name, regardless of whether client or server software is being installed.

3.	Choose Continue.

The Change SNA Server Role dialog box, shown in the next section, appears.


Selecting the Server Role
Installing SNA Servers	16 of 33

Selecting the Server Role

When installing an SNA server, the server is designated as primary, backup, or member. These server roles, and the method for selecting them, are described in this section.

To select the server role

1.	Complete the procedures in the previous sections.

The dialog box shown in Figure 2.4 appears.

Figure 2.4    Change SNA Server Role Dialog Box

2.	Select the appropriate role for this server:

Primary Configuration Server

The primary SNA server contains the domain-wide configuration file. The configuration file reflects the SNA Server resources for the domain, including all SNA servers, link services, LUs, 3270 users, and so on. There can be only one primary server in the domain. Typically, the primary server is the first server installed.

Backup Configuration Server

A backup SNA server is a server on which the configuration file is replicated by SNA Server. There can be more than one backup server in a domain. SNA Server will load the copy of the configuration file located on a backup SNA server if the primary SNA server goes down; in this case, servers and connections can be started and stopped, but the configuration cannot be changed or saved.

Member Server (no configuration)

A member SNA server does not contain the configuration file. One or more SNA servers can operate as member servers.

Note

When the primary server or a backup server is installed using Setup, the path of \SNAroot\SYSTEM\CONFIG is automatically shared as \\servername\COMCFG. This share enables SNA Server to access the configuration file on the primary or backup servers.

For more information on saving, copying, and backing up the configuration file, see the Microsoft SNA Server Administration Guide.

3.	Choose the Continue button.

The Review Settings dialog box appears.

4.	If you want to review your settings, choose the Review button, and confirm or change settings as needed.

The Review Settings dialog box reappears.

5.	Choose the Continue button.

Setup copies the files to the selected location. If you are installing from floppy disks, you will be prompted to insert floppy disks as they are needed.

After the files are copied, the Link Service Installation dialog box, shown in Figure 2.4, appears.

6.	If you want to complete the SNA Server installation without installing link services, choose the Continue button and go to “Completing Setup” later in this chapter.

To install link services, see the next section.


Installing a Link Service
Installing SNA Servers	17 of 33

Installing a Link Service

Link services define the protocol used between the SNA Server software and the communications adapters installed in a computer. Link services are written to the SNADIS interface. You can install any of the link services listed in the Available Link Services box of the Link Service Installation dialog box, shown in Figure 2.5; you can also install a link service provided by a third-party software vendor. For information on installing a link service not listed in the Available Link Services box, see the next section.

Setup will lead you through several dialog boxes to install and configure the link service. Repeat this process of installing and configuring for each link service you need.

Note

If you are installing a DLC (802.2) link service, and you have not already installed the DLC networking protocol through the Windows NT Control Panel, SNA Server Setup will automatically help you carry out the installation of the protocol. However, you will need the disc or floppy disks from which you installed Windows NT in order to install the DLC protocol (required by the DLC link service).

To install a link service

1.	Complete the procedures in the previous sections.

The dialog box shown in Figure 2.5 appears.

Figure 2.5    Link Service Installation Dialog Box

2.	In the Available Link Services box of the Link Service Installation dialog box, select a link service.

3.	Choose the Install button.

A link service configuration dialog box appears, specific to the type of link service you selected: 802.2, SDLC, DFT, or X.25.

For information about configuring link services, go to “Configuring a Link Service” later in this chapter.

Note

When making a selection from any of the list boxes in Setup, you can also double-click the item you want to select.


Installing Other Link Services
Installing SNA Servers	18 of 33

Installing a Link Service

Installing Other Link Services

SNA Server includes link services for several popular IBM and third-party adapters. If the link service you need is not listed in the Available Link Services box of the Link Service Installation dialog box, shown in Figure 2.5, you can install it from disk or specify the network path where it can be found.

To install other link services

From the Link Service Installation dialog box, shown in Figure 2.5, choose the Other button.

The dialog box shown in Figure 2.6 appears.

Figure 2.6    Link Service Import Dialog Box

To install link services from drive A (the default drive)

In the Link Service Import dialog box, shown in Figure 2.6, choose the Continue button.

Setup looks in drive A for other link services. The Link Service Installation dialog box (shown in Figure 2.5) reappears, listing any link service found.

To install link services from another drive or network path

1.	In the Path box of the Link Service Import dialog box, shown in Figure 2.6, delete the default drive.

2.	In the Path box, type the drive or network path.

3.	Choose the Continue button.

Setup looks in the specified location for other link services. The Link Service Installation dialog box (shown in Figure 2.5) reappears, listing any link service found.


Configuring a Link Service
Installing SNA Servers	19 of 33

Configuring a Link Service

Once you have installed a link service, you must configure it. Once you have configured a link service, you can install additional services or you can complete the SNA Server installation.

The following sections discuss the issue of avoiding interrupt and other conflicts between adapters, and describe each type of link service that can be configured (802.2, SDLC, DFT, or X.25). Review the information about adapters, and then turn to the appropriate section for your link service.


Avoiding Interrupt or Address Conflicts Between Adapters
Installing SNA Servers	20 of 33

Configuring a Link Service

Avoiding Interrupt or Address Conflicts Between Adapters

The various adapters in a computer must be configured to work together, so that there are no interrupt, port address, or direct memory access (DMA) conflicts. When you install a new adapter in your computer, you may need to study the configuration of the new and old adapters to make sure there are no conflicts. The following section discusses some specific steps to take with IBM SDLC and token ring adapters.

Note

Device drivers provided by SNA Server report any interrupt, port address, or DMA conflicts they detect to the Windows NT system event log.

SDLC Adapter Notes

The following sections provide information about IBM SDLC and MPCA adapters and Microgate SDLC adapters.

Avoiding Interrupt Conflicts

If you are using an IBM SDLC or MPCA card in an ISA or EISA bus system, you should do the following:

Disable SERIAL.SYS (which is enabled by default) to prevent an interrupt conflict. To do this, use the Devices option in the Windows NT Control Panel.

Disable any COM ports that use interrupts that conflict with the IBM SDLC adapters. This is normally done through EISA configuration programs, CMOS setup programs, or jumpers on the motherboard.

Working with SDLC Adapters and Sound System Adapters

Because IBM SDLC adapters and various sound adapters use overlapping I/O addresses on the bus, these adapters cannot both be installed in a computer at the same time. Neither of these types of adapters will function correctly with the other type installed in the computer. Either the sound adapter must be removed from the computer, or an alternate SDLC adapter with a configurable port address must be used.

SDLC adapters that have a configurable port address are listed in the SNA Server Companion Product Catalog (ISVCATAL.DOC, in the \COLLATRL directory on the SNA Server CD).

Configuring Microgate SDLC Adaptersfor Compatibility with Sound System Adapters

Contrary to the current edition of the Microgate hardware documentation, the Microgate MG96 or MG144 SDLC adapter can be configured to use the secondary adapter address with Microsoft SNA Server. Operation at the secondary address of 0x3A0 avoids conflict with Windows Sound System adapters in the address range 0x380 – 0x38F. The current edition of hardware documentation indicates that adapter DIP 1, switch 8 must be ON (which causes operation at the primary SDLC adapter address), but it can, in fact, be set to OFF (causing operation at the secondary address). SNA Server Setup automatically detects this secondary address when installing the link service.

Adding an IBM SDLC Adapter on MIPS or Alpha AXP

If you are adding an IBM SDLC adapter to a MIPS or Alpha AXP computer, use your EISA configuration utility to add a non-EISA adapter with the following settings:

Base I/O address: 0x380

Interrupt: 3

DMA channel: 1

IBM Token Ring Adapter Notes

If you are using an IBM token ring adapter in an ISA or EISA bus system, you should do the following:

By default, Windows NT loads PARALLEL.SYS during initialization. To avoid interrupt conflicts between PARALLEL.SYS and IBMTOK.SYS, the IBM Token Ring device driver, be sure to choose an interrupt other than 7 on your IBM Token Ring card, or disable the Parallel driver services by using the Devices option in the Windows NT Control Panel.

Disable any parallel ports that use interrupts that conflict with the IBM Token Ring cards. This is normally done through EISA configuration programs, CMOS setup programs, or jumpers on the motherboard.


Configuring a DLC 802.2 Link Service
Installing SNA Servers	21 of 33

Configuring a Link Service

Configuring a DLC 802.2 Link Service

An SNA DLC link service allows SNA Server to communicate with host, peer, or downstream computers over token ring and Ethernet LANs, using the IEEE standard 802.2 data link control (DLC) protocol. The following illustration shows the DLC 802.2 link service.

SNA Server DLC Connection

If you are using an IBM token ring adapter, see "IBM Token Ring Adapter Notes," earlier in this chapter.

If you have an Ethernet LAN in which SNA servers communciate with remote computers via routers (not MAC layer bridges), see "Installing SNA Servers in an Ethernet LAN with Routers," later in this chapter.

To configure a DLC 802.2 link service

1.	Complete the procedures in the previous sections, so that you access the link service setup dialog box for the DLC 802.2 link service you want to configure. The following list reviews the methods for accessing this dialog box:

If this is the first link service you are installing, in the Link Service Installation dialog box (shown in Figure 2.5), select the DLC 802.2 link service and choose the Install button.

If you are adding this link service after installing others, in the Link Service Configuration dialog box (shown in Figure 2.7), choose the Add button. Then, in the Link Service Installation dialog box (shown in Figure 2.5), select the DLC 802.2 link service and choose the Install button.

If you have already installed this link service and want to reconfigure it, in the Link Service Configuration dialog box (shown in Figure 2.7), select the DLC 802.2 link service and choose the Configure button.

The DLC 802.2 Link Service Setup dialog box appears.

2.	Either accept the default title, or delete the default in the Title box and type the new title for this link service.

You can use as many as 40 characters for the title.

3.	In the Adapter box, select the adapter card you are using.

4.	In the Local Service Access Point (SAP) box, type the local SAP, a value that codes for access to certain services on an 802.2 connection within an SNA network.

This number must be a multiple of 4, ranging from 4 through 252. In most cases, the SAP for SNA Server is 4.

5.	Choose the Continue button.

Setup copies the required files, and the dialog box similar to the one shown in Figure 2.7 appears, listing the entry for this link service.

Figure 2.7    Link Service Configuration Dialog Box

6.	You can continue to install and configure link services, or you can complete the SNA Server setup.

To continue with installing and configuring link services, choose the Add button and go to the appropriate section for the link service.

To complete the SNA Server setup, choose the Continue button and go to “Completing Setup” later in this chapter.

Installing SNA Servers in an Ethernet LAN with Routers

If you have an Ethernet LAN in which SNA servers communicate with remote host, peer, or downstream systems via routers (not MAC layer bridges), you may need to set the FrameType registry entry. This entry specifies the type of frames for the DLC (802.2) link service to send over the Ethernet LAN. The frame type used by SNA Server must match the frame type used by the routers.

For information about editing the Windows NT Registry, see your Windows NT documentation. The FrameType registry entry can be set on an SNA server only and is found in the following location in the Registry:

HKEY_LOCAL_MACHINE

SYSTEM

  CurrentControlSet

    Services

      DLCLinkServiceName

        Parameters

          ExtraParameters

This is the variable name and description:

FrameType:REG_DWORD:number

This variable specifies the type of frames for the DLC (802.2) link service to send over an Ethernet LAN. The variable need be set only if the LAN is Ethernet, not token ring, and only if the SNA server communicates with remote host, peer, or downstream systems via routers (not MAC layer bridges).

If the SNA server communicates over Ethernet via routers, check with the local network support staff to determine what type of frames the routers pass. The frames can be either standard 802.3 format or 802.2 packets prefixed by DIX headers using EtherType value 0x80D5.

Specify the number in FrameType as follows:

Value	Effect
0	Use the frame type specified for this adapter in the Registry entry for the DLC protocol stack: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services \DLC\Parameters\AdapterName\UseDixOverEthernet. The default for UseDixOverEthernet is 0, resulting in 802.3 format.
1	Use the frame type automatically determined by the DLC stack during XID exchange.
2	Use standard 802.3 format.
3	Use 802.2 packets prefixed by DIX headers using EtherType value 0x80D5.
If FrameType is not set, it defaults to 0, which means that the frame type is the one specified in UseDixOverEthernet, as described in the preceding table.


Configuring an SDLC Link Service
Installing SNA Servers	22 of 33

Configuring a Link Service

Configuring an SDLC Link Service

An SDLC link service enables SNA Server to communicate with host, peer, or downstream computers through full-duplex or half-duplex synchronous modems, over telecommunications lines that are switched (dialed in the standard way) or leased (dedicated).  SDLC is IBM's implementation of a bit-oriented serial protocol with a standardized frame reader and block check sequence. SDLC applies to synchronous transmissions; it organizes information in rigidly structured units called frames. The following illustration shows the SDLC link service.

SNA Server SDLC Link Service

If you are using an IBM SDLC or MPCA adapter or a Microgate SDLC adapter, see "SDLC Adapter Notes," earlier in this chapter. If you are configuring the Barr SDLC link service, see "Notes on the Barr SDLC Link Service," later in this chapter.

To configure an SDLC link service

1.	Complete the procedures in the previous sections, so that you access the link service setup dialog box for the SDLC link service you want to configure. The following list reviews the methods for accessing this dialog box:

If this is the first link service you are installing, in the Link Service Installation dialog box (shown in Figure 2.5), select the SDLC link service you want and choose the Install button.

If you are adding this link service after installing others, in the Link Service Configuration dialog box (shown in Figure 2.7), choose the Add button. Then, in the Link Service Installation dialog box (shown in Figure 2.5), select the SDLC link service you want and choose the Install button.

If you have already installed this link service and want to reconfigure it, in the Link Service Configuration dialog box (shown in Figure 2.7), select the SDLC link service you want and choose the Configure button.

2.	If one or more dialog boxes appear, offering choices for IRQ, DMA, and other settings, complete the dialog boxes and choose Continue.

When you have completed any preliminary dialog boxes, an SDLC Link Service Setup dialog box appears. The IBM SDLC Link Service Setup dialog box is shown here.

3.	Either accept the default title, or delete the default in the Title box and type the new title for this link service.

You can use as many as 40 characters for the title.

4.	If the Card Type box is included in the dialog box, select the card you will be using.

Note

If you have an IBM SDLC adapter or an IBM MCPA adapter, and you want to use a transmission speed greater than 9600 baud, select half-duplex and not full-duplex in SNA Server Admin. These adapters lack a coprocessor and cannot handle full-duplex transmission at high transmission speeds.

5.	If the Details or Adapter Details button is included in the dialog box, you can choose it and view the settings for the SDLC card. (If you have a Microgate card, you can also change one setting, the DMA channel.) For information, see the documentation for your adapter.

6.	Under Line Type, select the appropriate option:

Leased

Choose this option for a dedicated telecommunications line.

Switched: Server-Stored Number

Choose this option if the modem can accept a phone number from SNA Server, that is, if the SDLC adapter to which the modem is attached has a built-in serial (COM) port (like the SDLC adapters from Microgate). For more information, see "Requirements for Using Server-Stored Numbers," later in this chapter.

Switched: Modem-Stored Number

Choose this option for a modem that stores a phone number. Make sure that the modem is configured to dial the number when the Data Terminal Ready (DTR) is raised, in conformance with the IEEE RS 232 Modem Specification for line 108.1.

Switched: Manual Dial

Choose this option if you will dial the phone number. SNA Server will prompt you when it is time to dial the number.

7.	If you would like the line to use constant RTS, select the Constant RTS check box.

Constant RTS (Request to Send) causes the SDLC adapter to be in constant readiness to send data. This option is required if a line is to be used for full duplex. It cannot be used with multidrop.

If an SDLC adapter does not use Constant RTS, before the adapter can send data, it must raise RTS and then wait for the remote end to raise CTS (Clear To Send). In contrast, an adapter that uses Constant RTS holds RTS high so CTS is always high, and the wait is eliminated.

Note

For higher throughput, choose Constant RTS whenever you can. It is generally used on leased lines and is often available on modems for switched connections as well.

However, do not select this option when configuring this link service for use by a multidrop connection. Multidrop connections allow multiple SDLC connections to connect to the same physical wire. Usually, SDLC is a point-to-point connection protocol.

8.	If other options are displayed in the dialog box, fill in the appropriate information. For information about the choices offered, choose the Help button.

9.	If the Dialer Settings button is included in the dialog box, choose it, and configure the settings as follows:

COM Port

Select the number of the COM port; for example, for COM1, select 1.

If you are adding a COM port by adding this SDLC card, and you select a new number for that COM port, Setup responds by allowing you to access the appropriate dialog box for configuring the COM port within Windows NT.

The range is from None through 254. The default is None.

Baud Rate

Select the rate of transmission. The range includes relevant values from 75 through 115200. The default is 9600.

Incoming String

Type the string to be sent to the modem when an incoming call is detected. The default is AT&F&C1&S1&D3&Q1Q1S0=1. This string will be appropriate in most situations. For more information, see "Command String Examples," later in this chapter.

Outgoing String

Type the string to be sent to the modem when an outgoing call is detected. The default is AT&F&C1&S1&D3&Q1Q1S0=0DT. This string will be appropriate in most situations. For more information, see "Command String Examples," later in this chapter.

10.	Choose the Continue button.

Setup copies the required files, and the Link Service Configuration dialog box (similar to the one shown in Figure 2.7) appears, listing the entry for this link service.

11.	You can continue to install and configure link services, or you can complete the SNA Server setup.

To continue with installing and configuring link services, choose the Add button and go to the appropriate section for the link service.

To complete the SNA Server setup, choose the Continue button and go to “Completing Setup” later in this chapter.

For information about specifying dial data to be sent to the modem or displayed in a pop-up message, or configuring parameters to match your modem, see the Microsoft SNA Server Administration Guide.

Requirements for Using Server-Stored Numbers

The preceding section tells how to configure an SDLC link service. This section gives specific information about choosing a line type of “Switched: Server-Stored Number” for your SDLC link service.

In order to accept a phone number from SNA Server, your modem must be set up so that it will:

Accept dial commands in ASCII (eight data bits, no parity bit, one stop bit).

Not dial when the DTR signal is raised.

Set Clear to Send (CTS) and Data Set Ready (DSR) to on when ready to accept dial commands.

Set DSR to off after accepting a dial command.

Set DSR to on again when (and only when) the dialed connection is made.

Change to synchronous mode after the dial-up has completed.

Change back to dial-command mode if Data Terminal Ready (DTR) is dropped and raised again.

When SNA Server is sending a phone number to a modem, it ignores modem responses and holds the modem interface signals Select Standby and DTR to off.

The dialing attempt initiated by SNA Server is assumed to have failed if one of the following occurs:

DSR stays on after the dial string has been sent.

The connection time-out expires before DSR comes on to indicate that the call is connected.

For Microgate link services, when you install the link service, default dialer commands are supplied for both incoming and outgoing calls, as displayed in the Microgate Dialer Setup dialog box. If your modem accepts the standard AT command set, these defaults will probably be appropriate. (For an explanation of each of the commands specified in these strings, see your modem documentation.)

When SNA Server creates a dial string to send to a modem, it uses the outgoing command string supplied in Setup as a base, and then appends the Dial Data (phone number) configured in SNA Server Admin, followed by a carriage-return line-feed sequence.


Command String Examples
Installing SNA Servers	23 of 33

Configuring a Link Service

Command String Examples

In the Microgate Dialer Setup dialog box in SNA Server Setup, the following command string is the default for outgoing calls.

AT&F&C1&S1&D3&Q1Q1S0=0DT

As described in the preceding section, the command string forms the base onto which the phone number is appended when SNA Server sends a dial string to a modem.

The elements in the command string have the following effects:

AT is the standard modem command prefix.

&F resets the modem to the factory defaults.

&C1 makes the modem track the status of the Carrier Detect (CD) line.

&S1 makes the modem raise the Data Set Ready (DSR) line after it has dialed.

&D3 makes the modem reset when the Data Transmit Ready (DTR) line drops.

&Q1 makes the modem come up in command mode and switch to synchronous mode when it has dialed. For some modems, this parameter is &M1.

Q1 turns off modem result codes.

S0=0 turns off auto-answer mode, so that the modem is set for outgoing calls.

DT dials the number following it, using tone dialing (DP indicates pulse dialing, used with older exchanges)

In the Microgate Dialer Setup dialog box in SNA Server Setup, the following command string is the default for incoming calls.

AT&F&C1&S1&D3&Q1Q1S0=1

The elements in the command string have the same effects as in the preceding list, except that S0=1 tells the modem to answer the phone after one ring.

For information about specifying the dial string to be sent to a modem that accepts SNA server-stored numbers, see the Microsoft SNA Server Administration Guide.

Notes on the Barr SDLC Link Service

When configuring the Barr SDLC link service, configure the Data Rate field in the Barr SDLC Device Driver Setup dialog box as follows:

When the Line Type is “Switched: SNA Server-Stored Number,” use Data Rate to specify the baud rate used to communicate with the modem in asynchronous mode while sending the dial string and setup commands.

When the T1-SYNC card provides clocking in conjunction with a Barr synchronous modem eliminator cable, use Data Rate to specify the data rate supplied for synchronous communications.


Configuring an X.25 Link Service
Installing SNA Servers	24 of 33

Configuring a Link Service

Configuring an X.25 Link Service

An X.25 link service enables you to connect SNA Server through public or private X.25 packet switching networks to host, peer, or downstream computers. The following illustration shows the X.25 link service.

SNA Server X.25 Link Service

Configuring an X.25 link service involves specifying a number of values including transmission options, channel ranges, data rate, encoding, and line type. Before configuring an X.25 link service, review the values needed for steps 4 – 9 to ensure you have all the information at hand.  For information about the correct settings to use for your X.25 link service, contact your network administrator.

If you are using an IBM SDLC or MPCA adapter, see "SDLC Adapter Notes," earlier in this chapter.

Note

If you have an IBM SDLC adapter or an IBM MCPA adapter, you cannot use a transmission speed greater than 9600 baud for an X.25 connection. These adapters lack a coprocessor, and at high transmission speeds cannot handle full-duplex transmission, which is the type of transmission used by SNA Server X.25 connections.

To configure an X.25 link service

1.	Complete the procedures in the previous sections, so that you access the link service setup dialog box for the X.25 link service you want to configure. The following list reviews the methods for accessing this dialog box:

If this is the first link service you are installing, in the Link Service Installation dialog box (shown in Figure 2.5), select the X.25 link service you want and choose the Install button.

If you are adding this link service after installing others, in the Link Service Configuration dialog box (shown in Figure 2.7), choose the Add button. Then, in the Link Service Installation dialog box (shown in Figure 2.5), select the X.25 link service you want and choose the Install button.

If you have already installed this link service and want to reconfigure it, in the Link Service Configuration dialog box (shown in Figure 2.7), select the X.25 link service you want and choose the Configure button.

An X.25 Link Service Setup dialog box appears. The IBM X.25 Link Service Setup dialog box is shown here.

2.	Either accept the default title, or delete the default in the Title box and type the new title for this link service.

You can use as many as 40 characters for the title.

3.	If the Card Type box is included in the dialog box, select the correct card.

4.	If the Details or Adapter Details button is included in the dialog box, choose it, and confirm or configure settings for the X.25 card. (If you have a Microgate card, you can also change one setting, the DMA channel.) For information, see the documentation for your adapter.

5.	Provide values to configure the transmissions:

Local X.25 Address

The Local X.25 Address contains 15 decimal digits, with no spaces separating the digits. The final 3 digits of the address are used for routing between stations with the same 12-digit address. There is no default.

Default L3 Window Size

The default L3 window size is the maximum number of packets that can be sent  to or received from a remote computer before an acknowledgment is required. This applies only to switched virtual circuit (SVC) connections. The range is from 1 through 7; the default is 2.

Default L3 Packet Size

The default L3 packet size is the maximum length of data in each packet sent to or received from the remote computer through SVCs. This value can be overridden by any value entered in the User Data or Facility Data fields of the X.25 Setup dialog box in SNA Server Admin. Allowed values are 64, 128, 256, and 512; the default is 128.

L2 Window Size

The L2 window size is the number of frames that SNA Server can send to the network without having to wait for an acknowledgment. The range is from 1 through 7; the default is 7.

T1 Timeout (0.1s)

The T1 timeout is the time, in tenths of a second, that the local system should wait for the remote system to respond to a transmission before the local system tries again. Specify a time greater than that needed for relaying frames back and forth between the local and remote systems. The range is from 1 through 100 tenths of a second; the default is 30.

N2 Retry Limit

The N2 retry limit is the number of times to attempt retransmitting data. The range is from 1 through 100; the default is 10.

6.	Select or clear check boxes as appropriate:

Accept Reverse Charge

Accept Reverse Charge indicates whether SNA Server should accept an incoming call with reverse charge facility in the call packet. By default, this setting is off.

Select Standby

Select Standby specifies whether you want your modem standby lines set to on. A standby line is a backup line (usually switched) included on some leased line modems. Check your modem documentation for directions. By default, this setting is off.

Startup Restart

Startup restart indicates whether a restart should be performed each time the link is activated. By default, this setting is on.

Incoming Filter

Incoming Filter determines whether calls to X.25 addresses other than the local one are filtered out. By default, this setting is on.

7.	Specify channel ranges as described in the following list. For more information, see "Guidelines for Assigning Channel Numbers," later in this chapter.

Note

The specification of channel ranges must match your X.25 carrier's configuration for your X.25 link.

Outgoing SVC

Outgoing SVC channel range is the range of switched virtual circuit (SVC) channels used for outgoing calls. Specify the smallest and largest numbers in the range, in the format x – x. For example, 0008 – 0009 is a valid entry.

For the Outgoing SVC channels, specify numbers greater than any PVC, Incoming SVC, or Two-Way SVC channels used by this link service. There is no default.

Two-Way SVC

Two-way SVC channel range is the range of switched virtual circuit (SVC) channels that can be used for either incoming or outgoing calls. Specify the smallest and largest numbers in the range, in the format x – x. For example, 0006 – 0007 is a valid entry.

For the Two-Way SVC channels, specify numbers greater than any Incoming SVC channels but less than any Outgoing SVC channels used by this link service. The default is 0001 – 0004.

Incoming SVC

Incoming SVC channel range is the range of switched virtual circuit (SVC) channels used for incoming calls. Specify the smallest and largest numbers in the range, in the format x – x. For example, 0004 – 0005 is a valid entry.

For the Incoming SVC channels, specify numbers greater than any PVC channels but less than any Two-Way SVC channels used by this link service. There is no default.

PVC

The permanent virtual circuit (PVC) channel range is the range of permanent virtual circuit (PVC) channels used by the computer on the X.25 network. Specify the smallest and largest numbers in the range, in the format x – x. For example, 0001 – 0003 is a valid entry.

This range must be specified if a PVC connection uses the link service. For the PVC channels, specify numbers less than any Incoming SVC, Two-Way SVC, or Outgoing SVC channels used by this link service. There is no default.

8.	Select communications options:

Data Rate

Data Rate is the rate for communications between your modem and the communications adapter, in cases where the modem speed can be set in software.

Select Low if poor quality lines cause errors at the full rate. If you select High, CCITT Line 111 on the V24 interface is set to on. Check your modem documentation for directions. The default is High.

Encoding

Encoding specifies the encoding scheme for transmitting and receiving data. The local computer must use the same encoding scheme as the remote computer. When you connect to a host, your choice must match the option specified in the Line/Group macro.

The options are NRZ (nonreturn to zero) and NRZI (nonreturn to zero inverted). The default is NRZ.

9.	Under Line Type, select the appropriate option:

Leased

Choose this option for a dedicated telecommunications line.

Switched: Modem-Stored Number

Choose this option for a modem that stores a phone number. Make sure that the modem is configured to dial the number when the Data Terminal Ready (DTR) is raised, in conformance with the IEEE RS 232 Modem Specification for line 108.1.

Switched: Manual Dial

Choose this option if you will dial the phone number. SNA Server will prompt you when it is time to dial the number.

10.	If other options are displayed in the dialog box, fill in the appropriate information. For information about the choices offered, choose the Help button.

11.	If the Dialer Settings button is included in the dialog box, choose it, and configure the settings as follows:

COM Port

Select the number of the COM port; for example, for COM1, select 1.

If you are adding a COM port by adding this SDLC card, and you select a new number for that COM port, Setup responds by allowing you to access the appropriate dialog box for configuring the COM port within Windows NT.

The range is from None through 254. The default is None.

Baud Rate

Select the rate of transmission. The range includes relevant values from 75 through 115200. The default is 9600.

Incoming String

Type the string to be sent to the modem when an incoming call is detected. The default is AT&F&C1&S1&D3&Q1Q1S0=1. This string will be appropriate in most situations. For more information, see "Command String Examples," earlier in this chapter.

Outgoing String

Type the string to be sent to the modem when an outgoing call is detected. The default is AT&F&C1&S1&D3&Q1Q1S0=0DT. This string will be appropriate in most situations. For more information, see "Command String Examples," earlier in this chapter.

12.	After completing all the fields in this dialog box, choose the Continue button.

Setup copies the required files, and the Link Service Configuration dialog box (similar to the one shown in Figure 2.7) appears, listing the entry for this link service.

13.	You can continue to install and configure link services, or you can complete the SNA Server setup.

To continue with installing and configuring link services, choose the Add button and go to the appropriate section for the link service.

To complete the SNA Server setup, choose the Continue button and go to “Completing Setup” later in this chapter.

Guidelines for Assigning Channel Numbers

When specifying channel numbers in the X.25 Link Service Configuration dialog box, note that:

Channels must range from 1 through 4096.

The format for specifying channel numbers is x – x. For example, 0001 – 0004 is a valid entry for channel numbers.

There is no requirement for the number of channels a particular switched virtual circuit (SVC) or permanent virtual circuit (PVC) type uses, but the total number of channels among all types must be from 1 through 16.

Channel number ranges must be unique and must not overlap across different connection types.

To accept incoming calls, you need at least one SVC incoming or SVC two-way channel.

To configure more than one channel type, specify channel number values in ascending order: PVCs, incoming SVCs, two-way SVCs, and outgoing SVCs. PVCs do not need to start at channel 1, but they must be set for the lowest channel numbers in this link service. Outgoing SVCs do not need to end at channel 4096, but they must be set for the highest numbers in this link service.


Configuring a DFT Link Service
Installing SNA Servers	25 of 33

Configuring a Link Service

Configuring a DFT Link Service

A DFT link service is used to connect SNA Server to host systems, generally over coaxial cable. DFT stands for distributed function terminal, a type of terminal supported by IBM 3270 control units, in which some of the terminal's functions are controlled by the terminal and some by the control unit. DFT allows multiple sessions, and connects to host systems (or to peer systems via host systems).

The following figure shows the DFT link service.

SNA Server DFT Link Service

To configure a DFT link service

1.	Complete the procedures in the previous sections, so that you access the link service setup dialog box for the DFT link service you want to configure. The following list reviews the methods for accessing this dialog box:

If this is the first link service you are installing, in the Link Service Installation dialog box (shown in Figure 2.5), select the DFT link service and choose the Install button.

If you are adding this link service after installing others, in the Link Service Configuration dialog box (shown in Figure 2.7), choose the Add button. Then, in the Link Service Installation dialog box (shown in Figure 2.5), select the DFT link service and choose the Install button.

If you have already installed this link service and want to reconfigure it, in the Link Service Configuration dialog box (shown in Figure 2.7), select the DFT link service and choose the Configure button.

The IBM DFT Link Service Setup dialog box appears.

2.	Either accept the default title, or choose the Change button.

If you choose the Change button, the Link Service Title dialog box appears; in the Title box, delete the default, type the new title for the link service, and then choose the Continue button.

You can use as many as 40 characters for the title.

3.	Either accept the default base address, or choose the Configure button.

If you choose the Configure button, the dialog box shown in Figure 2.8 appears.

Figure 2.8    Adapter Base Address Dialog Box

In the Base Address box, delete the default, type the new base address, and then choose the Continue button.

The address must be a multiple of hexadecimal 1000; the range is from hexadecimal A0000 through FF000.

4.	For additional adapter cards, choose Add New.

The Adapter Base Address dialog box, similar to the one shown in Figure 2.8, appears.

In the Base Address box, type a multiple of hexadecimal 1000, ranging from hexadecimal A0000 through FF000, and then choose Continue.

Repeat this step for any other cards you are using. You can use up to four cards with this service.

5.	Choose the Continue button.

Setup copies the required files, and the Link Service Configuration dialog box (similar to the one shown in Figure 2.7) appears, listing the entry for this link service.

6.	You can continue to install and configure link services, or you can complete the SNA Server setup.

To continue with installing and configuring link services, choose the Add button and go to the appropriate section for the link service.

To complete the SNA Server setup, choose the Continue button and go to the next section.


Completing Setup
Installing SNA Servers	26 of 33

Completing Setup

From the SNA Server Setup Finished dialog box, you can either exit the Setup program or proceed directly to SNA Server Admin to configure the connections and LUs for your link services. For information on issues that may improve the performance of your SNA Server system, see the information about Registry and environment variables in the Microsoft SNA Server Reference.

SNA Server Setup Finished Dialog Box

To exit Setup and proceed to SNA Server Admin

From the SNA Server Setup Finished dialog box, choose the Admin button.

To exit Setup without going to SNA Server Admin

From the SNA Server Setup Finished dialog box, choose the Exit button.


Installing SNA Servers in an IP Routed Network
Installing SNA Servers	27 of 33

Installing SNA Servers in an IP Routed Network

SNA servers communicate with each other using mailslot broadcast messages to the domain. On a TCP/IP WAN, mailslots are NetBIOS multicast (broadcast) messages, which typically are not propagated across IP routers.

To allow full communication between SNA servers across an IP routed network, set up the SNA servers on computers running Windows NT Advanced Server or Windows NT Server, and make these servers primary or backup domain controllers. Then, on any of the SNA servers, start SNA Server Admin and, from the Options menu, choose Server Broadcasts. In the resulting dialog box, select “Route Server Broadcasts over IP routers.” When this feature is enabled, broadcast messages are propagated across IP routed networks to all primary and backup domain controllers in the Windows NT domain. For more information, see the Microsoft SNA Server Administration Guide.


Preparing an SNA Server to Support Macintosh Clients
Installing SNA Servers	28 of 33

Preparing an SNA Server to Support Macintosh Clients

To prepare an SNA server to support Macintosh clients, a few basic steps are needed. The first set of steps is described in detail in the documentation for Microsoft Services for Macintosh:

1.	Install Services for Macintosh on the Windows NT Advanced Server or Windows NT Server.

2.	Configure Services for Macintosh, which includes specifying the network and zone and carrying out seeding.

The next step is described in detail in the documentation for the Windows NT Advanced Server or Windows NT Server:

Set up standard Windows NT user accounts for the Macintosh users.

The next set of steps is described in detail in the Microsoft SNA Server Administration Guide:

1.	Add Macintosh users, or the groups they are in, to the list recognized by the SNA server.

2.	Assign appropriate LUs to the Macintosh users or to the groups they are in. For 3270 users, assign 3270 LUs or 3270 LU pools; for 5250 users, assign default local and remote APPC LUs, as appropriate.

After preparing the SNA server in this way, you can install and configure emulation software on the Macintosh computer(s).


Modifying or Removing SNA Servers
Installing SNA Servers	29 of 33

Modifying or Removing SNA Servers

When you run Setup after the initial installation, SNA Server detects your configuration and presents the Setup Options dialog box to you. From Setup Options, you can:

Change the configuration of a link service that is already installed.

Add or remove a link service.

Change the role of an SNA server in the domain.

Change client/server protocol selections.

Remove SNA Server.

When removing SNA Server device drivers, such as the IBM SDLC driver and link service, always use SNA Server Setup. Do not use the Network option of the Windows NT Control Panel to remove such drivers; doing so may cause unexpected system events. To correct such a situation, remove and reinstall SNA Server, using SNA Server Setup.

For information about installing or modifying clients, see Chapter 3, "Installing SNA Server Clients."

To view the Setup Options dialog box

1.	In the Windows NT Program Manager, open the SNA Server program group.

2.	Activate the SNA Server Setup icon.

A welcome to SNA Server Setup dialog box appears.

3.	Choose the Continue button.

The dialog box shown in Figure 2.9 appears.

Figure 2.9    Setup Options Dialog Box


Adding or Removing a Link Service
Installing SNA Servers	30 of 33

Modifying or Removing SNA Servers

Adding or Removing a Link Service

You can configure any of the installed link services, or add a link service. If you no longer need a link service, you can remove it.

Important

When removing SNA Server device drivers, such as the IBM SDLC driver and link service, always use SNA Server Setup. Do not use the Network option of the Windows NT Control Panel to remove such drivers; doing so may cause unexpected system events. To correct such a situation, remove and reinstall SNA Server, using SNA Server Setup.

To add, configure, or remove a link service

1.	Under Options in the Setup Options dialog box, shown in Figure 2.9, choose the Links button.

The Link Service Configuration dialog box, similar to the one shown in Figure 2.7, appears.

2.	Choose an appropriate button:

To configure an existing link service, in the Link Services Installed box, select an available link service and then choose the Configure button.

A configuration dialog box, specific to the type of link service you selected, appears.

To add a new link service, choose the Add button.

The Link Service Installation dialog box appears.

To remove a link service, select the link service you want to remove and then choose the Remove button. When the Confirm Link Service Removal dialog box appears, choose the Continue button.

For information about configuring link services, see "Configuring a Link Service" earlier in this chapter.


Changing the Server Role
Installing SNA Servers	31 of 33

Modifying or Removing SNA Servers

Changing the Server Role

You can change the configuration role for an SNA server.

To change the server role

Under Options in the Setup Options dialog box, shown in Figure 2.9, choose the Role button.

The Change SNA Server Role dialog box, shown in Figure 2.4, appears.

For more information on server roles for SNA Server, see “Selecting the Server Role” earlier in this chapter.


Changing Client/Server Protocol Selections
Installing SNA Servers	32 of 33

Modifying or Removing SNA Servers

Changing Client/Server Protocol Selections

You can change client/server protocol selections after installing SNA Server.

To change client/server protocol selections

1.	Under Options in the Setup Options dialog box, shown in Figure 2.9, choose the Protocols button.

The Select Client/Server Protocols dialog box, similar to the one shown in Figure 2.2, appears. Follow the procedures in “Selecting Client/Server Protocols,” earlier in this chapter.

2.	When the Setup Options dialog box reappears, choose the Continue button, and then exit from SNA Server Setup.


Removing SNA Server
Installing SNA Servers	33 of 33

Modifying or Removing SNA Servers

Removing SNA Server

You can remove SNA Server at any time. However, removing SNA Server deletes all of the SNA Server files and directories from your computer, including link service files. To use SNA Server again, you must run Setup to reinstall the files from the beginning.

To remove SNA Server from an entire domain, do the following in the order given:

1.	Stop all the SNA Server components on the network, including SnaBase.

2.	Use SNA Server Setup to remove the client software from all clients.

3.	Use SNA Server Setup to remove the SNA server software from the backup and member SNA servers.

4.	Use SNA Server Setup to remove the SNA server software from the primary server.

To remove SNA Server

1.	Under Options in the Setup Options dialog box, shown in Figure 2.9, choose the Remove button.

The Confirm Removal dialog box appears.

2.	Choose the Continue button.


Installing SNA Server Clients
Chapter 3	1 of 14

Installing SNA Server Clients

This chapter explains how to install, modify, or remove SNA Server clients. Clients can be installed on computers running the following operating systems:

Windows NT or Windows NT Advanced Server version 3.1 or Windows NT Server or Windows NT Workstation version 3.5

Windows version 3.x

MS-DOS

OS/2

For SNA servers, there is no effect if client software exists in the SNA Server home directory.


Clients in Relation to the Domain of Servers
Installing SNA Server Clients	2 of 14

Clients in Relation to the Domain of Servers

Clients can be either local or remote:

Local clients operate on the same network domain as the primary SNA server (the server that contains the configuration file). They issue a mailslot to find a server in their domain. Once they connect to this server, they discover all the other servers in the domain.

Remote clients are not located in the same domain as the primary SNA server. Remote clients explicitly list servers in the remote domain to which they can connect. Once connected to one server, they discover all the other servers in that domain. If you are installing a remote client, you must specify the first server that the client should attempt to connect to, and, optionally, a second server name.

Local and remote clients do not differ in functionality, but only in the method for connecting to the domain of servers.


Information Needed for Client Setup
Installing SNA Server Clients	3 of 14

Information Needed for Client Setup

During the setup process, you will be prompted to supply information about the following:

Whether your computer is local (on the same domain as the SNA servers) or remote (on a different domain from the SNA servers). If remote, you must provide the names of one or two SNA servers in the remote domain.

For MS-DOS – based clients only, the interrupt value from the network card.

For clients not using Microsoft Networking (Named Pipes), the domain name and, if such clients use Banyan VINES, the Banyan StreetTalk group name.


Client Installation and the Network
Installing SNA Server Clients	4 of 14

Client Installation and the Network

Any type of SNA Server client can be installed from a network share; alternatively, Intel-based clients can be installed from floppy disks.

The client software must be run from a hard disk on the client computer, except for clients running Windows version 3.x, which can run the client software from either the local hard disk or a network share.

For more information about using a network share to install clients that will run the client software from the local hard disk, see the next section. For more information about installing client software that will run from a network share, see "Installing Windows-Based Client Software to Run from a Network Share," later in this chapter.


Making Client Installation Available Over the Network
Installing SNA Server Clients	5 of 14

Client Installation and the Network

Making Client Installation Available Over the Network

You can place files in a shared directory on a server to allow client installation over the network.

Note that for Intel-based client computers, client installation can also be carried out from floppy disks. If you want to carry out installation from floppy disks but you only have a CD, use the procedure in "Client Installation from Floppy Disks," later in this chapter, to create the disks.

To make client installation available over the network

1.	On the server from which you want to make client installation available over the network, create and share a directory.

This server can be any kind of server that is accessible over your network. The directory will contain the shared files for client installation. For information about sharing a directory, see the documentation for your server.

2.	If your original distribution medium for SNA Server is the SNA Server CD, skip to the next step. If your original distribution medium for SNA Server is floppy disks, in the directory created in step 1, create a subdirectory for each of the client types you plan to install, as described in the following table:

Operating system used on client		Name of subdirectory to create
Windows NT		winnt
Windows version 3.x		win3x
MS-DOS		msdos
OS/2		os2
3.	Insert the SNA Server CD, or a floppy disk for a client type that you want, into the appropriate drive of a Windows NT-based computer.

4.	If you are using the SNA Server CD, at the command prompt, type a command of the following form:

xcopy d:\clients \\servername\sharename /s /e

For d, substitute the letter of the CD-ROM drive. For servername and sharename, substitute the server name and share name used in step 1.

The directories and files for installing client software are copied to the shared directory. Each type of client software is located in an appropriate subdirectory.

5.	If you are using floppy disks, at the command prompt, type one or more commands, each command corresponding to a type of client that you want to install:

Operating system used on client		Command to type
Windows NT		xcopy d:  \\servername\sharename\winnt /s /e
Windows version 3.x		xcopy d:  \\servername\sharename\win3x /s /e
MS-DOS		xcopy d:  \\servername\sharename\msdos /s /e
OS/2		xcopy d:  \\servername\sharename\os2 /s /e
For d, substitute the letter of the floppy disk drive. For servername and sharename, substitute the server name and share name used in step 1.

For clients that will run Windows NT, Windows version 3.x, or MS-DOS, for each of the installation disks for that client, repeat the process of inserting the disk and typing the command.

The directories and files for installing client software are copied to the shared directory. Each type of client software is located in an appropriate subdirectory.

To install client software from the shared directory, connect to it and run Setup from the appropriate subdirectory for the client type you want. For instructions on using Setup to install clients, see the next sections.


Client Installation from Floppy Disks
Installing SNA Server Clients	6 of 14

Client Installation from Floppy Disks

You can install SNA Server client software from floppy disks if the client computer is Intel-based. For information about preparing to install from a network share, see the preceding section. For information about client software that will always be run from a network share, see "Installing Windows-Based Client Software to Run from a Network Share," later in this chapter.

If you have an SNA Server CD, but do not have floppy disks, you can use the following procedure to create them.

To create floppy disks from the SNA Server CD

1.	Obtain the correct number of blank, high-density, formatted 5.25-inch or 3.5inch disks:

Operating system	Number of disks needed
Windows NT	3
Windows version 3.x	2
MS-DOS	2
OS/2	1
2.	Insert the SNA Server CD into the CD-ROM drive.

3.	In File Manager or at the command prompt, change to the drive containing the CD.

4.	Change to the \I386\DISKS directory on the CD.

5.	Insert a floppy disk in an appropriate drive.

6.	Copy all files and subdirectories from the appropriate directory on the CD to the root directory of the floppy disk:

Operating system	Directory to copy from
Windows NT	DISK1
Windows version 3.x	WIN3X_1
MS-DOS	MSDOS_1
OS/2	OS2
7.	Remove the floppy disk.

8.	For clients running Windows NT or Windows version 3.x, repeat steps 5 – 7 to copy more directories to additional floppy disks:

For Windows NT-based clients: the DISK2 and DISK3 directories.

For clients running Windows version 3.x: the WIN3X_2 directory.

For MS-DOS – based clients: the MSDOS_2 directory.


Installing Clients
Installing SNA Server Clients	7 of 14

Installing Clients

Any type of SNA Server client can be installed from a network share; alternatively, Intel-based clients can be installed from floppy disks. To create floppy disks or a network share from which to install clients, see the preceding sections.

For important background information, including information about how local and remote clients work, see "Clients in Relation to the Domain of Servers" and "Information Needed for Client Setup," earlier in this chapter.

For a listing of the system and memory requirements required for SNA Server clients, see Chapter 1, "Overview."


Installing a Windows NT-Based Client
Installing SNA Server Clients	8 of 14

Installing Clients

Installing a Windows NT-Based Client

For important background information about installing clients, see the preceding sections of this chapter.

To install a Windows NT-based client

1.	You can install from a network share or, for Intel-based clients, from floppy disks:

To install from a network share, create the share as described in "Making Client Installation Available Over the Network," earlier in this chapter. Then, on the client computer, connect to the share.

To start the client Setup program, type a command as shown in the following  table:

Hardware	Command to type
Intel-based	drive:\winnt\i386\setup
MIPS	drive:\winnt\mips\setup
Alpha AXP	drive:\winnt\alpha\setup
In this command, drive represents the drive used to connect to the clientinstallation share.

An introductory Setup dialog box appears.

To install from disk, put the first SNA Server disk in a disk drive, type the following command (substituting the appropriate drive letter for drive), and press ENTER:

drive:\setup

An introductory Setup dialog box appears.

Note

Choose the Help button to get assistance any time you are using a dialog box. When you do, Setup displays a text box explaining the choices you have at that point and the procedure to complete the dialog box.

2.	Choose the Continue button.

If you are installing from floppy disks, the Server/Client Selection dialog box appears; choose the Client button.

The dialog box shown in Figure 3.1 appears.

Figure 3.1    Installation Path Dialog Box

3.	Accept or change the default installation path:

To accept the default path, choose the Continue button.

To change the default path, in the Install to box, delete the default and type the full path for the new destination, and then choose the Continue button. (It is best to specify an empty directory, so that Setup will not inadvertently overwrite a file needed by another program.)

If Setup detects more than one client/server protocol on your client, the dialog box shown in Figure 3.2 appears. Otherwise, the SNA Client Mode dialog box, shown in Figure 3.3, appears; continue with step 8.

Figure 3.2    Select Client/Server Protocols Dialog Box

4.	If the Select Client/Server Protocols dialog box appears, select one, several, or all of the check boxes:

Microsoft Networking (Named Pipes)

Novell NetWare (IPX/SPX)

Banyan VINES

TCP/IP

If the system you are installing on does not include one or several of the client/server protocols, the corresponding check boxes are unavailable.

5.	Choose the Continue button.

If you did not select the Microsoft Networking (Named Pipes) option, the Network Domain Name dialog box appears. Otherwise, the SNA Client Mode dialog box, shown in Figure 3.3, appears; continue with step 8.

6.	If the Network Domain Name dialog box appears, type the network domain name and choose the Continue button.

For a TCP/IP network, you can specify the name in any of several forms:

The domain name used in the Windows NT domain.

The host name plus the TCP domain name. This is an example:

host1.location.com

If you use a name in this form, you must also configure the computer to map from the name to an IP address. This can be done with the Domain Name System (DNS) resolver or by adding an appropriate entry to a file called HOSTS. For information about either of these, see your TCP/IP documentation.

The IP address. This is an example:

11.123.45.67

If you are using Banyan VINES (and not Microsoft Networking), the StreetTalk Group Name dialog box appears.

Otherwise, the SNA Client Mode dialog box, shown in Figure 3.3, appears; continue with step 8.

7.	If the StreetTalk Group Name dialog box appears, in the Group Name box, type the StreetTalk group name (with an @ sign between the two parts of the name), and choose Continue.

If you leave this box blank, Setup uses the group name of the user currently logged on in the Banyan VINES network.

If you type the group name into the dialog box, type the same name for all the servers and clients. If you use the default, make sure that the group name of the user logged on in the Banyan VINES network during installation of SNA Server is always the same group name, regardless of whether client or server software is being installed. For more information, see "Specifying the StreetTalk Group Name on a Banyan VINES Network" in Chapter 2.

The dialog box shown in Figure 3.3 appears.

Figure 3.3    SNA Client Mode Dialog Box

8.	Specify the client mode:

Local: If this client is located in the same network domain as the primary SNA server (the server that contains the configuration file), choose the Continue button.

The Optional Administration Program dialog box appears.

Remote: If this client is not located in the same domain as the primary SNA server (the server that contains the configuration file), carry out the following:

a.	Select the Remote option button, and choose the Continue button.

The Remote SNA Server Names dialog box appears.

b.	In the Primary box, type the name of the first SNA server that the client should attempt to connect to.

c.	Optionally, in the Backup box, type the name of the second SNA server that the client should attempt to connect to.

Once connected to one server, a remote client discovers all the other servers in that domain.

d.	Choose the Continue button.

The Optional Administration Program dialog box appears.

9.	To avoid installing SNA Server Admin, in the Optional Administration Program dialog box, choose the Continue button. To install SNA Server Admin, select the Install Administration Program check box, and then choose the Continue button.

The Review Settings dialog box appears.

10.	Choose the Review button to review the configuration, or the Continue button to allow SNA Server to begin copying the files.

If you are installing from floppy disks, you will be prompted to insert floppy disks as they are needed.

When installation is complete, the SNA Client Setup Finished dialog box appears.

11.	Choose the Exit button.

The SNA Server Client (Common) program group appears in the Windows NT Program Manager window.


Installing a Client Running Windows Version 3.x
Installing SNA Server Clients	9 of 14

Installing Clients

Installing a Client Running Windows Version 3.x

The following section tells how to install Windows-based client software to run from the hard disk of the Windows-based computer. For information about client software that will run from a network share, see "Installing Windows-Based Client Software to Run From a Network Share," later in this chapter.

Installing Windows-Based Client Software to Run Locally

For important background information about installing clients, including information about how local and remote clients work, see "Clients in Relation to the Domain of Servers" and "Information Needed for Client Setup," earlier in this chapter.

For important information about specifying the number of active connections on a client running Windows version 3.x with the LAN Manager redirector, see "Maximum Network Connections on Clients Using LAN Manager," later in this chapter.

For information about client software that will run from a network share, see "Installing Windows-Based Client Software to Run From a Network Share," later in this chapter.

To install client software to run locally on a computer running Windows version 3.x

1.	At the computer on which you are installing the client software, close any Windows version 3.x system applications that are running.

2.	You can install from a network share or, for Intel-based clients, from floppy disks:

To install from a network share, create the share as described in "Making Client Installation Available Over the Network," earlier in this chapter. Then, on the client computer, connect to the share.

From the Windows Program Manager File menu, choose Run. In the Command Line box, type the following command to start the client Setup program:

drive:\win3x\setup

In this command, drive represents the drive used to connect to the clientinstallation share.

An introductory Setup dialog box appears.

To install from floppy disk, put the first disk for clients running Windows 3.x in a disk drive; then, from the Windows Program Manager File menu, choose Run. In the Command Line box, type the following command to start the client Setup program:

drive:\setup

In this command, drive represents the floppy disk drive.

An introductory Setup dialog box appears.

Note

Choose the Help button to get assistance any time you are using a dialog box. When you do, Setup displays a text box explaining the choices you have at that point and the procedure to complete the dialog box.

3.	Choose the Continue button.

The Installation Path dialog box, similar to the dialog box shown in Figure 3.1, appears.

4.	Accept or change the default installation path:

To accept the default path, choose the Continue button.

To change the default path, in the Install to box, delete the default and type the full path for the new destination, and then choose the Continue button. (It is best to specify an empty directory, so that Setup will not inadvertently overwrite a file needed by another program.)

If Setup detects more than one client/server protocol on your client, the Select Client/Server Protocols dialog box, shown in Figure 3.2, appears. Otherwise, the SNA Server Location dialog box, shown in Figure 3.4, appears; continue with step 9.

5.	If the Select Client/Server Protocols dialog box appears, select one of the check boxes:

Microsoft Networking (Named Pipes)

Novell NetWare (IPX/SPX)

Banyan VINES

TCP/IP

If the system you are installing on does not include one or several of the client/server protocols, the corresponding check boxes are unavailable.

6.	Choose the Continue button.

If you did not select the Microsoft Networking (Named Pipes) option, the Network Domain Name dialog box appears. Otherwise, the SNA Server Location dialog box, shown in Figure 3.4, appears; continue with step 9.

7.	If the Network Domain Name dialog box appears, type the network domain name and choose the Continue button.

For a TCP/IP network, you can specify the name in any of several forms:

The domain name used in the Windows NT domain.

The host name plus the TCP domain name. This is an example:

host1.location.com

If you use a name in this form, you must also configure the computer to map from the name to an IP address. This can be done with the Domain Name System (DNS) resolver or by adding an appropriate entry to a file called HOSTS. For information about either of these, see your TCP/IP documentation.

The IP address. This is an example:

11.123.45.67

If you are using Banyan VINES (and not Microsoft Networking), the StreetTalk Group Name dialog box appears.

Otherwise, the SNA Server Location dialog box, shown in Figure 3.4, appears; continue with step 9.

8.	If the StreetTalk Group Name dialog box appears, in the Group Name box, type the StreetTalk group name (with an @ sign between the two parts of the name), and choose Continue.

If you leave this box blank, Setup uses the group name of the user currently logged on in the Banyan VINES network.

If you type the group name into the dialog box, type the same name for all the servers and clients. If you use the default, make sure that the group name of the user logged on in the Banyan VINES network during installation of SNA Server is always the same group name, regardless of whether client or server software is being installed. For more information, see "Specifying the StreetTalk Group Name on a Banyan VINES Network" in Chapter 2.

The dialog box shown in Figure 3.4 appears.

Figure 3.4    SNA Server Location Dialog Box

9.	To specify the location of the SNA servers in the domain:

Local Domain: If this client is located in the same network domain as the primary SNA server (the server that contains the configuration file), choose the Continue button.

Remote Domain: If this client is not located in the same domain as the primary SNA server (the server that contains the configuration file), carry out the following:

a.	Select the Remote Domain option button.

b.	In the Primary Server box, type the name of the first SNA server that the client should attempt to connect to.

c.	Optionally, in the Backup Server box, type the name of the second SNA server that the client should attempt to connect to.

Once connected to one server, a remote client discovers all the other servers in that domain.

d.	Choose the Continue button.

SNA Server installs the necessary files. If you are installing from floppy disks, you will be prompted to insert a second floppy disk when it is needed.

When installation is complete, the Setup Complete dialog box appears.

10.	Choose the Exit button.

The SNA Server Client program group appears in the Windows Program Manager window.

Installing Windows-Based Client Software to Run from a Network Share

This section tells how to install Windows-based client software to run from a network share. For information about client software that will run from the hard disk of the Windows-based computer, see the previous section.

SNA Server clients running the Windows version 3.x operating system can be set up to run the SNA Server client software from a network share. Such a client may, but does not have to, run its operating system (Windows 3.x) from a network share. If a shared directory is used for the Windows system, it should be a different directory from the one used for the SNA Server client software.

When installing SNA Server client software for systems that will run the software from a network share, be sure to log on with a user name that has read and write access to the Windows system directories, wherever they are located. You must be logged on in this way in order to carry out steps 3 through 8 of the following procedure:

1.	On the server from which the SNA Server client software will be run, create and share a directory for the software.

2.	At one of the computers that will run SNA Server client software from the network share, connect to the share, specifying an appropriate drive letter (such as g: or x: ).

3.	On the same computer as step 2, start SNA Server Setup in one of two ways:

Insert the SNA Server CD or the appropriate floppy disk in the drive of the client system. Then, from the File menu in Program Manager, choose the Run command, and carry out the following:

If using a floppy disk, type  drive:setup /a

If using the CD, type  drive:\clients\win3x\setup /a

In this command, substitute the letter for the floppy disk drive or CD-ROM drive for drive. After typing the command, choose OK.

Create a share as described in "Making Client Installation Available Over the Network," earlier in this chapter. Then, on the client computer, open the File menu in Program Manager, choose the Run command, and type the following:

\\servername\sharename\win3x\setup /a

In this command, servername and sharename specify the appropriate share.

With the /a (administrative) option, SNA Server Setup installs the software needed for Windows clients to run SNA Server from a network share; at the same time, Setup creates the first client.

4.	Carry out the installation. When prompted for the destination for the SNA Server client software, type the network drive letter assigned in step 2.

5.	On any other Windows client that will run the SNA Server client software from the network share, connect to the shared directory created in step 1, specifying an appropriate drive letter (such as g: or x:).

6.	On the client chosen for the previous step, start SNA Server Setup in one of the two ways explained in step 3, and type one of the following:

For installing from a floppy disk, type

drive:setup /n

For installing from a CD-ROM drive, type

drive:\clients\win3x\setup /n

For installing across the network, type

\\servername\sharename\win3x\setup /n

With the /n (network) option, SNA Server Setup creates a client based on Windows version 3.x that runs SNA Server client software from a network share.

7.	Carry out the installation. When prompted for the location of SNA Server files on a network server, type the network drive letter assigned in step 5.

8.	Repeat steps 5 through 7 for each additional client that will run the client software from the network share.

Removing a Windows-Based Client that Runs from a Network Share

When removing access to Windows-based SNA Server client software that is run from a network share, be sure to log on with a user name that has read and write access to the Windows system directories, whether they are on the local system or in a network share. You must log on in this way to do either of the following:

To remove the capability for a particular client system to run SNA Server from a network share, on the client, follow the usual procedure for removing Windows-based client software. See "Removing SNA Server Clients," later in this chapter.

To remove SNA Server client software from a network share (so that no clients can run from that share), from a client, start SNA Server Setup with the /a option, using one of the methods described in step 3 of the previous procedure. Then follow the usual procedure for removing Windows-based client software. See "Removing SNA Server Clients," later in this chapter.


Maximum Network Connections on Clients Using LAN Manager
Installing SNA Server Clients	10 of 14

Installing Clients

Maximum Network Connections on Clients Using LAN Manager

Before you start SNA Server client software on a computer running MS-DOS or Windows version 3.x with the LAN Manager redirector, you should take note of how many network connections are in use. Unexpected behavior may occur if you exceed the number of maximum supported active network connections; some systems are known to fail. The standard maximum number for total connections is 10, and SNA Server requires a minimum of 2.

The workaround is to delete a few network connections before starting the SNA Server client software. Note that this is not an issue with Windows for Workgroups or NetWare.

If necessary, the numresources entry in the [workstation] section of LANMAN.INI can be increased to allow a greater number of connections. For example:

[workstation]

 numresources = 13

SNA Server typically requires two to four numresources, and each network connection requires one; the number specified in LANMAN.INI should be adjusted accordingly. For more information, see your LAN Manager administrative documentation.


Installing an MS-DOS – Based Client
Installing SNA Server Clients	11 of 14

Installing Clients

Installing an MS-DOS – Based Client

For important background information about installing clients, including information about how local and remote clients work, see "Clients in Relation to the Domain of Servers" and "Information Needed for Client Setup," earlier in this chapter. For information about the installation medium, see "Making Client Installation Available Over the Network" or "Client Installation from Floppy Disks," earlier in this chapter.

Note that for MS-DOS – based clients, you will need to know the interrupt value for the network card.

For important information about specifying the number of active connections on a client running MS-DOS with the LAN Manager redirector, see the previous section.

To install an MS-DOS–based client

1.	You can install from a network share or from floppy disks:

To install from a network share, create the share as described in "Making Client Installation Available Over the Network," earlier in this chapter. Then, on the client computer, connect to the share.

To start the client Setup program, type:

drive:\msdos\setup

In this command, drive represents the drive used to connect to the clientinstallation share.

An introductory Setup screen appears.

To install from disk, put the disk for MS-DOS – based clients in a disk drive, type the following command (substituting the appropriate drive letter for drive), and press ENTER:

drive:\setup

An introductory Setup screen appears.

2.	From the introductory screen, press ENTER to begin installing the MS-DOS – based client.

The Home Directory Path screen appears.

3.	Accept or change the default installation path:

To accept the default path, press ENTER.

To change the path, delete the default path, type the full path for the new destination, and then press ENTER. (It is best to specify an empty directory, so that Setup will not inadvertently overwrite a file needed by another program.)

If Setup detects more than one client/server protocol on your computer, the Client/Server Protocols screen appears. Otherwise, the Remote Operation screen appears; continue with step 8.

4.	If the Client/Server Protocols screen appears, select one of the options in the list:

Microsoft Networking (Named Pipes)

Novell NetWare (IPX/SPX)

Banyan VINES

5.	Press ENTER.

If you did not select the Microsoft Networking (Named Pipes) option, the Network Domain Name screen appears. Otherwise, the Remote Operation screen appears; continue with step 8.

6.	If the Network Domain Name screen appears, type the network domain name, and then press ENTER.

If you are using Banyan VINES (and not Microsoft Networking), the StreetTalk Group Name screen appears.

Otherwise, the Remote Operation screen appears; continue with step 8.

7.	If the StreetTalk Group Name screen appears, in the Group Name box, type the StreetTalk group name (with an @ sign between the two parts of the name), and choose Continue.

If you leave this box blank, Setup uses the group name of the user currently logged on in the Banyan VINES network.

If you type the group name into the screen, type the same name for all the servers and clients. If you use the default, make sure that the group name of the user logged on in the Banyan VINES network during installation of SNA Server is always the same group name, regardless of whether client or server software is being installed. For more information, see "Specifying the StreetTalk Group Name on a Banyan VINES Network" in Chapter 2.

The Remote Operation screen appears.

8.	To specify the location of the SNA servers in the domain:

No remote operation: If this client is located in the same network domain as the primary SNA server (the server that contains the configuration file), select No remote operation, and then press ENTER.

Remote operation: If this client is not located in the same domain as the primary SNA server (the server that contains the configuration file), carry out the following:

a.	Select Remote operation, and then press ENTER.

b.	In the Primary Remote Server Name screen, type the name of the first SNA server that the client should attempt to connect to, and then press ENTER.

c.	Optionally, in the Backup Remote Server Name screen, type the name of the second SNA server that the client should attempt to connect to.

Once connected to one server, a remote client discovers all the other servers in that domain.

d.	Press ENTER.

The Operating Environment screen appears.

9.	To install the MS-DOS – based client on an MS-DOS system, press ENTER. To install the MS-DOS – based client on a Windows version 3.x system, select Set up MS-DOS client on a Windows 3.x system, and then press ENTER.

An MS-DOS – based client can run as either an MS-DOS application or as a character application under Windows version 3.x. For a client running as an MS-DOS application, the SnaBase is started automatically from the AUTOEXEC.BAT file. By contrast, for a client running as a character application under Windows version 3.x, you must manually start the SnaBase in a Windows version 3.x MS-DOS session.

If you are running Windows Enhanced Mode with Windows version 3.0, the Background option must be selected. This is configured through the Enhanced option in the Control Panel.

The LAN Adapter Interrupt Level screen appears.

10.	To specify the interrupt level for the LAN adapter you are using, select the correct value from the list, and then press ENTER.

The Number of SNA Servers screen appears.

11.	Specify the number of servers to connect to:

To specify that you are connecting to one SNA server, press ENTER.

 To change the number of SNA servers to which you are connecting, delete the default, type the correct number of servers, and then press ENTER.

SNA Server adjusts several file entries to prepare the network for the SNA Server client. These entries depend on the number of servers to which you will be connecting. Connecting to fewer servers reduces the memory usage; however, you should select the actual number of servers you will be using.

The Backup Extension screen appears.

12.	Specify the file extension to be used when SNA Server saves backup copies of your AUTOEXEC.BAT and of any other *.INI files that may be changed:

To use a file extension of .OLD, press ENTER.

To change the file extension for the backup files, type the correct extension, and then press ENTER.

The Confirm Setup Execution screen appears.

13.	Review your choices or allow the copying of files to begin:

To review your Setup choices, press ENTER.

To allow the copying of files to begin, select Execute Setup and then press ENTER.

SNA Server installs the necessary files. When installation is complete, the Setup Completed Successfully screen appears.

14.	To exit Setup, press ENTER.

15.	Restart your computer so that the changes will take effect.

PC Support Router Replacement

This section describes the SNA Server Router (Router), a replacement for the IBM AS/400 PC Support program router component. Router provides the software interface to an APPC network used by several popular 5250 emulators, including the 5250 emulator provided with IBM PC Support/400. This reduces the configuration required at the client. It also allows the client to communicate through an SNA server instead of directly with an AS/400, so that the client can use standard transports such as IPX/SPX, NetBEUI, or any other LAN or WAN transport. Without the SNA Server Router, the client must communicate directly with an AS/400 over DLC.

For information about PC Support, refer to your IBM PC support manual(s).

Router provides the same interface as the PC Support program router component. It offers the following advantages:

Unlike the PC Support program router component, Router allows an MS-DOS–based client to use a single protocol (such as NetBEUI). With PC Support, an MS-DOS–based client must use the DLC protocol in addition to any other protocol it uses.

With Router, the DLC protocol does not need to be loaded.

Note

Many 5250 emulators do not require the IBM PC Support router (or the SNA Server Router), but instead use the Windows APPC API. Examples of 5250 emulators that do not require the PC Support router are the SNA Server 5250 Applet and other 5250 emulators listed in the SNA Server Companion Product Catalog.

Before you can use Router, you must take the following steps:

1.	Install at least one SNA server.

2.	Install the MS-DOS–based SNA Server client software on the client that will use Router.

3.	If the PC Support utilities (file transfer, shared folders, IBM DOS 5250) are needed, install the IBM PC Support program software on the client as well.

Note

If you are using Windows for Workgroups, you must use a certain system configuration for IBM PC Support or any other software that requires the PC Support Router API. For details, see "PC Support Used with Windows for Workgroups," later in this chapter.

To install SNA Server Router

1.	Copy the ROUTER.EXE and INITRTR.EXE files to your PC Support directory.

2.	Comment out the line that loads the COMNDIS program in your AUTOEXEC.BAT file. For example:

rem c:\snaserv\rbin\comndis.com 2

Note

After the line that loads COMNDIS is commented out, you must include the IRQ numbers of your network adapter cards in the command line that starts Router. For information, see "Using the router Command to Start SNA Server Router," later in this chapter.

3.	Comment out the following lines in your CONFIG.SYS file:

rem device=path\DXMA0MOD.SYS

rem device=path\DXMx0MOD.SYS

where path is the path of the directory where these drivers are located, and the x in DXMx0MOD.SYS can be either c for Token Ring or e for Ethernet.

Since the Router only replaces the router component of the PC Support program, you must always load the EIMPCS.SYS driver in your CONFIG.SYS file, along with any other driver options you need. For example, if you want to use shared folders, you may also need to load the ECYDDX.SYS driver. The following is an example of a CONFIG.SYS file for an MS-DOS–based SNA Server client:

DEVICE=C:\PCS\EIMPCS.SYS

DEVICE=C:\PCS\ECYDDX.SYS

DEVICE=C:\DOS\SETVER.EXE

DEVICE=C:\WINDOWS\HIMEM.SYS

DEVICE=C:\WINDOWS\EMM386.EXE  NoEMS  X=D800-DFFF

DOS=HIGH,UMB

FILES=3.0

SHELL=C:\DOS\COMMAND.COM C:\DOS\  /p

LASTDRIVE=Z

STACKS=9,256

DEVICE=C:\LANMAN.DOS\DRIVERS\PROTMAN\PROTMAN.DOS /i:C:\LANMAN.DOS

DEVICE=C:\LANMAN.DOS\DRIVERS\ETHERNET\UB\UBNEI.DOS

The following list describes the drivers that are loaded with PC Support and their function. Use the rmvpcs command to remove any drivers that you do not need.

Driver	Purpose
EIMPCS.SYS	Memory management
ECYDDX.SYS	Shared folders
Using the router Command to Start SNA Server Router

To start the SNA Server Router, you must first start the SnaBase service, then use the router command with appropriate options. This section shows the syntax to use with the router command, then gives a detailed procedure for starting the SNA Server Router.

The router command uses the following syntax:

router [/cconfigpath] [/bufs=buffer_count] [/irq=irq#,irq#]ORrouter  [/d]

where

/cconfigpath

Specifies the PC Support configuration file path. For example, to indicate that your configuration file path is C:\PCS\CONFIG.AS4, you would type:

router /cc:\pcs\config.as4

The default path is CONFIG.PCS.

/bufs=buffer_count

Specifies the number of communication buffers Router allocates. For buffer_count, specify an integer from 24 through 64.

Each buffer takes approximately 280 bytes of memory. With MS-DOS version 5.0 or later, Router allocates the memory for communication buffers from upper memory if there are enough free upper memory blocks available. Increase the number of buffers to at least 48 if you transfer or copy files (with the shared folders program).

The default for buffer_count is 24.

/irq=irq#,irq#

Specifies the IRQ numbers (in decimal) of your network adapter cards. Separate multiple IRQ numbers with commas. You must specify this option if you remove (or comment out) the COMNDIS line from your AUTOEXEC.BAT file.

/d

Removes the SNA Server Router.

Use in the following procedure to start the Router with the router command.

To start SNA Server Router

1.	On the MS-DOS–based SNA Server client, start the SnaBase by typing

snabase

2.	Change to your PC Support directory. For example, type:

cd \pcs

3.	Start SNA Server Router by typing

router [options]

where options are as described in the preceding section.

4.	Start the other PC Support components that you need, or start the Windows environment and use Windows-based 5250-emulation programs, such as RUMBA [image] /400.

Note

If you are running Windows version 3.x, the SnaBase and SNA Server Router should be started before Windows version 3.x is started.

Also, if you are using Windows for Workgroups, you must use a certain system configuration for IBM PC Support or any other software that requires the PC Support Router API. For details, see "PC Support Used with Windows for Workgroups," later in this chapter.

Modifying the Router Configuration File

Router is configured through the PC Support configuration file. You can use the default filename for this file, CONFIG.PCS, or you can rename your configuration file and specify the new pathname in the /c option of the router command, as described in the previous section.

The following CONFIG.PCS identifiers are used by Router. RTLN and TRLI are required, and the rest of the identifiers are optional:

INTL

Specifies the interrupt number used by the PC Support program components when they communicate with Router. Specify a hexadecimal number from 60 through 68. This identifier is optional. If you do not specify this identifier, 68 is used. If you use extended memory manager, do not use interrupt 67.

RTCU

Specifies the ID to be used if a user ID is not specified for the system on the TRLI identifier. This identifier is optional. If you do not specify this identifier, you are prompted for the user ID and password.

RTDN

Provides the name of the AS/400 system used to start the conversation if a name is not specified. This system name must be one of the remote LU names in the SNA Server configuration. This identifier is optional. If you do not specify this identifier, the default is the first system specified with TRLI.

RTLN

Provides the name that uniquely identifies this computer in the APPN [image] network. This identifier is required. It is a 17-character name that must be the same as the fully-qualified LU name of your local LU in the SNA server configuration. For example:

rtln appn.user1

The name must contain the period between the two parts of the fully-qualified network name.

RTYP

Specifies the router type. This identifier is optional. If specified, RTYP must have a value of ITRN (local area network). The ITRN is an IBM-defined value for the RTYP.

TRLI

Specifies the link identification identifier. This identifier is required. More than one identifier can be specified for each AS/400 you communicate with. The following example shows the full syntax of the TRLI identifier:

trli system name for link,system address,DSAP, user id, MAXOUT, MAXIN, TIMERT1,TIMERT2,TIMERTI

where system name for link is the name of the remote LU (AS/400 name) you connect to and user id is used to sign on to an AS/400. The system address is required, but this value is ignored by the SNA Server Router. The system address may be specified as 000000000000.

The user id is optional. If this parameter is not specified, Router uses the common user ID or prompts for a user ID.

Removing Router

After you install Router, you can remove it any time; however, you must first unload other PC Support components (workstation function, shared folders, and so on) by using the rmvpcs command.

To remove SNA Server Router

Type

router /d

For additional information about PC Support functions, refer to your IBM PC support manual(s).

Using the Default LUs Specified in the PC Support Configuration

On a client running MS-DOS or Windows version 3.x, if you want to use the default LUs specified in the PC Support configuration file, you must set a variable in the SNA.INI file (for MS-DOS) or the WIN.INI file (for Windows version 3.x):

OverrideDefaultLU=YES

When this variable is set to YES, SNA Server will use the default APPC LUs configured for PC Support; these LUs are specified on the RTLN line of the CONFIG.PCS file. Otherwise, SNA Server will use the default APPC LUs configured in SNA Server; these LUs are assigned to users or groups through SNA Server Admin or through the SNA Server command-line interface ( snacfg ).

PC Support Used with Windows for Workgroups

There are certain limitations in using the SNA Server Windows-based client software with IBM PC Support functions (for AS/400 connectivity) with Windows for Workgroups versions 3.1 and 3.11:

If you are running the real mode (MS-DOS) redirector provided with Windows for Workgroups, and running the PC Support functions in MS-DOS (that is, Windows for Workgroups is not loaded), and you are not running over the IPX/SPX transport, then you must add the entry MAXCMDS=10 to the [networks] section of the SYSTEM.INI file, and start the redirector with the following command:

net start full

With Windows for Workgroups version 3.1, you must use the following configuration when using PC Support functions or other software that requires the PC Support router API:

Use the SNA Server MS-DOS – based client, not the Windows-based client.

Run Windows for Workgroups in standard mode, not enhanced mode.

With Windows for Workgroups version 3.11, the following rules apply for AS/400 connectivity:

You can use the PC Support functions by starting all the necessary SNA Server MS-DOS – based client components (SNABASE, ROUTER) from an MS-DOS command prompt of Windows (or in MS-DOS by exiting from Windows for Workgroups). Windows programs cannot access the router API in this configuration; you must use only the IBM PC Support functions (such as the "WSF" function for 5250 emulation).

When using SNA Server client software to communicate with an AS/400, you should use applications (including 5250 emulators) that use the Windows APPC API, and avoid applications that use the IBM PC Support router API.

Note that using the Windows APPC API means that terminate-and-stay-resident software is avoided, making the local system environment simpler and more robust.

Many 5250 emulators do not require the IBM PC Support router, but instead use the Windows APPC API. Examples of 5250 emulators that do not require the PC Support router are the SNA Server 5250 Applet and other 5250 emulators listed in the SNA Server Companion Product Catalog.


Installing an OS/2 Client
Installing SNA Server Clients	12 of 14

Installing Clients

Installing an OS/2 Client

To install an OS/2 client

1.	From the PM Desktop Manager Main Group, select OS/2 Full Screen or OS/2 Window.

2.	You can install from a network share or from floppy disks:

To install from a network share, create the share as described in "Making Client Installation Available Over the Network," earlier in this chapter. Then, on the client computer, connect to the share.

To start the client Setup program, type:

drive:\os2\setup

In this command, drive represents the drive used to connect to the client-installation share.

An introductory Setup screen appears.

To install from disk, put the disk for OS/2-based clients in a disk drive, type the following command (substituting the appropriate drive letter for drive), and press ENTER:

drive:\setup

An introductory Setup screen appears.

3.	From the introductory screen, press ENTER to begin installing the OS/2 client.

The Home Directory Path screen appears.

4.	Accept or change the default installation path:

To accept the default path, press ENTER.

To change the path, delete the default, type the full path for the new destination, and then press ENTER. (It is best to specify an empty directory, so that Setup will not inadvertently overwrite a file needed by another program.)

The Remote Operation screen appears.

5.	To specify the location of the SNA servers in the domain:

No remote operation: If this client is located in the same network domain as the primary SNA server (the server that contains the configuration file), select No remote operation, and then press ENTER.

Remote operation: If this client is not located in the same domain as the primary SNA server (the server that contains the configuration file), carry out the following:

a.	Select Remote Operation, and then press ENTER.

b.	In the Primary Remote Server Name screen, type the name of the first SNA server that the client should attempt to connect to, and then press ENTER.

c.	Optionally, in the Backup Remote Server Name screen, type the name of the second SNA server that the client should attempt to connect to.

Once connected to one server, a remote client discovers all the other servers in that domain.

d.	Press ENTER.

The Backup Extension screen appears.

6.	Specify the file extension to be used when SNA Server saves backup copies of your AUTOEXEC.BAT and of any other *.INI files that may be changed:

To use a file extension of .OLD, press ENTER.

To change the file extension for the backup files, delete the default, type the correct extension, and then press ENTER.

The Confirm Setup Execution screen appears.

7.	Review your choices or allow the copying of files to begin:

To review your Setup choices, press ENTER.

To allow the copying of files to begin, select Execute Setup and then press ENTER.

SNA Server installs the necessary files. When installation is complete, the Setup Completed Successfully screen appears.

8.	To exit Setup, press ENTER.

9.	Restart your computer so that the changes will take effect.


Modifying Clients
Installing SNA Server Clients	13 of 14

Modifying Clients

Once you have installed an SNA Server client, you may want to modify the options you selected during Setup. For example, you may want to change the client operation from remote to local, or vice versa. For a remote client, you may also want to change the server(s) that the client initially tries to connect to.

When you run Setup, it determines whether there is a version of SNA Server already installed on the computer. If so, Setup assumes that you want to modify or remove the client software. For information about removing clients, see the next section.

To modify an SNA Server client running Windows NT or Windows version 3.x

1.	Double-click on the SNA Server Client Setup icon (located by default in the SNA Server program group).

An introductory Setup dialog box appears.

2.	Choose the Continue button.

A dialog box similar to the one shown in Figure 3.5 appears.

Figure 3.5    Setup Options Dialog Box

3.	For a client running Windows version 3.x, select Setup System Files only and choose the Continue button.

For a client running Windows NT, choose the Configure button.

Setup presents a selection of the dialog boxes used to install the SNA Server client. For information about how to complete these dialog boxes, see "Installing Clients" earlier in this chapter.

4.	Complete the dialog boxes with the required modifications to the client configuration.

Setup copies the files, and the Setup Complete dialog box appears.

5.	Choose the Exit button.

6.	Restart your computer so the changes will take effect.

To modify an SNA Server client running MS-DOS or OS/2

1.	Use the procedures for installing clients described earlier in this chapter to invoke Setup for the type of client you are modifying (MS-DOS–based or OS/2).

2.	From the introductory screen, press ENTER.

The Home Directory Path screen appears.

3.	To accept the default path of C:\SNA, press ENTER. To change the path, delete the default path, type the full path for the SNA client files, and then press ENTER.

The Select Function screen appears.

4.	In the Select Function screen, select "Install SNA Client and set up system files," and then press ENTER.

5.	Change the setup options as directed by the resulting screens.

6.	When the Confirm Setup Execution screen appears, and you are satisfied with the values you entered, select Execute Setup, and then press ENTER.

Setup carries out the changes.

7.	When the Setup Completed Successfully screen appears, press ENTER.

8.	Restart your computer so that the changes will take effect.


Removing SNA Server Clients
Installing SNA Server Clients	14 of 14

Removing SNA Server Clients

Use the Setup program to remove SNA Server client software from a client computer. For information about removing software so that a Windows-based client cannot run from a network share, see "Removing a Windows-Based Client that Runs From a Network Share," earlier in this chapter.

Note

Always use Setup for removing client software; do not use other methods such as deletion commands.

Once you remove an SNA Server client, you will have to use Setup to reinstall the SNA Server client software.

To remove an SNA Server client running Windows NT or Windows version 3.x

For information about removing software so that a Windows-based client cannot run from a network share, see also "Removing a Windows-Based Client that Runs From a Network Share," earlier in this chapter.

1.	Double-click on the SNA Server Client Setup icon (located by default in the SNA Server program group).

An introductory Setup dialog box appears.

2.	Choose the Continue button.

A Setup Options dialog box, similar to the one shown in Figure 3.5, appears.

3.	For a client running Windows version 3.x, select Remove the SNA Client and choose the Continue button.

For a client running Windows NT, choose the Remove button.

4.	When the Confirm Removal dialog box appears, choose the Continue button.

5.	If a Setup Message dialog box appears, choose the OK button to force the SNA components to stop.

6.	When the Remove Complete dialog box appears, choose OK.

7.	Restart your computer so that the changes will take effect.

To remove an SNA Server client running MS-DOS or OS/2

1.	Start Setup from a floppy disk or from a network share, as described in "Installing an MS-DOS–based Client" or "Installing an OS/2 Client," earlier in this chapter.

Important

When removing an SNA Server client running MS-DOS or OS/2, start Setup from a floppy disk or a network share, not from the SNA root directory on the hard drive.

2.	From the introductory screen, press ENTER.

The Home Directory Path screen appears.

3.	To accept the default path of C:\SNA, press ENTER. To change the path, delete the default path, type the full path for the SNA client files, and then press ENTER.

The Select Function screen appears.

4.	To remove the SNA client, select Remove SNA Client, and then press ENTER. The Confirm Remove Execution screen appears.

5.	To begin removing the files for the client, select Execute Removal and then press ENTER.

SNA Server removes the necessary files. When removal is complete, the Setup Completed Successfully screen appears.

6.	To exit Setup, press ENTER.

7.	Restart your computer so that the changes will take effect.


Upgrading to SNA Server Version 2.1
Chapter 4	1 of 7

Upgrading to SNA Server Version 2.1

This chapter describes the process of upgrading to SNA Server 2.1 from either of the following:

Comm Server 1.x

SNA Server 2.0

The chapter tells the steps for upgrading, and provides important information about how to make your upgrade go smoothly.


Upgrading from Comm Server 1.x
Upgrading to SNA Server Version 2.1	2 of 7

Upgrading from Comm Server 1.x

This section includes information about:

The advantages of upgrading Comm Server 1.x clients.

The order of steps for upgrading from Comm Server Comm Server 1.x to SNA Server 2.1, including the steps for the conversion of a configuration file from Comm Server 1.x to SNA Server format.

For more information about SNA Server configuration files, see the Microsoft SNA Server Administration Guide.

Using the MS-DOS – based Comm Server 1.x 3270 emulator through a connection on a version 2.1 SNA server

Using the MS-DOS – based Comm Server 1.x 3270 emulator with version 2.1 SNA Server client software


Advantages of Upgrading Comm Server 1.x Clients
Upgrading to SNA Server Version 2.1	3 of 7

Upgrading from Comm Server 1.x

Advantages of Upgrading Comm Server 1.x Clients

SNA Server clients provide the following advantages over Comm Server 1.x clients:

Faster response. Improved client-server protocols work more efficiently over slow Remote Access Service or TCP/IP links.

Improved security. Security is maintained by the SNA server(s) instead of the client.

Novell NetWare client support that works with integrated security with Windows NT. The transports used by NetWare clients, called native IPX/SPX client transports, are supported by SNA Server.

Removal of mailslot routing between clients and servers. This ensures more reliable communication between clients and servers.

Integration of event logging. Events on SNA Server clients are recorded in a centralized log on an SNA server, instead of being recorded locally.


Steps for Upgrading from Comm Server 1.x
Upgrading to SNA Server Version 2.1	4 of 7

Upgrading from Comm Server 1.x

Steps for Upgrading from Comm Server 1.x

To upgrade an installation from Comm Server 1.x to SNA Server, you must install SNA Server software on all Comm Server 1.x servers in a given domain. It is recommended that you also install SNA Server client software on your Comm Server 1.x clients. However, these clients can connect to a version 2.1 SNA server, if SNA Server Admin has been used to enable the "DCA/Microsoft Comm Server client support" option in the Server Broadcasts dialog box. For details, see the procedure in this section.

Important

When you upgrade to SNA Server, it is recommended that you create a new domain for the new SNA servers as they are upgraded. Avoid having Comm Server 1.x servers and SNA servers in the same domain, because they cannot function together. If one or more Comm Server 1.x servers are started in a domain with one or more SNA servers, conflicting messages will be sent regarding the roles of the servers — which server is to load the configuration and which configuration file is current. A probable result is that one or more Comm Server 1.x servers in the domain will stop functioning.

When you upgrade, if you have client applications that use the Comm Server 1.x APIs, these applications will continue to function with SNA Server.

Configurations created on a Comm Server 1.x server can easily be converted for use with SNA Server. Save the Comm Server 1.x configuration and security files, and copy them to the SNA server after installation, as described in the next section. When SNA Server Admin is started for the first time with the Comm Server 1.x configuration and security files in place, the configuration will be converted to the file format used by SNA Server.

Note

If you are using the MS-DOS – based Comm Server 1.x 3270 emulator through a connection on an SNA Server, see "Copying Files for the Comm Server 1.x 3270 Emulator" later in this chapter.

To upgrade a domain from Comm Server 1. x software to SNA Server software

1.	To locate the Comm Server configuration and security files, on a server containing the files, change to the COMCFG subdirectory of the Comm Server root directory.

The configuration file has a filename of COM.CFG. The security file has a filename of COM.SEC.

2.	Copy the COM.CFG and COM.SEC files to a location that will not be affected by the deletion of Comm Server software and the installation of the Windows NT Advanced Server or Windows NT Server operating system and the SNA Server software.

3.	Install the Windows NT Advanced Server or Windows NT Server operating system on the computers that will be SNA servers.

As you install Windows NT, it is recommended that you create a new domain to hold the new SNA servers. For information about planning the domain(s) for the Windows NT systems that will be SNA servers, see your Windows NT documentation and "Planning SNA Server Domains" in Chapter 1. For information about installing the Windows NT Advanced Server or Windows NT Server operating system, see your Windows NT documentation.

Important

When you upgrade to SNA Server, it is recommended that you create a new domain for the new SNA servers as they are upgraded. Avoid having Comm Server 1.x servers and SNA servers in the same domain, because they cannot function together.

4.	On the Windows NT-based server containing user accounts for the new domain, configure any user and group accounts needed for users who will access SNA Server.

For information about user and group accounts, see your Windows NT documentation.

5.	Install SNA Server on all computers that will be SNA servers in the new domain.

For information about designating one primary SNA server and one or more backup or member SNA servers in the domain, see "Selecting the Server Role" in Chapter 2.

6.	Before starting SNA Server Admin on any computer, copy the COM.CFG and COM.SEC files (saved in step 2) to the configuration directory of the primary SNA server in the domain. This directory is called \SNAroot\SYSTEM\CONFIG (where SNAroot represents the SNA Server root directory) on the primary SNA server and is also shared as \\servername\COMCFG (where servername is the name of the primary SNA server).

When a primary SNA server is installed, Setup automatically shares \SNAroot\SYSTEM\CONFIG as \\servername\COMCFG on that server.

7.	Start SNA Server Admin on the primary SNA server in the domain.

SNA Server Admin converts the Comm Server 1.x configuration file to SNA Server format before loading the file as the current configuration.

8.	From the File menu, choose Save Configuration.

9.	In SNA Server Admin, for each connection in the configuration, assign a link service.

For information about assigning a link service for a connection, see the Microsoft SNA Server Administration Guide.

10.	Add users to the list recognized by SNA Server.

For information about adding users to this list, see the Microsoft SNA Server Administration Guide.

11.	Assign LUs to SNA Server users and groups.

For information about assigning LUs to users, see the Microsoft SNA Server Administration Guide.

12.	From the File menu, choose Save Configuration.

13.	Start other SNA servers as needed.

For information about starting SNA servers, see the Microsoft SNA Server Administration Guide.

14.	To ensure support of all clients, carry out one of the following:

Install SNA Server client software on all former Comm Server 1.x client systems.

For information about installing client software, see Chapter 3, "Installing SNA Server Clients."

If you choose not to upgrade all your Comm Server 1.x clients, on an SNA server, start SNA Server Admin and, from the Options menu, choose Server Broadcasts. Then, from the Server Broadcasts dialog box, select DCA/Microsoft Comm Server client support, and choose OK.

This option allows version 2.1 SNA servers to support Comm Server 1.x client systems. However, it decreases the efficiency of the SNA servers by a potentially significant amount. With the option enabled, servers must send out twice as many broadcasts — both the older type of broadcasts expected by Comm Server clients, and the newer type used by SNA server clients.

If you temporarily leave some Comm Server 1.x clients in your installation, after removing them, you should disable the DCA/Microsoft Comm Server client support option. This will increase efficiency on the SNA servers. For more information, see the Microsoft SNA Server Administration Guide.


Copying Files for the Comm Server 1.x 3270 Emulator
Upgrading to SNA Server Version 2.1	5 of 7

Upgrading from Comm Server 1.x

Copying Files for the Comm Server 1.x 3270 Emulator

Before using the MS-DOS – based Comm Server 1.x 3270 emulator through a connection on an SNA server, either obtain an upgraded version of the emulator from Digital Communications Associates, Inc. (DCA), or carry out the following procedure for copying the necessary files. Additionally, if you are using the MS-DOS – based Comm Server 1.x 3270 emulator with SNA Server client software, and you have not obtained an upgraded version of the emulator, see the next section.

To copy files necessary for the MS-DOS – based Comm Server 1.x 3270 emulator

1.	Make sure that there is a server available that has the Comm Server server software on it.

Note

Do not start a Comm Server server in the same domain as an SNA server.

2.	On the primary SNA server in the domain where the Comm Server 1.x 3270 emulator will be used, create a share called COMMSRV.

For example, if the primary SNA server is called SNA1, the share you create will be called \\SNA1\COMMSRV. It is recommended that the COMMSRV share be a new, empty directory on the SNA server.

For information about creating a share, see your Windows NT documentation.

3.	From the root directory of the COMMSRV share created in step 2, create a subdirectory called DAT.

4.	Repeat steps 2 and 3 for each backup SNA server in the domain.

5.	Connect to the share called \\commservername\COMMSRV, where commservername is the name of the server that has the Comm Server software on it.

The COMMSRV share exists on all servers on which the Comm Server server software has been installed.

6.	From the DAT directory under \\commservername\COMMSRV, copy all files to the DAT directories under the COMMSRV shares on the primary and backup SNA servers.

For example, if the server with Comm Server software is called COMM1, and the primary or a backup SNA server is called SNA1, you will copy files from \\COMM1\COMMSRV\DAT\*.* to \\SNA1\COMMSRV\DAT.

There are more than 200 files to be copied.

7.	Disconnect from the \\commservername\COMMSRV share.

8.	Ensure that the COMMSRV share on the primary or backup SNA servers will be available whenever an MS-DOS – based Comm Server 1.x 3270 emulator will be running in that domain.

When the MS-DOS – based Comm Server 1.x 3270 emulator runs, it accesses the files in the DAT directory of the COMMSRV share on the primary SNA server (or a backup SNA server, if the primary is not functioning).

Note

The MS-DOS – based Comm Server 1.x 3270 emulator should run with local style files only.

For more information about using the MS-DOS – based Comm Server 1.x 3270 emulator with SNA Server client software, see the next section.

Using the MS-DOS – Based Comm Server 1.x 3270 Emulator with Client Software

If you are using the MS-DOS – based Comm Server 1.x 3270 emulator with SNA Server client software, it is recommended that you obtain an upgraded version of the emulator from DCA. Otherwise, you must carry out the following procedure, in addition to the procedure in the preceding section.

Note

After this procedure is carried out, the client will not support LUA applications.

To copy files necessary to use the MS-DOS – based Comm Server 1.x 3270 emulator with SNA Server client software

1.	Insert the SNA Server installation disk for MS-DOS – based clients into a disk drive on the client system.

2.	Copy the CSBASE.EXE file from the installation disk to the SNA Server root directory on the client system.

3.	Load the AUTOEXEC.BAT file of the client system into a text editor, search for SNABASE.EXE, and replace it with CSBASE.EXE.

4.	Save AUTOEXEC.BAT, and restart the client system.

For more information about compatibility between SNA Server and Comm Server 1.x, see the preceding sections of this chapter and the Microsoft SNA Server Administration Guide.


Upgrading from SNA Server Version 2.0
Upgrading to SNA Server Version 2.1	6 of 7

Upgrading from SNA Server Version 2.0

This section provides important information about upgrading from SNA Server version 2.0 to SNA Server version 2.1.

In order to make a transition from SNA Server version 2.0 to SNA Server version 2.1, you may want to have both versions of SNA servers running in a domain. This can be done, but should be done only temporarily. The following factors should be kept in mind when running one or more version 2.0 SNA servers in the same domain with version 2.1 SNA servers:

The version 2.0 SNA server(s) should be upgraded as soon as possible.

For information about upgrading a domain of SNA servers from version 2.0 to version 2.1, see the next section.

The primary SNA server (the server containing the primary configuration file) must use version 2.1.

In SNA Server Admin, in the Server Broadcasts dialog box, the option called "SNA Server 2.0 servers in the same domain" must be enabled. For details, see the next section.

SNA Server Admin can only be run from version 2.1 SNA servers or clients.

The version 2.0 SNA servers must be upgraded with the latest SNACFG.DLL patch.

New features available in version 2.1 may not work reliably while the version 2.0 SNA server(s) are running. For example, if the SNA Server administrative permission configured for a particular user is No Access, only the version 2.1 SNA servers would prevent access to the snacfg (command-line) program. The version 2.0 SNA servers in that domain would allow the user to run snacfg.


Upgrading a Domain of SNA Servers from Version 2.0
Upgrading to SNA Server Version 2.1	7 of 7

Upgrading from SNA Server Version 2.0

Upgrading a Domain of SNA Servers from Version 2.0

For background information about the upgrade process, see the preceding section.

To upgrade a domain of SNA servers from version 2.0 to version 2.1

1.	On the primary SNA server, start SNA Server Admin.

2.	From the File menu, choose Backup.

The Save Configuration As dialog box appears.

3.	Select a drive and/or directory for the configuration file, avoiding the current SNA Server directories.

4.	Specify an appropriate filename for the backup configuration file.

5.	Choose OK.

6.	Stop the primary SNA server.

7.	Exit from SNA Server Admin.

If the event Viewer, the Performance Monitor, or a TN3270 gateway is running, it is recommended that you exit from (stop) these also.

8.	While still on the primary SNA server, start SNA Server Setup (version 2.0), and use it to remove the SNA Server version 2.0 software.

9.	Insert the SNA Server version 2.1 CD or the first installation disk in the appropriate drive, and install SNA Server version 2.1 from it.

10.	Start SNA Server Admin (version 2.1).

11.	From the File menu, choose Restore.

The Restore Configuration From dialog box appears.

12.	Select the same drive, directory, and filename selected earlier in this procedure.

13.	Choose OK.

The configuration created with SNA Server version 2.0 is loaded on the version 2.1 SNA server.

14.	From the Options menu, choose Server Broadcasts.

The Server Broadcasts dialog box appears.

15.	Under SNA Server 2.0 and Comm Server support, select "SNA Server 2.0 servers in the same domain."

This option allows version 2.1 SNA servers to work with version 2.0 SNA servers in the same domain. However, it decreases the efficiency of the version 2.1 SNA servers by a potentially significant amount. With the option enabled, version 2.1 SNA servers must send broadcasts on Microsoft Networking or Novell NetWare once every minute. With the option disabled,  version 2.1 SNA servers can send broadcasts only as needed, and can limit broadcasts to the network operating system selected in the installation process.

16.	Choose OK.

17.	From the File menu, choose Save Configuration.

18.	On each of the other servers in the domain, remove SNA Server version 2.0 and install SNA Server version 2.1.

If you temporarily leave some version 2.0 SNA servers in your installation, when you do remove them, you should disable the "SNA Server 2.0 servers in the same domain" option. This can increase efficiency significantly on the SNA servers. For more information, see the Microsoft SNA Server Administration Guide.