Contents
Contents for SNA Server Setup Help

  Overview

  Installing SNA Server

  Installing Link Services

  Configuring Link Services

  Installing an SNA Server Client

  Installing Windows-Based Client Software to Run Across the Network

  Changing Setup Options After Installation


Contents (Expanded)
Contents for SNA Server Setup Help

  Overview

  Welcome to SNA Server Setup

  Using SNA Server Help

  Using Dialog Boxes

  Planning SNA Server Domains

  File System Choices and Security

  SNA Server Components

  SNA Server Sponsor Connections

  Installing SNA Server

  Installing Link Services

  Configuring Link Services

  Installing an SNA Server Client

  Installing Windows-Based Client Software to Run Across the Network

  Changing Setup Options After Installation


Contents (Expanded)
Contents for SNA Server Setup Help

  Overview

  Installing SNA Server

  Selecting the Installation Type

  Choose Licensing Mode

  Recording Identifying Information

  Specifying the Setup Installation Path

  Selecting Client/Server Protocols

  Specifying the Network Domain Name

  Specifying the StreetTalk Group Name

  Selecting the SNA Server Role

  Support for 16-bit SNA Applications on Windows NT

  Completing Setup

  Installing Link Services

  Configuring Link Services

  Installing an SNA Server Client

  Installing Windows-Based Client Software to Run Across the Network

  Changing Setup Options After Installation


Contents (Expanded)
Contents for SNA Server Setup Help

  Overview

  Installing SNA Server

  Installing Link Services

  Installing a Link Service

  Installing Other Link Services

  Configuring Link Services

  Installing an SNA Server Client

  Installing Windows-Based Client Software to Run Across the Network

  Changing Setup Options After Installation


Contents (Expanded)
Contents for SNA Server Setup Help

  Overview

  Installing SNA Server

  Installing Link Services

  Configuring Link Services

  Selecting a Link Service to Configure

  Configuring a DEMO SDLC Link Service

  Configuring a DLC 802.2 Link Service

  Configuring an SDLC Link Service

  Configuring an X.25 (QLLC) Link Service

  Configuring a DFT Link Service

  Configuring a Distributed Link Service

  Installing an SNA Server Client

  Installing Windows-Based Client Software to Run Across the Network

  Changing Setup Options After Installation


Contents (Expanded)
Contents for SNA Server Setup Help

  Overview

  Installing SNA Server

  Installing Link Services

  Configuring Link Services

  Installing an SNA Server Client

  Installing a Client Over the Network

  Selecting the Installation Type

  Specifying the Setup Installation Path

  Selecting Client/Server Protocols on the Client

  Specifying the Network Domain Name

  Specifying the StreetTalk Group Name

  Specifying Client Mode

  Specifying Remote SNA Server Names

  Installing Optional Components

  EHNAPPC API and CA/400 Support for Win 3.x Clients

  Support for 16-bit SNA Applications on Windows NT

  Completing SNA Server Client Setup

  Installing Windows-Based Client Software to Run Across the Network

  Changing Setup Options After Installation


Contents (Expanded)
Contents for SNA Server Setup Help

  Overview

  Installing SNA Server

  Installing Link Services

  Configuring Link Services

  Installing an SNA Server Client

  Installing Windows-Based Client Software to Run Across the Network

  Installing Clients to Run SNA Server from a Network Share

  Removing Clients that Run SNA Server from a Network Share

  Changing Setup Options After Installation


Contents (Expanded)
Contents for SNA Server Setup Help

  Overview

  Installing SNA Server

  Installing Link Services

  Configuring Link Services

  Installing an SNA Server Client

  Installing Windows-Based Client Software to Run Across the Network

  Changing Setup Options After Installation

  Changing Setup Options on an SNA Server

  Changing Setup Options on a Client


Welcome to SNA Server Setup

