Contents
  Contents for SNA Server Admin Help

  Using SNA Server Help

  Accessing Microsoft Support Services

  Getting Started with the SNA Server Admin Program

  Configuring Servers, Connections, and LUs

  Using LU Pools to Maximize Access

  Setting Up 3270 User and Group Access

  Managing SNA Server and Configuring Security

  Using Diagnostic Tools

Reference Information

  Guidelines for Specific Configurations

  Definitions

  Finding Further Information


Contents (Expanded)
  Contents for SNA Server Admin Help

  Using SNA Server Help

  Accessing Microsoft Support Services

  Getting Started with the SNA Server Admin Program

  Overview of SNA Server Admin

  Before Using SNA Server Admin

  SNA Server Preparation Forms

  Using the SNA Server Admin Interface

  Configuring Servers, Connections, and LUs

  Using LU Pools to Maximize Access

  Setting Up 3270 User and Group Access

  Managing SNA Server and Configuring Security

  Using Diagnostic Tools

Reference Information

  Guidelines for Specific Configurations

  Definitions

  Finding Further Information


Contents (Expanded)
  Contents for SNA Server Admin Help

  Using SNA Server Help

  Accessing Microsoft Support Services

  Getting Started with the SNA Server Admin Program

  Configuring Servers, Connections, and LUs

  Overview

  Configuring Servers and Connections

  Configuring LUs

  Using LU Pools to Maximize Access

  Setting Up 3270 User and Group Access

  Managing SNA Server and Configuring Security

  Using Diagnostic Tools

Reference Information

  Guidelines for Specific Configurations

  Definitions

  Finding Further Information


Contents (Expanded)
  Contents for SNA Server Admin Help

  Using SNA Server Help

  Accessing Microsoft Support Services

  Getting Started with the SNA Server Admin Program

  Configuring Servers, Connections, and LUs

  Using LU Pools to Maximize Access

  Overview

  Creating 3270 LU Pools

  Configuring Properties for a 3270 LU Pool

  Creating LUA Pools

  Creating Downstream Pools

  Assigning LUs to an LU Pool

  Removing LUs from an LU Pool

  Moving an LU to a Different Pool

  Setting Up 3270 User and Group Access

  Managing SNA Server and Configuring Security

  Using Diagnostic Tools

Reference Information

  Guidelines for Specific Configurations

  Definitions

  Finding Further Information


Contents (Expanded)
  Contents for SNA Server Admin Help

  Using SNA Server Help

  Accessing Microsoft Support Services

  Getting Started with the SNA Server Admin Program

  Configuring Servers, Connections, and LUs

  Using LU Pools to Maximize Access

  Setting Up 3270 User and Group Access

  Overview

  LUs for User Access: the 3270 LU

  Adding, Viewing, or Modifying Users or Groups

  Configuring Properties for a User or Group

  Giving Users Access to 3270 LUs and LU Pools

  Copying Properties and LUs Between Users and/or Groups

  Managing SNA Server and Configuring Security

  Using Diagnostic Tools

Reference Information

  Guidelines for Specific Configurations

  Definitions

  Finding Further Information


Contents (Expanded)
  Contents for SNA Server Admin Help

  Using SNA Server Help

  Accessing Microsoft Support Services

  Getting Started with the SNA Server Admin Program

  Configuring Servers, Connections, and LUs

  Using LU Pools to Maximize Access

  Setting Up 3270 User and Group Access

  Managing SNA Server and Configuring Security

  Overview

  Viewing the Status of Servers, Connections, and LUs

  Copying and Moving Services

  Starting and Stopping Servers and Connections

  Resetting LUs

  Changing the Domain of Focus

  Deleting SNA Resources

  Working with Configuration Files

  Setting Up Security with SNA Server

  Using Diagnostic Tools

Reference Information

  Guidelines for Specific Configurations

  Definitions

  Finding Further Information


Contents (Expanded)
  Contents for SNA Server Admin Help

  Using SNA Server Help

  Accessing Microsoft Support Services

  Getting Started with the SNA Server Admin Program

  Configuring Servers, Connections, and LUs

  Using LU Pools to Maximize Access

  Setting Up 3270 User and Group Access

  Managing SNA Server and Configuring Security

  Using Diagnostic Tools

  Overview

  Viewing the Status of Servers, Connections, and LUs

  Configuring for NetView

  SNA Server NetView Extensions: NVAlert and NVRunCmd

  Using Event Logs

  Configuring RTM Settings

  Performance Monitor Options for SNA Server

  Collecting Traces and Other Detailed System Information

Reference Information

  Guidelines for Specific Configurations

  Definitions

  Finding Further Information


Contents (Expanded)
  Contents for SNA Server Admin Help

  Using SNA Server Help

  Accessing Microsoft Support Services

  Getting Started with the SNA Server Admin Program

  Configuring Servers, Connections, and LUs

  Using LU Pools to Maximize Access

  Setting Up 3270 User and Group Access

  Managing SNA Server and Configuring Security

  Using Diagnostic Tools

Reference Information

  Guidelines for Specific Configurations

  Working with VTAM, NCP, and/or CICS

  AS/400 Configuration

  Configuring Hot Backup for LUs for 5250

  Phone Number Storage and Modem Types

  Administration After Upgrading from Comm Server 1.x

  Enabling Communication Between Version 2.0 SNA Servers and Version 2.1 SNA Servers

  Diagram of SNA Server Architecture

  Adapter, Connection, and Server Capacities for SNA Server

  Determining the LUs Assigned to a DFT Adapter

  Definitions

  Finding Further Information


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


Getting Started with the SNA Server Admin Program

  Overview of SNA Server Admin

  Before Using SNA Server Admin

  SNA Server Preparation Forms

  Using the SNA Server Admin Interface


Overview of SNA Server Admin

The SNA Server Admin program provides a graphical interface that allows you to configure connections between your PC and remote computers--IBM mainframes, AS/400s, or other PCs--within an IBM SNA network. SNA Server allows your PC to establish connections with several computers at the same time, with any of four methods of communication: 3270 terminal emulation,  APPC (which includes 5250 terminal emulation), communication using LUA, and/or communication involving downstream systems.

Basic Tasks

These are the basic tasks of an SNA Server administrator:

Gather information about local hardware and software.

Contact the administrator of the remote host, peer, and/or downstream system(s) to gather information about the system(s).

Study and plan for the ways SNA Server will be used.

Configure servers, connections, LUs, and LU pools.

If 3270 LUs will be used, assign the LUs and/or LU pools to users. Or, if APPC LUs will be used, and they are to be made available for 5250 emulation (or other communication with an AS/400), assign default APPC LUs to users.

As needed, set up security (through SNA Server dialog boxes).

Start and stop servers and connections.

Use diagnostic tools to monitor SNA Server.

For information about the kinds of connections and LUs available with SNA Server, see Connection Options and LU Options. For information about the capacities of connections, see Adapter, Connection, and Server Capacities for SNA Server.

Configuring for 3270 Terminal Emulation

The basic steps for configuring for 3270 terminal emulation are as follows:

1	Configure connections, by supplying information such as the Connection Name and the Local Node ID, and other information specific to your needs.

SNA Server is designed to provide reasonable default values for connections whenever possible. You will need to specify parameters that identify your system, and that differ from default values.

2	Assign 3270 logical units (LUs) to the connection, and configure the LUs. One or many LUs can be assigned to a given connection.

3	Add users and/or groups to the list recognized by SNA Server. These users and/or groups must already have network accounts.

4	Optionally, create 3270 LU pools and assign the 3270 LUs to them.

5	Assign the LUs and/or LU pools to users and/or groups.

6	Save the configuration and restart the affected SNA server, to put configuration changes into effect.

For information about 3270 LUs, and also about APPC LUs, LUA LUs, and downstream LUs, see the topics in Configuring LUs.

The SNA Server Admin Interface

For information about how the SNA Server Admin interface works, see Using the SNA Server Admin Interface.


   Connection Options

With SNA Server, you can use a number of connection types:

Connection  identifier	Connection type
802.2	Token ring or Ethernet; uses 802.2 protocol
SDLC	Synchronous Data Link Control
X25	X.25; uses qualified logical link control  (QLLC) protocol
DFT	Distributed function terminal
Channel	Channel attached; provides direct  channel attachment to a mainframe
Twinax	Twinaxial connection to an AS/400
Connections are generally used directly, but 802.2, SDLC, and X.25 connections can also be used indirectly, as downstream connections. A downstream connection allows an SNA server to support communication between hosts and clients such as IBM Communications Manager/2 systems. Even though such clients do not use the SNA Server client/server interface, with a downstream connection, they can access host connections available through an SNA server.


   LU Options

With SNA Server, you can use several different kinds of LUs:

 	3270 LUs, which allow a PC that emulates a 3270-type terminal to connect to a mainframe.

APPC LUs, which are used for APPC transaction programs and for 5250 emulation.

LUA LUs, which can be used with LUA to allow clients to communicate with host applications using LU 0, 1, 2, or 3 protocols.

Downstream LUs, which are used by clients such as IBM Communications Manager/2 systems in order to access a host connection on an SNA server. Such clients do not use the SNA Server client/server interface, but by using a downstream LU, can receive access to connections on an SNA server. A downstream LU is configured to pass information between downstream system and host.


Configuring Servers, Connections, and LUs: Overview

Before you configure servers, connections, and LUs, you will need information about local software and hardware, the configuration of the remote system, and how SNA Server will be used. For details, see Before Using SNA Server Admin and SNA Server Preparation Forms.

Basic Configuration Tasks

Before configuring the server, connections, and LUs, be sure to read the SNA Server README file, and then use Setup to install SNA Server and to configure link services. Then you can use SNA Server Admin to perform the following:

1	If a server will accept incoming calls or be used for APPC (which includes 5250 terminal emulation), it is recommended that you configure the Control Point Name and Network Name for the server.

2	Configure connections of the appropriate type: 802.2, SDLC, X.25, DFT, Channel, and/or Twinax.

3	Assign LUs to the connection(s), and configure the LUs for 3270 terminal emulation, for APPC (which includes 5250 emulation), for LUA, and/or as downstream LUs.

You can create 3270 LUs, LUA LUs, and downstream LUs one at a time or in a consecutively numbered range.

If you are using APPC with CPI-C or you want to specify a default connection for the DISPLAY verb, configure these options as well.

4	Optionally, group the LUs into LU pools.

5	If you are using 3270 LUs, assign the 3270 LUs or LU pools to users or groups.

6	Stop and restart the affected SNA server to put the configuration changes into effect.

For information about the capacities of connections, see Adapter, Connection, and Server Capacities for SNA Server. For information about working in multiple domains, see Multiple Domains in an SNA Server Installation.

You can use existing connections and LUs as a source from which to copy configuration properties to newly created connections and LUs. For details, see Copying Properties Between Connections or LUs, Moving a Connection to a Different Server, and Moving an LU.

After Configuration is Complete

When you have completed the configurations and assignments, stop and restart the affected SNA server, to put the configuration changes into effect; see Restarting an SNA Server. Finally, carry out the management of the SNA Server installation, by setting up security as needed, and by starting, monitoring, and stopping SNA servers (nodes), connections, and LUs.


Configuring Servers and Connections

  Overview

  Configuring Servers

  Configuring 802.2 Connections

  Configuring SDLC Connections

  Configuring X.25 Connections

  Configuring DFT Connections

  Configuring Channel Connections

  Configuring Twinax Connections

  Configuring Downstream Connections

See Also

  Commonly Required Server and Connection Parameters

  Guidelines for Specific Configurations

  Working with VTAM, NCP, and/or CICS

  Configuring LUs

  Starting and Stopping Servers and Connections


Configuring Servers and Connections (Expanded List)
Configuring Servers and Connections

  Overview

  Configuring Servers

  Configuring Server Identifiers

  Configuring Server Broadcasts

  Configuring 802.2 Connections

  Configuring SDLC Connections

  Configuring X.25 Connections

  Configuring DFT Connections

  Configuring Channel Connections

  Configuring Twinax Connections

  Configuring Downstream Connections

See Also

  Commonly Required Server and Connection Parameters

  Guidelines for Specific Configurations

  Working with VTAM, NCP, and/or CICS

  Configuring LUs

  Starting and Stopping Servers and Connections


Configuring Servers and Connections (Expanded List)
Configuring Servers and Connections

  Overview

  Configuring Servers

  Configuring 802.2 Connections

  Initial Connection Settings

  Basic 802.2 Settings

  Advanced 802.2 Settings

  SNA Server, VTAM, and NCP Parameters for 802.2 Connections

  Configuring SDLC Connections

  Configuring X.25 Connections

  Configuring DFT Connections

  Configuring Channel Connections

  Configuring Twinax Connections

  Configuring Downstream Connections

See Also

  Commonly Required Server and Connection Parameters

  Guidelines for Specific Configurations

  Working with VTAM, NCP, and/or CICS

  Configuring LUs

  Starting and Stopping Servers and Connections


Configuring Servers and Connections (Expanded List)
Configuring Servers and Connections

  Overview

  Configuring Servers

  Configuring 802.2 Connections

  Configuring SDLC Connections

  Initial Connection Settings

  Basic SDLC Settings

  Advanced SDLC Settings

  Configuring Multidrop Connections

  SNA Server, VTAM, and NCP Parameters for SDLC Connections

  Configuring X.25 Connections

  Configuring DFT Connections

  Configuring Channel Connections

  Configuring Twinax Connections

  Configuring Downstream Connections

See Also

  Commonly Required Server and Connection Parameters

  Guidelines for Specific Configurations

  Working with VTAM, NCP, and/or CICS

  Configuring LUs

  Starting and Stopping Servers and Connections


Configuring Servers and Connections (Expanded List)
Configuring Servers and Connections

  Overview

  Configuring Servers

  Configuring 802.2 Connections

  Configuring SDLC Connections

  Configuring X.25 Connections

  Initial Connection Settings

  Basic X.25 Settings

  Advanced X.25 Settings

  Facility Data Structuring

  SNA Server, VTAM, and NCP Parameters for X.25 Connections

  Configuring DFT Connections

  Configuring Channel Connections

  Configuring Twinax Connections

  Configuring Downstream Connections

See Also

  Commonly Required Server and Connection Parameters

  Guidelines for Specific Configurations

  Working with VTAM, NCP, and/or CICS

  Configuring LUs

  Starting and Stopping Servers and Connections


Configuring Servers and Connections (Expanded List)
Configuring Servers and Connections

  Overview

  Configuring Servers

  Configuring 802.2 Connections

  Configuring SDLC Connections

  Configuring X.25 Connections

  Configuring DFT Connections

  Initial Connection Settings

  Configuring Channel Connections

  Configuring Twinax Connections

  Configuring Downstream Connections

See Also

  Commonly Required Server and Connection Parameters

  Guidelines for Specific Configurations

  Working with VTAM, NCP, and/or CICS

  Configuring LUs

  Starting and Stopping Servers and Connections


Configuring Servers and Connections (Expanded List)
Configuring Servers and Connections

  Overview

  Configuring Servers

  Configuring 802.2 Connections

  Configuring SDLC Connections

  Configuring X.25 Connections

  Configuring DFT Connections

  Configuring Channel Connections

  Configuring Twinax Connections

  Configuring Downstream Connections

  Downstream Connections and LUs: Overview

  Guidelines for Downstream Configurations

  Configuring Downstream Connections

See Also

  Commonly Required Server and Connection Parameters

  Guidelines for Specific Configurations

  Working with VTAM, NCP, and/or CICS

  Configuring LUs

  Starting and Stopping Servers and Connections


Configuring Servers and Connections(Expanded List)
Configuring Servers and Connections

  Overview

  Configuring Servers

  Configuring 802.2 Connections

  Configuring SDLC Connections

  Configuring X.25 Connections

  Configuring DFT Connections

  Configuring Channel Connections

  Initial Connection Settings

  Basic Channel Settings

  Advanced Channel Settings

  Configuring Twinax Connections

  Configuring Downstream Connections

See Also

  Commonly Required Server and Connection Parameters

  Guidelines for Specific Configurations

  Working with VTAM, NCP, and/or CICS

  Configuring LUs

  Starting and Stopping Servers and Connections


Configuring Servers and Connections(Expanded List)
Configuring Servers and Connections

  Overview

  Configuring Servers

  Configuring 802.2 Connections

  Configuring SDLC Connections

  Configuring X.25 Connections

  Configuring DFT Connections

  Configuring Channel Connections

  Configuring Twinax Connections

  Initial Connection Settings

  Configuring Downstream Connections

See Also

  Commonly Required Server and Connection Parameters

  Guidelines for Specific Configurations

  Working with VTAM, NCP, and/or CICS

  Configuring LUs

  Starting and Stopping Servers and Connections


Configuring LUs

  Overview

  LUs for User Access: the 3270 LU

  LUs for APPC TPs and for 5250 Emulation

  Configuring for CPI-C or the DISPLAY Verb

  LUs for the LUA Interface

  Downstream LUs

See Also

  Commonly Required LU Parameters

  Configuring Servers and Connections

  Using LU Pools to Maximize Access


Configuring LUs (Expanded List)
Configuring LUs

  Overview

  LUs for User Access: the 3270 LU

  Assigning, Viewing, or Modifying 3270 LUs

  Configuring Properties for a 3270 LU

  Configuring Numbering for a 3270 LU Range

  Configuring Properties for a 3270 LU Range

  Setting Up 3270 User and Group Access: Overview

  LUs for APPC TPs and for 5250 Emulation

  Configuring for CPI-C or the DISPLAY Verb

  LUs for the LUA Interface

  Downstream LUs

See Also

  Commonly Required LU Parameters

  Configuring Servers and Connections

  Using LU Pools to Maximize Access


Configuring LUs (Expanded List)
Configuring LUs

  Overview

  LUs for User Access: the 3270 LU

  LUs for APPC TPs and for 5250 Emulation

  Overview

  Topic List for APPC LUs

  Configuring for CPI-C or the DISPLAY Verb

  LUs for the LUA Interface

  Downstream LUs

See Also

  Commonly Required LU Parameters

  Configuring Servers and Connections

  Using LU Pools to Maximize Access


Configuring LUs (Expanded List)
Configuring LUs

  Overview

  LUs for User Access: the 3270 LU

  LUs for APPC TPs and for 5250 Emulation

  Configuring for CPI-C or the DISPLAY Verb

  Adding, Viewing, or Editing CPI-C Information

  Configuring Properties for CPI-C

  Configuring the Default DISPLAY Connection

  LUs for the LUA Interface

  Downstream LUs

See Also

  Commonly Required LU Parameters

  Configuring Servers and Connections

  Using LU Pools to Maximize Access


Configuring LUs (Expanded List)
Configuring LUs

  Overview

  LUs for User Access: the 3270 LU

  LUs for APPC TPs and for 5250 Emulation

  Configuring for CPI-C or the DISPLAY Verb

  LUs for the LUA Interface

  Assigning, Viewing, or Modifying LUA LUs

  Configuring Properties for LUA LUs

  Configuring Numbering for an LUA LU Range

  Configuring Properties for an LUA LU Range

  Downstream LUs

See Also

  Commonly Required LU Parameters

  Configuring Servers and Connections

  Using LU Pools to Maximize Access


Configuring LUs (Expanded List)
Configuring LUs

  Overview

  LUs for User Access: the 3270 LU

  LUs for APPC TPs and for 5250 Emulation

  Configuring for CPI-C or the DISPLAY Verb

  LUs for the LUA Interface

  Downstream LUs

  Downstream Connections and LUs: Overview

  Guidelines for Downstream Configurations

  Assigning, Viewing, or Modifying Downstream LUs

  Configuring Properties for a Downstream LU

  Configuring Numbering for a Downstream LU Range

  Adding a Comment for a Downstream LU Range

  Associating Downstream LUs with a Downstream Connection

  Adjusting the Numbering of Downstream LUs

See Also

  Commonly Required LU Parameters

  Configuring Servers and Connections

  Using LU Pools to Maximize Access


LUs for User Access: the 3270 LU

  Assigning, Viewing, or Modifying 3270 LUs

  Configuring Properties for a 3270 LU

  Configuring Numbering for a 3270 LU Range

  Configuring Properties for a 3270 LU Range

  Setting Up 3270 User and Group Access: Overview

See Also

  Commonly Required LU Parameters

  Using LU Pools to Maximize Access


 Managing SNA Server and Configuring Security

  Overview

  Viewing the Status of Servers, Connections, and LUs

  Copying and Moving Services

  Starting and Stopping Servers and Connections

  Resetting LUs

  Changing the Domain of Focus

  Deleting SNA Resources

  Working with Configuration Files

  Adding Users and Groups and Setting Permissions

  Configuring SNA Domain Permissions

  Taking Ownership of the Ability to Administer SNA Server

  Setting Up Auditing of Access to the Configuration File

See Also

  Using Diagnostic Tools: Overview


Setting Up Security with SNA Server

  Overview

  Adding Users and Groups and Setting Permissions

  Configuring SNA Domain Permissions

  Taking Ownership of the Ability to Administer SNA Server

  Setting Up Auditing of Access to the Configuration File


Managing SNA Server and Configuring Security: Overview

You can manage SNA Server services by starting and stopping SNA servers (nodes), starting and stopping connections, and resetting LUs. These actions have the following effects:

Starting SNA servers (nodes) and connections makes them available for use.

Stopping SNA servers (nodes) and connections frees up communications lines (unless they are leased or permanent). However, stopping services can also interrupt interactions between a peer or a host and a user. Therefore, when possible, have users log off from the remote peer or host before stopping services.

See also Note About "On Demand" and "Incoming" Connections.

Restarting servers (nodes) after stopping them allows configuration changes to take effect.

Resetting an LU may restore function to the LU if a problem has occurred.

When managing an SNA Server installation, you may also need to change the domain of focus, delete SNA resources, or work with configuration files, including saving, reopening, backing up, or restoring the files.

Viewing the Status of Services

When working on system performance, it is often useful to observe which LUs are active on which connections, and which users are accessing the LUs. This information is available when you view the status of servers, connections, and LUs:

Server status includes the number of active users and the number of 3270, APPC, and LUA sessions.

Connection status indicates the state that the connection is in.

See Note About "On Demand" and "Incoming" Connections.

LU status includes the username of the user accessing an LU, if any user is doing so. You can also view an active user and see which LUs that user is using.

Setting Up Security with SNA Server

Through commands on the Security menu in SNA Server Admin, you can configure security (permissions and auditing) for your SNA servers. Also, if necessary, you can take ownership of the ability to administer SNA Server (this action requires appropriate permissions). For background information about these topics, see your Windows NT documentation and the Microsoft SNA Server Administration Guide. (For step-by-step instructions for the security dialog boxes, see other topics in this Help.)


Setting Up Security with SNA Server: Overview

SNA Server includes security features that allow you to control administrative access to SNA Server. The security in SNA Server is built around the same user accounts database as is used by Windows NT-based servers in a Windows NT domain. This means that you create user and group accounts only once for use by both Windows NT and SNA Server.

With dialog boxes in SNA Server Admin, you can specify the users and groups who are:

Allowed to run SNA Server Admin (the graphical interface for administration) and snacfg (the command-line interface for administration).

Allowed to change the SNA Server configuration file, which stores the information that allows user access to SNA resources.

Subject to auditing when carrying out actions affecting the SNA Server configuration file.

For background information about security, see your Windows NT documentation.  For information about basic elements for security on SNA servers and about implementing this security, see the Microsoft SNA Server Administration Guide. For step-by-step instructions for the security dialog boxes, see the following topics:

  Adding Users and Groups and Setting Permissions

  Configuring SNA Domain Permissions

  Taking Ownership of the Ability to Administer SNA Server

  Setting Up Auditing of Access to the Configuration File


Setting Up 3270 User and Group Access: Overview

Before users can be recognized by SNA Server, they must have accounts on the local area network. Once users (and groups of users) have network accounts, you can add them to the list used by SNA Server. Then you can assign 3270 LUs and/or 3270 LU pools (containing LUs) to the users.

When you assign properly configured 3270 LUs or LU pools to users or groups, the users can gain access to the host system(s) that the LUs connect to.

Important  If a user or group needs access to multiple LU sessions, assign one LU or LU pool for each session needed. You can assign a pool multiple times to the same user or group.

When you assign LUs to user and group accounts with overlapping memberships, some of these assignments override others. See Precedence of Accounts in Determining LU Access.

To configure for 3270 emulation, take the following steps:

1	Configure the servers and connections that will be needed for 3270 terminal emulation.

2	Assign 3270 LUs to the connections, and configure the LUs.

One or many LUs can be assigned to a given connection.

3	Add users and/or groups to the list recognized by SNA Server.

These users and/or groups must already have network accounts.

4	Optionally, create 3270 LU pools and assign 3270 LUs to them.

5	Assign the LUs and/or LU pools to users and/or groups.

Important  If a user or group needs access to multiple LU sessions, assign one LU or LU pool for each session needed. You can assign a pool multiple times to the same user or group.

6	Save the configuration and restart the affected SNA server, to put configuration changes into effect.


Using Diagnostic Tools: Overview

Diagnostic tools allow you to collect information about the sequence of events leading up to a difficulty, and the exact state of the system when the difficulty occurs. Diagnostic tools can provide the following kinds of information:

The status of servers, connections, and LUs.

NetView management data.

Windows NT event logs for application events. These logs can be viewed using the Windows NT Event Viewer.

RTM data, available via 3270 emulators that support viewing this data.

Information from the Windows NT Performance Monitor tool.

Trace files.

You can specify the following for SNA Server diagnostic information:

The connection through which NetView alerts sent should be sent.

The RTM triggers for registering a host response and for sending data (applicable only if the emulators in use support the viewing of RTM data).

The types of events (besides errors) to record in the event log. The choices are all events that can be recorded, general-activity events, or significant system events.

The server on which to store event logs.

A server to which pop-up error messages should be routed, in addition to appearing on the local server.

For background technical information about SNA Server, including information about Registry and environment variables, see the Microsoft SNA Server Reference.


Finding Further Information

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

Microsoft SNA Server Installation Guide

Microsoft SNA Server Administration Guide

Microsoft SNA Server Reference

For more information about SNA and about 3270 information display systems, see the following manuals:

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

Microsoft SNA Server LUA Programmer's Guide*

*	Available in the Microsoft SNA Server Software Development Kit.

For more information about LU 6.2, APPC, and/or CPI-C, see the following manuals:

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 SNA Server APPC Programmer's Guide*

Microsoft SNA Server CPI-C Programmer's Guide*

*	Available in the Microsoft SNA Server Software Development Kit.


Guidelines for Specifc Configurations
Guidelines for Specific Configurations

  Working with VTAM, NCP, and/or CICS

  Adapter, Connection, and Server Capacities for SNA Server

  AS/400 Configuration

  Phone Number Storage and Modem Types

  Administration After Upgrading from Comm Server 1.x

  Enabling Communication Between Version 2.0 SNA Servers and Version 2.1 SNA Servers

  Diagram of SNA Server Architecture

  Determining the LUs Assigned to a DFT Adapter


Before Using SNA Server Admin

Before using SNA Server Admin, you must run SNA Server Setup, gather information, and make choices about your installation.

Configuring Link Services with SNA Server Setup

Before using the SNA Server Admin program, be sure to read the SNA Server README file, and then use the Setup program to install one or more SNA link services. Link services can only be changed by running the Setup program. For information about Setup, see the Microsoft SNA Server Installation Guide or the online help for Setup.

Information to Gather and Choices to Make

Before you can successfully configure SNA Server, you must gather information about the local and remote computers (host, peer, and/or downstream systems) and make choices about how SNA Server will be used.

Some of the basic information on which a configuration is built is as follows:

The type of communications hardware (communications adapter and lines) to be used. The options are 802.2 (token ring or Ethernet), SDLC (leased or switched line), X.25 (permanent or switched virtual circuit), DFT, Channel, or Twinax.

The type of remote system(s): host system (mainframe), peer system, and/or downstream system.

The configuration parameters set on the remote host, peer, or downstream system(s). Some of these parameters must be set to match identifying information on the local system, such as the Local Node ID or, for incoming calls or LU 6.2  (APPC), the local Network Name and Control Point Name. Coordinate these parameters, and other system-specific information, with the administrator of the remote host, peer, or downstream system. (For information about determining the local address of your 802.2 or X.25 adapter, see Note on Local Adapter Address.)

The ways SNA Server will be used: for 3270 terminal emulation, for APPC (which includes 5250 terminal emulation), for applications using LUA, and/or for downstream systems.. Also, SNA Server may be used in multiple domains, as described in Multiple Domains in an SNA Server Installation.

The names and addresses of any LUs that will be accessed on the remote systems.

For a set of forms to help you gather information and make choices, see SNA Server Preparation Forms.


[]JAN: COMMONLY REQUIRED IS DUPLICATED IN TWO CONTEXTS: THE CONTEXT FOR A SECONDARY WINDOW FROM ANOTHER WINDOW, AND THE CONTEXT FOR A REGULAR WINDOW FROM THE SEARCH LIST.


Commonly Required Server and Connection Parameters

There are a number of parameters that are commonly required on SNA Server connections and servers, as shown in the following table. The table lists specific system elements and types of configurations, and the parameters that must be set for them. Consult with the administrator of the remote host, peer, and/or downstream system(s) when specifying values for these parameters. (For information about determining the local address of your 802.2 or X.25 adapter, see Note on Local Adapter Address.)

The table does not include all information about the parameters that identify the remote node. For detailed information about what these parameters are and when they should be specified, see Using Remote Node Identifiers.

System element	Common configuration parameters	Applicable situations
Server (node)	Network Name and Control Point Name	Recommended for LU 6.2 (APPC) and for systems that accept incoming calls
Connection (any type)	Local Node ID	Required for all systems
802.2 connection	Remote Network Address	Required for all 802.2 connections
X.25 connection	Remote X.25 Address	Required for all X.25 connections
X.25 connection using PVC	PVC Alias	Required for all X.25 connections using PVC


Commonly Required Server and Connection Parameters

There are a number of parameters that are commonly required on SNA Server connections and servers, as shown in the following table. The table lists specific system elements and types of configurations, and the parameters that must be set for them. Consult with the administrator of the remote host, peer, and/or downstream system(s) when specifying values for these parameters. (For information about determining the local address of your 802.2 or X.25 adapter, see Note on Local Adapter Address.)

The table does not include all information about the parameters that identify the remote node. For detailed information about what these parameters are and when they should be specified, see Using Remote Node Identifiers.

System element	Common configuration parameters	Applicable situations
Server (node)	Network Name and Control Point Name	Recommended for LU 6.2 (APPC) and for systems that accept incoming calls
Connection (any type)	Local Node ID	Required for all systems
802.2 connection	Remote Network Address	Required for all 802.2 connections
X.25 connection	Remote X.25 Address	Required for all X.25 connections
X.25 connection using PVC	PVC Alias	Required for all X.25 connections using PVC


[]JAN: COMMONLY REQUIRED IS DUPLICATED IN TWO CONTEXTS: THE CONTEXT FOR A SECONDARY WINDOW FROM ANOTHER WINDOW, AND THE CONTEXT FOR A REGULAR WINDOW FROM THE SEARCH LIST.


Note on Local Adapter Address

When communicating with the administrator of a remote host, peer, or downstream system, you may need to tell that administrator the address of your local adapter.

To determine the local address of an 802.2 or X.25 adapter

At the command prompt, type

net config server

In the resulting display, the address of the local adapter appears in the line labeled Server is active on.


Commonly Required LU Parameters

The following table shows LU parameters that are set on remote host or peer systems and that must match parameters on the local system. The table lists specific types of LUs, and the parameters that must be set for them. Consult with the administrator of the remote host, peer, and/or downstream system(s) when specifying values for these parameters:

System element	Required  configuration parameters
3270 LU (on connections other than DFT)	LU Number and LU Name
3270 LU for DFT	Port Number, LT Number, and  LU Name
Local LU for independent APPC	LU Alias, Network Name, and  LU Name
Remote LU for independent APPC	LU Alias, Network Name, and  LU Name
Local LU for dependent APPC	LU Alias and LU Number (recommended parameters: Network Name and LU Name)
Remote LU for dependent APPC	Network Name, LU Name, and  Uninterpreted LU Name
LUA LU (on connections other than DFT)	LU Number and LU Name
LUA LU for DFT	Port Number, LT Number, and  LU Name
Downstream LU	LU Number (recognized by host) and Downstream LU Number (recognized  by downstream system)


Commonly Required LU Parameters

The following table shows LU parameters that are set on remote host or peer systems and that must match parameters on the local system. The table lists specific types of LUs, and the parameters that must be set for them. Consult with the administrator of the remote host, peer, and/or downstream system(s) when specifying values for these parameters:

System element	Required  configuration parameters
3270 LU (on connections other than DFT)	LU Number and LU Name
3270 LU for DFT	Port Number, LT Number, and  LU Name
Local LU for independent APPC	LU Alias, Network Name, and  LU Name
Remote LU for independent APPC	LU Alias, Network Name, and  LU Name
Local LU for dependent APPC	LU Alias and LU Number (recommended parameters: Network Name and LU Name)
Remote LU for dependent APPC	Network Name, LU Name, and  Uninterpreted LU Name
LUA LU (on connections other than DFT)	LU Number and LU Name
LUA LU for DFT	Port Number, LT Number, and  LU Name
Downstream LU	LU Number (recognized by host) and Downstream LU Number (recognized  by downstream system)


Using Remote Node Identifiers

There are several different types of parameters that you can use to specify the remote node with which a connection should connect:

Remote address (802.2 and X.25 connections only)

This parameter is required for 802.2 and X.25 connections. For outgoing calls, it is used to specify the remote host, peer, or downstream system being called. For 802.2, this parameter is the Remote Network Address; for X.25 connections, it is the Remote X.25 Address.

Network Name (Remote Node) and Control Point Name (Remote Node)

As a general guideline, use these parameters if the administrator of the remote host, peer, or downstream system uses them.

These two parameters work together; if either parameter is supplied, the other should also be supplied. These parameters are used only for Format 3 XIDs, one of two types of identification exchange. Format 3 XIDs are generally used for APPC. If a connection does not use Format 3 XIDs, there is no need to specify these parameters. For information about how these parameters are checked on incoming calls (as identifiers for the remote system making the call), see Identifiers in Incoming XIDs.

See also Note About Local and Remote Names.

Remote Node ID

As a general guideline, use this parameter if the administrator of the remote host, peer, or downstream system uses it.

This parameter can be used in Format 0 XIDs or Format 3 XIDs, the two types of identification exchange. Format 0 XIDs are generally used for 3270 communication and for LUA; Format 3 XIDs are generally used for APPC. For information about how the Remote Node ID is checked on incoming calls (as an identifier for the remote system making the call), see Identifiers in Incoming XIDs.

The following tables provides guidelines about which parameter(s) to use for identifying the remote node:

Guidelines for Identifiers for 802.2 Connections

Guidelines for Identifiers for SDLC Connections

Guidelines for Identifiers for X.25 Connections


Note About Local and Remote Names

The Network Name and Control Point Name for the remote node are different from the Network Name and Control Point Name for the local node. The remote Network Name and Control Point Name are specified in the Connection Properties dialog box. The local Network Name and Control Point Name are specified in the Server Properties dialog box.


Guidelines for Identifiers for 802.2 Connections

Conn. type	Allowed call direction(s)	Guidelines for identifier(s) for remote node
802.2	Outgoing	Use Remote Network Address
802.2	Incoming	Match the identifer(s) used on the remote system:     Remote node Network Name and Control Point Name     Or     Remote Node ID     Or     Remote Network Address
802.2	Both	Use a combination of outgoing plus incoming identifiers


Guidelines for Identifiers for SDLC Connections

Conn. type	Allowed call direction(s)	Guidelines for identifier(s) for remote node
SDLC	Outgoing	If SNA Server supplies the phone number to the modem, specify Dial Data (phone number of remote system)
SDLC	Incoming	Match the identifer(s) used on the remote system:     Remote node Network Name and Control Point Name     Or     Remote Node ID
SDLC	Both	Use a combination of outgoing plus incoming identifiers


Guidelines for Identifiers for X.25 Connections

Conn. type	Allowed call direction(s)	Guidelines for identifier(s) for remote node
X.25	Outgoing	Use Remote X.25 Address
X.25	Incoming	Match the identifer(s) used on the remote system:     Remote node Network Name and Control Point Name     Or     Remote Node ID     Or     Remote X.25 Address
X.25	Both	Use a combination of outgoing plus incoming identifiers


Identifiers in Incoming XIDs

When deciding which kind of remote node identifier to specify for a connection that accepts incoming calls, it may be helpful to understand how SNA Server uses identifying information (XIDs) from incoming calls.

When SNA Server receives an XID from an incoming call, it looks at the XID for some kind of identifier of the remote system that made the call. It compares this identifier, in the order shown in the following list, against identifiers stored in the SNA Server configuration. If it finds a match, it accepts the call. If it finds that identifiers are left unspecified (in the configuration and/or the XID), and the connection is an SDLC connection, SNA Server accepts the call, pending further exchange of information. In other cases--when every comparison yields a mismatch, or when identifiers are left unspecified but the connection is 802.2 or X.25--SNA Server rejects the incoming call.

Identifiers are compared in the following order:

1	If the incoming XID is Format 3, SNA Server examines the XID for a remote node Network Name and Control Point Name. If these parameters are present in both the incoming XID and in the SNA Server configuration, and they match, the call is accepted. If the parameters are present and do not match, the call is rejected.

2	If the parameters were not available for the preceding step, Remote Node IDs are examined next. (Remote Node IDs may be used in either Format 0 or Format 3 XIDs.) If a Remote Node ID is present in both the incoming XID and in the SNA Server configuration, and they match, the call is accepted. If the parameters are present and do not match, the call is rejected.

3	If the parameters were not available for the preceding steps, for 802.2 and X.25 connections, remote addresses are examined:

For 802.2 connections, the Remote Network Address in the SNA Server configuration is compared to the address from which the XID was received. If the addresses match, the call is accepted; if not, the call is rejected.

For X.25 connections, the Remote X.25 Address in the SNA Server configuration is compared to the address from which the XID was received. If the addresses match, the call is accepted; if not, the call is rejected.

4	For 802.2 and X.25 connections, if no match is found in any of the preceding steps, the incoming call is rejected.

For SDLC connections, if no match is found in the preceding steps, but identifiers were left unspecified in the configuration and/or the XID, the call is accepted, pending further exchange of identifiers. However, if identifiers were not left unspecified and no identifiers match, the call is rejected.


SNA Server Preparation Forms

You can print these forms and use them as a guide for gathering information.

Forms for Configuring the Server and Connections

  Server Resources Planning

  Server Information

  Initial Connection Settings

  802.2 Settings

  SDLC Settings

  X.25 Settings

  Channel Settings

Forms for Configuring LUs

  3270 LUs (for Individual LUs)

  3270 LUs (for Ranges of LUs)

  3270 LU Pools

  Users and Groups

  Local APPC LUs

  Remote APPC LUs

  Mode Properties for LU-LU Pairs

  CPI-C Properties

Form for Diagnostics

  RTM Settings


Configuring Server Identifiers

If an SNA server will accept incoming calls or be used for APPC (which includes 5250 terminal emulation), it is recommended that you configure two parameters for the server: the local Network Name and Control Point Name. Note that these two names work together to identify the SNA server; if either of these names is supplied, the other should also be supplied.

For information about working in multiple domains, see Multiple Domains in an SNA Server Installation. For a table showing configuration parameters for the AS/400 environment, see AS/400 Configuration.

To specify identifiers for an SNA server

1	In the Servers and Connections window, select the server you want to configure.

2	Press ENTER.

3	In the Network Name box, type the Network Name for the server.

4	In the Control Point Name box, type the Control Point Name for the server.

If you will be connecting to an AS/400 computer, see also Note About AS/400 Computers.

If you will be connecting to a host system with VTAM or NCP, see also Note About SNA Server Parameters and VTAM.

5	Optionally, in the Comment box, type a comment of up to 25 characters.

6	Choose OK.


Configuring Server Broadcasts

Server broadcasts are the method of communication used between SNA servers. Configure settings in the Server Broadcasts dialog box to ensure that your SNA servers use the appropriate protocols for communication with clients and other servers. You need to configure server broadcasts only once for the domain.

Note  Choose only the protocols you need, because sending unneeded broadcasts can significantly decrease network efficiency. See Note About Protocols Available and Note About Optimizing Efficiency.

For information about setting up a server to support Macintosh clients, see the Microsoft SNA Server Installation Guide.

To configure server broadcasts and other communication items

1	From the Options menu, choose Server Broadcasts.

The Server Broadcasts dialog box appears.

2	Select the client-server protocol(s) that you need for server broadcasts between SNA servers. See Note About Protocols Available. The options are:

Microsoft Networking (Named Pipes)

Novell NetWare (IPX/SPX)

Banyan VINES/IP

Windows Sockets (TCP/IP)

Route Server Broadcasts over IP routers

See Note About Server Broadcasts Over IP Routers.

3	Select the types of support needed for earlier software versions:

SNA Server 2.0 servers in the same domain

DCA/Microsoft Comm Server client support

See Note About Support for Earlier Software Versions.

4	If you did not select any support for earlier software versions, you can specify the number of seconds for the Mean Time between Server Broadcasts.

Specifying a larger value causes less demand on the network (since broadcasts occur less often). However, a smaller value compensates better for loss of broadcast messages (which by definition are not guaranteed to be received).

The range is from 45 through 65535 seconds; the default is 60 seconds.

5	To accept the settings, choose OK. To exit the dialog box without accepting the settings, choose Cancel.


Note About Protocols Available

You may be able to select extra protocols that do not exist on your network; however, selecting these has no effect. A full range of protocols are displayed (unless you enable support of SNA Server 2.0 servers or Comm Server clients) because the software on the local server has no way to determine what protocols are available on other computers on the network. (To add protocols, see your Windows NT documentation; to set up your SNA servers to use available protocols, see Chapter 2 of the Microsoft SNA Server Installation Guide.)


Note About Optimizing Efficiency

For optimal efficiency, upgrade any Comm Server 1.x clients and SNA Server version 2.0 servers to the appropriate SNA Server version 2.1 software. Then select one network protocol--for example, Microsoft Networking (Named Pipes) or Novell NetWare (IPX/SPX) but not both. Finally, for the Mean Time between Server Broadcasts, specify a value greater than or equal to 60 seconds. The smaller this value, the less the efficiency, but the more the broadcasts compensate for possible message loss. If messages are lost infrequently, an appropriate value might be 120 seconds; if messages are lost more frequently, an appropriate value might be 60 seconds.


Note About Server Broadcasts Over IP Routers

If you need to route server broadcasts over IP routers, you must select Microsoft Networking (Named Pipes).

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. When you select Route Server Broadcasts over IP routers, the messages are propagated between primary or backup domain controllers (but not other servers on the domain).


Note About Support for Earlier Software Versions

Supporting earlier software versions decreases network efficiency. To support either type of earlier software, servers must send out additional broadcasts, and may have to use additional transports.

If you choose to support SNA Server 2.0 servers in the same domain, you must select Microsoft Networking (Named Pipes) and/or Novell NetWare (IPX/SPX). These servers rely on these protocols. If you choose to support DCA/Microsoft Comm Server clients, your selections must include Microsoft Networking (Named Pipes). These clients rely on this protocol.


SEVEN VERSIONS OF "CONFIGURING INITIAL CONNECTION SETTINGS" EXIST HERE: one for each kind of connection, one for general information


Initial Connection Settings

After accessing or assigning a connection, in the Connection Properties dialog box, find the items appropriate to your configuration, and supply information as follows:

Connection Name

Type a Connection Name.

Comment

Optionally, type a comment of up to 25 characters.

Link Service

Select a link service. If the link service you want is not in the list, choose Cancel, and use the Setup program to install the link service.

See also Note About DFT Link Services.

Remote End

Select the type of remote system for this connection: Host System (mainframe), Peer System, or Downstream. (See also Note About Downstream Connections.)

For DFT, Channel, and Twinax connections, the Remote End is preset.

If this connection will be used for 3270 or LUA LUs, select Host System.

If you will be using dependent APPC, which relies on a host system for communications, select Host System, not Peer System.

For a table showing configuration parameters for the AS/400 environment, see AS/400 Configuration.

For information about how SNA Server parameters correspond to VTAM host parameters, see Working with VTAM and NCP.

Activation

If Outgoing Calls are included in Allowed Directions, select an Activation setting:

On Server Startup  Select this option if you want the connection to be readily available whenever the server is started.

On Demand  Select this option if you want the connection to be started when needed, and stopped when not in use.

By Administrator  Select this option if you want the administrator to control the connection on a case-by-case basis.

See also Note on Activation and Allowed Directions.

Allowed Directions

Select the allowed call direction(s), Outgoing Calls and/or Incoming Calls.

If you are configuring an SDLC connection that will accept incoming calls, see also Note on Encoding for Incoming-Call Connections.

For DFT, Channel, and Twinax connections, the allowed call direction of Outgoing Calls is automatically selected.

Virtual Circuit Type (X.25 connections only)

If you are configuring an X.25 connection, select the type of circuit used by the connection:

Switched (SVC)

Permanent (PVC)

To continue configuring an 802.2, SDLC, X.25, or Channel connection, choose Setup.

For a DFT or Twinax connection, the configuration is complete. To accept the settings, choose OK; to exit the dialog box without accepting the settings, choose Cancel.

To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


SEVEN VERSIONS OF "CONFIGURING INITIAL CONNECTION SETTINGS" EXIST HERE


Initial Connection Settings

To access an existing connection for viewing or modifying

1	In the Servers and Connections window, select the connection.

2	On the Toolbar, click  [image].

See also Copying Properties Between Connections or LUs and Moving a Connection to a Different Server.

To assign a new 802.2 connection

1	In the Servers and Connections window, select the  [image]  server on which to add the connection.

2	On the Toolbar, click  [image].

3	Under Connection, select  802.2.

4	Choose OK.

After accessing or assigning a connection, in the Connection Properties dialog box, find the items appropriate to your configuration, and supply information as follows:

Connection Name

Type a Connection Name.

Comment

Optionally, type a comment of up to 25 characters.

Link Service

Select a link service. If the link service you want is not in the list, choose Cancel, and use the Setup program to install the link service.

Remote End

Select the type of remote system for this connection: Host System (mainframe), Peer System, or Downstream. (See also Note About Downstream Connections.)

If this connection will be used for 3270 or LUA LUs, select Host System.

If you will be using dependent APPC, which relies on a host system for communications, select Host System, not Peer System.

For a table showing configuration parameters for the AS/400 environment, see AS/400 Configuration.

For information about how SNA Server parameters correspond to VTAM host parameters, see SNA Server, VTAM, and NCP Parameters for 802.2 Connections.

Activation

If Outgoing Calls are included in Allowed Directions, select an Activation setting:

On Server Startup  Select this option if you want the connection to be readily available whenever the server is started.

On Demand  Select this option if you want the connection to be started when needed, and stopped when not in use.

By Administrator  Select this option if you want the administrator to control the connection on a case-by-case basis.

See also Note on Activation and Allowed Directions.

Allowed Directions

Select the allowed call direction(s), Outgoing Calls and/or Incoming Calls.

To configure Basic 802.2 settings, choose Setup.


SEVEN VERSIONS OF "CONFIGURING INITIAL CONNECTION SETTINGS" EXIST HERE


Initial Connection Settings

To access an existing connection for viewing or modifying

1	In the Servers and Connections window, select the connection.

2	On the Toolbar, click  [image].

See also Copying Properties Between Connections or LUs and Moving a Connection to a Different Server.

To assign a new SDLC connection

1	In the Servers and Connections window, select the  [image]  server on which to add the connection.

2	On the Toolbar, click  [image].

3	Under Connection, select SDLC.

4	Choose OK.

After accessing or assigning a connection, in the Connection Properties dialog box, find the items appropriate to your configuration, and supply information as follows:

Connection Name

Type a Connection Name.

Comment

Optionally, type a comment of up to 25 characters.

Link Service

Select a link service. If the link service you want is not in the list, choose Cancel, and use the Setup program to install the link service.

Remote End

Select the type of remote system for this connection: Host System (mainframe), Peer System, or Downstream. (See also Note About Downstream Connections.)

If this connection will be used for 3270 or LUA LUs, select Host System.

If you will be using dependent APPC, which relies on a host system for communications, select Host System, not Peer System.

For a table showing configuration parameters for the AS/400 environment, see AS/400 Configuration.

For information about how SNA Server parameters correspond to VTAM host parameters, see SNA Server, VTAM, and NCP Parameters for SDLC Connections.

Activation

If Outgoing Calls are included in Allowed Directions, select an Activation setting:

On Server Startup  Select this option if you want the connection to be readily available whenever the server is started.

On Demand  Select this option if you want the connection to be started when needed, and stopped when not in use.

By Administrator  Select this option if you want the administrator to control the connection on a case-by-case basis.

See also Note on Activation and Allowed Directions.

Allowed Directions

Select the allowed call direction(s), Outgoing Calls and/or Incoming Calls.

If you are configuring an SDLC connection that will accept incoming calls, see also Note on Encoding for Incoming-Call Connections.

To configure Basic SDLC settings, choose Setup.


SEVEN VERSIONS OF "CONFIGURING INITIAL CONNECTION SETTINGS" EXIST HERE


Initial Connection Settings

To access an existing connection for viewing or modifying

1	In the Servers and Connections window, select the connection.

2	On the Toolbar, click  [image].

See also Copying Properties Between Connections or LUs and Moving a Connection to a Different Server.

To assign a new X.25 connection

1	In the Servers and Connections window, select the  [image]  server on which to add the connection.

2	On the Toolbar, click  [image].

3	Under Connection, select  X.25.

4	Choose OK.

After accessing or assigning a connection, in the Connection Properties dialog box, find the items appropriate to your configuration, and supply information as follows:

Connection Name

Type a Connection Name.

Comment

Optionally, type a comment of up to 25 characters.

Link Service

Select a link service. If the link service you want is not in the list, choose Cancel, and use the Setup program to install the link service.

Remote End

Select the type of remote system for this connection: Host System (mainframe), Peer System, or Downstream. (See also Note About Downstream Connections.)

If this connection will be used for 3270 or LUA LUs, select Host System.

If you will be using dependent APPC, which relies on a host system for communications, select Host System, not Peer System.

For a table showing configuration parameters for the AS/400 environment, see AS/400 Configuration.

For information about how SNA Server parameters correspond to VTAM host parameters, see SNA Server, VTAM, and NCP Parameters for X.25 Connections.

Activation

If Outgoing Calls are included in Allowed Directions, select an Activation setting:

On Server Startup  Select this option if you want the connection to be readily available whenever the server is started.

On Demand  Select this option if you want the connection to be started when needed, and stopped when not in use.

By Administrator  Select this option if you want the administrator to control the connection on a case-by-case basis.

See also Note on Activation and Allowed Directions.

Allowed Directions

Select the allowed call direction(s), Outgoing Calls and/or Incoming Calls.

Virtual Circuit Type

Select the type of circuit used by the connection:

Switched (SVC)

Permanent (PVC)

To configure Basic X.25 settings, choose Setup.


SEVEN VERSIONS OF "CONFIGURING INITIAL CONNECTION SETTINGS" EXIST HERE


Initial Connection Settings

To access an existing connection for viewing or modifying

1	In the Servers and Connections window, select the connection.

2	On the Toolbar, click  [image].

See also Copying Properties Between Connections or LUs and Moving a Connection to a Different Server.

To assign a new DFT connection

1	In the Servers and Connections window, select the  [image]  server on which to add the connection.

2	On the Toolbar, click  [image].

3	Under Connection, select DFT.

4	Choose OK.

After accessing or assigning a connection, in the Connection Properties dialog box, find the items appropriate to your configuration, and supply information as follows:

Connection Name

Type a Connection Name.

Comment

Optionally, type a comment of up to 25 characters.

Link Service

Select a link service. If the link service you want is not in the list, choose Cancel, and use the Setup program to install the link service.

See also Note About DFT Link Services.

Remote End

A Remote End of Host System (mainframe) is automatically selected for a DFT connection.

Activation

Select an Activation setting:

On Server Startup  Select this option if you want the connection to be readily available whenever the server is started.

On Demand  Select this option if you want the connection to be started when needed, and stopped when not in use.

By Administrator  Select this option if you want the administrator to control the connection on a case-by-case basis.

Allowed Directions

The allowed call direction of Outgoing Calls is automatically selected.

For a DFT connection, the configuration is complete. To accept the settings, choose OK; to exit the dialog box without accepting the settings, choose Cancel.

To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


SEVEN VERSIONS OF "CONFIGURING INITIAL CONNECTION SETTINGS" EXIST HERE


Initial Connection Settings

To access an existing connection for viewing or modifying

1	In the Servers and Connections window, select the connection.

2	On the Toolbar, click  [image].

See also Copying Properties Between Connections or LUs and Moving a Connection to a Different Server.

To assign a new Channel connection

1	In the Servers and Connections window, select the  [image]  server on which to add the connection.

2	On the Toolbar, click  [image].

3	Under Connection, select Channel.

4	Choose OK.

After accessing or assigning a connection, in the Connection Properties dialog box, find the items appropriate to your configuration, and supply information as follows:

Connection Name

Type a Connection Name.

Comment

Optionally, type a comment of up to 25 characters.

Link Service

Select a link service. If the link service you want is not in the list, choose Cancel, and use the Setup program to install the link service.

Remote End

A Remote End of Host System (mainframe) is automatically selected for a Channel connection.

Activation

Select an Activation setting:

On Server Startup  Select this option if you want the connection to be readily available whenever the server is started.

On Demand  Select this option if you want the connection to be started when needed, and stopped when not in use.

By Administrator  Select this option if you want the administrator to control the connection on a case-by-case basis.

Allowed Directions

The allowed call direction of Outgoing Calls is automatically selected.

To configure Basic Channel settings, choose Setup.


SEVEN VERSIONS OF "CONFIGURING INITIAL CONNECTION SETTINGS" EXIST HERE


Initial Connection Settings

To access an existing connection for viewing or modifying

1	In the Servers and Connections window, select the connection.

2	On the Toolbar, click  [image].

See also Copying Properties Between Connections or LUs and Moving a Connection to a Different Server.

To assign a new Twinax connection

1	In the Servers and Connections window, select the  [image]  server on which to add the connection.

2	On the Toolbar, click  [image].

3	Under Connection, select Twinax.

4	Choose OK.

After accessing or assigning a connection, in the Connection Properties dialog box, find the items appropriate to your configuration, and supply information as follows:

Connection Name

Type a Connection Name.

Comment

Optionally, type a comment of up to 25 characters.

Link Service

Select a link service. If the link service you want is not in the list, choose Cancel, and use the Setup program to install the link service.

Remote End

A Remote End of Peer System is automatically selected for a Twinax connection.

Activation

Select an Activation setting:

On Server Startup  Select this option if you want the connection to be readily available whenever the server is started.

On Demand  Select this option if you want the connection to be started when needed, and stopped when not in use.

By Administrator  Select this option if you want the administrator to control the connection on a case-by-case basis.

Allowed Directions

The allowed call direction of Outgoing Calls is automatically selected.

For a Twinax connection, the configuration is complete. To accept the settings, choose OK; to exit the dialog box without accepting the settings, choose Cancel.

To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


Note on Activation and Allowed Directions

Activation affects only outgoing calls. Connections that accept incoming calls begin to listen for these calls when the server is started.


Basic 802.2 Settings

In the 802.2 Setup dialog box, find the items appropriate to your configuration, and supply information as follows:

Remote Network Address

Type the Remote Network Address of the computer with which you will communicate on this connection.

For more information about the Remote Network Address, see Using Remote Node Identifiers. For information about determining the local network address for your token ring or Ethernet adapter, see Note on Local Adapter Address.

Local Node ID

Type the Local Node ID. Use the same Local Node ID for all connections and link services on a particular server.

Note  Do not use 000 or FFF for the first three digits; these values are reserved.

Network Name (Remote Node)

If instructed to by the administrator of a remote host, peer, or downstream system, and if you are using Format 3 XIDs, type the Network Name of the remote system. Format 3 is the default XID type.

The Network Name works with the Control Point Name to identify a system. If either of these parameters is supplied, the other should also be supplied.

If you will be connecting to an AS/400 computer, see Note About AS/400 Computers.

If you will be connecting to a host system with VTAM or NCP, see Note About Connection Parameters and VTAM.

For more information about Network Name (Remote Node), see Using Remote Node Identifiers.

Control Point Name (Remote Node)

If instructed to by the administrator of a remote host, peer, or downstream system, and if you are using Format 3 XIDs, type the Control Point Name of the remote system. Format 3 is the default XID type.

The Control Point Name works with the Network Name to identify a system. If either of these parameters is supplied, the other should also be supplied.

If you will be connecting to an AS/400 computer, see Note About AS/400 Computers.

If you will be connecting to a host system with VTAM or NCP, see Note About Connection Parameters and VTAM.

For more information about Control Point Name (Remote Node), see Using Remote Node Identifiers.

Remote Node ID

If instructed to by the administrator of a remote host, peer, or downstream system, type the Remote Node ID.

Note  Do not use 000 or FFF for the first three digits; these values are reserved.

For more information about the Remote Node ID, see Using Remote Node Identifiers.

After specifying basic 802.2 settings, choose a button according to the following:

To configure advanced settings, choose Advanced, and see Advanced 802.2 Settings.

To accept the settings, and use the advanced settings set by default or previously configured, choose OK.

To exit the dialog box without accepting the settings, choose Cancel.

To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


Advanced 802.2 Settings

SNA Server is designed to provide reasonable defaults for connections whenever possible, especially for advanced settings.

After choosing Advanced in the 802.2 Setup dialog box, find the items appropriate to your configuration, and supply information as follows:

XID Type

Select the XID Type. Most systems use Format 3.

If you want to use independent APPC LUs on this connection, you must select Format 3.

When SNA Server is configured to use Format 0 over a host connection, the host treats it as a PU type 2.0, and so SNA Server exercises only its PU type 2.0 capabilities. When SNA Server establishes a host or peer connection using Format 3 and independent LUs, SNA Server exercises its PU type 2.1 capabilities.

Remote SAP Address

Type the Remote SAP Address.

For most installations, you should leave this address at the default value of 04.

Retry Limit

Specify the number of times that the local system should retransmit a frame if no response is received from the remote system.

Max BTU Length

Specify the maximum for the BTU length.

See Note About Max BTU Length.

XID Retries

Specify the number of times that the local system should retransmit an XID (an identifying message) if no response is received from the remote system.

Response (t1) Timeout

Select a value for the Response (t1) Timeout. See Selecting a Response Timeout and Note About Timeouts for 802.2.

Receive ACK (t2) Timeout

Select a value for the Receive ACK (t2) Timeout. See Selecting a Receive ACK Timeout and Note About Timeouts for 802.2.

Inactivity (ti) Timeout

Select a value for the Inactivity (ti) Timeout. See Selecting an Inactivity Timeout and Note About Timeouts for 802.2.

Receive ACK Threshold (frames)

Specify the maximum number of frames that the local system can receive from the remote system before sending a response. Set this to a value less than the Unacknowledged Send Limit, so that the local system acknowledges received transmissions more frequently than it expects responses to sent transmissions.

Unacknowledged Send Limit (frames)

Specify the maximum number of frames that the local system can send without receiving a response from the remote system. This parameter is sometimes called the send window size.

To exit the dialog box without accepting the configuration settings, choose Cancel. To accept the settings, choose OK.

To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


Basic SDLC Settings

In the SDLC Setup dialog box, find the items appropriate to your configuration, and supply information as follows:

Dial Data

If this connection uses a switched line and the phone number is not stored in the modem, type the Dial Data. With a leased SDLC line, this field is unavailable.

For information about the available methods for supplying a phone number to the modem, see Phone Number Storage and Modem Types.

Local Node ID

If this connection uses a switched SDLC line (standard telephone line) to connect to a host system, type the Local Node ID. Use the same Local Node ID for all connections and link services on a particular server.

If this connection uses a leased SDLC line, you can use the default for the Local Node ID.

Note  Do not use 000 or FFF for the first three digits; these values are reserved.

Network Name (Remote Node)

If instructed to by the administrator of a remote host, peer, or downstream system, and if you are using Format 3 XIDs, type the Network Name of the remote system. Format 3 is the default XID type.

The Network Name works with the Control Point Name to identify a system. If either of these parameters is supplied, the other should also be supplied.

If you will be connecting to an AS/400 computer, see Note About AS/400 Computers.

If you will be connecting to a host system with VTAM or NCP, see Note About Connection Parameters and VTAM.

For more information about Network Name (Remote Node), see Using Remote Node Identifiers.

Control Point Name (Remote Node)

If instructed to by the administrator of a remote host, peer, or downstream system, and if you are using Format 3 XIDs, type the Control Point Name of the remote system. Format 3 is the default XID type.

The Control Point Name works with the Network Name to identify a system. If either of these parameters is supplied, the other should also be supplied.

If you will be connecting to an AS/400 computer, see Note About AS/400 Computers.

If you will be connecting to a host system with VTAM or NCP, see Note About Connection Parameters and VTAM.

For more information about Control Point Name (Remote Node), see Using Remote Node Identifiers.

Remote Node ID

If instructed to by the administrator of a remote host, peer, or downstream system, type the Remote Node ID.

Note  Do not use 000 or FFF for the first three digits; these values are reserved.

For more information about the Remote Node ID, see Using Remote Node Identifiers.

After specifying basic SDLC settings, choose a button according to the following:

To configure advanced settings, choose Advanced, and see Advanced SDLC Settings.

To accept the settings, and use the advanced settings set by default or previously configured, choose OK.

To exit the dialog box without accepting the settings, choose Cancel.

To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


Advanced SDLC Settings

SNA Server is designed to provide reasonable defaults for connections whenever possible, especially for advanced settings.

After choosing Advanced in the SDLC Setup dialog box, find the items appropriate to your configuration, and supply information as follows:

XID Type

Select the XID Type. Most systems use Format 3.

If you want to use independent APPC LUs on this connection, you must select Format 3.

When SNA Server is configured to use Format 0 over a host connection, the host treats it as a PU type 2.0, and so SNA Server exercises only its PU type 2.0 capabilities. When SNA Server establishes a host or peer connection using Format 3 and independent LUs, SNA Server exercises its PU type 2.1 capabilities.

Encoding

Select the encoding scheme for your modem to use.

Your modem must use the same encoding scheme as the modem at the remote computer.

If you will be connecting to a host system with VTAM, see also Note on Encoding and VTAM.

For information about connections that accept incoming calls, see also Note on Encoding for Incoming-Call Connections.

Duplex

Select the setting that matches your modem:

For a half-duplex modem, select Half. If none of your adapters were installed with the Constant RTS option set, you can only choose half-duplex.

For a full-duplex modem, select Full. If you want to use the full-duplex setting, one or more of your adapters must have the Constant RTS option set (at installation).

See also Note About Adapters.

Most SNA servers will use the default, Half.

Data Rate

Select the Data Rate.

Check your adapter and modem manuals to find out if the data rate can or must be set for your equipment.

Poll Address

Type a two-digit hexadecimal number. Contact the administrator of the remote system to determine the appropriate value. See Note on Poll Address.

Note  Do not use 00 or FF. These values are reserved.

Poll Rate

If the remote system is a peer or downstream system, specify the poll rate (in polls per second).

Poll Timeout (for peer or downstream connections)

Specify the length of time, in tenths of a second, for the local system to wait for a response to a poll before trying again. Too small a timeout can cause connection problems. See Note About Sessions Affected.

Poll Retry Limit (for peer or downstream connections)

Specify the number of times for the local system to poll the remote system if there is no response. See Note About Sessions Affected.

Contact Timeout

Specify the length of time, in tenths of a second, that the local system should wait between attempts to make a connection with a remote system.

This parameter is ignored for incoming calls.

Contact Retry Limit

Specify the maximum number of times the local system should attempt to make a given connection.

This parameter is ignored for incoming calls.

Idle Timeout (for host or peer connections)

Specify the length of time, in tenths of a second, for the local system to wait for a response to a transmission before trying again.  Too small a timeout can cause connection problems. See Note About Sessions Affected.

Idle Retry Limit (for host or peer connections)

Specify the number of times for the local system to try to send data to the remote system if there is no response. See Note About Sessions Affected.

Max BTU Length

Specify the maximum for the BTU length.

See Note About Max BTU Length.

Multidrop Primary

If this is a leased SDLC line to downstream systems, and this server will be the primary station for a multidrop connection, select this box. For information about configuring for multidrop, see Configuring Multidrop Connections.

Select Standby

If you want your modem's standby line to be set to on, select this check box.

Check your adapter and modem manuals to find out if standby can be set for your equipment.

Switched Connection Establishment Timeout

If this connection uses a switched SDLC line (standard telephone line), specify the number of seconds that will be allowed for the user or modem to dial and make a connection to the remote computer. If the dialing will be done manually, be sure to allow enough time for the user to dial, wait for an answer, and make the connection.

This parameter is ignored by incoming calls.

To exit the dialog box without accepting the configuration settings, choose Cancel. To accept the settings, choose OK.

To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


[]JAN: MULTIDROP IS DUPLICATED IN TWO CONTEXTS: THE CONTEXT FOR A SECONDARY WINDOW FROM ANOTHER WINDOW, AND THE CONTEXT FOR A REGULAR WINDOW FROM THE SEARCH LIST.  KEEP BOTH COPIES UPDATED. JUMPS ARE ONLY IN THE REGULAR-WINDOW COPY.


Configuring Multidrop Connections

In a multidrop connection, one primary computer comunicates simultaneously with multiple secondary computers. SNA Server supports multidrop connections used for downstream systems on leased SDLC lines.

You can configure up to four multidrop connections on each line, with an SNA server as the primary server on each.

Configure each connection to be used in the multidrop configuration according to the guidelines that follow.

Guidelines for multidrop connections

1	Use the Setup program to configure a link service for an SDLC line with the Constant RTS option not selected.

2	Configure each connection to be used in the multidrop configuration as follows:

In the Connection Properties dialog box, select the same Link Service for each connection.

In the Connection Properties dialog box, under Remote End, select Downstream.

Make all the parameters identical for each configuration, except for Poll Address, and possibly the Local Node ID and Remote Node ID. For these parameters, obtain values from the downstream system administrator(s). Make the Poll Address unique for each station.

3	For the primary connection in the multidrop configuration, in the Advanced part of the SDLC Setup dialog box, select the Multidrop Primary box.


[]JAN: MULTIDROP IS DUPLICATED IN TWO CONTEXTS: THE CONTEXT FOR A SECONDARY WINDOW FROM ANOTHER WINDOW, AND THE CONTEXT FOR A REGULAR WINDOW FROM THE SEARCH LIST.  KEEP BOTH COPIES UPDATED. JUMPS ARE ONLY IN THE REGULAR-WINDOW COPY.


Configuring Multidrop Connections

In a multidrop connection, one primary computer comunicates simultaneously with multiple secondary computers. SNA Server supports multidrop connections used for downstream systems on leased SDLC lines.

You can configure up to four multidrop connections on each line, with an SNA server as the primary server on each.

Configure each connection to be used in the multidrop configuration according to the instructions that follow.

Guidelines for multidrop connections

1	Use the Setup program to configure a link service for an SDLC line with the Constant RTS option not selected.

2	Configure each connection to be used in the multidrop configuration as follows:

In the Connection Properties dialog box, select the same Link Service for each connection.

In the Connection Properties dialog box, under Remote End, select Downstream.

Make all the parameters identical for each configuration, except for Poll Address, and possibly the Local Node ID and Remote Node ID. For these parameters, obtain values from the downstream system administrator(s). Make the Poll Address unique for each station.

3	For the primary connection in the multidrop configuration, in the Advanced part of the SDLC Setup dialog box, select the Multidrop Primary box.

For information about using the configuration dialog boxes, see Initial Connection Settings, Basic SDLC Settings, and Advanced SDLC Settings.


Basic X.25 Settings

In the X.25 Setup dialog box, find the items appropriate to your configuration, and supply information as follows. See also Note About Adapters for X.25.

Remote X.25 Address

Type the Remote X.25 Address to connect to.

For more information about the Remote X.25 Address, see Using Remote Node Identifiers. For information about determining the local network address for your X.25 adapter, see Note on Local Adapter Address.

Local Node ID

If this connection is using SVC, type the Local Node ID. Use the same Local Node ID for all connections and link services on a particular server.

If this connection is using PVC, you can use the default for the Local Node ID.

Note  Do not use 000 or FFF for the first three digits; these values are reserved.

Network Name (Remote Node)

If instructed to by the administrator of a remote host, peer, or downstream system, and if you are using Format 3 XIDs, type the Network Name of the remote system. Format 3 is the default XID type (configured in Advanced X.25 settings).

The Network Name works with the Control Point Name to identify a system. If either of these parameters is supplied, the other should also be supplied.

If you will be connecting to an AS/400 computer, see Note About AS/400 Computers.

If you will be connecting to a host system with VTAM or NCP, see Note About Connection Parameters and VTAM.

For more information about Network Name (Remote Node), see Using Remote Node Identifiers.

Control Point Name (Remote Node)

If instructed to by the administrator of a remote host, peer, or downstream system, and if you are using Format 3 XIDs, type the Control Point Name of the remote system. Format 3 is the default XID type (configured in Advanced X.25 settings).

The Control Point Name works with the Network Name to identify a system. If either of these parameters is supplied, the other should also be supplied.

If you will be connecting to an AS/400 computer, see Note About AS/400 Computers.

If you will be connecting to a host system with VTAM or NCP, see Note About Connection Parameters and VTAM.

For more information about Control Point Name (Remote Node), see Using Remote Node Identifiers.

Remote Node ID

If instructed to by the administrator of a remote host, peer, or downstream system, type the Remote Node ID.

Note  Do not use 000 or FFF for the first three digits; these values are reserved.

For more information about the Remote Node ID, see Using Remote Node Identifiers.

After specifying basic X.25 settings, choose a button according to the following:

To configure advanced settings, choose Advanced, and see Advanced X.25 Settings.

To accept the settings, and use the advanced settings set by default or previously configured, choose OK.

To exit the dialog box without accepting the settings, choose Cancel.

To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


Advanced X.25 Settings

SNA Server is designed to provide reasonable defaults for connections whenever possible, especially for advanced settings.

After choosing Advanced in the X.25 Setup dialog box, find the items appropriate to your configuration, and supply information as follows. See also Note About Adapters for X.25.

XID Type

Select the XID Type. Most systems use Format 3.

If you want to use independent APPC LUs on this connection, you must select Format 3.

When SNA Server is configured to use Format 0 over a host connection, the host treats it as a PU type 2.0, and so SNA Server exercises only its PU type 2.0 capabilities. When SNA Server establishes a host or peer connection using Format 3 and independent LUs, SNA Server exercises its PU type 2.1 capabilities.

Packet Size (PVC only)

For a PVC channel, select the maximum number of data bytes (not header bytes) to be sent in a frame. Obtain this value from your network provider.

Window Size (PVC only)

For a PVC channel, select the maximum number of frames that the local system can send without receiving a response from the remote system. Obtain this value from the administrator of the remote host or peer system.

PVC Alias (PVC only)

For a PVC channel, type the number that identifies the channel: 1 for the first channel, 2 for the second, and so on.

Max BTU Length

Specify the maximum for the BTU length.

See Note About Max BTU Length.

Facility Data (SVC only)

For an SVC channel, specify the codes for any Facility Data required by your network provider or by the administrator of the remote system. You can specify as many as 126 hexadecimal characters (63 hexadecimal bytes). For detailed information about how facility data is coded, see Facility Data Structuring.

User Data (SVC only)

For an SVC channel, specify the codes for any User Data required by your network provider. Type an even number of hexadecimal characters, up to the maximum of 32 characters.

To exit the dialog box without accepting the configuration settings, choose Cancel. To accept the settings, choose OK.

To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


Facility Data Structuring

Facility data strings are often used to request nondefault functions from the X.25 network for a particular SVC connection. A string of facility data is built up from shorter groupings, or "requests," consisting of a two-character identifier followed by a series of parameter characters. Because the identifier tells how many characters follow it, each request can be distinguished from the ones that follow.

The first character of the identifier tells how many parameter characters follow:

First character	Number of characters
0 through 3	2
4 through 7	4
8 through b	6
c through f	Length given by characters 3 and 4
The second character of the identifier is usually specific to each facility. Identifiers should not be repeated.

For  some pop-up examples of facility data strings, see Simplified Facility Data Example and Standard Facility Data Example.

The characters used after the identifiers vary among sites. For a table of facility requests common to most sites, see Common Identifier Table.

When the local system initiates an X.25 connection and sends a facility request, sometimes the remote system negotiates changes. The network sends a packet (the CALL Accepted packet) containing the outcome of the negotiations to the local system. When flow-control facilities such as packet and window size are negotiated, the remote system can only negotiate up to, or closer to, standard default values.


Simplified Facility Data Example

The following simplified example shows how identifiers allow each facility request to be distinguished from the ones that follow:

40AAAA20BB

The example contains two requests. The first request begins with a 4, indicating that after the two-character identifier there are four characters (in this case, four occurrences of the A character). The second request follows, beginning with a 2, indicating that after the two-character identifier there are two characters (two occurrences of the B character).


Standard Facility Data Example

The facility data string in this example initiates a connection using 256-byte packets, a sending window of 7, a receive window of 4, and charges reversed. The facility requests that do this are as follows:

42 08 08 for packet size

43 04 07 for window sizes

01 01 for reverse charging

When these requests are concatenated, the following facility data string is created:

4208084304070101


Common Identifier Table

The following table shows commonly used identifiers for facility requests:

Facility	Identifier	Parameters	Meaning
Reverse charging	01	00 01	Reverse charging NOT requested Reverse charging requested
Packet sizes	42	0r0s	r = receive packet size s = send packet size
			r and s can have the following values:
			6 for 64-byte packets 7 for 128-byte packets 8 for 256-byte packets 9 for 512-byte packets A for 1024-byte packets
Window sizes	43	0r0s	r = receive window size s = send window size r and s can be from 1 through 7.   They are usually set equal,  making the send and receive  windows the same size.
In this table, send and receive operate from the point of view of the initiator of the connection.


Basic Channel Settings

In the Channel Attached Setup dialog box, find the items appropriate to your configuration, and supply information as follows:

Channel Address

Type a two-digit hexadecimal number identifying the channel. The range is from 00 through FF; the default is FF.

Local Node ID

Type the Local Node ID. Use the same Local Node ID for all connections and link services on a particular server.

Note  Do not use 000 or FFF for the first three digits; these values are reserved.

After specifying basic Channel settings, choose a button according to the following:

To configure advanced settings, choose Advanced, and see Advanced Channel Settings.

To accept the settings, and use the advanced settings set by default or previously configured, choose OK.

To exit the dialog box without accepting the settings, choose Cancel.

To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


Advanced Channel Settings

SNA Server is designed to provide reasonable defaults for connections whenever possible, especially for advanced settings.

After choosing Advanced in the Channel Attached Setup dialog box, find the items appropriate to your configuration, and supply information as follows:

XID Type

Select the XID Type. Most systems use Format 3.

When SNA Server is configured to use Format 0 over a host connection, the host treats it as a PU type 2.0, and so SNA Server exercises only its PU type 2.0 capabilities. When SNA Server establishes a host or peer connection using Format 3 and independent LUs, SNA Server exercises its PU type 2.1 capabilities.

Max BTU Length

Specify the maximum for the BTU length.

See Note About Max BTU Length.

To exit the dialog box without accepting the configuration settings, choose Cancel. To accept the settings, choose OK.

To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


FOLLOWING TOPIC IS BASICALLY THE SAME AS A TOPIC IN DBOXS.RTF


Connection Activation Limits Dialog Box

Supply activation limits for the connection:

Maximum number of attempts

Select the number of attempts for SNA Server to make when trying to establish the connection. After making this number of attempts, SNA Server makes an entry in the event log and stops trying. The range is from 1 through No Limit; the default is No Limit.

Delay after failed attempts

Select the length of time for SNA Server to wait between attempts to establish the connection. The range is from 5 seconds through 255 seconds; the default is 10 seconds.


JAN, REMEMBER TO COPY CHANGES TO THE 3270 (INDIVIDUAL) TOPIC OVER TO THE 3270 (RANGE) TOPIC.


Assigning, Viewing, or Modifying 3270 LUs

The 3270 LU allows a user to access a mainframe through 3270 terminal emulation software on a PC. For a complete list of the steps for configuring for 3270, see Configuring for 3270 Terminal Emulation.

You can create LUs one at a time or in a consecutively numbered range (except on a DFT connection, where you must create LUs one at a time). When you create a range of LUs, all the LUs are given the same properties. You can modify individual LUs after creating them.

To assign a new 3270 LU or a range of 3270 LUs

1	In the Servers and Connections window, select the connection to which you want to assign the 3270 LU(s).

2	On the Toolbar, click  [image].

3	In the Insert dialog box, under New Logical Unit, select 3270.

4	To add a range of LUs instead of just one, select Range of LUs.

On a DFT connection, you cannot add a range of LUs.

5	Choose OK.

To configure an LU, see Configuring Properties for a 3270 LU.

To begin configuring a range of 3270 LUs, see Configuring Numbering for a 3270 LU Range.

To access an existing 3270 LU for viewing or modifying

1	In the Servers and Connections window, select the LU you want to view or modify.

2	On the Toolbar, click  [image].

For information about LU properties, see Configuring Properties for a 3270 LU.

See also Copying Properties Between Connections or LUs, Moving an LU, and Setting Up 3270 User and Group Access: Overview.


JAN, REMEMBER TO COPY CHANGES FROM 3270 TOPICS TO LUA TOPICS AND VICE VERSA.


Configuring for 3270 Terminal Emulation

The basic steps for configuring for 3270 terminal emulation are as follows:

1	Configure the servers and connections that will be needed for 3270 terminal emulation.

2	Assign 3270 LUs to the connections, and configure the LUs.

One or many LUs can be assigned to a given connection.

3	Add users and/or groups to the list recognized by SNA Server. These users and/or groups must already have network accounts.

4	Optionally, create 3270 LU pools and assign 3270 LUs to them.

5	Assign the LUs and/or LU pools to users and/or groups.

6	To put configuration changes into effect, save the configuration file and restart the affected SNA server.


JAN, NUMBERING TOPIC COMES IN A GENERIC VSN FOR DBOX AND IN SPECIAL VSNS FOR 3270, LUA, DN.


Configuring Numbering for a 3270 LU Range

After assigning a range of 3270 LUs to a connection, in the Add LU Range dialog box, supply information as follows:

Base LU Name

Type the Base LU Name.

First LU Number

Type the first LU Number in the range.

Number of LUs

Type the number of LUs that you want in the LU range. Check with the host administrator to find out how many LUs are available for your system.

Note  The LU numbers generated for an LU range are sequential. If the numbers assigned by your host administrator are not sequential, you can modify the numbers of individual LUs after they have been created.

When you have typed the appropriate LU range values, choose one of the following:

To modify the extension numbering format (displayed under Selected LU Range), choose Options. See Modifying the Extension Numbering Format.

To exit the dialog box without accepting the settings, choose Cancel.

To accept the settings and begin configuring the properties for the LU range, choose OK.


Modifying the Extension Numbering Format

To modify the numbering format of the extension numbers for the LU range, type values for the following:

First Extension

Type the first extension number in the range. If the base name is six characters long, limit the extensions to two digits or less. If the base name is five characters long, limit the extensions to three digits or less.

Number System

Select Decimal or Hexadecimal. The number system affects the extension number, not the LU number. The default is Decimal.

Add Leading Zeroes ( 07 vs. 7 )

Clear this box if you do not want leading zeroes to be added to the extension numbers. Leading zeroes ensure that LU names will display in correct order.


Configuring Properties for a 3270 LU

After assigning or viewing a 3270 LU, supply the information in the following list. If you are configuring a DFT 3270 LU, see also Numbers Needed for DFT LUs.

Note  After making configuration changes, to put the changes into effect, restart the SNA server, as described in Restarting an SNA Server.

LU Number (for LUs on 802.2, SDLC, or X.25)

Type the LU Number.

If the LU is on a DFT connection , it does not use an LU number, but requires other identifying numbers instead. For information, see Numbers Needed for DFT LUs.

LU Name

Type the LU Name.

Connection

The connection for this LU is shown. The connection cannot be changed from this dialog box. To change the connection after configuring the LU, see Moving an LU.

Pool

If the LU has already been assigned to a pool, the pool name appears here.

Comment

Optionally, type a comment of up to 25 characters.

LU Type

Select Display if the LU will be used for display (terminal emulation). Select Printer if the LU will be used to print from the host system to a local printer or a local area network printer.

Display Model

If you select Display for the LU Type, you can select a Display Model.

When an LU is assigned to a pool, the display model setting for the pool overwrites the setting of the LU, and the setting displayed in the 3270 LU Properties dialog box is dimmed.

Some emulators can only emulate certain display models. For more information, see your emulator documentation.

Model can be overridden

Select this check box to allow the user to override the display model type by using a 3270 terminal emulation program. See also Note on LU and LU Pool Settings.


Numbers Needed for DFT LUs

An LU on a DFT connection does not require an LU number, but instead uses the following:

Port Number

Type the number of the DFT adapter that will be used. (This is not the port of the 3174.) The range is from 1 through 4.

LT Number

Type the logical terminal number as configured at the 3174 for this coaxial cable. The range is from 1 through 5.


Determining the LUs Assigned to a DFT Adapter

To determine which LUs are assigned to a given DFT adapter, use the SNADFTLU.EXE utility provided with SNA Server.

To use the SNADFTLU.EXE utility:

1	Make sure that all SNA Server services are stopped; this includes all connections, link services, and the SNA server (node). To stop a connection or the SNA server, select it and then select [image].

2	Switch to a command prompt.

3	Type

snadftlu

The program displays the available LU numbers for each coaxial connection in your installation.

Note  If you have multiple DFT adapters that communicate with a 3174 controller running either microcode level 5.0 or later, or B1.0 or later, and the LU addresses are set up multiple times on the ports to which the adapters are attached, you must set up each DFT adapter with its own device driver, link service, and connection.


Configuring Properties for a 3270 LU Range

After assigning and numbering a range of 3270 LUs, in the 3270 LU Range Properties dialog box, supply the information in the following list.

Note  After making configuration changes, to put the changes into effect, restart the SNA server, as described in Restarting an SNA Server.

LU Numbers

The range of LU numbers that you entered appears here.

LU Names

The range of LU names that you entered appears here.

Connection

The connection for the LU range is shown. The connection cannot be changed from this dialog box. To change the connection after configuring the LUs, see Moving an LU.

Comment

Optionally, type a comment of up to 25 characters.

LU Type

Select Display if the LUs will be used for display (terminal emulation). Select Printer if the LUs will be used to print from the host system to a local printer or a local area network printer.

Display Model

If you select Display for the LU Type, you can select a Display Model.

Some emulators can only emulate certain display models. For more information, see your emulator documentation.

Model can be overridden

Select this check box to allow the user to override the display model type by using a 3270 terminal emulation program.


JAN, REMEMBER THAT THERE'S ANOTHER COPY OF "MOVING A CONNECTION TO A DIFFERENT SERVER" IN S_ONLY.RTF.


Copying and Moving Services

You can copy properties from one service to another, that is, from one connection or LU to another. You can also move a connection to a different server or move an LU to a different connection.

Note  After making configuration changes, to put the changes into effect, restart the SNA server, as described in Restarting an SNA Server.

To copy properties between connections or LUs

1	In the Servers and Connections window, select the connection or LU from which you want to copy properties.

2	From the Services menu, choose Copy Properties.

3	In the Copy Properties dialog box, select the connection or LU you want to copy properties to.

If you copy properties to an active service, the properties take effect when the service is restarted.

4	Choose OK.

To move a connection to a different server, or move an LU to a different connection or server

1	In the Servers and Connections window, click the connection or LU once to highlight it.

2	Point to the highlighted item with the mouse pointer.

3	Press and hold the left mouse button and move the mouse.

An icon representing the item moves on the screen. While the icon is in a place where releasing it has no effect, it changes to a slashed circle.

4	When the icon is on the intended location, release the mouse button.

An LU, other than a local APPC LU, can be assigned to a connection only. A local APPC LU or a connection can be assigned to a server only.


Copying Properties Between Connections or LUs

1	In the Servers and Connections window, select the connection or LU from which you want to copy properties.

2	From the Services menu, choose Copy Properties.

3	In the Copy Properties dialog box, select the connection or LU to which you want to copy properties.
If you copy properties to an active service, the properties take effect when the service is restarted.

4	Choose OK.


Moving an LU

To move an LU by dragging and dropping it:

1	In the Servers and Connections window, click the LU once.
The LU is highlighted to show that it is selected.

2	Point to the LU with the mouse pointer.

3	Press and hold the left mouse button and move the mouse.
An icon representing the LU moves on the screen. The icon changes to a slashed circle while in a place where releasing the LU has no meaning.

4	When the icon is on the intended connection (or for a local APPC LU, on the intended server), release the mouse button.


LUs for APPC: Overview

APPC over an SNA network requires at least two LUs--one for each direction of the communications. The APPC LUs, which are LU type 6.2, are used by transaction programs (TPs) or by 5250 emulators. The following diagrams illustrate how TPs use LU 6.2 for APPC:

Two TPs Using LU 6.2

Three TPs Using LU 6.2

For more information about TPs, see the Microsoft SNA Server Administration Guide, the Microsoft SNA Server APPC Programmer's Guide, and the Microsoft SNA Server CPI-C Programmer's Guide.

APPC generally uses a local LU and one or more remote LUs. A local APPC LU can be independent or dependent. For more information about independent and dependent local APPC LUs, see the following:

Independent APPC Diagram

Characteristics of Independent LUs

Dependent APPC Diagram

Characteristics of Dependent LUs

If you will be using APPC or CPI-C with an AS/400, see AS/400 Configuration. To configure hot backup for 5250 emulation, see Configuring Hot Backup for LUs for 5250. For additional details about configuring for the AS/400 environment, see Chapter 7 of the Microsoft SNA Server Administration Guide.

 If you will be supporting clients that use the PC Support router, see Note About PC Support.

Configuring APPC LUs for TPs or for 5250 Emulation

APPC LUs are used for TPs or for 5250 emulation. APPC LUs used with TPs are generally used for communication between TPs on different systems, not communication between TPs on a single system. For information about configuring LUs for TPs on a single system, see Basic Steps for Single-System APPC.

The following list outlines the steps for configuring APPC LUs for 5250 emulation or for TPs on two different systems. For detailed information about configuring APPC LUs, see the topics in Topic List for APPC LUs.

1	Assign the local APPC LU to a server.

Note  The local APPC LU is assigned to a server, not a connection.

2	Configure the local APPC LU:

For an independent LU, specify LU Alias, Network Name, and LU Name. Depending on system configuration, you may need to specify other information.

For a dependent LU, specify LU Alias, LU Number, and LU Name.. Depending on system configuration, you may need to specify other information.

3	Assign the remote APPC LU to a connection.

Note  The remote APPC LU is assigned to a connection, not a server.

4	Configure the remote APPC LU:

For a remote LU to be used with an independent local LU, specify LU Alias, Network Name and LU Name. Depending on system configuration, you may need to specify other information. For communication with an AS/400, make the remote LU Name the same as the name of the AS/400.

For a remote LU to be used with a dependent local LU, specify LU Alias, Network Name, LU Name, and Uninterpreted LU Name. Depending on system configuration, you may need to specify other information.

5	If an appropriate mode has not already been configured, configure it.

For communication with an AS/400, skip this step, because the necessary mode (QPCSUPP) is supplied with SNA Server.

6	View or create LU-LU pairs, depending on whether you are using automatic partnering:

About viewing automatically created pairs

About creating pairs

7	Optionally, configure session security for the remote LU.

8	Optionally, assign a default local APPC LU and/or a default remote APPC LU to users and/or groups.

For information about default LUs in AS/400 environments, see Note About AS/400s.

See also Precedence of Accounts in Determining Default LUs.

9	If you will be using CPI-C, configure one or more CPI-C symbolic destination names.

10	If you will be using the DISPLAY verb, you may want to change the default connection that SNA Server uses for the verb. For detailed information about the DISPLAY verb and how it uses a default connection, see the Microsoft SNA Server APPC Programmer's Guide.

11	To ensure that all changes take effect, restart the SNA server, as described in Restarting an SNA Server.

For detailed descriptions of the preceding APPC tasks, see Topic List for APPC LUs, Adding, Viewing, or Editing CPI-C Information, and Configuring the Default DISPLAY Connection.


The following diagram shows how two TPs use LU 6.2 for APPC:


The following diagram shows how three TPs use LU 6.2 for APPC:


Independent APPC is shown in the following diagram:

In the diagram, two TPs communicate via APPC LUs. The local LU in the diagram is considered an independent local APPC LU because it does not depend on another system (a host) for communicating with the remote TP.


Dependent APPC is shown in the following diagram:

The dependent local LU requires the support of the host configuration in order to communicate with the remote LU and the remote TP.


[]JAN: PC SUPPORT IS DUPLICATED IN TWO CONTEXTS: THE CONTEXT FOR A POPUP, AND THE CONTEXT FOR A REGULAR TOPIC ACCESSED FROM THE KEYWORD LIST.  KEEP BOTH COPIES UPDATED.


Note About PC Support

For important information about using PC Support with SNA Server, see the following:

Microsoft SNA Server Installation Guide (Chapter 3), or the Readme file  for the MS-DOS-based client

The main Readme file for SNA Server

Microsoft SNA Server Reference (Appendix C, under the description of the environment variable OverrideDefaultLU)

Microsoft SNA Server Administration Guide (Chapter 7)


Note About PC Support

For important information about using PC Support with SNA Server, see the following:

Microsoft SNA Server Installation Guide (Chapter 3), or the Readme file  for the MS-DOS-based client

The main Readme file for SNA Server

Microsoft SNA Server Reference (Appendix C, under the description of the environment variable OverrideDefaultLU)

Microsoft SNA Server Administration Guide (Chapter 7)


[]JAN: SINGLE-SYSTEM IS DUPLICATED IN TWO CONTEXTS: THE CONTEXT FOR A SECONDARY WINDOW FROM ANOTHER WINDOW, AND THE CONTEXT FOR A REGULAR WINDOW FROM THE SEARCH LIST.  KEEP BOTH COPIES UPDATED.


Basic Steps for Single-System APPC

Single-system APPC is generally used for testing TPs. The basic steps for single-system APPC are as follows:

1	Assign two local APPC LUs to a server.

Note  The local APPC LUs are assigned to a server, not a connection.

2	Configure the local APPC LUs by specifying LU Alias, Network Name, and LU Name.

3	If an appropriate mode has not already been configured, configure it.

Note that for single-system APPC, the Automatic Activation Limit in the mode is meaningless.

4	Pair the two local APPC LUs together, and assign a mode to the LU-LU pair.

5	If you will be using CPI-C, configure one or more CPI-C symbolic destination names.

Detailed descriptions for these tasks are given in the APPC LU topics and in the CPI-C topics.


[]JAN: SINGLE-SYSTEM IS DUPLICATED IN TWO CONTEXTS: THE CONTEXT FOR A SECONDARY WINDOW FROM ANOTHER WINDOW, AND THE CONTEXT FOR A REGULAR WINDOW FROM THE SEARCH LIST.  KEEP BOTH COPIES UPDATED.


Basic Steps for Single-System APPC

Single-system APPC is generally used for testing TPs. The basic steps for single-system APPC are as follows:

1	Assign two local APPC LUs to a server.

Note  The local APPC LUs are assigned to a server, not a connection.

2	Configure the local APPC LUs by specifying LU Alias, Network Name, and LU Name.

3	If an appropriate mode has not already been configured, configure it.

Note that for single-system APPC, the Automatic Activation Limit in the mode is meaningless.

4	Pair the two local APPC LUs together, and assign a mode to the LU-LU pair.

5	If you will be using CPI-C, configure one or more CPI-C symbolic destination names.

Detailed descriptions for these tasks are given in the APPC LU topics and in the CPI-C topics.


Characteristics of Independent LUs

Independent LUs have the following characteristics:

They can support multiple parallel sessions.

If the independent local APPC LU communicates with a TP on a host (which is possible), the host system must be using VTAM version 3, release 2, or later with either NCP version 5, release 2, or later (3745 systems), or NCP version 4, release 3, or later (3725 systems).

For independent LUs that communicate with a host, the LOCADDR parameter should be set to 0 in VTAM or in the NCP Gen.

On connections used for independent APPC, the XID Type must be Format 3.


Characteristics of Dependent LUs

Dependent local APPC LUs have the following characteristics:

They allow only a single session per LU.

They use a connection configured with a Remote End of Host, not Peer.

They are the only kind of APPC LUs that SNA Server supports when communicating with a host using a version of VTAM earlier than version 3, release 2.

They require the host VTAM to use a value of 1 or greater in the LOCADDR= parameter of the LU definition.


   Topic List for APPC LUs

  LUs for APPC: Overview

  Assigning a Local or Remote APPC LU

  Viewing or Modifying a Local or Remote APPC LU

  Configuring Local APPC LU Properties

  Configuring Remote APPC LU Properties

  Configuring Modes for LU-LU Pairs

  Pairing Local and Remote LUs

  Configuring Session Security for Remote LUs

  Assigning Default APPC LUs to Users or Groups

Forms and Reference Information

  SNA Server Preparation Forms

  AS/400 Configuration

  Configuring Hot Backup for LUs for 5250

  Sample VTAM Parameters for LU 6.2

  Sample CICS Configuration Screens for LU 6.2


Viewing or Modifying a Local or Remote APPC LU

To access an existing APPC LU for viewing or modifying

1	In the Servers and Connections window, select the server (for a local APPC LU) or the connection (for a remote APPC LU) on which the LU is located.

The LU appears in the right side of the window.

2	Select the LU.

3	On the Toolbar, click  [image].

For information about APPC LU properties, see Configuring Local APPC LU Properties or Configuring Remote APPC LU Properties.

See also Copying Properties Between Connections or LUs and Moving an LU. When you copy the properties of an APPC LU, you also copy the pairings associated with that LU.


Assigning a Local or Remote APPC LU

Local and remote APPC LUs work together in pairs. The local APPC LU is assigned to a server (unlike other LUs); the remote APPC LU is assigned to a connection.

To assign a local APPC LU

1	In the Servers and Connections window, select a  [image]  server.

Note  Select a server, not a connection, if you want to assign a local APPC LU.

2	On the Toolbar, click  [image].

3	In the Insert dialog box, select APPC [Local].

4	Choose OK.

To configure the LU, see Configuring Local APPC LU Properties.

To assign a remote APPC LU

1	In the Servers and Connections window, select the connection to assign the LU to.

Note  Select a connection, not a server, if you want to assign a remote APPC LU.

See also Note About Remote End for Connections Used for APPC.

2	On the Toolbar, click  [image].

3	In the Insert dialog box, select APPC [Remote].

4	Choose OK.

To configure the LU, see Configuring Remote APPC LU Properties.


Note About Remote End for Connections Used for APPC

Remote APPC LUs can be assigned to connections that have a Remote End of Host System, or a Remote End of Peer System. Select the Remote End for such a connection as follows:

If the remote APPC LU will be used for independent APPC, that is, without the support of a host, select Peer for the Remote End of the connection that the LU will be assigned to.

If the remote APPC LU will be used for dependent APPC, that is, with the support of a host, select Host for the Remote End of the connection that the LU will be assigned to.


Configuring Local APPC LU Properties

Local APPC LUs can be independent or dependent. For more information, see LUs for APPC: Overview, Independent APPC Diagram, and Dependent APPC Diagram.

After assigning a local LU to a server, in the New APPC LU Properties dialog box, or the APPC LU Properties dialog box, supply information as follows:

LU 6.2 Type

Select Independent or Dependent. If the local LU will be used with a remote LU on a DFT connection, the local LU must be Dependent.

LU Alias

Type the LU Alias.

Network Name

Type the Network Name. Obtain the correct name from the host or peer administrator. If you will be connecting to a host system with VTAM, see also Note About APPC LU Parameters and VTAM.

For independent LUs, the Network Name is required. For dependent LUs, the Network Name is recommended but not required, since it is used only by local software, such as the Windows NT event log software.

LU Name

Type the LU Name. See Note About LU Name.

LU Number

For dependent LUs, type the LU Number.

For independent LUs, this field is unavailable.

Comment

Optionally, type a comment of up to 25 characters.

Enable Automatic Partnering

To designate the LU as a local automatic partner, select Enable Automatic Partnering. To avoid designating the local LU as an automatic partner, so that it is only partnered with the remote LUs and modes you explicitly choose, clear Enable Automatic Partnering. See Note on Automatic Partnering.

Member of Default Outgoing Local APPC LU Pool

If you want this LU to be available for use by a 5250 user or invoking TP not specifying a local LU, select this check box. See Note About the Default Outgoing Local APPC LU Pool.

This default pool differs from, and should not be confused with, the 3270, LUA, and downstream LU pools configured in the LU Pools window.

Implicit Incoming Remote LU

To specify an implicit incoming remote LU, choose an existing remote LU name from the list. See Steps for Using Implicit Remote LUs and Modes.

Timeout for Starting Invokable TPs

Specify the Timeout for Starting Invokable TPs. If the invokable TP is started manually by an operator, specify a value greater than 60 seconds to give the operator sufficient time.

If you have already configured a remote LU to pair with this LU, and you want to create the LU-LU pair, select Partners, and see Pairing Local and Remote LUs.


Configuring Remote APPC LU Properties

After assigning a remote LU to a connection, in the New APPC Remote LU Properties dialog box or the APPC Remote LU Properties dialog box, supply information as follows:

LU Alias

Type an LU Alias.

Network Name

Type the Network Name. Obtain the correct name from the host or peer administrator. If you will be connecting to a host system with VTAM, see also Note About APPC LU Parameters and VTAM.

LU Name

Type the LU Name. See Note About LU Name.

For communication with an AS/400, make the remote LU Name the same as the name of the AS/400.

Uninterpreted LU Name

If this LU will be paired with a dependent local APPC LU, type the Uninterpreted LU Name.

Comment

Optionally, type a comment of up to 25 characters.

Supports Parallel Sessions

If this LU will be used with an independent local LU, and parallel sessions will be used, select this check box. If this LU will be used with a dependent local APPC LU, do not select this box.

If a remote LU supports parallel sessions, it can only be used with a mode that has a value greater than 1 for the parallel session limit.

Enable Automatic Partnering

To designate the LU as a remote automatic partner, select Enable Automatic Partnering. To avoid designating the remote LU as an automatic partner, so that it is only partnered with the local LUs and modes you explicitly choose, clear Enable Automatic Partnering. See Note on Automatic Partnering.

Implicit Incoming Mode

To designate a mode as the implicit incoming mode for this LU, select a mode name from the list.

If this remote LU will be used as an implicit incoming remote LU, be sure to select a mode from the list.

To create a new mode to use as the implicit incoming mode, choose the Partners button, then the Modes button, and see Configuring Modes for LU-LU Pairs.

See also Steps for Using Implicit Remote LUs and Modes.

If you have already configured a local LU to pair with this LU, and you want to create the LU-LU pair, select Partners, and see Pairing Local and Remote LUs.


Pairing Local and Remote LUs

After assigning and configuring all necessary APPC LUs (both local and remote), in the Properties dialog box for the local or remote LU, choose Partners. The LU 6.2 Partner LUs dialog box appears.

If you enabled automatic partnering for the selected LU, and also enabled automatic partnering for one or more partner LUs and modes, the LU-LU pairs that have automatically been generated appear in the LU 6.2 Partner LUs dialog box. For communication with an AS/400, be sure that QPCSUPP is the only mode used.

In the LU 6.2 Partner LUs dialog box, select buttons as appropriate:

Add

To add a partner to the list for this LU, choose Add. Then, in the Add APPC LU Partner dialog box, select the partner LU and mode for the LU-LU pair. See Note About Uniqueness of Pairs.

For communication with an AS/400, use the QPCSUPP mode (provided with SNA Server).

If you have not already configured the other LU for this LU-LU pair, close or cancel all dialog boxes, and in the Servers and Connections window, begin the process of assigning and configuring the new LU. See Assigning a Local or Remote APPC LU.

A number of standard modes (including QPCSUPP) are provided with SNA Server, as described in Properties of Standard Modes. If you need to create additional modes, choose the Modes button and see Configuring Modes for LU-LU Pairs.

Delete

To delete a partner LU from the list, select the partner to delete, and choose Delete.

Modes

SNA Server keeps a list of modes available for LU-LU pairs; to change the list by adding, deleting, or configuring modes, select Modes. A number of standard modes are provided with SNA Server; if you need to create additional modes, choose the Modes button and create them before adding LU-LU pairs. For more information, see Properties of Standard Modes and Configuring Modes for LU-LU Pairs.

Note  To associate an existing mode with an LU-LU pair, choose Add, not Modes.

When you are finished configuring the partners in the LU 6.2 Partner LUs dialog box, choose Close.

To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


To choose a button in a dialog box

Click the button.

--or--

Press TAB until the button is selected, and then press ENTER.


Steps for Using Implicit Remote LUs and Modes

To make use of an Implicit Incoming Remote LU and Implicit Incoming Mode:

1	Configure an appropriate remote LU.

2	Configure one or more local LUs that are appropriate.

All incoming requests must specify a local LU name that is recognized by SNA Server, even when an Implicit Incoming Remote LU and Implicit Incoming Mode are used.

3	Assign the remote LU (configured in step 1) as the Implicit Incoming Remote LU for the local LU(s) (configured in step 2).

4	Configure a mode that is appropriate for the implicit incoming mode.

5	Assign the mode (configured in step 4) as the Implicit Incoming Mode for the remote LU (configured in step 1).


Configuring Modes for LU-LU Pairs

For a list of the standard modes available with SNA Server, see Properties of Standard Modes.

After configuring local and remote APPC LUs, from the Properties dialog box for either a local or a remote LU, choose Partners. Next, in the LU 6.2 Partner LUs dialog box, choose Modes. In the APPC Mode Properties dialog box, you can configure a new mode, or delete or modify an existing one.

Procedures for the APPC Mode Properties Dialog Box

  To add a mode to the list

  To delete a mode

  To modify an existing mode

In the APPC Mode Properties dialog box, find the item(s) appropriate to your configuration, and supply information as follows:

Mode Name

Type a Mode Name.

Comment

Optionally, type a comment of up to 25 characters.

Parallel Session Limit

Specify the maximum number of sessions allowed with this mode. To allow only a single session, specify 1. To allow parallel sessions, specify a value greater than 1. If the local APPC LU to be used with this mode is dependent, specify 1; dependent local APPC LUs cannot have parallel sessions. See also Note on Parallel Session Limits.

Minimum Contention Winner Limit

Specify the Minimum Contention Winner Limit. The sum of the Minimum Contention Winner Limit and the Partner Min Contention Winner Limit must be less than or equal to the Parallel Session Limit.

Partner Min Contention Winner Limit

Specify the Partner Min Contention Winner Limit. The sum of the Partner Min Contention Winner Limit and the Minimum Contention Winner Limit must be less than or equal to the Parallel Session Limit.

Automatic Activation Limit

Specify the number of contention winner sessions to be activated for the local LU whenever the connection for this mode is started. In a local contention winner session, the local LU can initiate conversations without permission from the partner LU.

For single-system APPC (communication between two local LUs on the same system), this field is meaningless.

Enable Automatic Partnering

To allow the mode to be associated with remote LUs and local LUs designated for automatic partnering, use the default setting of Enable Automatic Partnering. To avoid designating the mode as an automatic partner, so that it is only associated with the remote LUs and modes you explicitly choose, clear Enable Automatic Partnering. See Note on Automatic Partnering.

High Priority Mode

Select this check box to give preference to communication with this mode over communication with a low-priority mode.

Pacing Send Count

Specify the maximum number of frames for the local LU to send without an SNA pacing response from the partner LU. If you specify 0, the local LU can send an unlimited number of frames without receiving a response; in this case, the partner LU can negotiate and set a limit on the count.

Pacing Receive Count

Specify the maximum number of frames for the local LU to receive from the partner LU before the local LU sends an SNA pacing response. If you specify 0, the local LU can receive an unlimited number of frames without sending a response.

Max Send RU Size

Specify the maximum size for RUs sent by the TP(s) on the local system.

It is not necessary to set a minimum send RU size, which is 256 on SNA Server.

Max Receive RU Size

Specify the maximum size for RUs received from the TP(s) on the remote system.

It is not necessary to set a minimum receive RU size, which is 256 on SNA Server.

When you are finished with the APPC Mode Properties dialog box, choose Close.


[]JAN: STANDARD MODES IS DUPLICATED IN TWO CONTEXTS: THE CONTEXT FOR A SECONDARY WINDOW FROM ANOTHER WINDOW, AND THE CONTEXT FOR A REGULAR WINDOW FROM THE SEARCH LIST.


Properties of Standard Modes

The modes provided with SNA Server have the following properties:

QPCSUPP
Parallel Session Limit	64
Minimum Contention  Winner Limit	32
Partner Min Contention Winner Limit	0
Automatic Activation Limit	0
Enable Automatic Partnering	Yes
High Priority Mode	Yes
Pacing Send Count	7
Pacing Receive Count	7
Max Send RU Size	1024
Max Receive RU Size	1024
#BATCH,  #BATCHSC, and  BLANK
Parallel Session Limit	8
Minimum Contention  Winner Limit	4
Partner Min Contention Winner Limit	0
Automatic Activation Limit	0
Enable Automatic Partnering	No
High Priority Mode	No
Pacing Send Count	3
Pacing Receive Count	3
Max Send RU Size	1024
Max Receive RU Size	1024
#INTER and #INTERSC
Parallel Session Limit	8
Minimum Contention  Winner Limit	4
Partner Min Contention Winner Limit	0
Automatic Activation Limit	0
Enable Automatic Partnering	No
High Priority Mode	Yes
Pacing Send Count	7
Pacing Receive Count	7
Max Send RU Size	1024
Max Receive RU Size	1024


[]JAN: STANDARD MODES IS DUPLICATED IN TWO CONTEXTS: THE CONTEXT FOR A SECONDARY WINDOW FROM ANOTHER WINDOW, AND THE CONTEXT FOR A REGULAR WINDOW FROM THE SEARCH LIST.


Properties of Standard Modes

The modes provided with SNA Server have the following properties:

QPCSUPP
Parallel Session Limit	64
Minimum Contention  Winner Limit	32
Partner Min Contention Winner Limit	0
Automatic Activation Limit	0
Enable Automatic Partnering	Yes
High Priority Mode	Yes
Pacing Send Count	7
Pacing Receive Count	7
Max Send RU Size	1024
Max Receive RU Size	1024
#BATCH,  #BATCHSC, and  BLANK
Parallel Session Limit	8
Minimum Contention  Winner Limit	4
Partner Min Contention Winner Limit	0
Automatic Activation Limit	0
Enable Automatic Partnering	No
High Priority Mode	No
Pacing Send Count	3
Pacing Receive Count	3
Max Send RU Size	1024
Max Receive RU Size	1024
#INTER and #INTERSC
Parallel Session Limit	8
Minimum Contention  Winner Limit	4
Partner Min Contention Winner Limit	0
Automatic Activation Limit	0
Enable Automatic Partnering	No
High Priority Mode	Yes
Pacing Send Count	7
Pacing Receive Count	7
Max Send RU Size	1024
Max Receive RU Size	1024


1	In the Mode Name box, type a name containing from one through eight characters; the name can include alphanumeric characters and/or $, #, and @. Lowercase letters are converted to uppercase. The first character cannot be a digit. The mode name cannot be the same as any other mode name in the domain of the server.

2	Specify parameters as described in the list that follows.

3	Choose Add.

4	Choose Close.


1	In the Mode Name box, select a mode name.

2	Choose Delete.

3	Choose Close.


1	In the Mode Name box, select a mode name.

2	Change one or more parameters as described in the list that follows.

3	Choose Change.

4	Choose Close.


Note on Parallel Session Limits

One of the key mode properties is the parallel session limit. This limit determines whether an LU-LU pair can carry on only one interaction at a time (a parallel session limit of 1), or multiple concurrent interactions (a parallel session limit greater than 1). If parallel sessions are to be allowed with an LU-LU pair, the local LU must be independent, the connection cannot be a DFT connection, and the remote LU in the pair must support parallel sessions.

If the LU-LU pair can carry on multiple parallel sessions, other mode properties, such as minimum contention-winner limit, determine to what extent each LU can initiate interactions.


Configuring Session Security for Remote LUs

Session security for remote LUs is optional.

  To access the APPC Session Security dialog box

In the APPC Session Security dialog box, find the item(s) appropriate to your configuration, and supply information as follows:

No Session-Level Security

Select this option to turn off Session-Level Security.

Security Key in Hex

For a security key in hexadecimal, select this option, then type a 16-digit hexadecimal number.

Security Key in Characters

For a security key in characters, select this option, then type an eight-character string. The string can include uppercase and lowercase alphanumeric characters, and the special characters $, @, #, and the period (.).

To exit the dialog box without accepting the configuration settings, choose Cancel. To accept the settings, choose OK.

To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


1	In the Servers and Connections window, select the remote APPC LU.

2	On the Toolbar, click  [image].

3	In the APPC Remote LU Properties dialog box, choose Security.

The APPC Session Security dialog box appears.


Adding, Viewing, or Editing CPI-C Information

If you are using applications based on CPI-C, you will need to configure one or more CPI-C symbolic destination names.

To add, delete, view, or edit CPI-C symbolic destination names

1	From the Options menu, choose CPI-C.

2	If you want to delete, view, or edit a symbolic destination name, under CPI-C Symbolic Destination Name, select the name.

3	Choose the appropriate button:

Add (for adding a symbolic destination name)

Delete (for deleting the selected symbolic destination name)

Edit (for viewing or editing the selected symbolic destination name)

4	To configure properties for a CPI-C symbolic destination name, see Configuring Properties for CPI-C.

When you are finished with the CPI-C Symbolic Destination Name Properties dialog box, choose Close.


Configuring Properties for CPI-C

After adding or viewing a CPI-C symbolic destination name, in the CPI-C Symbolic Destination Name Properties dialog box, find the item(s) appropriate to your configuration, and supply information as follows:

Name

Type the symbolic destination name.

Comment

Optionally, type a comment of up to 25 characters.

Partner TP Name

Application TP  For an application TP, select this option, and type the Application TP Name.

SNA Service TP ( in hex )  For an SNA Service TP, select this option, and type the SNA Service TP Number.

Partner LU Name

Alias  To identify the partner LU by Alias, select this option, and type the alias.

Fully Qualified  To identify the partner LU by a Fully Qualified name, select this option, and type the name.

Mode Name

Select a Mode Name. For information about modes, see topics in Topic List for APPC LUs.

Conversation Security

Select a Conversation Security option:

None  To turn off conversation security, select None.

Same  To require the same user ID and password as that of the remote partner LU, select Same.

Program  To specify the user ID and password, select Program, and then choose User ID. For information, see To specify a User ID and Password.

To accept the settings, choose OK; to exit the dialog box without accepting the settings, choose Cancel.

To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


To specify a User ID and Password

1	In the CPI-C Security Settings dialog box, type the User ID, which can contain from 1 through 10 characters.

2	Type the password, which can contain from 1 through 10 characters.

3	In the Verify Password field, type the password again.

4	Choose OK.


Configuring the Default DISPLAY Connection

When the DISPLAY verb is used but does not specify a connection, SNA Server uses the connection you specify in the Display Verb Options dialog box. If you do not specify a default DISPLAY connection, SNA Server randomly selects a connection for the verb to use.

To change the default DISPLAY connection

1	From the Options menu, choose Display Verb.

2	Under Display Verb uses Connection for Default, select a connection.

3	Choose OK.

To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


Assigning, Viewing, or Modifying LUA LUs

An LUA LU allows a connection to communicate with host applications using LU 0, 1, 2, or 3 protocols. Before configuring an LU, configure the server and connection the LU will use. For more information, see Configuring Servers, Connections, and LUs: Overview and Configuring Servers and Connections.

You can create LUs one at a time or in a consecutively numbered range (except on a DFT connection, where you must create LUs one at a time). When you create a range of LUs, all the LUs are given the same properties. You can modify individual LUs after creating them.

To assign an LUA LU, or a range of LUA LUs

1	In the Servers and Connections window, select the connection to assign the LU(s) to.

2	On the Toolbar, click  [image].

3	In the Insert dialog box, select LUA.

4	To add a range of LUs instead of just one, select Add Range of LUs.

On a DFT connection, you cannot add a range of LUs.

5	Choose OK.

To configure an LU, see Configuring Properties for LUA LUs.

To begin configuring a range of LUs, see Configuring Numbering for an LUA LU Range.

To access an existing LUA LU for viewing or modifying

1	In the Servers and Connections window, select the LU that you want to view or modify.

2	On the Toolbar, click  [image].

For information about LUA properties, see Configuring Properties for LUA LUs.

See also Copying Properties Between Connections or LUs and Moving an LU.


JAN, REMEMBER TO COPY CHANGES FROM 3270 TOPICS TO LUA TOPICS AND VICE VERSA. THE "CONFIGURING NUMBERING" TOPICS ARE THE SAME FOR 3270 AND LUA, EXCEPT FOR THE SEE ALSOS.


Configuring Numbering for an LUA LU Range

After assigning a range of LUA LUs to a connection, in the Add LU Range dialog box, supply information as follows:

Base LU Name

Type the Base LU Name.

First LU Number

Type the first LU Number in the range.

Number of LUs

Type the number of LUs that you want in the LU range. Check with the host administrator to find out how many LUs are available for your system.

Note  The LU numbers generated for an LU range are sequential. If the numbers assigned by your host administrator are not sequential, you can modify the numbers of individual LUs after they have been created.

When you have typed the appropriate LU range values, choose one of the following:

To modify the extension numbering format (displayed under Selected LU Range), choose Options. See Modifying the Extension Numbering Format.

To exit the dialog box without accepting the settings, choose Cancel.

To accept the settings and begin configuring the properties for the LU range, choose OK.


Configuring Properties for LUA LUs

After assigning or viewing an LUA LU, in the New LUA LU Properties or LUA LU Properties dialog box, supply information according to the following list. If you are configuring a DFT LUA LU, see also Numbers Needed for DFT LUs.

Note  After making configuration changes, to put the changes into effect, restart the SNA server, as described in Restarting an SNA Server.

LU Number (for LUs on 802.2, SDLC, or X.25)

Type the LU Number.

If the LU is on a DFT connection , it does not use an LU number, but requires other identifying numbers instead. For information, see Numbers Needed for DFT LUs.

LU Name

Type the LU Name.

Connection

The connection for this LU is shown. The connection cannot be changed in this dialog box. To change the connection after configuring the LU, see Moving an LU.

Pool

If the LU has already been assigned to a pool, the pool name appears here.

Comment

Optionally, type a comment of up to 25 characters.

High Priority LU

Select this check box to give preference to this LU over low-priority LUs. See also Note on LU and LU Pool Settings.


Configuring Properties for an LUA LU Range

After assigning and numbering a range of LUA LUs, in the LUA LU Range Properties dialog box, supply the information in the following list.

Note  After making configuration changes, to put the changes into effect, restart the SNA server, as described in Restarting an SNA Server.

LU Numbers

The range of LU numbers that you entered appears here.

LU Names

The range of LU names that you entered appears here.

Connection

The connection for the LU range is shown. The connection cannot be changed in this dialog box. To change the connection after configuring the LUs, see Moving an LU.

Comment

Optionally, type a comment of up to 25 characters.

LUA High Priority LU

Select this check box to give preference to these LUs over low-priority LUs.


Using the SNA Server Admin Interface

This topic describes how to use the SNA Server Admin interface. For more detailed instructions, see the following:

Initiating Actions with Keys or Toolbar Buttons

Initiating Actions with Menu Commands

Initiating Actions by Dragging with the Mouse

Modifying the SNA Server Admin Display

The Windows in SNA Server Admin

The SNA Server Admin interface is structured around three windows that appear inside the main window. The windows can be shrunk to icons, and then restored to windows, as described in Using the Windows in SNA Server Admin. For basic information about working with windows, see your Windows NT documentation.

The actions you can perform in the three windows are as follows:

Icon	Window name	Use to
	Servers and Connections	Configure servers, connections, and logical units (LUs); start and stop servers and connections; reset LUs
	LU Pools	Configure LU pools
	Users and Groups	Assign items for users: LUs, LU pools, and properties
Initiating Tasks in SNA Server Admin

The SNA Server Admin interface allows you to initiate most tasks in several ways. You can do any of the following:

Click a button on the Toolbar

Use menu commands

Use keys such as ENTER, INS, and DEL

For some tasks, you can also use the mouse to drag and drop the appropriate item. For example, to assign an existing LU to a user, you can drag the LU listing from the Servers and Connections window and drop it on the user listing in the Users and Groups window.


Initiating Actions with Keys or Toolbar Buttons

You can initiate many actions in SNA Server Admin by selecting the item that the action relates to, and then pressing a key or clicking a button from the Toolbar:

For basic information about working with windows, see Using the SNA Server Admin Interface and your Windows documentation.

If the Toolbar is not displayed, from the Options menu, choose Preferences, then from the Preferences dialog box, select Enable Toolbar, and then choose OK.

The following table lists the tasks you can perform with a Toolbar button or with a key:

Task	Button or key
Adding a connection, LU, user, or other item
Viewing or modifying an existing connection, LU, user, or other item
Deleting a connection, LU, user, or other item
Copying properties from one connection, LU, or user to another
Moving a connection to a different server, or moving an LU to a different connection
Starting a server or connection
Stopping a server or connection, or resetting an LU
Reopening the last configuration saved
Saving the current configuration
The following topics give more detail about how to initiate actions with keys or Toolbar buttons. Choose the action you want to perform:

Adding

Copying Properties

Deleting

Saving and Reopening the Configuration

Starting, Stopping, and Resetting

Viewing or Modifying


Initiating Actions with Keys or Buttons: Adding

To initiate the adding actions listed in the following table, select an appropriate item, and then press INS or click  [image]. If the Toolbar is not displayed, from the Options menu, choose Preferences, then from the Preferences dialog box, select Enable Toolbar, and then choose OK.

Task	Action to perform
Adding a connection to a server
Adding a 3270, remote APPC, LUA, or downstream LU
Adding a local APPC LU
Adding a network user or group to the list used by SNA Server
Adding LUs to a user or group
Adding a new LU pool
Adding LUs to an existing pool
The following topics give details about other actions with keys or Toolbar buttons:

Copying Properties

Deleting

Saving and Reopening the Configuration

Starting, Stopping, and Resetting

Viewing or Modifying


To select an item

Click the item.

--or--

Press CTRL+TAB until the appropriate window is selected, press TAB until the appropriate part of the screen is selected, and then press UP ARROW and DOWN ARROW until the appropriate item is selected.


Initiating Actions with Keys or Buttons: Viewing or Modifying

To initiate the viewing or modifying actions listed in the following table, select the indicated item, and then press ENTER or click  [image]. If the Toolbar is not displayed, from the Options menu, choose Preferences, then from the Preferences dialog box, select Enable Toolbar, and then choose OK.

Task	Action to perform
Viewing or modifying a connection
Viewing or modifying an LU
Viewing or modifying the properties assigned to a user or group
Viewing or modifying the properties of an LU pool
The following topics give details about other actions with keys or Toolbar buttons:

Adding

Copying Properties

Deleting

Saving and Reopening the Configuration

Starting, Stopping, and Resetting


The following topic is basically a duplicate of the general topic on deletion.


Initiating Actions with Keys or Buttons: Deleting

To initiate the deleting actions listed in the following table, select the indicated item, and then press DEL or click  [image]. If the Toolbar is not displayed, from the Options menu, choose Preferences, then from the Preferences dialog box, select Enable Toolbar, and then choose OK.

Note  Before deleting a server or connection, you must stop it. See Managing SNA Server and Configuring Security.

Task	Action to perform
Deleting a server
Deleting a connection
Deleting an LU
Deleting a network user or group from the list used by SNA Server
Pulling an LU or LU pool from those available to a user or group
Pulling an LU from an existing pool
Deleting an LU pool
The following topics give details about other actions with keys or Toolbar buttons:

Adding

Copying Properties

Saving and Reopening the Configuration

Starting, Stopping, and Resetting

Viewing or Modifying


Using Keys or Buttons: Starting, Stopping, and Resetting

This topic explains how to the use keys or Toolbar buttons to start, stop, or reset services. For more information about starting, stopping, and resetting, see Managing SNA Server and Configuring Security.

If the Toolbar is not displayed, from the Options menu, choose Preferences, then from the Preferences dialog box, select Enable Toolbar, and then choose OK.

To start or stop an SNA server or connection, or reset an LU

1	In the Servers and Connections window, select the appropriate item.

2	Click the button or press the key shown in the following table:

Task	Button or key
Starting an SNA server (node) Starting a connection
Stopping an SNA server (node) Stopping a connection Resetting an LU
The following topics give details about other actions with keys or Toolbar buttons:

Adding

Copying Properties

Deleting

Saving and Reopening the Configuration

Viewing or Modifying


Using Toolbar Buttons: Saving and Reopening the Configuration

For information about how the primary SNA server and backup SNA servers work with configuration files, see Configuration Files on Primary and Backup SNA Servers.

If the Toolbar is not displayed, from the Options menu, choose Preferences, then from the Preferences dialog box, select Enable Toolbar, and then choose OK.

To save the current configuration, click  [image]. See Note on Saving the Configuration.

To reopen the last configuration saved, click  [image]. See Note on Reopening the Configuration.

You can carry out other actions on configuration files by using commands in the File menu. For information, see Initiating Actions with Menu Commands: Configuration Files and Working with Configuration Files.

The following topics give details about other actions with keys or Toolbar buttons:

Adding

Copying Properties

Deleting

Starting, Stopping, and Resetting

Viewing or Modifying


Using Keys: Copying Properties

To initiate the copying actions listed in the following table, select the indicated item, press F8, and then, in the resulting dialog box, select the item to copy properties to.

Task	Action to perform
Copying properties from one connection to another
Copying properties from one LU to another
Copying properties and LUs from one user or group to another
The following topics give details about other actions with keys or Toolbar buttons:

Adding

Deleting

Saving and Reopening the Configuration

Starting, Stopping, and Resetting

Viewing or Modifying


Initiating Actions with Menu Commands

You can initiate any action in SNA Server Admin by selecting an appropriate item and then choosing a menu command. For basic information about working with windows, see Using the SNA Server Admin Interface and your Windows user's manuals.

The fourth menu in SNA Server Admin changes as the current active window changes:

Active window	Corresponding menu title
Servers and Connections	Services
Users and Groups	Users
LU Pools	Pools
The Options menu and the File menu remain the same regardless of which window is active. The following topics describe the menus:

Servers and Connections Window: Services Menu

Users and Groups Window: Users Menu

LU Pools Window: Pools Menu

Any Window: File Menu

Any Window: Options Menu

Any Window: Security Menu

The following topics give more detail about menu commands that affect specific items:

Configuration Files

Connections

LUs

Users and Groups


Servers and Connections Window:
Services Menu

Start Services

Stop Service

New Connection

Assign LUs

Move

Reorder LUs

Copy Properties

Properties


Users and Groups Window:
Users Menu

New User

Assign LUs

Reorder LUs

Copy Properties

Properties


LU Pools Window: Pools Menu

Reset LUs

New Pool

Assign LUs

Move

Properties


Any Window: Options Menu

NetView

RTM Triggers

Logs

CPI-C

DISPLAY Verb

Server Broadcasts

Preferences


Any Window: Security Menu

Permissions

Auditing

Owner


Any Window: File Menu

Reopen Configuration

Save Configuration

Backup

Restore

Select Domain

Exit


To select a menu command

Click the menu title, then the menu command.

--or--

Press ALT, then the underlined letter in the menu title, and then the underlined letter in the menu command.


To choose a menu command

Click the menu title, then the menu command.

--or--

Press ALT, then the underlined letter in the menu title, and then the underlined letter in the menu command.


Initiating Actions with Menu Commands: Connections

To initiate most actions involving connections, use the Servers and Connections window and choose a command from the Services menu:

Task	Select	Menu and command
Adding a connection to a server	The server	Services: New Connection
Viewing or modifying an existing connection	The connection	Services: Properties
Moving an existing connection to a different server	The connection	Services: Move
Starting a connection	The connection	Services: Start Services
Stopping a connection	The connection	Services: Stop Service
Copying properties from one connection to another	The connection	Services: Copy Properties
To delete a connection, use the Servers and Connections window and choose a command from the Edit menu:

Task	Select	Menu and command
Deleting a connection	The connection	Edit: Delete
For more information about configuring a connection, see Configuring Servers and Connections.

The following topics give detail about menu commands that affect other items:

Configuration Files

LUs

Users and Groups


Initiating Actions with Menu Commands: LUs

To initiate most actions involving LUs, use the Servers and Connections window and choose a command from the Services menu:

Task	Select	Menu and command
Adding an LU to a connection	The connection	Services: Assign LUs
Viewing or modifying an existing LU	The LU	Services: Properties
Copying properties from one LU to another	The LU	Services: Copy Properties
Moving an LU from one connection to another	The LU	Services: Move
Reordering the number of an LU or LU pool among those on the selected downstream connection	The LU on the downstream connection	Services: Reorder LUs
Resetting an LU	The LU	Services: Reset LUs (command appears when an active LU is selected)
To delete an LU, use the Servers and Connections window and choose a command from the Edit menu:

Task	Select	Menu and command
Deleting an LU	The LU	Edit: Delete
To assign LUs to an LU pool, use the LU Pools window and choose a command from the Pools menu:

Task	Select	Menu and command
Assigning LUs to an LU pool	The LU pool	Pools: Assign LUs
To assign a 3270 LU or LU pool to a user or group, use the Users and Groups window and choose a command from the Users menu:

Task	Select	Menu and command
Assigning a 3270 LU or LU pool to a user or group	The user or group (Users and Groups window)	Users: Assign LUs
For more information about configuring LUs, see Configuring LUs.

The following topics give detail about menu commands that affect other items:

Configuration Files

Connections

Users and Groups


Initiating Actions with Menu Commands: Users and Groups

Before users can be recognized by SNA Server, they must have accounts on the local area network.

To initiate most actions involving users and groups, use the Users and Groups window and choose a command from the Users menu:

Task	Select	Menu and command
Adding a network user or group to the list used by SNA Server	Any line in the Users and Groups column	Users: New User
Assigning an LU or LU pool to a user or group	The user or group	Users: Assign LUs
Viewing or modifying settings for a user or group	The user or group	Users: Properties
Copying properties from one user or group to another	The user or group	Users: Copy Properties
Reordering the number of an LU among those for the selected user or group	The LU	Users: Reorder LUs
To delete a user or group, use the Users and Groups window and choose a command from the Edit menu:

Task	Select	Menu and command
Deleting a user or group	The user or group	Edit: Delete
For more information about working with users and groups, see Setting Up 3270 User and Group Access: Overview.

The following topics give detail about menu commands that affect other items:

Configuration Files

Connections

LUs


Initiating Actions with Menu Commands: Configuration Files

To initiate actions involving configuration files, choose a command from the File menu:

Command	Action
Reopen Configuration	Reopening the configuration as it was when last saved, abandoning changes made since then.
Save Configuration	Saving the current configuration (the displayed configuration).
Backup	Saving the current configuration as a backup file.
Restore	Restoring a configuration that was saved as a backup file.
Select Domain	Selecting the domain containing the SNA servers to be displayed in SNA Server Admin.
Exit	Exiting SNA Server Admin.
For more information, see Working with Configuration Files.

The following topics give detail about menu commands that affect other items:

Connections

LUs

Users and Groups


Initiating Actions by Dragging with the Mouse

You can work with some items on the SNA Server Admin screen by using the mouse to drag and drop them. For basic information about working with windows, see Using the SNA Server Admin Interface and your Windows documentation.

If configuration conflicts are created by the action of dragging and dropping an item, SNA Server ignores the action and displays a message box.

You can control whether SNA Server prompts for confirmation of mouse operations. To turn the confirmation prompt setting on or off, from the Options menu, choose Preferences, then from the Preferences dialog box, select or clear Confirm Mouse Operations. Then choose OK.

The following table gives details for dragging and dropping with the mouse:

Task	Window to start in: item to drag	Window to end in:  item to drop onto
Moving a connection from one server to another	Servers and Connections:  the connection	Servers and Connections:  the intended server
Moving an LU from one connection to another	Servers and Connections:  the LU	Servers and Connections:  the intended connection
Assigning an LU to a pool	Servers and Connections: the LU	LU Pools: the pool
Moving an LU assignment from one pool to another	LU Pools: the LU	LU Pools: the intended pool
Assigning an LU to a user	Servers and Connections: the LU	Users and Groups: the user
Copying an LU assignment from one user to another	Users and Groups: the LU	Users and Groups: the intended user


To drag and drop an item in SNA Server Admin

1	Click the item once to highlight it.

2	Point to the highlighted item with the mouse pointer.

3	Press and hold the left mouse button and move the mouse.

An icon representing the item moves on the screen. While the icon is in a place where releasing it has no effect, it changes to a slashed circle.

4	When the icon is in the desired position, release the mouse button.


Modifying the SNA Server Admin Display

The SNA Server Admin display is structured around three windows that appear inside the main window. The windows can be shrunk to icons, and then restored to windows, as described in Using the Windows in SNA Server Admin and your Windows NT documentation.

Options Menu

The following table shows display options that can be modified using the Preferences command on the Options menu. For detailed instructions, see Accessing the Preferences Dialog Box.

Action	Preferences  check box
Turning the display of the Toolbar on or off.	Enable Toolbar
Turning the display of the status bar on or off.	Enable Status Bar
Enabling or disabling the automatic display of  advanced settings in dialog boxes that contain an Advanced button.	Always Display Advanced Settings
Enabling or disabling the confirmation prompt following mouse operations.	Confirm Mouse Operations
Enabling or disabling the saving of window settings on exit from SNA Server Admin. Window settings are the settings made in this dialog box (Preferences), and the settings for window size and shape.	Save Window Settings on Exit
View Menu

You can carry out the following actions for the active window for SNA Server Admin by choosing commands from the View menu:

Control the type of items displayed in the active window. For more information, see the following:

Modifying the Display for the Servers and Connections Window

Modifying the Display for the Users and Groups Window

Modifying the Display for the LU Pools Window

Control the order in which LUs are listed (Servers and Connections window only). For more information, see Modifying the Display for the Servers and Connections Window.

Move the split line between halves of the window or between column headings in the window. For more information, see Moving the Split Line.

As the current active window changes in SNA Server Admin, the commands on the View menu change also. Each View menu includes one or two groups of mutually exclusive commands. For example, when the Servers and Connections window is active, you can choose one command from the group of All Services, Active Services, or Inactive Services. When a command in such a group is chosen, a check mark appears beside the command.


Using the Windows in SNA Server Admin

Some ways to work with windows and icons are as follows:

To shrink a window to an icon, double-click the downward-pointing arrow (the Minimize button) in the window's upper right corner, or press CTRL+F6 until the window is selected, and, from the Control menu, choose Minimize (ALT, HYPHEN, N).

To restore a window from an icon, double-click the icon, or, from the Window menu, choose the number of the window (ALT, W, number).

To arrange windows edge-by-edge, from the Window menu, choose Tile (ALT, W, T); to arrange windows in an overlapping pattern, from the Window menu, choose Cascade (ALT, W, C).


1	From the Options menu, choose Preferences.

2	In the Preferences dialog box, select or clear check boxes according to the table that follows.

3	Choose OK.


1	With the mouse pointer, point to the split line that you want to move.

The pointer changes to [image].

2	Press and hold the left mouse button and move the mouse.

The split line moves as the mouse is moved.

3	When the split line is in the intended position, release the mouse button.


Modifying the Display for the Servers and Connections Window

To modify the display of services or the sorting of LU lists, choose commands from the command groups shown in the following tables. You can choose only one command from each group at a time. When one of these commands is chosen, a check mark appears beside it.

View Menu Commands for the Servers and Connections Window:
Modifying the Display of Services

Command	Effect
All Services	Display all servers and connections, and all LUs for the selected connection.
Active Services	Display only active servers and connections, and the active LUs for the selected connection.
Inactive Services	Display inactive servers and connections, and the inactive LUs for the selected connection.
View Menu Commands for the Servers and Connections Window:
Modifying the Sorting of LU Lists

Command	Effect
Sort LUs by Name	Sort by name the list of LUs for the selected connection.
Sort LUs by Type	Sort by type the list of LUs for the selected connection.
Sort LUs by Number	Sort by number the list of LUs for the selected connection.


Modifying the Display for the Users and Groups Window

To modify the display of users, choose one of the commands shown in the following table. Only one of these commands can be chosen at a time. The command that is currently chosen has a check mark beside it on the menu.

View Menu Commands for the Users and Groups Window:
Modifying the Display of Users

Command	Effect
Configured Users	Display configured users and allow changes to user configurations.
Active Users	Display active users and the computer and LUs that the selected user is using.


Modifying the Display for the LU Pools Window

To modify the display of  pools,  choose one of the commands shown in the following table. Only one of these commands can be chosen at a time. The command that is currently chosen has a check mark beside it on the menu.

View Menu Commands for the LU Pools Window:
Modifying the Display of Pools

Command	Effect
All LU Pools	Display all pools
3270 Pools	Display 3270 pools
LUA Pools	Display LUA pools
Downstream Pools	Display downstream pools


Determining a Connection's Link Role

The following table shows the link role that SNA Server assigns:

Remote end	Assigned link role for connection
Host	Secondary
Peer (other than multidrop)	Negotiable
Peer, with local server as the    SDLC Multidrop Primary    (see Advanced SDLC Settings    and Configuring Multidrop Connections)	Primary
Downstream	Primary


Working with VTAM, NCP, and/or CICS

  Sample VTAM Parameters for a Token Ring Connection

  SNA Server, VTAM, and NCP Parameters for 802.2 Connections

  Sample VTAM Parameters for an SDLC Connection

  SNA Server, VTAM, and NCP Parameters for SDLC Connections

  Sample VTAM Parameters for an X.25 Connection

  SNA Server, VTAM, and NCP Parameters for X.25 Connections

  Sample VTAM Parameters for LU 6.2

  Sample CICS Configuration Screens for LU 6.2


Sample VTAM Parameters for a Token Ring Connection

The following is a sample of VTAM parameters that might be used for a token ring connection to an IBM 9370 host. The underlined values correspond to values specified in SNA Server Admin.

R01100   PORT CUADDR=100,MACADDR=400040004001,LANCON=(5,2),         X
              MAXDATA=2012,MAXSTN=52,SAPADDR=04

SERVER01 PU   ADDR=C1, IDBLK=05D, IDNUM=00001,                      X
              ANS=CONTINUE,MAXDATA=0265,MAXOUT=7,MAXPATH=7,         X
              PACING=0,VPACING=0,SSCPFM=USSSCS,                     X
              LANACK=(0,0),LANCON=(5,2),LANINACT=4.8,LANRESP=(5,2), X
              LANSDWDW=(7,1),LANSW=YES,MACADDR=400040001111,        X
              USSTAB=MSUSSTAB,DLOGMOD=D4C32792,                     X
              PUTYPE=2,DISCNT=(NO),ISTATUS=ACTIVE,SAPADDR=04

T0110002 LU   LOCADDR=002
T0110003 LU   LOCADDR=003
T0110004 LU   LOCADDR=004
T0110005 LU   LOCADDR=005
P0110006 LU   LOCADDR=006,DLOGMOD=LU33286S
T0110007 LU   LOCADDR=007
T0110008 LU   LOCADDR=008

The following table shows the SNA Server parameters and values that correspond to the sample VTAM parameters:

SNA Server parameter	Sample value	VTAM parameter
Remote Network Address	400040004001	MACADDR= parameter in the PORT definition
Local Node ID, first three digits (block number)	05D	IDBLK= parameter in the PU definition
Local Node ID, last five digits (node number)	00001	IDNUM= parameter in the PU definition
Max BTU Length	265	MAXDATA= parameter in the PU definition (set Max BTU Length less than or equal to MAXDATA)
Remote SAP Address	04	SAPADDR= parameter in the PU definition
LU Numbers	2 through 8	LOCADDR= parameter in the LU definitions


Sample VTAM Parameters Including CPNAME

The following is a sample of VTAM parameters that might be used for a token ring connection to an IBM 9370 host, when identification of the SNA server is based on Control Point Name (CPNAME). For this configuration, Format 3 XIDs must be exchanged.

Note that in the PU definition, IDBLK, IDNUM, MACADDR, and SAPADDR are not used. In order for this configuration to work, on the SNA Server, the Remote Node ID, Remote Network Name, and Remote Control Point Name should all be left blank. Additionally, the Local Node ID can be left at the default value (since it is not used).

In this sample, the underlined values correspond to values specified in SNA Server Admin.

R01100   PORT CUADDR=100,MACADDR=400040004001,LANCON=(5,2),         X
              MAXDATA=2012,MAXSTN=52,SAPADDR=04

SERVER01 PU   ADDR=C1,CPNAME=SERVER01,ANS=CONTINUE,                 X
              MAXDATA=0265,MAXOUT=7,MAXPATH=7,                      X
              PACING=0,VPACING=0,SSCPFM=USSSCS,                     X
              LANACK=(0,0),LANCON=(5,2),LANINACT=4.8,               X
              LANRESP=(5,2),LANSDWDW=(7,1),LANSW=YES,               X
              USSTAB=MSUSSTAB,DLOGMOD=D4C32792,                     X
              PUTYPE=2,DISCNT=(NO),ISTATUS=ACTIVE

T0110002 LU   LOCADDR=002
T0110003 LU   LOCADDR=003
T0110004 LU   LOCADDR=004
T0110005 LU   LOCADDR=005
P0110006 LU   LOCADDR=006,DLOGMOD=LU33286S
T0110007 LU   LOCADDR=007
T0110008 LU   LOCADDR=008

The following table shows the SNA Server parameters and values that correspond to the sample VTAM parameters.

Note  For this example, it is assumed that the local Network Name configured for the SNA server matches the NETID parameter in the VTAM Start command for the local SSCP (the VTAM system to which SNA Server is attached).

SNA Server parameter	Sample value	VTAM parameter
Remote Network Address	400040004001	MACADDR= parameter in the PORT definition
Local Control Point Name (for the SNA server)	SERVER01	CPNAME= parameter in the PU definition
Max BTU Length	265	MAXDATA= parameter in the PU definition (set Max BTU Length less than or equal to MAXDATA)
LU Numbers	2 through 8	LOCADDR= parameter in the LU definitions


SNA Server, VTAM, and NCP Parameters for 802.2 Connections

The following table shows how SNA Server parameters for 802.2 connections correspond to VTAM or NCP parameters. Asterisks (*) indicate required parameters. For more information about using SNA Server with NCP, see Chapter 5 of the Microsoft SNA Server Administration Guide.

Setting level	SNA parameter	VTAM or NCP parameter
Initial settings	Local Node ID,* first three digits (block number)	IDBLK= parameter in the  PU definition
Initial settings	Local Node ID,* last five digits (node number)	IDNUM= parameter in the PU definition
Initial settings	Network Name (Remote Node) Note: Network Name for local and remote nodes is generally the same	NETID parameter in the VTAM Start command for the remote SSCP (VTAM system)
Initial settings	Control Point Name (Remote Node)	SSCPNAME parameter in the VTAM Start command for the remote SSCP (VTAM system)
802.2 Basic	Remote Network Address* when connecting to a 3720, 3725, or 3745  front-end processor	MACADDR= parameter in the NCP Gen
802.2 Basic	Remote Network Address* when connecting to an IBM 9370 host	MACADDR= parameter in the PORT definition
802.2 Advanced	Remote SAP Address when connecting to an IBM 9370 host	SAPADDR= parameter  in the PU definition
802.2 Advanced	Max BTU Length	MAXDATA= parameter in the PU definition (set Max BTU Length less than or equal to MAXDATA)
* Required parameter in SNA Server.


Sample VTAM Parameters for an SDLC Connection

The following is a sample of VTAM parameters that might be used for an SDLC connection to a host. The underlined values correspond to values specified in SNA Server Admin.

SERVER02 PU    ADDR=C1,IDBLK=017,IDNUM=B8001,DISCNT=NO,               X

               VPACING=00,PACING=00,PUTYPE=2,MAXDATA=265,             X

               DLOGMOD=D4C32792,USSTAB=MSUSSTAB

T01B8002 LU    LOCADDR=002

T01B8003 LU    LOCADDR=003

T01B8004 LU    LOCADDR=004

T01B8005 LU    LOCADDR=005

P01B8006 LU    LOCADDR=006,DLOGMOD=LU33286S

The following table shows the SNA Server parameters and values that correspond to the sample VTAM parameters:

SNA Server parameter	Sample value	VTAM parameter
Local Poll Address	C1	ADDR= parameter in the PU definition
Local Node ID, first three digits (block number)	017	IDBLK= parameter in the PU definition
Local Node ID, last five digits (node number)	B8001	IDNUM= parameter in the PU definition
Max BTU Length	265	MAXDATA= parameter in the PU definition (set Max BTU Length less than or equal to MAXDATA)
The encoding scheme (NRZ or NRZI)	Not specified; defaults to NRZI=YES on host	The NRZI= setting in the LINE/GROUP definition
LU Numbers	2 through 6	LOCADDR= parameter in the LU definitions


SNA Server, VTAM, and NCP Parameters for SDLC Connections

The following table shows how SNA Server parameters for SDLC connections correspond to VTAM or NCP parameters. Asterisks (*) indicate required parameters. For more information about using SNA Server with NCP, see Chapter 5 of the Microsoft SNA Server Administration Guide.

Setting level	SNA parameter	VTAM or NCP parameter
Initial settings	Local Node ID,* first three digits (block number)	IDBLK= parameter in the  PU definition
Initial settings	Local Node ID,* last five digits (node number)	IDNUM= parameter in the PU definition
Initial settings	Network Name (Remote Node) Note: Network Name for local and remote nodes is generally the same	NETID parameter in the VTAM Start command for the remote SSCP (VTAM system)
Initial settings	Control Point Name (Remote Node)	SSCPNAME parameter in the VTAM Start command for the remote SSCP (VTAM system)
SDLC Advanced	Max BTU Length	MAXDATA= parameter in the PU definition (set Max BTU Length less than or equal to MAXDATA)
SDLC Advanced	Encoding (NRZ or NRZI)	NRZI= setting in the LINE/GROUP definition (defaults to YES on host)
SDLC Advanced	Local Poll Address	ADDR= parameter in the PU definition
* Required parameter in SNA Server.


Sample VTAM Parameters for an X.25 Connection

The following is a sample of VTAM parameters that might be used for an X.25 connection to a host. The underlined values correspond to values specified in SNA Server Admin.

PORTA00  PORT  CUADDR=(A00,A08),NETTYPE=1,CHARGACC=YES,CHARGE=NO,    X
               VCALLS=(,,001,006,,),DIALNO=31370023061,MAXOUT=7,     X
               NETLEVEL=80,PMOD=8,PLENGTH=256,PWINDOW=3,             X
               REPLYT0=3,RETRIES=7

SERVER03 PU    ADDR=C1,IDBLK=05D,IDNUM=00025,ANS=CONTINUE,           X
               MAXDATA=265,MAXOUT=7,MAXPATH=0,PACING=0,VPACING=0,    X
               SSCPFM=USSSCS,IRETRY=YES,USSTAB=MSUSSTAB,PUTYPE=2,    X
               DISCNT=YES,ISTATUS=ACTIVE

The following table shows the SNA Server parameters and values that correspond to the sample VTAM parameters:

SNA Server parameter	Sample value	VTAM parameter
Remote X.25 Address	31370023061	DIALNO= parameter in the PORT definition
Local Node ID, first three digits (block number)	05D	IDBLK= parameter in the PU definition
Local Node ID, last five digits (node number)	00025	IDNUM= parameter in the PU definition
Max BTU Length	265	MAXDATA= parameter in the PU definition (set Max BTU Length less than or equal to MAXDATA)


SNA Server, VTAM, and NCP Parameters for X.25 Connections

The following table shows how SNA Server parameters for X.25 connections correspond to VTAM or NCP parameters. Asterisks (*) indicate required parameters. For more information about using SNA Server with NCP, see Chapter 5 of the Microsoft SNA Server Administration Guide.

Setting level	SNA parameter	VTAM or NCP parameter
Initial settings	Local Node ID,* first three digits (block number)	IDBLK= parameter in the PU definition
Initial settings	Local Node ID,* last five digits (node number)	IDNUM= parameter in the PU definition
Initial settings	Network Name (Remote Node) Note: Network Name for local and remote nodes is generally the same	NETID parameter in the VTAM Start command for the remote SSCP (VTAM system)
Initial settings	Control Point Name (Remote Node)	SSCPNAME parameter in the VTAM Start command for the remote SSCP (VTAM system)
X.25 Basic	Remote X.25 Address*	DIALNO= parameter in the PORT definition
X.25 Advanced	Max BTU Length	MAXDATA= parameter in the PU definition (set Max BTU Length less than or equal to MAXDATA)
* Required parameter in SNA Server.


Sample VTAM Parameters for LU 6.2

The following is a sample of VTAM parameters that might be used for communication using independent LU 6.2. The underlined values correspond to values specified in SNA Server Admin. For more information about VTAM, see your IBM documentation.

SERVER1  PU    ADDR=09,                                X

               IDBLK=05D,                              X

               IDNUM=11111,                            X

               CPNAME=SNASERV,                         X

               ISTATUS=ACTIVE                          X

               DLOGMOD=D4C32782,                       X

               MODETAB=ISTINCLM,                       X

               MAXDATA=521,                            X

               MAXPATH=1,                              X

               PUTYPE=2,                               X

               SSCPFN=USSSCS,                          X

               MAXOUT=7,                               X

               PASSLIM=4,                              X

               PACING=0,                               X

               DISCNT=NO,                              X

               USSTAB=USSTAB

TRPATH    PATH DIALNO=2223331234567890,                X

               GRPNM=AAA01,                            X

               GID=2

LOCLU1    LU   LOCADDR=0,                              X

               ISTATUS=ACTIVE,DLOGMOD=APPCMODE,        X

               RESSCB=25,USSTAB=USSTAB,PACING=0,       X

               VPACING=0

Note that in the preceding example, the LOCADDR= value for LOCLU1 is 0. This is the correct value to use with independent LU 6.2 LUs.

The following table shows the SNA Server parameters and values that correspond to the preceding sample VTAM parameters:

SNA Server parameter	Sample value	VTAM parameter
Connection: Local Node ID, first three digits (block number)	05D	IDBLK= parameter in the PU definition
Connection: Local Node ID, last five digits (node number)	11111	IDNUM= parameter in the PU definition
Server: Control Point Name	SNASERV	CPNAME= parameter in the PU definition
Connection: Max BTU Length	521	MAXDATA= parameter in the PU definition (set Max BTU Length less than or equal to MAXDATA)
Local APPC LU: LU Name	LOCLU1	Name in LU definition
LU 6.2 Partner LUs: Mode	APPCMODE	DLOGMOD= parameter in the LU definition
The following list shows mode table entries for use with independent LU 6.2 LUs.

*********************************************************

*           LOGMODE TABLE ENTRY FOR RESOURCES           *

*          CAPABLE OF ACTING AS LU 6.2 DEVICES          *

*********************************************************

SNASVCMG MODEENT LOGMODE=SNASVCMG,FMPROF=X'13',         X

               TSPROF=X'07',PRIPROT=X'B0',              X

               SECPROT=X'B0',COMPROT=X'D0B1',           X

               RUSIZES=X'8585',ENCR=B'0000',            X

               PSERVIC=X'060200000000000000000300'

APPCMODE MODEENT LOGMODE=APPCMODE,                      X

               TYPE=0,                                  X

               FMPROF=X'13',                            X

               TSPROF=X'07',                            X

               PRIPROT=X'B0',                           X

               SECPROT=X'B0',                           X

               COMPROT=X'50B1',                         X

               PSNDPAC=X'03',                           X

               SRCVPAC=X'03',                           X

               RUSIZES=X'8585',                         X

               PSERVIC=X'060200000000000000002F00'

In the preceding list, the mode named APPCMODE is an example of a mode configured for use with LU 6.2. (Note that the mode named SNASVCMG is included in SNA Server, since it is required for parallel session support; it does not need to be configured in SNA Server Admin.)


Sample CICS Configuration Screens for LU 6.2

The following series of screens show how CICS could be configured for independent LU 6.2 through VTAM. In the first screen, the underlined values correspond to values specified in SNA Server Admin.

_________________________________________________________________

OVERTYPE TO MODIFY                    CICS RELEASE = 0330

 CEDA  ALter

  Sessions       : LOCLU1

  Group          : VER3AAAA

  DEscription  ==> VERSION 3 LU 6.2 SESSION ENTRY

 SESSION IDENTIFIERS

  Connection   ==> CON1

  SESSName     ==>

  NETnameq     ==>

  MOdename     ==> APPCMODE

 SESSION PROPERTIES

  Protocol     ==> Appc                Appc | Lu61

  MAximum      ==> 250 , 125           0-999

  RECEIVEPfx   ==>

  RECEIVECount ==>                     1-999

  SENDPfx      ==>

  SENDCount    ==>                     1-999

  SENDSize     ==> 00521               1-30720

  RECEIVESize  ==> 00521               1-30720

                                            APPLID=CICSLU

PF 1 HELP 2 COM 3 END   6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL

_________________________________________________________________

The following table shows the SNA Server parameters and values that correspond to the preceding sample CICS parameters:

SNA Server parameter	Sample value	CICS parameter
LU Name for Local  APPC LU	LOCLU1	Sessions
Mode name	APPCMODE	MOdename
Parallel Session Limit in the mode	250	MAximum
Partner Min Contention Winner Limit in the mode	125	MAximum
Max Receive RU Size in the mode	00521	SENDSize
Max Send RU Size in the mode	00521	RECEIVESize
LU Name for  Remote APPC LU	CICSLU	APPLID
In the sample CICS screen, the parameter called MAximum has two values, 250 and 125, separated by commas. The first value (250) is the parallel session limit. The second value (125) is the host minimum contention winner limit. On the SNA server, this corresponds to Partner Min Contention Winner Limit in the mode. In addition, since the host is the contention winner on 125 sessions (out of a total of 250), then SNA Server should be configured as the contention winner on the remaining 125 sessions. In this case, the SNA Server mode would have the following values:

Parallel Session Limit 250

Minimum Contention Winner Limit 125

Partner Min Contention Winner Limit 125

Automatic Activation Limit 0

The remaining screens in this section show more information about how CICS could be configured for independent LU 6.2 through VTAM.

_________________________________________________________________

OVERTYPE TO MODIFY                    CICS RELEASE = 0330

 CEDA  ALter

 SESSION PROPERTIES

  SESSPriority ==> 000                 0-255

  Transaction    :

 OPERATOR DEFAULTS

  OPERId         :

  OPERPriority   : 000                 0-255

  OPERRsl        : 0                              0-24,...

  OPERSecurity   : 1                              1-64,...

 PRESET SECURITY

  USERId       ==>

 OPERATIONAL PROPERTIES

  Autoconnect  ==> Yes                 No | Yes | All

  INservice      :                     No | Yes

  Buildchain   ==> Yes                 Yes | No

  USERArealen  ==> 000                 0-255

  IOarealen    ==> 00000 , 00000       0-32767

  RELreq       ==> No                  No | Yes

  DIscreq      ==> No                  No | Yes

  NEPclass     ==> 000                 0-255

 RECOVERY

  RECOVOption  ==> Sysdefault  Sysdefault | Clearconv

                               | Releasesess | Uncondrel

                               | None

  RECOVNotify  ==> None       None | Message | Transaction

                                            APPLID=CICSLU

PF 1 HELP 2 COM 3 END   6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL

_________________________________________________________________

In the following screen, the underlined value corresponds to the LU Name of the local APPC LU in SNA Server.

_________________________________________________________________

OVERTYPE TO MODIFY                    CICS RELEASE = 0330

 CEDA  ALter

  Connection     : CON1

  Group          : VER3AAAA

  DEscription  ==> VERSION 3  LU 6.2 DEFINITION

 CONNECTION IDENTIFIERS

  Netname      ==> LOCLU1

  INDsys       ==>

 REMOTE ATTRIBUTES

  REMOTESystem ==>

  REMOTEName   ==>

 CONNECTION PROPERTIES

  ACcessmethod ==> Vtam                Vtam | IRc

                                       |INdirect | Xm

  Protocol     ==> Appc                Appc | Lu61

  SInglesess   ==> No                  No | Yes

  DAtastream   ==> User                User | 3270 | SCs

                                       | STrfield | Lms

  RECordformat ==> U                   U | Vb

 OPERATIONAL PROPERTIES

  AUtoconnect  ==> Yes                 No | Yes | All

  INService    ==> Yes                 Yes | No

 SECURITY

  SEcurityname ==>

  ATtachsec    ==> Verify              Local | Identify

                                       | Verify | Persistent

                                       | Mixidpe

  BINDPassword ==>                     PASSWORD SPECIFIED

  BINDSecurity ==> No                  No | Yes

                                            APPLID=CICSLU

PF 1 HELP 2 COM 3 END   6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL

_________________________________________________________________


[]JAN: ADAPTER & CONN CAPACITIES IS DUPLICATED IN TWO CONTEXTS: THE CONTEXT FOR A SECONDARY WINDOW FROM ANOTHER WINDOW, AND THE CONTEXT FOR A REGULAR WINDOW FROM JUMP LISTS AND THE SEARCH LIST.


Adapter, Connection, and Server Capacities for SNA Server

The SNA Server software has the following upper limits for use:

As many as 10,000 sessions per server.

250 total connections per server.

A maximum of 2000 clients per server.

One downstream connection is equivalent to one client, when figuring the total number of clients per server.

The following table tells the upper limits for connections and sessions.

Connection type	Maximum connections per adapter	Maximum  sessions* per connection
802.2	250**	254
SDLC	1	254
X.25	250**	254
DFT	1	5
Channel	250**	254
Twinax	1	20
*	LU sessions of the following types: 3270, LUA, and dependent APPC LU-LU sessions. For independent APPC LUs, the number of sessions is limited by the capacity of the SNA server (node), which is 10,000 sessions.

**	Total connections per server (node) are limited to 250.

Note that although you can use as many as four DFT adapters in one computer, you must use one link service for all the DFT adapters in that computer.

See also Note About Adapters for X.25.


Adapter, Connection, and Server Capacities for SNA Server

The SNA Server software has the following upper limits for use:

As many as 10,000 sessions per server.

250 total connections per server.

A maximum of 2000 clients per server.

One downstream connection is equivalent to one client, when figuring the total number of clients per server.

The following table tells the upper limits for connections and sessions.

Connection type	Maximum connections per adapter	Maximum  sessions* per connection
802.2	250**	254
SDLC	1	254
X.25	250**	254
DFT	1	5
Channel	250**	254
Twinax	1	20
*	LU sessions of the following types: 3270, LUA, and dependent APPC LU-LU sessions. For independent APPC LUs, the number of sessions is limited by the capacity of the SNA server (node), which is 10,000 sessions.

**	Total connections per server (node) are limited to 250.

Note that although you can use as many as four DFT adapters in one computer, you must use one link service for all the DFT adapters in that computer.

See also Note About Adapters for X.25.


AS/400 Configuration

The following table provides details about configuring for the AS/400 environment. In addition, for an X.25 connection using PVC, specify the PVC Alias.

For additional details about configuring for the AS/400 environment, see Chapter 7 of the Microsoft SNA Server Administration Guide.

If you will be supporting clients that use the PC Support router, see Note About PC Support.

SNA Server element	SNA Server parameter name	Instructions
Server	Network Name  (Local Node)	Be sure to specify. Generally corresponds to RMTNETID on AS/400. (APPN often used.)
Server	Control Point Name  (Local Node)	Corresponds to RMTCPNAME on the AS/400.
Connection	Remote End	Select Peer System.
Connection	Activation	If SWTDSC on AS/400 is *YES, select On Demand. If SWTDSC is *NO, select On Server Startup.
Connection	Local Node ID	Required parameter. Corresponds to EXCHID on AS/400.
Connection	Control Point Name (Remote Node)	Specify control point name (CP name) of AS/400 system.
Connection	Network Name (Remote Node)	Corresponds to RMTNETID on AS/400. (APPN often used.)
Connection	802.2: Remote Network Address SDLC: Poll Address X.25: Remote X.25 Address	Corresponds to ADPTADR in the Line Description. Corresponds to STNADR in the Line Description. Specify the address of the AS/400.
Connection	Max BTU Length	Corresponds to MAXFRAME on the AS/400.
Remote  APPC LU	LU Name	Specify control point name of AS/400 system for remote LU Name.
Mode	Mode Name	Use QPCSUPP.
User or group listing	Default Local LU Alias	Recommended for use with AS/400.
User or group listing	Default Remote  LU Alias	Recommended; affects which AS/400 a user will use by default.


Configuring Hot Backup for LUs for 5250

To configure hot backup for 5250 users, configure multiple servers and pairs of LUs that can all handle sessions to the intended AS/400s. (For better protection against failures, use multiple servers, not multiple connections on the same server.) To configure for hot backup, use the following steps:

1	Configure one connection to the AS/400 on each SNA server available for support of 5250 users.

2	Create a local LU on each server, specifying the following:

For LU 6.2 Type, select Independent.

For LU Alias, specify the same string on each server.

For LU Name, specify a unique string on each server. This is required to avoid device name conflicts across servers.

3	Create a remote LU on each server, and give all the remote LUs the same LU name and alias (which must match the control point name of the AS/400).

Be sure that the Supports Parallel Sessions box is selected for these LUs.

4	Using the Partners button, view or create LU-LU pairs on each server:

If you are using automatic partnering, you can view the pairings of local LUs, remote LUs, and modes that have automatically been created. If the intended pair does not use the QPCSUPP mode, delete that pair and create one that does.

QPCSUPP is the only correct mode to use with the AS/400.

If you are not using automatic partnering, pair the local LU with the remote LU, and assign the QPCSUPP mode.

5	Make the local and remote LUs available to users and/or groups, by doing one of the following:

With SNA Server: In the Users and Groups window, for each group or user that uses 5250, select the appropriate default local APPC LU and the appropriate default remote APPC LU.

To keep this process simple, use or create a group that includes all 5250 users, and assign the appropriate default LUs to that group.

With the 5250 emulator: Have users specify the local and remote LUs when configuring a session on the emulator.

When configured in this way, SNA Server will choose a server to connect with the AS/400, based on availability and current load.


hot backup

A configuration where one resource can automatically fill in if another fails. In such a configuration, resources are interchangeable; when a particular resource (such as an SNA server) is not working, another similar resource can automatically support the needed sessions.


Starting and Stopping Servers and Connections

Restarting (that is, stopping and starting) SNA servers is important because it is needed for putting many types of configuration changes into effect. For information about other reasons for starting and stopping connections, see Managing SNA Server and Configuring Security: Overview.

To start an SNA server (node) or connection

1	In the Servers and Connections window, select the SNA server or connection you want to start.

2	On the Toolbar, click  [image].

See also Note About "On Demand" and "Incoming" Connections.

To stop an SNA server (node) or connection

Note  When possible, have all users log off from the remote host or peer before stopping services, to avoid leaving the host or peer in an unresolved, nonfunctional state.

1	In the Servers and Connections window, select the SNA server or connection you want to stop.

2	On the Toolbar, click  [image].

3	When prompted for confirmation, choose Yes.

See also Note About "On Demand" and "Incoming" Connections.


Restarting an SNA Server

When possible, have all users log off from the remote host or peer system(s) before stopping and restarting the SNA server, to avoid leaving the host or peer in an unresolved, nonfunctional state.

To restart an SNA server

1	In the Servers and Connections window, select the SNA server that you want to restart.

2	On the Toolbar, click  [image].

3	When prompted for confirmation, choose Yes.

4	On the Toolbar, click  [image].


Viewing the Status of Servers, Connections, and LUs

When making decisions about starting, stopping, resetting, or modifying services, it may be helpful to gather status information.

  To view the status of an SNA server

Server status possibilities

  To view the status of a connection

Connection status possibilities

Note about "On Demand" and "Incoming" connections

  To view the status of an LU other than an APPC LU

Status possibilities for LUs other than APPC LUs

  To view the status of an APPC LU-LU pair

Status possibilities for APPC LUs

  To view the 3270 LUs being used by an active user


1	In the Servers and Connections window, select the server.

2	On the Toolbar, click  [image].

In the Server Properties dialog box, view the server status.


In the Servers and Connections window, view the connection status displayed to the right of the connection name.


1	In the Servers and Connections window, select the connection used by the LU.

2	Find the LU listed to the right of the connection, and view the status.


1	In the Servers and Connections window, select the local APPC LU.

2	On the Toolbar, click  [image].

The APPC LU Properties dialog box appears.

3	Choose Status.

The APPC LU Status dialog box appears.

4	To view more information about an APPC LU-LU session, select the LU-LU pair you are interested in, then choose Zoom.


1	In the Users and Groups window, from the View menu, choose Active Users.

2	Select the active user.

3	View the LUs listed in the LU or LU Pool column.


The possibilities for server status are:

Active

Inactive

Pending

Stopping

Active [Out of Date]

This status indicates that the SNA server needs to be restarted to bring internal parameters up-to-date with the latest configuration changes.

Error

This status indicates that an unexpected condition has made the SNA server (node) inaccessible to SNA Server Admin.

Also displayed are the version number and the number of each of the following: 3270 sessions, APPC sessions, and LUA sessions. If the server is active, the number of licensed users and licensed sessions is also shown.


The possibilities for connection status are:

Active

Inactive

Pending

Stopping

On Demand (for On Demand connections only)

Incoming (for Incoming connections only)


The possibilities for the status of LUs other than APPC LUs are:

Inactive

In Session

SSCP

This status indicates that the LU is in use but is not yet bound to a specific host application.

Available

This status indicates that the LU is recognized by the host as an available LU.


The status for an APPC LU will either be Inactive, or will show the number of active sessions.


FOLLOWING NOTE HAS TWO FORMS--INIT CAP AND NOT


Note About "On Demand" and "Incoming" Connections

On Demand connections have three levels of activation: Inactive (not available to be started), On Demand (available to be started when needed), and Active (started by the administrator and therefore to remain active until stopped). The Start button on the Toolbar shifts such a connection to the next higher activation, and the Stop button shifts the connection to Inactive.

Incoming connections have three levels of activation: Inactive (not available to receive incoming calls), Incoming (available to receive incoming calls), and Active (in use). The Start button on the Toolbar shifts such a connection from Inactive to Incoming, and the Stop button shifts the connection from any state to Inactive.


Note about "On Demand" and "Incoming" connections

On Demand connections have three levels of activation: Inactive (not available to be started), On Demand (available to be started when needed), and Active (started by the administrator and therefore to remain active until stopped). The Start button on the Toolbar shifts such a connection to the next higher activation, and the Stop button shifts the connection to Inactive.

Incoming connections have three levels of activation: Inactive (not available to receive incoming calls), Incoming (available to receive incoming calls), and Active (in use). The Start button on the Toolbar shifts such a connection from Inactive to Incoming, and the Stop button shifts the connection from any state to Inactive.


Resetting LUs

Resetting an LU stops it and allows it to restart when needed. Resetting an LU can help restore function when problems have occurred. With APPC LUs, you can also deactivate individual LU-LU sessions. To maximize user access to remote resources when one or more LUs is not functioning, you can create LU pools; see Using LU Pools to Maximize Access: Overview.

To reset an LU from the Servers and Connections window

1	In the Servers and Connections window, select the connection that has the LU you want to stop.

2	Select the LU.

You can only reset an LU that has a status of Active, SSCP, or In Session.

3	On the Toolbar, click  [image].

4	When prompted for confirmation, choose Yes.

To reset an LU in an LU pool

1	In the LU Pools window, select the pool containing the LU.

2	Select the LU.

You can only reset an LU that has a status of Active, SSCP, or In Session.

3	On the Toolbar, click  [image].

4	When prompted for confirmation, choose Yes.

To deactivate an APPC LU-LU session

1	In the Servers and Connections window, select the local APPC LU for which you want to deactivate an LU-LU session.

2	On the Toolbar, click  [image].

The APPC LU Properties dialog box appears.

3	Choose Status.

The APPC LU Status dialog box appears.

4	Select the LU-LU pair you are interested in, then choose Zoom.

A second APPC LU Status dialog box appears.

5	Select the LU-LU session that you want to deactivate.

6	Choose Deactivate.

7	Choose OK.

8	Choose Close or Cancel until the dialog boxes have all been closed.


Adding, Viewing, or Modifying Users or Groups

Before users can be added to the list used by SNA Server, they must have accounts on the local area network or the local server.

For a complete list of the steps for configuring for 3270, see Configuring for 3270 Terminal Emulation.

  To add a user or group to the list used by SNA Server

  To access a user or group for viewing or modifying

To configure default APPC LUs for the user or group, see Configuring Properties for a User or Group.


To add a user or group to the list used by SNA Server

1	In the Users and Groups window, select any line.

2	From the View menu, choose Configured Users.

3	On the Toolbar, click  [image].

4	In the Insert dialog box, select New User.

5	Choose OK.

6	In the List Names From box, select the domain from which to list users who have network accounts.

7	From Names, which lists the users and groups who have accounts, select the one you want to add.

8	Choose Add.

9	Choose OK.

The window title changes to Users and Groups - [Out of Date], to indicate that the configuration needs to be saved to bring it up to date.

10	On the Toolbar, click  [image].


1	In the Users and Groups window, from the View menu, choose Configured Users.

2	Select the user or group.

3	On the Toolbar, click  [image].


Giving Users Access to 3270 LUs and LU Pools

To give users access to host systems for which you have configured connections and 3270 LUs, assign the LUs and/or LU pools to users or groups.

When you assign LUs to user and group accounts with overlapping memberships, some of these assignments override others. See Precedence of Accounts in Determining LU Access.

You can also change the order in which LUs appear in lists seen by the user. For information, see Reordering LUs in User Lists.

For information about LUs and LU pools, see Configuring LUs and Using LU Pools to Maximize Access: Overview.

To assign one or more 3270 LUs or LU pools to a user or group

1	In the Users and Groups window, from the View menu, choose Configured Users.

2	Select the user or group to which you want to assign one or more LUs or LU pools.

3	On the Toolbar, click  [image].

4	In the Insert dialog box, select Add LUs to User.

5	Choose OK.

6	In the Assign User LU/Pool Sessions dialog box, select one or more LUs or LU pools.

To select multiple items in sequence, click the first item you want, hold down SHIFT, and click the last item you want.

To select multiple items out of sequence, hold down CTRL as you click the items that you want.

Important  If a user or group needs access to multiple LU sessions, assign one LU or LU pool for each session needed. You can assign a pool multiple times to the same user or group.

7	Choose OK.

The window title changes to Users and Groups - [Out of Date], to indicate that the configuration needs to be saved to bring it up to date.

8	On the Toolbar, click  [image].


Reordering LUs in User Lists

You can control the order of 3270 LUs or LU pools in lists seen by users.

To change the order of LUs or LU pools in lists seen by a user or group

1	In the Users and Groups window, from the View menu, choose Configured Users.

2	Select the user or group for which you want to control the listed order of LUs.

3	From the LUs or LU pools listed opposite the selected user or group, select one or more that you want to move up in the list.

To select multiple items in sequence, click the first item you want, hold down SHIFT, and click the last item you want.

To select multiple items out of sequence, hold down CTRL as you click the items that you want.

4	From the Users menu, choose Reorder LUs.

5	In Before Session Number, type the number that you want the first selected LU or pool to have in lists displayed for the user.

6	Choose OK.

The selected LUs are moved up in the list, and other LUs are moved down. The window title changes to Users and Groups - [Out of Date], to indicate that the configuration needs to be saved to bring it up to date.

7	On the Toolbar, click  [image].


Configuring Properties for a User or Group

After accessing a user or group, in the User Properties or Group Properties dialog box, find the items appropriate to your configuration, and supply information as follows:

Comment

Optionally, type a comment of up to 25 characters.

Local LU Alias

If this user will be using APPC programs (TPs, 5250 emulators, or APPC applications), you can choose a default local APPC LU to be used when the user starts such programs. For more information, see LUs for APPC: Overview.

Avoid assigning a default local APPC LU to the group "Everyone." Instead, to make a local APPC LU available to any user, when configuring the local LU, select the check box labeled Member of Default Outgoing Local APPC LU Pool.  For information about configuring a local LU, see the topic in Topic List for APPC LUs.

Remote LU Alias

If this user will be using APPC programs (TPs, 5250 emulators, or APPC applications), you can choose a default remote APPC LU to be used when the user starts such programs. For more information, see LUs for APPC: Overview.

To accept the settings, choose OK; to exit the dialog box without accepting the settings, choose Cancel.

When you assign default APPC LUs to user and group accounts with overlapping memberships, some of these assignments override others. See Precedence of Accounts in Determining Default LUs.


Assigning Default APPC LUs to Users or Groups

For a user or group who will be using TPs, 5250 emulators, and/or APPC applications, you can assign a default local APPC LU and a default remote APPC LU. These default LUs are accessed when the user or group member starts an APPC program (a TP, 5250 emulator, or APPC application) and the program does not specify LU aliases.

There are two steps to take before assigning default APPC LUs to a user or group. First, make sure the user or group has an account on the SNA server or on the local area network; accounts are explained in your Windows NT documentation. Second, add the user or group to the list used by SNA Server.

  To add a user or group to the list used by SNA Server

  To assign default APPC LUs to a user or group

For information about default LUs in AS/400 environments, see Note About AS/400s. For information about default LUs and system efficiency, see Note About System Efficiency. If you will be supporting clients that use the PC Support router, see Note About PC Support.

When you assign default APPC LUs to user and group accounts with overlapping memberships, some of these assignments override others. See Precedence of Accounts in Determining Default LUs.

Avoid assigning a default local APPC LU to the group "Everyone." Instead, to make a local APPC LU available to any user, when configuring the local LU, select the check box labeled Member of Default Outgoing Local APPC LU Pool. For information about configuring a local LU, see the topic in Topic List for APPC LUs.


Note About AS/400s

In AS/400 environments, the ability to assign default APPC LUs to users or groups is especially useful, because it gives the administrator centralized control over these LU assignments. In such environments, for each user or group, assign both a default local APPC LU and a default remote APPC LU. Assigning a default local APPC LU for each user fulfills the normal AS/400 procedure of assigning local LUs on a per-user basis. Assigning a default remote APPC LU is equivalent to assigning a default AS/400 for the user to connect to, since the remote LU designates the AS/400. By making these assignments, the administrator can centrally control the default AS/400 that a 5250 emulation user connects to.


Note About System Efficiency

For greater system efficiency, you can assign the same set of default LUs to more than one user (instead of a different set of LUs for each user).


To assign default APPC LUs to a user or group

1	In the Users and Groups window, from the View menu, choose Configured Users.

2	Select the user or group.

3	On the Toolbar, click  [image].

The User Properties or Group Properties dialog box appears.

4	In the Local LU Alias box, select a default local APPC LU.

Avoid assigning a default local APPC LU to the group "Everyone." Instead, to make a local APPC LU available to any user, when configuring the local LU, select the check box labeled Member of Default Outgoing Local APPC LU Pool.

5	In the Remote LU Alias box, select a default remote APPC LU.

6	Choose OK.

The window title changes to Users and Groups - [Out of Date], to indicate that the configuration needs to be saved to bring it up to date.

7	On the Toolbar, click  [image].


Copying Properties and LUs Between Users and/or Groups

The action of copying between users and/or groups copies both the properties and the LUs.

To copy properties and LUs between users and/or groups

1	In the Users and Groups window, from the View menu, choose Configured Users.

2	Select the user or group from which you want to copy properties and LUs.

2	From the Users menu, choose Copy Properties.

3	In the Copy Properties dialog box, select the user or group to which you want to copy properties and LUs.

4	Choose OK.

The window title changes to Users and Groups - [Out of Date], to indicate that the configuration needs to be saved to bring it up to date.

5	On the Toolbar, click  [image].


The following topic is basically a duplicate of the keyboard/button topic on deletion.


Deleting SNA Resources

To delete the SNA Server resources in the following table, select the indicated item, and then press DEL or click  [image]. When prompted to confirm the deletion, choose Yes.

Note  Before deleting a server or connection, you must stop it. See Managing SNA Server and Configuring Security.

Tasks Using the DEL Key or

Resource to delete	Action to take
A server
A connection
An LU
An SNA user or group
The assignment of an LU or LU pool to a user or group
The assignment of an LU to a pool
An LU pool


Working with Configuration Files

You can carry out the following actions with configuration files:

Action	Topic
Save the current configuration.	Saving and Reopening the Configuration  Configuration Files on Primary and Backup SNA Servers
Reopen the last configuration that was saved, abandoning any changes that have been made but not saved.	Saving and Reopening the Configuration  Configuration Files on Primary and Backup SNA Servers
Back up the current configuration. (See Note.)	Backing Up and Restoring the Configuration
Restore a configuration from a backup configuration file.	Backing Up and Restoring the Configuration
Create an offline configuration file	Offline Configuration


Note on Backup Configuration Files

Using the File menu Backup command to create a backup of the current configuration is a different action from working with a backup SNA server. When you use the File menu Backup command, the current configuration is copied to a backup configuration file, and the default extension offered by the software is .SNA. When you work with a backup SNA server, you are working with a server from which the configuration can be loaded if the primary SNA server is not available. The filename of the configuration file that is loaded on a backup SNA server is the same as the filename on the primary SNA server, COM.CFG.


Saving and Reopening the Configuration

When you save the configuration, the settings are recorded in the configuration file on the primary SNA server, and loaded again the next time you start SNA Server Admin. For information about how the primary and backup SNA servers work, see Configuration Files on Primary and Backup SNA Servers.

To save the current configuration

On the Toolbar, click  [image].

If a pop-up message appears, stating that there is a problem on the primary SNA server and the current configuration could not be saved on it, back up the configuration (as described in To back up the current configuration), then investigate the status of the primary SNA server.

To reopen the last configuration that was saved

From the File menu, choose Reopen Configuration.


Backing Up and Restoring the Configuration

You can save a backup copy of the configuration file, using any name for the file, and restore the backup copy when needed. Note that saving a backup copy in this way is different from carrying out actions involving a backup SNA server. The use of backup SNA servers is described in Configuration Files on Primary and Backup SNA Servers.

  To back up the current configuration

  To restore a configuration from a backup file


To back up the current configuration

1	From the File menu, choose Backup.

The Save Configuration As dialog box appears.

2	If you need to change drives, in the Drives box, select the desired drive.

3	In the Directories box, select the directory in which you want to back up the current configuration.

4	In the File Name box, type the filename to save the configuration file as, or select a filename from the list.

The default filename extension for backup configuration files is .SNA.

5	Choose OK.


To restore a configuration from a backup file

1	From the File menu, choose Restore.

The Restore Configuration From dialog box appears.

2	If you need to change drives, in the Drives box, select the desired drive.

3	In the Directories box, select the directory in which the backup file is located.

4	In the File Name box, type the filename of the backup file, or select a filename from the list.

The default filename extension for backup configuration files is .SNA.

5	Choose OK.


Offline Configuration

You can create or modify a configuration file for another SNA site. A file created at one site and used at another is called an offline configuration file. Offline configuration files and backup configuration files use the same filename extension, .SNA.

You can work on an offline configuration by using either of two interfaces: the offline version of SNA Server Admin, or the SNA Server command-line interface. To learn how to use the command-line interface, see Appendix E of the Microsoft SNA Server Administration Guide. This Help topic describes important differences between offline and on-site configuration, and tells how to use the offline version of SNA Server Admin.

Differences Between Offline Configuration and On-Site Configuration

The fact that a configuration file can be created offline, at a different site, allows more flexibility in using SNA Server Admin. It also means that the administrator must ensure that certain information is entered correctly when creating the offline configuration. For on-site configuration, this information is supplied in the setup process:

The server name(s).

The link service name(s) and properties (adapter type, line type).

The user and group names.

With the regular version of SNA Server Admin, once these items have been specified in the Setup program (or, for users, specified on a domain), you do not need to keep track of them or type them into SNA Server Admin. In contrast, the offline version dialog boxes allow these items to be typed in or modified. If any of these items is typed incorrectly, the offline configuration file will work incorrectly at the remote site. See also Note About User Security IDs.

Note  To ensure correctness in server names, link service names, adapter properties, and user names, start your offline configuration with a backup configuration file created at the remote site. This backup configuration file should be created after the intended SNA servers have already been installed and the intended users already added to the SNA Server configuration.

The following topics provide more information about how to use the offline version of SNA Server Admin:

  Guidelines for Offline Configuration

  Using the Offline Version of SNA Server Admin


Note About User Security IDs

When users are added offline to an SNA Server configuration, the security ID (SID) that is contained in each user account (on the domain) is not added to the user listing (in SNA Server). To make sure that all SIDs are added, after transferring the configuration file to its intended location, use the snacfg #configpath user /validate command to process the file. This command attempts to fill in SIDs that are missing from user or group listings in the SNA Server configuration. For more information, see Appendix E in the Microsoft SNA Server Administration Guide.


GUIDELINES FOR OFFLINE CONFIGURATION HAS ONE COPY THAT IS STARTED FROM A SECONDARY WINDOW AND ONE COPY THAT IS STARTED FROM THE SEARCH LIST.  KEEP BOTH COPIES UPDATED.


Guidelines for Offline Configuration

The following guidelines give the sequence of steps for creating and using an offline configuration file. See also Note About Interfaces for Offline Configuration.

Step	Additional information
1 If possible, obtain a backup configuration file from the remote site, with the intended SNA servers already installed and the intended users already added to the configuration.	Note About Information Contained in a Backup Configuration File Creating a Backup Configuration File to Use  with the Offline Version
2 Start the offline version of SNA Server Admin with a backup configuration file (if possible, the configuration file created in step 1), and modify the file.	Starting the Offline Version with a Backup  Configuration File Using the Offline Version  of SNA Server Admin
3 Send the offline configuration file to the site where it will be used.
4 Copy the configuration file onto an SNA server where the file will be used.
5 At the command prompt, run  snacfg #configpath user /validate  where configpath is the path of the configuration file.	Note About User  Security IDs
6 Start SNA Server Admin; focus on the domain where the configuration file will be used.	Changing the Domain of Focus
7 From the File menu, choose Restore, and then select the drive, directory, and filename of the offline configuration file.
8 Choose OK. The configuration is now available to be used in SNA Server Admin.


GUIDELINES FOR OFFLINE CONFIGURATION HAS ONE COPY THAT IS STARTED FROM A SECONDARY WINDOW AND ONE COPY THAT IS STARTED FROM THE SEARCH LIST.  KEEP BOTH COPIES UPDATED.


Guidelines for Offline Configuration

The following guidelines give the sequence of steps for creating and using an offline configuration file. See also Note About Interfaces for Offline Configuration.

Step	Additional information
1 If possible, obtain a backup configuration file from the remote site, with the intended SNA servers already installed and the intended users already added to the configuration.	Note About Information Contained in a Backup Configuration File Creating a Backup Configuration File to Use  with the Offline Version
2 Start the offline version of SNA Server Admin with a backup configuration file (if possible, the configuration file created in step 1), and modify the file.	Starting the Offline Version with a Backup  Configuration File Using the Offline Version  of SNA Server Admin
3 Send the offline configuration file to the site where it will be used.
4 Copy the configuration file onto an SNA server where the file will be used.
5 At the command prompt, run  snacfg #configpath user /validate  where configpath is the path of the configuration file.	Note About User  Security IDs
6 Start SNA Server Admin; focus on the domain where the configuration file will be used.	Changing the Domain of Focus
7 From the File menu, choose Restore, and then select the drive, directory, and filename of the offline configuration file.
8 Choose OK. The configuration is now available to be used in SNA Server Admin.


Note About Interfaces for Offline Configuration

These guidelines assume that you will use the offline version of SNA Server Admin to create or modify the offline configuration file. Alternatively, when modifying an offline configuration file, you can use the SNA Server command-line interface. For information about the command-line interface, see Appendix E in the Microsoft SNA Server Administration Guide.


Note About Information Contained in a Backup Configuration File

The important information in the backup configuration file is the server information (which includes the link services and adapter types specified in Setup) and the user information. Other information, such as connection and LU information, can readily be specified offline.


Creating a Backup Configuration File to Use with the Offline Version

You will need a backup configuration file in order to use the offline version of SNA Server Admin.

To create a backup configuration file

1	Start the regular version of SNA Server Admin.

The active configuration is displayed.

2	From the File menu, choose Backup.

3	In the Save Configuration As dialog box, specify the drive, directory, and filename for the backup configuration file. For the filename extension, use .SNA (the default extension for backup configuration files).

4	Choose OK.


Starting the Offline Version with a Backup Configuration File

With a backup configuration file available, you can start the offline version of SNA Server Admin.

To start the offline version of SNA Server Admin

1	Switch to a command prompt.

2	At the command prompt, type

snaadmin filename.sna

For filename, substitute the filename of the backup configuration file.

The offline version of SNA Server Admin starts.

3	Make changes to the configuration.

4	Save the configuration file:

To save the configuration file with the same filename, from the File menu, choose Save.

To save the configuration file with a different filename, from the File menu, choose Save As, specify a directory and filename, and choose OK.


Using the Offline Version of SNA Server Admin

The offline version of SNA Server Admin looks much like the regular version. For most configuration tasks, you can use the instructions for the regular version.

One key difference between the versions is that the offline version allows you to enter server names, link service names, adapter properties, and user names. You must enter these names correctly to ensure that the offline configuration will work correctly. See Important Note About Offline Configuration.

Specifically, the offline version of SNA Server Admin differs from the regular version in the following ways:

Servers can be added, by using the New Server command from the Services menu.

See Adding a Server to an Offline Configuration.

Adapters and link service properties can be specified.

See Specifying Adapter Properties in an Offline Configuration.

Services cannot be started; they can only be configured. Menu commands applying to starting, stopping, and resetting are unavailable. The Toolbar buttons for starting and stopping are unavailable.

Services cannot have any status except Inactive or Not Configured, since they cannot be started. The Status button in the APPC LU Properties dialog box is unavailable.

Domains cannot be selected; they can only be specified in the applicable dialog boxes. On the File menu, the Select Domain command is unavailable.

User names and domains can be specified in the User Properties dialog box. For important information about user names and security IDs, see Note About User Security IDs.

The only File menu commands for saving a file are Save and Save As.

Configuration files can be created, or opened for viewing, but cannot be loaded as active configurations.


Important Note About Offline Configuration

When you specify server names, link service names, adapter properties, and user names in the offline version of SNA Server, you must match the actual names and properties at the site where the offline configuration will be used. Otherwise, the offline configuration will not work properly.

To ensure correctness in these names, start your offline configuration with a backup configuration file created at the remote site. This backup configuration file should be created after the intended SNA servers have already been installed and the intended users already added to the SNA Server configuration.


Specifying Adapter Properties in an Offline Configuration

1	Start the offline version of SNA Server Admin.

2	In the Servers and Connections window, select the server for which you want to specify adapter properties.

3	On the Toolbar, click  [image].

The Server Properties dialog box appears.

3	In the Server Properties dialog box, choose the Adapters button.

4	Configure adapter properties as described in the Microsoft SNA Server Installation Guide.

5	Choose OK.


Configuring for NetView

NetView sends alerts back and forth between a host system and PCs.

To specify the connection through which NetView data should be sent

1	From the Options menu, choose NetView.

2	In the Send NetView Management Data to Connection box, choose a connection.

This can be any host connection except a DFT connection.

3	Choose OK.

For information about extending NetView functionality, see SNA Server NetView Extensions: NVAlert and NVRunCmd.


SNA Server NetView Extensions: NVAlert and NVRunCmd

The NetView reporting system sends alerts and other information back and forth between a host (mainframe) and computers that connect to the host. NetView functionality can be extended with the Windows NT NVAlert and NVRunCmd services. With NVAlert, events on the Windows NT system can be sent to NetView as generic alerts. With NVRunCmd, commands can be forwarded from a host-system NetView console so that they run on an SNA server.

By itself, NetView can forward SNA Server alerts to the host system. With NVAlert, the following two categories of alerts can also be forwarded:

Alerts generated by the Windows NT operating system

Alerts generated by Windows NT-based applications

The alerts can be forwarded to the host-system NetView console display or to a host-system log file. For more information about NVAlert, see The NVAlert Service, Modifying NVALERT.INI, and Example of NVALERT.INI Section.

The NVRunCmd service makes it possible for commands typed at a host-system NetView console to be carried out on an SNA server, with command results being sent back to the host console. For information about NVRunCmd, see The NVRunCmd Service, How NVRunCmd Runs, Functionality Available with NVRunCmd, and Command Syntax for NVRunCmd.

Related Topics

For information about the logging of system events under SNA Server, and about NetView options and functionality, see the following:

  Using Event Logs

  Configuring for NetView


The NVAlert Service

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. This means that not only SNA Server events, but also system events such as a disk becoming full, or an application failing to find a file, can cause an alert to be sent to the host.

The NVAlert service is installed by the SNA Server Setup program. 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.

The NVAlert service runs as a background process waiting for an event to be recorded in an event log, and compares each logged event to a list in the NVALERT.INI file. When an event matches one on the list, NVAlert forwards an alert (as specified in NVALERT.INI) to the host system. If there is a problem with sending the alert, NVAlert goes into a preset pattern of time-outs and retries. No additional alerts can be sent until a given alert has been successfully sent to the host.

The NVAlert service creates alerts with the standard syntax, structure, and meaning used by NetView. For more information, see your IBM NetView documentation.

To control the NVAlert service, modify the NVALERT.INI file to specify the Windows NT-based alerts that you want forwarded to the host system. For more information, see Modifying NVALERT.INI and Example of NVALERT.INI Section.


Modifying NVALERT.INI

To add alerts that will be sent by NVAlert, add sections to the NVALERT.INI file, found in the SYSTEM subdirectory of the SNA Server root directory. One way to do this is to copy and paste existing sections of the file, then modify the sections as needed.

In each section added to NVALERT.INI, some of the lines are required, and some are optional, as described in the text that follows. For information about standard code points and values used by NetView, see your IBM NetView documentation.

For an example, see Example of NVALERT.INI Section.

Required Lines for Alerts in NVALERT.INI

For each alert, add a section to NVALERT.INI, beginning with the following heading. For the heading, include the square brackets [ ] as shown:

[source.type.eventid]

To determine the appropriate values for source, type, and eventid, view the intended alert in the Windows NT Event Viewer, and supply values as described in the following list. For information about the Event Viewer, see your Windows NT documentation and Viewing Event Logs.

For source, substitute the name that appears beneath the Source heading in the Windows NT Event Viewer.

For type, find the Type listing in the Windows NT Event Viewer, and substitute one of the following values:

Type as listed in the Windows NT Event Viewer	Value to substitute
Success	0
Information	1
Warning	2
Error	3
Success Audit	4
Failure Audit	5
For eventid, substitute the decimal number that appears beneath the EventID heading in the Windows NT Event Viewer.

Choose alerts that will not exceed the Max BTU Length of the connection over which the alerts will flow. Alerts exceeding this size cannot be handled by the host.

Beneath each bracketed heading, type lines with the following syntax:

AlertType = xx
AlertDescription = xxxx
ProbableCauses = xxxx[,...]

In these lines, each letter x represents a hexadecimal digit; the digits specify NetView code points. For information about the appropriate values to provide, see your IBM NetView documentation. The special characters [,...] mean that the pattern immediately before the square brackets [ ] can be repeated, with commas separating the repetitions; do not type the brackets.

Optional Lines for Alerts in NVALERT.INI

You can also add the following optional lines to the entry for each alert:

UserCauses = xxxx[,...]
UserDetData = 00,xx,string[;...]
UserRecAct = xxxx[,...]
UserRecActDetData = 00,xx,string[;...]

FailureCauses = xxxx[,...]
FailureDetData = 00,xx,string[;...]
FailureRecAct = xxxx[,...]
FailureRecActDetData = 00,xx,string[;...]

InstallCauses = xxxx[,...]
InstallDetData = 00,xx,string[;...]
InstallRecAct = xxxx[,...]
InstallRecActDetData = 00,xx,string[;...]

In the preceding lines, each letter x represents a hexadecimal digit; the digits specify NetView code points. For information about the appropriate values to provide, see your IBM NetView documentation. The special characters [,...] and [;...] mean that the pattern before the square brackets [ ] can be repeated, with commas or semicolons, respectively, separating the repetitions; do not type the brackets.

In the names, the abbreviation RecAct stands for recommended action, and DetData stands for detailed data. For information about the detailed data lines, see Providing Detailed Data Information.


   Providing Detailed Data Information

This topic describes the following optional lines that can be included in NVALERT.INI:

UserDetData = 00,xx,string[;...]
UserRecActDetData = 00,xx,string[;...]
FailureDetData = 00,xx,string[;...]
FailureRecActDetData = 00,xx,string[;...]
InstallDetData = 00,xx,string[;...]
InstallRecActDetData = 00,xx,string[;...]

These lines allow you to include blocks of detailed data in the alert. Separate the items within the detailed data with commas, and separate the blocks of data with semicolons (;).

For the xx variable, replace xx with a Data ID code point, as described on page 9.161 of the IBM SNA: Formats manual (IBM document GA27-3136-12) or other NetView documentation.

For string, provide a text string. In the string, you can use the following variables:

Variable	Event log item that will replace variable
%M	Module name.
%C	Computer name.
%I	Event ID.
%Sn	String number n in the event log; the strings are numbered starting at zero.
You can use the following variable for string only if you do not use any other variables:

Variable	Event log item that will replace variable
%Dxxxx,yyyy	Raw hexadecimal data of length yyyy, starting at buffer offset xxxx. Both xxxx and yyyy are hexadecimal values.


Example of NVALERT.INI Section

The following is an example of a Windows NT-based alert that can be forwarded to a host system via the NVAlert and NetView services. The alert warns that a hard disk is nearly full. The NVALERT.INI section would contain the following lines and would convey the following information:

Lines in NVALERT.INI  section	Meaning
[Srv.2.2013]	Source Srv, type 2 (warning),  EventID 2013
AlertType = 11	Impending problem
AlertDescription = 5002	Resource nearing capacity
ProbableCauses =  5001	Media DASD device
UserCauses = 0102,F0A0	Insufficient storage media space available
UserDetData = 00,95,%C	Problem located on the indicated file server name (supplied via NetView value 95); event logged on indicated computer name (supplied via %C)


The NVRunCmd Service

With the NVRunCmd service, commands typed at a host-system NetView console can be carried out on an SNA server, with command results being sent back to the host. The NVRunCmd service uses the NetView reporting system for transferring information between the host system and the SNA server.

Command results that are sent back to the host via NVRunCmd can include only character or number output, since the results are to be displayed at a host-system NetView console. Graphical output is not sent back to the console by the NVRunCmd service. For example, a host-system operator could use NVRunCmd to run the dir command, and receive a character-based display of the current directory. However, if a host-system operator used NVRunCmd to start a graphical application, no command output would be sent back to the host-system NetView console.

In addition, NVRunCmd does not handle back-and-forth interactions, such as confirmation prompts generated at the SNA server in response to a command. If a command forwarded by NVRunCmd requires confirmation before being carried out, the command process will not be completed, and will eventually be timed out.

The NVRunCmd service is installed by the SNA Server Setup program.

By default, the NVRunCmd 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."

The following topics provide more detail about the NVRunCmd service:

  How NVRunCmd Runs

  Functionality Available with NVRunCmd

  Command Syntax for NVRunCmd


Command Syntax for NVRunCmd

The syntax to use for a command to be typed at the host NetView console and processed by NVRunCmd is as follows. Case is ignored, so the command can be typed in uppercase, lowercase, or a combination.

runcmd sp=servicepoint, appl=NVRunCmd  cmd commandname parameters

Supply the following values:

For servicepoint, substitute the VTAM PU name of the SNA server on which commandname should be run. Note that on the SNA server, this value is configured as the Control Point Name for the server.

For commandname, substitute the command to be run. This should be a command that can be processed by Windows NT and that does not return graphical output, since only character or number output can be received by the NetView console.

For parameters, substitute any parameters needed for running the command on the SNA server.

At the SNA server named by servicepoint, NVRunCmd receives the information in commandname parameters and passes it to the Windows NT system.


How NVRunCmd Runs

The NVRunCmd service runs as a background process on the SNA server, waiting for a command to be sent from a NetView console. When such a command is received, NVRunCmd determines if the command is one that it can process. If it can, NVRunCmd initiates processing of the command. Then NVRunCmd sends the output, or a message saying that the command failed, back to the requesting NetView console.

NVRunCmd makes only one attempt to send the output back to the NetView console. Any problem with sending probably means that the link or some other part of the communications has failed.

The NVRunCmd service runs by default in the local system's security context. As a result of this, some commands may generate responses different from those generated by a user logged on at the same Windows NT-based system. Examples of such commands are net use and chdir typed without options. When run using NVRunCmd, these commands generate a display relative to the context for NVRunCmd, not the context for a logged-on user.

For better system security, use the Windows NT Control Panel to access the Services dialog box and configure Startup options for the NVRunCmd service. Associate the NVRunCmd service with a user account that has the privilege level that you want for NVRunCmd. For more information about the Control Panel, see your Windows documentation.

NVRunCmd can process only one command at a time. If a command is received while a previous one is processing, the command is rejected by SNA Server.


Functionality Available with NVRunCmd

As configured by the SNA Server Setup program, NVRunCmd can process any command entered at a host-system console, within the following limitations:

Case is ignored; lowercase is converted to uppercase.

The command must be one that can be processed on a Windows NT system.

Any output other than character or number output to STDOUT and STDERR will not be sent to the NetView console.

Confirmation prompts will not be sent to the NetView console. If a command requires confirmation before it can be processed, it will not be completed.

The pipe symbol (|) cannot be used to combine commands. For example, the following command string cannot be processed by NVRunCmd:

dir | more

The maximum amount of information that can be returned to the NetView console is 64 kilobytes. Any additional information returned by the command will be lost.


JAN, "Viewing Event Logs" appears in TWO PLACES--IN THE FOLLOWING TOPIC AND IN A POPUP BY ITSELF.


Using Event Logs

You can use information from Windows NT event logs as you test a configuration or diagnose problems. (For information about the security log, which contains a different set of events, see the Microsoft SNA Server Administration Guide.)

If you seek product support, the support technician may request copies of the Windows NT event log files, which are stored in WindowsRoot\SYSTEM32\CONFIG, and have a filename extension of .EVT. Otherwise, view event logs by using the Windows NT Event Viewer, as described at the end of this topic.

To specify event types and servers for event logging

1	From the Options menu, choose Logs.

The Error/Audit Logging and Popups dialog box appears.

2	In the Centralized Event Log Server box, type the name of the server on which event logs for this SNA Server installation should be stored, or select a server from the list.

3	Under Default Audit Log Level, select a level:

Detailed problem analysis: To record all events that can be recorded, select this option.

General information messages: To record general activity but not all events, select this option.

Significant system events: To record only major events, select this option.

Audit logging disabled: To turn off audit logging, select this option.

4	In the box labeled Route All Server Popup Messages to, type the name of a server to which pop-up error messages for this SNA Server installation should be routed, or select a server from the list. See Note on Pop-Up Error Messages.

5	To accept the settings, choose OK; to exit the dialog box without accepting the settings, choose Cancel.

To view SNA Server event logs using the Windows NT Event Viewer

1	Start the Event Viewer. For information, see your Windows NT documentation.

2	From the Log menu in the Event Viewer, choose Application.

Under the Source heading, SNA events are listed with names starting with "SNA."

3	To view more detail about an event, double-click the event listing.


Configuring RTM Settings

RTM makes data available about the length of time it takes a host to respond during 3270 sessions. RTM is supported only by certain emulators. You should configure RTM settings only if the emulators in your installation support RTM. You can specify the times at which RTM should send data, and also the trigger that will cause RTM to register that the host has responded.

Note  If the host RTM settings are different, they can override the SNA Server settings.

To configure 3270 RTM settings

1	From the Options menu, choose RTM Triggers.

2	In the 3270 Response Time Monitor (RTM) dialog box, supply information as follows:

RTM Data Sent at

Select one or both of the following:

Counter Overflow:  To cause RTM data to be sent to the host when the number of host responses in a given time period overflows the size of the available counter, select this box.

End of Session:  To cause RTM data to be sent to the host at the end of each LU-to-LU session, select this box.

RTM Timers Run Until

Select the point at which RTM will register that a host has responded; this is when RTM stops the timers. (The timers are started when the local system sends data.)

First Data Reaches Screen:  To stop timing when data reaches the local screen, select this option.

Host Unlocks Keyboard:  To stop timing when the host unlocks the local keyboard, select this option.

Host Lets User Send:  To stop timing when the host lets the local computer send more data, select this option.

RTM Thresholds

Specify the cutoff times, in tenths of a second, at which RTM saves its count of host responses and then restarts the count. For example, you could specify 5, 10, 20, and 50, to save the count of host responses during the intervals from 0.0 to 0.5 seconds, from 0.5 to 1.0 seconds, from 1.0 to 2.0 seconds, and from 2.0 to 5.0 seconds.

3	To exit the dialog box without accepting the settings, choose Cancel. To accept the settings, choose OK.


THERE ARE TWO COPIES OF "PHONE NUMBER STORAGE AND MODEM TYPES": ONE THAT'S A SECONDARY WINDOW FOR ACCESS FROM "DIAL DATA" DESCRIPTION, ONE FOR ACCESSS FROM CONTENTS SCREEN ETC.  KEEP BOTH COPIES UPDATED!


Phone Number Storage and Modem Types

SNA Server can store a phone number and then send the number (in ASCII) to a modem, which dials the number. This requires that the modem be attached to an SDLC adapter with a built-in serial (COM) port (for example, the SDLC adapters from Microgate).

There are several connection parameters that must be set to work with your modem: Dial Data, the duplex setting (half-duplex or full-duplex), and the encoding scheme. To see all the settings, in the SDLC Setup dialog box, choose the Advanced button.

Changing the SNA Server Dialing Method

To change the SNA Server dialing method for a modem, use the SNA Server Setup program to modify the link service; then restart SNA Server Admin and, from the File menu, choose Save Configuration. For information about Setup, see the Setup online help or the Microsoft SNA Server Installation Guide.

Modem Requirements for Accepting a Phone Number from SNA Server

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.

SNA Server Actions When Sending a Phone Number

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.


THERE ARE TWO COPIES OF "PHONE NUMBER STORAGE AND MODEM TYPES": ONE THAT'S A SECONDARY WINDOW FOR ACCESS FROM "DIAL DATA" DESCRIPTION, ONE FOR ACCESSS FROM CONTENTS SCREEN ETC.  KEEP BOTH COPIES UPDATED!


Phone Number Storage and Modem Types

SNA Server can store a phone number and then send the number (in ASCII) to a modem, which dials the number. This requires that the modem be attached to an SDLC adapter with a built-in serial (COM) port (for example, the SDLC adapters from Microgate).

There are several connection parameters that must be set to work with your modem: Dial Data, the duplex setting (half-duplex or full-duplex), and the encoding scheme. To see all the settings, in the SDLC Setup dialog box, choose the Advanced button.

Changing the SNA Server Dialing Method

To change the SNA Server dialing method for a modem, use the SNA Server Setup program to modify the link service; then restart SNA Server Admin and, from the File menu, choose Save Configuration. For information about Setup, see the Setup online help or the Microsoft SNA Server Installation Guide.

Modem Requirements for Accepting a Phone Number from SNA Server

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.

SNA Server Actions When Sending a Phone Number

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.


Collecting Traces and Other Detailed System Information

If you are working to improve performance or solve a difficulty in your SNA installation, the types of information in the following list may be useful. If you seek product support, the support technician may work with you to collect some or all of the listed types of information.

Trace files, created when SNA tracing is turned on. On an SNA server or Windows NT-based client, tracing is turned on with the SNA Server Trace Options (snatrace) utility. On other clients, tracing is turned on with special commands or with lines in an initialization file.

Windows NT event logs.

The COM.CFG file (configuration file).

Dump files, which may be created by SNA Server when a system trap (exception error) occurs.

Datascope or sniffer traces of protocol exchanges.

The following table tells how to locate files containing diagnostic information:

File type	Location	Filename or  filename pattern
Trace files created by the snatrace utility	SNAroot\TRACES	*.TRC
Log files	WindowsRoot\SYSTEM32\CONFIG	*.EVT
Configuration file	SNAroot\SYSTEM\CONFIG	COM.CFG
Dr. Watson file	WindowsRoot	DRWTSN32.LOG
Dump files	SNAroot\TRACES	SNADUMP.LOG
For information about event logs, see Using Event Logs. For information about configuration files, see Working with Configuration Files.

More Information About Tracing

This Help file provides introductory information about tracing, including information about starting tracing on an SNA server or Windows NT-based client. For detailed information about tracing, see the Microsoft SNA Server Administration Guide. For detailed information about using the snatrace utility, see also the Help available from the utility.

The following topics provide introductory information about tracing and about starting the snatrace utility:

  Working with Trace Files

  Starting the SNA Server Trace Options (snatrace) Utility


Working with Trace Files

Trace files record activity between or within components of SNA Server. Trace files provide detailed information about the exact sequence of events occurring within an SNA server, or between an SNA server and another system on the network. For the SNA server, trace files are created in the TRACES subdirectory of the SNA Server root directory, with the filename extension .TRC.

If you seek product support, the support technician may request trace files, and then guide you through the process of selecting tracing options.

Note  When gathering information about system difficulties, it is generally best to start with event log information. Event log information is generally more straightforward to interpret than tracing information. Use tracing information if event logs do not provide needed detail. For instructions, see Using Event Logs.

On an SNA server or Windows NT-based client, tracing is turned on with the SNA Server Trace Options (snatrace) utility. On other clients, tracing is turned on with special commands or with lines in an initialization file. For information about the snatrace utility, see Starting the SNA Server Trace Options (snatrace) Utility. For background information about tracing, see Collecting Traces and Other Detailed System Information.


Starting the SNA Server Trace Options (snatrace) Utility

The SNA Server Trace Options (snatrace) utility is a graphical tool that allows you to enable or disable tracing options on an SNA server or Windows NT-based client. For general background information about tracing, see Collecting Traces and Other Detailed System Information. For detailed information about tracing, see the Microsoft SNA Server Administration Guide.

To start the snatrace utility locally or remotely on an SNA server

1	Start SNA Server Admin.

2	In the Servers and Connections window, select the server that you want traces for.

3	On the Toolbar, click  [image].

4	In the Server Properties dialog box, choose Addons.

5	In the SNA Server Additions dialog box, from the list of available additions, select SNA Server Trace Options.

6	Choose the Select button.

The SNA Server Trace Options dialog box appears.

To start the snatrace utility on a Windows NT-based client

1	On the Windows NT-based client, switch to a command prompt.

2	At the command prompt, type

snatrace

The SNA Server Trace Options dialog box appears.

For information about selecting trace options, see the Help for the SNA Server Trace Options (snatrace) utility, or the Microsoft SNA Server Administration Guide.


Performance Monitor Options for SNA Server

The Performance Monitor, a graphical tool included in Windows NT, allows you to measure the performance of your computer or other computers on the network. The following table shows the SNA Server counters that you can measure with the Performance Monitor, as long as one or more SNA servers are started. For more information about using the Performance Monitor, see your Windows NT documentation.

SNA Server  object available  for monitoring	Counters available
SNA Connections	Data Bytes Received/Sec
	Data Bytes Transmitted/Sec
	Throughput Bytes/Sec
SNA Logical Unit Sessions	Data Bytes Received/Sec
	Data Bytes Transmitted/Sec
	Throughput Bytes/Sec
SNA Adapter adaptername	Adapter Failures
	Connection Failures
	Data Bytes Received/Sec
	Data Bytes Transmitted/Sec
	Frames Received/Sec
	Frames Transmitted/Sec
	Successful Connects
	Throughput Bytes/Sec
	Throughput Frames/Sec
With SNA Server, a frame is an information structure recognized by one of the various protocols related to SNA. Frames contain multiple bytes of data. Throughput includes both incoming and outgoing information, and is a good indicator of how heavily the SNA server is loaded.


Diagram of SNA Server Architecture

The following diagram shows the architecture for SNA Server:

For background information about SNA and SNA Server, see the documentation listed in Finding Further Information.


Using LU Pools to Maximize Access: Overview

To maximize access to the resources available via 3270, LUA, or downstream LUs, you can group the LUs into pools. A user, LUA application, or downstream system using the pool can get LU access as long as one of the pooled LUs is available.

Note that the pooling of LUs is handled differently for APPC or for 5250; for information, see the Microsoft SNA Server Administration Guide, or the Help topics about configuring local APPC LUs, assigning default APPC LUs to users, and configuring hot backup for 5250.

LU pools can maximize access in several ways:

By allowing groups of intermittent users to use resources efficiently. For example, ten 3270 users who only need intermittent access may find that a pool of five 3270 LUs is adequate for their needs.

By providing hot backup. An LU pool can contain LUs from more than one server or adapter, so that even if one server or adapter stops working, users or applications using the pool can still get LU access. Users and applications may not even be aware that a server and/or adapter is not working, as long as one of the LUs in the pool is functioning.

By helping balance the load between servers. If an LU pool contains LUs from more than one server, the load is shared according to the number of users accessing each server.

Steps for Setting Up an LU Pool

To set up a fully functional LU pool, take the following steps:

Step	Additional information
1 Configure LUs for the pool.	Configuring LUs
2 Create the pool.	Creating 3270 LU Pools Configuring Properties for a 3270 LU Pool Creating LUA Pools Creating Downstream Pools
3 Assign the intended LUs to the pool. In order to provide LU access, a pool must contain LUs. An empty pool provides no LU access.	Assigning LUs to an LU Pool
4 For 3270 LU pools, assign the pool to a user. For downstream pools, associate the pool with a downstream connection	Giving Users Access to 3270 LUs and LU Pools Associating Downstream LUs with a Downstream Connection
5 Put the configuration changes into effect by restarting the affected  SNA server(s).	Restarting an SNA Server


Using LU Pools to Maximize Access

  Overview

  Creating 3270 LU Pools

  Configuring Properties for a 3270 LU Pool

  Creating LUA Pools

  Creating Downstream Pools

  Assigning LUs to an LU Pool

  Removing LUs from an LU Pool

  Moving an LU to a Different Pool


Creating 3270 LU Pools

For information about the uses of LU pools, see Using LU Pools to Maximize Access: Overview.

To initiate adding a 3270 LU pool

1	In the LU Pools window, select any item.

2	On the Toolbar, click  [image].

3	In the Insert dialog box, select New Pool.

4	Choose OK.

The New Pool dialog box appears. Under Pool Type, 3270 will already be selected.

To configure properties for the pool, see Configuring Properties for a 3270 LU Pool. To assign LUs to the pool (which is a necessary step), see Assigning LUs to an LU Pool.

To access an existing 3270 LU pool for viewing or modifying

1	In the LU Pools window, select the pool.

If the pool you want does not appear in the list, from the View menu, choose All LU Pools, and then select the pool.

2	On the Toolbar, click  [image].

For information about properties for the pool, see Configuring Properties for a 3270 LU Pool. To assign LUs to the pool (which is a necessary step), see Assigning LUs to an LU Pool.


Configuring Properties for a 3270 LU Pool

After adding or accessing an LU pool, in the New Pool dialog box or 3270 LU Pool Properties dialog box, find the items appropriate to your configuration, and supply information as follows:

Pool Name

Type a Pool Name.

Comment

Optionally, type a comment of up to 25 characters.

Display Model

Select a Display Model. If there is a conflict between the Display Model setting for the pool and the Display Model setting for an LU in the pool, a message box appears. You can allow the individual LU setting to be changed, or exclude the LU from the pool.

Model can be overridden

Select this check box to allow users to override the display model type by using a 3270 terminal emulation program. If there is a conflict between the model override setting for the pool and the model override setting for an LU in the pool, a message box appears. You can allow the individual LU setting to be changed, or exclude the LU from the pool.

To exit the dialog box without accepting the configuration settings, choose Cancel. To accept the settings, choose OK. After accepting the settings, add LUs to the pool; only a pool that contains LUs provides LU access. See Assigning LUs to an LU Pool.


Assigning LUs to an LU Pool

After defining properties for an LU pool, assign LUs to the pool. The pool provides LU access only to the LUs assigned to it.

For 3270 LU pools, after assigning LUs to the pool, assign the pool to a user, as described in Giving Users Access to 3270 LUs and LU Pools. For downstream LU pools, after assigning LUs to the pool, assign the pool to a downstream connection, as described in Associating Downstream LUs with a Downstream Connection.

To assign LUs to an LU pool

1	In the LU Pools window, select the pool.

If the pool you want does not appear in the list, from the View menu, choose All LU Pools, and then select the pool.

2	On the Toolbar, click  [image].

3	In the Insert dialog box, select Add LUs to Pool.

4	Choose OK.

5	In the Assign Pool LUs dialog box, under Available LUs, select one or more LUs.

To select multiple items in sequence, click the first item you want, hold down SHIFT, and click the last item you want.

To select multiple items out of sequence, hold down CTRL as you click the items that you want.

6	Choose OK.

If there is a conflict between the properties for the pool and the properties for an LU in the pool, a message box appears. You can allow the individual LU properties to be changed, or exclude the LU from the pool.

7	To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


To select an item in a list box

Keyboard: press UP ARROW and DOWN ARROW until the item is selected.

Mouse: Click the item.


Removing LUs from an LU Pool

You may need to remove LUs from an LU pool. Note that an empty pool provides no LU access.

To remove an LU from an LU pool:

1	In the LU Pools window, select the pool.

If the pool you want does not appear in the list, from the View menu, choose All LU Pools, and then select the pool.

2	In the right-hand pane of the LU Pools window, select the LU you want to remove.

3	On the Toolbar, click  [image].

4	When prompted for confirmation, choose Yes.

5	To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


Moving an LU to a Different Pool

You can move LUs from one pool to another. Note that an empty pool provides no LU access.

To move an LU from one LU pool to another

1	In the LU Pools window, select the pool that the LU is currently assigned to.

If the pool you want does not appear in the list, from the View menu, choose All LU Pools, and then select the pool.

2	In the right-hand pane of the LU Pools window, click the LU you want to move.

The LU is highlighted to show that it is selected.

3	Point to the LU with the mouse pointer.

4	Press and hold the left mouse button and move the mouse.

An icon representing the LU moves on the screen. The icon changes to a slashed circle while in a place where releasing the LU has no meaning.

5	When the icon is on the intended pool, release the mouse button.

If there is a conflict between the properties for the pool and the properties for an LU in the pool, a message box appears. You can allow the individual LU properties to be changed, or exclude the LU from the pool.

6	To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


Creating LUA Pools

For information about the uses of LU pools, see Using LU Pools to Maximize Access: Overview.

  To initiate adding an LUA LU pool

  To access an existing LUA LU pool for viewing or modifying

After adding or accessing an LU pool, in the New Pool or LUA LU Pool Properties dialog box, find the items appropriate to your configuration, and supply information as follows:

Pool Name

Type a Pool Name.

Comment

Optionally, type a comment of up to 25 characters.

LUA High Priority LU Pool

Select this check box to give preference to communication with LUs in this pool over low-priority communication.

If there is a conflict between the priority for the pool and the priority for an LU in the pool, a message box appears. You can allow the individual LU priority to be changed, or exclude the LU from the pool.

To exit the dialog box without accepting the configuration settings, choose Cancel. To accept the settings, choose OK. After accepting the settings, add LUs to the pool; only a pool that contains LUs provides LU access. See Assigning LUs to an LU Pool.


1	In the LU Pools window, select any item.

2	On the Toolbar, click  [image].

3	In the Insert dialog box, select New Pool.

4	Choose OK.

The New Pool dialog box appears.

5	Under Pool Type, select LUA.

6	Supply information as described in the remainder of this topic.


1	In the LU Pools window, select the pool.

If the pool you want does not appear in the list, from the View menu, choose All LU Pools, and then select the pool.

2	On the Toolbar, click  [image].


  Creating 3270 LU Pools


  Creating 3270 LU Pools

  Creating LUA Pools

  Creating Downstream Pools

  Assigning LUs to an LU Pool

  Configuring Servers, Connections, and LUs: Overview

  Resetting LUs

  Using Diagnostic Tools: Overview

  Topic List for APPC LUs

  Configuring Hot Backup for LUs for 5250


  Configuring Properties for a 3270 LU Pool

  Assigning LUs to an LU Pool


  Creating 3270 LU Pools

  Assigning LUs to an LU Pool


  Removing LUs from an LU Pool

  Moving an LU to a Different Pool

  Using LU Pools to Maximize Access: Overview

  Creating 3270 LU Pools

  Creating LUA Pools

  Creating Downstream Pools


  Assigning LUs to an LU Pool

  Moving an LU to a Different Pool

  Using LU Pools to Maximize Access: Overview

  Creating 3270 LU Pools

  Creating LUA Pools

  Creating Downstream Pools


  Assigning LUs to an LU Pool

  Removing LUs from an LU Pool

  Using LU Pools to Maximize Access: Overview

  Creating 3270 LU Pools

  Creating LUA Pools

  Creating Downstream Pools


  Assigning LUs to an LU Pool


  Initial Connection Settings for 802.2

  Initial Connection Settings for SDLC

  Initial Connection Settings for X.25

  Initial Connection Settings for DFT

  Initial Connection Settings for Channel

  Initial Connection Settings for Twinax


  Configuring Servers, Connections, and LUs: Overview


  Basic 802.2 Settings

  Advanced 802.2 Settings


  Basic SDLC Settings

  Advanced SDLC Settings


  Basic X.25 Settings

  Advanced X.25 Settings


  Basic Channel Settings

  Advanced Channel Settings


  Configuring LUs


  LUs for APPC: Overview

  Topic List for APPC LUs

  Configuring Hot Backup for LUs for 5250


  Adding, Viewing, or Editing CPI-C Information

  Configuring Properties for CPI-C

  CPI-C Properties Form


  Adding, Viewing, or Editing CPI-C Information

  Configuring Properties for CPI-C


  Setting Up 3270 User and Group Access: Overview

  Adding, Viewing, or Modifying Users or Groups

  Configuring Properties for a User or Group

  Giving Users Access to 3270 LUs and LU Pools


  Configuring for NetView

  SNA Server NetView Extensions: NVAlert and NVRunCmd


  Configuring RTM Settings


TOPICS BEFORE THIS ARE SEE ALSOS FOR FORMS; TOPICS AFTER ARE FOR INTER


  Initiating Actions with Menu Commands

  Initiating Actions by Dragging with the Mouse


  Initiating Actions with Keys or Toolbar Buttons

  Initiating Actions with Menu Commands

  Initiating Actions by Dragging with the Mouse


  Initiating Actions with Keys or Toolbar Buttons

  Initiating Actions by Dragging with the Mouse


  Initiating Actions with Keys or Toolbar Buttons

  Initiating Actions with Menu Commands


  Modifying the Display for the Servers and Connections Window

  Modifying the Display for the Users and Groups Window

  Modifying the Display for the LU Pools Window


TOPICS BEFORE THIS ARE SEE ALSOS FOR INTER; TOPICS AFTER ARE FOR MAIN


Expand Button (in Help)

Use this button to expand a collapsed list of Help topics.


Collapse Button (in Help)

Use this button to collapse an expanded list of Help topics.


Topic Button

Use this button to jump to a Help topic.


  Getting Started with the SNA Server Admin Program

  Configuring Servers, Connections, and LUs: Overview

  Using LU Pools to Maximize Access: Overview

  Setting Up 3270 User and Group Access: Overview

  Managing SNA Server and Configuring Security: Overview

  Using Diagnostic Tools: Overview


  Configuring Servers and Connections

  Configuring LUs

  Using LU Pools to Maximize Access: Overview

  Setting Up 3270 User and Group Access: Overview

  Managing SNA Server and Configuring Security: Overview

  Commonly Required Server and Connection Parameters

  Commonly Required LU Parameters

  Guidelines for Specific Configurations


  Viewing the Status of Servers, Connections, and LUs

  Copying and Moving Services

  Starting and Stopping Servers and Connections

  Resetting LUs

  Changing the Domain of Focus

  Deleting SNA Resources

  Working with Configuration Files

  Adding Users and Groups and Setting Permissions

  Configuring SNA Domain Permissions

  Taking Ownership of the Ability to Administer SNA Server

  Setting Up Auditing of Access to the Configuration File


  Adding Users and Groups and Setting Permissions

  Configuring SNA Domain Permissions

  Taking Ownership of the Ability to Administer SNA Server

  Setting Up Auditing of Access to the Configuration File


  Adding, Viewing, or Modifying Users or Groups

  Configuring Properties for a User or Group

  Giving Users Access to 3270 LUs and LU Pools

  Copying Properties and LUs Between Users and/or Groups

  Configuring LUs

  Using LU Pools to Maximize Access: Overview

  Managing SNA Server and Configuring Security


  Viewing the Status of Servers, Connections, and LUs

  Configuring for NetView

  SNA Server NetView Extensions: NVAlert and NVRunCmd

  Using Event Logs

  Configuring RTM Settings

  Performance Monitor Options for SNA Server

  Collecting Traces and Other Detailed System Information

  Working with Configuration Files

  Managing SNA Server and Configuring Security: Overview


TOPICS BEFORE THIS ARE SEE ALSOS FOR MAIN; TOPICS AFTER ARE FOR DBOXS


  Before Using SNA Server Admin

  Configuring Servers, Connections, and LUs: Overview

  Configuring Server Broadcasts


  Before Using SNA Server Admin

  Configuring Servers, Connections, and LUs: Overview

  Initial Connection Settings


  Before Using SNA Server Admin

  Configuring Servers, Connections, and LUs: Overview

  Configuring Servers and Connections

  Configuring LUs


  Before Using SNA Server Admin

  Configuring Servers, Connections, and LUs: Overview

  802.2 Setup Dialog Box

  SDLC Setup Dialog Box

  X.25 Setup Dialog Box


  Configuring Servers, Connections, and LUs: Overview

  Initial Connection Settings

  802.2 Setup Dialog Box (Advanced)

  802.2 Settings Form

  SNA Server, VTAM, and NCP Parameters for 802.2 Connections


  Configuring Servers, Connections, and LUs: Overview

  Initial Connection Settings

  802.2 Setup Dialog Box

  802.2 Settings Form

  SNA Server, VTAM, and NCP Parameters for 802.2 Connections


  Configuring Servers, Connections, and LUs: Overview

  Initial Connection Settings

  SDLC Setup Dialog Box (Advanced)

  SDLC Settings Form

  SNA Server, VTAM, and NCP Parameters for SDLC Connections


  Configuring Servers, Connections, and LUs: Overview

  Initial Connection Settings

  SDLC Setup Dialog Box

  SDLC Settings Form

  SNA Server, VTAM, and NCP Parameters for SDLC Connections


  Configuring Servers, Connections, and LUs: Overview

  Initial Connection Settings

  X.25 Setup Dialog Box (Advanced)

  X.25 Settings Form

  SNA Server, VTAM, and NCP Parameters for X.25 Connections


  Configuring Servers, Connections, and LUs: Overview

  Initial Connection Settings

  X.25 Setup Dialog Box

  X.25 Settings Form

  SNA Server, VTAM, and NCP Parameters for X.25 Connections


  Using Diagnostic Tools: Overview

  Setting Up Security with SNA Server


  Using Diagnostic Tools: Overview

  SNA Server NetView Extensions: NVAlert and NVRunCmd


  Setting Up 3270 User and Group Access: Overview


  Modifying the SNA Server Admin Display


  Adding Users and Groups and Setting Permissions

  Taking Ownership of the Ability to Administer SNA Server

  Setting Up Auditing of Access to the Configuration File


  Configuring SNA Domain Permissions

  Taking Ownership of the Ability to Administer SNA Server

  Setting Up Auditing of Access to the Configuration File


  Adding Users and Groups and Setting Permissions

  Configuring SNA Domain Permissions

  Setting Up Auditing of Access to the Configuration File


  Adding Users and Groups and Setting Permissions

  Configuring SNA Domain Permissions

  Taking Ownership of the Ability to Administer SNA Server


TOPICS BEFORE THIS ARE SEE ALSOS FOR DBOXS; TOPICS AFTER ARE FOR TPC1


  SNA Server Preparation Forms

  Commonly Required Server and Connection Parameters

  Commonly Required LU Parameters

  Guidelines for Specific Configurations

  Configuring Servers and Connections

  Configuring LUs

  Using the SNA Server Admin Interface

  Modifying the SNA Server Admin Display


  Guidelines for Identifiers for 802.2 Connections

  Guidelines for Identifiers for SDLC Connections

  Guidelines for Identifiers for X.25 Connections

  Identifiers in Incoming XIDs


  Using Remote Node Identifiers

  Guidelines for Identifiers for 802.2 Connections

  Guidelines for Identifiers for SDLC Connections

  Guidelines for Identifiers for X.25 Connections


  Before Using SNA Server Admin

  Configuring Servers and Connections


  Before Using SNA Server Admin

  Configuring Server Broadcasts


  Before Using SNA Server Admin

  Configuring Server Identifiers


  Before Using SNA Server Admin

  Basic 802.2 Settings

  Advanced 802.2 Settings


  Before Using SNA Server Admin

  Basic SDLC Settings

  Advanced SDLC Settings


  Before Using SNA Server Admin

  Basic X.25 Settings

  Advanced X.25 Settings


  Before Using SNA Server Admin

  Basic Channel Settings

  Advanced Channel Settings


  Before Using SNA Server Admin


  Initial Connection Settings

  Advanced 802.2 Settings

  802.2 Settings Form

  SNA Server, VTAM, and NCP Parameters for 802.2 Connections


  Initial Connection Settings

  Advanced SDLC Settings

  SDLC Settings Form

  SNA Server, VTAM, and NCP Parameters for SDLC Connections


  Initial Connection Settings

  Advanced X.25 Settings

  X.25 Settings Form

  SNA Server, VTAM, and NCP Parameters for X.25 Connections


  Initial Connection Settings

  Advanced Channel Settings


  Initial Connection Settings

  Basic 802.2 Settings

  802.2 Settings Form

  SNA Server, VTAM, and NCP Parameters for 802.2 Connections


  Initial Connection Settings

  Basic SDLC Settings

  SDLC Settings Form

  SNA Server, VTAM, and NCP Parameters for SDLC Connections


  Initial Connection Settings

  Basic X.25 Settings

  X.25 Settings Form

  SNA Server, VTAM, and NCP Parameters for X.25 Connections


  Initial Connection Settings

  Basic Channel Settings


  Configuring Properties for a 3270 LU

  Configuring Numbering for a 3270 LU Range

  Configuring Servers, Connections, and LUs: Overview

  Configuring Servers and Connections


  Assigning, Viewing, or Modifying 3270 LUs

  Configuring Properties for a 3270 LU Range

  Modifying the Extension Numbering Format


  Assigning, Viewing, or Modifying 3270 LUs

  Setting Up 3270 User and Group Access: Overview

  Creating 3270 LU Pools


  Configuring Numbering for a 3270 LU Range

  Creating 3270 LU Pools

  Setting Up 3270 User and Group Access: Overview


  Topic List for APPC LUs

  Adding, Viewing, or Editing CPI-C Information

  Configuring the Default DISPLAY Connection

  Assigning Default APPC LUs to Users or Groups


  Topic List for APPC LUs


  Topic List for APPC LUs

  Properties of Standard Modes


  Configuring Properties for CPI-C

  CPI-C Properties Form


  Adding, Viewing, or Editing CPI-C Information

  CPI-C Properties Form


  Configuring Properties for LUA LUs

  Configuring Numbering for an LUA LU Range


  Assigning, Viewing, or Modifying LUA LUs

  Configuring Properties for an LUA LU Range

  Modifying the Extension Numbering Format


  Assigning, Viewing, or Modifying LUA LUs

  Creating LUA Pools


  Assigning, Viewing, or Modifying LUA LUs

  Configuring Numbering for an LUA LU Range

  Creating LUA Pools


TOPICS BEFORE THIS ARE SEE ALSOS FOR TPC1; TOPICS AFTER ARE FOR MISC


  Initial Connection Settings

  Basic 802.2 Settings

  Advanced 802.2 Settings

  802.2 Settings Form

  SNA Server, VTAM, and NCP Parameters for 802.2 Connections


  Initial Connection Settings

  Basic 802.2 Settings

  Advanced 802.2 Settings

  802.2 Settings Form

  Sample VTAM Parameters for a Token Ring Connection


  Initial Connection Settings

  Basic SDLC Settings

  Advanced SDLC Settings

  SDLC Settings Form

  SNA Server, VTAM, and NCP Parameters for SDLC Connections


  Initial Connection Settings

  Basic SDLC Settings

  Advanced SDLC Settings

  SDLC Settings Form

  Sample VTAM Parameters for an SDLC Connection


  Initial Connection Settings

  Basic X.25 Settings

  Advanced X.25 Settings

  X.25 Settings Form

  SNA Server, VTAM, and NCP Parameters for X.25 Connections


  Initial Connection Settings

  Basic X.25 Settings

  Advanced X.25 Settings

  X.25 Settings Form

  Sample VTAM Parameters for an X.25 Connection


  Topic List for APPC LUs

  Sample CICS Configuration Screens for LU 6.2


  Topic List for APPC LUs

  Sample VTAM Parameters for LU 6.2


  LUs for APPC: Overview

  Topic List for APPC LUs

  Configuring Hot Backup for LUs for 5250


  LUs for APPC: Overview

  Topic List for APPC LUs

  AS/400 Configuration


  Configuring Properties for a User or Group


  Adding, Viewing, or Modifying Users or Groups

  Configuring Properties for a User or Group


  Giving Users Access to 3270 LUs and LU Pools


  Setting Up 3270 User and Group Access: Overview

  Adding, Viewing, or Modifying Users or Groups

  Giving Users Access to 3270 LUs and LU Pools


  Configuring Properties for a User or Group

  Giving Users Access to 3270 LUs and LU Pools


  Saving and Reopening the Configuration

  Configuration Files on Primary and Backup SNA Servers

  Backing Up and Restoring the Configuration

  Offline Configuration

  Managing SNA Server and Configuring Security


  Working with Configuration Files

  Configuration Files on Primary and Backup SNA Servers

  Backing Up and Restoring the Configuration

  Offline Configuration


  Working with Configuration Files

  Saving and Reopening the Configuration

  Configuration Files on Primary and Backup SNA Servers

  Offline Configuration


  Configuring for NetView

  SNA Server NetView Extensions: NVAlert and NVRunCmd


  The NVAlert Service

  Modifying NVALERT.INI

  Example of NVALERT.INI Section

  The NVRunCmd Service

  Command Syntax for NVRunCmd

  How NVRunCmd Runs

  Functionality Available with NVRunCmd


  SNA Server NetView Extensions: NVAlert and NVRunCmd

  Modifying NVALERT.INI

  Example of NVALERT.INI Section


  The NVAlert Service

  Providing Detailed Data Information

  Example of NVALERT.INI Section


  The NVAlert Service

  Providing Detailed Data Information

  Modifying NVALERT.INI


  Command Syntax for NVRunCmd

  How NVRunCmd Runs

  Functionality Available with NVRunCmd


  The NVRunCmd Service

  How NVRunCmd Runs

  Functionality Available with NVRunCmd


  The NVRunCmd Service

  Command Syntax for NVRunCmd

  Functionality Available with NVRunCmd


  The NVRunCmd Service

  Command Syntax for NVRunCmd

  How NVRunCmd Runs


  Working with Trace Files

  Starting the SNA Server Trace Options (snatrace) Utility

  Using Diagnostic Tools: Overview

  Using Event Logs


  Collecting Traces and Other Detailed System Information

  Starting the SNA Server Trace Options (snatrace) Utility

  Using Diagnostic Tools: Overview


  Collecting Traces and Other Detailed System Information

  Working with Trace Files

  Using Diagnostic Tools: Overview


  Offline Configuration

  Guidelines for Offline Configuration


  Offline Configuration

  Using the Offline Version of SNA Server Admin


  Guidelines for Offline Configuration

  Using the Offline Version of SNA Server Admin


  Offline Configuration

  Guidelines for Offline Configuration

  Using the Offline Version of SNA Server Admin


  Using Diagnostic Tools: Overview

  Viewing the Status of Servers, Connections, and LUs

  Using Event Logs


TOPICS BEFORE THIS ARE SEE ALSOS FOR MISC; TOPICS AFTER ARE FOR THE INTERFACE.


Properties Button

Use this button to view or modify the selected server, connection, LU, pool, user, or group.


Start Button

Use this button to start the selected server or connection.


Stop Button

Use this button to stop the selected server or connection, or reset the selected LU.


Insert Button

Use this button to initiate adding a connection, LU, pool, user, or group. For adding a connection to a server, first select the server, then the Insert button. For adding an LU to a connection, first select the connection, then the Insert button.


Delete Button

Use this button to delete the selected item.


Reopen Button

Use this button to reopen the last configuration saved.

The configuration is reopened from the configuration file on the primary SNA server. If the primary server is not functioning and a backup SNA server is available, the configuration is reopened (read-only) from the copy of the configuration file on the backup server.


Save Button

Use this button to save the current configuration.

The configuration is saved to the configuration file on the primary SNA Server. If the primary SNA server is not functioning, the only way to save a configuration is by using the Backup command.


 Insert button

or INS key


 Properties button

or ENTER key


 Delete button

or DEL key


F8  key


F7  key


 Start button

or F5 key


 Stop button

or F3 key


 Reopen button


 Save button


Note on Saving the Configuration

With the Save button, the configuration file is saved on the primary SNA server. If the primary server is not functioning, the only way to save a configuration is by using the Backup command.


Note on Reopening the Configuration

The configuration is reopened from the configuration file on the primary SNA server. If the primary server is not functioning and a backup SNA server is available, the configuration is reopened (read-only) from the copy of the configuration file on the backup server.


In the Servers and Connections window,
select [image] the server, then click [image] or press INS.


In the Servers and Connections window,
select the connection, then click [image] or press INS.


In the Users and Groups window,
select any line, then click [image] or press INS.


In the Users and Groups window,
select the user or group, then
click [image] or press INS.


In the LU Pools window,
select any line, then click [image] or press INS.


In the LU Pools window,
select the LU pool, then click [image] or press INS.


In the Servers and Connections window,
select the connection, then click [image] or press ENTER.


In the Servers and Connections window,
select the LU, then click  [image] or press ENTER.


In the Users and Groups window,
select the user or group, then
click [image] or press ENTER.


In the LU Pools window,
select the LU pool, then click [image] or press ENTER.


In the Servers and Connections window,
select [image] the server, then click [image] or press DEL.


In the Servers and Connections window,
select the connection, then click [image] or press DEL.


In the Servers and Connections window,
select the LU, then click  [image] or press DEL.


In the Users and Groups window,
select the user or group, then
click [image] or press DEL.


In the Users and Groups window, select
the LU or pool as it is listed across from
the user or group, then click  [image] or press DEL.


In the LU Pools window, select the LU
as it is listed across from the pool, then click
 or press DEL.


In the LU Pools window,
select the LU pool, then click [image] or press DEL.


In the Users and Groups window, select the LU
as it is listed across from the user or group, then
click [image] or press DEL.


In the Servers and Connections window,
select the connection from which to
copy properties, then press F8.


In the Servers and Connections window,
select the LU from which to copy properties,
then press F8.


In the Users and Groups window,
select the user or group from which
to copy properties, then press F8.


Use this command for starting a server or connection.


Use this command for stopping a server or connection, or resetting an LU. When an LU is selected, the command appears as "Reset LU."


Use this command for adding a connection to a server.


Use this command for adding an LU to a connection.


Use this command for moving a connection from one server to another, or moving an LU from one connection to another.


(Available for downstream connections only): use this command for reordering the number of an LU or LU pool among those on the selected connection.


Use this command for copying properties from one connection or LU to another.


Use this command for viewing or modifying an existing server, connection, or LU.


Use this command for adding a network user or group to the list used by SNA Server.


Use this command for assigning LUs or LU pools to a user or group.


Use this command for changing the number of an LU (to change its place in users' displays).


Use this command for copying properties and LUs from one user or group to another.


Use this command for viewing or modifying the properties for an existing user or group.


Use this command for resetting LUs that are in an LU pool.


Use this command for adding a new LU pool.


Use this command for assigning LUs to an LU pool.


Use this command for moving LUs from one LU pool to another.


Use this command for viewing or modifying properties for an existing LU pool.


Use this command for specifying the connection to be used for NetView.

NetView is a reporting system that runs on an IBM host (mainframe), forwarding alerts back and forth between the host and the PCs that connect to it.


Use this command for specifying parameters for the Response Time Monitor (RTM), which monitors the amount of time it takes for a host to respond during 3270 display sessions.


Use this command for specifying the location and the level of detail for SNA Server logs.


Use this command for specifying properties for the Common Programming Interface for Communications (CPI-C). CPI-C is a set of C-language routines that application programs distributed across an SNA network can use to work together.


Use this command for specifying the default connection to be used for the DISPLAY verb, an APPC verb that returns configuration information and current operating values for an SNA server.


Use this command to configure server broadcasts to support network software and protocols: Microsoft Networking (Named Pipes), Novell NetWare (IPX/SPX), Banyan VINES/IP, Windows Sockets (TCP/IP), IP routers, SNA Server 2.0 servers, and/or Comm Server clients.


Use this command for turning the following on and off: the Toolbar, status bar, advanced configuration displays, confirmation following mouse operations, and the saving of window settings on exit.


Use this command for setting permissions for administrative access to SNA Server.


Use this command for setting up auditing of administrative access to SNA Server.


Use this command if it is necessary to take ownership of administrative access to SNA Server.


Use this command for reopening the configuration as it was when last saved, abandoning changes made since then.

The configuration is reopened from the configuration file on the primary SNA server. If the primary server is not functioning and a backup SNA server is available, the configuration is reopened (read-only) from the copy of the configuration file on the backup server.


Use this command for saving the current configuration (the displayed configuration).

With this command, the configuration file is saved on the primary SNA server. If the primary server is not functioning, the only way to save a configuration is by using the Backup command.


Use this command for saving the current configuration as a backup file.


Use this command for restoring a configuration that was saved as a backup file.


Use this command for selecting the domain containing the SNA servers to be displayed in SNA Server Admin.


Use this command for exiting SNA Server Admin.


Server icon

Represents an SNA server.


Servers and Connections icon

Represents the Servers and Connections window; to restore the window from the icon, double-click the icon.


LU Pools icon

Represents the LU Pools window; to restore the window from the icon, double-click the icon.


Users and Groups icon

Represents the Users and Groups window; to restore the window from the icon, double-click the icon.


TOPICS BEFORE THIS ARE FOR THE INTERFACE; TOPICS AFTER ARE FOR CONNECTIONS.


Mean Time between Server Broadcasts

The interval at which server broadcasts are repeated. Broadcasts of state changes (such as the activation of a server) do not wait for this interval; instead, broadcasts are repeated at this interval to ensure reception (since broadcasts by definition are not guaranteed to be received).


Connection Name

A name identifying an SNA connection. The name can be from one through eight characters long and can contain alphanumeric characters and the special characters $, #, and @. Lowercase letters are converted to uppercase. The name cannot be the same as any other Connection Name in the installation and cannot be the reserved name SNASERVR.


Default for Activation

For 802.2 (token ring or Ethernet) DFT, Channel, and Twinax connections, the default is On Server Startup. For all other connections, the default is On Demand.


Default for Activation

For 802.2 (token ring or Ethernet) connections, the default is On Server Startup.


Default for Activation

For SDLC connections, the default is On Demand.


Default for Activation

For X.25 connections, the default is On Demand.


Default for Activation

For DFT connections, the default is On Server Startup.


Default for Activation

For Channel connections, the default is On Server Startup.


Default for Activation

For Twinax connections, the default is On Server Startup.


Default for Virtual Circuit Type

The default is Switched.


Default for Allowed Directions

The default is Outgoing Calls.


On Server Startup

A setting that starts the connection when the SNA server used by the connection is started, giving faster access to the first user who connects after startup. It is a good choice when charges for the communications line are fixed rather than assessed per time unit, specifically, 802.2 (token ring or Ethernet) connections, SDLC leased-line connections, and X.25 permanent virtual circuit connections.


On Demand

A setting that starts a connection when it is needed, and stops the connection when not in use. It is a good choice when charges for the line are assessed per time unit, specifically, SDLC switched-line connections and X.25 switched virtual circuit connections.


By Administrator

A setting that allows the administrator to control the starting of a connection on a case-by-case basis.


Dial Data

Information used when dialing; can be from 1 through 40 characters long. The way that SNA Server handles dial data depends on the modem's dialing method:

For a modem that accepts a phone number from SNA Server--that is, a modem attached to an SDLC adapter with a built-in serial (COM) port (for example, SDLC adapters from Microgate)--the dial data is the telephone number for SNA Server to send to the modem. Type the number in the format expected by the modem.

For a modem that accepts a manually dialed number, the dial data appears in a pop-up message when the connection is started. Type the telephone number that should appear in the pop-up message.


Default for Local Node ID

The default is 05D FFFFF.


Local Node ID

An eight-digit hexadecimal number that identifies the local system. Type the first three digits (the block number) in the first box and the last five digits (the node number) in the second box. Contact the host, peer, or downstream administrator(s) and notify them of the Local Node ID used for your system. For host systems, the numbers should match corresponding parameters in the VTAM PU definition: block number should match IDBLK, and node number should match IDNUM.


Remote Node ID

The eight-digit hexadecimal number that the remote system will send when establishing a connection. Type the first three digits (the block number) in the first box and the last five digits (the node number) in the second box. Contact the remote system's administrator for the correct values.


Network Name

A name identifying the SNA network of a system. The Network Name is used in Format 3 XIDs. The name can be from one through eight characters long and can contain alphanumeric characters and the special characters $, #, and @. Lowercase letters are converted to uppercase. The first character cannot be a digit.

The Network Name works with the Control Point Name to identify a system. If either of these parameters is supplied, the other should also be supplied.

With SNA Server Admin, the local Network Name is set in a different dialog box than the remote Network Name. The local Network Name is set in the Server Properties dialog box; the remote Network Name is set in the Connection Properties dialog box.


Control Point Name

A name that identifies a control point (node) to another control point on the SNA network. The Control Point Name is used in Format 3 XIDs. The name can be from one through eight characters long and can contain alphanumeric characters and the special characters $, #, and @. The first character cannot be a digit.

The Control Point Name works with the Network Name to identify a system. If either of these parameters is supplied, the other should also be supplied.

With SNA Server Admin, the local Control Point Name is set in a different dialog box than the remote Control Point Name. The local Control Point Name is set in the Server Properties dialog box; the remote Control Point Name is set in the Connection Properties dialog box.


Note About SNA Server Parameters and VTAM

The Network Name for the local SNA server corresponds to the NETID parameter in the VTAM Start command for the local SSCP (the VTAM system to which SNA Server is attached). Note: this is generally the same as the NETID for the remote SSCP.

The Control Point Name for the local SNA server corresponds to the CPNAME parameter in the PU definition of VTAM or NCP. For information, contact the host administrator.


Note About Connection Parameters and VTAM

When connecting to a host system and using a remote Network Name, the name should match the NETID parameter in the VTAM Start command for the remote SSCP (the VTAM system). For information, contact the host administrator.

When connecting to a host system and using a remote Control Point Name, the name should match the SSCPNAME parameter in the VTAM Start command for the remote SSCP (the VTAM system).


Note About APPC LU Parameters and VTAM

The Network Name for an APPC LU that communicates with a host should match the NETID parameter in the VTAM Start command for the VTAM system.

If this SNA server communicates with several different hosts over several connections, use the name of the subarea of the host with which the LU will communicate.


Note About APPC LU Parameters and VTAM

The Network Name for an APPC LU that communicates with a host should match the NETID parameter in the VTAM Start command for the VTAM system.


Note About AS/400 Computers

To connect to an AS/400 computer, supply the following parameters:

For the SNA server (local node): In the Server Properties dialog box, type the Control Point Name and the Network Name of the SNA server, corresponding to RMTCPNAME (in the Controller Description) and (usually) to RMTNETID on the AS/400.

For the connection that the AS/400 will use: In the 802.2 Setup dialog box, the SDLC Setup dialog box, or the X.25 Setup dialog box, find the Network Name (Remote Node) and Control Point Name (Remote Node) fields, and type the Network Name and Control Point Name (CP name) of the AS/400. For more information about these fields, see the topic on basic settings for the chosen connection type (802.2, SDLC, or X.25).

On an AS/400, the Network Name is specified as the RMTNETID parameter. For more information, see your APPN documentation.


Note About AS/400 Computers

To connect to an AS/400 computer, supply the following parameters:

For the connection that the AS/400 will use: In the 802.2 Setup dialog box, the SDLC Setup dialog box, or the X.25 Setup dialog box, find the Network Name (Remote Node) and Control Point Name (Remote Node) fields, and type the Network Name and Control Point Name (CP name) of the AS/400.

On an AS/400, the Network Name is specified as the RMTNETID parameter. For more information, see your APPN documentation.

For the SNA server (node): In the Server Properties dialog box, type the Control Point Name and the Network Name of the SNA server, corresponding to RMTCPNAME (in the Controller Description) and (usually) to RMTNETID on the AS/400. For information about the Server Properties dialog box, see the topic on configuring servers.


Note About DFT Link Services

Although you can use as many as four DFT adapters in one computer, you must use one link service for all the DFT adapters in that computer.


Note About Downstream Connections

For connections to downstream systems, be sure to set the Max BTU Length to a value supported by the downstream system. Max BTU Length is set in the Advanced section of the dialog box for the connection.


Default for XID Type

The default is Format 3.


XID Type

The type of identifying information for SNA Server to send:

Format 0 sends only the Node ID. Use this option only if connecting to a host that does not support Format 3; most hosts support Format 3.

Format 3 sends up to 100 bytes of identifying information, including the Local Node ID and Control Point Name.


Default for Encoding

The default is NRZI.


encoding scheme

One of two encoding methods for modems:

NRZ--Non-return to zero

NRZI--Non-return to zero inverted


Note on Encoding and VTAM

For connections to host systems, the encoding scheme must match the NRZI setting in the LINE/GROUP definition in VTAM. Obtain this setting from the host administrator. If VTAM does not specify an NRZI setting, it defaults to NRZI=YES.


Note on Encoding for Incoming-Call Connections

When multiple SDLC connections all use the same link service, and the connections accept incoming calls, the encoding (NRZ/NRZI) settings for all the connections must match.


Default for Duplex

The default is Half.


Note About Adapters

If your adapter is an IBM SDLC, IBM MPCA, or Microgate adapter, or any other SDLC adapter that does not contain a coprocessor, and you want to use a transmission speed greater than 9600 baud, select Half, not Full. Adapters that lack a coprocessor cannot handle full-duplex transmission at high transmission speeds.


Default for Data Rate

The default is High.


Data Rate

The data rate for transmissions between the SNA Server communications adapter and the modem:

"Low" gives more reliable transmissions and prevents the transmission errors sometimes caused by poor-quality lines at the high rate. If a fall-back line speed setting is supported by your modem and communications adapter, and you want to enable it, select Low.

"High" gives faster transmissions. If you select High, the CCITT line 111 on the V24 interface of your modem is set to on.


Default for Select Standby

By default, this setting is off.


standby line

A backup line (usually switched) available with some leased line modems.


BTU length

Basic transmission unit length. The number of bytes that can be transmitted in a single data-link information frame. For SDLC, a BTU is also called an I-frame.


THE FOLLOWING POP-UP IS REFERRED TO IN A DOWNSTREAM TOPIC IN S_ONLY.


Max BTU Length

Maximum basic transmission unit length. The maximum number of bytes that can be transmitted in a single data-link information frame. A BTU is sometimes called an I-frame.

For downstream connections, specify a Max BTU Length less than or equal to the maximum value supported by software on the downstream system.

For host connections, specify a Max BTU Length less than or equal to the VTAM PU definition for the MAXDATA= parameter.


Note About Max BTU Length

For host connections, specify a Max BTU Length less than or equal to the VTAM PU definition for the MAXDATA= parameter.

For downstream connections, specify a Max BTU Length less than or equal to the maximum value supported by the downstream system.

With an IBM SDLC adapter, set the Max BTU Length to 521 or less.


Range and Default for Max BTU Length

The range is from 265 through 16393; the default is 265.

With an IBM SDLC adapter, set the Max BTU Length to 521 or less.


Default for Poll Address

The default is C1.


Note on Poll Address

If the remote system is a host, the local poll address should match the VTAM PU definition for the ADDR= parameter.

If the remote system is a peer, the poll address can be any value except the reserved values 00 and FF. When the connection is used, the link roles will be negotiable; the system that takes on the primary role uses the poll address of the other system, so that the poll addresses match during the session.


Note About Sessions Affected

This parameter affects sessions in which the SNA server has a link role of primary; therefore, it affects all sessions with a downstream system and some sessions with a peer system (where the link role is negotiable).


Range and Default for Poll Timeout

The range is from 1 (one-tenth of a second) through 300 (30 seconds). The default is 10 (1 second).


Range and Default for Poll Retry Limit

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


Note About Sessions Affected

This parameter affects sessions in which the SNA server has a link role of secondary; therefore, it affects all sessions with a host system and some sessions with a peer system (where the link role is negotiable).


Range and Default for Idle Timeout

The range is from 1 (one-tenth of a second) through 300 (30 seconds). The default is 300 (30 seconds).


Range and Default for Idle Retry Limit

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


Range and Default for Contact Timeout

The range is from 5 (five-tenths of a second) through 300 (30 seconds).

The default for a host connection is 300 (30 seconds). The default for a peer or downstream connection is 10 (1 second).


Range and Default for Contact Retry Limit

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


Range and Default for Poll Rate

The range is from 1 through 50 polls per second; the default is 5.


Range and Default for Switched Connection Establishment Timeout

The range is from 10 through 500 seconds; the default is 300.


multidrop connection

A connection through which one primary computer simultaneously communicates with multiple secondary computers. SNA Server supports multidrop connections to peer or downstream systems on leased SDLC lines.


Remote Network Address

A 12-digit hexadecimal network address. Contact the remote system's administrator or the network administrator for the correct value. The value is determined as follows:

For connections to a 3174 controller, use the value in the configuration response 900 of the controller's customization program.

For connections to a 3720, 3725, or 3745 front-end processor, use the value in the MACADDR= parameter in the NCP configuration.

For connections to an IBM 9370 host, use the value in the VTAM PORT definition for the MACADDR= parameter.

For connections to another SNA Server system, the network address can be found through the net config server command. When this command is typed at the command prompt of the other SNA Server system, the resulting display shows the network address of that system, in the line labeled "Server is active on."


Default for Remote Network Address

The default is 400000000000.


Remote Service Access Point (SAP) Address

A 2-digit hexadecimal number--a multiple of 04, between 04 and EC. See your token ring or Ethernet manual for more information. You can also contact the remote system's administrator for information about the following:

For connections to a 3174 controller, use the value in the configuration response 940 of the controller's customization program.

For connections to an IBM 9370 host, use the value in the VTAM PU definition for the SAPADDR= parameter.


Default for Remote SAP Address

The default is 04.


BTU length

Basic transmission unit length. The number of bytes that can be transmitted in a single data-link control frame. For 802.2, a BTU is also called an I-frame.


Note About Max BTU Length

For host connections, specify a Max BTU Length less than or equal to the VTAM PU definition for the MAXDATA= parameter.

For downstream connections, specify a Max BTU Length less than or equal to the maximum value supported by the downstream system.

For a token ring adapter that transmits at 4 Mbps (four megabits per second), specify a Max BTU Length less than or equal to 4195.

For a token ring adapter that transmits at 16 Mbps (16 megabits per second), you can specify 16393, the greatest Max BTU Length available with SNA Server.

For an Ethernet adapter, specify a Max BTU Length less than or equal to 1493.


Range and Default for Max BTU Length

The range is from 265 through 16393. The default for token ring is 1929; the default for Ethernet is 1493.


Response (t1) Timeout

The amount of time that the local system should wait for the remote system to respond to a transmission before the local system tries again.


Selecting a Response Timeout

Select a value greater than the total amount of time needed for the relaying of frames between the local system, the remote system, and the network.

Select Default to allow for two timeout values--one for a remote system on a local ring, one for a remote system on a remote ring. If you do not select Default, but instead select a specific value, the timer always waits the selected amount of time, regardless of whether the remote system is on a local or remote ring.


Default for Response Timeout

The values used for Default for the Response Timeout are 400 milliseconds for a local ring and 2 seconds for a remote ring.

If you do not select Default, but instead select a specific value, the timer always waits the selected amount of time, regardless of whether the remote system is on a local or remote ring.


Note About Timeouts for 802.2

The timeouts for 802.2 (t1, t2, and ti) are derived from basic timer values that are set in the Windows NT Registry. SNA Server is designed with the assumption that these Registry values will not be changed after they have been set by the DLC (802.2) driver. If these Registry values are changed, the choices displayed in the Response Timeout, Receive ACK Timeout, and/or Inactivity Timeout fields may no longer reflect the actual amounts of time that SNA Server waits.

For details about the DLC protocol that specifies how timeouts are derived from basic timer values, see the Windows NT Resource Guide.


Receive ACK (t2) Timeout

The maximum amount of time that should be allowed before the local system sends an acknowledgment of a received transmission. An acknowledgment is sent at the end of the timeout, if it has not already been triggered by some other process.


Selecting a Receive ACK Timeout

Select a value less than the Response Timeout, so that the local system takes less time to acknowledge received transmissions than it takes to seek responses to sent transmissions.

Select Default to allow for two timeout values--one for a remote system on a local ring, one for a remote system on a remote ring. If you do not select Default, but instead select a specific value, the timer always waits the selected amount of time, regardless of whether the remote system is on a local or remote ring.


Default for Receive ACK Timeout

The values used for Default for the Receive ACK Timeout are 80 milliseconds for a local ring and 800 milliseconds for a remote ring.

If you do not select Default, but instead select a specific value, the timer always waits the selected amount of time, regardless of whether the remote system is on a local or remote ring.


Inactivity (ti) Timeout

The amount of time that the link can be inactive before the local system treats it as nonfunctioning and shuts it down.


Selecting an Inactivity Timeout

Select Default to allow for two timeout values--one for a remote system on a local ring, one for a remote system on a remote ring. If you do not select Default, but instead select a specific value, the timer always waits the selected amount of time, regardless of whether the remote system is on a local or remote ring.


Default for Inactivity Timeout

The values used for Default for the Inactivity Timeout are 5 seconds for a local ring and 25 seconds for a remote ring.

If you do not select Default, but instead select a specific value, the timer always waits the selected amount of time, regardless of whether the remote system is on a local or remote ring.


Range and Default for Receive ACK Threshold

The range is from 1 through 127; the default is 2.


Range and Default for Unacknowledged Send Limit

The range is from 1 through 127; the default is 8.


Range and Default for Retry Limit

The range is from 0 through 255; the default is 10. A value of 0 means the system uses its internal default retry limit.


Range and Default for XID Retries

The range is from 0 through 30; the default is 3.


Remote X.25 Address

An address specifying the X.25 remote system. The address consists of from 1 through 15 hexadecimal digits. Contact the network administrator for the correct value. If a 15-digit address is used, the final 3 digits are used for routing between stations with the same 12-digit address.

For connections to a host using VTAM, use the value in the VTAM PORT definition for the DIALNO= parameter.


Note About Adapters for X.25

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.


Range and Default for PVC Alias

The range is from 1 through the number of configued PVC channels; the default is 1.


Range and Default for Packet Size

The possible values are 64, 128, 256, 512, and 1024. The default is 128.


Range and Default for Window Size

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


BTU length

Basic transmission unit length. The number of bytes that can be transmitted in a single data-link information frame.


Note About Max BTU Length

For host connections, specify a Max BTU Length less than or equal to the VTAM PU definition for the MAXDATA= parameter.

For downstream connections, specify a Max BTU Length less than or equal to the maximum value supported by the downstream system.


Range and Default for Max BTU Length

The range is from 265 through 16393. The default for host connections is 265; the default for peer connections is 1033.


Facility Data

A coded string of information often used to request nondefault functions from the X.25 network for a particular SVC connection. The data string is built up from shorter groupings, or "requests," consisting of a two-character identifier followed by a series of parameter characters. Obtain information about facility data from the network administrator.


User Data

A coded string of information, specifying items such as the communications protocol used by the X.25 network (for SNA, this protocol must be QLLC, specified by C3). Obtain information about user data from the network administrator.


Default for User Data

The default is C3; this specifies the Qualified Logical Link Control (QLLC) protocol.


Note About Max BTU Length

For host connections, specify a Max BTU Length less than or equal to the VTAM PU definition for the MAXDATA= parameter.


Range and Default for Max BTU Length

The range is from 265 through 16393. The default is 4105.


TOPICS BEFORE THIS ARE FOR CONNECTIONS; TOPICS AFTER THIS ARE FOR LUs.


Range for LU number

The range is from 1 through 254.


LU Number

A number identifying an LU on its connection. Check with the administrator of the host system for the correct value; it should match the LOCADDR= parameter of the LU definition in VTAM or in the NCP Gen.

If the number you specify has already been assigned to an LU or an APPC LU-LU pair on the current connection, a message box appears, and you must change the number.


LU Name

A name identifying an LU. The name can be from one through eight characters long and can contain alphanumeric characters and the special characters $, #, and @. Lowercase letters are converted to uppercase. The name cannot be the same as any other LU name or pool name (except for APPC LU names) on the server.


Base LU Name

The name on which the numbered range of names will be built.

There is a limit of eight characters total for the base LU name and the range extension numbers (the numbers appended to the end of the base LU name). Therefore, if you plan to use three-digit extension numbers, limit the base name to five characters or less. If you plan to use two-digit extension numbers, limit the base name to six characters or less.

The name can contain alphanumeric characters and the special characters $, #, and @. Lowercase letters are converted to uppercase. The names formed for the range of LUs cannot be the same as any other LU name or pool name (except for APPC LU names) on the server.


Possible Values for First LU Number

Possible values are from 1 through 254.


Possible Values for Number of LUs

Possible values are from 2 through 254.


Range and Default for First Extension

The range is from 0 through 999 for decimal and from 0 through FFF for hexadecimal. The default is the value specified for First LU Number.


Default for Add Leading Zeroes

By default, leading zeroes are added.


Default for LU Type

The default is Display.


Display Model

One of several different sizes of display:

Model 2 is 24 lines by 80 characters.

Model 3 is 32 lines by 80 characters.

Model 4 is 43 lines by 80 characters.

Model 5 is 27 lines by 132 characters.

If an LU is assigned to a pool, the display model setting for the pool overwrites the setting of the LU, and the setting displayed in the 3270 LU Properties dialog box is dimmed.


Default for Display Model

The default is Model 2.


Note on LU and LU Pool Settings

If the LU is assigned to a pool, the model override setting of the pool overwrites the setting of the LU, and the setting displayed in the 3270 LU Properties dialog box is dimmed.


Default for Model can be overridden

By default, this check box is selected.


Note on LU and LU Pool Settings

If the LU is assigned to a pool, the priority setting of the pool overwrites the setting of the LU, and the setting displayed in the LUA LU Properties dialog box is dimmed.


Default for High Priority LU

By default, this check box is selected.


Pool Name

A name identifying an LU pool. The name can be from one through eight characters long, and can contain alphanumeric characters and the special characters $, #, and @. Lowercase letters are converted to uppercase. The name cannot be the same as any other LU name or pool name (except for APPC LU names) on the server.


Default for LUA High Priority LU Pool

By default, this check box is selected.


LU Alias

A name that identifies an APPC LU to local TPs. The name can be from one through eight characters long and can contain alphanumeric characters and the special characters %, $, #, and @. Lowercase letters are converted to uppercase.

For a local APPC LU, the LU Alias must be unique on the server. For a remote APPC LU, the LU Alias must be unique on the connection, and must not match that of a local LU on that server.

Assigning the same LU Alias on different servers can provide hot backup. That is, if the same LU alias is configured on several different servers, and a TP requests that LU alias, the LU will be available as long as one of the servers is functioning.

The LU Alias and LU Name for an APPC LU can match each other, or differ.


Network Name

A name identifying the SNA network. The name can be from one through eight characters long and can include alphanumeric characters and the special characters $, #, and @. The first character cannot be a digit.


Default for Network Name

The default is the network name specified for the SNA server. If no network name has been specified for the server, the default is APPN.


LU Name

A name identifying an APPC LU. The name can be from one through eight characters long and can contain alphanumeric characters and the special characters $, #, and @. Lowercase letters are converted to uppercase. The first character cannot be a digit.

For a local APPC LU, the fully qualified LU Name (Network Name plus LU Name) must be unique on the server. For a remote APPC LU, the fully qualified LU Name must be unique on the connection, and must not match that of a local LU on that server.

For an independent LU, the LU Name identifies the LU to other components on the SNA network, and therefore is required. For a dependent LU, the LU Name identifies the LU to local software, such as the Windows NT event log software, and is recommended but not required.

The LU Name and LU Alias for an APPC LU can match each other, or differ.


LU Name

A name identifying an APPC LU. The name can be from one through eight characters long and can contain alphanumeric characters and the special characters $, #, and @. Lowercase letters are converted to uppercase. The first character cannot be a digit.

For a local APPC LU, the fully qualified LU Name (Network Name plus LU Name) must be unique on the server. For a remote APPC LU, the fully qualified LU Name must be unique on the connection, and must not match that of a local LU on that server.


Note About LU Name

For independent APPC, the LU Name identifies the LU to other components on the SNA network, and therefore is required. For dependent APPC, the LU Name identifies the LU to local software, such as the Windows NT event log software, and is recommended but not required.

The LU Name and LU Alias for an APPC LU can match each other, or differ.


LU Number

A number identifying a dependent APPC LU on its connection. Check with the administrator of the host system for the correct value; it should match the LOCADDR= parameter for the LU definition in VTAM or in the NCP Gen.

Check the LU numbers for any non-APPC LUs on the connection that the remote partner for this LU will use. Avoid duplicating LU numbers between the local LU and any LUs on that connection. When you try to pair LUs, if an LU number is duplicated in this way, a message box appears, and you must change the number for one of the LUs.


Range for LU Number

The usual range is from 1 through 254. For a dependent LU that will be paired with a remote LU using a DFT connection, use a range of 2 through 254.


Uninterpreted LU Name

The name of the remote LU as defined on the remote system services control point (SSCP); this is generally the name of the host application (such as TSO or IMS). This name is required for dependent APPC. The name can be from one through eight characters long and can contain alphanumeric characters and the special characters $, #, @, and period (.).

The Uninterpreted LU Name, LU Alias, and LU Name can match each other, or differ. Each of these labels identifies the LU to a particular set of software components.


If you use automatic partnering, after creating the intended local LU(s) and remote LU(s), you can view the pairing(s) of local LU, remote LU, and mode that have automatically been created.

For communication with an AS/400, confirm that these LU-LU pairs use the QPCSUPP mode, which is the correct mode to use with an AS/400.


If you disable automatic partnering as you create LUs and modes, you must explicitly pair the local LU(s) with the remote LU(s), and assign a mode to each pair.

For communication with an AS/400, the mode to use is QPCSUPP.


Note on Automatic Partnering

SNA Server checks for automatic partners every time a new APPC LU or mode is created with automatic partnering enabled. At that time, SNA Server searches for existing LUs and modes that also have automatic partnering enabled. SNA Server then uses all available automatic partners to create as many unique LU-LU pairs as possible, each pair containing a remote LU, local LU, and assigned mode. Disabling an automatic partner setting after an LU or mode has been created does not remove that LU or mode from LU-LU pairs already generated.


local automatic partner

A local LU that is partnered with every remote LU and mode that is also designated as an automatic partner.


remote automatic partner

A remote LU that is partnered with every local LU and mode that is also designated as an automatic partner.

With remote LUs having the same fully qualified name (Network Name plus LU Name) and/or the same LU Alias on the same server, automatic partnering should not be used. These LUs cannot be partnered with the same local LU and mode. Automatic partnering will create only one LU-LU pair for each unique set of names (choosing the remote LU randomly, if a choice must be made); it will not create additional pairs with the same set.


Note About the Default Outgoing Local APPC LU Pool

When a request comes from an invoking TP, and the request does not specify a local LU for the invoking TP to use, SNA Server first checks the user record of the user who started the TP, and tries to use the default local APPC LU assigned to that user or group. If this does not succeed, SNA Server tries to find a free LU in the pool of Default Outgoing Local APPC LUs. If this in turn does not succeed, the request is rejected.


Timeout for Starting Invokable TPs

The number of seconds that the SNA server should wait for the invokable TP to respond to a start request from the invoking TP. After this time, responses from the invokable TP are ignored.


Range and Default for Timeout for Starting Invokable TPs

The range is from 1 through 3600 seconds; the default is 60 seconds.


Range and Default for Parallel Session Limit

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


Range and Default for Minimum Contention Winner Limit

The range is from 0 through the Parallel Session Limit; the default is 0.


Minimum Contention Winner Limit

The minimum number of sessions in which the local LU must be able to initiate conversations without permission from the partner LU--that is, in which the local LU must be the contention winner.


Range and Default for Partner Min Contention Winner Limit

The range is from 0 through the Parallel Session Limit; the default is 0.


Partner Min Contention Winner Limit

The minimum number of sessions in which the partner LU must be able to initiate conversations without permission from the local LU--that is, in which the partner LU must be the contention winner.


Range for Automatic Activation Limit

The range is from 0 through the Minimum Contention Winner Limit.


Note: the following topic exists for the APPC LU Overview, not for the main instructions.


Automatic Activation Limit

The number of contention winner sessions to be activated for the local LU whenever the connection is started.


Mode Name

A name identifying a mode. The name can be from one through eight characters long and can contain alphanumeric characters and the special characters $, #, and @. Lowercase letters are converted to uppercase. The first character cannot be a digit. The name cannot be the same as any other mode name in the domain of the server.


Range and Default for Pacing Send Count

The range is from 0 through 63; the default is 4.


Range and Default for Pacing Receive Count

The range is from 0 through 63; the default is 4.


Range and Default for Max Send RU Size

The range is from 256 through 16384; the default is 1024.


Range and Default for Max Receive RU Size

The range is from 256 through 16384; the default is 1024.


Default for High Priority Mode

By default, this box is selected.


QPCSUPP mode

Intended for all communication with AS/400 systems.


#BATCH mode

Intended for batch-oriented sessions.


#BATCHSC mode

Intended for batch-oriented sessions that employ a minimal level of routing security.


BLANK mode

Intended for sessions using a default mode name, encoded as eight blank EBCDIC spaces in BIND.


#INTER mode

Intended for interactive sessions.


#INTERSC mode

Intended for interactive sessions that employ a minimal level of routing security.


Note About Uniqueness of Pairs

For each LU-LU pair, the set of LU aliases and fully qualified LU names combined with a particular mode name must be unique. That is, if you have two remote LUs with the same fully qualified name (Network Name plus LU Name) and/or the same LU Alias on the same server, these LUs must either be paired with different local LUs or (if paired with the same local LU) use different modes.


Session-Level Security

Security that requires a match between the security key for the APPC session and the security key of the remote LU. The session is not activated unless the keys match.


Conversation Security

Security that requires a match between the user ID and password supplied by the invoking TP and the user ID and password stored on the computer where the remote TP resides. If the ID and password do not match, the session is not activated.


Default for Conversation Security

By default, conversation security is off.


Default for Can Prevalidate Conversation Security

By default, prevalidated conversation security is off.


Application TP Name

A name identifying an application TP. The name can be from 1 through 64 characters long and can contain alphanumeric characters and the special characters $, #, and @. Lowercase letters are converted to uppercase.


symbolic destination name

A name assigned to a set of properties for a CPI-C conversation. The name can be from one through eight characters long and can contain alphanumeric characters and the special characters $, #, and @.


SNA Service TP Number

A hexadecimal number identifying an SNA Service TP. The number can be from one through eight hexadecimal digits long.


Fully Qualified Partner LU Name

A two-part name that identifies the remote LU. Each part can be from one through eight characters long and can contain alphanumeric characters and the special characters $, #, and @. Lowercase letters are converted to uppercase. The first part of the fully qualified name is the network name; the second part is the remote LU name. The first character of either name cannot be a digit.


TOPICS BEFORE THIS ARE FOR LUS; TOPICS AFTER THIS ARE FOR OPTIONS (ALERTS ETC.).


pop-up error messages

Pop-up warnings and errors related to activity on the SNA network. These messages can be routed to a remote server, in addition to appearing on the local server. The routed messages do not include messages about an invalid parameter having been typed, or other SNA Server Admin messages.


Note on Pop-Up Error Messages

Pop-up error messages will always appear on the local server; routing them to a remote server means they will appear on both the remote and local server. When pop-up messages appear on a remote server, they include the name of the server on which the error took place.


Alert Description

A description that helps the user of a 3270 emulation program choose which alert to send to a host operator. The description can be from 1 through 52 characters long, and should match the alert type specified by the host administrator. The alert should tell the user which host the alert can be sent to, to avoid errors and pop-up error messages.


Range and Default for RTM Thresholds

The range is from 1 through 1000 tenths of a second (from 0.1 seconds to 100.0 seconds). The defaults are 5, 10, 20, and 50 (0.5 second, 1.0 second, 2.0 seconds, and 5.0 seconds).


TOPICS BEFORE THIS ARE FOR OPTIONS (ALERTS ETC.); TOPICS AFTER THIS ARE FOR USERS.


Precedence of Accounts in Determining LU Access

When user and group account memberships overlap, the highest-priority account that contains a 3270 LU or pool determines the access that the user gets. Accounts are prioritized as follows:

1	 User accounts (highest priority)

2	 Domain groups

3	 Local groups

4	 Well-known groups such as Everyone (lowest priority)

For example, if a 3270 LU called LU1 is assigned to a user account (a high-priority account) called JOHND, and at the same time an LU called LU2 is assigned to a local group (a low-priority account) of which JOHND is a member, JOHND will be given access to LU1, not LU2.


Precedence of Accounts in Determining Default LUs

When user and group account memberships overlap, the highest-priority account that contains a default local APPC LU determines that LU for the user, and the highest-priority account that contains a default remote APPC LU determines that LU for the user. Accounts are prioritized as follows:

1	 User accounts (highest priority)

2	 Domain groups

3	 Local groups

4	 Well-known groups such as Everyone (lowest priority)

For example, suppose a user account (a high-priority account) called JOHND contains LOCLU1 as the default local APPC LU, but no default remote APPC LU. At the same time, suppose a local group (a low-priority account) of which JOHND is a member contains LOCLU2 as the default local APPC LU, and REMLU2 as the default remote APPC LU. For JOHND, the high-priority assignment, a default local APPC LU of LOCLU1, will be combined with the only other available assignment, a default remote APPC LU of REMLU2.


Server Resources Planning Form

Server Name:__________________________________________________

Comment:____________________________________________________

Installed adapters:

_______________________________________________________________

_______________________________________________________________

_______________________________________________________________

Connections:

____________________  ____________________  ___________________

____________________  ____________________  ___________________

____________________  ____________________  ___________________

Remote system(s) to connect to:

_____________________________ [  ] Host  [  ] Peer [  ] Downstream

_____________________________ [  ] Host  [  ] Peer [  ] Downstream

_____________________________ [  ] Host  [  ] Peer [  ] Downstream

_____________________________ [  ] Host  [  ] Peer [  ] Downstream

_____________________________ [  ] Host  [  ] Peer [  ] Downstream


Server Information Form

Server Name:_______________   Server location:_____________

Manufacturer:________________ Type: [  ]Intel [  ]MIPS [  ]Alpha

Machine model:_______ RAM (megabytes):______  Speed:_________

Net adapter: Manufacturer:_______________ Model:_______________

Adapter Manufacturer    Model       Interrupt

____________________    ______      __________

____________________    ______      __________

____________________    ______      __________

IRQ (interrupt)	Common usage	Usage on this server
3	COM2	_________________________
4	COM1	_________________________
5	LPT2 or network	_________________________
6	Disk controller	_________________________
7	LPT1 or SCSI adapter	_________________________

UPS:[  ]Yes ( __COM1 __COM2 )   [  ]No

Network and version:

[  ] Microsoft networking (named pipes)   [  ]TCP/IP

[  ] NetWare, version______   [  ] Banyan VINES, version______

[  ] AppleTalk

Transport:

[ ]NetBEUI  [ ]TCP/IP  [ ]IPX/SPX  [ ]DECnet  [ ]RAS  [ ]Other

Role: Domain: [  ]Primary controller  [  ]Backup controller

              [  ]Server

      Replication:  [  ] Export   [  ] Import  [  ] Both

      SNA server:   [  ] Primary  [  ] Backup  [  ] Member

Supports network installation: [  ]Yes [  ] No


Initial Connection Settings Form

Server Name:_______________ Connection Name:________________

Comment:______________________________________________________

Link Service:__________________

Remote End:[  ] Host System

           [  ] Peer System

           [  ] Downstream

Activation:          [  ] On Server Startup

                     [  ] On Demand

                     [  ] By Administrator

Allowed Directions:  [  ] Outgoing Calls

                     [  ] Incoming Calls

Virtual Circuit Type (X.25 only):[  ]Switched  [  ]Permanent


802.2 Settings Form

Server Name:________________ Connection Name:_________________

Basic Settings

Remote Network Address:______________________________________

Local Node ID:   [  __ __ __  ]  [  __ __ __ __ __  ]

Remote Node Name:

  Network Name:_____________________________________________

  Control Point Name:_______________________________________

  Remote Node ID:  [  __ __ __  ]  [  __ __ __ __ __  ]

Conn. Activation: Maximum attempts:_______________________

                  Delay after failed attempts:___________

Advanced Settings

XID Type: [  ] Format 0   [  ] Format 3

Remote SAP Address:____________    Retry Limit:___________

Max BTU Length:_________________   XID Retries:___________

Response (t1) Timeout:   ____________

Receive ACK (t2) Timeout:____________

Inactivity (ti) Timeout: ____________

Receive ACK Threshold:____________________ frames.

Unacknowledged Send Limit:_________________ frames.


SDLC Settings Form

Server Name:________________ Connection Name:_________________

Basic Settings

Dial Data:___________________________________________________

Local Node ID:   [  __ __ __  ]  [  __ __ __ __ __  ]

Remote Node Name:

  Network Name:____________________________________________

  Control Point Name:_______________________________________

  Remote Node ID:  [  __ __ __  ]  [  __ __ __ __ __  ]

Conn. Activation: Maximum attempts:_______________________

                  Delay after failed attempts:___________

Advanced Settings

XID Type:     Encoding:  Duplex:      Data Rate:

[  ] Format 0  [  ] NRZ    [  ] Half     [  ] Low

[  ] Format 3  [  ] NRZI   [  ] Full     [  ] High

Poll Address:____________     Contact Timeout:_______x0.1s

Poll Rate: ____________per s   Contact Retry Limit:_______

Poll Timeout:______x0.1s      Idle Timeout:______x0.1s

Poll Retry Limit:________     Idle Retry Limit:________

Max BTU Length:__________

Multidrop Primary:  [  ] Yes   [  ] No

Select Standby:     [  ] Yes   [  ] No

Switched Connection Establishment Timeout:_______________ s


X.25 Settings Form

Server Name:________________ Connection Name:_________________

Basic Settings

Remote X.25 Address:________________________________________

Local Node ID:   [  __ __ __  ]  [  __ __ __ __ __  ]

Remote Node Name:

  Network Name:____________________________________________

  Control Point Name:_______________________________________

  Remote Node ID:  [  __ __ __  ]  [  __ __ __ __ __  ]

Conn. Activation: Maximum attempts:_______________________

                  Delay after failed attempts:___________

Advanced Settings

XID Type: [  ] Format 0   [  ] Format 3

Max BTU Length:__________

Packet Size (PVC only):______________________________________

Window Size (PVC only):______________________________________

PVC Alias (PVC only):  ______________________________________

Facility Data (SVC only): ____________________________________

User Data (SVC only):     ____________________________________


Channel Settings Form

Server Name:________________ Connection Name:_________________

Basic Settings

Channel Address:________________________________________

Local Node ID:   [  __ __ __  ]  [  __ __ __ __ __  ]

Advanced Settings

XID Type: [  ] Format 0   [  ] Format 3

Max BTU Length:__________


3270 LUs Form (for Individual LUs)

LU Number:__________________  LU Name:_____________________

Connection:_________________  Comment:_____________________

LU type:[  ] Display  Display Model:[  ] 2 (24x80)

        [  ] Printer                [  ] 3 (32x80)

                                    [  ] 4 (43x80)

                                    [  ] 5 (27x132)

          Model can be overridden: [  ] Yes [  ] No

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

LU Number:__________________  LU Name:_____________________

Connection:_________________  Comment:_____________________

LU type:[  ] Display  Display Model:[  ] 2 (24x80)

        [  ] Printer                [  ] 3 (32x80)

                                    [  ] 4 (43x80)

                                    [  ] 5 (27x132)

          Model can be overridden: [  ] Yes [  ] No

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

LU Number:__________________  LU Name:_____________________

Connection:_________________  Comment:_____________________

LU type:[  ] Display  Display Model:[  ] 2 (24x80)

        [  ] Printer                [  ] 3 (32x80)

                                    [  ] 4 (43x80)

                                    [  ] 5 (27x132)

          Model can be overridden: [  ] Yes [  ] No


3270 LUs Form (for Ranges of LUs)

Connection: _____________________________________________

Base LU Name:   _________________________________________

First LU Number:_________________________________________

Number of LUs:  _________________________________________

LU Numbers:_______________________________________________

LU Names:  _______________________________________________

Comment:   _______________________________________________

LU type:[  ] Display  Display Model:[  ] 2 (24x80)

        [  ] Printer                [  ] 3 (32x80)

                                    [  ] 4 (43x80)

                                    [  ] 5 (27x132)

          Model can be overridden: [  ] Yes [  ] No


3270 LU Pools (Form)
3270 LU Pools Form

Pool Name:________________  Comment:  ______________________

            Display Model: [  ] 2 (24x80)

                           [  ] 3 (32x80)

                           [  ] 4 (43x80)

                           [  ] 5 (27x132)

Model can be overridden:   [  ] Yes [  ] No

LUs in Pool:

   _______________  ______________  _______________  _____________

   _______________  ______________  _______________  _____________

   _______________  ______________  _______________  _____________

   _______________  ______________  _______________  _____________

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Pool Name:________________  Comment:  ______________________

            Display Model: [  ] 2 (24x80)

                           [  ] 3 (32x80)

                           [  ] 4 (43x80)

                           [  ] 5 (27x132)

Model can be overridden:   [  ] Yes [  ] No

LUs in Pool:

   _______________  ______________  _______________  _____________

   _______________  ______________  _______________  _____________

   _______________  ______________  _______________  _____________

   _______________  ______________  _______________  _____________


Remote APPC LUs Form

Connection:___________________________________________________

LU Alias:________________ LU Name:___________________________

Network Name:____________ Uninterpreted LU Name:______________

Comment:______________________________________________________

Supports Parallel Sessions:  [  ] Yes  [  ] No

Enable Automatic Partnering: [  ] Yes  [  ] No

Implicit Incoming Mode:________________________________________

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Connection:___________________________________________________

LU Alias:________________ LU Name:___________________________

Network Name:____________ Uninterpreted LU Name:______________

Comment:______________________________________________________

Supports Parallel Sessions:  [  ] Yes  [  ] No

Enable Automatic Partnering: [  ] Yes  [  ] No

Implicit Incoming Mode:________________________________________


Local APPC LUs Form

Server:_________  LU 6.2 Type: [  ]Independent  [  ]Dependent

LU Alias:___________________________________________________

Network Name:_______________________________________________

LU Name:_____________________________________________________

LU Number (Dependent only):__________________________________

Comment:_____________________________________________________

Enable Automatic Partnering: [  ]Yes   [  ]No

Member of Default Outgoing

Local APPC LU Pool:          [  ]Yes   [  ] No

Implicit Incoming Remote LU:__________________________

Timeout for Starting Invokable TPs:_____________s

Partner LUs:______________  ______________  ______________

            ______________  ______________  ______________

            ______________  ______________  ______________


Mode Properties for LU-LU Pairs Form

Mode Name:________________________________________________

Comment:_________________________________________________

LU-LU pairs that will use this mode:

Local                    Remote

_____________            _____________

_____________            _____________

_____________            _____________

_____________            _____________

Parallel Session Limit:_________________________________

Minimum Contention Winner Limit:_______________________

Partner Min Contention Winner Limit:___________________

Automatic Activation Limit:_____________________________

Enable Automatic Partnering:[  ] Yes    [  ] No

High Priority Mode:         [  ] Yes    [  ] No

Pacing Send Count:________ Max Send RU Size:____________

Pacing Receive Count:_____ Max Receive RU Size:________


CPI-C Properties Form

Name:_______________________  Comment:______________________

Partner TP Name

Application TP:_____________________________________________

OR

SNA Service TP ( in hex ):_________________________________

Partner LU Name

Alias:________________________________________________________

OR

Fully Qualified:_____________________________________________

Conversation Security:None   [  ]

                      Same   [  ]

                      Program[  ]

                      User ID___________________________

                      Password__________________________

Mode Name:_______________________________________________


Users and Groups Form

User or Group Name:____________________________________

Domain:__________________________________________________

Comment:_________________________________________________

3270 LUs:__________  ___________  ___________  ___________

         __________  ___________  ___________  ___________

Default Local APPC LU:______________________________________

Default Remote APPC LU:_____________________________________

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

User or Group Name:____________________________________

Domain:__________________________________________________

Comment:_________________________________________________

3270 LUs:__________  ___________  ___________  ___________

         __________  ___________  ___________  ___________

Default Local APPC LU:______________________________________

Default Remote APPC LU:_____________________________________


RTM Settings Form

RTM Data Sent at:[  ]Counter Overflow   [  ]End of Session

RTM Timers Run Until:

    [  ] First Data Reaches Screen

    [  ] Host Unlocks Keyboard

    [  ] Host Lets User Send

RTM Thresholds

Threshold #1:_________x0.1s   Threshold #3:_________x0.1s

Threshold #2:_________x0.1s   Threshold #4:_________x0.1s


Definitions

3270

3270 emulator

3270 terminal emulation

5250 emulator

5250 terminal emulation

802.2

-A-

ACTLU

ACTPU

adapter

administration access

Advanced Program-to-Program Communications (APPC)

alert

allocate

API

APPC

application programming interface (API)

application TP

ASCII

auditing

automatic partnering

-B-

backup configuration file

backup SNA server

basic transmission unit (BTU)

BTU

-C-

Channel

CICS or CICS/VS

click

client

coaxial cable

Common Programming Interface for Communications (CPI-C)

Common Service Verbs (CSVs)

communications controller

configuration file

connection

connectivity option

contention loser

contention winner

control point

Control Point Name

controller

conventional Logical Unit Application (LUA) programming interface

conversation

CPI-C

CSVs

Customer Information Control System (CICS)

Customer Information Control System for Virtual Storage (CICS/VS)

-D-

DACTLU

DACTPU

data link control (DLC)

deallocate

default

dependent local APPC LU

DFT

display emulation

display model

display session

DISPLAY verb

distributed function terminal (DFT)

DLC

DLL

double-click

downstream connection

downstream LU

downstream system

duplex

dynamic-link library (DLL)

-E-

emulation

environment variables

Ethernet

event log

Exchange Identification (XID)

-F-

file transfer

Format 0 XID

Format 3 XID

full-duplex

full-duplex transmission

-H-

half-duplex

half-duplex transmission

High-Level Language Application Programming Interface (HLLAPI)

HLLAPI

host-addressable printer

host response time

host system

hot backup

-I-

I-frame

IEEE

implicit incoming mode

implicit incoming remote LU

IND$FILE

independent local APPC LU

information frame (I-frame)

Institute of Electrical and Electronics Engineers (IEEE)

invokable

invokable TP

invoking TP

IP routed network

IPX/SPX

-L-

LAN

leased SDLC line

link service

load balancing

local area network (LAN)

local LU

local node

local printer

local TP

logical unit (LU)

Logical Unit Application (LUA)

LU

LU Alias

LU Name

LU pool

LU type

LU type 0

LU type 1

LU type 2

LU type 3

LU type 6.2

LUA

LU-LU session

-M-

MAC address

media access control (MAC) address

member SNA server

mode

Mode Name

model

modem

modem eliminator

modem-stored phone number

mouse

multidrop

-N-

NCP

negotiable link role

NetView

NetView alert

NetView user alert

NetWare

network

Network Control Program (NCP)

Network Name

node

node type 2.1

-O-

offline configuration file

operator-loaded TP

-P-

pacing receive count

pacing send count

packet

packet switching

parallel sessions

parameter

partner LUs

partner LU alias

partner LU name

partner TPs

path

PC Support

peer system

peer-to-peer

Performance Monitor

permanent virtual circuit (PVC)

permissions

physical unit (PU)

primary link role

primary SNA server

printer emulation

printer session

PU

PU 2.0

PU 2.1

PVC

-Q-

QLLC

qualified logical link control (QLLC)

queued TP

-R-

Registry variables

remote LU

Remote Network Address

remote node

Remote Node ID

remote TP

Remote X.25 Address

request unit (RU)

Response Time Monitor (RTM)

response unit (RU)

RTM

RU

-S-

SAA

SAP address

SDLC

secondary link role

security key

security log

server

service access point (SAP) address

service TP

session

session limit

Setup program

severity level

single session

SNA

SNA Server

SSCP

SVC

switched SDLC line

switched virtual circuit (SVC)

symbolic destination name

Synchronous Data Link Control (SDLC)

synchronous transmission

system administrator

system services control point (SSCP)

Systems Application Architecture (SAA)

Systems Network Architecture (SNA)

-T-

TCP/IP

terminal

token ring

TP

trace file

tracing

transaction

transaction program (TP)

Twinax

twisted-pair cable

-U-

Uninterpreted LU Name

user alert

-V-

VINES

Virtual Telecommunications Access Method (VTAM)

VTAM

-W-

WAN

Wide area network (WAN)

-X-

X.25

XID


3270

The information display system for IBM hosts (mainframes); the system includes terminals, printers, and controllers that allow a user to access host functions.


3270 emulator

Software that allows a microcomputer to act as a 3270 terminal, displaying information from a host system (mainframe). Emulator software can also allow a desktop computer to send print jobs from a host system to a printer connected to the microcomputer.


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.


5250 emulator

Software that allows a microcomputer to act as a 5250 terminal interacting with an AS/400 system.


5250 terminal emulation

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


  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.


ACTLU

SNA command sent by the system services control point (SSCP) to a logical unit (LU) to activate a session and establish session parameters.


ACTPU

SNA command sent by the system services control point (SSCP) to activate a physical unit (PU), so that any logical units (LUs) controlled by this PU are available to the SNA network.


adapter

Circuit card added to a PC to allow it to perform a specialized function, such as accessing a monitor or communications line.


administration access

The level of access allowed to a user attempting to use SNA Server interfaces (SNA Server Setup, SNA Server Admin, or the snacfg command). The user may be granted or denied the ability to use the interfaces to read and change the configuration file, to start and stop servers and connections, or to reset LUs.


alert

A message sent to indicate an abnormal event or a failure.


allocate

(1) The process an operating system uses to respond to a request from a program to reserve memory for use by the program. (2) In Advanced Program-to-Program Communications (APPC), a verb that assigns a session to a conversation. Contrast with deallocate.


API

Application programming interface. A programming language interface that provides information and services to application programs. APIs allow users to write their own programs for use with a specific product or in a specific environment.


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 used for 5250 terminal emulation.


application TP

An application program that uses Advanced Program-to-Program Communications (APPC) to accomplish tasks for end users and exchange data with other transaction programs (TPs) in an SNA environment. For information about TPs, see the Microsoft SNA Server Administration Guide, the Microsoft SNA Server APPC Programmer's Guide, and the Microsoft SNA Server CPI-C Programmer's Guide. See also service TP and TP.


application TP

An application program that uses Advanced Program-to-Program Communications (APPC) to accomplish tasks for end users and exchange data with other transaction programs (TPs) in an SNA environment. For information about TPs, see the Microsoft SNA Server Administration Guide, the Microsoft SNA Server APPC Programmer's Guide, and the Microsoft SNA Server CPI-C Programmer's Guide.


ASCII

American Standard Code for Information Interchange.


auditing

Tracking the activities of administrators and users by recording selected types of events (for example, the changing of the configuration file) in the security log of an SNA server or other Windows NT-based computer.


automatic partnering

A setting for APPC LUs and modes that allows LU-LU pairs (with assigned modes) to be generated automatically by SNA Server. Each time a new APPC LU or mode is created with automatic partnering enabled, SNA Server searches for existing LUs and modes that also have automatic partnering enabled. SNA Server then uses all available automatic partners to create as many unique LU-LU pairs as possible, each pair containing a remote LU, local LU, and assigned mode. Disabling an automatic partner setting after an LU or mode has been created does not remove that LU or mode from LU-LU pairs already generated.


backup configuration file

An extra copy of the configuration file, saved by using the File menu Backup command in SNA Server Admin. The default extension for backup configuration filenames is .SNA.


backup SNA server

An SNA server on which the configuration file is replicated by SNA Server. SNA Server will load the copy of the configuration file located on a backup SNA server if the primary SNA server goes down. One or more SNA servers can operate as backup SNA servers. Backup SNA servers are designated by using SNA Server Setup.

The other types of SNA servers are the primary SNA server and member SNA servers.


BTU

Basic transmission unit. A standard unit of information transmitted over an SNA network. A BTU consists of the transmission header (TH), the request/response header (RH), and the request/response unit (RU). The maximum size of the BTU is controlled in VTAM by the MAXDATA= parameter and in SNA Server by the Max BTU Length parameter.


 Channel

A channel-attached connection to a host system.


CICS or CICS/VS

Customer Information Control System or Customer Information Control System/Virtual Storage. An IBM transaction processing program that provides an environment on IBM mainframes in which applications can communicate with terminals or other applications.


click

To press and release the mouse button, thereby selecting an item. See also double-click.


client

A computer using services available through an SNA server. While running applications such as a 3270 emulator, the client uses the SNA server to access host or peer systems on the SNA network.


coaxial cable

A cable that consists of a conductor within another conductor, with insulation between the two conductors. The inner conductor is usually a small copper tube or wire, and the outer conductor is usually copper tubing or copper braid. It is the common medium used to connect LANs and 3270 devices. The maximum distance that a coaxial cable can be run between a 3270-type cluster controller and peripheral devices is 5,000 feet (1,500 meters).


CPI-C

Common Programming Interface for Communications. A set of C-language routines that applications distributed across an SNA network can use to work together. Through CPI-C, distributed applications on computers communicating as peers can exchange data in order to accomplish a processing task, such as querying a remote database or copying a remote file.


communications controller

A device that directs the transmission of data over a network (for example, the IBM 3725 front-end processor).


configuration file

A file containing setup and configuration information for SNA Server. The configuration file defines servers, connections, logical units (LUs), users, and other items. The configuration file that is loaded when SNA Server Admin starts is called COM.CFG.


connection

The data communication path between a workstation or server and other computers on the SNA network. SNA Server offers a variety of connection types:

 	802.2 (token ring or Ethernet)

Synchronous Data Link Control (SDLC)

X.25

Distributed function terminal (DFT)

Channel

Twinax


connectivity option

A type of connection hardware and software through which one computer communicates with other computers.


contention loser

In an APPC LU-LU session, the LU that cannot start a conversation with its partner LU (the contention winner) without first requesting permission of the partner LU. See also contention winner.


contention winner

In an APPC LU-LU session, the LU that can start a conversation with its partner LU (the contention loser). If parallel sessions between the two LUs are being used, each LU may be the contention winner for some sessions and the contention loser for other sessions. See also contention loser.


contention winner

In an APPC LU-LU session, the LU that can start a conversation with its partner LU (the contention loser). If parallel sessions between the two LUs are being used, each LU may be the contention winner for some sessions and the contention loser for other sessions.


control point

A node or other SNA component that controls network resources and coordinates the activation of sessions.


controller

A device that directs the transmission of data over a network (for example, the IBM 3725 front-end processor).


conversation

The process used by network-based applications to communicate with each other and to exchange data in order to accomplish processing tasks.


CSVs

Common Service Verbs. An application programming interface that provides ways of tracing, translating characters, and sending network management information to a host.


DACTLU

An SNA command that is sent to deactivate the session between the system services control point (SSCP) and a logical unit (LU).


DACTPU

An SNA command that is sent to deactivate the session between the system services control point (SSCP) and a physical unit (PU).


deallocate

(1) The process an operating system uses to free memory that has been previously allocated by a program. (2) In Advanced Program-to-Program Communications (APPC), a verb that ends a conversation. Contrast with allocate.


default

The value that is automatically used if nothing is specified.


dependent local APPC LU

A local logical unit (LU) that allows Advanced Program-to-Program Communications (APPC) with a peer system, but only via a host (mainframe) system. The type of LU used in dependent APPC is LU 6.2.


 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.


display emulation

A feature that allows a PC to emulate an IBM 3278 or 3279 terminal. See also emulation.


display model

One of several different sizes of display:

Model 2 is 24 lines by 80 characters.

Model 3 is 32 lines by 80 characters.

Model 4 is 43 lines by 80 characters.

Model 5 is 27 lines by 132 characters.


display session

A 3270 emulation session between a network PC and a host. The session is used to emulate a 3278 or 3279 display. Also called a host display session.


DISPLAY verb

An Advanced Program-to-Program Communications (APPC) verb that returns configuration information and current operating values for an SNA server.


DLC

Data link control. In SNA, the protocol stack layer that transmits messages across links and manages link-level flow and error recovery.


DLL

Dynamic-link library. An operating-system mechanism that automatically links executable code to an application program.


double-click

To rapidly press and release the mouse button twice, initiating an action on the selected item.


downstream connection

A connection that allows an SNA server to support communication between hosts and clients such as IBM Communications Manager/2 systems. Even though such clients do not use the SNA Server client/server interface, with a downstream connection, they can access host connections available through an SNA server.

SNA Server offers several types of downstream connection:

 	802.2 (token ring or Ethernet)

SDLC

X.25


 downstream LU

A logical unit (LU) used by clients such as IBM Communications Manager/2 systems in order to access a host connection via an SNA server. Such clients do not use the SNA Server client/server interface, but by using a downstream LU, can receive access to connections on an SNA server.

A downstream LU uses a downstream connection, and passes information between the client and the host.


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.


duplex

Capable of simultaneously transmitting and receiving data. Also called full-duplex or 4-wire. Contrast with half-duplex.


emulation

A process whereby one device imitates another; for example, a PC can emulate a 3278 terminal. See also display emulation.


environment variables

MS-DOS or OS/2 variables that start and stop tracing and that define the environment needed to run a particular transaction program (TP).


Ethernet

A type of LAN using the 802.3 or DIX version 2.0 protocol, in which any computer can transmit at any time, but must sense for possible collisions when transmitting. On an Ethernet network, computers are linked with coaxial cable or with twisted-pair wiring.


event log

The location in which SNA Server records events involving communications hardware (for example, communications adapters) or SNA Server software. Events may include attempts to establish communication, successful establishment of sessions, failures of system components, attempts to use files that are damaged or missing, configuration problems, and responses from remote systems. Use the Windows NT Event Viewer to view event logs. Event logs differ from security logs, which record actions related to security, such as writing to the SNA Server configuration file.


file transfer

The process of sending and receiving data files to and from computers.


Format 0 XID

A type of XID that supplies minimal information about the node. Format 0 XIDs have a fixed length. They can be used for 3270 and LUA communication, and cannot be used for Advanced Program-to-Program Communications (APPC). See also Format 3 XID and XID.


Format 3 XID

A type of XID that supplies more detailed information about the node than a Format 0 XID. Format 3 XIDs have a variable length. They can be used for 3270 and LUA communication, and are the only type of XID that can be used for Advanced Program-to-Program Communications (APPC). See also Format 0 XID and XID.


Format 3 XID

A type of XID that supplies more detailed information about the node than a Format 0 XID. Format 3 XIDs have a variable length. They can be used for 3270 and LUA communication, and are the only type of XID that can be used for Advanced Program-to-Program Communications (APPC).


full-duplex

Capable of simultaneously transmitting and receiving data. Also called duplex or 4-wire. Contrast with half-duplex.


full-duplex

Capable of simultaneously transmitting and receiving data. Also called duplex or 4-wire.


full-duplex transmission

Two-way electronic communication that takes place in both directions simultaneously. Also called duplex transmission or 4-wire transmission. Contrast with half-duplex transmission.


half-duplex

Capable of only one direction of communication at a time, either receiving data or transmitting data, but not doing both at the same time. Also called 2-wire. Contrast with full-duplex.


half-duplex

Capable of only one direction of communication at a time, either receiving data or transmitting data, but not doing both at the same time. Also called 2-wire.


half-duplex transmission

Two-way electronic communication that takes place in only one direction at a time. Also called 2-wire transmission. Contrast with full-duplex transmission.


HLLAPI

High-Level Language Application Programming Interface. An API that allows you to develop and run programmer-operator applications on IBM PCs (or compatibles) that communicate with IBM mainframes using 3270 emulation.


host system

A computer system, usually a mainframe, that controls interactions between it and PCs connecting to it. A host system makes its operating system and applications available via SNA Server to PCs running software for terminal emulation or for Advanced Program-to-Program Communications (APPC).

In SNA terminology, a host is capable of sending an ACTPU command to SNA Server, and will set up a PU-SSCP session with SNA Server.

Host system is the type of remote end to specify for connections that will be used for 3270 communications, LUA communications, or for dependent APPC.


host response time

The amount of time a host computer takes to reply to a message sent to it by a PC. It is measured from the moment that the PC sends the message until one of the following events: the PC receives data back from the host, the host unlocks the PC keyboard, or the host allows the PC to send more data.


host-addressable printer

A printer that is defined as a device associated with a logical unit (LU) configured as LU type 1 or 3 and that can support host printing as well as local printing.


hot backup

A configuration in which one resource (such as an SNA server) can automatically handle sessions if another cannot. SNA servers can provide hot backup for 3270, LUA, or downstream sessions through pools containing LUs from multiple servers. SNA servers can provide hot backup for 5250 terminal emulation through the use of LU names that are the same on multiple servers.


IEEE

Institute of Electrical and Electronics Engineers. An organization that maintains the standards for the 802.2 protocol used in communications on a token-ring LAN.


I-frame

Information frame. A standard unit of information transmitted over an SNA network. For 802.2 or SDLC communication, an I-frame is equivalent to a BTU. See also BTU.


implicit incoming mode

A mode that defines the properties to use when SNA Server receives a request to start a session, and the mode named in the request is not recognized by SNA Server. An implicit incoming mode allows greater flexibility in starting sessions with remote systems.

In order for a session to be established, the incoming local LU name must be recognized by SNA Server. Then the incoming remote LU must either be recognized explicitly or handled implicitly (if an implicit incoming remote LU has been configured). If the remote LU is recognized explicitly, but the mode is not recognized (as part of an LU-LU pair), SNA Server internally creates a new mode definition with the correct name, using the properties of the implicit incoming mode. Alternatively, if the remote LU is handled implicitly, SNA Server also handles the mode implicitly, by internally creating a mode, as described.

Note that an implicit incoming mode must be configured for any remote LU that will be used as an implicit incoming remote LU. An implicit incoming mode can be (but does not have to be) configured for remote LUs that will only be used explicitly.


implicit incoming remote LU

A remote APPC LU that defines the properties to use when SNA Server receives a request to start a session with a local LU, and the remote LU named in the request is not recognized by SNA Server. An implicit incoming remote LU allows greater flexibility in starting sessions with remote systems.

Note that in order for a session to be established, the local LU name must be recognized by SNA Server. If the local LU name is recognized, but the remote LU name is not recognized as a partner for the local LU, SNA Server internally creates a new remote LU definition with the correct name, using the properties of the implicit incoming remote LU.

In SNA Server Admin, before a remote APPC LU can be used as an implicit incoming remote LU, an implicit incoming mode must be configured for it.


independent local APPC LU

A local logical unit (LU) that allows Advanced Program-to-Program Communications (APPC) with a peer system without involving a host (mainframe) system. The type of LU used in independent APPC is LU 6.2. An independent LU does not require a host system, but can work through one.


IND$FILE

IBM's file transfer program that allows files to be transferred from a PC to the host and vice versa. It operates in three host environments: CICS, VM/CMS, and MVS/TSO.


invokable

Capability of a program to be started by another program. For example, an invokable APPC transaction program (TP) can be started in response to a request from another TP (the invoking TP).

For information about TPs, see the Microsoft SNA Server Administration Guide, the Microsoft SNA Server APPC Programmer's Guide, and the Microsoft SNA Server CPI-C Programmer's Guide.


invokable TP

A transaction program (TP) that can be activated by another (invoking) TP. The invokable TP is activated by an ALLOCATE verb sent to it by the invoking TP.

For information about TPs, see the Microsoft SNA Server Administration Guide, the Microsoft SNA Server APPC Programmer's Guide, and the Microsoft SNA Server CPI-C Programmer's Guide.


invoking TP

A transaction program (TP) that activates another TP. The invoking TP activates the other TP by sending an ALLOCATE verb via the SNA network.

For information about TPs, see the Microsoft SNA Server Administration Guide, the Microsoft SNA Server APPC Programmer's Guide, and the Microsoft SNA Server CPI-C Programmer's Guide.


IP routed network

Internet Protocol routed network. A TCP/IP wide area network in which IP packets are propagated across the network through devices called IP routers.


IPX/SPX

Internetwork Packet Exchange/Sequenced Packet Exchange. A set of protocols used by Novell NetWare networking software for communication across a network.


LAN

Local area network. A high-speed communication system consisting of hardware (computers and peripherals) and software (programs and data files) that are interconnected by cable in a way that allows these resources to be shared. The connected devices are located within a limited geographic area such as a building or campus.


leased SDLC line

A dedicated telecommunications line using SDLC. See also SDLC.


leased SDLC line

A dedicated telecommunications line using SDLC.


link service

The software component of SNA Server that communicates with the device driver for a particular communication adapter (802.2, SDLC, X.25, DFT, Channel, or Twinax).

In order for a link service to be available through SNA Server Admin, it must first be installed with the SNA Server Setup program.


load balancing

Distribution of the processing load between several servers carrying out network tasks, to increase overall network performance. SNA servers can provide automatic load balancing for 3270, LUA, or downstream communications through pools containing LUs from multiple servers. SNA servers can provide automatic load balancing for 5250 terminal emulation through the use of LU names that are the same on multiple servers.


local LU

In an Advanced Program-to-Program Communications (APPC) or Common Programming Interface for Communications (CPI-C) conversation, the logical unit (LU) on the local end. Contrast with partner LU and remote LU.


local node

The software component of SNA Server that interacts with clients and other nodes on the SNA network.


local printer

A printer that is attached directly to a PC.


local TP

In an Advanced Program-to-Program Communications (APPC) or Common Programming Interface for Communications (CPI-C) conversation, the transaction program (TP) on the local end. Contrast with partner TP and remote TP. See also local LU.

For information about TPs, see the Microsoft SNA Server Administration Guide, the Microsoft SNA Server APPC Programmer's Guide, and the Microsoft SNA Server CPI-C Programmer's Guide.


LU

Logical unit. A preset unit containing configuration information needed for a user, program, or downstream system to establish a session with a host or peer computer. SNA Server offers several types of LUs:

 	3270 LUs, used for 3270 terminal emulation

LUs of type LU 6.2, used for Advanced Program-to-Program Communications (APPC), including 5250 emulation

LUA LUs, used with programs written for the LUA interface

Downstream LUs, used to allow downstream systems to connect to a host via an SNA server


LU Name

A name identifying an LU. The name can be from one through eight characters long and can contain alphanumeric characters and the special characters $, #, and @. Lowercase letters are converted to uppercase.

For independent APPC, the LU Name identifies the LU to other components on the SNA network. For dependent APPC, the LU Name identifies the LU to local software, such as the Windows NT event log software. The LU Name and LU Alias for an APPC LU can match each other, or differ.


LU pool

A number of logical units (LUs), all of the same kind, that are made available as a group. A user, LUA application, or downstream system using the pool can get LU access as long as one of the pooled LUs is available. This provides for better access for multiple users, applications, or downstream systems in an SNA installation. SNA Server offers several types of LU pools:

3270 LU pools

LUA LU pools

Downstream LU pools


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.


LU-LU session

A logical, two-way exchange between two logical units (LUs) over a specific connection for a specific amount of time.


LU type

Logical unit type. A subset of the SNA protocol that characterizes the communication between two LUs.


LU type 0

A logical-unit protocol with minimal constraints, on which special applications can be built for SNA.


LU type 1

A logical-unit protocol used by a host application communicating with a printer, sending data that conforms to the 3270 SNA Character String (SCS) definition.


LU type 2

A logical-unit protocol used by a host application communicating with a 3270-type display terminal, using the SNA 3270 data stream.


LU type 3

A logical-unit protocol used by a host application communicating with a printer, sending data that is 3270 data stream compatible (DSC).


LU type 6.2

A logical-unit protocol used by two applications or transaction programs (TPs) communicating as peers in an SNA environment. LU 6.2 works in combination with node type 2.1 to provide Advanced Program-to-Program Communications (APPC) using independent LUs. LU 6.2 also works with node type 2.0 to provide APPC with dependent LUs.


MAC address

Media access control address. A 12-digit hexadecimal address used by the media access control layer of an 802.2 connection. The MAC address corresponds to the VTAM MACADDR= parameter and to the Remote Network Address parameter for an 802.2 connection with SNA Server.


member SNA server

An SNA server that does not contain a configuration file. One or more SNA servers can operate as member servers. The other types of SNA servers are the primary SNA server and backup SNA servers.


mode

A collection of session properties used by LU 6.2-type logical units (LUs) as they carry on a session. A mode can be used by many LU pairs at the same time.


model

One of several different sizes of display:

Model 2 is 24 lines by 80 characters.

Model 3 is 32 lines by 80 characters.

Model 4 is 43 lines by 80 characters.

Model 5 is 27 lines by 132 characters.


modem

Short for modulator/demodulator. Device that enables computers to communicate over standard telephone lines by converting analog signals to digital signals and digital signals to analog signals.


modem eliminator

A device that connects two PCs through their serial communication ports, eliminating the need for a modem. Also called a crossover cable.


modem-stored phone number

A dialing method in which a phone number is stored on a modem itself and dialed when needed. Contrast this with the method in which SNA Server stores a phone number and sends it to the modem.


mouse

A pointing device attached to a PC; used to make choices or to position the cursor on a display.


multidrop

A connection in which one primary node communicates with multiple secondary nodes concurrently over the same physical transmission medium.


negotiable link role

A role in which the SNA server negotiates with a remote system at the beginning of a session, to determine which system will control the communications. The SNA server takes a negotiable link role in connections with peer systems. See also primary link role and secondary link role.


NCP

Network Control Program. An IBM program that supports communication controllers in single-domain, multiple-domain, and interconnected networks.


NetView

A reporting system that runs on an IBM host (mainframe), forwarding alerts and other information back and forth between the host and PCs and other network addressable units that connect to the host.


NetView alert

A message sent to the NetView reporting system, indicating an abnormal event or a failure.


NetView user alert

A message sent by a 3270 user to a host system operator via NetView, requesting an action such as mounting a tape or changing forms on a printer. Also called user alert.


NetWare

A collection of networking software products from Novell, Inc.


network

Computer systems, controllers, terminals, and software connected in a way that allows them to communicate with each other.


node

A server, controller, workstation, printer, or other processor that implements SNA functions.

SNA defines three kinds of nodes: the host subarea node, which functions to control and manage a network; the communication controller subarea node, which routes and controls data flow through the network; and peripheral nodes, which include printers, workstations, cluster controllers, and distributed processors.


node type 2.1

An SNA component, such as an intelligent terminal or a PC, that works together with LU type 6.2 to support peer-to-peer communications, allowing the logical units (LUs) to function independently from the host.


offline configuration file

An SNA configuration file that is created or modified at one site and used at another site. With the offline version of SNA Server Admin, you can create, view, or modify an offline configuration file, independent of the local running configuration. This is possible because the offline version of SNA Server Admin displays offline configurations but does not load them as the local running configuration.


operator-loaded TP

An invokable transaction program (TP) that is manually loaded and started by an operator.

For information about TPs, see the Microsoft SNA Server Administration Guide, the Microsoft SNA Server APPC Programmer's Guide, and the Microsoft SNA Server CPI-C Programmer's Guide.


pacing receive count

The maximum number of frames for the local logical unit (LU) to receive from the partner LU before the local LU sends a response.


pacing send count

The maximum number of frames for the local logical unit (LU) to send without receiving an SNA pacing response from the partner LU.


packet

A transmission unit of fixed maximum size, used as the basic unit on a packet-switching network. A packet contains both a header and data.


packet switching

A message-delivery technique in which small units of information (packets) are relayed through stations in a computer network along the best route currently available between the source and the destination. Packet-switching networks are considered to be fast and efficient. The protocol used on packet-switching networks is X.25. See also X.25.


parallel sessions

Multiple concurrent sessions between a pair of LU 6.2-type logical units (LUs), allowing multiple operations to be performed simultaneously.


parameter

A variable used as input to a program, operating system, or API to govern how systems, programs, or functions perform.


partner LU alias

A name that identifies a partner logical unit (LU) to partner transaction programs (TPs).


partner LU name

A name that identifies a partner logical unit (LU) to other LUs on the LU 6.2 session.


partner LUs

Two logical units (LUs) that are configured to communicate with each other. Partner LUs can reside on the same or different nodes.


partner TPs

Two transaction programs (TPs), residing on the same or separate nodes, that are configured to communicate with each other. Partner TPs use partner LUs.

For information about TPs, see the Microsoft SNA Server Administration Guide, the Microsoft SNA Server APPC Programmer's Guide, and the Microsoft SNA Server CPI-C Programmer's Guide.


path

(1) In SNA, the series of nodes and communications links over which data must travel from one logical unit (LU) to another. (2) A sequence of directories that identify the location of a file.


PC Support

A set of IBM programs that helps PC users access, share, and store information on an AS/400.


peer system

A mainframe, mini, or PC that communicates with another computer as an equal partner, with both computers sharing control over the communication.


peer-to-peer

A type of communication in which two systems communicate as equal partners sharing the processing and control of the exchange, as opposed to host-terminal communication in which the host does most of the processing and controls the exchange.


Performance Monitor

A graphical tool included in Windows NT. The Performance Monitor allows you to measure the performance of your computer or other computers on the network.


PVC

Permanent virtual circuit. A type of circuit used by an X.25 connection, in which the circuit is constantly active, and the destination address is preset.


permissions

Settings that grant or deny a particular kind of access to a particular file, directory, or other object. For example, granting read permission but denying write permission for FILE1.EXT for Domain Admins means that members of this group can read, but not change, FILE1.EXT.


primary link role

The role taken by the system that controls communication in an SNA session. The SNA server takes the primary link role in connections with downstream systems, and also when the SNA server is the primary station for a multidrop connection. See also negotiable link role and secondary link role.


primary SNA server

The SNA server designated to contain the primary configuration file. There can be only one primary SNA server in the domain. The primary SNA server is designated by using SNA Server Setup.

The other types of SNA servers are backup SNA servers and member SNA servers.


printer emulation

The ability of a PC-type printer to emulate a 3287 or 4224 printer to print host data.


printer session

A 3270 emulation session between a host and a local area network printer connected to a PC. The printer emulates the type of printer normally used by a host system.


PU

Physical unit. A network-addressable unit that provides the services needed to use and manage a particular device, such as a communications link device. A PU is implemented with a combination of hardware, software, and microcode.


PU 2.0

In an SNA network, the component that defines controller and terminal-type resources similar to an IBM 3274 Control Unit.


PU 2.1

In an SNA network, a component such as an intelligent terminal or a PC that works together with LU type 6.2 to support peer-to-peer communications, allowing the logical units (LUs) to function independently from the host.


QLLC

Qualified logical link control. A protocol that permits SNA sessions to occur over X.25 networks.


queued TP

An invokable transaction program (TP) that can be started by only one incoming allocate command at a time. Incoming allocate commands that arrive while the queued TP is running do not start the program again, but are queued until the program issues another RECEIVE_ALLOCATE or until it finishes execution.

For more information about TPs, see the Microsoft SNA Server Administration Guide, the Microsoft SNA Server APPC Programmer's Guide, and the Microsoft SNA Server CPI-C Programmer's Guide.


Registry variables

System-configuration variables stored in the Windows NT Registry. For information about the Registry variables that affect SNA Server, see the Microsoft SNA Server Reference.


remote LU

In an Advanced Program-to-Program Communications (APPC) or Common Programming Interface for Communications (CPI-C) conversation, the logical unit (LU) on the remote end. Contrast with local LU. See also remote TP.


remote node

(1) The node at the other end of a connection. (2) The node that contains the logical unit (LU) at the other end of a session. (3) The node that contains the transaction program (TP) at the other end of a conversation.


remote TP

In an Advanced Program-to-Program Communications (APPC) or Common Programming Interface for Communications (CPI-C) conversation, the transaction program (TP) on the remote end. Contrast with local TP. See also remote LU.

For information about TPs, see the Microsoft SNA Server Administration Guide, the Microsoft SNA Server APPC Programmer's Guide, and the Microsoft SNA Server CPI-C Programmer's Guide.


RTM

Response Time Monitor. A 3270 and NetView facility that monitors the amount of time it takes for a host to respond during 3270 display sessions.


RU

Request/response unit. Under SNA, a message that controls the session, data flow, and function management aspects of the SNA protocol.


SAA

Systems Application Architecture. Guidelines created by IBM to help developers standardize applications so they function in different operating environments with minimal program modification and retraining of users.


SAP address

Service access point address. A value that codes for access to certain services on an 802.2 connection within an SNA network. The Remote SAP Address parameter is used for 802.2 connections in SNA Server, and corresponds to the VTAM parameter called SAPADDR= in the PU definition.


SNA

Systems Network Architecture. 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, in a form that is usable by the receiving computer.


SNA Server

A Microsoft software program that allows a PC to communicate with remote computers such as IBM mainframes, AS/400s, or other PCs on an SNA network.


 SDLC

Synchronous Data Link Control. A type of link service used for managing synchronous data transfer over standard telephone lines (switched lines) or leased lines.


secondary link role

The role taken by the system that yields to the control of the other system during an SNA session. The SNA server takes the secondary link role in connections with host systems. See also negotiable link role and primary link role.


security key

An identifier used by two Advanced Program-to-Program Communications (APPC) logical units (LUs) to validate security when a session is activated. The security key performs a function similar to that of a password, but at the LU-LU session level rather than at the TP-conversation level.


security log

The location in which events related to security are recorded when auditing is set up for such events. For example, auditing can be set up to create a security log entry every time the configuration file is changed on an SNA server. See also event log.


security log

The location in which events related to security are recorded when auditing is set up for such events. For example, auditing can be set up to create a security log entry every time the configuration file is changed on an SNA server.


server

A PC that provides network services on a local area network or SNA network.


session

(1) A period of time when a connection is active and communication can take place. (2) A set of resources that when activated allow communication to take place. See also LU-LU session.


session limit

The maximum number of parallel sessions that can be active between two Advanced Program-to-Program Communications (APPC) logical units (LUs). When an LU-to-LU session is established, the session limit is negotiated between the two LUs.


Setup program

The SNA Server software installation program.


severity level

A number that indicates the severity of an event message. Informational (audit) messages have severity 6, 8, or 10. Error or warning messages have severity 12 or 16, indicating a problem that needs to be corrected.


single session

A limit of one session between a pair of Advanced Program-to-Program Communications (APPC) logical units (LUs), which limits the associated transaction programs (TPs) to one operation at a time.


service TP

A transaction program (TP) that uses APPC to perform services related to SNA functionality. See also application TP and TP.

For information about TPs, see the Microsoft SNA Server Administration Guide, the Microsoft SNA Server APPC Programmer's Guide, and the Microsoft SNA Server CPI-C Programmer's Guide.


SNA Service TP

A transaction program (TP) that uses APPC to perform services related to SNA functionality.

For information about TPs, see the Microsoft SNA Server Administration Guide, the Microsoft SNA Server APPC Programmer's Guide, and the Microsoft SNA Server CPI-C Programmer's Guide.


SSCP

System services control point. 1) A host-system network component that provides network services for dependent nodes. 2) An SNA network component that helps control and maintain communication flow between physical units (PUs) and logical units (LUs) on the network. Multiple SSCPs may work together in order to coordinate communications.


switched SDLC line

A standard telephone line used for SDLC connections on an SNA network. The line is dialed in one of three ways: manually, by a modem that stores the phone number, or by a modem that accepts a phone number string from the software.


SVC

Switched virtual circuit. A type of circuit used by an X.25 connection, in which the circuit is not constantly active, but is called and cleared dynamically. The destination address is supplied when the circuit is called.


synchronous transmission

Transmission in which the data characters and bits are transmitted at a fixed rate, with the transmitter and receiver being synchronized. This eliminates the need for individual start and stop bits surrounding each byte. Both SDLC and X.25 use synchronous transmission.


system administrator

The person who configures, maintains the configuration of, helps users diagnose problems with, and manages a computer system. With SNA Server, this person may also be the LAN administrator.


TCP/IP

Transmission Control Protocol/Internet Protocol. The transport protocol in use by many academic, defense, scientific, and commercial organizations to provide communication across wide area networks (WANs). TCP/IP provides communication across interconnected networks that include a variety of different operating systems (such as VMS, UNIX, and Windows NT).


terminal

A device that can send or receive data over a data communications channel. SNA Server allows for emulation of 3278 and 3279 terminals.


token ring

A type of LAN using the 802.2 protocol, in which a token is passed in a ring around the network, permitting a computer on the network to transmit data only when that computer has the token.


TP

Transaction program. An application program that uses Advanced Program-to-Program Communications (APPC) to exchange data with another TP on a peer-to-peer basis.

For information about TPs, see the Microsoft SNA Server Administration Guide, the Microsoft SNA Server APPC Programmer's Guide, and the Microsoft SNA Server CPI-C Programmer's Guide.


trace file

A file containing detailed records of internal activities on the SNA network, including calls made to APIs, the activities of APIs, and the activities of communication links and internal flows.

For an SNA server or Windows NT-based client, trace files are created when SNA tracing is turned on with the SNA Server Trace Options (snatrace) utility.


tracing

The action of tracking the activities of APIs, communication links, and internal flows, including the calls made to APIs. Tracing stores a history of activity in trace files.

For an SNA server or Windows NT-based client, SNA tracing can be turned on with the SNA Server Trace Options (snatrace) utility.


transaction

Data entered into a system (such as a customer deposit to a bank account), triggering a certain action (such as updating an account balance).


 Twinax

A twinaxial connection to a peer system.


twisted-pair cable

Two paired wires, with each wire twisted two or more times per inch to help cancel out noise.


user alert

A message sent by a 3270 user to a host system operator via NetView, requesting an action such as mounting a tape or changing forms on a printer.


VINES

VIrtual NEtworking System. A collection of networking software products from Banyan Systems, Inc. VINES includes an addressing system called StreetTalk.


VTAM

Virtual Telecommunications Access Method. A set of IBM mainframe programs that control communications between mainframe applications and the terminals and computers that connect to the mainframe.


WAN

Wide area network. A high-speed communication system, consisting of hardware (computers and peripherals) and software (programs and files), that provides communications services and allows resources to be shared over a larger geographic area than that served by a LAN. Contrast with LAN.


 X.25

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


XID

Exchange Identification. An identifier that is exchanged between nodes on an SNA network, and that allows the nodes to recognize each other and to establish link and node characteristics for communicating. With SNA Server, there are two possible kinds of XIDs that can be exchanged: Format 0 XIDs (containing only basic information such as Node ID) and Format 3 XIDs (containing more detailed information such as Network Name and Control Point Name). See also Format 0 XID and Format 3 XID.


XID

Exchange Identification. An identifier that is exchanged between nodes on an SNA network, and that allows the nodes to recognize each other and to establish link and node characteristics for communicating. With SNA Server, there are two possible kinds of XIDs that can be exchanged: Format 0 XIDs (containing only basic information such as Node ID) and Format 3 XIDs (containing more detailed information such as Network Name and Control Point Name).


  Working with Configuration Files

  Saving and Reopening the Configuration

  Backing Up and Restoring the Configuration

  Offline Configuration


  Guidelines for Downstream Configurations

  Configuring Servers and Connections

  Configuring Downstream Connections

  Assigning, Viewing, or Modifying Downstream LUs

  Configuring Properties for a Downstream LU

  Creating Downstream Pools

  Associating Downstream LUs with a Downstream Connection

  Adjusting the Numbering of Downstream LUs


  Downstream Connections and LUs: Overview


  Downstream Connections and LUs: Overview

  Guidelines for Downstream Configurations


  Downstream Connections and LUs: Overview

  Guidelines for Downstream Configurations

  Configuring Downstream Connections

  Configuring Properties for a Downstream LU

  Configuring Numbering for a Downstream LU Range

  Associating Downstream LUs with a Downstream Connection


  Guidelines for Downstream Configurations

  Assigning, Viewing, or Modifying Downstream LUs

  Creating Downstream Pools

  Modifying the Extension Numbering Format

  Adding a Comment for a Downstream LU Range


  Guidelines for Downstream Configurations

  Configuring Numbering for a Downstream LU Range

  Creating Downstream Pools


  Assigning, Viewing, or Modifying Downstream LUs

  Associating Downstream LUs with a Downstream Connection

  Adjusting the Numbering of Downstream LUs

  Creating Downstream Pools


  Downstream Connections and LUs: Overview

  Associating Downstream LUs with a Downstream Connection

  Adjusting the Numbering of Downstream LUs

  Creating Downstream Pools


  Downstream Connections and LUs: Overview

  Guidelines for Downstream Configurations

  Example of Reordering Downstream LUs

  Example of Adding Empty LU Pools


Configuration Files on Primary and Backup SNA Servers

The configuration file that stores the last saved configuration for the domain is an important file for SNA Server. Each time you start SNA Server Admin, it loads this file. Each time you make configuration changes and save them, they are saved to this file.

To ensure that the last saved configuration can be loaded, SNA Server Setup allows you to designate a primary SNA server and one or more backup SNA 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 Admin 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 SNA 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.

If for some reason replication of the configuration file does not complete successfully, use the following procedure to ensure that the configuration is copied to the backup SNA server(s).

  To copy the configuration file from the primary SNA server to a backup SNA server

Another method for copying the configuration file from the primary server to the backup server(s) is to use the replication capabilities of Windows NT Server. Use these capabilities to replicate the \SNAroot\SYSTEM\CONFIG subdirectory on the primary server. For information about replication, see the Microsoft Windows NT Server System Guide.


1	On the primary SNA server, switch to a command prompt, or start File Manager.

2	Change to \SNAroot\SYSTEM\CONFIG, where SNAroot is the SNA Server root directory.

3	Using network commands, connect to \\servername\COMCFG, where servername is the name of the intended backup SNA server.

4	Copy the COM.CFG file from the \SNAroot\SYSTEM\CONFIG directory to the \\servername\COMCFG share, where servername is the name of the backup SNA server.

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

 5	When prompted for confirmation, choose Yes.


Moving a Connection to a Different Server

To move a connection by dragging and dropping it:

1	In the Servers and Connections window, click the connection once.
The connection is highlighted to show that it is selected.

2	Point to the connection with the mouse pointer.

3	Press and hold the left mouse button and move the mouse.
An icon representing the connection moves on the screen. The icon changes to a slashed circle while in a place where releasing the connection has no meaning.

4	When the icon is on the intended server, release the mouse button.


Downstream LU Pool Dialog Box

In the Downstream LU Pool dialog box, confirm or change the Pool Name and the optional comment of up to 25 characters.

To exit the dialog box without affecting configuration settings, choose Cancel. To accept the settings, choose OK. After creating a pool, add LUs to the pool; only a pool that contains LUs provides LU access. See Assigning LUs to an LU Pool.


Creating Downstream Pools

This topic tells how to add a new downstream LU pool, or access an existing one. After adding the pool, assign LUs to it; only a pool that contains LUs provides LU access. See Assigning LUs to an LU Pool.

For information about the uses of LU pools, see Using LU Pools to Maximize Access: Overview.

To add a downstream LU pool

1	In the LU Pools window, select any item.

2	On the Toolbar, click  [image].

3	In the Insert dialog box, select New Pool.

4	Choose OK.

5	In the New Pool dialog box, under Pool Type, select Downstream.

6	In the Pool Name box, type a pool name. The name identifies the pool on the SNA server only, not on a host or downstream system.

7	Optionally, in the Comment box, type a comment of up to 25 characters.

8	Choose OK.

To access an existing downstream LU pool for viewing or modifying

1	In the LU Pools window, select the pool.

If the pool you want does not appear in the list, from the View menu, choose All LU Pools, and then select the pool.

2	On the Toolbar, click  [image].


Downstream Connections and LUs: Overview

Downstream connections and LUs allow an SNA server to support communication between hosts and clients such as IBM Communications Manager/2 systems. Even though such clients do not use the SNA Server client/server interface, with a downstream connection, they can access host connections available through an SNA server. For a diagram of a single downstream system using SNA Server, see Downstream Connection Diagram. For a diagram of multiple downstream systems using an SNA server (which is also called DSPU concentration), see the Microsoft SNA Server Administration Guide.

Note  With SNA  Server, communication over a downstream connection and LU is always dependent, that is, controlled by a host. SNA Server does not support independent LU 6.2 communication over a downstream connection and LU.

To the downstream system, there appears to be a direct connection to the host. The SNA server accomplishes this by passing information back and forth between downstream system and host.

The information that SNA Server passes from downstream system to host includes LU information. Therefore, SNA Server does not store detailed LU configuration information for downstream LUs. However, SNA Server does require all the usual connection information for the host and downstream connections.

Whenver you make changes to downstream configurations, to put the changes into effect, restart the affected SNA server, as described in Restarting an SNA Server.


DSPU

Downstream physical unit; also known as a 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.


A host connection, a single downstream connection, and a downstream LU are illustrated in the following diagram:


[]JAN: DOWNSTREAM GUIDELINES ARE DUPLICATED IN TWO CONTEXTS: THE CONTEXT FOR A SECONDARY WINDOW FROM ANOTHER WINDOW, AND THE CONTEXT FOR A REGULAR WINDOW FROM THE SEARCH LIST.  KEEP BOTH COPIES UPDATED.


Guidelines for Downstream Configurations

The following table shows the basic steps for configuring downstream LUs and connections, and tells where to find additional information about each step:

Step	Additional information
1 Gather needed information about the host and downstream systems, including information about identifiers (such as addresses and XID information) and information about Max BTU Length.	Working with VTAM, NCP, and/or CICS
2 Configure the host connection as you would configure any other connection to a host. When specifying the remote end for the connection, select Host System.	Configuring Servers and Connections
3 Configure the downstream connection. When specifying the remote end for the connection, select Downstream. The downstream connection can be an 802.2, SDLC, or X.25 connection. It cannot be a DFT, Channel, or Twinax connection.	Configuring Downstream Connections
4 Select the host connection, and assign one or more new downstream LUs to that connection.	Assigning, Viewing,  or Modifying Downstream LUs
5 Optionally, pool downstream LUs, to maximize the access available through these LUs.	Creating Downstream Pools
6 Select the downstream connection, and associate the downstream LUs (from step 4) and/or the LU pools (from step 5) with that connection.	Associating Downstream LUs  with a Downstream Connection
7 If necessary, reorder the downstream LU numbers, that is, the LU numbers used by the downstream system (not the host). A downstream LU has two LU numbers: one recognized by the downstream system, one recognized by the host. These numbers need not match, and probably will not match.	Adjusting the Numbering of Downstream LUs
8 To put configuration changes into effect, restart the SNA server.	Restarting an SNA Server


Guidelines for Downstream Configurations

The following table shows the basic steps for configuring downstream LUs and connections, and tells where to find additional information about each step:

Step	Additional information
1 Gather needed information about the host and downstream systems, including information about identifiers (such as addresses and XID information) and information about Max BTU Length.	Working with VTAM, NCP, and/or CICS
2 Configure the host connection as you would configure any other connection to a host. When specifying the remote end for the connection, select Host System.	Configuring Servers and Connections
3 Configure the downstream connection. When specifying the remote end for the connection, select Downstream. The downstream connection can be an 802.2, SDLC, or X.25 connection. It cannot be a DFT, Channel, or Twinax connection.	Configuring Downstream Connections
4 Select the host connection, and assign one or more new downstream LUs to that connection.	Assigning, Viewing,  or Modifying Downstream LUs
5 Optionally, pool downstream LUs, to maximize the access available through these LUs.	Creating Downstream Pools
6 Select the downstream connection, and associate the downstream LUs (from step 4) and/or the LU pools (from step 5) with that connection.	Associating Downstream LUs  with a Downstream Connection
7 If necessary, reorder the downstream LU numbers, that is, the LU numbers used by the downstream system (not the host). A downstream LU has two LU numbers: one recognized by the downstream system, one recognized by the host. These numbers need not match, and probably will not match.	Adjusting the Numbering of Downstream LUs
8 To put configuration changes into effect, restart the SNA server.	Restarting an SNA Server


Configuring Downstream Connections

Two connections are needed for a downstream system: a downstream connection (from the downstream system to the SNA server) and an ordinary host connection (from the SNA server to the host). For a diagram of the connections, see Downstream Connection Diagram.

To access an existing connection for viewing or modifying

1	In the Servers and Connections window, select the connection.

2	On the Toolbar, click  [image].

For information about appropriate values to specify for a downstream connection, see steps 5-10 of the following procedure.

To configure a new downstream connection

1	In the Servers and Connections window, select the server on which to add the downstream connection.

2	On the Toolbar, click  [image].

3	In the Insert dialog box, select the connection type: 802.2, SDLC, or X.25. See Note.

4	Choose OK.

5	In the Connection Properties dialog box, specify an appropriate Connection Name and select a link service; optionally, specify a comment.

6	For an X.25 connection, select a Virtual Circuit Type of Switched (SVC) or Permanent (PVC).

7	Under Remote End, select Downstream.

8	Under Allowed Directions, select Incoming Calls and/or Outgoing Calls as needed.

For an SDLC downstream connection, Outgoing Calls must be selected.

9	If the Allowed Directions include Outgoing Calls, under Activation, make any desired changes. For outgoing calls on a downstream connection, the only functional choices are On Server Startup and By Administrator.

Activation does not affect Incoming Calls.  A connection that accepts incoming calls begins to listen for these calls when the SNA server (node) is started.

10	Choose Setup and then choose Advanced.

11	Specify other connection parameters according to the hardware and software between the downstream system and the SNA server. Be sure to specify the Max BTU Length correctly. For details, contact the network administrator and/or the operator of the downstream system, and see the topics in Configuring Servers and Connections. See also Note About Link Roles.

12	When you are finished with the 802.2 Setup, SDLC Setup, or X.25 Setup dialog box, choose OK.

The Connection Properties dialog box appears.

13	Choose OK.


Note

The downstream connection can be an 802.2, SDLC, or X.25 connection. It cannot be a DFT, Channel, or Twinax connection.


Note About Link Roles

The SNA server will assume the link role of Primary in a connection with a downstream system. Therefore, the administrator of the downstream system should configure the downstream system with the link role of Secondary.


Assigning, Viewing, or Modifying Downstream LUs

Before you can create a new downstream LU, you must configure the host connection the LU will use. Configure this connection as you would any other host connection. For more information, see Configuring Servers and Connections.

You can create LUs one at a time or in a consecutively numbered range. When you create a range of LUs, all the LUs will be given the same properties. You can modify individual LUs after creating them.

  To assign a new downstream LU or a range of downstream LUs to a host connection

  To access an existing downstream LU for viewing or modifying

To configure an LU, see Configuring Properties for a Downstream LU. To configure a range of downstream LUs, see Configuring Numbering for a Downstream LU Range. See also Moving an LU.

After creating a new downstream LU on a host connection, associate the LU with the downstream connection it will use. For more information, see Associating Downstream LUs with a Downstream Connection.

To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


1	In the Servers and Connections window, select the host connection to which you want to assign the downstream LU(s).

2	On the Toolbar, click  [image].

3	In the Insert dialog box, under New Logical Unit, select Downstream.

4	To add a range of LUs instead of just one, select Range of LUs.

5	Choose OK.


1	In the Servers and Connections window, select the LU you want to view or modify.

2	On the Toolbar, click  [image].


Configuring Numbering for a Downstream LU Range

After assigning a range of downstream LUs to a connection, in the Add LU Range dialog box, supply information as follows:

Base LU Name

Type the Base LU Name.

First LU Number

Type the first LU Number in the range.

Number of LUs

Type the number of LUs that you want in the LU range. Check with the host administrator to find out how many LUs are available for your system.

Note  The LU numbers generated for an LU range are sequential. If the numbers assigned by your host administrator are not sequential, you can modify the numbers of individual LUs after they have been created.

When you have typed the appropriate LU range values, choose one of the following:

To modify the extension numbering format (displayed under Selected LU Range), choose Options. See Modifying the Extension Numbering Format.

To exit the dialog box without accepting the settings, choose Cancel.

To accept the settings, choose OK. Then, in the Downstream LU Range Properties dialog box, you can choose OK to accept the range configuration, or you can add an optional comment. For information about adding a comment, see Adding a Comment for a Downstream LU Range.


Adding a Comment for a Downstream LU Range

After assigning and numbering a range of downstream LUs, you can add an optional comment for the range. All the LUs will receive the same comment; you can modify individual LU comments after finishing the configuration of the range. For information about modifying individual LUs, see Configuring Properties for a Downstream LU.

To add an optional comment for a new downstream LU range

1	In the Downstream LU Range Properties dialog box, under Comment, type a comment of up to 25 characters.

2	Choose OK.

3	To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


Configuring Properties for a Downstream LU

After assigning or viewing a downstream LU, supply the information in the following list. If you are configuring a downstream LU on a DFT host connection, see also Numbers Needed for DFT LUs.

Note  After making configuration changes, to put the changes into effect, restart the SNA server, as described in Restarting an SNA Server.

LU Number

Type the LU Number that identifies the LU to the host.

If the LU is on a DFT host connection , it does not use an LU number, but requires other identifying numbers instead. For information, see Numbers Needed for DFT LUs.

Downstream LU Number

The Downstream LU Number is assigned by SNA Server when the LU is associated with a downstream connection. This number need not match the LU number. To change the Downstream LU Number, first complete the configuration of the downstream LU, and make sure it is associated with a downstream connection, as described in Associating Downstream LUs with a Downstream Connection. Then you can reorder downstream LU numbers, as described in Adjusting the Numbering of Downstream LUs.

LU Name

Type the LU Name.

The LU name identifies the LU on the SNA server only, not on the host or downstream system.

Connection

The connection for this LU is shown. The connection cannot be changed from within this dialog box. To change the connection after configuring the LU, see Moving an LU.

Pool

If the LU has already been assigned to a pool, the pool name appears here.

Comment

Optionally, type a comment of up to 25 characters.


Downstream LU Properties

In the New Downstream LU Properties or the Downstream LU Properties dialog box, supply the information in the following list.

Note  After making configuration changes, to put the changes into effect, restart the SNA server, as described in Restarting an SNA Server.

LU Number

Type the LU Number that identifies the LU to the host.

Downstream LU Number

The Downstream LU Number is assigned by SNA Server when the LU is associated with a downstream connection. This number need not match the LU number. To change the Downstream LU Number, first complete the configuration of the downstream LU, and make sure it is associated with a downstream connection, as described in Associating Downstream LUs with a Downstream Connection. Then you can reorder downstream LU numbers, as described in Adjusting the Numbering of Downstream LUs.

LU Name

Type the LU Name.

The LU name identifies the LU on the SNA server only, not on the host or downstream system.

Connection

The connection for this LU is shown. The connection cannot be changed from within this dialog box. To change the connection after configuring the LU, see Moving an LU.

Pool

If the LU has already been assigned to a pool, the pool name appears here.

Comment

Optionally, type a comment of up to 25 characters.


Downstream LU Properties

In the New Downstream LU Properties or the Downstream LU Properties dialog box, supply the information in the following list.

Note  After making configuration changes, to put the changes into effect, restart the SNA server, as described in Restarting an SNA Server.

Port Number

Type the number of the DFT adapter that will be used. (This is not the port of the 3174.)

LT Number

Type the logical terminal number as configured at the 3174 for this coaxial cable.

Downstream LU Number

The Downstream LU Number is assigned by SNA Server when the LU is associated with a downstream connection. This number need not match the LU number. To change the Downstream LU Number, first complete the configuration of the downstream LU, and make sure it is associated with a downstream connection, as described in Associating Downstream LUs with a Downstream Connection. Then you can reorder downstream LU numbers, as described in Adjusting the Numbering of Downstream LUs.

LU Name

Type the LU Name.

The LU name identifies the LU on the SNA server only, not on the host or downstream system.

Connection

The connection for this LU is shown. The connection cannot be changed from within this dialog box. To change the connection after configuring the LU, see Moving an LU.

Pool

If the LU has already been assigned to a pool, the pool name appears here.

Comment

Optionally, type a comment of up to 25 characters.


LU Number

A number identifying a downstream LU on a host connection. Check with the administrator of the host system for the correct value; it should match the LOCADDR= parameter of the LU definition in VTAM or in the NCP Gen.

If the number you specify has already been assigned to an LU or an APPC LU-LU pair on the current connection, a message box appears, and you must change the number.


Downstream LU Number

A number identifying a downstream LU to the downstream system.


LU Name

A name identifying the LU. The name can be from one through eight characters long, and can contain alphanumeric characters and the special characters $, #, and @. Lowercase letters are converted to uppercase. The name cannot be the same as any other LU or LU pool that uses this connection.


Associating Downstream LUs with a Downstream Connection

Before you can associate downstream LUs or LU pools with a downstream connection, you must configure the connection and the LUs. For information, see the following:

Configuring Servers and Connections

Configuring Downstream Connections

Assigning, Viewing, or Modifying Downstream LUs

Configuring Properties for a Downstream LU

To associate one or more downstream LUs or LU pools with a downstream connection

1	In the Servers and Connections window, select the downstream connection.

2	On the Toolbar, click  [image].

3	In the Insert dialog box, under New Logical Unit, select Downstream.

4	Choose OK.

The Assign Downstream LU/Pool Sessions dialog box appears. Only downstream LUs and pools are listed in the dialog box.

5	Under Available LUs and Pools, choose one or more downstream LUs and/or pools:

To select multiple items in sequence, click the first item you want, hold down SHIFT, and click the last item you want.

To select multiple items out of sequence, hold down CTRL as you click the items that you want.

Important  If a downstream system needs access to multiple LU sessions, assign one LU or LU pool for each session needed. You can assign a pool multiple times to the same downstream connection.

6	Choose OK.

7	To put configuration changes into effect, restart the affected SNA server(s), as described in Restarting an SNA Server.


Adjusting the Numbering of Downstream LUs

Downstream LUs have two different numbers:

The LU number, which identifies the LU to the host

The downstream LU number, which identifies an LU or LU pool to the downstream system

The LU number and the downstream LU number need not match, and probably will not match. The downstream LU number should match the LU number on the downstream system.

A downstream LU number is assigned by SNA Server to each LU or LU pool in the list for the downstream connection. SNA Server assigns downstream LU numbers starting with 2 and ascending consecutively. Therefore, one way to change downstream LU numbers is to reorder the list of LUs for the downstream connection. Another way to change downstream LU numbers is to use empty LU pools to take up unwanted numbers, leaving the correct (larger) numbers for other LU pools or LUs. For examples, see Example of Reordering Downstream LUs and Example of Adding Empty LU Pools.

To reorder one or more LUs in the list for a downstream connection

1	In the Servers and Connections window, select the downstream connection with which the LUs are associated.

2	Select one or more LUs and/or pools that you want to move up in the list.

To select multiple items in sequence, click the first item you want, hold down SHIFT, and click the last item you want.

To select multiple items out of sequence, hold down CTRL as you click the items that you want.

3	From the Services menu, choose Reorder LUs.

The Reorder LU Session dialog box appears.

4	In the Move Selected LU Session(s) Before Session Number box, type the number that you want the first selected LU or pool to have.

5	Choose OK.

The selected LUs are moved up in the list, and other LUs are moved down.

6	To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


Example of Reordering Downstream LUs

An administrator might create a downstream LU called DOWNLU3, and then realize that two additional LUs are needed. After creating the LUs, with the names DOWNLU2 and DOWNLU4, the LUs would be associated with the listed LU numbers:

LU name	Downstream LU number
DOWNLU3	2
DOWNLU2	3
DOWNLU4	4
To change the downstream numbers so that they match the digits in the LU names, DOWNLU2 could be reordered so that it is placed before DOWNLU3:

LU name	Downstream LU number
DOWNLU2	2
DOWNLU3	3
DOWNLU4	4


Example of Adding Empty LU Pools

Three downstream LUs could be created with the following names and downstream LU numbers:

LU name	Downstream LU number
DOWNLU5	2
DOWNLU6	3
DOWNLU7	4
If the downstream system expects downstream LU numbers 5, 6, and 7, three empty LU pools could then be created, using the names EMPTY2, EMPTY3, and EMPTY4. Then the LUs and LU pools could be ordered as shown:

LU name	Downstream LU number
EMPTY2	2
EMPTY3	3
EMPTY4	4
DOWNLU5	5
DOWNLU6	6
DOWNLU7	7


Adding a Server to an Offline Configuration

1	Start the offline version of SNA Server Admin.

2	In the Servers and Connections window, select any line.

3	From the Services menu, choose New Server.

4	In the Server Properties dialog box, type a server name for the new server.
Important  The server name must match the computer name of an installed SNA server at the site where the configuration will be used.

5	If desired, specify other configuration settings for the server.
To configure an adapter for the server, choose the Adapters button, and see the Microsoft SNA Server Installation Guide.

6	Choose OK.


Administration After Upgrading from Comm Server 1.x

This topic, and the topics that can be reached from it, provide information about Comm Server 1.x and SNA Server compatibility, and describe the steps to take when beginning to administer a domain that has been upgraded from Comm Server 1.x to SNA Server. For details about how to carry out the upgrade, see the Microsoft SNA Server Installation Guide.

Compatibility Between Comm Server 1.x and SNA Server

For a listing of the Comm Server 1.x software and files that are compatible with SNA Server, and those that are not, see Comm Server 1.x and SNA Server Compatibility, and Important Note About Compatibility. For important information about the MS-DOS--based Comm Server 1.x 3270 emulator, see Files Needed for the Comm Server 1.x 3270 Emulator.

Using SNA Server Admin After Upgrading

Before starting SNA Server Admin on servers that have been upgraded from Comm Server 1.x, read the Important Note About Compatibility, and note the instructions in the Microsoft SNA Server Installation Guide, especially the instructions regarding Comm Server 1.x configuration and security files.

To reinstate all functionality in a configuration file that has been successfully converted from Comm Server 1.x format, carry out the following steps, which are also included in the upgrading procedure in the Microsoft SNA Server Installation Guide:

1	Add the needed user and group accounts to the Windows NT domain, as described in the Microsoft SNA Server Installation Guide and in the Windows NT documentation.

2	In SNA Server Admin, for each connection in the configuration, assign a link service.

To do this, in the Servers and Connections window, select the connection, then click  [image].  Then, in the Connection Properties dialog box, select a Link Service. If the link service you want is not in the list, choose Cancel, and use SNA Server Setup to install the link service.

3	In the Users and Groups window, add users and groups to the list recognized by SNA Server.

4	In the Users and Groups window, assign LUs to SNA Server users and groups.

5	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 the Microsoft SNA Server Installation Guide.

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

6	On the Toolbar, click  [image].


Comm Server 1.x and SNA Server Compatibility

Some of the software and files in a Comm Server 1.x installation are compatible with SNA Server, and some are not:

Comm Server 1.x clients are compatible with SNA Server software, and can function in the same domain with SNA servers and SNA Server clients.

A Comm Server 1.x configuration file can be saved before an upgrade and then used with SNA Server. When such a file is loaded by SNA Server Admin, it is automatically converted to SNA Server format.

In contrast, an SNA Server configuration file cannot be loaded by a Comm Server 1.x server.

Comm Server 1.x servers are not compatible with SNA servers, and should not be started in the same domain with SNA servers.

Applications written according to the Comm Server 1.x APIs are compatible with SNA Server, and will function in an SNA Server domain.

However, before using the MS-DOS--based Comm Server 1.x 3270 emulator, you must either obtain an upgraded version of the emulator, or must copy certain Comm Server files to the primary SNA server. For information, see Files Needed for the Comm Server 1.x 3270 Emulator.


Files Needed 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 DCA, or carry out the following procedure for copying needed files.

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 the \\SNA1\COMMSRV share. 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.

If you will be running the MS-DOS--based Comm Server 1.x 3270 emulator with the MS-DOS--based SNA Server client software, see also Important Note About Client and Emulator Software.

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.

Also note that the MS-DOS--based Comm Server 1.x 3270 emulator should run with local style files only.


Important Note About Compatibility

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.


Important Note About Client and Emulator 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 preceding procedure. Note that after this procedure is carried out, the client will not support LUA applications.

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 reboot the client system.


Enabling Communication Between Version 2.0 SNA Servers and Version 2.1 SNA Servers

For a complete list of steps for upgrading a domain of SNA servers from version 2.0 to version 2.1, see the Microsoft SNA Server Installation Guide.

To enable communication between version 2.0 SNA servers and version 2.1 SNA servers

1	On a version 2.1 SNA server, start SNA Server Admin.

2	From the Options menu, choose Server Broadcasts.

The Server Broadcasts dialog box appears.

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

4	Choose OK.

5	On the Toolbar, click  [image].


Multiple Domains in an SNA Server Installation

With SNA Server, you can work with multiple domains in your SNA installation. For information about planning the domains, see the Microsoft SNA Server Installation Guide. For information about setting up necessary user accounts and the associated user rights, see your Windows NT documentation.

With SNA Server Admin, you can change the domain of focus as needed. To change the domain of focus, from the File menu, choose Select Domain, then, from the resulting dialog box, select the intended domain or type a domain name. Then choose OK.


Changing the Domain of Focus

With SNA Server Admin, you can work with servers in different domains, by changing the domain of focus as needed.

To change the domain of focus of SNA Server Admin

1	From the File menu, choose Select Domain.

The Select Domain dialog box appears.

2	Select the intended domain from the list under Select Domain, or type a domain name in the Domain box.

3	Choose OK.


Changing the Domain of Focus

With SNA Server Admin, you can work with servers in different domains, by changing the domain of focus as needed.

To change the domain of focus of SNA Server Admin

1	From the File menu, choose Select Domain.

The Select Domain dialog box appears.

2	Select the intended domain from the list under Select Domain, or type a domain name in the Domain box.

3	Choose OK.


Select Domain Dialog Box

With SNA Server Admin, you can work with servers in different domains, by changing the domain of focus as needed.

In the Select Domain dialog box, select the intended domain from the list under Select Domain, or type a domain name (or the name of a server in the domain) in the Domain box. Then choose OK.


Adding Users and Groups and Setting Permissions

For background information about security with SNA Server, see the Microsoft SNA Server Administration Guide.

To add groups and users to the list of those with SNA Server administrative permissions

1	From the Security menu, choose Permissions.

The SNA Domain Permissions dialog box appears.

2	Choose Add.

3	If you want to add users from another domain, in the List Names from box, select a different domain.

The domains listed are trusted domains.

4	If you want the accounts displayed to include users as well as groups, choose the Show Users button.

5	Under Names, select one or more groups or users.

To select multiple names in sequence, click the first name you want, hold down SHIFT, and click the last name you want.

To select multiple names out of sequence, hold down CTRL as you click the names that you want.

6	Choose the Add button.

The selected group or user name(s) appear in the Add Names box.

7	Repeat steps 5 and 6 as needed.

8	In the Type of Access box, select the permission that you want the listed user(s) or group(s) to have. If multiple names appear in the Add Names box, they will all be assigned the same permission--the last one you select before choosing OK. The permissions for any particular account can easily be changed later. The permissions are as follows:

No Access

With No Access permission in the SNA domain, a user or group cannot run SNA Server Admin or the snacfg command-line program, and cannot read or write the configuration file.

No Access overrides any other permissions that apply to a particular user. For example, if a user belongs to a group that has Read permission, but the user has No Access, the user is not permitted administrative access.

Read (Manage Only)

With Read (Manage Only) permission in the SNA domain, a user or group can run SNA Server Admin and the snacfg command-line program, but only to read (not write to) the configuration file. See Recommendation for Read Permission.

Read/Write

With Read/Write permission in the SNA domain, a user or group can run SNA  Server Admin and the snacfg command-line program, and can read and write to the configuration file. See Recommendation for Read/Write Permission.

Full Control

With Full Control permission in the SNA domain, a user or group can run SNA  Server Admin and the snacfg command-line program; can read and write to the configuration file; can change the administrative permissions assigned to others; and can remove SNA Server software. See Recommendation for Full Control Permission.

9	Choose OK.


Recommendation for Read Permission

Assign Read (Manage Only) permission to SNA administrators who will manage SNA Server (view, start and stop SNA Server services), but not change the SNA Server configuration.


Recommendation for Read/Write Permission

Assign Read/Write permission to SNA administrators who will manage SNA Server (start and stop SNA Server services) and also change the SNA Server configuration, but who will not manage the administrative permissions of other SNA Server users.


Recommendation for Full Control Permission

Assign Full Control permission to SNA administrators who will manage SNA Server (start and stop SNA Server services), change the SNA Server configuration, and manage the permissions of other SNA Server users. In addition, assign Full Control to SNA administrators who will remove SNA Server software from servers.


Configuring SNA Domain Permissions

For background information about security with SNA Server, see the Microsoft SNA Server Administration Guide.

To configure permissions for users and groups in SNA Server Admin

1	From the Security menu, choose Permissions.

The SNA Domain Permissions dialog box appears.

2	To add users or groups to the list of those with permissions in SNA Server, choose the Add button, and use the Add Users and Groups dialog box to select and add the intended users or groups.

3	Under Name, select a group or user for whom you want to specify administrative permissions.

4	In the Type of Access box, select the permission that you want the selected user or group to have:

No Access

With No Access permission in the SNA domain, a user or group cannot run SNA Server Admin or the snacfg command-line program, and cannot read or write the configuration file.

No Access overrides any other permissions that apply to a particular user. For example, if a user belongs to a group that has Read permission, but the user has No Access, the user is not permitted administrative access.

Read (Manage Only)

With Read (Manage Only) permission in the SNA domain, a user or group can run SNA Server Admin and the snacfg command-line program, but only to read (not write to) the configuration file. See Recommendation for Read Permission.

Read/Write

With Read/Write permission in the SNA domain, a user or group can run SNA  Server Admin and the snacfg command-line program, and can read and write to the configuration file. See Recommendation for Read/Write Permission.

Full Control

With Full Control permission in the SNA domain, a user or group can run SNA  Server Admin and the snacfg command-line program; can read and write to the configuration file; can change the administrative permissions assigned to others; and can remove SNA Server software. See Recommendation for Full Control Permission.

Special

Use the option marked Special if you need to specify a special set of permissions for a particular user or group. It is recommended that you avoid creating special sets of permissions except when necessary; the standard administrative permissions should be appropriate for most situations.

The permission listed under Name changes to match the permission selected in the Type of Access box.

5	Choose OK.


Setting Up Auditing of Access to the Configuration File

For important information about auditing with SNA Server, see the Microsoft SNA Server Administration Guide. For additional background information about auditing, see your Windows NT documentation.

To set up auditing of security events affecting SNA Server

1	To make sure that auditing is turned on in the domain, start User Manager and then, from the Policies menu, choose Audit. In the resulting dialog box, be sure that Audit These Events has been selected, along with File and Object Access (Success and Failure); then choose OK, and close User Manager.

2	Start SNA Server Admin.

3	From the Security menu, choose Auditing.

The SNA Domain Auditing dialog box appears.

4	To add users or groups to the list of those whose actions are audited, choose the Add button, and use the Add Users and Groups dialog box to select and add the intended users or groups.

To audit actions carried out by any user (rather than the actions of a specific group), add the group called Everyone.

5	Under Name, select a user or group.

6	Under Events to Audit, select the events you want to audit for that user or group.

7	Repeat steps 5 and 6 for each of the users and groups listed under Name.

If you do not specify any actions to audit for a user or group, and then you close and reopen the dialog box, that user or group name will no longer appear in the list under Name.

8	Choose OK.


SNA Server User Licensing Dialog Box

You must first purchase one or more Microsoft SNA Server user licenses in order to enter any number into the field provided. Otherwise, you will be in violation of the license agreement. After you have purchased the user licenses, you can enter the number of user licenses purchased into the field provided. The minimum value for legal use is 1.

The user limit is a domain-wide limit. The user license allows the user to access any SNA server or multiple SNA servers in the same Windows NT Server domain. The maximum possible user limit per server is 2000. As many as 50 SNA servers can exist in a single domain, for a combined maximum user limit of 100,000. For each SNA server installed, a server license for SNA Server must be purchased. This server license alone does not allow any users to use SNA Server services; a user license is also required.

If the user limit is exceeded, for each occurrence, an event log entry is written indicating the license violation. However, the additional user will be allowed to connect. The event is recorded in the Windows NT application event log and can be viewed through the Windows NT Event Viewer. The event message explains in detail what to do to bring the system in accordance with the required license.


Microsoft Support Services Contents
Microsoft Support Services

When You Have a Question

Product Support Within the United States and Canada

Product Support Outside the United States and Canada


When You Have a Question

If you have a question about 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 your SNA Server CD-ROM or disks. If you cannot find the answer, contact the Microsoft Support Network.

Outside the United States and Canada, contact Microsoft Product Support Services at the Microsoft subsidiary office that serves your area.

The Microsoft Support Network

The Microsoft Support Network offers high quality technical support options that allow you to get what you need: the right answers right now. For information about support services in the United States and Canada, see Product Support Within the United States and Canada.

Services vary outside the United States and Canada. In other locations, contact a local Microsoft subsidiary for information. The Microsoft Support Network is subject to Microsoft's then-current prices, terms, and conditions, and is subject to change without notice. For information about support services outside the United States and Canada, see Product Support Outside the United States and Canada.


Product Support Within the United States and Canada

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

Electronic Services

Priority Support

Text Telephone

Other Support Options

Other Microsoft Services


Electronic Services

These services are available 24 hours a day, 7 days a week, including holidays.

Microsoft FastTips

(800) 936-4400 on a touch-tone telephone. Receive automated answers to common questions, and access a library of technical notes, all delivered by recording or fax. You can use the following keys on your touch-tone telephone after you reach FastTips:

To	Press
Advance to the next message	*
Repeat the current message	7
Return to the beginning of FastTips	#
CompuServe

Interact with other users and Microsoft support engineers, or access the Microsoft Knowledge Base to get product information. At any ! prompt, type go microsoft to access Microsoft forums, type go mskb to access the Microsoft Knowledge Base, or type go mssna to access the Microsoft SNA forum. For an introductory CompuServe membership kit, call (800) 848-8199, operator 524.

Microsoft Download Service

Access, via modem, the Driver Library and the most current technical notes (1200, 2400, or 9600 baud; no parity; 8 data bits; 1 stop bit). In the United States, call (206) 936-6735. In Canada, call (905) 507-3022.

Internet

Access the Driver Library and the Microsoft Knowledge Base. The Microsoft Internet FTP archive host, ftp.microsoft.com, supports anonymous login. When logging in as anonymous, you should type your complete electronic mail name as your password.

See also

Priority Support

Text Telephone

Other Support Options

Other Microsoft Services


Priority Support

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

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

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

In Canada, call (800) 563-9048 for more information.

See also

Electronic Services

Text Telephone

Other Support Options

Other Microsoft Services


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) 635-4948 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) 568-9641 between 8:00 A.M. and 8:00 P.M. Eastern time, Monday through Friday, excluding holidays.

See also

Electronic Services

Priority Support

Other Support Options

Other Microsoft Services


Other Support Options

The Microsoft Support Network offers annual and multiple incident support plans. For information, in the United States, contact the Microsoft Support Network Sales and Information group at (800) 936-3500 between 6:00 A.M. and 6:00 P.M. Pacific time, Monday through Friday, excluding holidays. In Canada, call (800) 563-9048 between 8:00 A.M. and 8:00 P.M. Eastern time, Monday through Friday, excluding holidays. Technical support is not available through these sales numbers.

Electronic Services

Priority Support

Text Telephone

Other Microsoft Services


Other Microsoft Services

Microsoft Solution Providers Program

Microsoft Solution Providers are independent organizations that provide consulting, integration, customization, development, technical support and training, and other services for Microsoft products. These companies are called Solution Providers because they apply technology and provide services to help solve real-world problems.

In the United States, for more information about the Microsoft Solution Providers program or the Microsoft Solution Provider nearest to you, please call (800) 426-9400 between 6:30 A.M. and 5:30 P.M. Pacific time, Monday through Friday, excluding holidays. In Canada, call (800) 563-9048 between 8:00 A.M. and 8:00 P.M. Eastern time, Monday through Friday, excluding holidays.

Microsoft TechNet

Microsoft TechNet is an annual information service created for those who support or educate end users, administer networks or databases, create automated solutions and recommend or evaluate information technology solutions.  Microsoft TechNet gives you the answers you need, when you need them by providing timely, comprehensive and in-depth information on Microsoft products and on supporting and administering Microsoft-based solutions via the monthly Microsoft TechNet CD and monthly TechNet Supplemental (Drivers & Patches) CD.

For more information about Microsoft TechNet, in the United States and Canada, call (800) 344-2121, dept. 3013, between 7:00 A.M. and 7:00 P.M. Central time, Monday through Friday.

See also

Electronic Services

Priority Support

Text Telephone

Other Support Options


Product Support Outside the United States and Canada

Area	Telephone Numbers
Argentina	Microsoft de Argentina S.A. Customer Service: (54) (1) 8145105 (54) (1) 8144807 (54) (1) 8144808 (54) (1) 8117199 Fax: (54) (1) 8140372 Technical Support: (54) (1) 8151521
Australia	Microsoft Pty. Ltd. Fax: (61) (02)8050519 Sales Information Centre: (61) (02) 8702100 Installation Support: (61) (02) 8702132 Bulletin Board Service: (61) (02) 8785200 Technical Support: (61) (02) 8702131
Austria	Microsoft Ges.m.b.H. Phone: 022268 76 07 Fax: 022268 16 2710 Information: 06606520 Prices, updates, etc.: 06606520 CompuServe: GO MSEURO (Microsoft Central Europe) General information about the Microsoft Support Network in Central Europe: FAX: 0049/2622/167006
Belgium	Microsoft NV Phone: 027303911 Customer Service: 027303922 CompuServe: 022150530 (GO MSBEN) Bulletin Board: 027303911 (1200/2400/9600 bd, 8N1, ANSI) Technical Support: 025133274 (Dutch speaking) 025023432 (English speaking) 025132268 (French speaking)
Bolivia	See Argentina
Brazil	Microsoft Informatica Ltda. Phone: (55) (11) 5304455 Fax: (55) (11) 2402205 Technical Support Phone: (55) (11) 8710090 Technical Support Fax: (55) (11) 2411157 Technical Support Bulletin Board Service: (55) (11) 8724106
Canada	Microsoft Canada Inc. Head Office Phone: 1 (905) 5680434 Customer Support Centre: 1 (800) 5639048 Microsoft Support Network: Priority Support Information: 1 (800) 6687975 Text Telephone (TT/TDD) 1 (905) 5689641 Technical Support Bulletin Board Service: 1 (905) 5073022
Caribbean	Microsoft Caribbean, Inc. Phone: (809) 2733600 Fax: (809) 2733636 Technical Support: (214) 7149100
Chile	Microsoft Chile S.A. Phone: 56 2 218 5771 56 2 218 5711 56 2 218 6966 Fax: 56 2 233 5917 Customer Service: 56 2 218 5399
Colombia	Microsoft Colombia Phone: (571) 618 2245 Fax:(571) 618 2269 Technical Support: (571) 618 2255
Czech Republic	Microsoft Panská 6/ I 11000 Praha 1 Phone (+42) (2) 268320 or 27 Fax: (+42) (2) 266020 Technical Support: Phone: (+42) (2) 245 10554
Denmark	Microsoft Denmark AS Phone: (45) (44) 89 01 11 Microsoft Sales Support: (45) (44) 89 01 90 Microsoft FaxSvar: (45) (44) 89 01 44 Microsoft BBS: (45) (44) 66 90 46 (Document 303030 in FaxSvar contains detailed instructions) Technical Support: (45) (44) 89 01 11
Dubai	Microsoft Middle East Phone: (971) 4 513 888 Fax: (971) 4 527 444
Ecuador	Corporation Microsoft del Ecuador S.A. Technical Support: (593) (2) 463094
England	See United Kingdom
Finland	Microsoft OY Phone: (0358) (90) 525 502 500 Microsoft FaxSvar: (46) (0)8 752 29 00 (Information in Swedish and English) Microsoft BBS: (46) (0) 8 750 47 42 (Information in Swedish and English) For Technical Support, please contact your local dealer.
France	Microsoft France Phone: (33) (1) 69864646 Fax: (33) (1) 64460660 Telex: MSPARIS 604322 Technical Support Phone: (33) (1) 69861020 Technical Support Fax: (33) (1) 69280028 Fax Information Service: (33) 36701313
French Polynesia	See France
Germany	Microsoft GmbH Phone: 08931760 Fax: 08931761000 Telex: (17) 89 83 28 MS GMBH D Information: 0893176 1199 Prices, updates, etc.: 0893176 1199 CompuServe: GO MSEURO (Microsoft Central Europe) Bulletin board, device drivers, tech notes: Btx: *microsoft# or *610808000#  General information about the Microsoft Support Network in Central Europe: FAX: 02622/167006
Greece	Microsoft Hellas, S.A. Phone: (30) (1) 6893631 through (30) 1 6893635 Fax: (30) (1) 6893 636
Hong Kong	Microsoft Hong Kong Limited Fax: (852) 5602217 Technical Support: (852) 8044222
Hungary	Microsoft Hungary Phone: (+36) (1) 2691212 Fax: (+36) (1) 269 1030 Technical Support: Phone: (36) (0)1/1172289
Ireland	See United Kingdom
India	Microsoft India Phone: (01) (91) 646 0694, 646 0767, 646 0813 Fax: (01) (91) 6460813
Israel	Microsoft Israel Ltd. Phone: 97236130833 Fax: 97236130834
Italy	Microsoft SpA Phone: (39) (2) 703921 Fax: (39) (2) 70392020 Customer Service (Prices, new product info, product literature): (39) (2) 70398359 Bulletin Board: (39) (2) 70300102 Technical Support: (39) (2) 70398351
Japan	Microsoft Company Ltd. Phone: (81) (3) 54542490 Fax: (81) (3) 54547972 Channel Marketing (Presales Product Support) Information Center Phone: (81) (3) 54542300 Fax: (81) (3) 54547951 Customer Service Phone (Version upgrade/Registration) Phone: (81) (3) 54542305 Fax: (81) (3) 54547952 PSS Technical Support Fax: (81) (3) 54547955
Korea	Microsoft CH Phone: (82) (2) 5314500 Fax: (82) (2) 5311724 Technical Support: (82) (2) 5314800 Technical Support Fax: (82) (2) 5635194 Technical Support Bulletin Board Service: (82) (2) 5383256
Liechtenstein	See Switzerland (German speaking)
Luxembourg	Microsoft NV Phone: (32) 27303911 Customer Service: (32) 27303922 CompuServe: (32) 22150530 (GO MSBEN) Bulletin Board: (32) 27350045 (1200/2400/9600 bd, 8N1, ANSI) Technical Support: (32) 25133274 (Dutch speaking) (32) 25023432 (English speaking) (32) 25132268 (French speaking)
México	Microsoft México, S.A. de C.V. Technical Support: (52) (5) 3250912 Applications and Operating Systems Bulletin Board Service: (52) (5) 5905988 (1200/2400 baud, 8 bits, No parity, 1 stop bit, ANSI terminal emulation) User MSMEXICO, NO Password
Netherlands	Microsoft BV Phone: 0250389189 Customer Service: 0250377700 CompuServe: 0206880085 (GO MSBEN) Bulletin Board: 0250334221 (1200/2400/9600 bd, 8N1, ANSI) Technical Support: 0250377877 (Dutch speaking) 0250377853 (English speaking)
New Zealand	Microsoft New Zealand Ltd Phone: 64 (9) 3583724 Fax: 64 (9) 3583726 Technical Support: Phone: 64 (9) 3575575 Fax: 64 (9) 3580092
Northern Ireland	See United Kingdom
Norway	Microsoft Norway AS Phone: (47) (22) 02 25 50 Microsoft Sales Support: (47) (22) 02 25 80 Microsoft BBS: (47) 22 18 22 09 (Document 404040 in FaxSvar contains detailed instructions) Microsoft FaxSvar: (47) (22) 02 25 70 Technical Support: (47) (22) 02 25 50
Papua New Guinea	See Australia
Paraguay	See Argentina
Poland	Microsoft Sp.z o.o. ul. Grzybowska 80/82 00844 Warszawa Phone: (+48) (2) 661543 Fax: (+48) (2) 6615434 Technical Support: Phone: (+48) (2) 6216793 or (+48) (71) 441357
Portugal	MSFT, Lda. Phone: (351) 1 4412205 Fax: (351) 1 4412101
Republic of China	Microsoft Taiwan Corp. Phone: (886) (2) 5043122 Fax: (886) (2) 5043121 Technical Support: (886) (2) 5089501
Republic of Ireland	See United Kingdom
Russia	Microsoft A/O Leningradsky Prospekt80 125178 Moscow Phone: (+7) (502) 224 50 46 Fax: (+7) (502) 224 50 45 Technical Support: Phone:(+7) (095) 2678844 or (+7) (095)1586963
Scotland	See United Kingdom
Singapore	Microsoft Singapore Pte Ltd Phone: (65) 2276833 Fax  : (65) 2276811 Microsoft Download Service BBS : (65) 2276798
Slowenia	See Germany Technical Support Phone: (+386) (61) 1232354
Slovak Republic	Microsoft Panská 6/ I 11000 Praha 1 Phone (+42) (2) 268320 or 27 Fax: (+42) (2) 266020 Technical Support: Phone: (+42) (7) 312083
South Africa	Microsoft South Africa Phone: (27) 11 445 0000 Fax: (27) 11 445 0045 or (27) 11 445 0046 Technical Support (Toll Free): 0 802 11 11 04 (Toll): (2) 11 445 0100 Customer Service Centre: (27) 11 445 0145
Spain	Microsoft Iberica SRL Phone: (34) (1) 8040000 Fax: (34) (1) 8038310 Technical Support: (34) (1) 8039960
Sweden	Microsoft AB Phone: (46) (08) 752 09 29 Sales Support: (46) (8) 752 56 30 Microsoft FaxSvar: (46) (0)8 752 29 00 Microsoft BBS: (46) (8) 750 47 42 (Document 202020 in FaxSvar contains detailed instructions) Information on Technical Support: (46) (8) 752 09 29
Switzerland	Microsoft AG Phone: 01839 61 11 Fax: 01831 08 69 Prices, updates, etc.: 01/839 61 11 CompuServe: GO MSEURO(Microsoft Central Europe) Documentation: Phone: 155 59 00 Fax: 064224294, Microsoft InfoService, Postfach, 8099 Zürich Technical support (French speaking): 022738 96 88 General information about the Microsoft Support Network in Central Europe: FAX: 0049/2622/167006
Turkey	Microsoft Turkey Phone: (90) 212 2585998 Fax: (90) 212 2585954
United Kingdom	Microsoft Limited Product Support Services Bulletin Board Service Microsoft KeyData: (01734) 270065 (up to 14.4Kbaud, n, 8, 1)  Faxback Information Service Microsoft KeyFax: (01734) 270080 Telephone Support Developer Support: (01734) 270414 Advanced Systems Support: (01734) 270007  Microsoft Ltd Microsoft Information Centre: (0345) 002000 Microsoft Ltd fax: (01734) 270002 Microsoft Ltd phone: (01734) 270001
Uruguay	See Argentina
Venezuela	Corporation MS 90 de Venezuela S.A. Other information: 58.2.910008 58.2.914739 58.2.913342 Fax: 58.2.923835 Technical Support: 58.2.910046 58.2.910510
Wales	See United Kingdom


Server Properties Dialog Box

In the Server Properties dialog box, find the items appropriate to your configuration, and supply information as shown in the following list. Additionally, in the Server Properties dialog box, you can view the server's status, as described in server status possibilities, or you can use the Addons button to access programs such as the SNA Server Trace Options utility.

Comment

Optionally, type a comment of up to 25 characters.

Network Name

If this SNA server will accept incoming calls or be used for APPC (which includes 5250 terminal emulation), it is recommended that you type a Network Name for the server.

The Network Name works with the Control Point Name to identify a system. If either of these parameters is supplied, the other should also be supplied.

If you will be connecting to an AS/400 computer, see also Note About AS/400 Computers.

If you will be connecting to a host system with VTAM or NCP, see also Note About SNA Server Parameters and VTAM.

Control Point Name

If this SNA server will accept incoming calls or be used for APPC (which includes 5250 terminal emulation), it is recommended that you type a Control Point Name for the server.

The Control Point Name works with the Network Name to identify a system. If either of these parameters is supplied, the other should also be supplied.

If you will be connecting to an AS/400 computer, see also Note About AS/400 Computers.

If you will be connecting to a host system with VTAM or NCP, see also Note About SNA Server Parameters and VTAM.

For a table showing configuration parameters for the AS/400 environment, see AS/400 Configuration. For information about working in multiple domains, see Multiple Domains in an SNA Server Installation.


Configuring Server Broadcasts

Server broadcasts are the method of communication used between SNA servers. Configure settings in the Server Broadcasts dialog box to ensure that your SNA servers use the appropriate protocols for communication with clients and other servers. You need to configure server broadcasts only once for the domain.

Note  Choose only the protocols you need, because sending unneeded broadcasts can significantly decrease network efficiency. See Note About Protocols Available and Note About Optimizing Efficiency.

For information about setting up a server to support Macintosh clients, see the Microsoft SNA Server Installation Guide.

To configure server broadcasts and other communication items

1	Select the client-server protocol(s) that you need for server broadcasts between SNA servers. See Note About Protocols Available. The options are:

Microsoft Networking (Named Pipes)

Novell NetWare (IPX/SPX)

Banyan VINES/IP

Windows Sockets (TCP/IP)

Route Server Broadcasts over IP routers

See Note About Server Broadcasts Over IP Routers.

2	Select the types of support needed for earlier software versions:

SNA Server 2.0 servers in the same domain

DCA/Microsoft Comm Server client support

See Note About Support for Earlier Software Versions.

3	If you did not select any support for earlier software versions, you can specify the number of seconds for the Mean Time between Server Broadcasts.

Specifying a larger value causes less demand on the network (since broadcasts occur less often). However, a smaller value compensates better for loss of broadcast messages (which by definition are not guaranteed to be received).

The range is from 45 through 65535 seconds; the default is 60 seconds.

4	To accept the settings, choose OK. To exit the dialog box without accepting the settings, choose Cancel.


SNA Server Additions Dialog Box

Select the SNA Server addition you want to use, then choose the Select button.

For background information about tracing, see Collecting Traces and Other Detailed System Information. For detailed information about selecting trace options, see the Help in the SNA Server Trace Options utility, or the Microsoft SNA Server Administration Guide.


Insert Connection Dialog Box

Select a connection type:

802.2

802.2 is the protocol for token ring or Ethernet connections; the 802.2 protocol is an IEEE standard.

SDLC

Synchronous Data Link Control (SDLC) is used over standard telephone lines (switched lines) or leased lines.

Channel

A Channel connection to a host system.

X.25

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

DFT

Distributed function terminal (DFT) is 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.

Twinax

A twinaxial connection to a peer system.


Insert Dialog Box

Select a Connection or a New Logical Unit:

Connection

802.2

SDLC

Channel

X.25

DFT

Twinax

New Logical Unit

The types of available New Logical Unit (LU) depend on whether you are adding the LU to a server, a host connection a peer connection, or a downstream connection:

Item to which LU will be added	Available New Logical Unit types
SNA server	APPC [Local], used for APPC, which includes 5250 terminal emulation
Host connection	3270, used for 3270 terminal emulation
	APPC [Remote], used for APPC
	LUA, used for LUA
	Downstream
	Range of LUs, for creating 3270, LUA, or downstream LUs in a consecutively numbered range (not available for DFT connections)
Peer connection	APPC [Remote], used for APPC
Downstream connection	Downstream (for associating an existing downstream LU with the downstream connection)


Connection Properties Dialog Box

In the Connection Properties dialog box, find the items appropriate to your configuration, and supply information as follows:

Connection Name

Type a Connection Name.

Comment

Optionally, type a comment of up to 25 characters.

Link Service

Select a link service. If the link service you want is not in the list, choose Cancel, and use the Setup program to install the link service.

See also Note About DFT Link Services.

Remote End

Select the type of remote system for this connection: Host System (mainframe), Peer System, or Downstream. (See also Note About Downstream Connections.)

For DFT, Channel, and Twinax connections, the Remote End is preset.

If this connection will be used for 3270 or LUA LUs, select Host System.

If you will be using dependent APPC, which relies on a host system for communications, select Host System, not Peer System.

For a table showing configuration parameters for the AS/400 environment, see AS/400 Configuration.

For information about how SNA Server parameters correspond to VTAM host parameters, see Working with VTAM, NCP, and/or CICS.

Activation

If Outgoing Calls are included in Allowed Directions, select an Activation setting:

On Server Startup  Select this option if you want the connection to be readily available whenever the server is started.

On Demand  Select this option if you want the connection to be started when needed, and stopped when not in use.

By Administrator  Select this option if you want the administrator to control the connection on a case-by-case basis.

See also Note on Activation and Allowed Directions.

Allowed Directions

Select the allowed call direction(s), Outgoing Calls and/or Incoming Calls.

If you are configuring an SDLC connection that will accept incoming calls, see also Note on Encoding for Incoming-Call Connections.

For DFT, Channel, and Twinax connections, the allowed call direction of Outgoing Calls is automatically selected.

Virtual Circuit Type (X.25 connections only)

If you are configuring an X.25 connection, select the type of circuit used by the connection:

Switched (SVC)

Permanent (PVC)

To continue configuring an 802.2, SDLC, X.25, or Channel connection, choose Setup.

For a DFT or Twinax connection, the configuration is complete. To accept the settings, choose OK; to exit the dialog box without accepting the settings, choose Cancel.

To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


802.2 Setup Dialog Box

In the 802.2 Setup dialog box, find the items appropriate to your configuration, and supply information as follows:

Remote Network Address

Type the Remote Network Address of the computer with which you will communicate on this connection.

For more information about the Remote Network Address, see Using Remote Node Identifiers. For information about determining the local network address for your token ring or Ethernet adapter, see Note on Local Adapter Address.

Local Node ID

Type the Local Node ID. Use the same Local Node ID for all connections and link services on a particular server.

Note  Do not use 000 or FFF for the first three digits; these values are reserved.

Network Name (Remote Node)

If instructed to by the administrator of a remote host, peer, or downstream system, and if you are using Format 3 XIDs, type the Network Name of the remote system. Format 3 is the default XID type.

The Network Name works with the Control Point Name to identify a system. If either of these parameters is supplied, the other should also be supplied.

If you will be connecting to an AS/400 computer, see Note About AS/400 Computers.

If you will be connecting to a host system with VTAM or NCP, see Note About Connection Parameters and VTAM.

For more information about Network Name (Remote Node), see Using Remote Node Identifiers.

Control Point Name (Remote Node)

If instructed to by the administrator of a remote host, peer, or downstream system, and if you are using Format 3 XIDs, type the Control Point Name of the remote system. Format 3 is the default XID type.

The Control Point Name works with the Network Name to identify a system. If either of these parameters is supplied, the other should also be supplied.

If you will be connecting to an AS/400 computer, see Note About AS/400 Computers.

If you will be connecting to a host system with VTAM or NCP, see Note About Connection Parameters and VTAM.

For more information about Control Point Name (Remote Node), see Using Remote Node Identifiers.

Remote Node ID

If instructed to by the administrator of a remote host, peer, or downstream system, type the Remote Node ID.

Note  Do not use 000 or FFF for the first three digits; these values are reserved.

For more information about the Remote Node ID, see Using Remote Node Identifiers.

After specifying basic 802.2 settings, choose a button according to the following:

To configure advanced settings, choose Advanced, and see 802.2 Setup Dialog Box (Advanced).

To accept the settings, and use the advanced settings set by default or previously configured, choose OK.

To exit the dialog box without accepting the settings, choose Cancel.

To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


802.2 Setup Dialog Box (Advanced)

SNA Server is designed to provide reasonable defaults for connections whenever possible, especially for advanced settings.

After choosing Advanced in the 802.2 Setup dialog box, find the items appropriate to your configuration, and supply information as follows:

XID Type

Select the XID Type. Most systems use Format 3.

If you want to use independent APPC LUs on this connection, you must select Format 3.

When SNA Server is configured to use Format 0 over a host connection, the host treats it as a PU type 2.0, and so SNA Server exercises only its PU type 2.0 capabilities. When SNA Server establishes a host or peer connection using Format 3 and independent LUs, SNA Server exercises its PU type 2.1 capabilities.

Remote SAP Address

Type the Remote SAP Address.

For most installations, you should leave this address at the default value of 04.

Retry Limit

Specify the number of times that the local system should retransmit a frame if no response is received from the remote system.

Max BTU Length

Specify the maximum for the BTU length.

See Note About Max BTU Length.

XID Retries

Specify the number of times that the local system should retransmit an XID (an identifying message) if no response is received from the remote system.

Response (t1) Timeout

Select a value for the Response (t1) Timeout. See Selecting a Response Timeout and Note About Timeouts for 802.2.

Receive ACK (t2) Timeout

Select a value for the Receive ACK (t2) Timeout. See Selecting a Receive ACK Timeout and Note About Timeouts for 802.2.

Inactivity (ti) Timeout

Select a value for the Inactivity (ti) Timeout. See Selecting an Inactivity Timeout and Note About Timeouts for 802.2.

Receive ACK Threshold (frames)

Specify the maximum number of frames that the local system can receive from the remote system before sending a response. Set this to a value less than the Unacknowledged Send Limit, so that the local system acknowledges received transmissions more frequently than it expects responses to sent transmissions.

Unacknowledged Send Limit (frames)

Specify the maximum number of frames that the local system can send without receiving a response from the remote system. This parameter is sometimes called the send window size.

To exit the dialog box without accepting the configuration settings, choose Cancel. To accept the settings, choose OK.

To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


SDLC Setup Dialog Box

In the SDLC Setup dialog box, find the items appropriate to your configuration, and supply information as follows:

Dial Data

If this connection uses a switched line and the phone number is not stored in the modem, type the Dial Data. With a leased SDLC line, this field is unavailable.

For information about the available methods for supplying a phone number to the modem, see Phone Number Storage and Modem Types.

Local Node ID

If this connection uses a switched SDLC line (standard telephone line) to connect to a host system, type the Local Node ID. Use the same Local Node ID for all connections and link services on a particular server.

If this connection uses a leased SDLC line, you can use the default for the Local Node ID.

Note  Do not use 000 or FFF for the first three digits; these values are reserved.

Network Name (Remote Node)

If instructed to by the administrator of a remote host, peer, or downstream system, and if you are using Format 3 XIDs, type the Network Name of the remote system. Format 3 is the default XID type.

The Network Name works with the Control Point Name to identify a system. If either of these parameters is supplied, the other should also be supplied.

If you will be connecting to an AS/400 computer, see Note About AS/400 Computers.

If you will be connecting to a host system with VTAM or NCP, see Note About Connection Parameters and VTAM.

For more information about Network Name (Remote Node), see Using Remote Node Identifiers.

Control Point Name (Remote Node)

If instructed to by the administrator of a remote host, peer, or downstream system, and if you are using Format 3 XIDs, type the Control Point Name of the remote system. Format 3 is the default XID type.

The Control Point Name works with the Network Name to identify a system. If either of these parameters is supplied, the other should also be supplied.

If you will be connecting to an AS/400 computer, see Note About AS/400 Computers.

If you will be connecting to a host system with VTAM or NCP, see Note About Connection Parameters and VTAM.

For more information about Control Point Name (Remote Node), see Using Remote Node Identifiers.

Remote Node ID

If instructed to by the administrator of a remote host, peer, or downstream system, type the Remote Node ID.

Note  Do not use 000 or FFF for the first three digits; these values are reserved.

For more information about the Remote Node ID, see Using Remote Node Identifiers.

After specifying basic SDLC settings, choose a button according to the following:

To configure advanced settings, choose Advanced, and see SDLC Setup Dialog Box (Advanced).

To accept the settings, and use the advanced settings set by default or previously configured, choose OK.

To exit the dialog box without accepting the settings, choose Cancel.

To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


SDLC Setup Dialog Box (Advanced)

SNA Server is designed to provide reasonable defaults for connections whenever possible, especially for advanced settings.

After choosing Advanced in the SDLC Setup dialog box, find the items appropriate to your configuration, and supply information as follows:

XID Type

Select the XID Type. Most systems use Format 3.

If you want to use independent APPC LUs on this connection, you must select Format 3.

When SNA Server is configured to use Format 0 over a host connection, the host treats it as a PU type 2.0, and so SNA Server exercises only its PU type 2.0 capabilities. When SNA Server establishes a host or peer connection using Format 3 and independent LUs, SNA Server exercises its PU type 2.1 capabilities.

Encoding

Select the encoding scheme for your modem to use.

Your modem must use the same encoding scheme as the modem at the remote computer.

See also Note on Encoding and VTAM and Note on Encoding for Incoming-Call Connections.

Duplex

Select the setting that matches your modem:

For a half-duplex modem, select Half. If none of your adapters were installed with the Constant RTS option set, you can only choose half-duplex.

For a full-duplex modem, select Full. If you want to use the full-duplex setting, one or more of your adapters must have the Constant RTS option set (at installation).

See also Note About Adapters.

Most SNA servers will use the default, Half.

Data Rate

Select the Data Rate.

Check your adapter and modem manuals to find out if the data rate can or must be set for your equipment.

Poll Address

Type a two-digit hexadecimal number. Contact the administrator of the remote system to determine the appropriate value. See Note on Poll Address.

Note  Do not use 00 or FF. These values are reserved.

Poll Rate

If the remote system is a peer or downstream system, specify the poll rate (in polls per second).

Poll Timeout (for peer or downstream connections)

Specify the length of time, in tenths of a second, for the local system to wait for a response to a poll before trying again. Too small a timeout can cause connection problems. See Note About Sessions Affected.

Poll Retry Limit (for peer or downstream connections)

Specify the number of times for the local system to poll the remote system if there is no response. See Note About Sessions Affected.

Contact Timeout

Specify the length of time, in tenths of a second, that the local system should wait between attempts to make a connection with a remote system.

This parameter is ignored for incoming calls.

Contact Retry Limit

Specify the maximum number of times the local system should attempt to make a given connection.

This parameter is ignored for incoming calls.

Idle Timeout (for host or peer connections)

Specify the length of time, in tenths of a second, for the local system to wait for a response to a transmission before trying again.  Too small a timeout can cause connection problems. See Note About Sessions Affected.

Idle Retry Limit (for host or peer connections)

Specify the number of times for the local system to try to send data to the remote system if there is no response. See Note About Sessions Affected.

Max BTU Length

Specify the maximum for the BTU length.

See Note About Max BTU Length.

Multidrop Primary

If this is a leased SDLC line to downstream systems, and this server will be the primary station for a multidrop connection, select this box. For information about configuring for multidrop, see Configuring Multidrop Connections.

Select Standby

If you want your modem's standby line to be set to on, select this check box.

Check your adapter and modem manuals to find out if standby can be set for your equipment.

Switched Connection Establishment Timeout

If this connection uses a switched SDLC line (standard telephone line), specify the number of seconds that will be allowed for the user or modem to dial and make a connection to the remote computer. If the dialing will be done manually, be sure to allow enough time for the user to dial, wait for an answer, and make the connection.

This parameter is ignored by incoming calls.

To exit the dialog box without accepting the configuration settings, choose Cancel. To accept the settings, choose OK.

To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


X.25 Setup Dialog Box

In the X.25 Setup dialog box, find the items appropriate to your configuration, and supply information as follows. See also Note About Adapters for X.25.

Remote X.25 Address

Type the Remote X.25 Address to connect to.

For more information about the Remote X.25 Address, see Using Remote Node Identifiers. For information about determining the local network address for your X.25 adapter, see Note on Local Adapter Address.

Local Node ID

If this connection is using SVC, type the Local Node ID. Use the same Local Node ID for all connections and link services on a particular server.

If this connection is using PVC, you can use the default for the Local Node ID.

Note  Do not use 000 or FFF for the first three digits; these values are reserved.

Network Name (Remote Node)

If instructed to by the administrator of a remote host, peer, or downstream system, and if you are using Format 3 XIDs, type the Network Name of the remote system. Format 3 is the default XID type (configured in Advanced X.25 settings).

The Network Name works with the Control Point Name to identify a system. If either of these parameters is supplied, the other should also be supplied.

If you will be connecting to an AS/400 computer, see Note About AS/400 Computers.

If you will be connecting to a host system with VTAM or NCP, see Note About Connection Parameters and VTAM.

For more information about Network Name (Remote Node), see Using Remote Node Identifiers.

Control Point Name (Remote Node)

If instructed to by the administrator of a remote host, peer, or downstream system, and if you are using Format 3 XIDs, type the Control Point Name of the remote system. Format 3 is the default XID type (configured in Advanced X.25 settings).

The Control Point Name works with the Network Name to identify a system. If either of these parameters is supplied, the other should also be supplied.

If you will be connecting to an AS/400 computer, see Note About AS/400 Computers.

If you will be connecting to a host system with VTAM or NCP, see Note About Connection Parameters and VTAM.

For more information about Control Point Name (Remote Node), see Using Remote Node Identifiers.

Remote Node ID

If instructed to by the administrator of a remote host, peer, or downstream system, type the Remote Node ID.

Note  Do not use 000 or FFF for the first three digits; these values are reserved.

For more information about the Remote Node ID, see Using Remote Node Identifiers.

After specifying basic X.25 settings, choose a button according to the following:

To configure advanced settings, choose Advanced, and see X.25 Setup Dialog Box (Advanced).

To accept the settings, and use the advanced settings set by default or previously configured, choose OK.

To exit the dialog box without accepting the settings, choose Cancel.

To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


X.25 Setup Dialog Box (Advanced)

SNA Server is designed to provide reasonable defaults for connections whenever possible, especially for advanced settings.

After choosing Advanced in the X.25 Setup dialog box, find the items appropriate to your configuration, and supply information as follows. See also Note About Adapters for X.25.

XID Type

Select the XID Type. Most systems use Format 3.

If you want to use independent APPC LUs on this connection, you must select Format 3.

When SNA Server is configured to use Format 0 over a host connection, the host treats it as a PU type 2.0, and so SNA Server exercises only its PU type 2.0 capabilities. When SNA Server establishes a host or peer connection using Format 3 and independent LUs, SNA Server exercises its PU type 2.1 capabilities.

Packet Size (PVC only)

For a PVC channel, select the maximum number of data bytes (not header bytes) to be sent in a frame. Obtain this value from your network provider.

Window Size (PVC only)

For a PVC channel, select the maximum number of frames that the local system can send without receiving a response from the remote system. Obtain this value from the administrator of the remote host or peer system.

PVC Alias (PVC only)

For a PVC channel, type the number that identifies the channel: 1 for the first channel, 2 for the second, and so on.

Max BTU Length

Specify the maximum for the BTU length.

See Note About Max BTU Length.

Facility Data (SVC only)

For an SVC channel, specify the codes for any Facility Data required by your network provider or by the administrator of the remote system. You can specify as many as 126 hexadecimal characters (63 hexadecimal bytes). For detailed information about how facility data is coded, see Facility Data Structuring.

User Data (SVC only)

For an SVC channel, specify the codes for any User Data required by your network provider. Type an even number of hexadecimal characters, up to the maximum of 32 characters.

To exit the dialog box without accepting the configuration settings, choose Cancel. To accept the settings, choose OK.

To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


FOLLOWING TOPIC IS BASICALLY THE SAME AS A TOPIC IN TPC1.RTF


Connection Activation Limits Dialog Box

Supply activation limits for the connection:

Maximum number of attempts

Select the number of attempts for SNA Server to make when trying to establish or re-establish a connection. After making this number of attempts, SNA Server makes an entry in the event log and stops trying. The range is from 1 through No Limit; the default is No Limit.

Delay after failed attempts

Select the length of time for SNA Server to wait between attempts to establish or re-establish a connection. The range is from 5 seconds through 255 seconds (in multiples of 5); the default is 10 seconds.


Insert LU Dialog Box

Select a New Logical Unit (LU). The types available depend on whether you are adding the LU to a server, a host connection, a peer connection, or a downstream connection:

Item to which LU will be added	Available New Logical Unit types
SNA server	APPC [Local], used for APPC, which includes 5250 terminal emulation
Host connection	3270, used for 3270 terminal emulation
	APPC [Remote], used for APPC
	LUA, used for LUA
	Downstream
	Range of LUs, for creating 3270, LUA, or downstream LUs in a consecutively numbered range (not available for DFT connections)
Peer connection	APPC [Remote], used for APPC
Downstream connection	Downstream (for associating an existing downstream LU with the downstream connection)


3270 LU Properties

In the New 3270 LU Properties or the 3270 LU Properties dialog box, supply the information in the following list.

Note  After making configuration changes, to put the changes into effect, restart the SNA server, as described in Restarting an SNA Server.

LU Number

Type the LU Number.

LU Name

Type the LU Name.

Connection

The connection for this LU is shown. The connection cannot be changed from this dialog box. To change the connection after configuring the LU, see Moving an LU.

Pool

If the LU has already been assigned to a pool, the pool name appears here.

Comment

Optionally, type a comment of up to 25 characters.

LU Type

Select Display if the LU will be used for display (terminal emulation). Select Printer if the LU will be used to print from the host system to a local printer or a local area network printer.

Display Model

If you select Display for the LU Type, you can select a Display Model.

When an LU is assigned to a pool, the display model setting for the pool overwrites the setting of the LU, and the setting displayed in the 3270 LU Properties dialog box is dimmed.

Some emulators can only emulate certain display models. For more information, see your emulator documentation.

Model can be overridden

Select this check box to allow the user to override the display model type by using a 3270 terminal emulation program. See also Note on LU and LU Pool Settings.


3270 LU Properties

In the New 3270 LU Properties or the 3270 LU Properties dialog box, supply the information in the following list.

Note  After making configuration changes, to put the changes into effect, restart the SNA server, as described in Restarting an SNA Server.

Port Number

Type the number of the DFT adapter that will be used. (This is not the port of the 3174.)

LT Number

Type the logical terminal number as configured at the 3174 for this coaxial cable.

LU Name

Type the LU Name.

Connection

The connection for this LU is shown. The connection cannot be changed from this dialog box. To change the connection after configuring the LU, see Moving an LU.

Pool

If the LU has already been assigned to a pool, the pool name appears here.

Comment

Optionally, type a comment of up to 25 characters.

LU Type

Select Display if the LU will be used for display (terminal emulation). Select Printer if the LU will be used to print from the host system to a local printer or a local area network printer.

Display Model

If you select Display for the LU Type, you can select a Display Model.

When an LU is assigned to a pool, the display model setting for the pool overwrites the setting of the LU, and the setting displayed in the 3270 LU Properties dialog box is dimmed.

Some emulators can only emulate certain display models. For more information, see your emulator documentation.

Model can be overridden

Select this check box to allow the user to override the display model type by using a 3270 terminal emulation program. See also Note on LU and LU Pool Settings.


Range for Port Number

The range is from 1 through 4.


Range for LT Number

The range is from 1 through 5.


Add LU Range Dialog Box

In the Add LU Range dialog box, supply information as follows:

Base LU Name

Type the Base LU Name.

First LU Number

Type the first LU Number in the range.

Number of LUs

Type the number of LUs that you want in the LU range. Check with the host administrator to find out how many LUs are available for your system.

Note  The LU numbers generated for an LU range are sequential. If the numbers assigned by your host administrator are not sequential, you can modify the numbers of individual LUs after they have been created.

When you have typed the appropriate LU range values, choose one of the following:

To modify the extension numbering format (displayed under Selected LU Range), choose Options. See Modifying the Extension Numbering Format.

To exit the dialog box without accepting the settings, choose Cancel.

To accept the settings and begin configuring the properties for the LU range, choose OK.


3270 LU Range Properties Dialog Box

In the 3270 LU Range Properties dialog box, supply the information in the following list.

Note  After making configuration changes, to put the changes into effect, restart the SNA server, as described in Restarting an SNA Server.

LU Numbers

The range of LU numbers that you entered appears here.

LU Names

The range of LU names that you entered appears here.

Connection

The connection for the LU range is shown. The connection cannot be changed from this dialog box. To change the connection after configuring the LUs, see Moving an LU.

Comment

Optionally, type a comment of up to 25 characters.

LU Type

Select Display if the LUs will be used for display (terminal emulation). Select Printer if the LUs will be used to print from the host system to a local printer or a local area network printer.

Display Model

If you select Display for the LU Type, you can select a Display Model.

Some emulators can only emulate certain display models. For more information, see your emulator documentation.

Model can be overridden

Select this check box to allow the user to override the display model type by using a 3270 terminal emulation program.


LUA LU Range Properties Dialog Box

In the LUA LU Range Properties dialog box, supply the information in the following list.

Note  After making configuration changes, to put the changes into effect, restart the SNA server, as described in Restarting an SNA Server.

LU Numbers

The range of LU numbers that you entered appears here.

LU Names

The range of LU names that you entered appears here.

Connection

The connection for the LU range is shown. The connection cannot be changed in this dialog box. To change the connection after configuring the LUs, see Moving an LU.

Comment

Optionally, type a comment of up to 25 characters.

LUA High Priority LU

Select this check box to give preference to these LUs over low-priority LUs.


LUA LU Properties

In the New LUA LU Properties or LUA LU Properties dialog box, supply information according to the following list.

Note  After making configuration changes, to put the changes into effect, restart the SNA server, as described in Restarting an SNA Server.

LU Number

Type the LU Number.

LU Name

Type the LU Name.

Connection

The connection for this LU is shown. The connection cannot be changed in this dialog box. To change the connection after configuring the LU, see Moving an LU.

Pool

If the LU has already been assigned to a pool, the pool name appears here.

Comment

Optionally, type a comment of up to 25 characters.

High Priority LU

Select this check box to give preference to this LU over low-priority LUs. See also Note on LU and LU Pool Settings.


LUA LU Properties

In the New LUA LU Properties or LUA LU Properties dialog box, supply information according to the following list.

Note  After making configuration changes, to put the changes into effect, restart the SNA server, as described in Restarting an SNA Server.

Port Number

Type the number of the DFT adapter that will be used. (This is not the port of the 3174.)

LT Number

Type the logical terminal number as configured at the 3174 for this coaxial cable.

LU Name

Type the LU Name.

Connection

The connection for this LU is shown. The connection cannot be changed in this dialog box. To change the connection after configuring the LU, see Moving an LU.

Pool

If the LU has already been assigned to a pool, the pool name appears here.

Comment

Optionally, type a comment of up to 25 characters.

High Priority LU

Select this check box to give preference to this LU over low-priority LUs. See also Note on LU and LU Pool Settings.


LU 6.2 Partner LUs Dialog Box

The LU 6.2 Partner LUs dialog box appears when you choose the Partners button from an APPC LU properties dialog box.

If you enabled automatic partnering for the selected LU, and also enabled automatic partnering for one or more partner LUs and modes, the LU-LU pairs that have automatically been generated appear in the LU 6.2 Partner LUs dialog box. For communication with an AS/400, be sure that QPCSUPP is the only mode used.

In the LU 6.2 Partner LUs dialog box, select buttons as appropriate:

Add

To add a partner to the list for this LU, choose Add. Then, in the Add APPC LU Partner dialog box, select the partner LU and mode for the LU-LU pair. See Note About Uniqueness of Pairs.

For communication with an AS/400, use the QPCSUPP mode (provided with SNA Server).

If you have not already configured the other LU for this LU-LU pair, close or cancel all dialog boxes, and in the Servers and Connections window, begin the process of assigning and configuring the new LU. See Assigning a Local or Remote APPC LU.

A number of standard modes (including QPCSUPP) are provided with SNA Server, as described in Properties of Standard Modes. If you need to create additional modes, choose the Modes button and see Configuring Modes for LU-LU Pairs.

Delete

To delete a partner LU from the list, select the partner to delete, and choose Delete.

Modes

SNA Server keeps a list of modes available for LU-LU pairs; to change the list by adding, deleting, or configuring modes, select Modes. A number of standard modes are provided with SNA Server; if you need to create additional modes, choose the Modes button and create them before adding LU-LU pairs. For more information, see Properties of Standard Modes and Configuring Modes for LU-LU Pairs.

Note  To associate an existing mode with an LU-LU pair, choose Add, not Modes.

When you are finished configuring the partners in the LU 6.2 Partner LUs dialog box, choose Close.

To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


Add APPC LU Partner Dialog Box

In the Add APPC LU Partner dialog box, select the partner LU and mode for the LU-LU pair. See Note About Uniqueness of Pairs.

For communication with an AS/400, use the QPCSUPP mode.

If you have not already configured the other LU for this LU-LU pair, close or cancel all dialog boxes, and in the Servers and Connections window, begin the process of assigning and configuring the new LU. See Assigning a Local or Remote APPC LU.

A number of standard modes (including QPCSUPP) are provided with SNA Server, as described in Properties of Standard Modes. If you need to create additional modes, choose the Cancel button, then the Modes button, and see Configuring Modes for LU-LU Pairs.

When you have selected the partner LU and mode, choose OK. To exit without selecting a partner LU and mode, choose Cancel.


APPC Mode Properties Dialog Box

For a list of the standard modes available with SNA Server, see Properties of Standard Modes.

Procedures for the APPC Mode Properties Dialog Box

  To add a mode to the list

  To delete a mode

  To modify an existing mode

In the APPC Mode Properties dialog box, find the item(s) appropriate to your configuration, and supply information as follows:

Mode Name

Type a Mode Name.

Comment

Optionally, type a comment of up to 25 characters.

Parallel Session Limit

Specify the maximum number of sessions allowed with this mode. To allow only a single session, specify 1. To allow parallel sessions, specify a value greater than 1. If the local APPC LU to be used with this mode is dependent, specify 1; dependent local APPC LUs cannot have parallel sessions. See also Note on Parallel Session Limits.

Minimum Contention Winner Limit

Specify the Minimum Contention Winner Limit. The sum of the Minimum Contention Winner Limit and the Partner Min Contention Winner Limit must be less than or equal to the Parallel Session Limit.

Partner Min Contention Winner Limit

Specify the Partner Min Contention Winner Limit. The sum of the Partner Min Contention Winner Limit and the Minimum Contention Winner Limit must be less than or equal to the Parallel Session Limit.

Automatic Activation Limit

Specify the number of contention winner sessions to be activated for the local LU whenever the connection for this mode is started. In a local contention winner session, the local LU can initiate conversations without permission from the partner LU.

For single-system APPC (communication between two local LUs on the same system), this field is meaningless.

Enable Automatic Partnering

To allow the mode to be associated with remote LUs and local LUs designated for automatic partnering, use the default setting of Enable Automatic Partnering. To avoid designating the mode as an automatic partner, so that it is only associated with the remote LUs and modes you explicitly choose, clear Enable Automatic Partnering. See Note on Automatic Partnering.

High Priority Mode

Select this check box to give preference to communication with this mode over communication with a low-priority mode.

Pacing Send Count

Specify the maximum number of frames for the local LU to send without an SNA pacing response from the partner LU. If you specify 0, the local LU can send an unlimited number of frames without receiving a response; in this case, the partner LU can negotiate and set a limit on the count.

Pacing Receive Count

Specify the maximum number of frames for the local LU to receive from the partner LU before the local LU sends an SNA pacing response. If you specify 0, the local LU can receive an unlimited number of frames without sending a response.

Max Send RU Size

Specify the maximum size for RUs sent by the TP(s) on the local system.

It is not necessary to set a minimum send RU size, which is 256 on SNA Server.

Max Receive RU Size

Specify the maximum size for RUs received from the TP(s) on the remote system.

It is not necessary to set a minimum receive RU size, which is 256 on SNA Server.

When you are finished with the APPC Mode Properties dialog box, choose Close.


APPC Session Security Dialog Box

Session security for remote LUs is optional.

In the APPC Session Security dialog box, find the item(s) appropriate to your configuration, and supply information as follows:

No Session-Level Security

Select this option to turn off Session-Level Security.

Security Key in Hex

For a security key in hexadecimal, select this option, then type a 16-digit hexadecimal number.

Security Key in Characters

For a security key in characters, select this option, then type an eight-character string. The string can include uppercase and lowercase alphanumeric characters, and the special characters $, @, #, and the period (.).

To exit the dialog box without accepting the configuration settings, choose Cancel. To accept the settings, choose OK.

To put configuration changes into effect, restart the SNA server, as described in Restarting an SNA Server.


Configure CPI-C Names Dialog Box

If you are using applications based on CPI-C, you will need to configure one or more CPI-C symbolic destination names.

In the Configure CPI-C Names dialog box, you can do the following:

To add a name, choose Add.

The CPI-C Symbolic Destination Name Properties dialog box appears. For information, see Configuring Properties for CPI-C.

To delete a name, select the name, then choose Delete.

The name is removed from the list.

To view or edit a name, select the name, then choose Edit.

The CPI-C Symbolic Destination Name Properties dialog box appears. For information, see Configuring Properties for CPI-C.


Error/Audit Logging and Popups Dialog Box

You can use information from Windows NT event logs as you test a configuration or diagnose problems. (For information about the security log, which contains a different set of events, see the Microsoft SNA Server Administration Guide.)

In the Error/Audit Logging and Popups dialog box, select options as follows:

Centralized Event Log Server

Type the name of the server on which Windows NT event logs for this SNA Server installation should be stored, or select a server from the list.

Event log files are stored in WindowsRoot\SYSTEM32\CONFIG, and have a filename extension of EVT. View event logs by using the Windows NT Event Viewer, as described in Viewing Event Logs.

Default Audit Log Level

Select a level:

Detailed problem analysis:   To record all events that can be recorded, select this option.

General information messages:  To record general activity but not all events, select this option.

Significant system events:  To record only major events, select this option.

Audit logging disabled:  To turn off audit logging, select this option.

Route All Server Popup Messages to

Type the name of a server to which pop-up error messages for this SNA Server installation should be routed, or select a server from the list. See Note on Pop-Up Error Messages.


Viewing Event Logs

To view SNA Server event logs:

1	Start the Windows NT Event Viewer. For information, see your Windows NT documentation.

2	From the Log menu in the Event Viewer, choose Application.

Under the Source heading, SNA events are listed with names starting with "SNA."

3	To view more detail about an event, double-click the event listing.


NetView Options Dialog Box

NetView sends alerts back and forth between a host system and PCs. In the NetView Options dialog box, you can specify the connection to which NetView data should be sent.

Send NetView Management Data to Connection

Select a connection. This can be any host connection except a DFT connection.


3270 Response Time Monitor (RTM) Dialog Box

RTM makes data available about the length of time it takes a host to respond during 3270 sessions. RTM is supported only by certain emulators. You should configure RTM settings only if the emulators in your installation support RTM.

Note  If the host RTM settings are different, they can override the SNA Server settings.

In the 3270 Response Time Monitor (RTM) dialog box, supply information as follows:

RTM Data Sent at

Select one or both of the following:

Counter Overflow:  To cause RTM data to be sent to the host when the number of host responses in a given time period overflows the size of the available counter, select this box.

End of Session:  To cause RTM data to be sent to the host at the end of each LU-to-LU session, select this box.

RTM Timers Run Until

Select the point at which RTM will register that a host has responded; this is when RTM stops the timers. (The timers are started when the local system sends data.)

First Data Reaches Screen:  To stop timing when data reaches the local screen, select this option.

Host Unlocks Keyboard:  To stop timing when the host unlocks the local keyboard, select this option.

Host Lets User Send:  To stop timing when the host lets the local computer send more data, select this option.

RTM Thresholds

Specify the cutoff times, in tenths of a second, at which RTM saves its count of host responses, and then restarts the count. For example, you could specify 5, 10, 20, and 50, to save the count of host responses during the intervals from 0.0 to 0.5 seconds, from 0.5 to 1.0 seconds, from 1.0 to 2.0 seconds, and from 2.0 to 5.0 seconds.


Copy Properties Dialog Box

The Copy Properties dialog box allows you to copy properties from the item you selected before you chose the Copy Properties command or pressed F8.

In the Copy Properties dialog box, select the item (connection, LU, or user) to which you want to copy properties, and then choose OK.

If you copy properties to an active service (such as an active connection), the properties take effect when the service is restarted or reset.

If you copy the properties of an APPC LU, you also copy the pairings associated with that LU.

If you copy properties from one user to another, you copy both the assigned LUs or LU pools and the assigned properties.


Move Dialog Box

The Move dialog box allows you to move the connection or LU you selected before you chose the Move command or pressed F7.

In the Move dialog box, select the destination to which you want to move the connection or LU, and then choose OK.


Reorder LU Session Dialog Box

The Reorder LU Session dialog box allows you to change the session number or (for downstream LUs) the downstream LU number of the LU(s) or pool(s) you selected before you chose the Reorder LUs command.

In the Reorder LU Session dialog box, in Before Session Number, type the number that you want the first selected LU or pool to have. When you choose OK, the selected LU(s) or pool(s) are reordered according to the number you specified, and other LU session numbers shift to accommodate.

For more information about reordering LUs, see Reordering LUs in User Lists and Adjusting the Numbering of Downstream LUs.


Insert Dialog Box

In the Insert dialog box, select an option:

New User: Select this option to add a user to the list used by SNA Server.

Before users can be added to this list, they must have accounts on the local area network or the local server.

Add LUs to User: Select this option to assign LUs to the user that you selected before accessing the Insert dialog box.

For a complete list of the steps for configuring for 3270, see Configuring for 3270 Terminal Emulation.


Add Users and Groups Dialog Box

Before users can be added to the list used by SNA Server, they must have accounts on the local area network or the local server.

To add users and groups to the list used by SNA Server

1	In the List Names From box, select the domain from which to list users who have network accounts.

2	From Names, which lists the users and groups who have accounts, select the one you want to add.

3	Choose Add.

4	Repeat steps 2 and 3 as needed.

5	Choose OK.

The window title changes to Users and Groups - [Out of Date], to indicate that the configuration needs to be saved to bring it up to date.

6	On the Toolbar, click  [image].

For a complete list of the steps for configuring for 3270, see Configuring for 3270 Terminal Emulation.


Assigning LUs

To assign an LU to the user, LU pool, or downstream connection that you selected, from the list of available LUs and/or LU pools, select the intended items, then choose OK.

Important  If you are assigning LUs or LU pools to a user, group, or downstream system, assign one LU or LU pool for each session needed. That is, assign multiple LUs or LU pools if multiple sessions are needed. You can assign a pool multiple times to one user or group or to one downstream connection.

When you assign 3270 LUs to user and group accounts with overlapping memberships, some of these assignments override others. See Precedence of Accounts in Determining LU Access.

If the LUs or LU pools that you want to assign have not yet been created, choose Cancel, and see the topics in Configuring LUs or Using LU Pools to Maximize Access: Overview.


Preferences Dialog Box

You can select or clear the following options in the Preferences dialog box:

Option	Result
Enable Toolbar	Turns the display of the Toolbar on or off.
Enable Status Bar	Turns the display of the status bar on or off.
Always Display Advanced Settings	Enables or disables the automatic display of  advanced settings in dialog boxes that contain an Advanced button.
Confirm Mouse Operations	Enables or disables the confirmation prompt following mouse operations.
Save Window Settings on Exit	Enables or disables the saving of window settings on exit from SNA Server Admin. Window settings are the settings made in this dialog box (Preferences), and the settings for window size and shape.


APPC Status Dialog Boxes

The APPC LU Status dialog box provides status information about an APPC LU, including the partner LU(s), mode(s), and connection(s) that the APPC LU is using for LU-LU sessions.

An additional dialog box, available through the Zoom button, provides information about individual APPC LU-LU sessions, and allows you to deactivate one or more sessions.


Server Properties Dialog Box (Offline Configuration)

In the Server Properties dialog box, find the items appropriate to your configuration, and supply information as shown in the following list.

Important  When you specify a server name in the offline version of SNA Server, you must match the server name used in SNA Server Setup at the site where the offline configuration will be used. Otherwise, the offline configuration will not work properly. For more information, see Offline Configuration.

Server Name

Type a server name; the name must match the computer name of an installed SNA server at the site where the configuration will be used.

Note  Specifying a server name in this box only places the name into the offline configuration file. Specifying a server name does not change the name of any computer, nor install SNA Server on any computer. For information about changing a computer name, see your Windows NT documentation. For information about installing SNA Server, see the Microsoft SNA Server Installation Guide or the online Help for the SNA Server Setup program.

Service Name

The service name must be SNASERVR.

Comment

Optionally, type a comment of up to 25 characters.

Network Name

If this SNA server will accept incoming calls or be used for APPC (which includes 5250 terminal emulation), it is recommended that you type a Network Name for the server.

The Network Name works with the Control Point Name to identify a system. If either of these parameters is supplied, the other should also be supplied.

If you will be connecting to an AS/400 computer, see also Note About AS/400 Computers.

If you will be connecting to a host system with VTAM or NCP, see also Note About SNA Server Parameters and VTAM.

Control Point Name

If this SNA server will accept incoming calls or be used for APPC (which includes 5250 terminal emulation), it is recommended that you type a Control Point Name for the server.

The Control Point Name works with the Network Name to identify a system. If either of these parameters is supplied, the other should also be supplied.

If you will be connecting to an AS/400 computer, see also Note About AS/400 Computers.

If you will be connecting to a host system with VTAM or NCP, see also Note About SNA Server Parameters and VTAM.

In addition to specifying server properties, you can choose the Adapters button, and configure one or more adapters for the SNA server, as described in the Microsoft SNA Server Installation Guide.

Important  When you specify properties for an adapter or link service in the offline version of SNA Server, you must match the adapter or link service properties specified in SNA Server Setup at the site where the offline configuration will be used. Otherwise, the offline configuration will not work properly. For more information, see Offline Configuration.


Adapter Properties (Offline Configuration)

In the Adapter Properties for Server servername dialog box, configure adapter and link service properties as described in the Microsoft SNA Server Installation Guide.

Important  When you specify properties for an adapter or link service in the offline version of SNA Server, you must match the adapter or link service properties specified in SNA Server Setup at the site where the offline configuration will be used. Otherwise, the offline configuration will not work properly. For more information, see Offline Configuration.


Backing Up a Configuration

In the Save Configuration As dialog box, you can back up the current configuration:

1	If you need to change drives, in the Drives box, select the desired drive.

2	In the Directories box, select the directory in which you want to back up the current configuration.

3	In the File Name box, type the filename to save the configuration file as, or select a filename from the list.

The default filename extension for backup configuration files is .SNA.

4	Choose OK.

A file that has been saved as a backup configuration file can be restored using the File menu Restore command.


Restoring a Backed-up Configuration

In the Restore Configuration From dialog box, you can restore a backup configuration file, making it the active (displayed) configuration:

1	If you need to change drives, in the Drives box, select the desired drive.

2	In the Directories box, select the directory in which the backup file is located.

3	In the File Name box, type the filename of the backup file, or select a filename from the list.

The default filename extension for backup configuration files is .SNA.

4	Choose OK.


Insert Dialog Box

In the Insert dialog box, select an option:

New Pool: Select this option to add a new pool.

After adding and configuring the pool, add LUs to the pool. For information, see Assigning LUs to an LU Pool. An empty pool provides no LU access.

Add LUs to Pool: Select this option to assign LUs to the LU pool you selected before accessing this dialog box.

For a complete list of the steps for using pools, see Using LU Pools to Maximize Access: Overview.


New Pool Dialog Box

In the New Pool dialog box, carry out the following:

1	Type a Pool Name.

2	Optionally, type a comment of up to 25 characters.

3	Select a Pool Type depending on how the pool will be used: for 3270, for LUA, or for Downstream LUs.

4	For a 3270 LU pool, configure display model settings:

Display Model

Select a Display Model..

Model can be overridden

Select this check box to allow users to override the display model type by using a 3270 terminal emulation program.

5	For an LUA LU pool, select or clear the LUA High Priority LU Pool check box.

Selecting the check box gives preference to communication with LUs in this pool over low-priority communication. By default, the check box is selected.

6	Choose OK.

After configuring the pool, add LUs to the pool. For information, see Assigning LUs to an LU Pool. An empty pool provides no LU access.

For a complete list of the steps for using pools, see Using LU Pools to Maximize Access: Overview.


3270 LU Pool Properties Dialog Box

In the 3270 LU Pool Properties dialog box, find the items appropriate to your configuration, and supply information as follows:

Pool Name

Type a Pool Name.

Comment

Optionally, type a comment of up to 25 characters.

Display Model

Select a Display Model. If there is a conflict between the Display Model setting for the pool and the Display Model setting for an LU in the pool, a message box appears. You can allow the individual LU setting to be changed, or exclude the LU from the pool.

Model can be overridden

Select this check box to allow users to override the display model type by using a 3270 terminal emulation program. If there is a conflict between the model override setting for the pool and the model override setting for an LU in the pool, a message box appears. You can allow the individual LU setting to be changed, or exclude the LU from the pool.

To exit the dialog box without accepting the configuration settings, choose Cancel. To accept the settings, choose OK. After accepting the settings, make sure that LUs have been added to the pool; only a pool that contains LUs provides LU access. See Assigning LUs to an LU Pool.


LUA LU Pool Properties Dialog Box

In the LUA LU Pool Properties dialog box, find the items appropriate to your configuration, and supply information as follows:

Pool Name

Type a Pool Name.

Comment

Optionally, type a comment of up to 25 characters.

LUA High Priority LU Pool

Select this check box to give preference to communication with LUs in this pool over low-priority communication.

If there is a conflict between the priority for the pool and the priority for an LU in the pool, a message box appears. You can allow the individual LU priority to be changed, or exclude the LU from the pool.

To exit the dialog box without accepting the configuration settings, choose Cancel. To accept the settings, choose OK. After accepting the settings, add LUs to the pool; only a pool that contains LUs provides LU access. See Assigning LUs to an LU Pool.


Adding Users and Groups and Setting Permissions

For background information about security with SNA Server, see the Microsoft SNA Server Administration Guide.

To add groups and users to the list of those with SNA Server administrative permissions

1	If you want to add users from another domain, in the List Names from box, select a different domain.

The domains listed are trusted domains.

2	If you want the accounts displayed to include users as well as groups, choose the Show Users button.

3	Under Names, select one or more groups or users.

To select multiple names in sequence, click the first name you want, hold down SHIFT, and click the last name you want.

To select multiple names out of sequence, hold down CTRL as you click the names that you want.

4	Choose the Add button.

The selected group or user name(s) appear in the Add Names box.

5	Repeat steps 3 and 4 as needed.

6	In the Type of Access box, select the permission that you want the listed user(s) or group(s) to have. If multiple names appear in the Add Names box, they will all be assigned the same permission--the last one you select before choosing OK. The permissions for any particular account can easily be changed later. The permissions are as follows:

No Access

With No Access permission in the SNA domain, a user or group cannot run SNA Server Admin or the snacfg command-line program, and cannot read or write the configuration file.

No Access overrides any other permissions that apply to a particular user. For example, if a user belongs to a group that has Read permission, but the user has No Access, the user is not permitted administrative access.

Read (Manage Only)

With Read (Manage Only) permission in the SNA domain, a user or group can run SNA Server Admin and the snacfg command-line program, but only to read (not write to) the configuration file. See Recommendation for Read Permission.

Read/Write

With Read/Write permission in the SNA domain, a user or group can run SNA  Server Admin and the snacfg command-line program, and can read and write to the configuration file. See Recommendation for Read/Write Permission.

Full Control

With Full Control permission in the SNA domain, a user or group can run SNA  Server Admin and the snacfg command-line program; can read and write to the configuration file; can change the administrative permissions assigned to others; and can remove SNA Server software. See Recommendation for Full Control Permission.

7	Choose OK.


Configuring SNA Domain Permissions

For background information about security with SNA Server, see the Microsoft SNA Server Administration Guide.

To configure permissions in the SNA Domain Permissions dialog box

1	To add users or groups to the list of those with permissions in SNA Server, choose the Add button, and use the Add Users and Groups dialog box to select and add the intended users or groups.

2	Under Name, select a group or user for whom you want to specify administrative permissions.

3	In the Type of Access box, select the permission that you want the selected user or group to have:

No Access

With No Access permission in the SNA domain, a user or group cannot run SNA Server Admin or the snacfg command-line program, and cannot read or write the configuration file.

No Access overrides any other permissions that apply to a particular user. For example, if a user belongs to a group that has Read permission, but the user has No Access, the user is not permitted administrative access.

Read (Manage Only)

With Read (Manage Only) permission in the SNA domain, a user or group can run SNA Server Admin and the snacfg command-line program, but only to read (not write to) the configuration file. See Recommendation for Read Permission.

Read/Write

With Read/Write permission in the SNA domain, a user or group can run SNA  Server Admin and the snacfg command-line program, and can read and write to the configuration file. See Recommendation for Read/Write Permission.

Full Control

With Full Control permission in the SNA domain, a user or group can run SNA  Server Admin and the snacfg command-line program; can read and write to the configuration file; can change the administrative permissions assigned to others; and can remove SNA Server software. See Recommendation for Full Control Permission.

Special

Use the option marked Special if you need to specify a special set of permissions for a particular user or group. It is recommended that you avoid creating special sets of permissions except when necessary; the standard administrative permissions should be appropriate for most situations.

The permission listed under Name changes to match the permission selected in the Type of Access box.

4	Choose OK.


Searching for a User or Group Account

When you add a user or group to a list used  by SNA Server, you must know the name of the domain that contains the user or group's account. Use the Find Account dialog box to locate the domain of an account on a Windows NT Server network.

For background information about security with SNA Server, see the Microsoft SNA Server Administration Guide.

To search for users or groups in the Find Account dialog box

1	In the Find User or Group box, type the name of the user or group whose account you want to find.

2	Select Search All, or select Search Only In and select a domain in which to search.

3	Choose the Search button.

The results appear under Search Results.

4	To add the results of the search to the list that you were accessing, select the user or group and then choose the Add button.

To avoid adding any search results to a list, choose the Cancel button.

The Add Users and Groups dialog box reappears, with any user or group additions listed in the Add Names box.


Taking Ownership of the Ability to Administer SNA Server

For more detailed information about taking ownership of the ability to administer SNA Server, see the Microsoft SNA Server Administration Guide. For information about the concept of ownership, see your Windows NT documentation.

Note  Ownership of the ability to administer SNA Server normally includes ownership of all copies of the configuration file, including the copies on backup SNA servers. Therefore, in domains that include multiple SNA servers, ownership should only be taken with an account that exists on every primary and backup SNA server in the domain. This is because ownership of a file cannot be taken by an account that does not exist on a given server. If an attempt is made to take ownership, but the account used does not exist on some servers, ownership will not be transferred on those servers. The previous owner will retain ownership. The situation can readily be corrected by logging on in an account that is a member of the Administrators group and then taking ownership.

To designate a different owner for the ability to administer SNA Server

1	Log on to Windows NT, using the account to which you want to confer owner status.

For important information about the account in which you log on to take ownership, see the preceding paragraph. The account must have administrative permissions.

2	Start SNA Server Admin.

3	From the Security menu, choose Owner.

The Owner dialog box appears.

4	Choose the Take Ownership button.

5	Choose OK.


Setting Up Auditing of Access to the Configuration File

For important information about auditing with SNA Server, see the Microsoft SNA Server Administration Guide. For background information about auditing, see your Windows NT documentation.

To make sure that auditing is turned on in the domain, start User Manager and then, from the Policies menu, choose Audit. In the resulting dialog box, be sure that Audit These Events has been selected, along with File and Object Access (Success and Failure); then choose OK, and close User Manager.

To set up auditing of security events affecting SNA Server

1	To add users or groups to the list of those whose actions are audited, choose the Add button, and use the Add Users and Groups dialog box to select and add the intended users or groups.

To audit actions carried out by any user (rather than the actions of a specific group), add the group called Everyone.

2	Under Name, select a user or group.

3	Under Events to Audit, select the events you want to audit for that user or group.

4	Repeat steps 2 and 3 for each of the users and groups listed under Name.

If you do not specify any actions to audit for a user or group, and then you close and reopen the dialog box, that user or group name will no longer appear in the list under Name.

5	Choose OK.


Adding Users and Groups and Setting Permissions
Adding Users and Groups for Auditing

For background information about security with SNA Server, see the Microsoft SNA Server Administration Guide.

To add groups and users to the list of those whose actions are audited

1	If you want to add users from another domain, in the List Names from box, select a different domain.

The domains listed are trusted domains.

2	If you want the accounts displayed to include users as well as groups, choose the Show Users button.

3	Under Names, select one or more groups or users.

To select multiple names in sequence, click the first name you want, hold down SHIFT, and click the last name you want.

To select multiple names out of sequence, hold down CTRL as you click the names that you want.

To audit actions carried out by any user (rather than the actions of a specific group), select the group called Everyone.

4	Choose the Add button.

The selected group or user name(s) appear in the Add Names box.

5	Repeat steps 3 and 4 as needed.

6	Choose OK.