Microsoft SNA Server combines client-server architecture with the power and productivity of the Windows NT Server. By using SNA Server, you can establish connections with remote computers, such as IBM mainframes, AS/400(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.

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 supports the following types of connections:

DLC 802.2

Token-Ring or Ethernet connections using 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.

Twinax

Twinaxial connections to AS/400 systems.

Channel

Connections that provide direct channel attachment to mainframe systems.

In addition, an SNA Server can distribute any of these link services, allowing a remote SNA Server to connect to the host using Distributed Link Service. For example, a remote SNA Server in a branch office can use Distributed Link Service to connect to an AS/400 via the Twinax connection of a local SNA Server.

About SNA Server Setup

The SNA Server Setup program (Setup) is a graphical interface that allows you to:

Install, configure, and remove SNA Server.

Install, configure, and remove link services.

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.

After you have installed SNA Server and the link services, you use the SNA Server Administration program (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.

To use Setup, you must be logged on as an Administrator on the Windows NT system, 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.

See Also

Using Dialog Boxes

Planning SNA Server Domains

SNA Server Components

SNA Server Sponsor Connections


3270 terminal emulation

The use of software that allows a microcomputer to act as a 3270 terminal, displaying information from a host system (mainframe). Emulation software can also allow a microcomputer to send print jobs from a host system to a printer connected to the microcomputer.


APPC

Advanced Program-to-Program Communications. A method for allowing programs to communicate directly with each other, across a network or within a single system. APPC uses a type of logical unit (LU) called LU 6.2 and allows transaction programs (TPs) to engage in peer-to-peer communications in an SNA environment. APPC is also the communication method used for 5250 emulation.


CPI-C

Common Programming Interface for Communications. A method for allowing programs to engage in peer-to-peer communications within an SNA environment.


5250 terminal emulation

The use of software that allows a microcomputer to act as a 5250 terminal interacting with an AS/400 system.


LUA

Logical Unit Application. A conventional LU application, or the interface that these applications use. LUA allows clients to communicate with host applications using LU 0, 1, 2, or 3 protocols.


downstream system

A client such as an IBM Communications Manager/2 system that can access host connections available on an SNA server. Even though such clients do not use the SNA Server client/server interface, they can use a downstream connection and a downstream LU to communicate with the host via an SNA server. The SNA server passes the information between the downstream system and the host. With SNA Server, downstream systems appear to the host as logical units, not physical units.


dialog boxes

Windows displayed by the system or application to solicit a response from the user. The user must provide a response before the program can continue.


Recording Identifying Information

You can record identifying information in your SNA Server software.

To record identifying information in SNA Server software

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

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

3	In the box marked Product ID, type the product identification number, available on the inside back cover of the Microsoft SNA Server Installation Guide.

By entering the Product ID, 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.

4	Choose Continue.

The Confirm License Information dialog box appears.

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

6	In the Confirm License Information dialog box, choose OK.

The Installation Path dialog box appears.


Specifying the Setup Installation Path

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

To accept the default path

In the Installation Path dialog box, choose Continue.

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

To change the installation path

1	In the Install To box of the Installation Path dialog box, delete the default path.

2	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.

3	Choose Continue.

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


Installing a Link Service

You can install any of the link services listed as Available Link Services in the Link Service Installation dialog box; you can also install a link service provided by a third-party software vendor. 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.

To install a link service

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

2	Choose Install.

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

Note  When carrying out an action from any of the list boxes in Setup, you can also double-click on the item you want to act on.

If the link service you need is not listed in the Available Link Services box, you can install other link services from disk or specify the network path where a link service can be found.

To install other link services

From the Link Service Installation dialog box, choose Other.

The Link Service Import dialog box appears.


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, you can install it from disk or specify the network path where it can be found.

To install a link service from drive A (the default drive)

In the Link Service Import dialog box, choose Continue.

Setup looks in drive A for other link services. The Link Service Installation dialog box 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, delete the default drive.

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

3	Choose Continue.

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


Selecting a Link Service to Configure

Once you have installed a link service, you must configure it. If you would like to install additional services, you can return to the Link Service Installation dialog box. You can also remove a link service after installing it.

To select a link service to configure

1	In the Link Services Installed box of the Link Service Configuration dialog box, select a link service.

2	Choose Configure.

A link service configuration dialog box appears, specific to the link service you selected: DLC 802.2, SDLC, X.25 (QLLC), DFT, or Demo Link Service.

To add a new link service

From the Link Service Configuration dialog box, choose Add.

The Link Service Installation dialog box appears.

To make a link service available to Distributed Link Service on other SNA Servers

In the Link Service Configuration dialog box, select a link service and then choose Distribute.

A link services that is accessible by Distributed Link Service on other SNA Servers is displayed in the Link Services Installed list box preceded by (D). To stop making the link service available to Distributed Link Service on other SNA Servers, select the link service and then choose Distribute.

The 802.2 Link Service cannot support more than one 802.2 connection to the same MAC address (that is, to the same host) at the same time, whether the connections originate from the local or a remote SNA Server.  The 802.2 protocol specification does not permit two distinct connections to have the same Source MAC, Source SAP, Destination MAC and Destination SAP.  Because of this, you must configure a different 802.2 link service for each SNA Server PU connected to a given host, and each link service must use a different Source SAP value.

When you make an 802 link service available to Distributed Link Service on other SNA Servers, it cannot be used by the local SNA Server, and is not visible in SNA Admin on the local machine.

To remove a link service

1	In the Link Services Installed box of the Link Service Configuration dialog box, select a link service.

2	From the Link Service Configuration dialog box, choose Remove.

The Confirm Link Service Removal dialog box appears.

See Also

Configuring a Demo SDLC Link Service

Configuring a DLC 802.2 Link Service

Configuring an SDLC Link Service

Configuring an X.25 (QLLC) Link Service

Configuring a DFT Link Service

Configuring a Distributed Link Service


Remote Link Services Example

To provide hot backup using a link service named SNASdlc1 on a server named SNA001 and using a link service named SNADLC3 on a server named SNA002, enter the following in the Remote Link Services box:

\\SNA001\SNASdlc1;\\SNA002\SNADLC3


Configuring a Distributed Link Service

Using Distributed Link Service, an SNA Server can use a link service on another SNA Server as though it were installed on the local SNA Server.

Distributed Link Service:

Allows multiple SNA Servers to share a single adapter (such as a channel adapter).

Supports load balancing across multiple Distributed Link Services.

Supports hot backup because the Distributed Link Service can select alternate remote servers when a remote link fails.

Allows a branch SNA Server that would otherwise connect to the host over a wide-area network link type (such as X.25 or SDLC) to connect instead over TCP/IP. This is especially useful when a routed WAN is the path between the branch and the host.

To configure a Distributed Link Service

1	In the Distributed Link Service Setup dialog box, select the type of link the Distributed Link Service represents. You can specify the link type only when adding a new Distributed Link Service.

2	In the Service Names box, type the names of the remote link services the Distributed Link Service represents. The format of a service name is \\server\servicename, specifying the remote server name and the name of the link service on the remote server. Multiple service names must be of the same link type. If you enter more than one service name, separate the service names with a semicolon (;). Example

The link services specified in the Service Names box do not have to be installed on the remote server, but Distributed Link Service will support active connections only if at least one of the link services is activated and available to be distributed when the connection is activated.

Both the SNA Server running Distributed Link Service and the remote SNA Server providing the actual link service must be running at least one of the following protocols:

TCP/IP

IPX/SPX

Banyan VINES


The name of the link service as shown in the Properties dialog box for the connection using the link service. To view the Properties dialog box for a connection, in SNA Admin, double-click the connection.


Making a Link Service Available to Be Distributed

Use the Link Service Configuration dialog box to make link services available to a Distributed Link Service on a remote SNA Server.

To make a link service available to be distributed

In the Link Service Configuration dialog box, select a link service, and then choose Distribute.

Link services that are accessible to Distributed Link Service on other SNA Servers are displayed in the Link Services Installed list box preceded by (D).

The 802.2 Link Service cannot support more than one 802.2 connection to the same MAC address (that is, to the same host) at the same time, whether the connections originate from the local or a remote SNA Server.  The 802.2 protocol specification does not permit two distinct connections to have the same Source MAC, Source SAP, Destination MAC and Destination SAP.  Because of this, you must configure a different 802.2 link service for each SNA Server PU connected to a given host, and each link service must use a different Source SAP value.

When you make an 802 link service available to Distributed Link Service on other SNA Servers, it cannot be used by the local SNA Server, and is not visible in SNA Admin on the local machine.


Configuring a DEMO SDLC Link Service

To configure a DEMO SDLC Link Service connection

1	In the DEMO SDLC Link Service Setup dialog box, select the script file that you would like to install for this SDLC connection:

3270 Continuous Demo

3270 File Transfer Demo

3270 Logon Demo

AS/400 Demo

Important  If you plan to install multiple demonstrations, note which demonstration script you have chosen for each Service Name (SnaDEMO1 for 3270 Continuous Demo, SnaDEMO2 for 3270 File Transfer Demo, and so on). You will need this information later when configuring the connection.

2	Choose the Continue button.

The supplied scripts are automatically copied to the SNARoot\SYSTEM directory by Setup.

The Link Service Configuration dialog box appears, listing the entry for this link service.

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

To continue installing and configuring link services, choose the Add button and select the link service to add.

Note  A separate DEMO SDLC Link Service connection must be created and configured for each demonstration script you install.

To complete the SNA Server setup, choose the Continue button.

The connections for the DEMO SDLC Link Services installed will need to be configured for the demonstration scripts that were specified for those connections. This configuration is done in the SNA Server Admin graphical interface. Please see Chapter 2 of the Microsoft SNA Server Enhancements Guide for procedures.


3270 Continuous Demo

Choose this option for an emulation of 3270 flash. (Flash is a test transaction program which runs on the host, continuously sending screenfuls of data at the emulator. The 3270 continuous demo script emulates this behavior.) This option can also be used when the client emulator is connected to the SNA Server running the link service across a Downstream (DSPU) connection.


3270 Logon Demo

Choose this option for an emulation of 3270 logon and logoff to a mainframe computer.


AS/400 Demo

Choose this option for a demonstration of a 5250 emulation session on an AS/400 computer. This demo script provides a 5250 loop script as well the ability to demonstrate SQL queries to an AS/400 database through a 5250 session and through the new ODBC/DRDA driver.


3270 File Transfer Demo

Select this option for an emulation of a 3270 File Transfer. This demo emulates the receipt of a 1MB binary file from VM. Note you must have 1MB of free disk space to successfully complete the file transfer.


Configuring a DLC 802.2 Link Service

A DLC 802.2 link service allows SNA Server to communicate with host, peer, or downstream computers over token ring and Ethernet LANs.

For specific information about using an IBM token ring adapter, see the Microsoft SNA Server Installation Guide.

To configure a DLC 802.2 link service

1	To change the default title, in the Title box, delete the default, and type the new title for this link service.

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

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

3	In the Local Service Access Point (SAP) box, type the local SAP.

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

4	Choose Continue.

Setup copies the required files, and the Link Service Configuration dialog box appears, listing the entry for this link service.


  DLC 802.2

Data Link Control or 802.2. The logical link control protocol used for communication over a token ring or Ethernet network. The 802.2 protocol is an IEEE standard.


SAP address

Service access point address. A value that codes for access to certain services on an 802.2 connection within an SNA network.


Configuring a DFT Link Service

A DFT link service is used to connect SNA Server to host systems, generally over coaxial cable.

To configure a DFT link service

1	To change the default title, choose Change.

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 Continue.

2	To change the value of the base address, choose Configure.

The Adapter Base Address dialog box appears.

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

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

3	For additional adapter cards, choose Add New.

The Adapter Base Address dialog box appears.

In the Base Address box, type a multiple of hexadecimal 1000, ranging from hexadecimal A0000 through hexadecimal 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 Continue.

Setup copies the required files, and the Link Service Configuration dialog box appears, listing the entry for this link service.


 DFT

Distributed function terminal. A type of intelligent 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. Allows multiple sessions; connects to host systems, or to peer systems via host systems. DFT terminals are often connected using coaxial cable.


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 switched or leased telecommunications lines.

For specific information about using IBM SDLC and MPCA adapters and Microgate SDLC adapters, see the Microsoft SNA Server Installation Guide.

To configure an SDLC link service

1	To change the title for this service, in the Service Title box, delete the default, and type the new title.

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

2	In the Card Type box, select the card you will be using.

Note  If the card is an IBM SDLC, IBM MPCA, or Microgate card, or any other SDLC card that does not contain a coprocessor, and you want to use a transmission speed greater than 9600 baud, select select half-duplex and not full-duplex in SNA Server Admin. Adapters that lack a coprocessor cannot handle full-duplex transmission at high transmission speeds.

3	Under Line Type, select the appropriate option:

Leased

Switched: Server-Stored Number

Select this option only 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

Routines Used with Server-Stored Numbers

Switched: Modem-Stored Number

Switched: Manual Dial

4	If you would like the line to use constant RTS, select the Constant RTS check box. See Note About Constant RTS.

5	If the Dialer Settings button is included in the dialog box, you can choose it and configure dialer settings.

6	Choose Continue.

Setup copies the required files, and the Link Service Configuration dialog box appears, listing the entry for this link service.


 SDLC

Synchronous Data Link Control. 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.


Leased

Choose this option for a dedicated telecommunications line. The line can be a point-to-point leased line or a multidrop leased 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).


Requirements for Using Server-Stored Numbers

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.


Routines Used with Server-Stored Numbers

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.

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.


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.


constant RTS

Constant Request To Send. An option that 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 About Constant RTS

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.)


switched SDLC line

A standard dial-up telephone line used for synchronous data link control (SDLC) connections.


leased SDLC line

A telecommunications line committed solely to use by synchronous data link control (SDLC) connections. The line may be used for point-to-point connections or multidrop connections.


Configuring an X.25 (QLLC) Link Service

An X.25 (QLLC) link service enables you to connect SNA Server through public or private X.25 packet switching networks to host, peer, or downstream computers.

For information about the correct settings to use for your X.25 link service, contact your network administrator. For specific information about using IBM SDLC and MPCA adapters, see the Microsoft SNA Server Installation Guide.

Note  If your adapter is an IBM SDLC, IBM MPCA, or Microgate adapter, or any other SDLC adapter that does not contain a coprocessor, you cannot use a transmission speed greater than 9600 baud for an X.25 connection. At high transmission speeds, adapters that lack a coprocessor cannot handle full-duplex transmission, which is the type of transmission used by SNA Server X.25 connections.

To configure an X.25 (QLLC) link service

1	To change the default title, in the Service Title box, delete the default and type as many as 40 characters for the new title.

2	In the Card Type box, select the correct card.

3	Use the following table to configure the listed fields:

Field Name	Default
Local X.25 Address	No default
Default L3 Window Size	2
Default L3 Packet Size	128
L2 Window Size	7
T1 Timeout	30
N2 Retry Limit	10
Accept Reverse Charge	Off
Select Standby	Off
Startup Restart	On
Incoming Filter	On
Outgoing SVC	No default
Two-Way SVC	0001--0004
Incoming SVC	No default
PVC	No default
Data Rate	High
Encoding	NRZ
See also Guidelines for Assigning Channel Numbers.

4	Under Line Type, choose the appropriate option:

Leased (the default)

Switched: Modem-Stored Number

Switched: Manual Dial

5	If the Dialer Settings button is included in the dialog box, you can choose it and configure dialer settings.

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

Setup copies the required files, and the Link Service Configuration dialog box appears, listing the entry for this link service.


 X.25

The CCITT standard used for communication over a packet-switching network. X.25 uses the protocol called Qualified Logical Link Control (QLLC).


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.

See Also

Outgoing SVC Channel Range

Two-Way SVC Channel Range

Incoming SVC Channel Range

PVC Channel Range


Local X.25 Address

An address containing 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 maximum number of packets that can be sent to or received from a remote computer before an acknowledgement 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 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 number of frames that SNA Server can send to the network without having to wait for an acknowledgement.

The range is from 1 through 7; the default is 7.


T1 Timeout

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 number of times to attempt retransmitting data.

The range is from 1 through 100; the default is 10.


Accept Reverse Charge

Indicates whether SNA Server should accept an incoming call with reverse charge facility in the call packet.

The field is either on or off. The default is off.


Startup Restart

Indicates whether a restart should be performed each time the link is activated.

The field is either on or off. The default is on.


Select Standby

Sets the modem standby lines to on or off. A standby line is a backup line (usually switched) included on some leased line modems. Check your modem documentation for directions.

The field is either on or off. The default is off.


Data Rate

The data 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

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 definition.

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


Incoming Filter

Determines whether calls to X.25 addresses other than the local one are filtered out.

The field is either on or off. The default is on.


REMEMBER THAT CHANNEL STUFF  IS DUPLICATED IN TWO FORMS: POPUP AND NOTPOP.


Outgoing SVC

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

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

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 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.


Outgoing SVC

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

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

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 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.


Changing Setup Options on an SNA Server

The Setup Options dialog box allows you to make changes to your initial configuration. 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 settings.

Remove SNA Server.

To add, configure, or remove a link service

Under Options in the Setup Options dialog box, choose Links.

The Link Service Configuration dialog box appears.

Note  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 change the server role

Under Options in the Setup Options dialog box, choose Role.

The Change SNA Server Role dialog box appears.

To change client/server protocol settings

Under Options in the Setup Options dialog box, choose Protocols.

The Select Client/Server Protocols dialog box appears.

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

Under Options in the Setup Options dialog box, choose Remove.

The Confirm Removal dialog box appears.


Confirming SNA Services Removal
Confirming SNA Server Removal

Because removing SNA Server erases all of your existing SNA Server configurations, you must confirm that this is your intent. To use SNA Server again, you must run Setup to reinstall the files from the beginning.

To remove SNA Server

Choose Continue.

All files are deleted and the SNA Server program group icons are deleted from the Windows NT Program Manager.


Confirming Link Service Removal

To remove a link service already installed in SNA Server, you must confirm that this is your intent.

To remove a link service

Choose Continue.

The Link Service Configuration dialog box reappears, and the link service you removed is no longer listed in the Link Services Installed box.


Using Dialog Boxes

SNA Server Setup consists of a set of dialog boxes presented in a predetermined order. 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, which allows you to add, configure, or remove link services, change the SNA server role for the domain, modify client/server protocol settings, or remove SNA Server.

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.
Cancel or Exit	Cancels the information in the dialog box or exits the SNA Server Setup program.
Back	Returns you to the previous dialog box.
Help	Displays online help for the dialog box you are currently using.


Using SNA Server Help

You can find information in Help by choosing a Help topic or by using the Search feature. To return to the Help contents screen after you read the following instructions, click Back or press B.

For complete instructions on how to use Help, press F1 while Help is active.

To expand a topic list

Click a button showing a closed file folder  [image].
Or press TAB until the intended heading is highlighted, and press ENTER.

To collapse a topic list

Click a button showing an open file folder  [image].
Or press TAB until the intended heading is highlighted, and press ENTER.

To choose a Help topic

Click an underlined topic or a topic with a button  [image].
Or press TAB until the intended topic is highlighted, and then press ENTER.

To return to the previous topic

Click Back or press B.

To use the Search feature

Click Search or press S.

To close Help

From the File menu for Help, choose Exit (ALT, F, X).


Collapse Button

Use this button to collapse the list of help topics.


Expand Button

Use this button to expand the list of help topics.


Topic Button

Use this button to jump to a help topic.


link services

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


Selecting the Installation Type

On a Windows NT system, you can install software for either an SNA server or a client. A client uses the communications adapters installed in the SNA server(s) as well as the resources defined in the master configuration file to communicate with remote systems. For information on installing software for SNA Server clients that use the Windows NT, Windows version 3.x, MS-DOS, or OS/2 operating systems, see the Microsoft SNA Server Installation Guide.

Note  The following procedures apply when installing from floppy disks to a computer running Windows NT.

To choose an SNA server installation

From the Server/Client Selection dialog box, choose Server.

To choose an SNA Server client installation

From the Server/Client Selection dialog box, choose Client.


Specifying Client Mode

Clients can be either local or remote. The functionality for local and remote clients is the same; the difference is in how the local and remote clients connect to the domain of servers.

Local clients operate on the same network domain or SNA Server Subdomain as the SNA server. Each client issues a mailslot (Microsoft Networking [named pipes]and TCP/IP clients) or uses the native directory services (NetWare and Vines clients) to find a server in its subdomain. Once they connect to this server, they discover all the other servers in the subdomain.

Clients connecting over RAS should use the remote option, event though the client may be connecting to its local domain.

For clients using TCP/IP sockets, see the section, "Specifying Local or Remote Client Information with TCP/IP", in Appendix A of the Microsoft SNA Server Planning Guide.

Remote clients are not located in the same subdomain as the SNA server(s). Remote clients explicitly list servers in the remote subdomain to which they can connect. Once connected to one server, they discover all the other servers in that subdomain. 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.

To install a local client

1	From the SNA Client Mode dialog box, choose Local (same domain).

2	Choose Continue.

The Network Domain Name dialog box appears.

3	Accept the default domain name, or type the name of an SNA Server Subdomain.

4	Choose Continue.

Setup installs the necessary SNA Server files, and the Optional Administration Program dialog box appears.

To install a remote client

1	From the SNA Client Mode dialog box, choose Remote (different domain).

2	Choose Continue.

The Remote SNA Server Names dialog box appears.

3	Enter the names of the primary server (and backup server if desired).

4	Choose Continue.

Setup installs the necessary SNA Server files, and the Optional Administration Program dialog box appears.


Selecting the SNA Server Role

To ensure that the last saved configuration can be loaded, Setup allows you to designate both a primary configuration server and one or more backup configuration servers. SNA servers that are not primary or backup servers are member servers.

If you designate one or more backup servers, and the primary server is not functioning when you start SNA Server Admin, SNA Server loads a copy of the configuration file from a backup server. SNA Server will then allow you to manage the displayed configuration, but will not allow you to change settings or save the configuration. In installations that have one or more backup servers, SNA Server replicates the configuration file to the backup SNA server(s) each time it is changed and saved on the primary SNA server.

For information about the Directory Replicator service, see the Windows NT documentation.

To install a primary server

In the Change SNA Server Role dialog box, choose Continue.

The Review Settings dialog box appears.

To install a backup or member server

1	Under Server Roles for this Domain, select either Backup Configuration Server or Member Server.

2	Choose Continue.

The Review Settings dialog box appears.

See Also

SNA Server Components


primary configuration server

The SNA server designated to contain the domain-wide configuration file. The configuration file reflects the SNA Server resources for the SNA Server Subdomain, including all SNA servers, link services, LUs, 3270 users, and so on. There can be only one primary server in the subdomain.


backup configuration server

An SNA server on which the configuration file is replicated by SNA Server. There can be more than one backup server in an SNA Server Subdomain. 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

An SNA server that does not contain a configuration file. One or more SNA servers can operate as member servers.


Selecting Client/Server Protocols

If Setup detects more than one client/server protocol on your computer, you must specify the client/server protocol(s) to use with SNA Server.

To select client/server protocols

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

Microsoft Networking (Named Pipes)

Novell NetWare (IPX/SPX) (see Note on SPXII Protocol)

Banyan VINES (see Note on Banyan Vines )

TCP/IP (see Note on TCP/IP Protocol)

(SNA servers only:) AppleTalk

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

2	Choose Continue.

You will be prompted to supply the name of the network domain or SNA Server Subdomain.


Selecting Client/Server Protocols on the Client

If Setup detects more than one client/server protocol on your computer, you must specify the client/server protocol(s) to use with SNA Server. You can only choose one protocol for the client, and this protocol must also be installed on the SNA Server.

To select client/server protocols

1	In the Select Client/Server Protocols dialog box, select one of the check boxes:

Microsoft Networking (Named Pipes)

Novell NetWare (IPX/SPX) (see Note on SPXII Protocol)

Banyan VINES (see Note on Banyan Vines )

TCP/IP (see Note on TCP/IP Protocol)

(SNA servers only:) AppleTalk

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

2	Choose Continue.

You will be prompted to supply the name of the network domain or SNA Server Subdomain.


Specifying the Network Domain Name

You must specify the name of the domain in which SNA Server will operate. This domain can be the same as the server's Windows NT domain, or it can be the name of an SNA Server Subdomain whose members all belong to the same Windows NT domain.

If the Windows NT domain contains more than one primary configuration SNA Server, a separate SNA Server subdomain must be established for each primary configuration server. All backup configuration servers and member servers that belong to an SNA Server subdomain must also belong to the Windows NT domain to which the primary configuration server belongs.

The subdomain name is set by SNA Server Setup program for the server, and by SNA Server Client Setup program for Windows 3.x and Windows NT clients. The default is the name of the Windows NT domain, but this can be replaced with any subdomain name you choose. For clients this entry is presented only if you choose the local option during setup. Remote clients are configured using the server name rather than the subdomain name.

If your client/server protocol is Banyan VINES (and not Microsoft networking), you must also specify the Banyan StreetTalk group name.

To specify the subdomain name for a server or a Windows NT or Windows 3.x client

1	In the Domain Name box, type the subdomain name.

2	Choose Continue.

If you are configuring the names for a Banyan VINES network, you will be prompted to supply the StreetTalk group name.

SNA Server client software running on MS-DOS or OS/2 must be manually configured to access a subdomain if the subdomain name differs from the name of the Windows NT domain.

To specify the subdomain name for an MS-DOS client

In the case of MS-DOS clients, the following entry must be edited in the SNABASE section of SNA.INI:

REMOTE=subdomain_name

This entry is created but left blank by SNA Server Client Setup, and the client subdomain name defaults to the Windows NT domain name. To access an SNA Server subdomain with a name other than the Windows NT domain, specify the subdomain name in this entry.

To specify the subdomain name for an OS/2 client

In the case of OS/2 clients, the following entry must be added to the COMNAP section of SNA.INI:

SNADOMAIN=subdomain_name

As with the MS-DOS client, the name of the subdomain that the client software accesses is the same as the Windows NT domain name unless the subdomain name is specified in this entry.


SNA Server Subdomain

A new feature in SNA Server version 2.11 makes it possible to have several SNA Server Subdomains in a Windows NT domain.

A Windows NT domain

Can contain several SNA Server Subdomains

Can contain several primary SNA Servers, provided that each one is set up in its own subdomain

With regard to SNA Server, each Subdomain

Contains one primary SNA Server

Can contain up to 49 backup SNA Servers

Cannot contain SNA Servers from other Windows NT domains

SNA Server Setup requires you to specify the name of the subdomain to which the server will belong. One of the SNA Server Subdomains can have the same name as that of the Windows NT domain in which all the SNA Servers operate.

Because each subdomain can have only one primary SNA Server, it is not advisable to implement an SNA Server Subdomain across a slow bridges or routers. Multiple SNA Servers in a single subdomain can produce unwanted traffic on the wide-area network.


Specifying the StreetTalk Group Name

A Banyan 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.

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

To specify the StreetTalk group name

1	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.

2	Choose Continue.

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.


Specifying Remote SNA Server Names

If you select remote operation for a client, you must specify the name of the first SNA server the client will try to connect to. Optionally, you can specify the name of a second SNA server. Leading backslashes are not required.

Once a remote client has connected to one server, it discovers all the other servers in that domain. That is, a remote client is not limited to the servers specified in the Remote SNA Server Names dialog box.

To specify remote SNA server names

1	In the Primary box, type the name of the first server the remote client should try to connect to.

2	Optionally, in the Backup box, type the name of the second server the remote client should try to connect to.

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

3	Choose Continue.

The Optional Administration dialog box appears.


Installing Optional Components

  Installing Optional Components on a Windows NT Client

  Installing Optional Components on a Win 3.x Client


Installing Optional Components on a Windows NT Client

To install SNA Server components for a client computer running Window NT

1	From the Optional Administration Program dialog box, select one or more of the following options:

Install Administration Program

Install ODBC/DRDA driver

Install 3270 Applet

Install 5250 Applet

Install AFTP Server

Install NetView Alerter

2	Choose Continue.

The Review Settings dialog box appears.


Install Admin Program

You can install the SNA Server Administration program on a client computer. This program allows you to change certain configuration settings and start and stop servers and connections. Most clients will not need this functionality.


Install ODBC/DRDA driver

SNA Server version 2.11 includes the StarSQL ODBC/DRDA drivers for Windows and Windows NT clients. With these drivers, applications designed to use the ODBC interface and Structured Query Language (SQL) can access databases located on IBM hosts that use the DRDA protocol to manage distributed data, without requiring a host-based database gateway. These drivers allow ODBC-enabled applications (such as Microsoft Excel and Microsoft Access) to query, create, delete, and update tables in the following host databases:

DB2 for MVS

SQL/DS for VM and VSE

DB2/400 for OS/400

When installing SNA Server or client software for SNA Server on a computer running Windows NT, SNA Server Setup installs the files necessary to support Win32-based ODBC applications. To support 16-bit ODBC applications, you must install the 16-bit version of the ODBC/DRDA driver. To install this driver, run \CLIENTS\WIN3X\ODBC\SETUP.EXE.

You can also install the driver from a floppy disk.

To create an installation disk

1.	Insert a blank, formatted floppy disk in the appropriate drive

2.	Start the Windows NT Command Prompt (in the Main program group) and enter the following commands:

cd CD_drive:

cd \i386\disks

snadisk floppy_drive: win3x

3.	Insert the floppy disk in the drive of the computer on which you want to install the drivers and run \ODBC\SETUP.EXE on that disk.


Install 3270 Applet

With the SNA Server 3270 Applet for Windows NT and Windows, you can access an IBM host using a single logical unit (LU) for your SNA session.


Install 5250 Applet

With the SNA Server 5250 Applet for Windows NT and Windows, you can access an AS/400 system.


Install AFTP Server

APPC File Transfer Protocol (AFTP) is an IBM-developed protocol that duplicates for the SNA environment the function of the popular FTP utility in the TCP/IP environment. SNA Server AFTP Server is a Windows NT service that will allow AFTP clients to perform multi-megabyte file transfers between the host and the Windows NT-based system quickly using native SNA protocols, eliminating the need to install the expensive and CPU-intensive TCP/IP stack for the host in order to perform FTP file transfers.


Install NetView Alerter

The NVAlert service allows alerts generated by the Windows NT system or by Windows NT- based applications to be forwarded to a host system via NetView. As part of the NVAlert service installation, SNA Server Setup creates an NVAlert configuration file, NVALERT.INI, in the SYSTEM subdirectory of the SNA Server root directory.

By default, the NVAlert service has a Startup setting of Manual. To arrange for the service to start up every time the Windows NT system is started, use the Services option in the Control Panel to change the Startup setting to Automatic.

For more information, see Appendix C of the SNA Server Administration Guide and your IBM NetView documentation.


Installing Optional Components on a Windows 3.x Client

To install SNA Server components for a client computer running Windows 3.x

1	From the Optional Administration Program dialog box, select one or more of the following options:

Install Administration Program

Install 3270 Applet

Install 5250 Applet

2	Choose Continue.

The Review Settings dialog box appears.


Selecting the Installation Type

On a Windows NT system, you can install software for either an SNA server or a client. A client uses the communications adapters installed in the server(s) in the domain and the components defined in the master configuration file to communicate with remote systems.

To choose a server installation

From the Server/Client Selection dialog box, choose Server.

To choose a client installation

From the Server/Client Selection dialog box, choose Client.


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.

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 advantages of the non-centralized 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.

See Also

File System Choices and Security

SNA Server Components

SNA Server 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 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.

See Also

Planning SNA Server Domains

SNA Server Components

SNA Server Sponsor Connections


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 to them in the domain. Servers can be primary, backup, or member servers.

SnaServer

SnaServer 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

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.

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.

See Also

Planning SNA Server Domains

File System Choices and Security

SNA Server Sponsor Connections


SnaNMVT

The software component that routes NetView alerts back and forth between an SNA server and a host, and provides basic support to NVAlert and NVRunCmd.


NVAlert

A software component that allows you to specify NetView alerts that would not otherwise be forwarded. For example, with NVAlert, system events such as a disk becoming full can cause an alert to be sent to the host.


NVRunCmd

A software component that allows commands that are typed at a host console to be run on an SNA server.


SNA Server 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 by sponsor connections.

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

Configuration data

APPC attach messages

Directory services

Event logging

See Also

Planning SNA Server Domains

File System Choices and Security

SNA Server Components


SnaBase

The component of SNA Server that maintains lists of service names and statuses. The SnaBase is a fundamental component of SNA Server, and must be running before any other SNA component can start.


Changing Setup Options on a Client

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.

To modify an SNA Server client

1	From the Setup Options dialog box, choose Configure.

Setup presents the same dialog boxes as those used to install the SNA Server client.

2	Complete the dialog boxes with the required modificiations to the client configuration.

Setup copies the files, and the Setup Complete dialog box appears.

3	Choose Exit.

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

To remove an SNA Server client

1	From the Setup Options dialog box, choose Remove.

2	When prompted to confirm that you want to remove the SNA Server client software, choose Continue.

3	If a Setup Message dialog box appears, choose the OK button to force the SNA components to stop.

4	When the Remove Complete dialog box appears, choose OK.

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


Completing Setup

After you have installed and configured all the link services you need, the SNA Server Setup Finished dialog box appears. SNA Server is successfully installed on your computer. You can either exit the Setup program or proceed directly to SNA Server Admin to configure the connections and LUs for your service.

To exit Setup and proceed to SNA Server Admin

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

To exit Setup without going to SNA Server Admin

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

If you want to add, configure, or remove link services, change the SNA server role for the domain, modify client/server protocol settings, or remove SNA Server, you can start SNA Server Setup again (after exiting), and use the Setup Options dialog box to make changes.


Completing SNA Server Client Setup

Setup has finished copying the files. The SNA Server client is successfully installed on your computer.

To exit Setup

From the SNA Client Setup Finished dialog box, choose Exit.

If you want to modify settings on the client, you can start Setup again (after exiting) to make changes.


Installing a Client Over 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 can be installed to run from the local hard disk or from a network share. For clients running Windows version 3.x , a special procedure is needed for installing the client software to run from a network share; see Installing Clients to Run SNA Server from a Network Share.

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	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.

See Also

Installing Clients to Run SNA Server from a Network Share


Installing Clients to Run SNA Server from a Network Share

This topic provides details about setting up a computer running Windows version 3.x so that it will run the SNA Server client software from a network share. Such a client may, but does not have to, run its operating system from a network share. If a shared directory is used for the Windows system, it should be a different directory than the one used for the SNA Server client software.

When installing SNA Server client software for Windows-based 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.

To install Windows-based client software on a shared directory

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 shared directory, 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, in Program Manager, choose the File menu 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.

Determine the servername and sharename of a share from which client installation can be carried out. Then, in Program Manager, choose the File menu Run command, and in the dialog box, type:

\\servername\sharename\win3x\setup /a

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 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.1 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-7 for each client that will run the client software from the network share.

See Also

Removing Clients that Run SNA Server from a Network Share

Installing a Client Over the Network


Removing Clients that Run SNA Server 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 version 3.x system directories, whether they are on the local system or in a network share.

To remove one Windows-based client that runs from a network share

To remove the capability for a particular Windows-based client  to run SNA Server from a network share, on the client, follow the usual procedure for removing Windows-based client software.

To remove all Windows-based client software that is run from a network share

1	On a client that runs the software from a network share, 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, in Program Manager, choose the File menu 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.

Determine the servername and sharename of a share from which client installation can be carried out. Then, in Program Manager, choose the File menu Run command, and in the dialog box, type:

\\servername\sharename\win3x\setup /a

An introductory Setup dialog box appears.

2	Choose Continue.

The Setup Options dialog box appears.

3	Select Remove the SNA Client.

4	Choose the Continue button.

See Also

Changing Setup Options on a Client

Installing Clients to Run SNA Server from a Network Share


Choose Licensing Mode

Licensing for the Microsoft BackOffice family of server products requires a Server License and a license for each client computer to access the server, which is called a Client Access License. These licenses are acquired separately prior to using the product. For SNA Server, Windows NT Server, and SQL Server, the Client Access License can be used in either of two licensing modes (Per Server and Per Seat) offering customers the flexibility to choose the option that best meets their needs.

SNA Server version 2.11 Setup presents a Choose Licensing Mode dialog box. It also allows access through Help to online versions of the Microsoft Client Access License and Server License agreements. You will be required to select a licensing option and accept the terms of the license agreement for Setup to complete. In this dialog box, you must indicate whether you want SNA Server version 2.11 to be installed in the Per Server or Per Seat licensing mode.

For more detailed information about and an exact description of either the Per Server or Per Seat licensing modes, choose the Help button in the Choose Licensing Mode dialog box (or open LICCPA.HLP), see the Microsoft license agreement in your product package, or see the online Help for Licensing or License Manager.

Licensing is a Windows NT Server-only application located in Control Panel. Licensing allows you to manage licensing for Microsoft server products installed on your networks.

Note  License Manager is available only with Windows NT Server version 3.51 or later, and is located in the Network Administration program group.


EHNAPPC API and CA/400 Support for Win 3.x Clients

  Enabling EHNAPPC.API Support

  Enabling CA/400 Support


Enabling EHNAPPC.API Support

To enable EHNAPPC API support, Microsofts version of EHNAPPC.DLL will install automatically with a 16-bit client installation, and will be copied to the WINDOWSROOT\SYSTEM (WINDOWSROOT is the directory where the 16-bit version of Windows is located).

If an existing copy of the EHNAPPC.DLL file is detected in the WINDOWSROOT\SYSTEM directory by the Setup program, the Backup File dialog box will appear after all Setup questions have been answered and just before files are copied:

Choose Yes to back up the EHNAPPC.DLL as EHNAPPC.MS0, or choose NO to skip the backup step.

If an existing copy of the EHNRTRW.DLL file is detected in the WINDOWSROOT\SYSTEM directory by the Setup program, a similar dialog box will appear.

If an existing copy of EHNAPPC.MS0 or EHNRTRW.MS0 is detected, this dialog boxes will not appear,  the backup is assumed to have already occurred.

For additional information about the EHNAPPC API, see IBM AS/400, Client Access/400 for Windows 3.1, API and Technical Reference, Version 3 (SC41-3531-00).


Enabling CA/400 Support

If you want to use the new IBM Client Access/400 (CA/400) for Windows product with SNA Server version 2.11, you must change entries in the WIN.INI file and rename two files in the local directory in which CA/400 is installed. Please see Chapter 2 of the Microsoft SNA Server Enhancements Guide for instuctions.


Note on SPXII Protocol

If you choose Novell NetWare (IPX/SPX) as the client/server protocol and you want to enable communication over SPXII protocol, rather than SPX protocol, you will need to add a registry key (SnaSpx) to the SnaBase section of the registry.

For information about editing the Windows NT Registry, see your Windows NT documentation.

The SnaSpx registry key must be added in the following location in the Registry:

HKEY_LOCAL_MACHINE
  SYSTEM
    CurrentControlSet
      Services
        SnaBase
          Parameters
            SnaSpx

Add the SnaSpx key to Parameters, if it is not present already, and then add the following value to this key of the registry:

SPXII:REG_SZ:{ YES | NO }	Default: NO

Set this variable to YES to enable communication over SPXII protocol. Without this registry key, or if the variable is set to NO, SPXII protocol will not be enabled and any requests for SPXII protocol will be handled by standard SPX protocol.

Note  This entry applies to both SNA servers and Windows NT clients. The MSDOS and Windows 3.x/Windows for Workgroups 3.x clients will automatically use SPXII if the server and the MSDOS/Windows IPX driver supports it.


Note on Banyan Vines Protocol

If you choose to use Banyan® VINES® as the client/server protocol, the following Banyan VINES client software versions are recommended:

Operating system	Banyan VINES client software
Microsoft Windows version 3.1	versions 5.56(1) through 5.56(4)
Microsoft Windows NT version 3.5x	versions 5.56(5) and above


Note on TCP/IP Protocol

If you are installing on a TCP/IP network, the procedure for installing a client has been updated. Please see Appendix A of the Microsoft SNA Server Planning Guide for complete details and correct procedures.


Support for 16-bit SNA Applications on Windows NT

This will allow SNA Server 16-bit applications (written for Win16) to run on Windows NT Server version 3.5x SNA Server 2.11 server or client (Win32).

These thunking DLL files will be installed into a SNAROOT\SYSTEM\THUNK directory, created at the time of setup. This directory must be added to the PATH statement of the AUTOEXEC.BAT file, or the files must be copied to a directory in the users path.

Important  Be careful not to include the directory for the thunking WINAPPC.DLL in the PATH statement when running 32-bit third-party applications written for SNA Server version 2.0.

Be careful not to overwrite the WINAPPC.DLL file of a 16-bit client with the Win16 to Win32 thunking WINAPPC.DLL file.