Copyright: Administration Guide
Citation: Administration Guide


Microsoft SNA Server Master Table of Contents
Microsoft SNA Server

Master Table of Contents

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


Administration Guide Contents
Microsoft SNA Server

Administration Guide

Contents

Before You Begin

Chapter 1	Getting Started

Chapter 2	Using the SNA Server Administration Program

Chapter 3	Configuring Servers and Connections

Chapter 4	Configuring for 3270

Chapter 5	Working with Settings in VTAM and NCP

Chapter 6	Configuring LUs for APPC

Chapter 7	Configuring for 5250 Emulation in the AS/400 Environment

Chapter 8	Configuring LUs for LUA

Chapter 9	Configuring Downstream Connections and LUs

Chapter 10	Using LU Pools to Maximize Access

Chapter 11	Managing SNA Server

Chapter 12	Setting Up Security with SNA Server

Chapter 13	Using Diagnostic Tools

Appendix A	Guidelines for Specific Configurations

Appendix B	SNA Server Preparation Forms

Appendix C	SNA Server NetView Extensions

Appendix D	Offline Configuration

Appendix E	The Command-Line Interface

List of Figures

List of Tables


Welcome Contents, Administration Guide
Microsoft SNA Server

Administration Guide

Contents

Before You Begin

How to Use This Guide

Document Conventions

Common Abbreviations

Finding Further Information

Chapter 1	Getting Started

Chapter 2	Using the SNA Server Administration Program

Chapter 3	Configuring Servers and Connections

Chapter 4	Configuring for 3270

Chapter 5	Working with Settings in VTAM and NCP

Chapter 6	Configuring LUs for APPC

Chapter 7	Configuring for 5250 Emulation in the AS/400 Environment

Chapter 8	Configuring LUs for LUA

Chapter 9	Configuring Downstream Connections and LUs

Chapter 10	Using LU Pools to Maximize Access

Chapter 11	Managing SNA Server

Chapter 12	Setting Up Security with SNA Server

Chapter 13	Using Diagnostic Tools

Appendix A	Guidelines for Specific Configurations

Appendix B	SNA Server Preparation Forms

Appendix C	SNA Server NetView Extensions

Appendix D	Offline Configuration

Appendix E	The Command-Line Interface

List of Figures

List of Tables


Chapter 1 Contents, Administration Guide
Microsoft SNA Server

Administration Guide

Contents

Before You Begin

Chapter 1	Getting Started

Basic Elements of SNA Server Configurations

Basic Tasks

Gathering Information

Communications Adapters and Lines

Remote System Types

Uses for SNA Server

Multiple Domains in an SNA Server Installation

Local and Remote Configuration Parameters

Commonly Required Server and Connection Parameters

Creating Multiple Connections

Using Remote Node Identifiers

Determining the Local Address of an 802.2 or X.25 Adapter

Commonly Required LU Parameters

Creating Multiple LUs

Setting Up Security with SNA Server

Managing SNA Server

Using Diagnostic Tools

Administering an Installation After Upgrading to SNA Server Version 2.1

Comm Server 1.x and SNA Server Compatibility

Using SNA Server Admin After Upgrading

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

SNA Architecture

Chapter 2	Using the SNA Server Administration Program

Chapter 3	Configuring Servers and Connections

Chapter 4	Configuring for 3270

Chapter 5	Working with Settings in VTAM and NCP

Chapter 6	Configuring LUs for APPC

Chapter 7	Configuring for 5250 Emulation in the AS/400 Environment

Chapter 8	Configuring LUs for LUA

Chapter 9	Configuring Downstream Connections and LUs

Chapter 10	Using LU Pools to Maximize Access

Chapter 11	Managing SNA Server

Chapter 12	Setting Up Security with SNA Server

Chapter 13	Using Diagnostic Tools

Appendix A	Guidelines for Specific Configurations

Appendix B	SNA Server Preparation Forms

Appendix C	SNA Server NetView Extensions

Appendix D	Offline Configuration

Appendix E	The Command-Line Interface

List of Figures

List of Tables


Chapter 2 Contents, Administration Guide
Microsoft SNA Server

Administration Guide

Contents

Before You Begin

Chapter 1	Getting Started

Chapter 2	Using the SNA Server Administration Program

Starting SNA Server Admin

The SNA Server Admin Display

Working with Windows and Icons

Selecting Items

Initiating Actions

Initiating Actions with Keys or Toolbar Buttons

Initiating Actions with Menu Commands

Carrying Out Actions by Dragging with the Mouse

Modifying the SNA Server Admin Display

Options Menu

View Menu

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

Moving the Split Line

Chapter 3	Configuring Servers and Connections

Chapter 4	Configuring for 3270

Chapter 5	Working with Settings in VTAM and NCP

Chapter 6	Configuring LUs for APPC

Chapter 7	Configuring for 5250 Emulation in the AS/400 Environment

Chapter 8	Configuring LUs for LUA

Chapter 9	Configuring Downstream Connections and LUs

Chapter 10	Using LU Pools to Maximize Access

Chapter 11	Managing SNA Server

Chapter 12	Setting Up Security with SNA Server

Chapter 13	Using Diagnostic Tools

Appendix A	Guidelines for Specific Configurations

Appendix B	SNA Server Preparation Forms

Appendix C	SNA Server NetView Extensions

Appendix D	Offline Configuration

Appendix E	The Command-Line Interface

List of Figures

List of Tables


Chapter 3 Contents, Administration Guide
Microsoft SNA Server

Administration Guide

Contents

Before You Begin

Chapter 1	Getting Started

Chapter 2	Using the SNA Server Administration Program

Chapter 3	Configuring Servers and Connections

Putting Configuration Changes into Effect

Configuring Servers

Configuring Server Broadcasts

Working with SNA Servers in Different Domains

Configuring Connections

Organization of Connection Information

Initial Connection Configuration

List of Connection Properties

Basic 802.2 Configuration

List of Basic 802.2 Settings

Advanced 802.2 Configuration

List of Advanced 802.2 Settings

Basic SDLC Configuration

List of Basic SDLC Settings

Advanced SDLC Configuration

List of Advanced SDLC Settings

Configuring Multidrop Connections

Basic X.25 Configuration

List of Basic X.25 Settings

Advanced X.25 Configuration

List of Advanced X.25 Settings

Facility Data Structuring for X.25 Networks

Basic Channel Configuration

List of Basic Channel Settings

Advanced Channel Configuration

List of Advanced Channel Settings

Copying Properties Between Connections

Moving a Connection to a Different Server

Chapter 4	Configuring for 3270

Chapter 5	Working with Settings in VTAM and NCP

Chapter 6	Configuring LUs for APPC

Chapter 7	Configuring for 5250 Emulation in the AS/400 Environment

Chapter 8	Configuring LUs for LUA

Chapter 9	Configuring Downstream Connections and LUs

Chapter 10	Using LU Pools to Maximize Access

Chapter 11	Managing SNA Server

Chapter 12	Setting Up Security with SNA Server

Chapter 13	Using Diagnostic Tools

Appendix A	Guidelines for Specific Configurations

Appendix B	SNA Server Preparation Forms

Appendix C	SNA Server NetView Extensions

Appendix D	Offline Configuration

Appendix E	The Command-Line Interface

List of Figures

List of Tables


Chapter 4 Contents, Administration Guide
Microsoft SNA Server

Administration Guide

Contents

Before You Begin

Chapter 1	Getting Started

Chapter 2	Using the SNA Server Administration Program

Chapter 3	Configuring Servers and Connections

Chapter 4	Configuring for 3270

Steps for Configuring for 3270

Configuration Steps Described in This Chapter

Configuring Individual 3270 LUs

Configuring Properties for a 3270 LU

After Configuring 3270 LU Properties

Numbers Needed for DFT LUs

Configuring a Range of 3270 LUs

Configuring Numbering for a 3270 LU Range

After Configuring Numbering for a 3270 LU Range

Modifying the Extension Numbering Format

After Modifying the Extension Numbering Format

Configuring Properties for a 3270 LU Range

Range Properties

Copying Properties Between LUs

Moving an LU to a Different Connection

Setting Up User and Group Access

Adding, Viewing, or Modifying Users or Groups

Configuring Properties for a 3270 User or Group

Giving Users Access to 3270 LUs

Copying Properties and LUs Between Users and/or Groups

Deleting LUs

Chapter 5	Working with Settings in VTAM and NCP

Chapter 6	Configuring LUs for APPC

Chapter 7	Configuring for 5250 Emulation in the AS/400 Environment

Chapter 8	Configuring LUs for LUA

Chapter 9	Configuring Downstream Connections and LUs

Chapter 10	Using LU Pools to Maximize Access

Chapter 11	Managing SNA Server

Chapter 12	Setting Up Security with SNA Server

Chapter 13	Using Diagnostic Tools

Appendix A	Guidelines for Specific Configurations

Appendix B	SNA Server Preparation Forms

Appendix C	SNA Server NetView Extensions

Appendix D	Offline Configuration

Appendix E	The Command-Line Interface

List of Figures

List of Tables


Chapter 5 Contents, Administration Guide
Microsoft SNA Server

Administration Guide

Contents

Before You Begin

Chapter 1	Getting Started

Chapter 2	Using the SNA Server Administration Program

Chapter 3	Configuring Servers and Connections

Chapter 4	Configuring for 3270

Chapter 5	Working with Settings in VTAM and NCP

Working with Host Connections and 3270

Configuring Host Connections

Configuring 3270 LUs

Assigning 3270 LUs to Users

Sample VTAM Parameters

Sample VTAM Parameters for a Token Ring Connection

Sample VTAM Parameters for an SDLC Connection

Sample VTAM Parameters for an X.25 Connection

NCP Parameters Needed for Independent APPC

Table of NCP Parameters That Affect Independent APPC

BUILD Definition

PUDRPOOL Definition

LUDRPOOL Definition

PU Definition

LU Definition

Sample VTAM and CICS Parameters for Independent LU 6.2

Sample VTAM Parameters for Use with LU 6.2

Sample CICS Configuration Screens for Use with LU 6.2

Chapter 6	Configuring LUs for APPC

Chapter 7	Configuring for 5250 Emulation in the AS/400 Environment

Chapter 8	Configuring LUs for LUA

Chapter 9	Configuring Downstream Connections and LUs

Chapter 10	Using LU Pools to Maximize Access

Chapter 11	Managing SNA Server

Chapter 12	Setting Up Security with SNA Server

Chapter 13	Using Diagnostic Tools

Appendix A	Guidelines for Specific Configurations

Appendix B	SNA Server Preparation Forms

Appendix C	SNA Server NetView Extensions

Appendix D	Offline Configuration

Appendix E	The Command-Line Interface

List of Figures

List of Tables


Chapter 6 Contents, Administration Guide
Microsoft SNA Server

Administration Guide

Contents

Before You Begin

Chapter 1	Getting Started

Chapter 2	Using the SNA Server Administration Program

Chapter 3	Configuring Servers and Connections

Chapter 4	Configuring for 3270

Chapter 5	Working with Settings in VTAM and NCP

Chapter 6	Configuring LUs for APPC

How LUs Work Together for APPC

Transaction Programs

Invoking and Invokable TPs

Invoking TPs

Invokable TPs

Possible Arrangements of TPs Within an SNA Network

Troubleshooting for Invokable TPs

Configuring LUs for APPC

SNA Server Features That Simplify APPC Configuration

Implicit Incoming Remote LU and Implicit Incoming Mode

Default Local APPC LU and the Default Remote APPC LU

Default Outgoing Local APPC LU Pool

Automatic Partnering

Single-System APPC

Section List for APPC

Assigning a Local APPC LU to a Server

Viewing or Modifying a Local or Remote APPC LU

Configuring Local APPC LU Properties

After Configuring Local APPC LU Properties

Assigning a Remote APPC LU to a Connection

Configuring Remote APPC LU Properties

After Configuring Remote APPC LU Properties

Configuring Modes for LU-LU Pairs

Properties of Standard Modes

Before Configuring a Mode

The APPC Mode Properties Dialog Box

Mode Properties

Pairing Local and Remote LUs

Configuring Session Security for Remote LUs

Configuring Properties for CPI-C

Specifying a User ID and Password

Configuring the Default DISPLAY Connection

Copying Properties Between LUs

Moving an LU to a Different Connection or Server

Assigning Default APPC LUs to Users or Groups

Chapter 7	Configuring for 5250 Emulation in the AS/400 Environment

Chapter 8	Configuring LUs for LUA

Chapter 9	Configuring Downstream Connections and LUs

Chapter 10	Using LU Pools to Maximize Access

Chapter 11	Managing SNA Server

Chapter 12	Setting Up Security with SNA Server

Chapter 13	Using Diagnostic Tools

Appendix A	Guidelines for Specific Configurations

Appendix B	SNA Server Preparation Forms

Appendix C	SNA Server NetView Extensions

Appendix D	Offline Configuration

Appendix E	The Command-Line Interface

List of Figures

List of Tables


Chapter 7 Contents, Administration Guide
Microsoft SNA Server

Administration Guide

Contents

Before You Begin

Chapter 1	Getting Started

Chapter 2	Using the SNA Server Administration Program

Chapter 3	Configuring Servers and Connections

Chapter 4	Configuring for 3270

Chapter 5	Working with Settings in VTAM and NCP

Chapter 6	Configuring LUs for APPC

Chapter 7	Configuring for 5250 Emulation in the AS/400 Environment

Configuration Steps for the AS/400 Environment

Strategies for Assigning LU Names and Aliases

Specifying Local LU Aliases That Match User Names

Configuring Hot Backup for LUs for 5250

Table of Parameters for AS/400 Communication

Guidelines for Configuring an AS/400 Computer

Guidelines for an AS/400 That Does Not Have PC Support

Changing Session Limits with a Single Mode Name

Chapter 8	Configuring LUs for LUA

Chapter 9	Configuring Downstream Connections and LUs

Chapter 10	Using LU Pools to Maximize Access

Chapter 11	Managing SNA Server

Chapter 12	Setting Up Security with SNA Server

Chapter 13	Using Diagnostic Tools

Appendix A	Guidelines for Specific Configurations

Appendix B	SNA Server Preparation Forms

Appendix C	SNA Server NetView Extensions

Appendix D	Offline Configuration

Appendix E	The Command-Line Interface

List of Figures

List of Tables


Chapter 8 Contents, Administration Guide
Microsoft SNA Server

Administration Guide

Contents

Before You Begin

Chapter 1	Getting Started

Chapter 2	Using the SNA Server Administration Program

Chapter 3	Configuring Servers and Connections

Chapter 4	Configuring for 3270

Chapter 5	Working with Settings in VTAM and NCP

Chapter 6	Configuring LUs for APPC

Chapter 7	Configuring for 5250 Emulation in the AS/400 Environment

Chapter 8	Configuring LUs for LUA

Putting Configuration Changes into Effect

Configuring Individual LUA LUs

Configuring Properties for an LUA LU

After Configuring LUA LU Properties

Numbers Needed for DFT LUs

Configuring a Range of LUA LUs

Configuring Numbering for an LUA LU Range

After Configuring Numbering for an LUA LU Range

Modifying the Extension Numbering Format

After Modifying the Extension Numbering Format

Configuring Properties for an LUA LU Range

Range Properties

Copying Properties Between LUs

Moving an LU to a Different Connection

Deleting LUs

Chapter 9	Configuring Downstream Connections and LUs

Chapter 10	Using LU Pools to Maximize Access

Chapter 11	Managing SNA Server

Chapter 12	Setting Up Security with SNA Server

Chapter 13	Using Diagnostic Tools

Appendix A	Guidelines for Specific Configurations

Appendix B	SNA Server Preparation Forms

Appendix C	SNA Server NetView Extensions

Appendix D	Offline Configuration

Appendix E	The Command-Line Interface

List of Figures

List of Tables


Chapter 9 Contents, Administration Guide
Microsoft SNA Server

Administration Guide

Contents

Before You Begin

Chapter 1	Getting Started

Chapter 2	Using the SNA Server Administration Program

Chapter 3	Configuring Servers and Connections

Chapter 4	Configuring for 3270

Chapter 5	Working with Settings in VTAM and NCP

Chapter 6	Configuring LUs for APPC

Chapter 7	Configuring for 5250 Emulation in the AS/400 Environment

Chapter 8	Configuring LUs for LUA

Chapter 9	Configuring Downstream Connections and LUs

Guidelines for Downstream Connections and LUs

Configuring a Downstream Connection

Configuring Individual Downstream LUs

Configuring Properties for a Downstream LU

After Configuring Downstream LU Properties

Configuring a Range of Downstream LUs

Configuring Numbering for a Downstream LU Range

After Configuring Numbering for a Downstream LU Range

Modifying the Extension Numbering Format

After Modifying the Extension Numbering Format

Adding a Comment for a Downstream LU Range

Associating Downstream LUs with a Downstream Connection

Adjusting the Numbering of Downstream LUs

Examples of Adjusted Numbering

Reordering the List of LUs for a Downstream Connection

Moving an LU to a Different Host Connection

Deleting LUs

Chapter 10	Using LU Pools to Maximize Access

Chapter 11	Managing SNA Server

Chapter 12	Setting Up Security with SNA Server

Chapter 13	Using Diagnostic Tools

Appendix A	Guidelines for Specific Configurations

Appendix B	SNA Server Preparation Forms

Appendix C	SNA Server NetView Extensions

Appendix D	Offline Configuration

Appendix E	The Command-Line Interface

List of Figures

List of Tables


Chapter 10 Contents, Administration Guide
Microsoft SNA Server

Administration Guide

Contents

Before You Begin

Chapter 1	Getting Started

Chapter 2	Using the SNA Server Administration Program

Chapter 3	Configuring Servers and Connections

Chapter 4	Configuring for 3270

Chapter 5	Working with Settings in VTAM and NCP

Chapter 6	Configuring LUs for APPC

Chapter 7	Configuring for 5250 Emulation in the AS/400 Environment

Chapter 8	Configuring LUs for LUA

Chapter 9	Configuring Downstream Connections and LUs

Chapter 10	Using LU Pools to Maximize Access

Putting Configuration Changes into Effect

3270 LU Pools

Configuring Properties for a 3270 LU Pool

LUA Pools

Configuring Properties for an LUA LU Pool

Downstream Pools

Specifying the LUs in an LU Pool

Resetting an LU in an LU Pool

Chapter 11	Managing SNA Server

Chapter 12	Setting Up Security with SNA Server

Chapter 13	Using Diagnostic Tools

Appendix A	Guidelines for Specific Configurations

Appendix B	SNA Server Preparation Forms

Appendix C	SNA Server NetView Extensions

Appendix D	Offline Configuration

Appendix E	The Command-Line Interface

List of Figures

List of Tables


Chapter 11 Contents, Administration Guide
Microsoft SNA Server

Administration Guide

Contents

Before You Begin

Chapter 1	Getting Started

Chapter 2	Using the SNA Server Administration Program

Chapter 3	Configuring Servers and Connections

Chapter 4	Configuring for 3270

Chapter 5	Working with Settings in VTAM and NCP

Chapter 6	Configuring LUs for APPC

Chapter 7	Configuring for 5250 Emulation in the AS/400 Environment

Chapter 8	Configuring LUs for LUA

Chapter 9	Configuring Downstream Connections and LUs

Chapter 10	Using LU Pools to Maximize Access

Chapter 11	Managing SNA Server

Starting and Stopping Servers and Connections

Resetting LUs

Changing the Domain of Focus

Using SNA Server Additions

Deleting SNA Resources

Working with Configuration Files

Saving and Reopening the Configuration

Backing Up and Restoring the Configuration

Configuration Files on Primary and Backup SNA Servers

Changing the Primary SNA Server

Copying the Configuration File Between Servers

Chapter 12	Setting Up Security with SNA Server

Chapter 13	Using Diagnostic Tools

Appendix A	Guidelines for Specific Configurations

Appendix B	SNA Server Preparation Forms

Appendix C	SNA Server NetView Extensions

Appendix D	Offline Configuration

Appendix E	The Command-Line Interface

List of Figures

List of Tables


Chapter 12 Contents, Administration Guide
Microsoft SNA Server

Administration Guide

Contents

Before You Begin

Chapter 1	Getting Started

Chapter 2	Using the SNA Server Administration Program

Chapter 3	Configuring Servers and Connections

Chapter 4	Configuring for 3270

Chapter 5	Working with Settings in VTAM and NCP

Chapter 6	Configuring LUs for APPC

Chapter 7	Configuring for 5250 Emulation in the AS/400 Environment

Chapter 8	Configuring LUs for LUA

Chapter 9	Configuring Downstream Connections and LUs

Chapter 10	Using LU Pools to Maximize Access

Chapter 11	Managing SNA Server

Chapter 12	Setting Up Security with SNA Server

Overview of Security on SNA Servers

How SNA Server Components Provide Secure Access

Security with Windows NT, SNA Server, and Other SNA Systems

Client Logon

Allowing Open-Ended Access to LUs

Increasing the Security of SNA Servers in a Domain

File System Choices and Security

Resources to Consider When Establishing Security

Steps for Increasing Security on SNA Servers

Specifying Administrative Permissions on SNA Servers

Denying Administrative Permission on SNA Servers

Specifying the Owner of Administrative Access to SNA Servers

Setting Up Auditing of Access to the Configuration File

Viewing and Interpreting SNA Server Events

Setting Permissions for the COMCFG Share

Chapter 13	Using Diagnostic Tools

Appendix A	Guidelines for Specific Configurations

Appendix B	SNA Server Preparation Forms

Appendix C	SNA Server NetView Extensions

Appendix D	Offline Configuration

Appendix E	The Command-Line Interface

List of Figures

List of Tables


Chapter 13 Contents, Administration Guide
Microsoft SNA Server

Administration Guide

Contents

Before You Begin

Chapter 1	Getting Started

Chapter 2	Using the SNA Server Administration Program

Chapter 3	Configuring Servers and Connections

Chapter 4	Configuring for 3270

Chapter 5	Working with Settings in VTAM and NCP

Chapter 6	Configuring LUs for APPC

Chapter 7	Configuring for 5250 Emulation in the AS/400 Environment

Chapter 8	Configuring LUs for LUA

Chapter 9	Configuring Downstream Connections and LUs

Chapter 10	Using LU Pools to Maximize Access

Chapter 11	Managing SNA Server

Chapter 12	Setting Up Security with SNA Server

Chapter 13	Using Diagnostic Tools

Viewing the Status of Servers, Connections, and LUs

Configuring for NetView

Using Event Logs

Configuring RTM Settings

Performance Monitor Options for SNA Server

Collecting Traces and Other Detailed System Information

Trace Files

Tracing on SNA Servers or Windows NT-Based Clients

Types of Tracing for SNA Servers or Windows NT-Based Clients

Starting the Snatrace Utility

Enabling or Disabling Trace Options

Files Created by the Snatrace Utility

Available Trace Options for SNA Server and Windows NTBased Clients

Tracing on Clients Running Windows Version 3.x

Types of Tracing for Clients Running Windows Version 3.x

Available Trace Options for Clients Running Windows Version 3.x

Enabling or Disabling Tracing on Clients Running Windows Version 3.x

Tracing on MS-DOS  Based Clients

Types of Tracing for MS-DOS  Based Clients

Available Trace Options for MS-DOS  Based Clients

Enabling or Disabling Tracing on MS-DOS  Based Clients

Tracing on OS/2-Based Clients

Types of Tracing for OS/2-Based Clients

The Set Command

Available Trace Options for OS/2-Based Clients

Other Tracing Options

Tracing Examples for OS/2-Based Clients

Enabling or Disabling Tracing on Clients Running OS/2

Appendix A	Guidelines for Specific Configurations

Appendix B	SNA Server Preparation Forms

Appendix C	SNA Server NetView Extensions

Appendix D	Offline Configuration

Appendix E	The Command-Line Interface

List of Figures

List of Tables


Appendix A Contents, Administration Guide
Microsoft SNA Server

Administration Guide

Contents

Before You Begin

Chapter 1	Getting Started

Chapter 2	Using the SNA Server Administration Program

Chapter 3	Configuring Servers and Connections

Chapter 4	Configuring for 3270

Chapter 5	Working with Settings in VTAM and NCP

Chapter 6	Configuring LUs for APPC

Chapter 7	Configuring for 5250 Emulation in the AS/400 Environment

Chapter 8	Configuring LUs for LUA

Chapter 9	Configuring Downstream Connections and LUs

Chapter 10	Using LU Pools to Maximize Access

Chapter 11	Managing SNA Server

Chapter 12	Setting Up Security with SNA Server

Chapter 13	Using Diagnostic Tools

Appendix A	Guidelines for Specific Configurations

SNA Server Adapter and Connection Capacities

Phone Number Storage and Modem Types

Changing the SNA Server Dialing Method

Modem Requirements for Accepting a Phone Number from SNA Server

SNA Server Actions When Sending a Phone Number

Command String Examples

Determining the LUs Assigned to a DFT Adapter

Determining a Connections Link Role

Appendix B	SNA Server Preparation Forms

Appendix C	SNA Server NetView Extensions

Appendix D	Offline Configuration

Appendix E	The Command-Line Interface

List of Figures

List of Tables


Appendix B Contents, Administration Guide
Microsoft SNA Server

Administration Guide

Contents

Before You Begin

Chapter 1	Getting Started

Chapter 2	Using the SNA Server Administration Program

Chapter 3	Configuring Servers and Connections

Chapter 4	Configuring for 3270

Chapter 5	Working with Settings in VTAM and NCP

Chapter 6	Configuring LUs for APPC

Chapter 7	Configuring for 5250 Emulation in the AS/400 Environment

Chapter 8	Configuring LUs for LUA

Chapter 9	Configuring Downstream Connections and LUs

Chapter 10	Using LU Pools to Maximize Access

Chapter 11	Managing SNA Server

Chapter 12	Setting Up Security with SNA Server

Chapter 13	Using Diagnostic Tools

Appendix A	Guidelines for Specific Configurations

Appendix B	SNA Server Preparation Forms

Server Resources Planning Form

Server Information Form

Initial Connection Settings Form

802.2 Settings Form

SDLC Settings Form

X.25 Settings Form

Channel Settings Form

3270 LUs Form (for Individual LUs)

3270 LUs Form (for Ranges of LUs)

3270 LU Pools Form

Users and Groups Form

Local APPC LUs Form

Remote APPC LUs Form

Mode Properties for LU-LU Pairs Form

CPI-C Properties Form

3270 RTM Settings Form

Appendix C	SNA Server NetView Extensions

Appendix D	Offline Configuration

Appendix E	The Command-Line Interface

List of Figures

List of Tables


Appendix C Contents, Administration Guide
Microsoft SNA Server

Administration Guide

Contents

Before You Begin

Chapter 1	Getting Started

Chapter 2	Using the SNA Server Administration Program

Chapter 3	Configuring Servers and Connections

Chapter 4	Configuring for 3270

Chapter 5	Working with Settings in VTAM and NCP

Chapter 6	Configuring LUs for APPC

Chapter 7	Configuring for 5250 Emulation in the AS/400 Environment

Chapter 8	Configuring LUs for LUA

Chapter 9	Configuring Downstream Connections and LUs

Chapter 10	Using LU Pools to Maximize Access

Chapter 11	Managing SNA Server

Chapter 12	Setting Up Security with SNA Server

Chapter 13	Using Diagnostic Tools

Appendix A	Guidelines for Specific Configurations

Appendix B	SNA Server Preparation Forms

Appendix C	SNA Server NetView Extensions

Code Page Settings for NVAlert and NVRunCmd

The NVAlert Service

Modifying NVALERT.INI

Required Lines for Alerts in NVALERT.INI

Optional Lines for Alerts in NVALERT.INI

Example of NVALERT.INI Section

The NVRunCmd Service

How NVRunCmd Runs

Typing a Command at the Host Console

Functionality Available with NVRunCmd

Appendix D	Offline Configuration

Appendix E	The Command-Line Interface

List of Figures

List of Tables


Appendix D Contents, Administration Guide
Microsoft SNA Server

Administration Guide

Contents

Before You Begin

Chapter 1	Getting Started

Chapter 2	Using the SNA Server Administration Program

Chapter 3	Configuring Servers and Connections

Chapter 4	Configuring for 3270

Chapter 5	Working with Settings in VTAM and NCP

Chapter 6	Configuring LUs for APPC

Chapter 7	Configuring for 5250 Emulation in the AS/400 Environment

Chapter 8	Configuring LUs for LUA

Chapter 9	Configuring Downstream Connections and LUs

Chapter 10	Using LU Pools to Maximize Access

Chapter 11	Managing SNA Server

Chapter 12	Setting Up Security with SNA Server

Chapter 13	Using Diagnostic Tools

Appendix A	Guidelines for Specific Configurations

Appendix B	SNA Server Preparation Forms

Appendix C	SNA Server NetView Extensions

Appendix D	Offline Configuration

Differences Between Offline Configuration and OnSite Configuration

Guidelines for Offline Configuration

Starting the Offline Version of SNA Server Admin

Using the Offline Version of SNA Server Admin

Adding a Server to an Offline Configuration

Specifying Adapter Properties in an Offline Configuration

Appendix E	The Command-Line Interface

List of Figures

List of Tables


Appendix E Contents, Administration Guide
Microsoft SNA Server

Administration Guide

Contents

Before You Begin

Chapter 1	Getting Started

Chapter 2	Using the SNA Server Administration Program

Chapter 3	Configuring Servers and Connections

Chapter 4	Configuring for 3270

Chapter 5	Working with Settings in VTAM and NCP

Chapter 6	Configuring LUs for APPC

Chapter 7	Configuring for 5250 Emulation in the AS/400 Environment

Chapter 8	Configuring LUs for LUA

Chapter 9	Configuring Downstream Connections and LUs

Chapter 10	Using LU Pools to Maximize Access

Chapter 11	Managing SNA Server

Chapter 12	Setting Up Security with SNA Server

Chapter 13	Using Diagnostic Tools

Appendix A	Guidelines for Specific Configurations

Appendix B	SNA Server Preparation Forms

Appendix C	SNA Server NetView Extensions

Appendix D	Offline Configuration

Appendix E	The Command-Line Interface

Avoiding Critical Errors in Commands

Task Order

Getting Help with the Command-Line Interface

Specifying the Configuration File

Using a Command File

Creating a Snacfg Command File from a Configuration File

General Syntax for the /print Option

Examples of Syntax for the /print Option

Ways of Using the /print Option

Displaying the Contents of a Configuration File

Document Conventions

Snacfg APPCLLU

Snacfg APPCRLU

Snacfg Connection

Snacfg CPIC

Snacfg Diagnostic

Snacfg Link

Snacfg LU

Snacfg LUA

Snacfg LUD

Snacfg Mode

Snacfg Pool

Snacfg PoolA

Snacfg PoolD

Snacfg Server

Snacfg User

List of Figures

List of Tables


Appendix E Contents, Administration Guide
Microsoft SNA Server

Administration Guide

Contents

Before You Begin

Chapter 1	Getting Started

Chapter 2	Using the SNA Server Administration Program

Chapter 3	Configuring Servers and Connections

Chapter 4	Configuring for 3270

Chapter 5	Working with Settings in VTAM and NCP

Chapter 6	Configuring LUs for APPC

Chapter 7	Configuring for 5250 Emulation in the AS/400 Environment

Chapter 8	Configuring LUs for LUA

Chapter 9	Configuring Downstream Connections and LUs

Chapter 10	Using LU Pools to Maximize Access

Chapter 11	Managing SNA Server

Chapter 12	Setting Up Security with SNA Server

Chapter 13	Using Diagnostic Tools

Appendix A	Guidelines for Specific Configurations

Appendix B	SNA Server Preparation Forms

Appendix C	SNA Server NetView Extensions

Appendix D	Offline Configuration

Appendix E	The Command-Line Interface

List of Figures

An SNA Server with Multiple Connections

SNA Server Architecture

SNA Server Admin Display

Connection Properties Dialog Box (for Ethernet Connection)

802.2 Setup Dialog Box (Basic Settings)

802.2 Setup Dialog Box (Advanced Settings)

SDLC Setup Dialog Box (Basic Settings)

SDLC Setup Dialog Box (Advanced Settings)

X.25 Setup Dialog Box (Basic Settings)

X.25 Setup Dialog Box (Advanced Settings)

Channel Attached Setup Dialog Box (Basic Settings)

Channel Attached Setup Dialog Box (Advanced Settings)

A Highlighted Connection

Insert LU Dialog Box

3270 LU Properties Dialog Box

Add LU Range Dialog Box

Add LU Range Dialog Box (with Numbering Options Displayed)

3270 LU Range Properties Dialog Box

User Properties Dialog Box

Independent APPC

Dependent APPC

Two TPs Using LU 6.2

Three TPs Using LU 6.2

APPC LU Properties Dialog Box

APPC Remote LU Properties Dialog Box

APPC Mode Properties Dialog Box

LU 6.2 Partner LUs Dialog Box

CPI-C Symbolic Destination Name Properties Dialog Box

A Highlighted Connection

Insert LU Dialog Box

LUA LU Properties Dialog Box

Add LU Range Dialog Box

Add LU Range Dialog Box (with Numbering Options Displayed)

LUA LU Range Properties Dialog Box

Communication with a Downstream System

Multiple Downstream Systems

Connection Properties Dialog Box (802.2 Connection)

Servers and Connections Window with Connection Highlighted

Insert LU Dialog Box

Downstream LU Properties Dialog Box

Add LU Range Dialog Box

Add LU Range Dialog Box (with Numbering Options Displayed)

Downstream Connection with Associated Downstream LUs

New Pool Dialog Box

3270 LU Pool Properties Dialog Box

LUA LU Pool Properties Dialog Box

How the DMOD Service Layer Provides Secure Access

SNA Domain Permissions Dialog Box

Add Users and Groups Dialog Box

List of Tables


Appendix E Contents, Administration Guide
Microsoft SNA Server

Administration Guide

Contents

Before You Begin

Chapter 1	Getting Started

Chapter 2	Using the SNA Server Administration Program

Chapter 3	Configuring Servers and Connections

Chapter 4	Configuring for 3270

Chapter 5	Working with Settings in VTAM and NCP

Chapter 6	Configuring LUs for APPC

Chapter 7	Configuring for 5250 Emulation in the AS/400 Environment

Chapter 8	Configuring LUs for LUA

Chapter 9	Configuring Downstream Connections and LUs

Chapter 10	Using LU Pools to Maximize Access

Chapter 11	Managing SNA Server

Chapter 12	Setting Up Security with SNA Server

Chapter 13	Using Diagnostic Tools

Appendix A	Guidelines for Specific Configurations

Appendix B	SNA Server Preparation Forms

Appendix C	SNA Server NetView Extensions

Appendix D	Offline Configuration

Appendix E	The Command-Line Interface

List of Figures

List of Tables

Servers and Connections Window: Services Menu

LU Pools Window: Pools Menu

Users and Groups Window: Users Menu

Any Window: File Menu

Any Window: Options Menu

Any Window: Security Menu

View Menu Commands for the Servers and Connections Window

View Menu Commands for the Users and Groups Window

View Menu Commands for the LU Pools Window

Configuration Information for Connections

SNA Server and VTAM Parameters for SNA Servers

SNA Server, VTAM, and NCP Parameters for 802.2 Connections

SNA Server, VTAM, and NCP Parameters for SDLC Connections

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

SNA Server, VTAM, and NCP Parameter for 3270 LUs

NCP Parameters: Recommendations for Independent APPC

Types of Tracing

Information Needed for Interpreting Tracing

Examples of Tracing for SNA Servers and Windows NT-Based Clients

SNA Applications Trace Options: Message Traces

SNA Applications Trace Options: Client API Tracing

SnaBase Trace Options

SnaServer (PU 2.1 Node) Trace Options

Link Service Trace Options

Trace Options for a Client Running Windows Version 3.x

Trace Options for an MS-DOS  Based Client

Information Needed for Interpreting Tracing on OS/2-Based Clients

Trace Options for an OS/2-Based Client

Forms for Configuring the Server and Connections

Forms for Configuring LUs

Form for Configuring Diagnostics

Task Order for Configuration Tasks


Before You Begin
1 of 5

Before You Begin

The Microsoft [image] SNA Server Administration Guide explains how to administer Microsoft SNA Server (SNA Server).


How to Use This Guide
Before You Begin	2 of 5

How to Use This Guide

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

Chapter 1, “Getting Started”

Gives an overview of the tasks carried out by SNA Server administrators.

Chapter 2, “Using the SNA Server Administration Program”

Tells how to start the SNA Server Administration Program (SNA Server Admin) and use the interface, including the windows, icons, menus, Toolbar, mouse, and keyboard.

Chapter 3, “Configuring Servers and Connections”

Tells how to configure servers and the six kinds of connections: Synchronous Data Link Control (SDLC), 802.2, X.25, distributed function terminal (DFT), Twinax, and Channel. Also tells how to copy connection properties from one connection to another and move a connection to a different server.

Chapter 4, “Configuring for 3270”

Tells how to configure LUs for user access to a host system via 3270 terminal emulation and how to assign the LUs to users. Also tells how to copy LU properties, move LUs from one connection to another, and configure properties for 3270 users and groups.

Chapter 5, “Working with Settings in VTAM [image] and NCP”

Tells how settings used in VTAM and NCP correspond to settings in SNA Server. Provides a number of tables listing corresponding settings.

Chapter 6, “Configuring LUs for APPC”

Tells how to configure LU 6.2 LUs for Advanced Program-to-Program Communication (APPC). Also tells how to configure for Common Programming Interface for Communications (CPI-C) or for a default connection for the DISPLAY verb. In addition, tells how to copy LU properties and move LUs from one connection to another.

Chapter 7, “Configuring for 5250 Emulation in the AS/400 Environment”

Tells how to configure connections and LUs to support 5250 emulation in the AS/400 [image] environment. Includes specific information about the correspondences between SNA Server parameters and AS/400 parameters.

Chapter 8, “Configuring LUs for LUA”

Tells how to configure LUs for the conventional logical unit application programming interface (LUA). Also tells how to copy LU properties and move LUs from one connection to another.

Chapter 9, “Configuring Downstream Connections and LUs”

Tells how to configure downstream connections and LUs, which allow SNA Server to support communication between hosts and clients that do not use the SNA Server client/server interface. Such clients include IBM [image] Communications Manager/2 systems.

Chapter 10, “Using LU Pools to Maximize Access”

Tells how to group 3270, LUA, or downstream LUs together in pools to provide more flexible access to the LUs.

Chapter 11, “Managing SNA Server”

Tells how to start and stop servers and connections, reset LUs, and delete Systems Network Architecture (SNA) resources. Also tells how to save, reopen, back up, or restore a configuration file, and how to work with configuration files on the primary and backup SNA servers.

Chapter 12, “Setting Up Security with SNA Server”

Discusses the elements to consider when setting up security on SNA servers, and tells how to configure permissions and auditing through SNA Server Admin.

Chapter 13, “Using Diagnostic Tools”

Tells how to view the status of services, configure NetView, use event logs that record SNA Server events, configure Response Time Monitor (RTM) settings, use the Windows NT [image] Performance Monitor, and work with trace files.

Appendix A, “Guidelines for Specific Configurations”

Gives reference information about adapter and connection capacities, modems, determining the LUs assigned to a DFT adapter, and determining a connection’s link role.

Appendix B, “SNA Server Preparation Forms”

Provides information-gathering forms.

Appendix C, “SNA Server NetView Extensions”

Tells about the NVAlert and NVRunCmd services, which extend NetView functionality.

Appendix D, “Offline Configuration”

Tells how to create a configuration file for another SNA Server site.

Appendix E, “The Command-Line Interface”

Tells how to use the SNA Server command-line interface.


Document Conventions
Before You Begin	3 of 5

Document Conventions

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

Convention	Purpose

bold	Indicates syntax items that must be typed exactly as shown.

italic	Indicates variables.

monospace	Represents examples and program code.

SMALL CAPS	Represent return values and key names, such as CTRL.

UPPERCASE	Represents filenames, paths, volumes, array and structure names, values, and conversation states.

[brackets]	Enclose optional items in syntax statements.

{braces}	Enclose required items in syntax statements.

| (vertical bar)	Stands for OR and separates items in syntax statements.

... (ellipsis)	Indicates that the preceding syntax item can be repeated. If a punctuation mark precedes the ellipsis, you must include the punctuation when repeating the item.

X'nnnn'	Indicates hexadecimal digits.


Common Abbreviations
Before You Begin	4 of 5

Common Abbreviations

The following is an alphabetical list of common abbreviations used in this manual. For definitions of these and other SNA terms, see: the glossary in the Microsoft SNA Server Reference.

Abbreviation	Description

API	Application programming interface

APPC	Advanced Program-to-Program Communications

ASCII	American Standard Code for Information Interchange

BTU	Basic transmission unit

CPI-C	Common Programming Interface for Communications

CSV	Common Service Verb

CTS	Clear-to-send

DFT	Distributed function terminal

DLC	Data link control

DLL	Dynamic-link library

DSR	Data-set-ready

DTR	Data-terminal-ready

EBCDIC	Extended Binary Coded Decimal Interchange Code

K	Kilobyte

LU	Logical unit

LUA	Conventional Logical Unit Application programming interface

MB	Megabyte

NCP	Network Control Panel

NRZ	Nonreturn to zero

NRZI	Nonreturn to zero inverted

PU	Physical unit

PVC	Permanent virtual circuit

QLLC	Qualified logical link control

RTM	Response time monitor

RU	Request/response unit

RUI	Request Unit Interface

SAP	System access point

SDLC	Synchronous Data Link Control

SID	Security ID

SLI	Session Level Interface

SNA	Systems Network Architecture

SSCP	System services control point

SVC	Switched virtual circuit

TP	Transaction program

VTAM	Virtual Telecommunications Access Method


Finding Further Information
Before You Begin	5 of 5

Finding Further Information

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

Microsoft SNA Server Installation 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

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

Microsoft SNA Server APPC Programmer’s Guide

Microsoft SNA Server CPI-C Programmer’s Guide

IBM Systems Network Architecture: Introduction to APPC

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

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

IBM SNA: Formats

IBM SNA: Technical Overview

IBM SNA: ACF/VTAM Programming for LU Type 6.2


Getting Started
Chapter 1	1 of 17

Getting Started

The SNA Server Administration program (SNA Server Admin) provides a graphical interface that allows you to configure connections between PCs and remote computers — IBM mainframes, AS/400 systems, or other PCs — within an IBM Systems Network Architecture (SNA) network. SNA Server allows PCs to establish connections with several computers at the same time, with any of three methods of communication: 3270 terminal emulation, Advanced Program-to-Program Communications (APPC), and/or communication using the logical unit application programming interfaces (LUA).

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 are the software components that allow SNA Server to use the communications adapter(s) installed in the computer(s). If you add a communications adapter to an SNA Server, and the adapter will be used for SNA communications, install link services to work with the adapter. Link services can be installed or removed only by running the Setup program.

This chapter outlines the basic elements in an SNA Server configuration and indicates where to find more information about each element. In addition, this chapter provides information about upgrading to SNA Server version 2.1, to supplement the Microsoft SNA Server Installation Guide. For details, see: "Administering an Installation After Upgrading to SNA Server Version 2.1," later in this chapter.


Basic Elements of SNA Server Configurations
Getting Started	2 of 17

Basic Elements of SNA Server Configurations

Two important elements are used in every SNA configuration: connections and logical units (LUs). A connection is the data communication path between computers on the SNA network. An LU is a preset unit containing all the configuration information needed for a user, program, or downstream system to establish a session with a host or peer computer. Connections are configured first, and then one or more LUs can be assigned to each connection.

Multiple connections can share a single link service. Multiple LUs can share a single connection.

Most client systems access connections and LUs by using the SNA Server client/server interface. However, certain systems do not use this interface. These systems are called downstream systems, and include IBM Communications Manager/2 systems. They can be given access to host connections through an SNA server by the use of downstream connections and LUs.

After LUs are configured, they can be grouped together in LU pools, to maximize access to resources. A user, LUA application, or downstream system using the pool can get LU access as long as one of the pooled LUs is available.


Basic Tasks
Getting Started	3 of 17

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 those 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 to give users access to a host via terminal emulation, assign LUs and/or LU pools to the users. Or, if APPC LUs will be used to give users access to 5250 emulators, transaction programs (TPs), or APPC applications, assign default APPC LUs to the users.

Manage SNA Server, by starting and stopping servers, connections, and other services.

Use diagnostic tools to monitor SNA Server.

The following sections describe these tasks in more detail. For information about working with menus, Toolbar buttons, and other items in SNA Server Admin, see: Chapter 2, "Using the SNA Server Administration Program." For specific information about configuring for hosts and for 3270 emulation, see: "Working with Host Connections and 3270" in Chapter 5.

For detailed information about SNA Server configuration and management tasks, see the following chapters or appendixes:

SNA Server element or task		Chapter or appendix
Gathering information		Appendix B, "SNA Server Preparation Forms"
Servers and connections		Chapter 3, "Configuring Servers and Connections"
3270 LUs		Chapter 4, "Configuring for 3270"
Users and groups		Chapter 4, "Configuring for 3270"
Host parameters		Chapter 5, "Working with Settings in VTAM and NCP"
LUs for APPC TPs		Chapter 6, "Configuring LUs for APPC"
AS/400 parameters; LUs for 5250		Chapter 7, "Configuring for 5250 Emulation in the AS/400 Environment"
LUs for LUA		Chapter 8, "Configuring LUs for LUA"
Downstream Connections and LUs		Chapter 9, "Configuring Downstream Connections and LUs"
LU pools		Chapter 10, "Using LU Pools to Maximize Access"
Managing SNA Server		Chapter 11, "Managing SNA Server"
Setting up security		Chapter 12, "Setting Up Security with SNA Server"
Using diagnostic tools		Chapter 13, "Using Diagnostic Tools"
Connection capacities		Appendix A, "Guidelines for Specific Configurations"
Modems		Appendix A, "Guidelines for Specific Configurations"
Also, for important information about planning the domains for an SNA Server installation, see: the Microsoft SNA Server Installation Guide.


Gathering Information
Getting Started	4 of 17

Gathering Information

Before you can successfully configure SNA Server, you must gather information about local and remote computers, and make choices about how SNA Server will be used.

The basic components on which a configuration is based are as follows:

Communications hardware (communications adapter and lines).

Remote systems: host (mainframe), peer, or downstream.

Intended uses for SNA Server: terminal emulation, APPC, specially written programs using LUA, and/or support of downstream systems (such as IBM Communications Manager/2 systems).

Configuration parameters that are set on the remote host, peer, and/or downstream system(s).

SNA Server systems are highly varied in requirements and use. They may access mainframes, AS/400 systems, or remote peer systems. The communications lines and adapters may be fast or slow, with light traffic or heavy. The remote host or peer may respond to requests from one local system or many.

Because SNA Server systems are so varied, the parameters that must be configured for a given system are also varied. SNA Server has been designed to supply reasonable default values for parameters whenever possible. However, you will need to specify parameters that identify your system, and parameters that differ from common default values.

To determine parameter values needed for your system, work with the system administrator of the remote host, peer, and/or downstream system(s).

The following sections describe basic components for an SNA Server configuration in more detail. For a set of forms to help you gather information and make choices, see: Appendix B, "SNA Server Preparation Forms."


Communications Adapters and Lines
Getting Started	5 of 17

Gathering Information

Communications Adapters and Lines

The communications adapters and lines used for SNA Server connections include the following types:

Connection identifier		Connection type		Line types (as applicable)
		802.2		Ethernet or token ring; uses 802.2 protocol
		SDLC		Synchonous Data Link Control (SDLC)		Leased (committed solely to the connection) or switched (committed when needed)
		X.25		X.25; uses Qualified Logical Link Control (QLLC) protocol		Permanent virtual circuit (constantly active, with preset destination) or switched (active only when called, with requested destination)
		DFT		Distributed function terminal
		Channel		Channel attached
		Twinaxial		Twinaxial
The following diagram shows an SNA Server with a variety of connections:

Figure 1.1    An SNA Server with Multiple Connections


Remote System Types
Getting Started	6 of 17

Gathering Information

Remote System Types

Remote system(s) can be of three types:

Host systems (mainframes)

Host systems (mainframes) control the interactions with systems that connect to them. 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.

Peer systems

Peer systems use APPC to communicate with other systems as equal partners, with both systems sharing control over the communication.

APPC can also be carried out with a host, in addition to being carried out peer-to-peer. Such APPC is called dependent APPC, and is configured with a remote system setting of Host, not Peer.

Downstream systems

Downstream systems are clients such as IBM Communications Manager/2 systems that do not use the conventional SNA Server client/server interface.


Uses for SNA Server
Getting Started	7 of 17

Gathering Information

Uses for SNA Server

An SNA Server configuration is based on the ways the system will be used:

3270 terminal emulation

Users can connect to a host using 3270 terminal-emulation software on PCs. Such users access 3270 LUs configured on an SNA server.

APPC

Programs on separate computers can work together using APPC. Such programs include 5250 emulators, and access APPC LUs configured on an SNA server.

LUA

Programs can be based on LUA, which allows communication between a PC and a host. LUA programs can use LU 0, LU 1, LU 2, or LU 3 protocols. Such programs access LUA LUs configured on an SNA server.

Downstream systems

SNA Server can support downstream systems, such as IBM Communications Manager/2 systems, by providing those systems with connections to a host. Downstream systems access downstream LUs on an SNA server.

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 for your SNA Server installation, see: the Microsoft SNA Server Installation Guide.

As you work in multiple domains, you will need user rights on the Windows NT-based systems that you access. For information about setting up 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 and choose OK.


Local and Remote Configuration Parameters
Getting Started	8 of 17

Gathering Information

Local and Remote Configuration Parameters

Certain configuration parameters on the local system need to match or work correctly with configuration parameters on the remote host, peer, and/or downstream system(s). These parameters include information that the remote system expects from the local system, such as the local node ID. Necessary parameters for the local system also include the names and addresses of any LUs that will be accessed on remote systems. Work with the administrator of the remote host, peer, and/or downstream system(s) to find out the relevant information.

Commonly Required Server and Connection Parameters

The following table shows server and connection parameters that are often or always required when configuring SNA Server. 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 when specifying values for these parameters:

System element		Common configuration parameters		Applicable situations
Server (node)		Local Control Point Name and Network Name		Recommended for LU 6.2 (APPC) and 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
For information about how SNA Server parameters correspond to Virtual Telecommunications Access Method (VTAM) host parameters, see: "Working with Host Connections and 3270" in Chapter 5.

Creating Multiple Connections

If you want to set up the same properties for multiple connections, you can use one existing connection as a source from which to copy configuration properties to others. For details about copying connection properties, see: "Copying Properties Between Connections" in Chapter 3.

Using Remote Node Identifiers

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

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 only used 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 the next section.

Note that these parameters (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.

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 the next section.

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

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 identifier(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 combination of outgoing plus incoming identifiers
SDLC	Outgoing	If SNA Server supplies the phone number to the modem, specify Dial Data (phone number of remote system)
SDLC	Incoming	Match the identifier(s) used on the remote system: Remote node Network Name and Control Point Name     Or Remote Node ID
SDLC	Both	Use combination of outgoing plus incoming identifiers
X.25	Outgoing	Use Remote X.25 Address
X.25	Incoming	Match the identifier(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 combination of outgoing plus incoming identifiers
Identifying Information on Incoming XIDs

When deciding which kind of remote node identifier to specify for a connection that accepts incoming calls, it can 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.

Determining the Local Address of an 802.2 or X.25 Adapter

When gathering information and 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. In other words, you may need to find out your local network address (for an 802.2 adapter, that is, token ring or Ethernet) or local X.25 address (for an X.25 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
Getting Started	9 of 17

Gathering Information

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 when specifying values for these parameters:

System element		Required configuration parameters
3270 LU (on connection 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. (Additional recommended parameters:  Network Name and LU Name.)
Remote LU for dependent APPC		Network Name, LU Name, and Uninterpreted LU Name.
LUA LU (on connection 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).
For information about how SNA Server parameters correspond to VTAM host parameters, see: "Working with Host Connections and 3270" in Chapter 5.

Creating Multiple LUs

You can create 3270, LUA, or downstream LUs one at a time or in a consecutively numbered range. When you create a range of LUs, all the LUs are given the same properties. You can modify individual LUs after creating them.

You can also copy configuration properties from one LU to others. For details about copying LU properties, see "Copying Properties Between LUs" in Chapter 4, Chapter 6, or Chapter 8.

After creating multiple 3270, LUA, or downstream LUs, you can pool the LUs together and then make the pool available to users, LUA applications, or downstream systems. As long as one LU in the pool is functioning and available, a user, application, or downstream system can get LU access. For more information about LU pools, see: Chapter 10, "Using LU Pools to Maximize Access."


Setting Up Security with SNA Server
Getting Started	10 of 17

Setting Up Security with SNA Server

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 information about basic elements for security on SNA servers and about implementing this security, and see: Chapter 12, "Setting Up Security with SNA Server."


Managing SNA Server
Getting Started	11 of 17

Managing SNA Server

When the configurations and assignments are complete, you can manage SNA Server by:

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

Stopping SNA servers (nodes) and connections, which frees up communications lines (unless they are leased or permanent).

When possible, have any active users log off from the remote host or peer before stopping services, to avoid interrupting interactions between a user and the host or peer. When interactions are interrupted, the remote host or peer can be left in an unresolved state.

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

Viewing status information, such as the number of each kind of session that is active on a server.

Resetting LUs, which may restore function to the LUs if problems have occurred.

In addition, when managing an SNA Server installation, you may need to change the domain of focus, delete SNA resources, or work with configuration files. For more information about all these management tasks, see: Chapter 11, "Managing SNA Server."


Using Diagnostic Tools
Getting Started	12 of 17

Using Diagnostic Tools

The following kinds of diagnostic information can be used with SNA Server:

Server status, which includes the number of active users and the number of each kind of session: 3270, APPC, LUA, and downstream.

Connection status.

LU status, which includes the name 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.

NetView management information, which is sent and received by NetView, a reporting system that runs on host (mainframe) systems. NetView forwards alerts back and forth between the host and the computers that connect to the host.

Windows NT event logs, which can be viewed using the Windows NT Event Viewer.

Response Time Monitor (RTM) data, which can be received and displayed by some 3270 emulators. RTM data shows how quickly the host is responding to requests from the emulator.

Performance Monitor counters, which provide information about system performance.

Trace-file information, detailed diagnostic information about system events, which product-support technicians may work with you to collect.

For more information about these diagnostics, see: Chapter 13, "Using Diagnostic Tools." For information about services that extend the capabilities of NetView, see: Appendix C, "SNA Server NetView Extensions."


Administering an Installation After Upgrading to SNA Server Version 2.1
Getting Started	13 of 17

Administering an Installation After Upgrading to SNA Server Version 2.1

The following sections provide information about upgrading to SNA Server version 2.1. The sections include information about the following:

Comm Server 1.x and SNA Server compatibility

Steps to take when beginning to administer a domain that has been upgraded from Comm Server 1.x to SNA Server

Enabling communication between version 2.0 SNA servers and version 2.1 SNA servers

For important details about how to carry out an upgrade to SNA Server version 2.1, see: the Microsoft SNA Server Installation Guide.


Comm Server 1.x and SNA Server Compatibility
Getting Started	14 of 17

Administering an Installation After Upgrading to SNA Server Version 2.1

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. For information about how to enable an  SNA server to support Comm Server 1.x clients, see the next section.

Applications written according to the Comm Server 1.x application programming interfaces (APIS) are compatible with SNA Server, and will function in an SNA Server domain.

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.

Important

When you upgrade to SNA Server, it is recommended that you create a new domain for the new SNA servers as they are upgraded. Avoid having Comm Server 1.x servers and SNA servers in the same domain, because they cannot function together. If one or more Comm Server 1.x servers are started in a domain with one or more SNA servers, conflicting messages will be sent regarding the roles of the servers, which server is to load the configuration, and which configuration file is current. A probable result is that one or more Comm Server 1.x servers in the domain will stop functioning.

For detailed information about upgrading from Comm Server 1.x to SNA Server, see: the Microsoft SNA Server Installation Guide.


Using SNA Server Admin After Upgrading
Getting Started	15 of 17

Administering an Installation After Upgrading to SNA Server Version 2.1

Using SNA Server Admin After Upgrading

There are several things to remember before starting SNA Server Admin on servers that have been upgraded from Comm Server 1.x:

Avoid starting SNA servers and Comm Server 1.x servers in the same domain, because they cannot function together. It is recommended that you create a new domain for the new SNA servers.

If you saved the Comm Server 1.x configuration and security files (as described in the Microsoft SNA Server Installation Guide), copy them to the primary SNA server before starting SNA Server Admin for the first time.

When such files are loaded by SNA Server Admin, they are automatically converted to SNA Server format.

There are also several steps to take to reinstate user and group access to SNA Server LUs. These steps are included in the upgrading procedure in the Microsoft SNA Server Installation Guide. The steps related to administration are listed here as well:

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. For information about assigning a link service for a connection, see: "Initial Connection Configuration" in Chapter 3.

3.	Add users to the list recognized by SNA Server. For information about adding users, see: "Setting Up User and Group Access" in Chapter 4, or "Assigning Default APPC LUs to Users or Groups" in Chapter 6.

4.	Assign LUs to SNA Server users and groups. For information about assigning LUs to users, see: "Giving Users Access to 3270 LUs" in Chapter 4, or "Assigning Default APPC LUs to Users or Groups" in Chapter 6.

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.	From the File menu, choose Save Configuration.

If you temporarily leave some Comm Server 1.x clients in your installation, after removing them, you should disable the DCA/Microsoft Comm Server client support option. This will increase efficiency on the SNA servers.


Enabling Communication Between Version 2.0 SNA Servers and Version 2.1 SNA Servers
Getting Started	16 of 17

Administering an Installation After Upgrading to SNA Server Version 2.1

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. The steps related to administration are repeated in the following procedure.

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 Novel [image] NetWare [image], 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.	From the File menu, choose Save Configuration.


SNA Architecture
Getting Started	17 of 17

SNA Architecture

Figure 1.2 shows the architecture for SNA Server:

Figure 1.2    SNA Server Architecture1


Using the SNA Server Administration Program
Chapter 2	1 of 16

Using the SNA Server Administration Program

This chapter provides basic instructions for using SNA Server Admin. The chapter provides instructions for:

Starting SNA Server Admin.

Identifying elements in the SNA Server Admin display.

Working with windows and icons.

Selecting items, such as connections and other services, or menu commands.

Initiating actions with keys, Toolbar buttons, menu commands, or by dragging and dropping with the mouse.

Modifying the SNA Server Admin display.


Starting SNA Server Admin
Using the SNA Server Administration Program	2 of 16

Starting SNA Server Admin

You can start SNA Server Admin using either the mouse or the keyboard. For detailed information about working with windows and icons, see your Windows documentation.

To start SNA Server Admin using the mouse

Double-click the SNA Server Admin icon.

If the group that contains the SNA Server Admin icon is minimized, double-click the group icon, then double-click the SNA Server Admin icon.

To start SNA Server Admin using the keyboard

1.	Press CTRL+TAB until the group that contains the SNA Server Admin icon is selected; a group is selected when the group title is highlighted.

If the group appears as an icon, not a window, after pressing CTRL+TAB to select it, press ENTER to restore it to a window.

2.	Use the arrow keys to select the SNA Server Admin icon.

3.	Press ENTER.


The SNA Server Admin Display
Using the SNA Server Administration Program	3 of 16

The SNA Server Admin Display

Figure 2.1 shows the SNA Server Admin display.

Figure 2.1    SNA Server Admin Display

The SNA Server Admin display is structured around several windows that appear inside the main window. The windows can be shrunk to icons, and then restored to windows, as described in the next section. The windows are as follows:

Window Name	Use to

Servers and Connections	Configure servers, connections, and LUs; start and stop servers and connections; reset LUs.

An LU is a preset unit containing all the configuration information needed for a user or a program to establish a session with a host or peer computer. One or many LUs can be assigned to a given connection.

LU Pools	Configure LU pools.

An LU pool is a number of LUs that are grouped together before being assigned to users. A user who is assigned the pool can get LU access as long as one of the pooled LUs is available.

Users and Groups	Assign items for users: properties, LUs, and LU pools.

The SNA Server Admin Toolbar contains the following buttons:


Working with Windows and Icons
Using the SNA Server Administration Program	4 of 16

Working with Windows and Icons

The following paragraphs describe basic actions with windows and icons. For more information, see your Windows documentation.

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 to restore (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).


Selecting Items
Using the SNA Server Administration Program	5 of 16

Selecting Items

The first step for many actions in SNA Server Admin is to select an appropriate item, such as a connection to which you want to assign an LU. Next you can click a button on the Toolbar, or select a menu command.

To select an item displayed in a window

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.

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.


Initiating Actions
Using the SNA Server Administration Program	6 of 16

Initiating Actions

The SNA Server Admin program allows you to initiate most actions in several ways. You can:

Click a button on the Toolbar.

Use a key such as ENTER, INS, or DEL.

Use a menu command.

Drag and drop an appropriate item with the mouse.

This is used for assigning or reassigning an 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
Using the SNA Server Administration Program	7 of 16

Initiating Actions

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

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.

Choose the key or button according to the task you want to initiate:

Button			Key		Task
	Properties		ENTER		Viewing or modifying an existing connection, LU, User, or other item.
	Start		F5		Starting a server or connection.
	Stop		F3		Stopping a server or connection, or resetting an LU.
	Insert		INS		Adding a connection, LU, user or other item.
	Delete		DEL		Deleting a connection, LU, or other item.
			F8 F7		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.
	Reopen				Reopening the last configuration saved. For information about how SNA Server uses configuration files on the primary and backup SNA Servers, see "Configuration Files on Primary and Backup SNA Servers" in Chapter 11.
	Save				Saving the current configuration. For information about how SNA Server uses configuration files on the primary and backup SNA Servers, see "Configuration Files on Primary and Backup SNA Servers" in Chapter 11.


Initiating Actions with Menu Commands
Using the SNA Server Administration Program	8 of 16

Initiating Actions

Initiating Actions with Menu Commands

You can initiate any action in SNA Server Admin by selecting an appropriate item and then a menu command. For information about working with windows, see: "Working with Windows and Icons" earlier in this chapter, or your Windows documentation.

As the current active window changes in SNA Server Admin, the fourth menu changes also. When the Servers and Connections window is active, the fourth menu is the Services menu:

Servers and Connections Window: Services Menu

Command		Action
Start Services		Starting a server or connection.
Stop ServiceReset LU		Stopping a server or connection, or resetting an LU (depending on whether a server, connection, or LU is selected).
New Connection		Adding a connection to a server.
Assign LUs		Adding an LU to a connection.
Move ConnectionMove LU		Moving a connection from one server to another, or moving an LU from one connection to another.
Reorder LUs		Reordering downstream LUs; the command is unavailable unless a downstream connection is selected.
Copy Properties		Copying properties from one connection or LU to another.
Properties		Viewing or modifying an existing connection or LU.
When the LU Pools window is active, the fourth menu is the Pools menu:

LU Pools Window: Pools Menu

Command	Action

Reset LUs	Resetting LUs that are in an LU pool

New Pool	Adding a new LU pool

Assign LUs	Assigning LUs to an LU pool

Move	Moving LUs from one LU pool to another

Properties	Viewing or modifying properties for an existing LU pool

When the Users and Groups window is active, the fourth menu is the Users menu:

Select a command according to the type of action you want to perform:

Users and Groups Window: Users Menu

Command	Action

New User	Adding a network user or group to the list used by SNA Server

Assign LUs	Assigning an LU or LU pool to a user

Reorder LUs	Changing the number of an LU session (to change its place in users' displays)

Copy Properties	Copying properties from one user to another

Properties	Viewing or modifying an existing user's properties (including permissions)

The File menu is accessible from any window:

Any Window: File Menu

Command	Action

Reopen Configuration	Reopen the configuration as it was when last saved, abandoning changes made since then.For information about how SNA Server uses configuration files on the primary and backup SNA Servers, see: "Configuration Files on Primary and Backup SNA Servers" in Chapter 11.

Save Configuration	Save the current configuration (the displayed configuration).For information about how SNA Server uses configuration files on the primary and backup SNA Servers, see: "Configuration Files on Primary and Backup SNA Servers" in Chapter 11.

Backup	Save the current configuration as a backup file.

Restore	Restore a configuration that was saved as a backup file.

Select Domain	Select the domain containing the SNA servers to be displayed in SNA Server Admin.

Exit	Exit SNA Server Admin.

The Options menu is also available from any window:

Any Window: Options Menu

Command	Action

NetView	Specifying the connection to be used by NetView.

RTM Triggers	Configuring properties for RTM, a 3270 and NetView facility that monitors the amount of time it takes for a host to respond during 3720 display sessions.

Logs	Configuring the location and the level of detail for SNA Server logs.

CPI-C	Setting properties for the Common Programming Interface for Communications (CPI-C).

Display Verb	Specifying a default connection for the DISPLAY verb, an APPC verb that returns configuration information about an SNA server.

Server Broadcasts	Selecting the protocols to be used for sending server broadcasts between SNA servers, and for communicating with earlier versions of server and client software within the domain.

Preferences	Turning the following on and off: the Toolbar, status bar, advanced configuration displays, confirmation following mouse operations, and the saving of settings on exit.

The Security menu is also available from any window:

Any Window: Security Menu

Command	Action

Permissions	Setting permissions for administrative access to SNA Server.

Auditing	Setting up auditing of administrative access to SNA Server.

Owner	Taking ownership of administrative access to SNA Server.


Carrying Out Actions by Dragging with the Mouse
Using the SNA Server Administration Program	9 of 16

Initiating Actions

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

You can also 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.

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

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.

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


Modifying the SNA Server Admin Display
Using the SNA Server Administration Program	10 of 16

Modifying the SNA Server Admin Display

When you work with SNA Server, you may want to modify the display to make it easier to use. For example, you may want to move the split line between windows, or show only a certain type of item.


Options Menu
Using the SNA Server Administration Program	11 of 16

Modifying the SNA Server Admin Display

Options Menu

You can modify certain aspects of the active window by using the Options menu.

To specify preferences for the active window

1.	From the Options menu, choose Preferences.

The Preferences dialog box appears:

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

Action		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
Automatically displaying advanced settings in dialog boxes that contain an Advanced button, or hiding advanced settings until the Advanced button is chosen.		Always Display Advanced Settings
Enabling or disabling the confirmation prompt following mouse operations.		Confirm Mouse Operations
Turning on and off 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
3.	Choose the OK button.


View Menu
Using the SNA Server Administration Program	12 of 16

Modifying the SNA Server Admin Display

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

Control the order in which LUs are listed (Servers and Connections window only). For more information, see the next section.

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

As the current active window changes in SNA Server, 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.

The following sections give details about modifying the display.


Modifying the Display for the Servers and Connections Window
Using the SNA Server Administration Program	13 of 16

Modifying the SNA Server Admin Display

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

Purpose	Command	Effect
Modifying the display of services
	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.
Modifying the sorting of LU lists
	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
Using the SNA Server Administration Program	14 of 16

Modifying the SNA Server Admin Display

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.

Note

If you want to assign LUs to users, first, from the View menu, choose Configured Users. Only when the display shows Configured Users can you make changes to user configurations.

View Menu Commands for the Users and Groups Window

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


Modifying the Display for the LU Pools Window
Using the SNA Server Administration Program	15 of 16

Modifying the SNA Server Admin Display

Modifying the Display for the LU Pools Window

To modify the display of LU 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

Purpose	Command	Effect
Modifying the display of pools
	All LU Pools	Display all LU pools
	3720 LU Pools	Display 3270 LU pools
	LUA Pools	Display LUA pools
	Downstream Pools	Display downstream pools


Moving the Split Line
Using the SNA Server Administration Program	16 of 16

Modifying the SNA Server Admin Display

Moving the Split Line

To move the split line between halves of a window or between column headings in a window

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

The mouse pointer changes to two outward-pointing arrows.

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.


Configuring Servers and Connections
Chapter 3	1 of 18

Configuring Servers and Connections

Two of the most important initial tasks for an SNA Server administrator are configuring servers and connections. Before configuring servers and connections, you will need to gather information about local software and hardware, the configuration of the remote host, peer, or downstream system, and the ways SNA Server will be used. For details, see: Chapter 1, "Getting Started" and Appendix B, "SNA Server Preparation Forms." For specific information about configuring host connections, see: "Working with Host Connections and 3270" in Chapter 5.

Before configuring servers and connections, be sure to read the SNA Server README file, and use the SNA Server Setup program to install SNA link services. For information about Setup and about link services, see: the Microsoft SNA Server Installation Guide.

Most types of connections are discussed in this chapter. However, for additional information about downstream connections, which allow an SNA server (node) to make its host connections available for use by a client such as an IBM Communications Manager/2 system, see: Chapter 9, "Configuring Downstream Connections and LUs." Such systems do not use the SNA Server client/server interface, but can still connect to a host via an SNA server (node).

After configuring servers and connections, assign and configure appropriate LUs (3270, APPC, LUA, or downstream) for the connections. LUs are logical units, and contain configuration information needed for a user or program to use a connection. For more information about configuring LUs, see: Chapter 4, "Configuring for 3270," Chapter 6, "Configuring LUs for APPC," Chapter 7, "Configuring for 5250 Emulation in the AS/400 Environment," Chapter 8, "Configuring LUs for LUA," or Chapter 9, "Configuring Downstream Connections and LUs."

LUs other than APPC LUs can also be pooled, to make them readily available to multiple users, applications, or downstream systems. For information about pooling LUs, see: Chapter 10, "Using LU Pools to Maximize Access."


Putting Configuration Changes into Effect
Configuring Servers and Connections	2 of 18

Putting Configuration Changes into Effect

Most configuration changes in SNA Server take effect the next time the server (node) is started. Therefore, after making changes to servers and connections in an existing configuration, stop and restart the affected servers (nodes) in order to put the changes into effect. For more information about stopping and starting servers and connections, see: Chapter 11, "Managing SNA Server."

This chapter tells how to configure servers, then how to configure connections. For a table showing the organization of this chapter's information about connections, see: "Organization of Connection Information" later in this chapter.


Configuring Servers
Configuring Servers and Connections	3 of 18

Configuring Servers

If an SNA server will accept incoming calls, or be used for LU 6.2 (APPC), it is recommended that you configure two names for the server: the local Network Name and Control Point Name. In addition, you may need to configure your SNA servers to use the correct type of server broadcasts, so the servers support the client-server protocols you use. The configuration of these elements is described in this section and the following two sections.

The local Network Name and Control Point Name work together to identify the server. If either of these names is supplied, the other should also be supplied. The Network Name and Control Point Name are included only in Format 3 XIDs, the default XID type. For information about whether you need to specify these parameters, and what to specify, consult with the administrator of the remote host, peer, or downstream system.

Note

The local Network Name and Control Point Name are set in a different dialog box than the remote Network Name and Control Point Name. Since the local Network Name and Control Point Name apply across all connections, they are set in the Server Properties dialog box, as described in this section. In contrast, the remote Network Name and Control Point Name must be set individually for each connection, and are set in the Connection Properties dialog box, as described in: "List of Basic 802.2 Settings," "List of Basic SDLC Settings," or "List of Basic X.25 Settings" later in this chapter. For additional information about the remote Control Point Name and Network Name, see: "Using Remote Node Identifiers" in Chapter 1.

Another parameter that you can specify for a server is a comment that is displayed when the server is listed in SNA Server Admin.

Server broadcasts are the method of communication used between SNA servers. Configure server broadcasts (and the other communication items in the Server Broadcasts dialog box) to ensure that your SNA servers will use the appropriate protocols for your situation. You need to configure server broadcasts only once for the domain, in a dialog box that allows you to specify support for various combinations of the following:

Microsoft Networking (Named Pipes)

Novell NetWare (IPX/SPX)

Banyan [image] VINES [image] /IP

Windows Sockets (TCP/IP)

Communication in an IP routed network

Communicating with version 2.0 SNA servers in the same domain

Communicating with DCA/Microsoft Comm Server 1.x clients

For more information about server broadcasts, see: "Configuring Server Broadcasts," later in this chapter. For information about setting up a server to support Macintosh clients, see: the Microsoft SNA Server Installation Guide.

To specify parameters for an SNA Server that will accept incoming calls or be used for LU 6.2 (APPC)

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

2.	From the Services menu, choose Properties.

The Server Properties dialog box appears:

3.	In the Network Name box, type a name identifying the SNA network of the local SNA server.

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. If you supply a Network Name, be sure to supply a Control Point Name, as described in step 4.

When connecting to a host system and using a local Network Name, the name should match the NETID parameter in the VTAM Start command for the local SSCP (the VTAM system to which SNA Server is attached). This is generally the same as the NETID for the remote SSCP.

To connect to an AS/400 computer, type the Network Name of the local SNA server in the Network Name box, and see step 5.

4.	In the Control Point Name box, type a name that identifies the local system to other control points (nodes) on the SNA network.

The name can be from one through eight characters long, and can contain alphanumeric characters and the special characters $, #, and @. If you supply a Control Point Name, it is recommended that you supply a Network Name, as described in step 3.

When connecting to a host system and using a local Control Point Name, the name should match the CPNAME = parameter in the host's PU definition; for information, contact the host administrator.

To connect to an AS/400 computer, type the Control Point Name of the local SNA server in the Network Name box. Also, when configuring the connection that the AS/400 will use, see the instructions for configuring connections. Specifically, see the instructions for Control Point Name (Remote Node) and Network Name (Remote Node) in the "List of Basic 802.2 Settings," the "List of Basic SDLC Settings," or the "List of Basic X.25 Settings" later in this chapter.

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

6.	Choose the OK button.


Configuring Server Broadcasts
Configuring Servers and Connections	4 of 18

Configuring Servers

Configuring Server Broadcasts

Server broadcasts (and other communication items in the Server Broadcasts dialog box) need to be configured only once for the domain. All servers (not just one) are affected by the options. For additional background information about server broadcasts, see: "Configuring Servers," earlier in this chapter. 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 in the Server Broadcasts dialog box

1.	From the Options menu, choose Server Broadcasts.

The Server Broadcasts dialog box appears.

2.	Select one or more client-server protocols that will be used to send server broadcasts between SNA servers. The options available are:

Microsoft Networking (Named Pipes)

Novell NetWare (IPX/SPX)

Banyan VINES/IP

Windows Sockets (TCP/IP)

Route Server Broadcasts over IP routers

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, it affects only those servers installed as primary or backup domain controllers.

Protocols not currently installed will be unavailable. To add protocols, see your Windows NT documentation; then, to set up your SNA servers to use available protocols, see Chapter 2 of the Microsoft SNA Server Installation Guide.

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

SNA Server 2.0 servers in the same domain

DCA/Microsoft Comm Server client support

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

Specifying a smaller value brings heavier demands on the network (since broadcasts occur more often). Specifying a larger value means that SNA servers will not communicate as frequently. The default is 60 seconds.

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


Working with SNA Servers in Different Domains
Configuring Servers and Connections	5 of 18

Configuring Servers

Working with SNA Servers in Different Domains

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.

The selected domain appears in the Domain box.

3.	Choose OK.


Configuring Connections
Configuring Servers and Connections	6 of 18

Configuring Connections

A connection can be one of four types, depending on the communications adapter and lines used by the connection. The connection accesses the communications adapter via the link service for the adapter. Before configuring connections, use the SNA Server Setup program to install link services.

The connection types shown in the following table are available.

Connection identifier		Connection type
		802.2		Ethernet or token ring; uses 802.2 protocol
		SDLC		Synchonous Data Link Control (SDLC); communicates over standard telephone lines (switched lines) or leased lines.
		X.25		X.25, the standard used for communication over a packet-switching network; uses Qualified Logical Link Control (QLLC) protocol
		DFT		Distributed function terminal, which works with IBM 3270 control units; often communicates over coaxial cable
		Channel		Channel attached; provides direct channel attachment to a mainframe
		Twinax		Twinaxial connection to an AS/400
For specific information about configuring connection parameters to correspond with VTAM, see: Chapter 5, "Working with Settings in VTAM and NCP." For details about AS/400 configuration, see: Chapter 7, "Configuring for 5250 Emulation in the AS/400 Environment." For information about downstream connections, see: Chapter 9, "Configuring Downstream Connections and LUs."


Organization of Connection Information
Configuring Servers and Connections	7 of 18

Configuring Connections

Organization of Connection Information

Configuration information for each type of connection is given in the following sections in this chapter:

Table 3.1    Configuration Information for Connections

Type of connection	Applicable sections
802.2 (token ring or Ethernet)	Initial Connection Configuration
	Basic 802.2 Configuration
	Advanced 802.2 Configuration
SDLC	Initial Connection Configuration
	Basic SDLC Configuration
	Advanced SDLC Configuration
X.25	Initial Connection Configuration
	Basic X.25 Configuration
	Advanced X.25 Configuration
Channel	Initial Connection Configuration
	Basic Channel Configuration
	Advanced Channel Configuration
DFT	Initial Connection Configuration
Twinax	Initial Connection Configuration
See also: "Copying Properties Between Connections" and "Moving a Connection to a Different Server" later in this chapter. In addition, for specific information about host connections and VTAM, see: Chapter 5, "Working with Settings in VTAM and NCP."


Initial Connection Configuration
Configuring Servers and Connections	8 of 18

Configuring Connections

Initial Connection Configuration

You can configure settings on a new or existing connection.

To access an existing connection for viewing or modifying

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

2.	From the Services menu, choose Properties.

The Connection Properties dialog box appears. For an illustration of the dialog box and details about the settings, see the next section.

To assign a new connection

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

2.	From the Services menu, choose New Connection.

The Insert Connection dialog box appears.

3.	Under Connection, select the type of connection: 802.2, SDLC, Channel, X.25, DFT, or Twinax.

4.	Choose the OK button.

The Connection Properties dialog box appears. For an illustration of the dialog box and details about the settings, see the following section.

List of Connection Properties

When you access an existing connection, or assign a new one, the Connection Properties dialog box appears. Depending on the type of connection, the last line in the dialog box and the icon in the upper left corner vary. The Connection Properties dialog box for an Ethernet (802.2) connection is shown in Figure 3.1.

Figure 3.1    Connection Properties Dialog Box (for Ethernet Connection)

Find the items appropriate to your configuration, and supply information as follows:

Connection Name

Type a name identifying the 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.

Comment

Optionally, type a comment of up to 25 characters.

Link Service

Select Link Service. A link service enables the connection to access a particular communications adapter.

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

Remote End

Select the type of remote system for this connection. (For Channel, Twinax, and DFT connections, the correct type is preselected.)

Host System: A system, usually a mainframe, that controls interactions between it and PCs connecting to it.

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

If this connection will be used for 3270 or LUA LUs, select Host System. For information about how SNA Server parameters correspond to VTAM host parameters, see: "Working with Host Connections and 3270" in Chapter 5.

Peer System: Mainframe, mini, or PC that communicates with another computer as an equal partner, with both computers sharing control over the communication.

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

For details about AS/400 configuration, see: Chapter 7, "Configuring for 5250 Emulation in the AS/400 Environment."

Downstream System: A client such as an IBM Communications Manager/2 system that does not use the SNA Server client/server interface, but that can access host connections available on the SNA server.

For connections to downstream systems, be sure to set the Max BTU Length to a value supported by the downstream system. For information about setting Max BTU Length, see: "List of Advanced 802.2 Settings," "List of Advanced SDLC Settings," or "List of Advanced X.25 Settings" later in this chapter.

Activation

If the Allowed Directions include outgoing calls, select an Activation setting:

On Server Startup: Select this option if you want the connection to be started when the SNA server used by this connection is started. This gives 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: Select this option if you want the connection to be started when needed, and stopped 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: Select this option if you want the administrator to control the connection on a case-by-case basis.

Activation affects only outgoing calls. With incoming calls, if a connection is configured to accept these calls, the connection begins to listen for the calls when the server is started.

For 802.2 (token ring or Ethernet) and distributed function terminal (DFT) connections, the default is On Server Startup. For all other connections, the default is On Demand.

Allowed Directions

Select the allowed call direction(s), Outgoing Calls and/or Incoming Calls. (For Channel, Twinax, and DFT connections, the direction is preselected.)

When multiple SDLC connections accept incoming calls and use the same link service, the encoding (NRZ/NRZI) settings for all the connections must match.

For DFT connections, this field is unavailable.

The default is Outgoing Calls.

Virtual Circuit Type (X.25 connections only)

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

Switched (SVC): These circuits are called and cleared dynamically, instead of being constantly active. The destination address is supplied when the circuit is called.

Permanent (PVC): These circuits are constantly active, and the destination address is preset.

The default for Virtual Circuit Type is Switched.

After Configuring Initial Connection Properties

After specifying initial connection settings in the Connection Properties dialog box, similar to the one shown in Figure 3.1, choose a button according to the following:

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

The dialog box that appears depends on the type of connection you are configuring. For information, see: "List of Basic 802.2 Settings," "List of Basic SDLC Settings," "List of Basic X.25 Settings," or  List of Basic Channel Settings," later in this chapter.

To complete the configuration for a DFT or Twinax connection, which requires only the settings in the Connection Properties dialog box, choose the OK button.

To accept settings after viewing or modifying an existing connection, choose the OK button.

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


Basic 802.2 Configuration
Configuring Servers and Connections	9 of 18

Configuring Connections

Basic 802.2 Configuration

To view or configure basic 802.2 settings, you must first view or configure initial connection settings, as described in: "Initial Connection Configuration" earlier in this chapter.

To view or modify basic settings for an existing 802.2 connection

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

2.	From the Services menu, choose Properties.

The Connection Properties dialog box, shown in Figure 3.1, appears.

3.	Choose the Setup button.

The 802.2 Setup dialog box appears. For an illustration of the dialog box and details about the settings, see the next section.

To configure basic settings for a new 802.2 connection

1.	Configure initial connection properties for an 802.2 connection, as described in: "Initial Connection Configuration" and "List of Connection Properties" earlier in this chapter.

2.	In the Connection Properties dialog box, shown in Figure 3.1, choose the Setup button.

The 802.2 Setup dialog box appears. For an illustration of the dialog box and details about the settings, see the following section.

List of Basic 802.2 Settings

When you choose the Setup button with an 802.2 connection, the dialog box shown in Figure 3.2 appears. For information about choosing the Setup button in the Connection Properties dialog box, see the preceding section.

Figure 3.2    802.2 Setup Dialog Box (Basic Settings)

Find the items appropriate to your configuration, and supply information as follows:

Remote Network Address

Type the 12-digit hexadecimal network address of the remote host, peer, or downstream system with which you will communicate on this connection. 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 SNA Server system, the resulting display shows the network address of that system, in the line labeled "Server is active on."

For more information about the Remote Network Address, see: "Using Remote Node Identifiers" in Chapter 1.

The default for Remote Network Address is 400000000000.

Local Node ID

Type the Local Node ID, an eight-digit hexadecimal number that identifies the local system to the remote 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.

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 of the Local Node ID. These values are reserved.

The default for Local Node ID is 05D FFFFF.

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 name identifying the SNA network of the remote system. (Format 3 is the default XID type.) 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 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.

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.

If this connection will access an AS/400 computer, type the Network Name of the AS/400 (the RMTNETID on the AS/400) in this box. For more information, see your APPN documentation.

This parameter, the Network Name (Remote Node), is different from the Network Name for the local node. For information, see: "Configuring Servers" earlier in this chapter.

For more information about Network Name (Remote Node), see: "Using Remote Node Identifiers" in Chapter 1.

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 name that identifies the remote system on the SNA network. (Format 3 is the default XID type.) The name can be from one through eight characters long, and can contain alphanumeric characters and the special characters $, #, and @.

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.

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). For information, contact the host administrator.

If this connection will access an AS/400 computer, type the name of the AS/400 in this box.

This parameter, the Control Point Name (Remote Node), is different from the Control Point Name for the local node. For information, see: "Configuring Servers" earlier in this chapter.

For more information about Control Point Name (Remote Node), see: "Using Remote Node Identifiers" in Chapter 1.

Remote Node ID

If instructed to by the administrator of a remote host, peer, or downstream system, type 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.

Note

Do not use 000 or FFF for the first three digits of the Remote Node ID. These values are reserved.

For more information about Remote Node ID, see: "Using Remote Node Identifiers" in Chapter 1.

Connection Activation Limits (Retry Timers)

From the 802.2 Setup dialog box, shown in Figure 3.2, you can configure connection activation limits (also known as retry timers). To do this, choose the Retry Timers button, and configure the activation limits as follows:

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.

After Configuring Basic 802.2 Settings

After specifying basic 802.2 settings in the 802.2 Setup dialog box, shown in Figure 3.2, choose a button according to the following:

To configure advanced settings, choose the Advanced button.

The 802.2 Setup dialog box expands to show the advanced fields. For information, see: "List of Advanced 802.2 Settings" later in this chapter.

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

The SNA Server program is designed to provide reasonable default settings wherever possible.

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


Advanced 802.2 Configuration
Configuring Servers and Connections	10 of 18

Configuring Connections

Advanced 802.2 Configuration

After configuring basic 802.2 settings, you can configure advanced 802.2 settings. SNA Server is designed to provide reasonable defaults for all advanced settings. The defaults will be appropriate for many installations; for some installations, the settings will need to be adjusted.

To view or modify advanced settings for an existing 802.2 connection

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

2.	From the Services menu, choose Properties.

The Connection Properties dialog box, shown in Figure 3.1, appears.

3.	Choose the Setup button.

The 802.2 Setup dialog box, shown in Figure 3.2, appears. For details about the settings in the dialog box, see the preceding section.

4.	Choose the Advanced button.

The 802.2 Setup dialog box expands to show the advanced fields. For information, see: "List of Advanced 802.2 Settings" later in this chapter.

To configure advanced settings for a new 802.2 connection

1.	Configure initial connection properties for an 802.2 connection, as described in: "Initial Connection Configuration" and "List of Connection Properties" earlier in this chapter.

2.	Configure basic 802.2 settings, as described in the preceding section.

3.	In the 802.2 Setup dialog box, shown in Figure 3.2, choose the Advanced button.

The 802.2 Setup dialog box expands to show the advanced fields. For information, see the following section.

List of Advanced 802.2 Settings

When you choose the Advanced button in the 802.2 Setup dialog box, the dialog box expands as shown in Figure 3.3. For information about accessing the 802.2 Setup dialog box advanced settings, see the preceding section.

Figure 3.3    802.2 Setup Dialog Box (Advanced Settings)

Find the items appropriate to your configuration, and supply information as follows:

XID Type

Select the type of identifying information for SNA Server to send:

Format 0 sends only the Node ID. Use this option only if the host 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.

If you want to use independent APPC LUs on this connection, you must select Format 3. For information about independent APPC LUs, see: Chapter 6, "Configuring LUs for APPC."

The default is Format 3.

Remote SAP Address

Type the remote system access point (SAP) address, which is a 2-digit hexadecimal number, a multiple of 4, between 04 and EC. For most installations, you should leave this address at the default value of 04.

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.

The default is 04. This value is recommended for most installations.

Retry Limit

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

The range is from 0 through 255. A value of 0 means the system uses its internal default retry limit. The default is 10.

Max BTU Length

Specify the maximum length for the basic transmission unit (BTU), which is the number of bytes that can be transmitted in a single data-link control frame. A BTU is also called an I-frame.

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.

The range is from 265 through 16393. The default for token ring is 1929; the default for Ethernet is 1493.

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.

The range is from 0 through 30; the default is 3.

Response (t1) Timeout

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

The values used for Default for the Response Timeout are 400 milliseconds for a local ring and 2 seconds for a remote ring.

Receive ACK (t2) Timeout

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

The values used for Default for the Receive ACK Timeout are 80 milliseconds for a local ring and 800 milliseconds for a remote ring.

Inactivity (ti) Timeout

Select the amount of time that the link can be inactive before the local system treats it as nonfunctioning and shuts it down.

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.

The values used for Default for the Inactivity Timeout are 5 seconds for a local ring and 25 seconds for a remote ring.

Note

The preceding timeout values — Response Timeout or t1, Receive ACK Timeout or t2, and Inactivity Timeout or 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 data link control (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 Microsoft Windows NT Resource Guide.

Receive ACK Threshold

Specify the maximum number of frames that the local system can receive from the remote system before sending a response. The Receive ACK Threshold should be set 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.

The range is from 1 through 127; the default is 2.

Unacknowledged Send Limit

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.

The range is from 1 through 127; the default is 8.

After Configuring Advanced 802.2 Settings

After specifying advanced 802.2 settings in the 802.2 Setup dialog box (advanced settings), shown in Figure 3.3, choose a button according to the following:

To accept the settings, choose the OK button.

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


Basic SDLC Configuration
Configuring Servers and Connections	11 of 18

Configuring Connections

Basic SDLC Configuration

To view or configure basic SDLC settings, you must first view or configure initial connection settings, as described in: "Initial Connection Configuration" earlier in this chapter.

To view or modify basic settings for an existing SDLC connection

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

2.	From the Services menu, choose Properties.

The Connection Properties dialog box, similar to the one shown in Figure 3.1, appears.

3.	Choose the Setup button.

The SDLC Setup dialog box appears. For an illustration of the dialog box and details about the settings, see the next section.

To configure basic settings for a new SDLC connection

1.	Configure initial connection properties for an SDLC connection, as described in: "Initial Connection Configuration" and "List of Connection Properties" earlier in this chapter.

2.	In the Connection Properties dialog box, similar to the one shown in Figure 3.1, choose the Setup button.

The SDLC Setup dialog box appears. For an illustration of the dialog box and details about the settings, see the following section.

List of Basic SDLC Settings

When you choose the Setup button with an SDLC connection, the dialog box shown in Figure 3.4 appears. For information about choosing the Setup button from the Connection Properties dialog box, see the preceding section.

Figure 3.4    SDLC Setup Dialog Box (Basic Settings)

Find the items appropriate to your configuration, and supply information as follows:

Dial Data

If this connection uses a switched line, type the information used when dialing (from 1 through 40 characters). 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.

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

With a leased SDLC line, this field is unavailable.

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

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 that appears in the Local Node ID box.

Note

Do not use 000 or FFF for the first three digits of the Local Node ID. These values are reserved.

The default for Local Node ID is 05D FFFFF.

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 name identifying the SNA network of the remote system. (Format 3 is the default XID type.) 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 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.

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.

If this connection will access an AS/400 computer, type the Network Name of the AS/400 (the RMTNETID on the AS/400) in this box. For more information, see your APPN documentation.

This parameter, the Network Name (Remote Node), is different from the Network Name for the local node. For information, see: "Configuring Servers" earlier in this chapter.

For more information about Network Name (Remote Node), see: "Using Remote Node Identifiers" in Chapter 1.

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 name that identifies the remote system on the SNA network. (Format 3 is the default XID type.) The name can be from one through eight characters long, and can contain alphanumeric characters and the special characters $, #, and @.

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.

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). For information, contact the host administrator.

If this connection will access an AS/400 computer, type the name of the AS/400 in this box.

This parameter, the Control Point Name (Remote Node), is different from the Control Point Name for the local node. For information, see: "Configuring Servers" earlier in this chapter.

For more information about Control Point Name (Remote Node), see: "Using Remote Node Identifiers" in Chapter 1.

Remote Node ID

If instructed to by the administrator of a remote host, peer, or downstream system, type 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.

Note

Do not use 000 or FFF for the first three digits of the Remote Node ID. These values are reserved.

For more information about Remote Node ID, see: "Using Remote Node Identifiers" in Chapter 1.

Connection Activation Limits (Retry Timers)

From the SDLC Setup dialog box, shown in Figure 3.4, you can configure connection activation limits (also known as retry timers). To do this, choose the Retry Timers button, and configure the activation limits as follows:

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.

After Configuring Basic SDLC Settings

After specifying basic SDLC settings in the SDLC Setup dialog box, shown in Figure 3.4, choose a button according to the following:

To configure advanced settings, choose the Advanced button.

The SDLC Setup dialog box expands to show the advanced fields. For information, see: "List of Advanced SDLC Settings" later in this chapter.

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

The SNA Server program is designed to provide reasonable default settings wherever possible.

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


Advanced SDLC Configuration
Configuring Servers and Connections	12 of 18

Configuring Connections

Advanced SDLC Configuration

After configuring basic SDLC settings, you can configure advanced SDLC settings. SNA Server is designed to provide reasonable defaults for all advanced settings. The defaults will be appropriate for many installations; for some installations, the settings will need to be adjusted.

To view or modify advanced settings for an existing SDLC connection

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

2.	From the Services menu, choose Properties.

The Connection Properties dialog box, similar to the one shown in Figure 3.1, appears.

3.	Choose the Setup button.

The SDLC Setup dialog box, shown in Figure 3.4, appears. For details about the settings in the dialog box, see the preceding section.

4.	Choose the Advanced button.

The SDLC Setup dialog box expands to show the advanced fields. For information, see: "List of Advanced SDLC Settings" later in this chapter.

To configure advanced settings for a new SDLC connection

1.	Configure initial connection properties for an SDLC connection, as described in: "Initial Connection Configuration" and "List of Connection Properties" earlier in this chapter.

2.	Configure basic SDLC settings, as described in the preceding section.

3.	In the SDLC Setup dialog box, shown in Figure 3.4, choose the Advanced button.

The SDLC Setup dialog box expands to show the advanced fields. For information, see the following section.

List of Advanced SDLC Settings

When you choose the Advanced button in the SDLC Setup dialog box, the dialog box expands as shown in Figure 3.5. For information about accessing the SDLC Setup dialog box advanced settings, see the preceding section.

Figure 3.5    SDLC Setup Dialog Box (Advanced Settings)

Find the items appropriate to your configuration, and supply information as follows:

XID Type

Select the type of identifying information for SNA Server to send:

Format 0 sends only the Node ID. Use this option only if the host 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.

If you want to use independent APPC LUs on this connection, you must select Format 3. For information about independent APPC LUs, see Chapter 6, "Configuring LUs for APPC."

The default is Format 3.

Encoding

Select the encoding scheme for your modem to use:

NRZ — Nonreturn to zero

NRZI — Nonreturn to zero inverted

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

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.

When multiple SDLC connections accept incoming calls and use the same link service, the encoding (NRZ/NRZI) settings for all the connections must match.

The default is NRZI.

Duplex

Select the setting that matches your modem:

For a half-duplex modem, select Half. If none of your adapters have the Constant RTS option set, you can only choose half-duplex. (The Constant RTS option is set in the SNA Server Setup program.)

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. (The Constant RTS option is set in the SNA Server Setup program.)

If you have an IBM SDLC adapter or an IBM MPCA adapter, and you want to use a transmission speed greater than 9600 baud, select Half, not Full. These adapters lack a coprocessor and cannot handle full-duplex transmission at high transmission speeds.

Most SNA Server computers will use the default, Half.

Data Rate

Check your adapter and modem manuals to find out if the data rate (for transmissions between the SNA Server communications adapter and the modem) can or must be set for your equipment. The settings are as follows:

"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. The default is High.

Poll Address

Type a two-digit hexadecimal number. Contact the administrator of the remote system to determine the appropriate value.

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

Do not use 00 or FF for the Poll Address. These values are reserved.

The default for Poll Address is C1.

Poll Rate

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

The range is from 1 through 50 polls per second; the default is 5.

Poll Timeout (for a peer or downstream connection)

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 time-out can cause connection problems.

This time-out 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).

The range is from 1 (one-tenth of a second) through 300 (30 seconds). The default is 10 (1 second).

Poll Retry Limit (for a peer or downstream connection)

Specify the number of times for the local system to poll the remote system if there is no response.

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

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

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.

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

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.

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

Idle Timeout (for a host or peer connection)

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 time-out can cause connection problems.

This time-out 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).

The range is from 1 (one-tenth of a second) through 300 (30 seconds). The default is 300 (30 seconds).

Idle Retry Limit (for a host or peer connection)

Specify the number of times for the local system to try to send data to the remote computer if there is no response.

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

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

Max BTU Length

Specify the maximum length for the BTU, which is the number of bytes that can be transmitted in a single data-link information frame. A BTU is also called an I-frame.

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.

The range is from 265 through 16393; the default is 265.

Multidrop Primary

If this is a leased SDLC line to a downstream system, and this server will be the primary station for a multidrop connection, select this box.

A multidrop connection is one in which a primary node communicates with multiple secondary nodes concurrently over the same physical transmission medium. For information about configuring for multidrop, see: "Configuring Multidrop Connections" later in this chapter.

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.

By default, this setting is off.

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 the remote computer's number. 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.

The range is from 10 through 500 seconds; the default is 300.

After Configuring Advanced SDLC Settings

After specifying advanced SDLC settings in the SDLC Setup dialog box (advanced settings), shown in Figure 3.5, choose a button according to the following:

To accept the settings, choose the OK button.

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

Configuring Multidrop Connections

In a multidrop connection, one primary computer communicates with multiple secondary computers at a time. SNA Server supports multidrop connections to downstream systems on leased SDLC lines.

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

Steps for Configuring Multidrop Connections

When configuring for multidrop, use the following guidelines:

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

2.	Follow the steps in: "Initial Connection Configuration," "Basic SDLC Configuration," and "Advanced SDLC Configuration," earlier in this chapter. Configure each connection to be used in the multidrop configuration as described in the following list. For information about copying properties between connections, see: "Copying Properties Between Connections" later in this chapter.

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, shown in Figure 3.5, select the Multidrop Primary Connection box. For information about accessing the advanced part of the SDLC Setup dialog box, see: "Advanced SDLC Configuration" earlier in this chapter.


Basic X.25 Configuration
Configuring Servers and Connections	13 of 18

Configuring Connections

Basic X.25 Configuration

To view or configure basic X.25 settings, you must first view or configure initial connection settings, as described in: "Initial Connection Configuration" earlier in this chapter.

To view or modify basic settings for an existing X.25 connection

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

2.	From the Services menu, choose Properties.

The Connection Properties dialog box, similar to the one shown in Figure 3.1, appears.

3.	Choose the Setup button.

The X.25 Setup dialog box appears. For an illustration of the dialog box and details about the settings, see the next section.

To configure basic settings for a new X.25 connection

1.	Configure initial connection properties for an X.25 connection, as described in: "Initial Connection Configuration" and "List of Connection Properties" earlier in this chapter.

2.	From the Connection Properties dialog box, similar to the one shown in Figure 3.1, choose the Setup button.

The X.25 Setup dialog box appears. For an illustration of the dialog box and details about the settings, see the following section.

Note

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

List of Basic X.25 Settings

When you choose the Setup button with an X.25 connection, the dialog box shown in Figure 3.6 appears. For information about choosing the Setup button from the Connection Properties dialog box, see the preceding section.

Figure 3.6    X.25 Setup Dialog Box (Basic Settings)

Find the items appropriate to your configuration, and supply information as follows:

Remote X.25 Address

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

For more information about the Remote X.25 Address, see: "Using Remote Node Identifiers" in Chapter 1.

Local Node ID

If this connection is using SVC, type the 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.

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 that appears in the Local Node ID box.

Note

Do not use 000 or FFF for the first three digits of the Local Node ID. These values are reserved.

The default for Local Node ID is 05D FFFFF.

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 name identifying the SNA network of the remote system. (Format 3 is the default XID type.) 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 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.

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.

If this connection will access an AS/400 computer, type the Network Name of the AS/400 (the RMTNETID on the AS/400) in this box. For more information, see your APPN documentation.

This parameter, the Network Name (Remote Node), is different from the Network Name for the local node. For information, see: "Configuring Servers" earlier in this chapter.

For more information about Network Name (Remote Node), see: "Using Remote Node Identifiers" in Chapter 1.

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 name that identifies the remote system on the SNA network. (Format 3 is the default XID type.) The name can be from one through eight characters long, and can contain alphanumeric characters and the special characters $, #, and @.

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.

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). For information, contact the host administrator.

If this connection will access an AS/400 computer, type the name of the AS/400 in this box.

This parameter, the Control Point Name (Remote Node), is different from the Control Point Name for the local node. For information, see: "Configuring Servers" earlier in this chapter.

For more information about Control Point Name (Remote Node), see: "Using Remote Node Identifiers" in Chapter 1.

Remote Node ID

If instructed to by the administrator of a remote host, peer, or downstream system, type 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.

Note

Do not use 000 or FFF for the first three digits of the Remote Node ID. These values are reserved.

For more information about Remote Node ID, see: "Using Remote Node Identifiers" in Chapter 1.

Connection Activation Limits (Retry Timers)

From the X.25 Setup dialog box, shown in Figure 3.6, you can configure connection activation limits (also known as retry timers). To do this, choose the Retry Timers button, and configure the activation limits as follows:

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.

After Configuring Basic X.25 Settings

After specifying basic X.25 settings in the X.25 Setup dialog box, shown in Figure 3.6, choose a button according to the following:

To configure advanced settings, choose the Advanced button.

The X.25 Setup dialog box expands to show the advanced fields. For information, see: "List of Advanced X.25 Settings" later in this chapter.

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

The SNA Server program is designed to provide reasonable default settings wherever possible.

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


Advanced X.25 Configuration
Configuring Servers and Connections	14 of 18

Configuring Connections

Advanced X.25 Configuration

After configuring basic X.25 settings, you can configure advanced X.25 settings. SNA Server is designed to provide reasonable defaults for all advanced settings. The defaults will be appropriate for many installations; for some installations, the settings will need to be adjusted.

To view or modify advanced settings for an existing X.25 connection

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

2.	From the Services menu, choose Properties.

The Connection Properties dialog box, similar to the one shown in Figure 3.1, appears.

3.	Choose the Setup button.

The X.25 Setup dialog box, shown in Figure 3.6, appears. For details about the settings in the dialog box, see the preceding section.

4.	Choose the Advanced button.

The X.25 Setup dialog box expands to show the advanced fields. For information, see: "List of Advanced X.25 Settings" later in this chapter.

To configure advanced settings for a new X.25 connection

1.	Configure initial connection properties for an X.25 connection, as described in: "Initial Connection Configuration" and "List of Connection Properties" earlier in this chapter.

2.	Configure basic X.25 settings, as described in the preceding section.

3.	In the X.25 Setup dialog box, shown in Figure 3.6, choose the Advanced button.

The X.25 Setup dialog box expands to show the advanced fields. For information, see the following section.

Note

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

List of Advanced X.25 Settings

When you choose the Advanced button in the X.25 Setup dialog box, the dialog box expands as shown in Figure 3.7. For information about accessing the X.25 Setup dialog box advanced settings, see the preceding section.

Figure 3.7    X.25 Setup Dialog Box (Advanced Settings)

Find the items appropriate to your configuration, and supply information as follows:

For a Permanent Virtual Circuit (PVC)

A PVC is constantly active, and the destination address is preset.

Packet Size

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.

The possible values are 64, 128, 256, 512, and 1024. The default is 128.

Window Size

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.

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

PVC Alias

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

The range is from 1 through the number of configured PVC channels; the default is 1.

For a Switched Virtual Circuit (SVC)

An SVC is called and cleared dynamically, instead of being constantly active. The destination address is supplied when the circuit is called.

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

Facility data is a coded string of information often used to request nondefault functions from the X.25 network for a particular SVC connection. For detailed information about how facility data is coded, see: "Facility Data Structuring for X.25 Networks" later in this chapter.

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.

User data is 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.

The default is C3; this specifies the QLLC protocol.

For Either Type of Circuit (PVC or SVC)

XID Type

Select the type of identifying information for SNA Server to send:

Format 0 sends only the Node ID. Use this option only if the host 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.

If you want to use independent APPC LUs on this connection, you must select Format 3. For information about independent APPC LUs, see: Chapter 6, "Configuring LUs for APPC."

The default is Format 3.

Max BTU Length

Specify the maximum length for the BTU, which is the number of bytes that can be transmitted in a single data-link information frame.

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.

The range is from 265 through 16393. The default for host connections is 265; the default for peer connections is 1033.

After Configuring Advanced X.25 Settings

After specifying advanced X.25 settings in the X.25 Setup dialog box (advanced settings), shown in Figure 3.7, choose a button according to the following:

To accept the settings, choose the OK button.

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

Facility Data Structuring for X.25 Networks

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.

Facility Data Examples

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 2-character identifier there are 4 characters (in this case, 4 occurrences of the A character). The second request follows, beginning with a 2, indicating that after the 2-character identifier there are 2 characters (2 occurrences of the B character).

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

Facility request		Description
42 08 08		Packet size
43 04 07		Window sizes
01 01		Reverse charging
When these requests are concatenated, the following facility data string is created:

4208084304070101

The characters used after the identifiers vary between sites. For a table of facility requests common to most sites, see the next section.

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.

Common Identifiers

The following table shows commonly used identifiers for facility requests:

Facility	Identifier	Parameters	Meaning
Reverse charging	01	0001	Reverse charging NOT requested Reverse charging requested
Packet sizes	42	0r0s	r = receive packet  sizes = 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 Configuration
Configuring Servers and Connections	15 of 18

Configuring Connections

Basic Channel Configuration

To view or configure basic Channel settings, you must first view or configure initial connection settings, as described in: "Initial Connection Configuration" earlier in this chapter.

To view or modify basic settings for an existing Channel connection

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

2.	From the Services menu, choose Properties.

The Connection Properties dialog box, similar to the one shown in Figure 3.1, appears.

3.	Choose the Setup button.

The Channel Attached Setup dialog box appears. For an illustration of the dialog box and details about the settings, see the next section.

To configure basic settings for a new Channel connection

1.	Configure initial connection properties for a Channel connection, as described in: "Initial Connection Configuration" and  "List of Connection Properties" earlier in this chapter.

2.	In the Connection Properties dialog box, similar to the one shown in Figure 3.1, choose the Setup button.

The Channel Attached Setup dialog box appears. For an illustration of the dialog box and details about the settings, see the following section.

List of Basic Channel Settings

When you choose the Setup button with a Channel connection, the dialog box shown in Figure 3.8 appears. For information about choosing the Setup button from the Connection Properties dialog box, see the preceding section.

Figure 3.8    Channel Attached Setup Dialog Box (Basic Settings)

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, 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. Notify the host administrator of the Local Node ID used for your system. The numbers should match corresponding parameters in the VTAM PU definition: block number should match IDBLK, and node number should match IDNUM.

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 of the Local Node ID. These values are reserved.

The default for Local Node ID is 05D FFFFF.

Connection Activation Limits (Retry Timers)

From the Channel Attached Setup dialog box, shown in Figure 3.8, you can configure connection activation limits (also known as retry timers). To do this, choose the Retry Timers button, and configure the activation limits as follows:

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.

After Configuring Basic Channel Settings

After specifying basic Channel settings in the Channel Attached Setup dialog box, shown in Figure 3.8, choose a button according to the following:

To configure advanced settings, choose the Advanced button.

The Channel Attached Setup dialog box expands to show the advanced fields. For information, see: "List of Advanced Channel Settings" later in this chapter.

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

The SNA Server program is designed to provide reasonable default settings wherever possible.

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


Advanced Channel Configuration
Configuring Servers and Connections	16 of 18

Configuring Connections

Advanced Channel Configuration

After configuring basic Channel settings, you can configure advanced Channel settings. SNA Server is designed to provide reasonable defaults for all advanced settings. The defaults will be appropriate for many installations; for some installations, the settings will need to be adjusted.

To view or modify advanced settings for an existing Channel connection

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

2.	From the Services menu, choose Properties.

The Connection Properties dialog box, similar to the one shown in Figure 3.1, appears.

3.	Choose the Setup button.

The Channel Attached Setup dialog box, shown in Figure 3.8, appears. For details about the settings in the dialog box, see the preceding section.

4.	Choose the Advanced button.

The Channel Attached Setup dialog box expands to show the advanced fields. For information, see: "List of Advanced Channel Settings" later in this chapter.

To configure advanced settings for a new Channel connection

1.	Configure initial connection properties for a Channel connection, as described in: "Initial Connection Configuration" and "List of Connection Properties" earlier in this chapter.

2.	Configure basic Channel settings, as described in the preceding section.

3.	In the Channel Attached Setup dialog box, shown in Figure 3.8, choose the Advanced button.

The Channel Attached Setup dialog box expands to show the advanced fields. For information, see the following section.

List of Advanced Channel Settings

When you choose the Advanced button in the Channel Attached Setup dialog box, the dialog box expands as shown in Figure 3.9. For information about accessing the Channel Attached Setup dialog box advanced settings, see the preceding section.

Figure 3.9    Channel Attached Setup Dialog Box (Advanced Settings)

Find the items appropriate to your configuration, and supply information as follows:

XID Type

Select the type of identifying information for SNA Server to send:

Format 0 sends only the Node ID. Use this option only if the host 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.

The default is Format 3.

Max BTU Length

Specify the maximum length for the BTU, which is the number of bytes that can be transmitted in a single data-link information frame. A BTU is also called an I-frame.

For host connections, specify a Max BTU Length less than or equal to the VTAM PU definition for the MAXDATA =  parameter.

The range is from 265 through 16393; the default is 4105.

After Configuring Advanced Channel Settings

After specifying advanced Channel settings in the Channel Attached Setup dialog box (advanced settings), shown in Figure 3.9, choose a button according to the following:

To accept the settings, choose the OK button.

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


Copying Properties Between Connections
Configuring Servers and Connections	17 of 18

Copying Properties Between Connections

To simplify the process of configuring connections, you may want to copy properties from one connection to another.

To copy properties between connections

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

2.	From the Services menu, choose Copy Properties.

3.	In the Copy Properties dialog box, select one or more connections to which you want to copy properties:

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.

If you copy properties to an active connection, the properties take effect when the connection is stopped and restarted. For information about stopping and restarting a connection, see: Chapter 11, "Managing SNA Server."

4.	Choose the OK button.


Moving a Connection to a Different Server
Configuring Servers and Connections	18 of 18

Moving a Connection to a Different Server

After configuring a connection, you can move it to a different server.

To move a connection to a different server

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

2.	From the Services menu, choose Move Connection.

The Move dialog box appears.

3.	In the To Server box, type the name of the server to which you want to move the connection, or select the server from the list.

4.	Choose the OK button.


Configuring for 3270
Chapter 4	1 of 16

Configuring for 3270

The 3270 LU allows a user to access a host system through 3270 terminal emulation software on a PC. Before you can configure 3270 LUs on an SNA server, you must first configure the connection the LUs will use. You can create 3270 LUs one at a time, or in a consecutively numbered range, and you can specify whether the 3270 LU(s) will be used for display or printing. After you have created the LUs, you can group them into pools. Then, to make the LUs available to users, you must assign the LUs and/or LU pools to users and/or groups.


Steps for Configuring for 3270
Configuring for 3270	2 of 16

Steps for Configuring for 3270

The following list tells the steps to take for configuring for 3270:

1.	Configure the server(s) and connection(s) that the 3270 LU(s) will use.

For information about configuring servers and connections, see: Chapter 3, "Configuring Servers and Connections." For information about configuring connections to a host, see: "Working with Host Connections and 3270" in Chapter 5.

2.	Configure the 3270 LU(s) that will access the host system.

You can specify whether the 3270 LU(s) will be used for display or printing. For display LUs, you can specify the display model, which controls the size of the display.

If you are making a host connection available to a downstream system via a downstream connection, you do not need to configure any 3270 LUs for downstream access. On a downstream connection, only downstream LUs are used. For information, see: Chapter 9, "Configuring Downstream Connections and LUs."

3.	If desired, create 3270 LU pools and assign 3270 LUs to them.

A 3270 LU pool groups 3270 LUs together, allowing more flexible access to the LUs. Users who are assigned the pool can get access to an LU as long as one of the LUs in the pool is available. For more information about LU pools, see: Chapter 10, "Using LU Pools to Maximize Access."

4.	Assign the 3270 LU(s) or LU pool(s) to one or more users.

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

Note

Most configuration changes in SNA Server take effect the next time the server (node) is started. Therefore, after making changes to 3270 LUs in an existing configuration, stop and restart the affected servers (nodes) in order to put the changes into effect. For more information about stopping and starting servers and connections, see: Chapter 11, "Managing SNA Server."


Configuration Steps Described in This Chapter
Configuring for 3270	3 of 16

Steps for Configuring for 3270

Configuration Steps Described This Chapter

This chapter tells how to carry out steps 2 and 4. Specifically, this chapter tells how to do the following actions involving 3270 LUs:

Assign a 3270 LU, or a range of 3270 LUs, to a connection. A range of 3270 LUs will allow multiple users to connect to the host system. For information, see: "Configuring Individual 3270 LUs" or "Configuring a Range of 3270 LUs" later in this chapter.

Configure the numbering for a new range of 3270 LUs, by specifying the lowest LU number and the number of LUs in the range. For information, see: "Configuring Numbering for a 3270 LU Range" later in this chapter.

After creating a range of LUs, you can change the numbering of individual LUs in the range.

Configure properties for a new 3270 LU or a new range of 3270 LUs. This includes specifying whether the LU will be used for display or printing and, for display LUs, specifying the display model that the LU works with. For information, see: "Configuring Properties for a 3270 LU" or "Configuring Properties for a 3270 LU Range" later in this chapter.

View or modify an existing 3270 LU, regardless of whether it was created as part of a range. For information, see: "Configuring Individual 3270 LUs" later in this chapter.

Copy properties from one LU to another. For information, see: "Copying Properties Between LUs" later in this chapter.

Move an LU from one connection to another. For information, see: "Moving an LU to a Different Connection" later in this chapter.

Assign one or more LUs or LU pools to a network user or group. For information, see: "Giving Users Access to 3270 LUs" later in this chapter.

Delete a 3270 LU, or delete the assignment of a 3270 LU to a user or group. For information, see: "Deleting LUs" later in this chapter.


Configuring Individual 3270 LUs
Configuring for 3270	4 of 16

Configuring Individual 3270 LUs

Before you can assign a new LU to a connection, you must configure the connection. For information about connections, see: Chapter 3, "Configuring Servers and Connections."

You can assign and configure new 3270 LUs one at a time, or as a consecutively numbered range. For information about assigning and configuring a range of new 3270 LUs, see "Configuring a Range of 3270 LUs" later in this chapter. You can view or modify individual LUs in a range after the range has been created.

You can copy properties from one 3270 LU to another, or move a 3270 LU from one connection to another. For information, see: "Copying Properties Between LUs" and "Moving an LU to a Different Connection" later in this chapter.

Check with the host administrator to determine the appropriate names and numbers for 3270 LUs on your system.

To assign a new 3270 LU

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

The connection is highlighted, as shown in Figure 4.1.

Figure 4.1    A Highlighted Connection

2.	From the Services menu, choose Assign LUs.

The dialog box shown in Figure 4.2 appears.

Figure 4.2    Insert LU Dialog Box

3.	Under New Logical Unit, select the 3270 option button.

4.	Choose the OK button.

The New 3270 LU Properties dialog box appears. For information, see the next section.

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.	From the Services menu, choose Properties.

The 3270 LU Properties dialog box appears. For information, see the next section.


Configuring Properties for a 3270 LU
Configuring for 3270	5 of 16

Configuring Individual 3270 LUs

Configuring Properties for a 3270 LU

For information about assigning a new 3270 LU, or accessing an existing one, see the preceding procedures. When you assign or access a 3270 LU, the New 3270 LU Properties dialog box or the 3270 LU Properties dialog box appears. The 3270 LU Properties dialog box is shown in Figure 4.3.

Figure 4.3    3270 LU Properties Dialog Box

Find the items appropriate to your configuration, and supply information as follows. If you are configuring a 3270 LU for a DFT connection, see also: "Numbers Needed for DFT LUs" later in this chapter.

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

Type a number identifying the 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 on the host.

If this 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" later in this chapter.

If the number you specify has already been assigned to an LU or an APPC LULU pair on the current connection, a message box appears, and you must change the number.

The range for LU Number is from 1 through 254.

LU Name

Type 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 name or pool name (except for APPC LU names) on the server.

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 to a Different Connection" later in this chapter.

Pool

If the LU has already been assigned to a pool, the pool name appears here. For information about LU pools, see: Chapter 10, "Using LU Pools to Maximize Access."

Comment

Optionally, type a comment of up to 25 characters.

LU Type

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

The default is Display.

Display Model

If you select the Display option button for the LU Type, you can select 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.

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

If the LU is assigned to a pool, the display model setting of the pool overwrites the setting of the LU, and the setting of the LU is unavailable.

The default is Model 2.

Model can be overridden

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

If the LU is assigned to a pool, the model override setting of the pool overwrites the setting of the LU, and the setting of the LU is unavailable.

By default, this check box is selected.

After Configuring 3270 LU Properties

After specifying 3270 LU properties, in the 3270 LU Properties dialog box, shown in Figure 4.3, choose a button according to the following:

To accept the settings, choose the OK button.

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

After configuring 3270 LUs, you can group them into LU pools. For information, see: Chapter 10, "Using LU Pools to Maximize Access."

Numbers Needed for DFT LUs

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


Configuring a Range of 3270 LUs
Configuring for 3270	6 of 16

Configuring a Range of 3270 LUs

Before you can assign LUs to a connection, you must configure the connection. For information about connections, see: Chapter 3, "Configuring Servers and Connections."

On a DFT connection, the only way to configure LUs is one at a time. For information about configuring LUs one at a time, see: "Configuring Individual 3270 LUs" earlier in this chapter.

On an 802.2, SDLC, or X.25 connection, you can configure multiple LUs at one time by configuring them as a consecutively numbered range. Multiple 3270 LUs allow multiple users to access the host simultaneously. After configuring the range of LUs, you can modify the numbering and properties of individual LUs in the range. For information about assigning and configuring individual 3270 LUs, see: "Configuring Individual 3270 LUs" earlier in this chapter.

After configuring 3270 LUs, you can group them into LU pools. For information, see: Chapter 10, "Using LU Pools to Maximize Access."

In addition, you can copy properties from one 3270 LU to another, or move a 3270 LU from one connection to another. For information, see: "Copying Properties Between LUs" and "Moving an LU to a Different Connection" later in this chapter.

Check with the host administrator to determine the appropriate names and numbers for 3270 LUs on your system.

To assign a range of new 3270 LUs

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

The connection is highlighted, as shown in Figure 4.1.

2.	From the Services menu, choose Assign LUs.

The Insert LU dialog box, shown in Figure 4.2, appears.

3.	Under New Logical Unit, select the 3270 option button.

4.	Under New Logical Unit, select the Range of LUs check box.

5.	Choose the OK button.

The Add LU Range dialog box appears. For information, see the next section.


Configuring Numbering for a 3270 LU Range
Configuring for 3270	7 of 16

Configuring a Range of 3270 LUs

Configuring Numbering for a 3270 LU Range

For information about assigning a range of new 3270 LUs, see the preceding procedure. When you assign a range of 3270 LUs, the dialog box shown in Figure 4.4 appears.

Figure 4.4    Add LU Range Dialog Box

Find the items appropriate to your configuration, and supply information as follows:

Base LU Name

Type 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 fewer. If you plan to use two-digit extension numbers, limit the base name to six characters or fewer.

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.

First LU Number

Type the first LU number in the range. An LU number identifies 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 on the host.

If the number you specify has already been assigned to an LU or an APPC LULU pair on the current connection, a message box appears, and you must change the number.

Possible values for the first LU number are from 1 through 254.

Number of LUs

Type the number of LUs that you want in the 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.

Possible values for the number of LUs are from 2 through 254.

Selected LU Range

The range of LU names that you specified appears here.

After Configuring Numbering for a 3270 LU Range

After typing the appropriate LU range values, in the Add LU Range dialog box, shown in Figure 4.1, choose a button according to the following:

To modify the extension numbering format (displayed under Selected LU Range), choose the Options button. See the next section.

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

To accept the settings and begin configuring the properties for the LU range, choose the OK button. For information, see: "Configuring Properties for a 3270 LU Range" later in this chapter.


Modifying the Extension Numbering Format
Configuring for 3270	8 of 16

Configuring a Range of 3270 LUs

Modifying the Extension Numbering Format

For information about accessing the dialog box described in this section, see: "Configuring a Range of 3270 LUs" and "Configuring Numbering for a 3270 LU Range" earlier in this chapter.

When you choose the Options button in the Add LU Range dialog box, the dialog box expands as shown:

Figure 4.5    Add LU Range Dialog Box (with Numbering Options Displayed)

Find the items appropriate to your configuration, and supply information as follows:

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 fewer. If the base name is five characters long, limit the extensions to three digits or fewer.

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.

Number System

Select the Decimal or Hexadecimal option button. As with other extension number format options, the number system affects the extension numbers, not the LU numbers.

The default is Decimal.

Add Leading Zeroes (07 vs. 7)

If you do not want leading zeroes to be added to the extension numbers, clear this check box.

Leading zeroes ensure that LU names will display in correct order. For example, 09 will appear before 10, while 9 will appear after.

By default, the Add Leading Zeroes check box is selected.

After Modifying the Extension Numbering Format

After modifying the extension numbering format, in the Add LU Range dialog box, as shown in Figure 4.5, choose a button according to the following:

To accept the settings and begin configuring the properties for the LU range, choose the OK button. For information, see the next section.

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


Configuring Properties for a 3270 LU Range
Configuring for 3270	9 of 16

Configuring a Range of 3270 LUs

Configuring Properties for a 3270 LU Range

After assigning and numbering a range of 3270 LUs, you can configure the LUs in the range. All the LUs will receive the same properties; you can modify individual LUs after configuring the range. For information about modifying individual LUs, see: "Configuring Individual 3270 LUs" earlier in this chapter.

To configure properties for a range of 3270 LUs

1.	Assign the range of 3270 LUs to a connection, as described in: "Configuring a Range of 3270 LUs" earlier in this chapter.

2.	Configure the numbering for the range, as described in: "Configuring Numbering for a 3270 LU Range" earlier in this chapter.

3.	In the Add LU Range dialog box, shown in Figures 4.4 and 4.5, choose the OK button.

The 3270 LU Range Properties dialog box appears. For information, see the following section.

Range Properties

When you choose the OK button in the Add LU Range dialog box, the dialog box shown in Figure 4.6 appears. For information about accessing the 3270 LU Range Properties dialog box, see the preceding procedure.

Figure 4.6    3270 LU Range Properties Dialog Box

Find the items appropriate to your configuration, and supply information as follows:

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 to a Different Connection" later in this chapter.

Comment

Optionally, type a comment of up to 25 characters.

LU Type

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

The default is Display.

Display Model

If you select the Display option button for the LU Type, you can select 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.

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

The default is Model 2.

Model can be overridden

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

By default, this check box is selected.

After Configuring Properties for a 3270 LU Range

After specifying properties for a 3270 LU range, in the 3270 LU Range Properties dialog box, shown in Figure 4.6, choose a button according to the following:

To accept the settings, choose the OK button.

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

After configuring 3270 LUs, you can group them into LU pools. For information, see: Chapter 10, "Using LU Pools to Maximize Access."


Copying Properties Between LUs
Configuring for 3270	10 of 16

Copying Properties Between LUs

You can copy properties from one LU to another, regardless of whether either LU was created as part of a range.

To copy properties between LUs

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

2.	From the Services menu, choose Copy Properties.

The Copy Properties dialog box appears.

3.	Under To Logical Unit (LU), select one or more LUs to which you want to copy properties:

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.

If you copy properties to an active LU, the properties take effect when the LU is reset. For information about resetting an LU, see: Chapter 11, "Managing SNA Server."

4.	Choose the OK button.


Moving an LU to a Different Connection
Configuring for 3270	11 of 16

Moving an LU to a Different Connection

You can move one or more LUs to a different connection, regardless of whether the LUs were created as part of a range.

To move one or more LUs to a different connection

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

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.

2.	From the Services menu, choose Move LU.

The Move dialog box appears.

3.	In the To Connection box, select the connection to which you want to move the LU.

4.	Choose the OK button.


Setting Up User and Group Access
Configuring for 3270	12 of 16

Setting Up User and Group Access

In order for users to 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, the users gain access to the host system(s) that the LUs connect to.

In addition to assigning 3270 LUs and LU pools to users, you can control the order in which LUs appear in lists seen by the users. You can also copy properties and LUs from one user to another.


Adding, Viewing, or Modifying Users or Groups
Configuring for 3270	13 of 16

Setting Up User and Group Access

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 server or on the local area network.

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.	From the Users menu, choose New User.

The Add Users and Groups dialog box appears:

4.	In the List Names From box, select the domain from which to list users or groups who have network accounts, or select the name of the local server.

5.	In the Names box, from the list of users and groups who have accounts, select the one you want to add.

6.	Choose the Add button.

7.	Choose the OK button.

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.	From the File menu, choose Save Configuration.

To view or modify properties for the user or group, see the next procedure.

To access a user or group for viewing or modifying

1.	In the Users and Groups window, from the View menu, choose Configured Users.

2.	Select the user or group.

3.	From the Users menu, choose Properties.

The User Properties or Group Properties dialog box appears. For an illustration of the User Properties dialog box and details about the settings, see the following section.

Configuring Properties for a 3270 User or Group

You can configure properties for each user or group, or you can copy properties from one user or group to another. For information about copying properties, see: "Copying Properties and LUs Between Users and/or Groups" later in this chapter.

For information about adding a new user or group to an SNA server, or accessing an existing user or group, see the preceding procedures. When you access an existing user or group, the User Properties or Group Properties dialog box appears. The User Properties dialog box is shown in Figure 4.7.

Figure 4.7    User 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.

Default Local APPC LU

If this user will be using APPC programs (transaction programs, 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: Chapter 6, "Configuring LUs for APPC" or Chapter 7, "Configuring for 5250 Emulation in the AS/400 Environment."

Default Remote APPC LU

If this user will be using APPC programs (transaction programs, 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: Chapter 6, "Configuring LUs for APPC" or Chapter 7, "Configuring for 5250 Emulation in the AS/400 Environment."

After Configuring Properties for a User or Group

After configuring properties for a user or group, in the User Properties dialog box, shown in Figure 4.7, or the Group Properties dialog box, choose a button according to the following:

To accept the settings, choose the OK button.

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


Giving Users Access to 3270 LUs
Configuring for 3270	14 of 16

Setting Up User and Group Access

Giving Users Access to 3270 LUs

To give users access to host systems for which you have configured connections and 3270 LUs, you may first want to group the 3270 LUs into LU pools. When an LU pool containing LUs is assigned to a user, the user can get a session through that pool as long as any of the pooled LUs are available. For more information about LU pools, see: Chapter 10, "Using LU Pools to Maximize Access."

Important

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

You can change the order in which LUs appear in lists seen by the user. For example, you can place an LU at the top of the list, in order to encourage the user to try that LU first.

If a user is assigned LUs through one or more accounts, such as group accounts and the user's individual account, the LUs do not accumulate. Instead, one account determines the access for that user. The account that determines this access is the account found first in the following search order:

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.

For information about configuring 3270 LUs, see the previous sections in this chapter.

To assign one or more 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.

You can distinguish the type of account by the appearance of the icon next to the user or group name.

3.	From the Users menu, choose Assign LUs.

The Assign User LU/Pool Sessions dialog box appears.

4.	Under Available LUs and Pools, 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 needs access to multiple LU sessions, assign one LU or LU pool for each session that the user needs. You can assign a pool multiple times to the same user.

5.	Choose the OK button.

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.	From the File menu, choose Save Configuration.

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 that you want to control the listed order of LUs for.

3.	From the LUs and/or LU pools listed opposite the selected user or group, select one or more LUs and/or LU 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.

Moving an LU or pool up in the list means it will be assigned a smaller number.

4.	From the Users menu, choose Reorder LUs.

The Reorder LU Session dialog box appears.

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

6.	Choose the OK button.

The other LU session numbers shift to accommodate the new ranking.

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.	From the File menu, choose Save Configuration.


Copying Properties and LUs Between Users and/or Groups
Configuring for 3270	15 of 16

Setting Up User and Group Access

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.

3.	From the Users menu, choose Copy Properties.

The Copy Properties dialog box appears.

4.	Under To User or Group, select the user or group to which you want to copy properties and LUs.

5.	Choose the OK button.

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.	From the File menu, choose Save Configuration.


Deleting LUs
Configuring for 3270	16 of 16

Setting Up User and Group Access

Deleting LUs

You can delete a 3270 LU, or delete the assignment of a 3270 LU to a user or group.

To delete a 3270 LU

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

2.	From the Edit menu, choose Delete.

3.	When prompted for confirmation, choose the Yes button.

To delete the assignment of a 3270 LU to a user or group

1.	In the Users and Groups window, from the View menu, choose Configured Users.

2.	Select the LU as it is listed across from the user or group.

3.	From the Edit menu, choose Delete.

4.	When prompted for confirmation, choose the Yes button.

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.	From the File menu, choose Save Configuration.


Working with Settings in VTAM and NCP
Chapter 5	1 of 19

Working with Settings in VTAM and NCP

This chapter tells how settings used in VTAM, NCP, and CICS correspond to settings in SNA Server. The chapter includes sections describing the following:

Host connections and 3270

NCP parameters for independent APPC

VTAM and CICS parameters for independent APPC (LU 6.2)

For more information about VTAM, NCP, and CICS, see: the Microsoft SNA Server Reference and your VTAM, NCP, and CICS documentation.


Working with Host Connections and 3270
Working with Settings in VTAM and NCP	2 of 19

Working with Host Connections and 3270

The following sections provide specific information about configuration parameters to use for host connections and 3270 LUs, and briefly describe other configuration steps for 3270, such as assigning 3270 LUs to users.

For information about the basic elements of SNA Server configurations, see: Chapter 1, "Getting Started." For forms that may be helpful when configuring SNA Server, see: Appendix B, "SNA Server Preparation Forms."

For more information about configuration topics related to host connections and 3270, see the following chapters or appendix:

Configuration topic	Chapter
Host Connections	Chapter 3, "Configuring Servers and Connections"
3270 LUs; users and groups	Chapter 4, "Configuring for 3270"
3270 LU pools	Chapter 10, "Using LU Pools to Maximize Access"
NetView and RTM	Chapter 13, "Using Diagnostic Tools"
Extensions to NetView	Appendix C, "SNA Server NetView Extensions"


Configuring Host Connections
Working with Settings in VTAM and NCP	3 of 19

Working with Host Connections and 3270

Configuring Host Connections

When setting certain SNA Server parameters for a host connection, you must match values set on the host or on frontend processors for the host. Host values are configured in VTAM; frontend processor values are configured in the Network Control Program (NCP).

Note

As the tables show, if both the local and remote Network Name and Control Point Name are needed, they must be set in different ways. The local Network Name and Control Point Name are set in the Server Properties dialog box (since these names apply across all connections). The remote Network Name and Control Point Name are set in the Connection Properties dialog box (since these names must be set individually for each connection). For information about the local Control Point Name and Network Name, see: "Configuring Servers" in Chapter 3. For information about the remote Control Point Name and Network Name, see: "Using Remote Node Identifiers" in Chapter 1, and "List of Basic 802.2 Settings," "List of Basic SDLC Settings," or "List of Basic X.25 Settings" in Chapter 3.

Table 5.1 shows how parameters for SNA servers correspond to VTAM host parameters.

Table 5.1    SNA Server and VTAM Parameters for SNA Servers

SNA parameter	VTAM parameter
Control Point Name (Local Node)†	CPNAME= in the PU definition.
Network Name (Local Node)†Note that the Network Name for the local and remote nodes is generally the same.	NETID parameter in the VTAM Start command for the local SSCP (the VTAM system to which SNA Server is attached). Note that this is generally the same as the NETID for the remote SSCP.
† The local Control Point Name and Network Name are needed only if the SNA server will accept incoming calls, or will be used for LU 6.2 (APPC).

Table 5.2 shows how SNA Server parameters for 802.2 connections correspond to VTAM or NCP parameters. Asterisks (*) indicate required parameters.

Table 5.2    SNA Server, VTAM, and NCP Parameters for 802.2 Connections

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 that the Network Name for the 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  MAXDATA)
* Required parameter in SNA Server

Table 5.3 shows how SNA Server parameters for SDLC connections correspond to VTAM or NCP parameters. Asterisks (*) indicate required parameters.

Table 5.3    SNA Server, VTAM and NCP Parameters for SDLC Connections

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 that the Network Name for the 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  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

Table 5.4 shows how SNA Server parameters for X.25 connections correspond to VTAM or NCP parameters. Asterisks (*) indicate required parameters.

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

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 that the Network Name for the 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  MAXDATA)
* Required parameter in SNA Server


Configuring 3270 LUs
Working with Settings in VTAM and NCP	4 of 19

Working with Host Connections and 3270

Configuring 3270 LUs

The 3270 LU allows a user to access a host system through 3270 terminal emulation software on a PC. Each 3270 LU is assigned to a host connection. You can create 3270 LUs one at a time, or in a consecutively numbered range, and you can specify whether the 3270 LU(s) will be used for display or printing. For detailed information about configuring 3270 LUs, see: Chapter 4, "Configuring for 3270."

Configuring a 3270 LU is simpler than configuring the host connection that the LU will use. There is one 3270 LU parameter in SNA Server that corresponds to a VTAM or NCP parameter. To find out the value to set for this parameter, consult with the host administrator.

Table 5.5    SNA Server, VTAM, and NCP Parameter for 3270 LUs

SNA parameter	VTAM or NCP parameter

LU Number*	LOCADDR= parameter in the LU definition

* Required parameter in SNA Server

For information about pooling 3270 LUs in order to make them more readily available to multiple users, see: Chapter 10, "Using LU Pools to Maximize Access."


Assigning 3270 LUs to Users
Working with Settings in VTAM and NCP	5 of 19

Working with Host Connections and 3270

Assigning 3270 LUs to Users

If you are using 3270 terminal emulation on PCs in your installation, after configuring servers, connections, and 3270 LUs, you can group the LUs together in pools. Then you can assign LUs or LU pools to users or groups. This gives the users access to the remote host(s) via the LUs.

For more information about assigning LUs to users, see: Chapter 4, "Configuring for 3270."


Sample VTAM Parameters
Working with Settings in VTAM and NCP	6 of 19

Sample VTAM Parameters

The following sections show some sample VTAM parameters for a token ring connection, an SDLC connection, and an X.25 connection.


Sample VTAM Parameters for a Token Ring Connection
Working with Settings in VTAM and NCP	7 of 19

Sample VTAM Parameters

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  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 for an SDLC Connection
Working with Settings in VTAM and NCP	8 of 19

Sample VTAM Parameters

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  MAXDATA)
The encoding scheme (NRZ versus 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


Sample VTAM Parameters for an X.25 Connection
Working with Settings in VTAM and NCP	9 of 19

Sample VTAM Parameters

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,
		NETLEVEL=80,PMOD=8,PLENGTH=256,PWINDOW=3,
		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  MAXDATA)


NCP Parameters Needed for Independent APPC
Working with Settings in VTAM and NCP	10 of 19

NCP Parameters Needed for Independent APPC

This section provides some information about NCP definitions used for supporting and defining independent LUs. The section is not intended to provide comprehensive information about NCP, which is described more thoroughly in IBM manuals such as:

Planning and Reference for NetView, NCP, VTAM (CN4D1200)

NCP, SSP, and EP Resource Definition Guide (CXDG7200)

NCP, SSP, and EP Resource Definition Reference (CXDH1200)

You may need to study other IBM documentation as well. Some of the topics to study are:

Independent LUs

Type 2.1 node support

Dynamic reconfiguration


Table of NCP Parameters That Affect Independent APPC
Working with Settings in VTAM and NCP	11 of 19

NCP Parameters Needed for Independent APPC

Table of NCP Parameters That Affect Independent APPC

The following table shows some basic recommendations for setting NCP parameters for independent APPC with an SNA server. The next sections describe the parameters in more detail.

Table 5.6    NCP Parameters: Recommendations for Independent APPC

NCP definition	NCP parameter	Recommendations
BUILD	ADDSESS	Must support the number of sessions needed.
	AUXADDR	Must support the number of additional addresses needed.
	MAXSESS	Use for setting the maximum sessions allowed for any LU. Corresponds to the sum of all the parallel session limits for all the modes with which a particular LU is partnered.
PUDRPOOL	NUMBER	Must support the number of servers accessing NCP.
LUDRPOOL	NUMILU	Must support the number of dynamically configurable LUs needed.
PU	NETID	Corresponds to the Local Network Name on the SNA server.
	PUTYPE	For independent APPC, use PUTYPE=2.
	XID	For independent APPC, use XID=YES.
LU	LOCADDR	For independent LUs with set definitions, use LOCADDR=0.
	PACING	Use a value greater than or equal to the corresponding SNA Server parameter, the Pacing Receive Count in the mode.
	VPACING	Use a value less than or equal to the corresponding SNA Server parameter, the Pacing Send Count in the mode.


BUILD Definition
Working with Settings in VTAM and NCP	12 of 19

NCP Parameters Needed for Independent APPC

BUILD Definition

The following parameters in the BUILD definition affect independent APPC:

ADDSESS=value

Is equivalent to the total number of sessions available to independent LUs. ADDSESS specifies the number of LU-LU session control blocks available for independent LUs. Note that session control blocks may be reserved for a particular LU by using RESSCB (reserved session control blocks) in the LU definition.

The sum of ADDSESS, AUXADDR, and NUMILU (described under "LUDRPOOL Definition," later in this chapter) equals the total number of control blocks available for dynamic configuration of LUs. This total should be high enough to support needed sessions, but low enough so that NCP does not exceed the storage capacity of the controller.

AUXADDR=value

Specifies the number of addresses that can be dynamically defined for both dependent and independent LUs. To allow for additional sessions between independent LUs, AUXADDR should be greater than ADDSESS. For more information about dynamic reconfiguration, see ADDSESS (the preceding description).

MAXSESS=value

Specifies the maximum number of LU-LU sessions that one independent LU can support. If you specify MAXSESS in an LU definition (as supported by NCP V6R2), the LU uses the value in the LU definition, not the BUILD definition. The limit set by MAXSESS prevents an independent LU from using up too many unreserved session control blocks.


PUDRPOOL Definition
Working with Settings in VTAM and NCP	13 of 19

NCP Parameters Needed for Independent APPC

PUDRPOOL Definition

The following parameter in the PUDRPOOL definition affects independent APPC:

NUMBER=value

Specifies the number of physical units (PUs) that can be dynamically defined.


LUDRPOOL Definition
Working with Settings in VTAM and NCP	14 of 19

NCP Parameters Needed for Independent APPC

LUDRPOOL Definition

The following parameter in the LUDRPOOL definition affects independent APPC:

NUMILU=value

Specifies the number of independent LUs that can be added through dynamic reconfiguration. Find a value high enough to support needed sessions (including control-session overhead for parallel sessions), but low enough so that NCP does not exceed the storage capacity of the controller. Note that total LUs allowed by NUMILU plus NUMTYP1 plus NUMTYP2 is limited — the exact limit depends on your version of NCP.


PU Definition
Working with Settings in VTAM and NCP	15 of 19

NCP Parameters Needed for Independent APPC

PU Definition

The following parameters in the PU definition affect independent APPC:

NETID=name

Specifies the name of an adjacent network, and corresponds to the local Network Name on the SNA server. NETID allows the network names to differ between the host and SNA Server. This name is used in XID negotiation.

PUTYPE=2

For independent APPC, use PUTYPE=2. When combined with XID=YES, this is equivalent to physical unit type 2.1.

XID=YES

For independent APPC, specify XID=YES, so that XIDs can be exchanged while in normal disconnected mode (NDM).


LU Definition
Working with Settings in VTAM and NCP	16 of 19

NCP Parameters Needed for Independent APPC

LU Definition

The following parameters in the LU definition affect independent APPC:

LOCADDR=0

For independent LUs configured by an administrator (as contrasted with LUs dynamically configured by NCP), specify LOCADDR=0.

PACING=value

Specifies the number of frames for NCP to send to an independent LU before NCP waits for a pacing response. The value for PACING should generally be greater than or equal to the corresponding SNA Server mode parameter, Pacing Receive Count. This ensures a smooth flow of data from the host to the SNA server. (SNA Server does not support adaptive pacing.)

VPACING=value

Specifies the number of frames for NCP to receive from an independent LU before NCP sends a pacing response; sometimes called the "receive window size." The value for VPACING should generally be less than or equal to the corresponding SNA Server mode parameter, Pacing Send Count. This prevents delays in sending from the SNA server to the host. (SNA Server does not support adaptive pacing.)


Sample VTAM and CICS Parameters for Independent LU 6.2
Working with Settings in VTAM and NCP	17 of 19

Sample VTAM and CICS Parameters for Independent LU 6.2

The following sections show some sample VTAM and CICS configurations for independent LU 6.2. For more information, see the appropriate IBM manuals, or access the IBM APPC forum on CompuServe; to do this, at any ! prompt, type go appc. One document available through the IBM APPC forum is MPCONT.ZIP, a multiplatform LU 6.2 configuration guide containing information about CICS and VTAM.


Sample VTAM Parameters for Use with LU 6.2
Working with Settings in VTAM and NCP	18 of 19

Sample VTAM and CICS Parameters for Independent LU 6.2

Sample VTAM Parameters for Use with LU 6.2

The lists in this section show sample VTAM parameters that might be used for communication using independent LU 6.2. The underlined values correspond to values specified in SNA Server Admin.

SERVER01	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	X
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 the 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  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 Use with LU 6.2
Working with Settings in VTAM and NCP	19 of 19

Sample VTAM and CICS Parameters for Independent LU 6.2

Sample CICS Configuration Screens for Use with 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


Configuring LUs for APPC
Chapter 6	1 of 21

Configuring LUs for APPC

APPC can be used to allow programs on peer systems to communicate with each other over an SNA network. For APPC, at least two LUs are required  one for each direction of the communications.

The type of LU used in APPC is LU 6.2. The programs that use LU 6.2 are called transaction programs (TPs).

This chapter describes the basic elements in APPC, and tells the basic procedure for configuring LUs for APPC. The chapter includes information about assigning default APPC LUs to users.

The following table tells where to find information on topics related to those in this chapter:

Topic		Source for information
VTAM, NCP, and CICS parameters used for independent APPC		Chapter 5, "Working with Settings in VTAM and NCP"
Configuring connections and LUs for 5250 emulation in the AS/400 environment		Chapter 7, "Configuring for 5250 Emulation in the AS/400 Environment"
Registry and environment variables used on computers where invokable TPs are located		Microsoft SNA Server APPC Programmer's Guide  or: Microsoft SNA Server CPI-C Programmer's Guide
APPC or CPI-C		IBM documentation


How LUs Work Together for APPC
Configuring LUs for APPC	2 of 21

How LUs Work Together for APPC

APPC generally uses a local LU and one or more remote LUs. A local APPC LU can be independent or dependent. An independent local APPC LU can communicate directly with a peer system, as shown in Figure 6.1.

Figure 6.1    Independent APPC

Independent LUs can support multiple parallel sessions. With independent LUs, there are some special requirements:

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. For information about VTAM, NCP, and CICS parameters for independent LUs, see: Chapter 5, "Working with Settings in VTAM and NCP."

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

A dependent local APPC LU requires the support of a host configuration in order to communicate with a remote TP, as shown in Figure 6.2.

Figure 6.2    Dependent APPC

Dependent local 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 in the NCP Gen.


Transaction Programs
Configuring LUs for APPC	3 of 21

Transaction Programs

The programs that use LU 6.2 are called TPs. Figure 6.3 illustrates how two TPs use LU 6.2 for APPC:

Figure 6.3    Two TPs Using LU 6.2

Figure 6.4 illustrates how three TPs use LU 6.2 for APPC:

Figure 6.4    Three TPs Using LU 6.2


Invoking and Invokable TPs
Configuring LUs for APPC	4 of 21

Transaction Programs

Invoking and Invokable TPs

There are two kinds of TPs: TPs that can invoke (that is, initiate a conversation with) other TPs, and TPs that can be invoked. A TP that can invoke another TP is called an invoking TP, and a TP that can be invoked is called an invokable TP.

The following sections describe invoking and invokable TPs. For more information about how TPs work, see: the Microsoft SNA Server APPC Programmer's Guide and the Microsoft SNA Server CPI-C Programmer's Guide.

Invoking TPs

An invoking TP can be located on any system on the SNA network. An invoking TP identifies itself by issuing a TP_STARTED verb. TP_STARTED specifies the name of the invoking TP, and may specify the LU alias that the TP uses (or may leave the LU alias blank).

Next, the invoking TP initiates the invoking process by issuing an ALLOCATE verb. In ALLOCATE, the invoking TP specifies the name of the invokable TP, and may also specify the partner LU alias (the LU alias to be used by the invokable TP).

Invoking TPs and the SNA Server Configuration

In order for an SNA server to support the beginning of the invoking process (that is, to accept the TP_STARTED and ALLOCATE verbs issued by an invoking TP), the following parameters must be configured correctly:

If the invoking TP specifies the LU alias that it uses (in TP_STARTED), that LU alias must match a local APPC LU alias on the supporting SNA server.

If the invoking TP leaves the LU alias blank in TP_STARTED, one of two methods for designating a default LU must be carried out on the supporting SNA server:

One method is to assign a Default Local APPC LU to the user or group that starts the invoking TP (that is, the user or group logged on at the system from which TP_STARTED is issued).

Another method is to designate one or more LUs as members of the Default Outgoing Local APPC LU Pool.

If the invoking TP leaves the LU alias blank in TP_STARTED, SNA Server first attempts to determine the Default Local APPC LU of the associated user or group, then attempts to assign an available LU from the Default Outgoing Local APPC LU Pool. If these attempts fail, SNA Server rejects the TP_STARTED request.

In most situations, the supporting SNA server must contain an appropriate connection to another system (host or peer). Sometimes, for testing purposes, the SNA server contains two local LUs paired together (for invoking and invokable TPs that are in the same domain); in this situation, a connection to a host or peer is not necessary.

If the invoking TP specifies the partner LU alias (in ALLOCATE), that LU alias must match a remote LU alias. In addition, that remote LU alias must be paired with the local LU alias specified in TP_STARTED. If the LU alias is left blank in ALLOCATE, a Default Remote APPC LU must be assigned to the user who started the invoking TP. If the Default Remote APPC LU is used, it must be paired with the local LU that will be used. Otherwise, the ALLOCATE verb fails.

The preceding parameters support the beginning of the invoking process. In order for the invoking process to successfully complete, additional parameters must be configured on another SNA server, as described in "Invokable TPs and the SNA Server Configuration" later in this chapter.

Invokable TPs

An invokable TP is a TP that can be invoked by another TP. Invokable TPs are written or configured (through Registry or environment variables) to supply their names to SNA Server, as a notification that they are available for incoming requests. SNA Server invokable TPs can be run on any SNA Server or client running Windows NT, Windows version 3.x, or OS/2. For information about configuring the Registry or environment variables used by invokable TPs, see: the Microsoft SNA Server APPC Programmer's Guide or the Microsoft SNA Server CPI-C Programmer's Guide.

There are two types of invokable TPs:

Operator-started invokable TPs

An operator-started invokable TP must be started by an operator before the TP can be invoked. When the operator-started invokable TP is started, it notifies SNA Server of its availability by issuing a RECEIVE_ALLOCATE verb. RECEIVE_ALLOCATE provides the name of the invokable TP.

Autostarted invokable TPs

An autostarted invokable TP can be started by SNA Server when needed. The TP must be registered on its local system, so that it can be identified to SNA Server. (For details about how the TP is registered, see: the Microsoft SNA Server APPC Programmer's Guide or the Microsoft SNA Server CPI-C Programmer's Guide.) The registered information defines the TP as autostarted, and must specify the TP name. The registered information may also specify the local LU alias that the invokable TP will use.

If no local LU alias is registered with autostarted TPs, the resulting SNA Server configuration can be more flexible in responding to invoking requests. For more information about such flexible configurations, see "TP Name Not Unique; Local LU Alias Unspecified," later in this chapter.

After an autostarted invokable TP is started by SNA Server, the TP issues RECEIVE_ALLOCATE (just as an operator-started TP does). RECEIVE_ALLOCATE must provide the same TP name as was registered for the TP.

Each SNA server maintains a list of invokable TP names and any LU aliases associated with the TP names. When a request comes in from an invoking TP, the SNA server compares the requested invokable TP name and the associated LU alias to the list of available invokable TPs (which may include associated LU aliases). For details about how this comparison is carried out, see the Microsoft SNA Server APPC Programmer's Guide or the Microsoft SNA Server CPI-C Programmer's Guide.

If a match is found, the SNA server signals the system containing the requested TP to connect to that SNA server.

If no match is found, the SNA server rejects the incoming request.

Invokable TPs and the SNA Server Configuration

In order for an SNA server to receive requests from an invoking TP on another system, and then route those requests to an invokable TP, certain parameters must be configured correctly:

The SNA server must have a connection to the system from which the invoking TP's request is sent.

The SNA server must have a remote LU capable of receiving the incoming request. This remote LU can be configured either explicitly or implicitly.

When configured explicitly, there is an explicit match between a remote LU alias on the SNA server and the alias of the LU that conveys the invoking TP's request.

When configured implicitly, an Implicit Incoming Remote LU (with its Implicit Incoming Mode) is used. This means that several items must work together. First, the LU alias specified in the incoming request (the LU alias requested for the invokable TP) must match a local LU alias on the SNA server receiving the request. Second, the local LU on the SNA server must have an Implicit Incoming Remote LU assigned to it. The properties of the Implicit Incoming Remote LU will be used for that LU-LU session. For more details about how an Implicit Incoming Remote LU works, see: "Implicit Incoming Remote LU and Implicit Incoming Mode" later in this chapter.

Appropriate local LUs must be defined in the SNA Server configuration. For descriptions of several ways to set up these local LUs, see the next section.

Possible Arrangements of TPs Within an SNA Network

If your SNA Server installation contains multiple systems (clients and/or SNA servers), you can place a given invokable TP on more than one system. When an invoking request is received in such an installation, there will (potentially) be a choice of systems on which to run the invokable TP. You can maintain specific control over this choice; alternatively, by following the instructions in "TP Name Not Unique; Local LU Alias Unspecified" (later in this chapter), you can allow the choice to be made randomly by SNA Server (to distribute the load).

You can maintain specific control over this choice of system by setting up invokable TPs with unique names, or by setting up each invokable TP to run only with a specific, unique LU alias. With this arrangement, the information provided by the invoking TP (in the ALLOCATE verb) can specify the particular system on which the TP should run.

You can avoid controlling this choice of system, and allow the choice to be made randomly by SNA Server, by setting the DloadMatchLocalFirst Registry entry to NO, as described in the Microsoft SNA Server Reference, and using invokable TPs that leave the local LU alias unspecified. Then, when an incoming request is received, it is routed randomly, rather than preferentially to the local SNA server; in addition, no matter what LU alias is requested for the invokable TP, there cannot be a mismatch. SNA Server will start the TP, choosing randomly among the available systems.

The following sections describe some of the possible arrangements that can be made for the running of TPs.

TP Name Unique for Each TP

If you want to specify the system where the invokable TP will run, one way to do it is to use a unique TP name for each invokable TP. In this arrangement, the invoking TP identifies the invokable TP (and system) simply by naming the TP. This makes it unnecessary for an invokable TP to specify any LU alias in Registry or environment variables.

TP Name Not Unique; Local LU Alias Unique

If you want to specify the system where the invokable TP will run, another way to do it (besides using unique TP names) is to give the same name to multiple invokable TPs, but associate each TP with a unique local LU alias. To do this, configure each invokable TP (through Registry or environment variables) to use a unique local LU alias. Then set up the invoking TPs so that each one is routed not only to the correct TP name but also to the correct partner LU alias for the intended invokable TP.

TP Name Not Unique; Local LU Alias Unspecified

If it does not matter which system an invokable TP runs on, use the same name for multiple invokable TPs, and in addition, do not specify an LU alias in the Registry or environment variables for the TPs. In such a situation, in the list of available invokable TP names on an SNA server, there are no associated LU aliases. Thus, a request received from an invoking TP cannot cause a mismatch on the LU alias, and will match according to the TP name.

In such a situation, if you set the DloadMatchLocalFirst Registry entry to NO, as described in the Microsoft SNA Server Reference, SNA Server randomly routes the request to one of the available TPs. This spreads the processing load out among multiple systems, and provides hot backup (so that you can take systems on- and offline without disrupting service).

Troubleshooting for Invokable TPs

If there are difficulties with starting an invokable TP, but SNA Server seems to be running smoothly otherwise, there may be a mismatch between the information for the invokable TP, the invoking TP, and/or LUs in the SNA Server configuration. That is, there may be a mismatch between the RECEIVE_ALLOCATE parameters, the TP_STARTED and/or ALLOCATE parameters, and/or LU aliases specified in SNA Server Admin. For details about TPs, including details about the list of invokable TPs maintained on an SNA server, as well as details about the invoking process, see: the Microsoft SNA Server APPC Programmer's Guide and the Microsoft SNA Server CPI-C Programmer's Guide.


Configuring LUs for APPC
Configuring LUs for APPC	5 of 21

Configuring LUs for APPC

Before configuring an APPC LU, configure the server and connection the LU will use, as described in: Chapter 3, "Configuring Servers and Connections."

For a list of the sections that provide detailed instructions for configuring LUs for APPC, see: "Section List for APPC" later in this chapter. For information about configuring LUs for 5250 emulation in the AS/400 environment, see: Chapter 7, "Configuring for 5250 Emulation in the AS/400 Environment."For information about VTAM, NCP, and CICS parameters for independent LUs, see: Chapter 5, "Working with Settings in VTAM and NCP."

APPC LUs 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: "Single-System APPC" later in this chapter.

For a list of powerful SNA Server features for use in APPC, see: "SNA Server Features That Simplify APPC Configuration" later in this chapter.

The following list outlines the basic steps for configuring LUs for TPs on two different systems, and tells where to find detailed information about each step:

1.	Assign the local APPC LU to a server. For more information, see: "Assigning a Local APPC LU to a Server" later in this chapter.

Note

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

2.	Specify identifiers for the local APPC LU:

For an independent LU, specify LU Alias, Network Name, and LU Name.

For a dependent LU, specify LU Alias, LU Number, and LU Name.

The LU Alias and LU Name can match each other, or differ from each other. Each of these labels identifies the LU to a particular set of software components, as described in: "Configuring Local APPC LU Properties" later in this chapter.

For more information about these parameters, see: "SNA Server Features that Simplify APPC Configuration" and "Configuring Local APPC LU Properties" later in this chapter.

3.	As needed, configure other parameters for the local APPC LU. For information about these parameters, see: "SNA Server Features That Simplify APPC Configuration" and "Configuring Local APPC LU Properties" later in this chapter.

4.	Assign the remote APPC LU to a connection. For more information, see: "Assigning a Remote APPC LU to a Connection" later in this chapter.

Note

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

5.	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. In addition, mark the Supports Parallel Sessions check box.

For a remote LU to be used with a dependent local LU, specify LU Alias, Network Name, LU Name, and Uninterpreted LU Name. In addition, make sure the Supports Parallel Sessions check box is cleared.

Consult with the administrator of the remote host or peer system regarding all these parameters. The LU Alias, LU Name, and (for dependent communication) the Uninterpreted LU Name can match each other or differ from each other. Each of these labels identifies the LU to a particular set of software components. For more information about these parameters and other parameters for remote LUs, see: "Configuring Remote APPC LU Properties" later in this chapter.

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

A mode is a collection of session properties used by LUs as they carry on an APPC session. A mode can be used by many LU pairs at the same time. For information about configuring modes, see: "Configuring Modes for LU-LU Pairs" later in this chapter.

If you use the automatic partnering feature, by configuring APPC LUs and then modes with automatic partnering enabled, a number of LU-LU pairs will be generated for you when you finish configuring the mode(s).

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

If you are using automatic partnering, you can view the pairing(s) of local LU, remote LU, and mode that have automatically been created.

If you are not using automatic partnering, pair the local LU with the remote LU, and assign a mode.

For information about automatic partnering, see: "Configuring Remote APPC LU Properties" later in this chapter. For information about pairing LUs, see: "Pairing Local and Remote LUs" later in this chapter.

8.	Optionally, configure session security for the remote LU. For more information, see: "Configuring Session Security for Remote LUs" later in this chapter.

9.	Optionally, assign a default local APPC LU and/or a default remote APPC LU to users and/or groups. For independent APPC of any kind, 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).

For more information, see: "Assigning Default APPC LUs to Users or Groups" later in this chapter.

10.	If you will be using CPI-C, configure one or more CPI-C symbolic destination names. For more information, see: "Configuring Properties for CPI-C" later in this chapter.

11.	If you will be using DISPLAY, an APPC verb, you may want to specify a default connection for the verb. For information about the DISPLAY verb and how it uses a default connection, see: the Microsoft SNA Server APPC Programmer's Guide.For information about configuring the default connection for the verb, see: "Configuring the Default DISPLAY Connection" later in this chapter.

12.	To ensure that all changes take effect, restart the SNA server, as described in: Chapter 11, "Managing SNA Server."

If the only change is the addition of new APPC LUs and their pairings, the server does not have to be restarted.


SNA Server Features That Simplify APPC Configuration
Configuring LUs for APPC	6 of 21

Configuring LUs for APPC

SNA Server Features That Simplify APPC Configuration

There are several features in SNA Server that can simplify configuration for APPC:

The Implicit Incoming Remote LU and the Implicit Incoming Mode, which allow SNA Server to accept requests that arrive by unrecognized remote LUs and modes.

The Default Local APPC LU and the Default Remote APPC LU, which allow LU aliases to be associated with user or group names, simplifying the routing of incoming requests and the configuration of client systems.

The Default Outgoing Local APPC LU Pool, which allows LUs to be allocated dynamically to any invoking TP that does not specify a local LU.

Automatic Partnering, which automatically creates LU-LU pairs and assigns modes to the pairs.

The following sections describe these features.

Implicit Incoming Remote LU and Implicit Incoming Mode

In your SNA Server installation, you may want to accept incoming requests that arrive by many different remote LUs, without having to explicitly define each remote LU on an SNA server. The Implicit Incoming Remote LU and Implicit Incoming Mode allow for such flexible acceptance of requests. When these two items have been configured, and an incoming request is received by SNA Server, the remote LU need not be recognized, as long as the local LU specified in the request is recognized. In such a situation, the SNA server uses the properties of the Implicit Incoming Remote LU and Implicit Incoming Mode for that LU-LU session.

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

1.	Configure a remote LU that is appropriate for incoming requests that specify an unrecognized remote LU. For information about configuring remote LUs, see: "Assigning a Remote APPC LU to a Connection" and "Configuring Remote APPC LU Properties" later in this chapter.

2.	Configure one or more local LUs that are appropriate for incoming requests that specify an unrecognized remote LU. For information about configuring a local LU, see: "Assigning a Local APPC LU to a Server" and "Configuring Local APPC LU Properties" later in this chapter.

All incoming requests must specify a local LU name that is recognized by SNA Server. This is true even with the use of an Implicit Incoming Remote LU and Implicit Incoming Mode.

3.	Assign the remote LU (configured in step 1) as the Implicit Incoming Remote LU for the local LU(s) (configured in step 2). For information about assigning an Implicit Incoming Remote LU to a local LU, see: "Configuring Local APPC LU Properties" later in this chapter.

4.	Configure a mode that is appropriate for incoming requests that specify an unrecognized remote LU. For information about configuring modes, see: "Configuring Modes for LU-LU Pairs" later in this chapter.

5.	Assign the mode (configured in step 4) as the Implicit Incoming Mode for the remote LU (configured in step 1). For information about assigning an Implicit Incoming Mode to a remote LU, see: "Configuring Remote APPC LU Properties" later in this chapter.

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.

Default Local APPC LU and the Default Remote APPC LU

With SNA Server, you can assign a Default Local APPC LU and a Default Remote APPC LU to each user or group. A user or group member can then start APPC programs (TPs, 5250 emulators, or APPC applications) that do not specify LU aliases. In this situation, SNA Server will use the Default Local APPC LU and the Default Remote APPC LU assigned to that user or group. For information about a contrasting default APPC LU feature, see the next section.

For more details about the information needed to start TPs, see: "Invoking and Invokable TPs" earlier in this chapter, the Microsoft SNA Server APPC Programmer's Guide, or the Microsoft SNA Server CPI-C Programmer's Guide.

For more information about the Default Local APPC LU and the Default Remote APPC LU, see: "Assigning Default APPC LUs to Users or Groups" later in this chapter.

Default Outgoing Local APPC LU Pool

With SNA Server, you can set up a pool of local APPC LUs that will be allocated dynamically for any invoking TP that does not specify a local LU. This feature is designed to coexist with the Default Local and Remote LUs for users and groups, and does not override these settings.

Both of the default APPC LU features  the Default Pool and the Default Local and Remote LUs for users and groups  allow clients to start a session without specifying an LU name. This helps to simplify administration by eliminating APPC configuration for clients, for example, for 5250 emulators.

If an application (for example, an application on a client) begins the invoking process but does not specify a Local APPC LU, SNA Server first tries to determine the Default Local APPC LU of the associated user or group (that is, the user or group logged on at the system where the application is running). If no such LU can be substituted, then SNA Server attempts to assign an LU from the Default Pool of Outgoing Local APPC LUs. If no LUs are available from the Default Pool, the attempt to begin the invoking process is rejected.

Automatic Partnering

With the automatic partnering feature, SNA Server can automatically generate pairs of local and remote LUs (with associated modes). This is in contrast to the method where you specifically create each LU-LU pair (with an associated mode). If you want to have LU-LU pairs that reflect most or all combinations of local LU, remote LU, and mode in your configuration, use automatic partnering. To use automatic partnering, make sure the Enable Automatic Partnering check box is selected as you configure the LUs and modes.

If you want to have only the LU-LU pairs that you specifically create, as you configure LUs and modes, clear the Enable Automatic Partnering check box.

SNA Server checks for automatic partners every time a new 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 LU-LU pairs as possible, each pair containing a remote LU, local LU, and 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.


Single-System APPC
Configuring LUs for APPC	7 of 21

Configuring LUs for APPC

Single-System APPC

Single-system APPC is generally used for testing TPs. For detailed instructions for configuring LUs for APPC, see the sections referenced in: "Section List for APPC" later in this chapter. The following list outlines the basic steps for single-system APPC:

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.

The LU Alias and LU Name can match each other, or differ from each other. Each of these labels identifies an LU to a particular set of software components.

3.	If an appropriate mode has not already been configured, configure it. A mode is a collection of session properties used by LUs as they carry on an APPC session. A mode can be used by many LU pairs at the same time.

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. For more information, see: "Configuring Properties for CPI-C" later in this chapter.


Section List for APPC
Configuring LUs for APPC	8 of 21

Section List for APPC

The following sections give details about configuring LUs for APPC. The sections are listed in the order that they appear.

Assigning a Local APPC LU to a Server

Viewing or Modifying a Local or Remote APPC LU

Configuring Local APPC LU Properties

Assigning a Remote APPC LU to a Connection

Configuring Remote APPC LU Properties

Configuring Modes for LU-LU Pairs

Pairing Local and Remote LUs

Configuring Session Security for Remote LUs

The following sections give details about configuring for CPI-C and configuring a default connection for DISPLAY, an APPC verb.

Configuring Properties for CPI-C

Configuring the Default DISPLAY Connection


Assigning a Local APPC LU to a Server
Configuring LUs for APPC	9 of 21

Section List for APPC

Assigning a Local APPC LU to a Server

Local and remote APPC LUs work together in pairs. The local APPC LU is assigned to a server (unlike other LUs, which are assigned to connections). For an overview of APPC LUs, see: "How LUs Work Together for APPC" earlier in this chapter.

To assign a local APPC LU

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

Note

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

2.	From the Services menu, choose Assign LUs.

The Insert LU dialog box appears.

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

4.	Choose the OK button.

To configure the LU, see: "Configuring Local APPC LU Properties" later in this chapter.


Viewing or Modifying a Local or Remote APPC LU
Configuring LUs for APPC	10 of 21

Section List for APPC

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.	From the Services menu, choose Properties.

To configure the LU, see the next section.


Configuring Local APPC LU Properties
Configuring LUs for APPC	11 of 21

Section List for APPC

Configuring Local APPC LU Properties

Local APPC LUs can be independent or dependent. For more information, see: "How LUs Work Together for APPC" earlier in this chapter.

For information about assigning or accessing a local APPC LU, see the preceding procedures. When you assign or access a local APPC LU, the New APPC LU Properties dialog box or the APPC LU Properties dialog box appears. The APPC LU Properties dialog box is shown in Figure 6.5.

Figure 6.5    APPC LU Properties Dialog Box

In the APPC LU Properties dialog box, supply information as follows:

Parameters for Both Independent and Dependent LUs

LU 6.2 Type

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

LU Alias

Type a name that identifies the 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 LU, the LU Alias must be unique on the server.

The LU Alias and LU Name for the LU can match each other, or differ.

Network Name

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

Obtain the correct name from the host or peer administrator. For communication with a host, the network name should match the NETID parameter in the VTAM Start command for the VTAM system. If this server communicates with several different hosts over several connections, type the name of the subarea of the host with which this LU will communicate.

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.

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

Type 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. For a local LU, the fully qualified LU Name (Network Name plus LU Name) must be unique on the 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 the LU can match each other, or differ.

Comment

Optionally, type a comment of up to 25 characters.

Enable Automatic Partnering

To designate the LU as a local automatic partner  a local LU that is partnered with every remote LU and mode also designated as an automatic partner  use the default setting of 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 the Enable Automatic Partnering check box.

SNA Server checks for automatic partners every time a new 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 LU-LU pairs as possible, each pair containing a remote LU, local LU, and 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.

Member of Default Outgoing Local APPC LU Pool

If you want this LU to be available for use by an invoking TP that does not specify a local LU, select this check box.

When a request comes from such a TP, 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.

This default pool differs from, and should not be confused with, the 3270, LUA, and downstream pools described in Chapter 10.

Implicit Incoming Remote LU

To specify an implicit incoming remote LU, choose an existing remote LU name from the list. An implicit incoming remote LU is 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.

For information about the Implicit Incoming Remote LU and the Implicit Incoming Mode (required with the implicit LU), see "Implicit Incoming Remote LU and Implicit Incoming Mode" earlier in this chapter, and "Configuring Remote APPC LU Properties" later in this chapter.

Timeout for Starting Invokable TPs

Specify 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. If the invokable TP is started manually by an operator, specify a value greater than 60 seconds to give the operator sufficient time.

The range is from 1 through 3600 seconds; the default is 60 seconds.

Parameter for Dependent LUs

LU Number

For dependent LUs, type the number identifying the 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 APPC 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.

For independent LUs, this field is unavailable.

The usual range for LU number 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.

After Configuring Local APPC LU Properties

After configuring local APPC LU properties, in the New APPC LU Properties dialog box or the APPC LU Properties dialog box, shown in Figure 6.5, choose a button according to the following:

To accept the settings, choose the OK button.

If you have not already configured a remote APPC LU that will work with this local APPC LU, you can configure it after choosing the OK button. For information, see: "Assigning a Remote APPC LU to a Connection" and "Configuring Remote APPC LU Properties" later in this chapter.

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

To pair this LU with a remote APPC LU that you have already configured,  choose the Partners button. See: "Pairing Local and Remote LUs" later in this chapter. If you have not configured a mode for the LU-LU pair to use, see also: "Configuring Modes for LU-LU Pairs" later in this chapter.


Assigning a Remote APPC LU to a Connection
Configuring LUs for APPC	12 of 21

Section List for APPC

Assigning a Remote APPC LU to a Connection

Local and remote APPC LUs work together in pairs. The remote APPC LU is assigned to a connection. For an overview of APPC LUs, see: "How LUs Work Together for APPC" earlier in this chapter.

Remote APPC LUs can be assigned to connections that have a Remote End of Host, or a Remote End of Peer. 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.

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.

2.	From the Services menu, choose Assign LUs.

The Insert LU dialog box appears.

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

4.	Choose the OK button.

To configure the LU, see the next section. For information about how to view or modify an existing remote APPC LU, see: "Viewing or Modifying a Local or Remote APPC LU" earlier in this chapter.


Configuring Remote APPC LU Properties
Configuring LUs for APPC	13 of 21

Section List for APPC

Configuring Remote APPC LU Properties

For information about assigning or viewing a remote APPC LU, see the preceding section, or: "Viewing or Modifying a Local or Remote APPC LU" earlier in this chapter. When you assign or view a local APPC LU, the New APPC Remote LU Properties dialog box or the APPC Remote LU Properties dialog box appears. The APPC Remote LU Properties dialog box is shown in Figure 6.6.

Figure 6.6    APPC Remote LU Properties Dialog Box

Find the items appropriate to your configuration, and supply information as follows:

LU Alias

Type a name that identifies the 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 remote LU, the LU Alias must be unique on the connection, and must not match that of a local LU on that server.

The LU Alias and LU Name for the LU can match each other, or differ.

Network Name

Type a name identifying the SNA network for the remote LU. The name can be from one through eight characters long, and can include alphanumeric characters and the special characters $, #, and @. The name cannot be the same as the network name for any partner LU for this LU.

Obtain the correct name from the host or peer administrator. For communication with a host, the network name should match the NETID parameter in the VTAM Start command for the VTAM system.

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

Type 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. For a remote LU, the fully qualified LU Name (Network Name plus LU Name) must be unique on the connection, and must not match that of a local LU on that server.

For a remote LU that will be partnered with an independent local APPC LU, the LU Name identifies the remote LU to other components on the SNA network, and therefore is required. For a remote LU that will be partnered with a dependent local APPC 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 the LU can match each other, or differ.

Uninterpreted LU Name

If this LU will be paired with a dependent local APPC LU, type the name of the remote LU as defined on the remote SSCP. This name is required when using 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 Name, and LU Alias for the LU can match each other, or differ.

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 (multiple concurrent sessions between a pair of APPC LUs) will be used, select this check box. If this LU will be used with a dependent local APPC LU, do not select this check 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  a remote LU that is partnered with every local LU and mode also designated as an automatic partner  use the default setting of 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 the Enable Automatic Partnering check box.

SNA Server checks for automatic partners every time a new 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 LULU pairs as possible, each pair containing a remote LU, local LU, and 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.

Automatic partnering should not be used with remote LUs having the same fully qualified name (Network Name plus LU Name) and/or the same LU Alias on the same server. These LUs cannot be partnered with the same local LU and mode. Instead, for each LU-LU pair, the set of LU aliases and fully qualified LU names combined with a particular mode name must be unique. 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.

Implicit Incoming Mode

To designate a mode as the implicit incoming mode for this LU, select a mode name from the list. An implicit incoming mode is 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.

If this remote LU will be used as an implicit incoming remote LU for a local APPC LU, select a mode from the list. An implicit incoming remote LU requires an implicit incoming mode.

To create a new mode to use as the implicit mode, choose the Partners button, then the Modes button, and see: "Configuring Modes for LU-LU Pairs" later in this chapter.

For more information about the implicit LU and mode, see: "Implicit Incoming Remote LU and Implicit Incoming Mode" and "Configuring Local APPC LU Properties" earlier in this chapter.

After Configuring Remote APPC LU Properties

After configuring remote APPC LU properties, in the New APPC Remote LU Properties dialog box or the APPC Remote LU Properties dialog box, shown in Figure 6.6, choose a button according to the following:

To accept the settings, choose the OK button.

If you have not already configured a local APPC LU that will work with this remote APPC LU, you can configure it after choosing the OK button. For information, see: "Assigning a Local APPC LU to a Server" and "Configuring Local APPC LU Properties" earlier in this chapter.

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

To pair this LU with a local APPC LU that you have already configured,  choose the Partners button. See: "Pairing Local and Remote LUs" later in this chapter. If you have not configured a mode for the LU-LU pair to use, see also the following section.


Configuring Modes for LU-LU Pairs
Configuring LUs for APPC	14 of 21

Section List for APPC

Configuring Modes for LU-LU Pairs

A mode is associated with an LU-LU pair, and determines session properties for that pair. 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. For more information, see: "Configuring Local APPC LU Properties" and "Configuring Remote APPC LU Properties" earlier in this chapter.

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.

A number of standard modes are provided with SNA Server. For more information, see the next section.

If the mode you need has already been created, and you want to assign the mode to an LU-LU pair, see: "Pairing Local and Remote LUs" later in this chapter.

Properties of Standard Modes

The modes provided with SNA Server are listed in the following table. For information about assigning a mode to an LU-LU pair, see: "Pairing Local and Remote LUs" later in this chapter.

Mode name	To be used for

#BATCH	Batch-oriented sessions

#BATCHSC	Batch-oriented sessions that employ a minimal level of routing security

BLANK	Sessions using a default mode name, encoded as eight blank EBCDIC spaces in BIND

#INTER	Interactive sessions

#INTERSC	Interactive sessions that employ a minimal level of routing security

QPCSUPP	All sessions with an AS/400 computer

The configuration parameters of the modes provided with SNA Server are shown in the following table.

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

For information about configuring the local and remote APPC LUs that you will pair together and assign a mode to, see the sections that precede this one:

Assigning a Local APPC LU to a Server

Viewing or Modifying a Local or Remote APPC LU

Configuring Local APPC LU Properties

Assigning a Remote APPC LU to a Connection

Configuring Remote APPC LU Properties

After configuring local and remote APPC LUs, you can configure a mode for the LUs to use.

To begin configuring a mode

1.	In the Servers and Connections window, select either the local or the remote APPC LU with which the mode will be associated.

The mode will be associated with a local APPC LU and a remote APPC LU in an LU-LU pair.

2.	From the Services menu, choose Properties.

Depending on the LU that you chose in step 1, either the APPC LU Properties dialog box, shown in Figure 6.5, or the APPC Remote LU Properties dialog box, shown in Figure 6.6, appears.

3.	From the Properties dialog box for the LU, choose the Partners button.

The LU 6.2 Partner LUs dialog box appears, as shown in Figure 6.8 later in this chapter.

4.	In the LU 6.2 Partner LUs dialog box, choose the Modes button.

The APPC Mode Properties dialog box, shown in the next section, appears.

The APPC Mode Properties Dialog Box

For information about accessing the APPC Mode Properties dialog box, see the previous section. The APPC Mode Properties dialog box is shown in Figure 6.7.

Figure 6.7    APPC Mode Properties Dialog Box

In the APPC Mode Properties dialog box, you can configure a new mode, or delete or modify an existing one.

To add a mode to the list in the APPC Mode Properties dialog box

For information about accessing the APPC Mode Properties dialog box, shown in Figure 6.7, see the preceding section.

1.	In the Mode Name box, type a name identifying the 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 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 these procedures.

3.	Choose the Add button.

4.	Choose the Close button.

To delete a mode in the APPC Mode Properties dialog box

For information about accessing the APPC Mode Properties dialog box, see the preceding section.

1.	From the Mode Name list box, select a mode name.

2.	Choose the Delete button.

3.	Choose the Close button.

To modify an existing mode in the APPC Mode Properties dialog box

For information about accessing the APPC Mode Properties dialog box, see the preceding section.

1.	From the Mode Name list box, select a mode name.

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

3.	Choose the Change button.

4.	Choose the Close button.

Mode Properties

For information about accessing the APPC Mode Properties dialog box, and an illustration of the dialog box, see the preceding section. For background information about the parallel session limit and other mode properties, see: "Configuring Modes for LU-LU Pairs" earlier in this chapter.

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

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. Parallel sessions are multiple concurrent sessions between a pair of APPC LUs, allowing two TPs to perform multiple operations simultaneously. For more information about the parallel session limit, see: "Configuring Modes for LU-LU Pairs" earlier in this chapter.

If the local APPC LU to be used with this mode is dependent, specify 1; dependent local APPC LUs cannot have parallel sessions.

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

Minimum Contention Winner Limit

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

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.

The range is from 0 through the Parallel Session Limit; the default is 0.

Partner Min Contention Winner Limit

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

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.

The range is from 0 through the Parallel Session Limit; the default is 0.

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 contention winner session, the LU can initiate conversations without permission from the partner LU.

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

The range is from 0 through the Minimum Contention Winner Limit.

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 the Enable Automatic Partnering check box.

SNA Server checks for automatic partners every time a new 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 LULU pairs as possible, each pair containing a remote LU, local LU, and 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.

High Priority Mode

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

By default, this check box is selected.

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.

The range is from 0 through 63; the default is 4.

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.

The range is from 0 through 63; the default is 4.

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

The range for Max Send RU Size is from 256 through 16384; the default is 1024.

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

The range for Max Receive RU Size is from 256 through 16384; the default is 1024.

After Configuring Modes

When you close the APPC Mode Properties dialog box, the LU 6.2 Partner LUs dialog box reappears. For information and an illustration, see the next section.


Pairing Local and Remote LUs
Configuring LUs for APPC	15 of 21

Section List for APPC

Pairing Local and Remote LUs

For information about configuring the local and remote APPC LUs that you will pair together, see the following sections, found earlier in this chapter:

Assigning a Local APPC LU to a Server

Viewing or Modifying a Local or Remote APPC LU

Configuring Local APPC LU Properties

Assigning a Remote APPC LU to a Connection

Configuring Remote APPC LU Properties

For information about configuring a new mode to assign to the LU-LU pair, see: "Configuring Modes for LU-LU Pairs" earlier in this chapter.

To add or delete an LU-LU pair

1.	In the Servers and Connections window, select either the local or the remote APPC LU for the pair.

2.	From the Services menu, choose Properties.

The Properties dialog box for the selected LU appears, as shown in either Figure 6.5 (APPC LU Properties dialog box) or Figure 6.6 (APPC Remote LU Properties dialog box).

3.	From the Properties dialog box for the selected LU, choose the Partners button.

The LU 6.2 Partner LUs dialog box, shown in Figure 6.8, appears.

Figure 6.8    LU 6.2 Partner LUs 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.

4.	If the mode you need does not already exist, choose the Modes button, and see "Configuring Modes for LU-LU Pairs" earlier in this chapter.

5.	In the LU 6.2 Partner LUs dialog box, shown in Figure 6.8, select buttons as appropriate:

Add

To add a partner to the list for this LU, choose the Add button. Then, in the Add APPC LU Partner dialog box, select the partner LU and mode for the LU-LU pair, and choose the OK button.

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.

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 APPC LU to a Server" or "Assigning a Remote APPC LU to a Connection" earlier in this chapter.

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: "Configuring Modes for LU-LU Pairs" earlier in this chapter.

Delete

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

Modes

SNA Server keeps a list of modes available for LU-LU pairs. To change the list by adding, deleting, or configuring modes, choose the Modes button. 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: "Configuring Modes for LU-LU Pairs" earlier in this chapter.

Note

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

6.	Choose the Close button.


Configuring Session Security for Remote LUs
Configuring LUs for APPC	16 of 21

Section List for APPC

Configuring Session Security for Remote LUs

After configuring a remote LU, you can optionally configure APPC security for it.

To configure session security for a remote LU

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

2.	From the Services menu, choose Properties.

The APPC Remote LU Properties dialog box, shown in Figure 6.6, appears.

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

The APPC Session Security dialog box appears.

4.	Find the item(s) appropriate to your configuration, and supply information as follows:

No Session-Level Security

Select this option button to turn off session-level security. Session-level security 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.

By default, this option button is selected.

Security Key in Hex

If you want the security key to be in hexadecimal, select Security Key in Hex, then type a 16-digit hexadecimal number.

Security Key in Characters

If you want the security key to be in characters, select Security Key in Characters, then type an eight-character string. The string can include uppercase and lowercase alphanumeric characters, and the special characters $, @, #, and the period (.).

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


Configuring Properties for CPI-C
Configuring LUs for APPC	17 of 21

Section List for APPC

Configuring Properties for CPI-C

CPI-C is a set of Clanguage 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.

If you are using applications based on CPI-C, you will need to configure one or more CPI-C symbolic destination names. A CPI-C symbolic destination name is a name assigned to a set of properties for a CPI-C conversation.

To configure CPI-C symbolic destination names

1.	In the Servers and Connections window, from the Options menu, choose CPIC.

The Configure CPI-C Names dialog box appears.

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

3.	Select the appropriate button:

Add (for adding a symbolic destination name).

Delete (for deleting the selected symbolic destination name). If you choose this button, skip to step 5.

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

If you choose the Add or Edit button, the dialog box shown in Figure 6.9 appears

Figure 6.9    CPI-C Symbolic Destination Name Properties Dialog Box

4.	Find the item(s) appropriate to your configuration, and supply information as follows:

Name

Type the symbolic destination name. The name can be from 1 through eight characters long, and can contain alphanumeric characters and the special characters $, #, and @.

Comment

Optionally, type a comment of up to 25 characters.

Partner TP Name

Application TP: For an application program that uses APPC to exchange data with another TP on a peer-to-peer basis, select this option button. Then type the Application TP name. 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.

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

SNA Service TP (in hex): For a TP that uses APPC to perform services related to SNA functionality, select this option. Then type a hexadecimal number identifying the SNA Service TP. The number can be from one through eight hexadecimal digits long.

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

Partner LU Name

Alias: To identify the partner LU by its LU alias, select this option, and type the alias. The alias can be from one through eight characters long, and can contain alphanumeric characters and the special characters %, $, #, and @. Lowercase letters are converted to uppercase.

Fully Qualified: To identify the partner LU by a fully qualified name, which is a two-part name that identifies the remote LU, select this option, and type the name. The first part of the fully qualified name is the network name; the second part is the remote LU name. 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.

Mode Name

Type a mode name, or select one from the list. For information about modes, see: "Configuring Modes for LU-LU Pairs" earlier in this chapter.

Conversation Security

Conversation-level security is 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 server where the remote TP resides. If the ID and password do not match, the session is not activated.

Select a conversation-level 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 the User ID button. For information, see: "Specifying a User ID and Password."

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

Specifying a User ID and Password

For information about accessing the CPI-C Symbolic Destination Name Properties dialog box, shown in Figure 6.9, see the preceding section.

When you choose the User ID button in the CPI-C Symbolic Destination Name Properties dialog box, the CPI-C Security Settings dialog box appears:

To specify a user ID and password in the CPI-C Security Settings dialog box

1.	In the User ID box, type the User ID, which can contain from 1 through 10 characters.

2.	In the Password box, type the password, which can contain from 1 through 10 characters.

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

4.	Choose the OK button.


Configuring the Default DISPLAY Connection
Configuring LUs for APPC	18 of 21

Section List for APPC

Configuring the Default DISPLAY Connection

The DISPLAY verb is an APPC verb that returns configuration information and current operating values for an SNA server. 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.

For information about the DISPLAY verb and how it uses a default connection, see: the Microsoft SNA Server APPC Programmer's Guide.

To configure the default DISPLAY connection

1.	In the Servers and Connections window, from the Options menu, choose Display Verb.

The Display Verb Options dialog box appears.

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

3.	Choose the OK button.


Copying Properties Between LUs
Configuring LUs for APPC	19 of 21

Copying Properties Between LUs

You can copy properties from one local APPC LU to another, or from one remote APPC LU to another. For APPC LUs, copied properties include partnerships.

To copy properties between LUs

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

2.	From the Services menu, choose Copy Properties.

The Copy Properties dialog box appears.

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

If you copy properties to an active LU, the properties take effect when the LU is reset. For information about resetting an LU, see: Chapter 11, "Managing SNA Server."

4.	Choose the OK button.


Moving an LU to a Different Connection or Server
Configuring LUs for APPC	20 of 21

Moving an LU to a Different Connection or Server

You can move a remote APPC LU to a different connection, and a local APPC LU to a different server.

To move an APPC LU

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

2.	From the Services menu, choose Move LU.

The Move dialog box appears.

3.	Specify a destination:

For a remote LU, type the name of the connection to which you want to move the LU, or select the connection from the list.

For a local LU, type the name of the server to which you want to move the LU, or select the server from the list.

4.	Choose the OK button.


Assigning Default APPC LUs to Users or Groups
Configuring LUs for APPC	21 of 21

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.

For information about configuring for the AS/400 environment, see: Chapter 7, "Configuring for 5250 Emulation in the AS/400 Environment."

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

1.	In the Users and Groups window, select any line.

2.	From the View menu, choose Configured Users.

3.	From the Users menu, choose New User.

The Add Users and Groups dialog box appears:

4.	In the List Names From box, select the domain from which to list users or groups who have network accounts, or select the name of the local server.

5.	In the Names box, from the list of users and groups who have accounts, select the one you want to add.

6.	Choose the Add button.

7.	Choose the OK button.

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.	From the File menu, choose Save Configuration.

If a user is assigned LUs through one or more accounts, such as group accounts and the user's individual account, the LUs do not accumulate. Instead, one account determines the access for that user. The account that determines this access is the account found first when searching is carried out in this order:

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.

To assign default local and remote 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.

You can distinguish the type of user account by the appearance of the icon next to the user or group name.

3.	From the Users menu, choose Properties.

The User Properties or Group Properties dialog box appears. The following illustration shows the User Properties dialog box:

4.	In the Default Local APPC LU box, select a local APPC LU.

The default local APPC LU will be accessed if the user starts a TP, 5250 emulator, or APPC application that does not specify a local APPC LU alias.

5.	In the Default Remote APPC LU box, select a remote APPC LU.

The default remote APPC LU will be accessed if the user starts a TP, 5250 emulator, or APPC application that does not specify a remote APPC LU alias.

6.	Choose the OK button.

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.	From the File menu, choose Save Configuration.


Configuring for 5250 Emulation in the AS/400 Environment
Chapter 7	1 of 7

Configuring for 5250 Emulation in the AS/400 Environment

This chapter provides information about configuring SNA Server to support 5250 emulation with an AS/400. The chapter includes

Steps for configuring SNA Server for 5250 emulation in the AS/400 environment.

A table that relates SNA Server parameters to AS/400 parameters.

Brief guidelines for configuring parameters on an AS/400.

For 5250 emulation in the AS/400 environment, you must configure the following elements:

SNA servers

Connections

Local APPC LUs

Remote APPC LUs

LU-LU pairs

For background information about configuring all these elements, see: Chapter 6, "Configuring LUs for APPC," or the SNA Server Admin Help.


Configuration Steps for the AS/400 Environment
	Configuring for 5250 Emulation in the AS/400 Environment	2 of 7
Configuration Steps for the AS/400 Environment

This section lists steps for configuring SNA Server for 5250 emulation in the AS/400 environment. The next two sections provide supplementary information about making LUs available to 5250 users and about hot backup.

Note

For additional details about the SNA Server configuration steps in the following procedure, see: Chapter 6, "Configuring LUs for APPC," or the SNA Server Admin Help.

To configure SNA Server for 5250 emulation in the AS/400 environment

1.	Find out the following from the administrator of the AS/400:

The RMTNETID (the network name) configured on the AS/400.

The EXCHID (node ID), which identifies a remote system that will connect to the AS/400.

The control point name (CP name) of the AS/400. This is shown in the "Display network attributes" screen (accessed through a menu or through the DSPNETA command) on the AS/400.

The address for connecting to the AS/400. The name of this parameter varies according to the connection type. One example is the local 802.2 adapter address for the Line Description on an AS/400, called ADPTADR. Another example is the SDLC Poll Address on the Line Description, called STNADR. With SDLC, you will also need the phone number of the AS/400.

The switched disconnect (SWTDSC) setting on the AS/400 (*YES or *NO).

For AS/400s on X.25 or SDLC lines, the NRZI (non-return to zero inverted) setting.

Whether autocreate controller (AUTOCRTCTL) is turned on in the Line Description (the DSPLIND command displays the Line Description).

2.	Plan the names of the local APPC LUs that you will use, coordinating your plans with the administrator of the AS/400.

Important

The appropriate choice of local LU name on an SNA Server depends on the AUTOCRTCTL (autocreate controller) setting on the AS/400. If the adminstrator of the AS/400 enables automatic creation of a controller (with AUTOCRTCTL *YES in the Line Description), it does not matter what name you use for the local LU. Alternatively, if the administrator disables automatic creation (with AUTOCRTCTL  *NO in the Line Description of the AS/400), you must coordinate your local LU names with the administrator. If automatic creation of the controller is disabled, when you specify the local LU name, use the Remote Control Point Name (RMTCPNAME) on the Controller Description of the AS/400.

Each LU is assigned both an LU alias and an LU name. These names can differ but generally are the same for a given LU. The LU alias identifies the LU to local emulators; the LU name identifies the LU to the AS/400.

For a local APPC LU, the fully qualified LU Name (Network Name plus LU Name) must be unique on the server. The LU Alias must be unique on the server.

For a discussion of ways of naming and using local LUs, see: "Strategies for Assigning LU Names and Aliases" and "Configuring Hot Backup for LUs for 5250" later in this chapter.

3.	Start SNA Server Admin.

4.	In the Servers and Connections window, for the SNA server that will connect to the AS/400, configure the local Network Name. (Access the Server Properties dialog box by double-clicking on the server name.)

Generally, the local Network Name should be the same network name as the RMTNETID setting on the AS/400. APPN is often used.

5.	For the same server as in the previous step, configure the local Control Point Name.

Commonly, the computer name of the server is used for the Control Point Name. Be sure to communicate the name to the administrator of the AS/400. On the AS/400, the corresponding setting is RMTCPNAME in the Controller Description.

Note

The local Network Name and Control Point Name, which are configured on the server, should not be confused with the remote Network Name and Control Point Name, which are configured on the connection.

6.	Assign a local APPC LU on the server. To do this, select the server and, from the Services menu, choose Assign LUs; in the resulting dialog box, choose OK.

Note

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

The New APPC LU Properties dialog box appears.

7.	For the LU Alias and LU Name of the local APPC LU, specify the name(s) chosen in step 2. For important information about these parameters, see step 2.

8.	For the Network Name of the local APPC LU, specify the same Network Name assigned to the server (step 4).

9.	Optionally, enable automatic partnering for the local APPC LU.

SNA Server checks for automatic partners every time a new 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 LULU pairs as possible, each pair containing a remote LU, a local LU, and a mode.

10.	Select the server configured in steps 4 and 5, and add the connection that will be used by the AS/400. To do this, from the Services menu, choose Add Connection; in the resulting dialog box, choose the connection type, and then choose OK.

The Connection Properties dialog box appears.

11.	In the Connection Properties dialog box, configure the following:

For Connection Name, choose any appropriate name.

For Link Service, select an appropriate link service. If an appropriate link service is not listed, use Setup to install the link service before returning to this configuration step.

For Remote End, select Peer System.

For Activation, select a setting that correlates with the switched disconnect (SWTDSC) setting on the AS/400. If SWTDSC is *YES, select On Demand. If SWTDSC is *NO, select On Server Startup.

If SWTDSC is *YES, the AS/400 disconnects when there are no active users (no demand), and the SNA server should allow the disconnection (be On Demand). If SWTDSC is *NO, the AS/400 does not disconnect except for problems, and therefore the SNA server should attempt to reconnect (have activation On Server Startup).

For Allowed Directions, be sure that Outgoing Calls is selected.

12.	In the Connection Properties dialog box, choose Setup.

13.	Configure connection settings:

For the address, specify the appropriate value. With 802.2, specify the network address of the AS/400; with X.25, the X.25 address; with SDLC, the poll address (an Advanced setting, which defaults to C1).

If you are using a modem that can accept a dial string from SNA Server, you will also need to specify the Dial Data for the SDLC connection.

For the Local Node ID, specify the EXCHID value configured on the AS/400.

For the remote Network Name, specify the RMTNETID configured on the AS/400. This is often APPN, the default.

For the remote Control Point Name, specify the control point name (CP name) of the AS/400.

For any Advanced parameters for which your system differs from the default, specify the appropriate values. The XID Type must be left at the default, Format 3.

For SDLC and X.25 connections, make sure that the NRZ or NRZI setting in the SNA Server dialog box (Advanced settings) matches the corresponding setting on the AS/400.

14.	Assign the remote APPC LU to the connection created in the previous steps. To do this, select the connection and, from the Services menu, choose Assign LUs; in the resulting dialog box, choose APPC [Remote], and choose OK.

Note

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

The New APPC Remote LU Properties dialog box appears.

15.	For the LU Alias of the remote APPC LU, specify the control point name of the AS/400, or another name that you have chosen.

With 5250, the remote LU Alias generally matches the remote LU Name, which must match the control point name of the AS/400.

The remote LU Alias must be unique on the connection, and must not match that of a local LU on that server.

16.	For the Network Name of the remote APPC LU, specify the RMTNETID used on the AS/400 (APPN is often used).

17.	For the LU Name of the remote APPC LU, specify the control point name (CP name) of the AS/400.

Note that because communication with an AS/400 is independent APPC, the Uninterpreted LU Name is ignored.

The fully qualified LU Name (Network Name plus LU Name) of a remote LU must be unique on the connection, and must not match that of a local LU on that server.

18.	Make sure the Supports Parallel Sessions check box is selected.

19.	Optionally, enable automatic partnering for the remote APPC LU.

20.	For each AS/400 you want to connect to, create a connection and an associated remote LU (steps 10 through 19).

21.	View or create LU-LU pairs, depending on whether you are using automatic partnering. First, access the LU 6.2 Partner LUs dialog box by double-clicking on an LU and (in the resulting dialog box) choosing the Partners button. Then carry out one of the following:

If you are using automatic partnering, you can view the pairings of local LUs, remote LUs, and modes that have automatically been created. If you see any pairs that do not use the QPCSUPP mode, delete those pairs. 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(s), and assign the QPCSUPP mode.

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. That is, for each LU-LU pair, the set of LU aliases and fully qualified LU names combined with a particular mode name must be unique.

22.	To make configuration of client computers simpler, add 5250 users and groups to the list recognized by SNA Server, and then assign a default local APPC LU and/or a default remote APPC LU to each 5250 user or group. To do this:

1.	In the Users and Groups window, from the Users menu, choose New User.

2.	In the Add Users and Groups dialog box, in the list under Names, select the intended user or group.

3.	Choose the Add button, and then choose OK.

4.	Double-click on the name of the user or group who has just been added.

5.	In the resulting dialog box, choose the intended default APPC LUs, and then choose OK.

You can assign the same set of default LUs to more than one user or group (instead of a different set of LUs for each user or group).

If no LUs are specified by a user trying to open a session, and default LUs have been configured for that user, the default LUs are used (if they are available).

For information about other ways of making APPC LUs available for sessions with an AS/400, see the next section.

23.	Save the configuration.

24.	To ensure that all changes take effect, restart the SNA server.

If the only changes are the addition of new APPC LUs and their pairings, or the assigning of default LUs to users or groups, the server does not have to be restarted.


Strategies for Assigning LU Names and Aliases
	Configuring for 5250 Emulation in the AS/400 Environment	3 of 7
Configuration Steps for the AS/400 Environment

Strategies for Assigning LU Names and Aliases

Administrators use a variety of strategies for the placement and naming of LUs for 5250. Two possible strategies are described in the next two sections:

Specifying local LU aliases that match user names

Configuring for hot backup for LUs for 5250

Specifying Local LU Aliases That Match User Names

This method allows you to tell which 5250 users are connected to the AS/400, because the local LU aliases match user names. It also makes it easy to keep track of which local LU a particular user should use.

For each user, create a separate local LU, with an LU Alias that matches the person's user name. Then carry out the other steps in the preceding list, including creating or viewing LU-LU pairs, adding each user to the list recognized by SNA Server, and assigning each user the appropriate Default Local LU and Default Remote LU. (Alternatively, you can skip the assignment of default LUs, and tell the user the appropriate LU aliases, so that the user can type these when starting a session.)

Note that this method uses SNA server resources somewhat less efficiently than other methods because it involves creating multiple local LUs where only one is necessary.

Configuring Hot Backup for LUs for 5250

Hot backup means that when a particular resource (such as an SNA server) is not working, another similar resource can automatically fill in and support the needed sessions. 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 make these resources interchangeable, so that one resource can automatically handle sessions if another can't, use the following procedure:

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 and LU Name, specify the same string on each server.

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.


Table of Parameters for AS/400 Communication
	Configuring for 5250 Emulation in the AS/400 Environment	4 of 7
Table of Parameters for AS/400 Communication

The following table summarizes details about configuring SNA Server for the AS/400 environment. In addition, for an X.25 connection using PVC, specify the PVC Alias.

SNA Server element	Parameter name in SNA Server		Instructions for configuring for the AS/400 environment
Server	Network Name (Local Node)		This generally corresponds to the RMTNETID setting on the AS/400. (APPN is often used.)
Server	Control Point Name (Local Node)		Corresponds to RMTCPNAME on the AS/400.
Connection	Remote End		Select Peer System as the Remote End for the connection.
Connection	Activation		Coordinate with the switched disconnect (SWTDSC) setting on the AS/400. If SWTDSC is *YES, select On Demand. If SWTDSC is *NO, select On Server Startup.
Connection	Local Node ID		Specify the Local Node ID, a required parameter for all connections. This corresponds to EXCHID on the AS/400.
Connection	Control Point Name (Remote Node)		Specify the AS/400 control point name (CP name) as the remote Control Point Name for the connection.
Connection	Network Name (Remote Node)		Corresponds to the RMTNETID on the AS/400. (APPN is often used.)
Connection	802.2: Remote Network Address SDLC: Poll Address X.25: Remote X.25 Address		Corresponds to ADPTADR in the Line Description on the AS/400. Corresponds to STNADR in the Line Description on the AS/400. Specify the address of the AS/400.
Connection	Max BTU Length		Corresponds to the MAXFRAME setting on the AS/400.
Remote APPC LU	LU Name		Specify the control point name of the AS/400 as the remote LU name.
Mode	Mode name		Choose the QPCSUPP mode for all LULU pairs to be used for AS/400 connectivity.
User or group listing	Default Local APPC LU		Assign a Default Local APPC LU to the user or group. If the user or group does not specify a Local LU name when opening a session to an AS/400, this default local LU name will be used.
User or group listing	Default Remote APPC LU		Assign a Default Remote APPC LU — which is the same as a default AS/400 — to the user or group. If the user or group does not specify a remote LU (that is, an AS/400) when opening a session, the assigned AS/400 will be used.


Guidelines for Configuring an AS/400 Computer
	Configuring for 5250 Emulation in the AS/400 Environment	5 of 7
Guidelines for Configuring an AS/400 Computer

This section provides some guidelines for configuring an AS/400 computer to communicate with an SNA server.

The administrator of the AS/400 may allow configurations to be created automatically in response to incoming requests. Alternatively, the administrator may disable this feature, to ensure a higher level of security. Work with the documentation for the AS/400 or with the administrator to determine the appropriate methods for configuring the AS/400.

Note

If the administrator of the AS/400 has allowed configurations to be created automatically in response to incoming requests, the parameters listed in this section need not be specified on the AS/400.

The following list shows some command sequences on the AS/400 and the parameters to set after choosing those command sequences. You must be logged on with administrative privilege on the AS/400 to configure the listed parameters. For more detailed information, see the AS/400 documentation.

Communications  Network configuration  Configure communications and remote hardware  Work with lines

Find out the name of the line from the AS/400 administrator. To enable automatic configuration for the line, for Autocreate controller, specify *YES, and for Autodelete controller (a timeout value), specify *NONE, or a large value such as 7000 (minutes). To prevent automatic configuration for the line, for Autocreate controller, specify *NO.

If the configuration is not automatic, specify the following:

APPN-capable *YES

A control point name and network identifier that match corresponding parameters in SNA Server

APPN CP session support *YES

Communications  Network configuration  Configure communications and remote hardware  Work with communications controllers

In this context, "Communications controller" means the SNA server.

If the configuration is not automatic, specify the local address of the SNA server:

Connection type	Address as specified in AS/400 configuration	Method for finding out address on SNA server
802.2	LAN remote adapter address	At the command prompt, type net config server; then view the line labeled "Server is active on."
SDLC	Station address (STNADR)	Start SNA Server Admin and view the Poll Address specified for the SDLC connection. (For SDLC, both ends use same address.)
X.25	Network address	Start SNA Server Setup, access the IBM X.25 Link Service Setup dialog box, and view the Local X.25 Address.


Guidelines for an AS/400 That Does Not Have PC Support
	Configuring for 5250 Emulation in the AS/400 Environment	6 of 7
Guidelines for Configuring an AS/400 Computer

Guidelines for an AS/400 That Does Not Have PC Support

You can connect to an AS/400 for 5250 emulation even if the AS/400 does not have PC Support. However, to do this, you must create the mode QPCSUPP on the AS/400, along with other resources that would have been created by PC Support. A recommended way to do this is to create the QPCSUPP mode, create the QWCPCSUP class, and add the class QWCPCSUP to the subsystem QCMN. For details about how to create these resources, see the online OS/400 [image] documentation for the related commands: CRTMODD, CRTCLS, and ADDRTGE.


Changing Session Limits with a Single Mode Name
	Configuring for 5250 Emulation in the AS/400 Environment	7 of 7
Guidelines for Configuring an AS/400 Computer

Changing Session Limits with a Single Mode Name

If the AS/400 requires different session limits on each LU (while the mode name stays the same), you must change the device description attached to the controller to reflect the correct number of sessions allowed for the LUs. For example, with a 5250 emulator, the mode name must be QPCSUPP. If you change the Parallel Session Limit on QPCSUPP for one LU-LU pair, all other LULU pairs that use the QPCSUPP mode will also be affected. Therefore, to change the session limit on some LUs but not others, you must change it at the AS/400.

The simplest way to get the correct number of sessions for the LUs on the AS/400 is to autocreate the controllers and devices, and then change the device description attached to the controller, so that the session limit is decreased. This is done by using the Change Device Description (CHGDEVAPPC) command. It needs to be done for each device description that needs to have different session limits. The AS/400 device settings that should be modified are Maximum sessions (MAXSSN) and Maximum conversations (MAXCNV).


Configuring LUs for LUA
Chapter 8	1 of 11

Configuring LUs for LUA

An LUA LU allows a connection to be used by applications based on LUA, which allows communication between a PC and a host. LUA applications can use LU 0, LU 1, LU 2, or LU 3 protocols.

You can carry out the following actions with LUA LUs:

Assign an LUA LU, or a range of LUA LUs, to a connection. A range of LUA LUs will allow multiple applications to use LUA simultaneously. For information, see: "Configuring Individual LUA LUs" or "Configuring a Range of LUA LUs" later in this chapter.

Configure the numbering for a new range of LUA LUs by specifying the lowest LU number and the number of LUs in the range. For information, see: "Configuring Numbering for an LUA LU Range" later in this chapter.

After creating a range of LUs, you can change the numbering of individual LUs in the range.

Configure properties for a new LUA LU or a new range of LUA LUs. This includes specifying the LU name and LU number for the LU(s). On a DFT connection, LUs must be configured one at a time, and require LU name, port number, and LT number. For information, see: "Configuring Properties for an LUA LU" or "Configuring Properties for an LUA LU Range" later in this chapter.

Optionally, group LUA LUs into one or more LUA LU pools. An LUA LU pool contains a number of LUs that are made available as a group to LUA applications. A given application can get LU access as long as one of the pooled LUs is available. For more information about LU pools, see: Chapter 10, "Using LU Pools to Maximize Access."

View or modify an existing LUA LU, regardless of whether it was created as part of a range. For information, see: "Configuring Individual LUA LUs" later in this chapter.

Copy properties from one LU to another. For information, see: "Copying Properties Between LUs" later in this chapter.

Move an LU from one connection to another. For information, see: "Moving an LU to a Different Connection" later in this chapter.

Delete an LU. For information, see: "Deleting LUs" later in this chapter.


Putting Configuration Changes into Effect
Configuring LUs for LUA	2 of 11

Putting Configuration Changes into Effect

Most configuration changes in SNA Server take effect the next time the server (node) is started. Therefore, after making changes to LUA LUs in an existing configuration, stop and restart the affected servers (nodes) in order to put the changes into effect. For more information about stopping and starting servers and connections, see: Chapter 11, "Managing SNA Server."


Configuring Individual LUA LUs
Configuring LUs for LUA	3 of 11

Configuring Individual LUA LUs

Before you can assign a new LU to a connection, you must configure the connection. For information about connections, see: Chapter 3, "Configuring Servers and Connections." For information about connections to host systems, see: "Working with Host Connections and 3270" in Chapter 5.

You can assign and configure new LUA LUs one at a time, or as a consecutively numbered range. For information about assigning and configuring a range of new LUA LUs, see: "Configuring a Range of LUA LUs" later in this chapter. You can view or modify individual LUs in a range after the range has been created.

You can copy properties from one LUA LU to another, or move an LUA LU from one connection to another. For information, see: "Copying Properties Between LUs" and "Moving an LU to a Different Connection" later in this chapter.

Check with the host administrator to determine the appropriate names and numbers for LUA LUs on your system.

To assign a new LUA LU

1.	In the Servers and Connections window, select the connection to which you want to assign the LUA LU.

The connection is highlighted, as shown in Figure 8.1.

Figure 8.1    A Highlighted Connection

2.	From the Services menu, choose Assign LUs.

The dialog box shown in Figure 8.2 appears.

Figure 8.2    Insert LU Dialog Box

3.	Under New Logical Unit, select the LUA option button.

4.	Choose the OK button.

The New LUA LU Properties dialog box appears. For information, see the next section.

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.	From the Services menu, choose Properties.

The LUA LU Properties dialog box appears. For information, see the next section.


Configuring Properties for an LUA LU
Configuring LUs for LUA	4 of 11

Configuring Individual LUA LUs

Configuring Properties for an LUA LU

For information about assigning a new LUA LU, or accessing an existing one, see the preceding section. When you assign or access an LUA LU, the New LUA LU Properties dialog box or the LUA LU Properties dialog box appears. The LUA LU Properties dialog box is shown in Figure 8.3.

Figure 8.3    LUA LU Properties Dialog Box

Find the items appropriate to your configuration, and supply information as follows. If you are configuring an LUA LU for a DFT connection, see also: "Numbers Needed for DFT LUs" later in this chapter.

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

Type a number identifying the 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 this 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" later in this chapter.

If the number you specify has already been assigned to an LU or an APPC LULU pair on the current connection, a message box appears, and you must change the number.

The range for LU Number is from 1 through 254.

LU Name

Type 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 name or pool name (except for APPC LU names) on the server.

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 to a Different Connection" later in this chapter.

Pool

If the LU has already been assigned to a pool, the pool name appears here. For information about LU pools, see: Chapter 10, "Using LU Pools to Maximize Access."

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. If the LU is assigned to a pool, the priority setting of the pool overwrites the setting of the LU, and the setting of the LU is grayed.

By default, this check box is selected.

After Configuring LUA LU Properties

After specifying LUA LU properties, in the LUA LU Properties dialog box, shown in Figure 8.3, choose a button according to the following:

To accept the settings, choose the OK button.

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

Numbers Needed for DFT LUs

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


Configuring a Range of LUA LUs
Configuring LUs for LUA	5 of 11

Configuring a Range of LUA LUs

Before you can assign LUs to a connection, you must configure the connection. For information about connections, see: Chapter 3, "Configuring Servers and Connections."

On a DFT connection, the only way to configure LUs is one at a time. For information about configuring LUs one at a time, see: "Configuring Individual LUA LUs" earlier in this chapter.

On an 802.2, SDLC, or X.25 connection, you can configure multiple LUs at one time by configuring them as a consecutively numbered range. Multiple LUA LUs allow multiple applications to access the host simultaneously. After configuring the range of LUs, you can modify the numbering and properties of individual LUs in the range. For information about assigning and configuring individual LUA LUs, see: "Configuring Individual LUA LUs" earlier in this chapter.

After configuring LUA LUs, you can assign them to LU pools. For information, see: Chapter 10, "Using LU Pools to Maximize Access."

In addition, you can copy properties from one LUA LU to another, or move an LUA LU from one connection to another. For information, see: "Copying Properties Between LUs" and "Moving an LU to a Different Connection" later in this chapter.

Check with the host administrator to determine the appropriate names and numbers for LUA LUs on your system.

To assign a range of new LUA LUs

1.	In the Servers and Connections window, select the connection to which you want to assign the LUA LU range.

The connection is highlighted, as shown in Figure 8.1.

2.	From the Services menu, choose Assign LUs.

The Insert LU dialog box, shown in Figure 8.2, appears.

3.	Under New Logical Unit, select the LUA option button.

4.	Under New Logical Unit, select the Range of LUs check box.

5.	Choose the OK button.

The Add LU Range dialog box appears. For information, see the next section.


Configuring Numbering for an LUA LU Range
Configuring LUs for LUA	6 of 11

Configuring a Range of LUA LUs

Configuring Numbering for an LUA LU Range

For information about assigning a range of new LUA LUs, see the preceding section. When you assign a range of LUA LUs, the dialog box shown in Figure 8.4 appears.

Figure 8.4    Add LU Range Dialog Box

Find the items appropriate to your configuration, and supply information as follows:

Base LU Name

Type 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 fewer. If you plan to use two-digit extension numbers, limit the base name to six characters or fewer.

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.

First LU Number

Type the first LU number in the range. An LU number identifies 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 LULU pair on the current connection, a message box appears, and you must change the number.

Possible values for the first LU number are from 1 through 254.

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.

Possible values for the number of LUs are from 2 through 254.

Selected LU Range

The range of LU names that you specified appears here.

After Configuring Numbering for an LUA LU Range

After typing the appropriate LU range values, in the Add LU Range dialog box, shown in Figure 8.4, choose a button according to the following:

To modify the extension numbering format (displayed under Selected LU Range), choose the Options button. See the next section.

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

To accept the settings and begin configuring the properties for the LU range, choose the OK button. For information, see: "Configuring Properties for an LUA LU Range" later in this chapter.


Modifying the Extension Numbering Format
Configuring LUs for LUA	7 of 11

Configuring a Range of LUA LUs

Modifying the Extension Numbering Format

For information about accessing the dialog box described in this section, see: "Configuring a Range of LUA LUs" and "Configuring Numbering for an LUA LU Range" earlier in this chapter.

When you choose the Options button in the Add LU Range dialog box, the dialog box expands as shown in Figure 8.5.

Figure 8.5    Add LU Range Dialog Box (with Numbering Options Displayed)

Find the items appropriate to your configuration, and supply information as follows:

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 fewer. If the base name is five characters long, limit the extensions to three digits or fewer.

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.

Number System

Select the Decimal or Hexadecimal option button. As with other extension number format options, the number system affects the extension numbers, not the LU numbers.

The default is Decimal.

Add Leading Zeroes (07 vs. 7)

If you do not want leading zeroes to be added to the extension numbers, clear this check box.

Leading zeroes ensure that LU names will display in correct order. For example, 09 will appear before 10, while 9 will appear after.

By default, the Add Leading Zeroes check box is selected.

After Modifying the Extension Numbering Format

After modifying the extension numbering format, in the Add LU Range dialog box, as shown in Figure 8.5, choose a button according to the following:

To accept the settings and begin configuring the properties for the LU range, choose the OK button. For information, see the next section.

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


Configuring Properties for an LUA LU Range
Configuring LUs for LUA	8 of 11

Configuring a Range of LUA LUs

Configuring Properties for an LUA LU Range

After assigning and numbering a range of LUA LUs, you can configure the LUs in the range. All the LUs will receive the same properties; you can modify individual LUs after configuring the range. For information about modifying individual LUs, see: "Configuring Individual LUA LUs" earlier in this chapter.

To configure properties for a range of LUA LUs

1.	Assign the range of LUA LUs to a connection, as described in: "To assign a range of new LUA LUs" earlier in this chapter.

2.	Configure the numbering for the range, as described in: "Configuring Numbering for an LUA LU Range" earlier in this chapter.

3.	In the Add LU Range dialog box, shown in Figures 8.4 and 8.5, choose the OK button.

The LUA LU Range Properties dialog box appears. For information, see the following section.

Range Properties

When you choose the OK button in the Add LU Range dialog box, the dialog box shown in Figure 8.6 appears. For information about accessing the LUA LU Range Properties dialog box, the preceding section.

Figure 8.6    LUA LU Range Properties Dialog Box

Find the items appropriate to your configuration, and supply information as follows:

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 to a Different Connection" later in this chapter.

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.

By default, this check box is selected.

After Configuring Properties for an LUA LU Range

After specifying properties for an LUA LU range, in the LUA LU Range Properties dialog box, shown in Figure 8.6, choose a button according to the following:

To accept the settings, choose the OK button.

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

After configuring LUA LUs, you can assign them to LU pools. For information, see: Chapter 10, "Using LU Pools to Maximize Access."


Copying Properties Between LUs
Configuring LUs for LUA	9 of 11

Copying Properties Between LUs

You can copy properties from one LU to another, regardless of whether either LU was created as part of a range.

To copy properties between LUs

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

2.	From the Services menu, choose Copy Properties.

The Copy Properties dialog box appears.

3.	Under To Logical Unit (LU), select one or more LUs to which you want to copy properties:

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.

If you copy properties to an active LU, the properties take effect when the LU is reset. For information about resetting an LU, see: Chapter 11, "Managing SNA Server."

4.	Choose the OK button.


Moving an LU to a Different Connection
Configuring LUs for LUA	10 of 11

Moving an LU to a Different Connection

You can move an LU to a different connection, regardless of whether the LU was created as part of a range.

To move one or more LUs to a different connection

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

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.

2.	From the Services menu, choose Move LU.

The Move dialog box appears.

3.	In the To Connection box, select the connection to which you want to move the LU.

4.	Choose the OK button.


Deleting LUs
Configuring LUs for LUA	11 of 11

Deleting LUs

To delete an LUA LU

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

2.	From the Edit menu, choose Delete.

3.	When prompted for confirmation, choose the Yes button.


Configuring Downstream Connections and LUs
Chapter 9	1 of 15

Configuring Downstream Connections and LUs

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 systems do not use the SNA Server client/server interface, with a downstream connection, they can use host connections available through the SNA server.

Figure 9.1 illustrates downstream connections and LUs:

Figure 9.1    Communication with a Downstream System

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 the downstream system and the host.

Multiple downstream systems can connect through one SNA server to a host, as shown in Figure 9.2:

Figure 9.2    Multiple Downstream Systems

The information that SNA Server passes from the downstream system to the 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.

Note that communication via a downstream connection and downstream LU in SNA Server is always dependent, that is, controlled by a host. Independent communication (not controlled by a host) is not available via downstream LUs on SNA Server.


Guidelines for Downstream Connections and LUs
Configuring Downstream Connections and LUs	2 of 15

Guidelines for Downstream Connections and LUs

As with any other connection, configuring a downstream connection requires you to gather information about the local and remote (downstream) systems, and consult with the administrator of the downstream system. For important details about gathering this information, see: Chapter 1, "Getting Started." For information about configuring connections, see: Chapter 3, "Configuring Servers and Connections."

The following guidelines give the sequence of steps for configuring downstream LUs and connections.

1.	Configure the host connection as you would configure any other connection to a host. When specifying the Remote End, in the Connection Properties dialog box, select Host System.

For information about configuring connections, see: Chapter 3, "Configuring Servers and Connections." For information about host parameters, see: "Working with Host Connections and 3270" in Chapter 5.

2.	Configure the downstream connection. To designate the connection as downstream, in the Connection Properties dialog box, under Remote End, select Downstream.

Note

The downstream connection can be an 802.2, SDLC, or X.25 connection. It cannot be a DFT connection.

For more information about configuring a downstream connection, see: "Configuring a Downstream Connection" later in this chapter. For information about configuring connections, also see: Chapter 3, "Configuring Servers and Connections."

3.	Select the host connection, and assign one or more new downstream LUs to that connection. For information about assigning new downstream LUs, see: "Configuring Individual Downstream LUs" or "Configuring a Range of Downstream LUs" later in this chapter.

4.	Optionally, pool downstream LUs, to maximize the access available via these LUs. For more information, see: Chapter 10, "Using LU Pools to Maximize Access."

5.	Select the downstream connection, and associate the downstream LUs (from step 3) and/or the LU pools (from step 4) with that connection. For more information, see: "Associating Downstream LUs with a Downstream Connection" later in this chapter.

6.	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. For more information, see: "Adjusting the Numbering of Downstream LUs" later in this chapter.

7.	To put all changes into effect, stop and restart the affected server as described in: Chapter 11, "Managing SNA Server."


Configuring a Downstream Connection
Configuring Downstream Connections and LUs	3 of 15

Configuring a Downstream Connection

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 Figure 9.1. Configure the host connection as described in: Chapter 3, "Configuring Servers and Connections."

To configure a new downstream connection

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

2.	From the Services menu, choose New Connection.

3.	In the Insert Connection dialog box, select the option button for the type of connection: 802.2, SDLC, or X.25.

Note

The downstream connection can be an 802.2, SDLC, or X.25 connection. It cannot be a DFT connection.

4.	Choose the OK button.

The Connection Properties dialog box appears. The dialog box is slightly different for each type of connection. The Connection Properties dialog box for an 802.2 connection is shown in Figure 9.3.

Figure 9.3    Connection Properties Dialog Box (802.2 Connection)

5.	In the Connection Properties dialog box, specify an appropriate connection name and link service; optionally, specify a comment. For more information, see: Chapter 3, "Configuring Servers and Connections."

6.	For an X.25 connection, select the appropriate Virtual Circuit Type. For more information, see: Chapter 3, "Configuring Servers and Connections."

7.	Under Remote End, select the Downstream option button.

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 the Setup button.

Depending on the type of the connection, the 802.2 Setup, SDLC Setup, or X.25 Setup dialog box appears. The 802.2 Setup dialog box is shown below.

For details about the 802.2 Setup, SDLC Setup, or X.25 Setup dialog boxes, see: Chapter 3, "Configuring Servers and Connections."

11.	Specify other connection parameters according to the hardware and software between the downstream system and the SNA server. For details, contact the network administrator and/or the operator of the downstream system, and see: Chapter 3, "Configuring Servers and Connections."

Note

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.

12.	When you are finished with the 802.2 Setup, SDLC Setup, or X.25 Setup dialog boxes, choose the OK button.

The Connection Properties dialog box, shown in Figure 9.3, appears.

13.	Choose OK.


Configuring Individual Downstream LUs
Configuring Downstream Connections and LUs	4 of 15

Configuring Individual 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: Chapter 3, "Configuring Servers and Connections."

You can assign and configure new downstream LUs one at a time, or as a consecutively numbered range. For information about assigning and configuring a range of new downstream LUs, see: "Configuring a Range of Downstream LUs" later in this chapter. You can view or modify individual LUs in a range after the range has been created.

In addition, you can move a downstream LU from one host connection to another. For information, see: "Moving an LU to a Different Host Connection" later in this chapter.

Check with the host administrator to determine the appropriate number(s) for downstream LU(s) on your system.

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" later in this chapter.

To assign a downstream LU to a host connection

1.	In the Servers and Connections window, select the host connection to which you want to assign the downstream LU.

The connection is highlighted, as shown in Figure 9.4.

Figure 9.4    Servers and Connections Window with Connection Highlighted

2.	From the Services menu, choose Assign LUs.

The dialog box shown in Figure 9.5 appears.

Figure 9.5    Insert LU Dialog Box

3.	Under New Logical Unit, select the Downstream option button.

4.	Choose the OK button.

The New Downstream LU Properties dialog box appears. For information, see: "Configuring Properties for a Downstream LU" later in this chapter.

To access an existing downstream LU for viewing or modifying

To modify the downstream LU number of a downstream LU, see: "Adjusting the Numbering of Downstream LUs" later in this chapter.

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

2.	From the Services menu, choose Properties.

The Downstream LU Properties dialog box appears. For information, see the next section.


Configuring Properties for a Downstream LU
Configuring Downstream Connections and LUs	5 of 15

Configuring Individual Downstream LUs

Configuring Properties for a Downstream LU

For information about assigning a new downstream LU, or accessing an existing one, see the preceding section. When you assign or access a downstream LU, the New Downstream LU Properties dialog box or the Downstream LU Properties dialog box appears. The Downstream LU Properties dialog box is shown in Figure 9.6.

Figure 9.6    Downstream LU Properties Dialog Box

Find the items appropriate to your configuration, and supply information as follows:

LU Number

Type a number identifying the LU to the host. 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 LULU pair on the current connection, a message box appears, and you must change the number.

The LU number, which identifies the LU to the host, need not match the downstream LU number, which identifies the LU to the downstream system. For information about changing the downstream LU number, see: "Adjusting the Numbering of Downstream LUs."

The range for LU Number is from 1 through 254.

Downstream LU Number

The downstream LU number is assigned by SNA Server when the LU is associated with a downstream connection. To change the downstream LU number, first complete the configuration of the downstream LU, then choose the OK button, and follow the procedure in: "Adjusting the Numbering of Downstream LUs" later in this chapter.

The downstream LU number identifies the LU to the downstream system, and need not match the LU number, which identifies the LU to the host.

LU Name

Type 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 in your installation.

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 to a Different Host Connection" later in this chapter.

Pool

If the LU has already been assigned to a pool, the pool name appears here. For information about LU pools, see: Chapter 10, "Using LU Pools to Maximize Access."

Comment

Optionally, type a comment of up to 25 characters.

After Configuring Downstream LU Properties

After specifying downstream LU properties, in the New Downstream LU Properties dialog box or the Downstream LU Properties dialog box, shown in Figure 9.6, choose a button according to the following:

To accept the settings, choose the OK button.

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

After configuring downstream LUs, you can group them into LU pools. For information, see: Chapter 10, "Using LU Pools to Maximize Access."

After creating a downstream LU or downstream LU pool, associate it with a downstream connection. For more information, see: "Associating Downstream LUs with a Downstream Connection" later in this chapter.


Configuring a Range of Downstream LUs
Configuring Downstream Connections and LUs	6 of 15

Configuring a Range of Downstream LUs

Before you can create a range of downstream LU, you must configure the host connection the LUs will use. Configure this connection as you would any other host connection. For more information, see: Chapter 3, "Configuring Servers and Connections."

You can configure multiple LUs at one time by configuring them as a consecutively numbered range. Multiple downstream LUs allow multiple downstream systems to access the host simultaneously. After configuring the range of LUs, you can modify the numbering of individual LUs in the range. For information about assigning and configuring individual downstream LUs, see: "Configuring Individual Downstream LUs" earlier in this chapter.

After configuring downstream LUs, you can group them into LU pools. For information, see: Chapter 10, "Using LU Pools to Maximize Access."

In addition, you can move downstream LUs from one host connection to another. For information, see: "Moving an LU to a Different Host Connection" later in this chapter.

Check with the host administrator to determine the appropriate numbers for downstream LUs on your system.

After creating downstream LUs or LU pools on a host connection, associate the LUs or pools with a downstream connection. For more information, see: "Associating Downstream LUs with a Downstream Connection" later in this chapter.

To assign a range of downstream LUs to a host connection

1.	In the Servers and Connections window, select the connection to which you want to assign the downstream LU range.

The connection is highlighted, as shown in Figure 9.4.

2.	From the Services menu, choose Assign LUs.

The Insert LU dialog box, shown in Figure 9.5, appears.

3.	Under New Logical Unit, select the Downstream option button.

4.	Under New Logical Unit, select the Range of LUs check box.

5.	Choose the OK button.

The Add LU Range dialog box appears. For information, see the next section.


Configuring Numbering for a Downstream LU Range
Configuring Downstream Connections and LUs	7 of 15

Configuring a Range of Downstream LUs

Configuring Numbering for a Downstream LU Range

For information about assigning a range of new downstream LUs, see the preceding section. When you assign a range of downstream LUs, the dialog box shown in Figure 9.7 appears.

Figure 9.7    Add LU Range Dialog Box

Find the items appropriate to your configuration, and supply information as follows:

Base LU Name

Type 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 fewer. If you plan to use two-digit extension numbers, limit the base name to six characters or fewer.

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 or LU pool in your installation.

The LU names identify the LUs on the SNA server only, not on the host or downstream system.

First LU Number

Type the first LU number in the range. An LU number identifies 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 LULU pair on the current connection, a message box appears, and you must change the number.

Possible values for the first LU number are from 1 through 254.

Number of LUs

Type the number of LUs that you want in the 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.

Possible values for the number of LUs are from 2 through 254.

Selected LU Range

The range of LU names that you specified appears here.

After Configuring Numbering for a Downstream LU Range

After typing the appropriate LU range values, in the Add LU Range dialog box, shown in Figure 9.7, choose a button according to the following:

To modify the extension numbering format (displayed under Selected LU Range), choose the Options button. See the next section.

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

To accept the settings and add a comment for the LU range, choose the OK button. For information, see: "Adding a Comment for a Downstream LU Range" later in this chapter.


Modifying the Extension Numbering Format
Configuring Downstream Connections and LUs	8 of 15

Configuring a Range of Downstream LUs

Modifying the Extension Numbering Format

For information about accessing the dialog box described in this section, see: "Configuring a Range of Downstream LUs" and "Configuring Numbering for a Downstream LU Range" earlier in this chapter.

When you choose the Options button in the Add LU Range dialog box, the dialog box expands as shown in Figure 9.8.

Figure 9.8    Add LU Range Dialog Box (with Numbering Options Displayed)

Find the items appropriate to your configuration, and supply information as follows:

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 fewer. If the base name is five characters long, limit the extensions to three digits or fewer.

The range is from 0 through 999 for decimal, and from 0 through FFF for hexadecimal. The default is the first LU number.

Number System

Select the Decimal or Hexadecimal option button.

The default is Decimal.

Add Leading Zeroes (07 vs. 7)

If you do not want leading zeroes to be added to the extension numbers, clear this check box.

Leading zeroes ensure that LU names will display in correct order. For example, 09 will appear before 10, while 9 will appear after.

By default, the Add Leading Zeroes check box is selected.

After Modifying the Extension Numbering Format

After modifying the extension numbering format, in the Add LU Range dialog box, shown in Figure 9.8, choose a button according to the following:

To accept the settings, choose the OK button. Then, in the Downstream LU Range Properties dialog box, you can choose OK to accept the range configuration, or you can add a comment. For information about adding a comment, see the next section.

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

After configuring downstream LUs, you can group them into LU pools. For information, see: Chapter 10, "Using LU Pools to Maximize Access."


Adding a Comment for a Downstream LU Range
Configuring Downstream Connections and LUs	9 of 15

Configuring a Range of Downstream LUs

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 Individual Downstream LUs" earlier in this chapter.

To add a comment for a range of downstream LUs

1.	Assign the range of downstream LUs to a connection, as described in: "Configuring a Range of Downstream LUs" earlier in this chapter.

2.	Configure the numbering for the range, as described in: "Configuring Numbering for a Downstream LU Range" earlier in this chapter.

3.	In the Add LU Range dialog box, shown in Figures 9.7 and 9.8, choose the OK button.

The Downstream LU Range Properties dialog box appears.

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

5.	Choose the OK button.

After configuring downstream LUs, you can group them into LU pools. For information, see: Chapter 10, "Using LU Pools to Maximize Access."


Associating Downstream LUs with a Downstream Connection
Configuring Downstream Connections and LUs	10 of 15

Associating Downstream LUs with a Downstream Connection

Before you can associate downstream LUs with a downstream connection, you must configure the connection and the LUs. For information about downstream connections, see: "Configuring a Downstream Connection" earlier in this chapter, and Chapter 3, "Configuring Servers and Connections." For information about downstream LUs, see: "Configuring Individual Downstream LUs" or "Configuring a Range of Downstream LUs" earlier in this chapter.

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.	From the Services menu, choose Assign LUs.

The Assign Downstream LU/Pool Sessions dialog box appears.

Only downstream LUs and pools are listed in the dialog box.

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

4.	Choose the OK button.

The LUs associated with the downstream connection are listed to the right of the connection. An example of such a list is shown in Figure 9.9.

Figure 9.9    Downstream Connection with Associated Downstream LUs

In this display, for a downstream LU in session, the host connection used by the LU is shown under Connection. For a downstream LU pool that has an LU in session, the LU name is shown under Host LU.

5.	To put all changes into effect, stop and restart the affected SNA server(s), as : Chapter 11, "Managing SNA Server."


Adjusting the Numbering of Downstream LUs
Configuring Downstream Connections and LUs	11 of 15

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.


Examples of Adjusted Numbering
Configuring Downstream Connections and LUs	12 of 15

Adjusting the Numbering of Downstream LUs

Examples of Adjusted Numbering

The following illustration shows three downstream LUs associated with a connection called DOWNCON1:

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:

For information about changing the order of downstream LUs, see: "Reordering the List of LUs for a Downstream Connection" later in this chapter.

The next illustration shows three LUs associated with a connection called DOWNCON2:

If the downstream system expects downstream LU numbers 5, 6, and 7, then 3 empty LU pools could be created, using the names EMPTY2, EMPTY3, and EMPTY4. Then the LUs and LU pools could be ordered as shown:


Reordering the List of LUs for a Downstream Connection
Configuring Downstream Connections and LUs	13 of 15

Adjusting the Numbering of Downstream LUs

Reordering the List of LUs for a Downstream Connection

For an explanation and examples of reordering a list of LUs for a downstream connection, see the previous sections.

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.

The LUs are listed to the right of the connection. An example of such a list is shown in Figure 9.9.

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.

Moving an LU or pool up in the list means it will be assigned a smaller number.

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 the OK button.

The selected LUs are moved up in the list, and other LUs are moved down.


Moving an LU to a Different Host Connection
Configuring Downstream Connections and LUs	14 of 15

Moving an LU to a Different Host Connection

You can move one or more downstream LUs to a different host connection, regardless of whether the LUs were created as part of a range. Downstream LUs can be assigned to only one host connection, although downstream LUs can be associated with multiple downstream connections.

To move one or more LUs to a different host connection

1.	In the Servers and Connections window, select the host connection to which the LUs are assigned.

2.	Select the LU(s) that you want to move to a different host connection.

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

The Move dialog box appears.

4.	In the To Connection box, select the connection to which you want to move the LU.

5.	Choose the OK button.


Deleting LUs
Configuring Downstream Connections and LUs	15 of 15

Deleting LUs

To delete a downstream LU

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

2.	From the Edit menu, choose Delete.

3.	When prompted for confirmation, choose the Yes button.


Using LU Pools to Maximize Access
Chapter 10	1 of 9

Using LU Pools to Maximize Access

LU pools are groupings of 3270, LUA, or downstream LUs that allow you to maximize access to these LUs. A user, LUA application, or downstream system using the pool can get LU access as long as one of the pooled LUs is available. If some of the pooled LUs are not functioning, the user, LUA application, or downstream system will not be affected, as long as another LU in the pool is available.

LU pools can maximize access:

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 balancing 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 per server.

A number of steps are needed in order to make an LU pool fully functional:

1.	Configure the LUs that the pool will contain. For information about configuring LUs that can be included in a pool, see: Chapter 4, "Configuring for 3270," Chapter 8, "Configuring LUs for LUA," or Chapter 9, "Configuring Downstream Connections and LUs."

2.	Create the pool, as described in: "3270 LU Pools," "LUA Pools," or "Downstream Pools" later in this chapter.

3.	Assign the intended LUs to the pool, as described in: "Specifying the LUs in an LU Pool" later in this chapter.

In order to provide LU access, a pool must contain LUs. An empty pool provides no LU access.

4.	Assign the pool to a user, LUA application, or downstream system. For information about assigning a 3270 pool to a user, see: Chapter 4, "Configuring for 3270." For information about LUA applications, see: the Microsoft SNA Server LUA Programmer's Guide.  For information about assigning a downstream pool to a downstream connection, see: Chapter 9, "Configuring Downstream Connections and LUs."

5.	To put all changes into effect, stop and restart the affected SNA server(s), as described in: Chapter 11, "Managing SNA Server."

This chapter tells how to:

Add, view, or modify pools of each of the available kinds: 3270, LUA, or downstream.

Specify the LUs in a given pool, by assigning, removing, or moving the LUs.

In order to provide LU access, a pool must contain LUs. An empty pool provides no LU access.

Reset the LUs in a pool.

For information about 3270 LUs and users, see Chapter 4, "Configuring for 3270." For information about LUA LUs, see: Chapter 8, "Configuring LUs for LUA." For information about downstream LUs, see: Chapter 9, "Configuring Downstream Connections and LUs."


Putting Configuration Changes into Effect
Using LU Pools to Maximize Access	2 of 9

Putting Configuration Changes into Effect

Most configuration changes in SNA Server take effect the next time the server (node) is started. Therefore, after making changes to LU pools in an existing configuration, stop and restart the affected servers (nodes) in order to put the changes into effect. For more information about stopping and starting servers and connections, see: Chapter 11, "Managing SNA Server."


3270 LU Pools
Using LU Pools to Maximize Access	3 of 9

3270 LU Pools

Before creating a 3270 LU pool, configure the LUs that will go in the pool. For information, see: Chapter 4, "Configuring for 3270." For important information about assigning LUs to a pool, see: "Specifying the LUs in an LU Pool" later in this chapter.

To initiate adding a 3270 LU pool

1.	In the LU Pools window, select any item.

2.	From the Pools menu, choose New Pool.

The New Pool dialog box appears. Under Pool Type, 3270 will already be selected.

For an illustration of the dialog box and details about the settings, see the next section.

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.	From the Pools menu, choose Properties.

The 3270 LU Pool Properties dialog box appears. For an illustration of the dialog box and details about the settings, see the next section.


Configuring Properties for a 3270 LU Pool
Using LU Pools to Maximize Access	4 of 9

3270 LU Pools

Configuring Properties for a 3270 LU Pool

For information about adding a 3270 LU pool, or accessing an existing 3270 LU pool, see the preceding section. When you add or access a 3270 LU pool, the New Pool dialog box or the 3270 LU Pool Properties dialog box appears. The New Pool dialog box is shown in Figure 10.1. The 3270 LU Pool Properties dialog box is shown in Figure 10.2.

Figure 10.1    New Pool Dialog Box

Figure 10.2    3270 LU Pool Properties Dialog Box

Find the items appropriate to your configuration, and supply information as follows:

Pool Name

Type a name identifying the 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) in the installation.

Comment

Optionally, type a comment of up to 25 characters.

Display Model

Select a size for the 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 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.

The default is Model 2.

Model can be overridden

Select this check box to allow users to override the display model type by using the 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.

By default, this check box is selected.

To exit the dialog box without accepting the configuration settings, choose the Cancel button. To accept the settings, choose the OK button. After accepting the settings, add LUs to the pool as described in: "Specifying the LUs in an LU Pool" later in this chapter. A pool provides LU access only after LUs have been added to it.


LUA Pools
Using LU Pools to Maximize Access	5 of 9

LUA Pools

Before creating an LUA LU pool, configure the LUs that will go in the pool. For information, see: Chapter 8, "Configuring LUs for LUA." For important information about assigning LUs to a pool, see: "Specifying the LUs in an LU Pool" later in this chapter.

To initiate adding an LUA LU pool

1.	In the LU Pools window, select any item.

2.	From the Pools menu, choose New Pool.

The New Pool dialog box, shown in Figure 10.1, appears.

3.	Under Pool Type, select LUA.

For an illustration of the dialog box and details about the settings, see the next section.

To access an existing LUA 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.	From the Pools menu, choose Properties.

The LUA LU Pool Properties dialog box appears. For an illustration of the dialog box and details about the settings, see the next section.


Configuring Properties for an LUA LU Pool
Using LU Pools to Maximize Access	6 of 9

LUA Pools

Configuring Properties for an LUA LU Pool

For information about adding an LUA LU pool, or accessing an existing LUA LU pool, see the preceding section. When you add or access an LUA LU pool, the New Pool dialog box or the LUA LU Pool Properties dialog box appears. The New Pool dialog box is shown in Figure 10.1. The LUA LU Pool Properties dialog box is shown in Figure 10.3.

Figure 10.3    LUA LU Pool Properties Dialog Box

Find the items appropriate to your configuration, and supply information as follows:

Pool Name

Type a name identifying the 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) in the installation.

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.

By default, this check box is selected.

To exit the dialog box without accepting the configuration settings, choose the Cancel button. To accept the settings, choose the OK button. After accepting the settings, add LUs to the pool as described in: "Specifying the LUs in an LU Pool" later in this chapter. A pool provides LU access only after LUs have been added to it.


Downstream Pools
Using LU Pools to Maximize Access	7 of 9

Downstream Pools

Before creating a downstream LU pool, configure the LUs that will go in the pool. For information, see: Chapter 9, "Configuring Downstream Connections and LUs." For important information about assigning LUs to a pool, see: "Specifying the LUs in an LU Pool" later in this chapter.

To add a downstream LU pool

1.	In the LU Pools window, select any item.

2.	From the Pools menu, choose New Pool.

The New Pool dialog box, shown in Figure 10.1, appears.

3.	Under Pool Type, select the Downstream option button.

4.	In the Pool Name box, type a name identifying the 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) in the installation.

The name identifies the pool on the SNA server only, not on a host or downstream system.

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

6.	Choose the OK button.

After adding the pool, add LUs to it as described in the next section. A pool provides LU access only after LUs have been added to it.

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.	From the Pools menu, choose Properties.

The Downstream LU Pool Properties dialog box appears, showing the name and the optional comment for the pool.

You can change the list of LUs assigned to the pool. For information, see the next section. Note that a pool provides LU access only if there are LUs in the pool.


Specifying the LUs in an LU Pool
Using LU Pools to Maximize Access	8 of 9

Specifying the LUs in an LU Pool

In order to provide LU access, a pool must contain LUs. You can add LUs to an LU pool, remove LUs from a pool, or move an LU to a different pool.

For information about adding or specifying properties for a specific LU pool, see the following sections earlier in this chapter:

3270 LU Pools

LUA Pools

Downstream Pools

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.	From the Pools menu, choose Assign LUs.

The Assign Pool LUs dialog box appears:

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

4.	Choose the OK 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.

The pool provides LU access only to the LUs assigned to it. The pool provides this access when the pool is assigned to a user, LUA application, or downstream connection. For information about assigning a 3270 pool to a user, see: Chapter 4, "Configuring for 3270." For information about LUA applications, see: the Microsoft SNA Server LUA Programmer's Guide. For information about assigning a downstream pool to a downstream connection, see: Chapter 9, "Configuring Downstream Connections and LUs."

To remove LUs 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(s) you want to remove.

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 Edit menu, choose Delete.

4.	When prompted for confirmation, choose the Yes button.

To move one or more LUs to a different pool

1.	In the LU Pools window, select the pool that the LU(s) are 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, select the LU(s) you want to move.

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.

The LU(s) are highlighted.

3.	From the Pools menu, choose Move.

The Move dialog box appears.

4.	Under To LU Pool, select the pool to which you want to move the LU(s).

5.	Choose the OK 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.

The pool provides LU access only to the LUs assigned to it. The pool provides this access when the pool is assigned to a user, LUA application, or downstream connection. For information about assigning a 3270 pool to a user, see: Chapter 4, "Configuring for 3270." For information about LUA applications, see the Microsoft SNA Server LUA Programmer's Guide. For information about assigning a downstream pool to a downstream connection, see: Chapter 9, "Configuring Downstream Connections and LUs."


Resetting an LU in an LU Pool
Using LU Pools to Maximize Access	9 of 9

Resetting an LU in an LU Pool

You can reset an LU from the LU Pools window. Resetting an LU stops it and allows it to restart when needed. Resetting an LU can help restore function when problems have occurred.

To reset an LU in an LU pool

1.	In the LU Pools window, select the pool containing the LU.

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.	Select the LU.

You can only reset an LU that has a status of Active, SSCP, or In Session.

3.	From the Pools menu, choose Reset LUs.

4.	When prompted for confirmation, choose the Yes button.


Managing SNA Server
Chapter 11	1 of 10

Managing SNA Server

You can manage services on the SNA network by starting and stopping SNA servers (nodes), starting and stopping connections, and resetting LUs. In addition, when managing an SNA Server installation, you may need to change the domain of focus, delete SNA resources, or perform actions on a configuration file, including saving, reopening, backing up, or restoring the file. This chapter describes these actions, which have the following effects:

Starting (or restarting) SNA servers makes them available for use, and puts recent configuration changes into effect.

Starting connections makes them available to the LUs and the users, applications, or downstream systems that access the LUs.

Stopping services allows you to modify the server configuration, correct problems, or perform routine server maintenance. However, stopping services can also interrupt interactions between a peer or a host and a user. Therefore, when possible, have users log off before stopping services.

Resetting an LU may restore function to the LU if problems have occurred.

Changing the domain of focus allows you to work with SNA servers in different domains.

Deleting SNA resources, such as connections assigned to a server, or LUs assigned to a user, removes the resources from the former assignments.

Saving and reopening a configuration allows you to create and use a set of useful configuration settings.

Backing up and restoring a configuration allows you to protect against loss of configuration information.

Changing the primary SNA server (the server that holds the configuration file for the domain) allows you to modify the way you use the hardware and software available in your domain.

The following table shows how to find other information that you may need when managing SNA Server:

Topic related to management of SNA Server		Source for information
Adjusting server broadcast settings and other settings that affect the way SNA servers communicate		Chapter 3, "Configuring Servers and Connections"
Configuring an SNA server to support Macintosh clients		Microsoft SNA Server Installation Guide
Setting up security in an SNA Server domain		Chapter 12, "Setting Up Security with SNA Server"
Finding out LU status: which LUs are active, what connection they are active on, and what users are using them		Chapter 13, "Using Diagnostic Tools"
Creating or modifying an SNA Server configuration file to be used at a remote site		Appendix D, "Offline Configuration"
SNA Server is fully integrated with the Windows NT Service Control Architecture. The background processes of SNA Server (SnaBase, SnaServer, NVRunCmd, NVAlert, and the link services) are services that can be managed by the same methods as other Windows NT services. That is, these background processes can be managed by net commands, and by the Services option in the Control Panel, as well as via SNA Server Admin.


Starting and Stopping Servers and Connections
Managing SNA Server	2 of 10

Starting and Stopping Servers and Connections

Stopping and restarting SNA servers is necessary in order to put many types of configuration changes into effect.

Before you can start a connection, you must configure it. For more information, see: Chapter 3, "Configuring Servers and Connections," and Chapter 9, "Configuring Downstream Connections and LUs."

To start an SNA server (node) or a connection

1.	In the Servers and Connections window, select the SNA server or connection you want to start.

2.	From the Services menu, choose Start Services.

For servers, or for connections other than those configured as On Demand or Incoming, the process of starting the service begins.

For On Demand connections, there are 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.

For Incoming connections, there are 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.

To stop an SNA server (node) or a connection

To avoid leaving a remote host or peer in an unresolved, nonfunctional state, have all users log off from the host before stopping services.

1.	In the Servers and Connections window, select the SNA server or connection you want to stop.

2.	From the Services menu, choose Stop Services.

3.	When prompted for confirmation, choose the Yes button.

For information about On Demand connections and Incoming connections, see the last step in the preceding procedure.


Resetting LUs
Managing SNA Server	3 of 10

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 access to LUs and the connections they use, you can create LU pools. For information, see: Chapter 10, "Using LU Pools to Maximize Access."

To reset an LU

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.	From the Services menu, choose Reset LU.

4.	When prompted for confirmation, choose the Yes button.

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.	From the Services menu, choose Properties.

The APPC LU Properties dialog box appears.

3.	Choose the Status button.

The APPC LU Status dialog box appears.

4.	Select the LU-LU pair you are interested in, then choose the Zoom button.

The Session Status dialog box appears.

5.	In the Session Status dialog box, select the LU-LU session that you want to deactivate.

6.	Choose the Deactivate button.

7.	Choose the OK button.

8.	Choose the Close button or the Cancel button until the dialog boxes have all been closed.


Changing the Domain of Focus
Managing SNA Server	4 of 10

Changing the Domain of Focus

With SNA Server Admin, you can change the domain of focus, which allows you to work with servers in different domains.

To change the domain of focus of SNA Server Admin

1.	From the File menu, choose Select Domain.

2.	The Select Domain dialog box appears.

3.	Select the intended domain, either from the list of recently selected domains (labeled "Select Domain"), or from the complete list of domains (labeled "Domains").

The selected domain appears in the Select Domain box.

4.	Choose OK.


Using SNA Server Additions
Managing SNA Server	5 of 10

Using SNA Server Additions

Certain software modules can be accessed through SNA Server Admin as additions to SNA Server. For example, the SNA Server Trace Options utility can be accessed through SNA Server Admin.

To access SNA Server Additions

1.	In the Servers and Connections window, select the SNA server that you want the SNA Server addition to affect.

2.	From the Services menu, choose Properties.

The Server Properties dialog box appears.

3.	Choose the Addons button.

The SNA Server Additions dialog box appears.

4.	In the list under Available SNA Server Additions, select the addition you want to use.

5.	Choose the Select button.

The addition is started through SNA Server. When you finish using the addition and close it, the SNA Server Additions dialog box reappears.

6.	Choose Close and then Cancel to close the dialog boxes.


Deleting SNA Resources
Managing SNA Server	6 of 10

Deleting SNA Resources

To delete the SNA resources shown in the following table, select the indicated item, and then press the DEL key or, from the Toolbar, click the Delete button. When prompted to confirm the deletion, choose the Yes button.

Note

Before deleting a server or connection, you must stop it. See: "Starting and Stopping Servers and Connections" earlier in this chapter.

Resource to delete		Window	Item to select
A server		Servers and Connections	The server
A connection		Servers and Connections	The connection
An LU		Servers and Connections	The LU
An SNA user or group		Users and Groups	The user or group
The assignment of an LU or LU pool to a user or group		Users and Groups	The LU or pool as it is listed across from the user or group
The assignment of an LU to a pool		LU Pools	The LU as it is listed across from the pool
An LU pool		LU Pools	The LU pool


Working with Configuration Files
Managing SNA Server	7 of 10

Working with Configuration Files

You can carry out the following actions with configuration files:

Save the current configuration. When you exit and restart SNA Server, the last configuration saved is the one that is loaded. For information about saving the configuration, see: "Saving and Reopening the Configuration" and "Configuration Files on Primary and Backup SNA Servers" later in this chapter.

Reopen the last configuration that was saved, abandoning any changes that have been made but not saved. For information about reopening the configuration, see: "Saving and Reopening the Configuration" and "Configuration Files on Primary and Backup SNA Servers" later in this chapter.

Back up the current configuration. The default extension for backup configuration files for SNA Server is .SNA. Note that creating a backup copy of the current configuration is a different action from working with a backup SNA server, which is described in: "Configuration Files on Primary and Backup SNA Servers" later in this chapter. For more information about backing up the configuration, see: "Backing Up and Restoring the Configuration" later in this chapter.

Restore a configuration from a backup configuration file. The default extension for backup configuration files for SNA Server is .SNA. For more information about restoring a configuration, see: "Backing Up and Restoring the Configuration" later in this chapter.

Create an SNA configuration file that will be sent to a different SNA site. A configuration file created at a site other than where it is used is called an offline configuration file. For more information, see: Appendix D, "Offline Configuration."


Saving and Reopening the Configuration
Managing SNA Server	8 of 10

Working with Configuration Files

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.

To save the current configuration

From the File menu, choose Save Configuration.

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 the next section), 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
Managing SNA Server	9 of 10

Working with Configuration Files

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" later in this chapter.

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 the OK button.

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 the OK button.


Configuration Files on Primary and Backup SNA Servers
Managing SNA Server	10 of 10

Working with Configuration Files

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, which holds the configuration file for the domain, and one or more backup SNA servers, on which SNA Server replicates the configuration file. If you designate one or more backup servers, and the primary server is not functioning when you start SNA Server Admin, SNA Server will load 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.

Changing the Primary SNA Server

This section tells how to designate a different server as the primary SNA server in a domain.

To change the primary SNA server

1.	On the original primary SNA server, in SNA Server Admin, use the File menu Backup command to back up the configuration file.

2.	Exit from SNA Server Admin.

3.	At the Windows NT command prompt, type:

net stop snabase

4.	Start SNA Server Setup and change the Server Role from Primary to Backup or Member.

The server is now a backup or member SNA server, not a primary SNA server.

5.	On the server that will become the primary SNA server, at the Windows NT command prompt, type:

net stop snabase

6.	Start SNA Server Setup and, in the Change SNA Server Role dialog box, select the Primary Configuration Server option.

The server is now the primary SNA server.

7.	Start SNA Server Admin.

8.	From the File menu, choose Restore, and select the backup configuration file saved in step 1.

9.	On the server that used to be the primary SNA server, at the Windows NT command prompt, type:

net start snabase

Copying the Configuration File Between Servers

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 file is copied to the backup SNA server(s).

To copy the configuration file from the primary SNA server to a backup SNA server

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 point, 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 point enables SNA Server to access the configuration file on the primary or backup servers.

5.	When prompted for confirmation, choose the Yes button.


Setting Up Security with SNA Server
Chapter 12	1 of 9

Setting Up Security with SNA Server

This chapter describes how security works with SNA Server, and how you can configure SNA servers to provide the level of security you choose.


Overview of Security on SNA Servers
Setting Up Security with SNA Server	2 of 9

Overview of Security on SNA Servers

The following sections provide background about the basic architecture of SNA Server security. The sections provide outlines of:

The architecture of SNA Server itself, and how it provides secure access.

The way that SNA Server interacts with security in Windows NT and with other SNA systems (generally mainframes and AS/400s).

The way that SNA Server handles logons carried out by users on client computers.


How SNA Server Components Provide Secure Access
Setting Up Security with SNA Server	3 of 9

Overview of Security on SNA Servers

How SNA Server Components Provide Secure Access

All SNA Server components communicate with each other, and with transport components, through the DMOD service layer. Because SNA Server security is carried out by the DMOD, and all communication passes through the DMOD, the security features in SNA Server cannot be bypassed. This is illustrated in Figure 12.1.

Figure 12.1    How the DMOD Service Layer Provides Secure Access

1. SNANW is a component that allows SNA Server to communicate on a NetWare network.

2. SNAAT is a component that allows SNA Server to communicate through AppleTalk [image].

3. SNAIP is a component that allows SNA Server to communicate through TCP/IP.


Security with Windows NT, SNA Server, and Other SNA Systems
Setting Up Security with SNA Server	4 of 9

Overview of Security on SNA Servers

Security with Windows NT, SNA Server, and Other SNA Systems

SNA Server uses 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. A simple dialog box in SNA Server Admin allows you to specify which users and groups defined in the domain will be SNA Server users and groups.

For mainframes, a basic unit of access is the 3270 logical unit (LU). To give users access to the mainframe through 3270 emulation, you assign 3270 LUs or LU pools (groups of LUs) to the users or groups. By controlling the assignment of 3270 LUs and LU pools, you can control access to the mainframe. (Access to a mainframe can also be controlled at the mainframe itself, through the logon process.)

Access to an AS/400 is not restricted in the same way as for a mainframe, because of the design of LU 6.2, the type of LU used with AS/400s. If a user has an account in the Windows NT domain and knows correct information about LU 6.2 LUs (APPC LUs) configured in SNA Server, that user can potentially access the AS/400 to which the LUs communicate. Therefore, access to AS/400s must be controlled through the accounts available to users, the LU information available to users, and/or the logon process used on the AS/400.

The user and LU information for SNA Server is stored in the SNA Server configuration file. Therefore, it is essential to control access to the configuration file. In other words, security on SNA servers involves control at two different levels:

Controlling user accounts and controlling the creation and assignment of LUs, so that you determine which users have access to mainframe or AS/400 resources, as outlined in this section.

Controlling access to the tools and files by which users can create or change accounts and LUs. These tools and files include the Windows NT administrative tools, SNA Server Admin, and the SNA Server configuration file. Control of these is described in: "Increasing the Security of SNA Servers in a Domain," later in this chapter.


Client Logon
Setting Up Security with SNA Server	5 of 9

Overview of Security on SNA Servers

Client Logon

The logon process used by a user on a client system is important, because it is through this process that the user is identified to the Windows NT domain and to SNA servers in the domain. The way that the logon process is handled by SNA Server depends on the network software on the client system.

Microsoft networking (using named pipes) on client systems

Microsoft networking is used on most computers running Windows NT or Windows for Workgroups; it is also used on all computers running Microsoft LAN Manager (the Microsoft network software used with Windows version 3.x or with MS-DOS).

A user on a computer using Microsoft networking only needs to log on once for access to both the Windows NT domain and SNA servers in the domain. Encryption and secure protocols are used for logging the user on across the network.

Non-Microsoft networking (not using named pipes) on client systems

Non-Microsoft networking includes software such as Novell [image] NetWare [image], TCP/IP, and Banyan [image] VINES [image], and does not use named pipes. A user on a computer using non-Microsoft networking must log on twice: once for access to the Windows NT domain, and once for access to SNA servers in the domain. Much as with named pipes, the password for the client is encrypted immediately, and secure protocols are used for logging the user on across the network. SNA Server sends no information to the client system until the logon process is successfully completed. A user on this type of client computer can use the same password for both logons, if desired.

For any type of client, once the client's logon process for one SNA server has been completed, additional SNA servers can provide services without another interactive user logon. That is, additional SNA servers can repeat the logon verification without the involvement of the user.

Further logon processes can be set up on mainframes or AS/400s; such logon processes should be coordinated between the system administrators for the various systems. For example, if tight security is maintained with the logon to a mainframe, it may make sense to keep access open-ended at the SNA server. This is described in the next section.


Allowing Open-Ended Access to LUs
Setting Up Security with SNA Server	6 of 9

Allowing Open-Ended Access to LUs

In some SNA Server domains, open-ended access to LUs may be preferable to restricted access, if the needed security already exists in the logon process used with the mainframe or AS/400. To create very open-ended access to LUs, you can establish the access through the Guest account or the account called Everyone:

To create access through the Guest account, activate that account in the Windows NT domain, as described in the Windows NT documentation. Then add the Guest account to the list of groups and users recognized by SNA Server, and assign LUs to the account.

To create access through the account called Everyone, add that account to the list of groups and users recognized by SNA Server, and assign LUs to the account.

Even in domains where users are allowed open-ended access to LUs, the security of the SNA Server configuration file may be important. For information about securing the configuration file, see the next section.


Increasing the Security of SNA Servers in a Domain
Setting Up Security with SNA Server	7 of 9

Increasing the Security of SNA Servers in a Domain

The security of SNA servers is built on the same foundation as the security in a Windows NT domain. When you use SNA Server Admin to configure permissions and auditing, your settings are implemented through Windows NT mechanisms.

For background information about security in a Windows NT domain, see the previous sections as well as your Windows NT documentation, which discusses important basic concepts such as domains, user accounts, logon, user rights, and permissions.

When SNA Server is first installed, it provides a base of functionality and security upon which you can place added restrictions. This functionality and security center around the SNA Server configuration file, which contains the information that allows users to connect to SNA resources. The configuration file must be shared between SNA servers in order for the servers to work together correctly.

Important

To increase security on an SNA server, use the dialog boxes in SNA Server Admin and/or the procedures in this chapter. Do not use administrative tools such as File Manager to place limited permissions on the SNA Server configuration file, or you may block the access that SNA servers require when working across the network.

The following sections describe:

The added security available with the Windows NT file system (NTFS), and the security advantage of installing SNA Server on an NTFS partition.

What resources can be secured through commands on the Security menu in SNA Server Admin.

The steps for using SNA Server Admin to increase security on an SNA server.

The steps for setting up auditing of SNA Server security events, and the steps for viewing these events.

How to configure a basic level of security on servers on which SNA Server is not installed on an NTFS partition.


File System Choices and Security
Setting Up Security with SNA Server	8 of 9

Increasing the Security of SNA Servers in a Domain

File System Choices and Security

One of the key elements to control when establishing security on SNA servers is the SNA Server configuration file. To maintain good security with this file, be sure to install the SNA Server software on an NTFS partition. With NTFS, permissions can be assigned on a file-by-file basis; with the FAT file system or HPFS, this is not possible. Installing the SNA Server software on an NTFS partition is especially important with the primary SNA server, the server that contains the main copy of the configuration file (used by all SNA servers in the domain).

If you choose to install the software for one or more SNA servers on a FAT or HPFS partition (not an NTFS partition), you can still use the Security menu and the security dialog boxes in SNA Server Admin. In this case, SNA Server will not be able to set permissions on the configuration file itself; however, SNA Server will be able to limit access to administration programs that can view or change the file.

In addition, if you choose to install the software for one or more SNA servers on a FAT or HPFS partition, you can set appropriate Read and Change permissions on the share which gives SNA servers access to the configuration file. (This is unnecessary for SNA Server software installed on an NTFS partition, because file permissions established through SNA Server Admin place tighter control on the configuration file than can be established by controlling the share.) For information about how to place such permissions on the share, see: "Setting Permissions for the COMCFG Share," later in this chapter.


Resources to Consider When Establishing Security
Setting Up Security with SNA Server	9 of 9

Increasing the Security of SNA Servers in a Domain

Resources to Consider When Establishing Security

There are a number of resources to consider when establishing security on a set of SNA servers. These resources include those on the server itself — hardware, operating system, and the tools and commands by which security is implemented and changed.

Note

Security established through SNA Server Admin cannot replace basic security on the server itself, such as the security of the server's hardware and operating system. For information about basic security issues, see your Windows NT documentation.

Once you have implemented basic security for servers on which you run SNA Server software, you can use SNA Server Admin to supplement this security. If SNA Server has been installed on an NTFS partition, SNA Server Admin allows you to establish tighter control over the following:

\SNAroot\SYSTEM\CONFIG\COM.CFG

The SNA Server configuration file. The configuration file contains important SNA access information, such as the names of SNA users and groups and the LUs or LU pools they're allowed to use. You can limit access to the configuration file (through settings in SNA Server Admin) only if SNA Server has been installed on an NTFS partition.

The configuration file is created by SNA Server Setup on primary and backup SNA servers, but not on member SNA servers. Setup also shares the configuration file, so that all SNA servers (primary, member, and backup) can work together.

SNAADMIN.EXE and SNACFG.EXE

The SNA Server Admin program and the SNA Server command-line configuration program. Both programs can be used to display or change the configuration file. The SNA Server Admin program can also be used to start and stop SNA servers and connections.

The fact that SNA Server configuration information is stored in a file has advantages (the file can be copied, stored, and moved like any other file) and disadvantages (the file can be damaged or tampered with, if not protected). However, the security tools in SNA Server Admin have been designed to allow you to protect the file and also prevent unwanted use of SNA Server Admin and SNACFG.EXE, the tools that can change the file.

There is one additional category of resources to be aware of when considering security: the services that make up SNA Server. These services include SnaBase, SnaServer, SnaNetMn, and link services. The best way to protect such services is to protect the basic resources of the server itself: the hardware, the operating system, and administrative tools such as Server Manager. For information, see your Windows NT documentation.

Steps for Increasing Security on SNA Servers

To increase security on SNA servers that work together in a domain, take the following steps on each SNA server. Steps 4 through 6 are described in more detail in the sections that follow. All the steps require that you be logged on as an administrator in the domain — that is, that your user account be listed as a member of the Administrators group in the domain.

1.	Carry out an appropriate plan to secure the servers in your Windows NT domain; the plan should include measures regarding physical access to the servers as well as access to administrative software, such as User Manager and Server Manager.

2.	If possible, install the SNA Server software for each server on an NTFS partition.

3.	Configure SNA Server Admin to allow the appropriate access for users who use LUs. For more information, see the chapter that describes the type of LU you need.

4.	Use SNA Server Admin to limit administrative permissions for SNA Server.

This allows you to control who can access the configuration file (if SNA Server is installed on an NTFS partition) and/or run SNA Server administration programs. SNA Server administration programs have the power to change the SNA Server configuration and to start and stop SNA servers, connections, and other services. For more information about limiting administrative permissions, see the next section.

5.	As needed, use User Manager and SNA Server Admin to enable auditing for SNA Server.

This allows you  to specify events for which the system will create event log entries. For example, you can cause the system to create an entry every time the configuration file is changed by a member of the Administrators group. The entry would include the time, the user and process IDs, and other information. For more details, see: "Setting Up Auditing of Access to the Configuration File" and "Viewing and Interpreting SNA Server Events," later in this chapter.

6.	If the software for an SNA server is not on an NTFS partition, set appropriate Read and Change permissions on the share which gives SNA servers access to the configuration file. (This is unnecessary for SNA Server software installed on an NTFS partition.) For more information, see: "Setting Permissions for the COMCFG Share," later in this chapter.

Specifying Administrative Permissions on SNA Servers

The procedures in this section correspond to step 4 in the list under: "Steps for Increasing Security on SNA Servers."

SNA Server Admin offers specific types of permissions for administrative access in SNA Server. When you set the permissions for a particular group or user, you control that group's or user's access to the configuration file, to SNA Server Admin, and to the command-line configuration utility, SNACFG.EXE. You control this access for each user or group from one dialog box.

The following list gives details about the administrative permissions offered in SNA Server Admin. When you assign these permissions, they are implemented through mechanisms in Windows NT.

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 the configuration file. The user or group cannot write to the configuration file.

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.

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.

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.

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; and can change the administrative permissions assigned to other users and groups.

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.

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.

To add groups and users to the list of those with SNA Server administrative permissions

1.	Start SNA Server Admin.

2.	From the Security menu, choose Permissions.

The SNA Domain Permissions dialog box appears.

Figure 12.2    SNA Domain Permissions Dialog Box

3.	Choose the Add button.

The dialog box shown in Figure 12.3 appears.

Figure 12.3    Add Users and Groups Dialog Box

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

5.	If you want the accounts displayed to include users as well as groups, choose the Show Users button.

6.	If you want to search for a particular user or group, follow the instructions under "To search for a user or group," later in this section.

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

8.	Choose the Add button.

The selected group or user name(s) appear in the Add Names box.

9.	Repeat steps 8 and 9 as needed.

10.	In the Type of Access box, select the permission that you want the listed user(s) or group(s) to have. For descriptions of the permissions, see the list under: "Specifying Administrative Permissions on SNA Servers," earlier in this chapter.

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.

11.	Choose OK.

To change the administrative permissions currently assigned to groups and users

1.	In SNA Server Admin, from the Security menu, choose Permissions.

The SNA Domain Permissions dialog box, shown in Figure 12.2, appears.

2.	Under Name, select a group or user for whom you want to change administrative permissions.

If the user or group you are seeking is not currently listed under Name, see the previous procedure.

3.	In the Type of Access box, select the permission that you want the selected user or group to have. For descriptions of the permissions, see the list under: "Specifying Administrative Permissions on SNA Servers," earlier in this chapter.

The permission listed under Name changes to match the permission selected in the Type of Access box.

4.	Choose OK.

To search for a user or group

1.	Start SNA Server Admin.

2.	From the Security menu, choose Permissions.

The SNA Domain Permissions dialog box, shown in Figure 12.2, appears.

3.	Choose the Add button.

The Add Users and Groups dialog box, shown in Figure 12.3, appears.

4.	If you want to search for users from another domain, in the List Names from box, select a different domain.

The domains listed are trusted domains.

5.	Choose the Search button.

The Find Account dialog box appears.

6.	In the Find User or Group box, type the name of the user or group you want to search for.

7.	Select Search All, or select Search Only In and select a domain in which to search.

8.	Choose the Search button.

The results appear under Search Results.

9.	Repeat steps 5 through 8 as needed.

10.	To add the results of the search(es) to the list of those with specific administrative permissions, select one or more users or groups, and then choose the Add button.

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 avoid adding any search results to the list of users and groups with specific administrative permissions, choose the Cancel button.

The Add Users and Groups dialog box reappears, with any user or group additions listed in the Add Names box.

11.	Carry out other actions in the Add Users and Groups dialog box as described in other procedures in this section.

Denying Administrative Permission on SNA Servers

To deny a user or group the ability to use SNA Server administration programs and access the configuration file, use one of two methods. Either remove the user or group from the list of those who have permissions granted, or assign No Access to the user or group.

When removing a user or group from the list of those who have permissions granted, be sure to consider all groups to which a particular user belongs. To deny access to that user, either remove the applicable groups from the list of those with permissions, or remove the user account from these groups. Otherwise, the user can receive access through one of the groups (unless the second method, assigning No Access, is used).

You can deny all access to a user or group by assigning No Access because No Access overrides any other permissions that may apply to a 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. Likewise, if a user belongs to Group1 and Group2, and Group1 has Read permission while Group2 has No Access, the user is not permitted administrative access.

The following table provides recommendations for using the two methods of denying access.

Method of denying access		Recommended situations for use
Remove from list of those granted permissions		Use when you want to deny access to a medium or large group. If you then want to grant access to specific users in that group, add these users to the list of those with permissions. In contrast, if you assign No Access to a large group, none of the members of the group will be allowed access, even if explicit access is assigned to them through other accounts.
Assign No Access		Use when you want to deny access to an individual user or a small group. If you then want to grant access to other groups to which the affected user(s) belong, you can do so; the No Access permission will override the other permissions for the affected user(s). In contrast, if you attempt to deny an individual user access by removing the user from the list of those granted permissions, a group to which the user belongs might be left in the list; the permissions assigned to that group would be given to the user.
To remove users or groups from the list of those having specific administrative permissions in SNA Server

1.	In SNA Server Admin, from the Security menu, choose Permissions.

The SNA Domain Permissions dialog box, shown in Figure 12.2, appears.

2.	Under Name, select the user or group that you want to remove from those granted administrative permissions in SNA Server.

3.	Choose the Remove button.

The name is removed from the list under Name.

4.	Choose OK.

To assign a user No Access permission for SNA Server administration

1.	To add the user to the list of those whose permissions are specified, follow the instructions under "To add groups and users to the list of those with SNA Server administrative permissions," earlier in this chapter.

2.	To change the user's permission, in the SNA Domain Permissions dialog box, shown in Figure 12.2, select the user or group name and then, under Type of Access, select No Access.

The permission listed under Name changes to No Access.

Specifying the Owner of Administrative Access to SNA Servers

One account is designated as the owner of the ability to administer SNA Server. By default, the Administrator account has this owner status. When you are logged on in an account with Full Control (or with the special permission of Change Owner), you can take ownership. If you take ownership while logged on in an account that is a member of the Administrators group , the ownership will pass to the Administrators group, not an individual user account.

Important

The owner can always change his or her administrative permission, no matter what permission was previously set for the owner. This means that the owner always has, or can get, administrative permission of Full Control. In effect, the owner has (or can get) greater permissions than anyone else.

If there is ever a situation where administrative permissions have been limited too severely in SNA Server Admin, the owner can change his or her permission to Full Control (if necessary) and then reinstate other permissions.

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.

The recommended method for ensuring successful transfer of ownership is to take ownership through the Administrators group, which exists on all Windows NTbased servers. To do this, take ownership while logged on in an account that is a member of the Administrators group.

For more information about the concept of ownership, see your Windows NT documentation.

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

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

When you set up auditing, you specify events for which the system will create event log entries. For example, you can cause the system to create an entry every time the configuration file is changed by a member of the Administrators group. The entry would include the time, the user and process IDs, and other information. For important information about viewing event log entries, see the next section.

When you set up auditing with SNA Server, the events audited include not only access to the configuration file, but the running of SNA Server processes. However, using a file system other than NTFS limits the possibilities for auditing, just as it limits the possibilities for setting permissions. When SNA Server is not installed on NTFS, the only event that will actually result in log entries is the starting of SNA Server Admin. (However, auditing information for this event is useful, if limited.) For more information about how NTFS enhances security with SNA Server, see: "File System Choices and Security," earlier in this chapter.

Auditing is an important way of collecting security-related information. However, there is some small performance overhead for each audit check the system performs. In addition, if a wide variety of events is recorded, the event log can get large very quickly. For these reasons, you may want to be selective when specifying events to be audited. Events you may want to focus on include Read Domain (Success), Write Domain (Success), and Manage Domain (Success). (This list of events is a suggestion only; all the events offered for auditing through SNA Server can be useful, depending on the situation.)

Among the events recorded when auditing is enabled in SNA Server Admin are the actions of SNA Server itself. For important information about this, see the note in the next section.

For more information about events logs, the Event Viewer, and strategies for 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.	Choose the Add button.

The Add Users and Groups dialog box, similar to the one shown in Figure 12.3, appears.

5.	If you want the accounts displayed to include users as well as groups, choose the Show Users button.

6.	If you want to search for a particular user or group, follow the instructions under "To search for a user or group," earlier in this section.

7.	Under Names, select one or more groups or users whose actions you want to audit:

To audit actions carried out by any user (rather than the actions of a specific group), select the group called Everyone.

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.

8.	Choose the Add button.

The selected group or user name(s) appear in the Add Names box.

9.	Repeat steps 8 and 9 as needed.

10.	Choose the OK button.

The SNA Domain Auditing dialog box reappears, with a list under Name, showing the users and groups for whom you can specify actions to be audited.

11.	Under Name, select a user or group.

12.	Under Events to Audit, select the events you want to audit for that user or group.

13.	Repeat steps 12 and 13 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.

14.	Choose OK.

Viewing and Interpreting SNA Server Events

Events generated through auditing that was configured in SNA Server Admin are stored on the server on which they occur. (They are not stored centrally, in contrast with the other events generated through SNA Server.) The events generated through auditing are stored in the security section of the event log. In contrast, other events generated through SNA Server are stored in the application section of the log; for information about these events, see: Chapter 13, "Using Diagnostic Tools."

To view events generated through SNA Server auditing

1.	Start the Event Viewer (usually located in the Administrative Tools group within Program Manager).

2.	From the Log menu, choose Select Computer.

The Select Computer dialog box appears.

3.	To select the SNA server on which you want to view events, type the name in the Computer box or, under Select Computer, select the intended server.

4.	Choose OK.

5.	From the Log menu, choose Security.

A list appears, showing events generated through auditing of resources (of all types) on the Windows NT-based server.

6.	To see detail about a particular event, double-click on the event.

The Event Detail dialog box appears. From inside this dialog box, you can view details about other events by choosing the Previous button or the Next button.

Note

When you view log entries for audited events related to SNA Server, you will see records of actions carried out by SNA Server itself, as well as actions carried out by users. The source of the actions carried out by SNA Server will be listed as "ANONYMOUS." Read access through "ANONYMOUS" is necessary and normal for the functioning of SNA Server.

In the event details for some events, an item called Accesses will be listed (in the Description box). Unusual information may be shown here for events related to SNA Server; use the following table for interpreting this information.

Information shown for Accesses (under Description)	Meaning
Unknown specific access (bit 0)	Read Domain access. This access applies when someone starts or attempts to start SNA Server Admin. (SNA Server Admin must read the configuration file in order to function.)
Unknown specific access (bit 1)	Write Domain access. This access applies when someone starts SNA Server Admin in write mode — that is, when someone starts SNA Server Admin and the primary SNA server is available.
Unknown specific access (bit 2)	Manage Domain access. This access applies when someone starts or attempts to start SNA Server Admin.
Setting Permissions for the COMCFG Share

If you choose to install the software for one or more SNA servers on a FAT or HPFS partition, you can set appropriate Read and Change permissions on the share which gives SNA servers access to the configuration file. (This is unnecessary for SNA Server software installed on an NTFS partition, because file permissions established through SNA Server Admin place tighter control on the configuration file than can be established by controlling the share.)

The following procedure corresponds to step 6 in the list under: "Steps for Increasing Security on SNA Servers."

To set permissions for the \\servername\COMCFG share when SNA Server software is not installed on NTFS

1.	On a server in the domain containing the SNA servers, start Server Manager (found in the Administrative Tools group).

2.	Select an SNA server from the list in the Server Manager window and then, from the Computer menu, choose Shared Directories.

The Shared Directories dialog box appears.

3.	In the Shared Directories dialog box, under Shared Directories on \\servername, select COMCFG.

This is the share that is created by SNA Server Setup to allow SNA servers the necessary network access to the configuration file.

4.	Choose the Properties button.

The Share Properties dialog box appears.

5.	Choose the Permissions button.

The Access Through Share Permissions dialog box appears.

6.	Choose the Add button.

The Add Users and Groups dialog box, shown in Figure 12.3, appears.

7.	If you want the accounts displayed to include users as well as groups, choose the Show Users button.

8.	From the Names list, select a user or group for whom you want to set permissions.

Note

With shares, such as the COMCFG share, it is usually better to assign permissions to groups rather than to individual users. For information about users and groups, see your Windows NT documentation.

9.	Choose the Add button.

10.	From the list in the Type of Access box, select the appropriate access:

Read

Select this type of access for users or groups who are to manage SNA Server (start and stop SNA Server services), but not change the SNA Server configuration.

Change

Select this type of access for users or groups who are to manage SNA Server (start and stop SNA Server services), and also change the SNA Server configuration.

Full Control

Select this type of access for users 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.

11.	Choose OK.

The Access Through Share Permissions dialog box reappears, allowing you to view the permissions currently set for the COMCFG share.

12.	Repeat steps 6 through 11 until you have added all users and/or groups to whom you want to give access to the configuration file used by SNA Server.

Note

It is recommended that you select Full Control for at least one user or group, preferably a trusted group such as Administrators. If no user or group has Full Control, the only person who can change the share permissions is the owner of the share, who can always change his or her own permissions to Full Control, as needed.

13.	Under Name, select the group called Everyone.

14.	Under Type of Access, select Read.

This permission is necessary for the group called Everyone; it allows SNA servers to work together across the network.

15.	If you want to remove any group or user currently listed in the Access Through Share Permissions dialog box, select the user or group, and then choose the Remove button.

Important

Do not remove the group called Everyone, nor assign this group No Access. A minimum permission of Read is required for Everyone, so that SNA servers can work together. SNA servers need to read the COMCFG share, and the SNA Server configuration file inside it, in order to function.

16.	If you want to change the access for any group or user currently listed in the Access Through Share Permissions dialog box, select the appropriate user or group, and then change the permission listed in the Type of Access box.

17.	Choose OK.

18.	Choose OK.

19.	Choose Close.

20.	Repeat this procedure for each of the primary and backup SNA servers in the domain.


Using Diagnostic Tools
Chapter 13	1 of 12

Using Diagnostic Tools

A variety of different diagnostic tools can be used with SNA Server. These 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, which includes the number of active users and the number of 3270, APPC, and LUA sessions. For information, see the next section.

The status of connections. For information, see the next section.

The status of LUs, which includes the name 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. For information, see the next section.

Data from NetView [image], which is a reporting system that runs on an IBM host (mainframe), forwarding alerts that help an SNA administrator manage operations, diagnose problems, and improve system performance. For information, see: "Configuring for NetView" later in this chapter.

Windows NT event logs for application events. These logs contain records of events on the SNA network and can be viewed using the Windows NT Event Viewer. For information, see: "Using Event Logs" later in this chapter.

For information about events recorded in the security log for SNA Server, see: Chapter 12, "Setting Up Security with SNA Server."

RTM data, available via 3270 emulators that are capable of receiving the data. RTM is a 3270 and NetView facility that monitors the amount of time it takes for a host to respond during 3270 display sessions. For information, see: "Configuring RTM Settings" later in this chapter.

Performance Monitor counters. The Performance Monitor is a graphical tool included in Windows NT. It allows you to monitor system performance.

Trace files, which contain 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. If you seek product support, the support technician may work with you to collect trace file information. For information, see: "Collecting Traces and Other Detailed System Information" later in this chapter.

The following table tells where to find information that may be useful when examining specific configurations:

Topic		Where to find additional information
VTAM or NCP		Chapter 5, "Working with Settings in VTAM and NCP"
AS/400 configuration		Chapter 7, "Configuring for 5250 Emulation in the AS/400 Environment"
Modem		Appendix A, "Guidelines for Specific Configurations"
Registry and environment variables		Microsoft SNA Server Reference
Background information about SNA		Microsoft SNA Server Reference


Viewing the Status of Servers, Connections, and LUs
Using Diagnostic Tools	2 of 12

Viewing the Status of Servers, Connections, and LUs

When there appears to be a difficulty with a service, and you are making a decision about starting, stopping, resetting, or modifying the service, it may be helpful to gather status information. For example, for a difficulty with a server, it may be helpful to know how many APPC sessions are currently active on the server.

To view the status of an SNA server

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

2.	From the Services menu, choose Properties.

The Server Properties dialog box appears, showing the server's status: Active, Inactive, Pending, Stopping, Active [Out of Date], or Error. The Active [Out of Date] status indicates that the SNA server needs to be restarted, to bring internal parameters up-to-date with the latest configuration changes. The Error status indicates that an unexpected condition has made the SNA server inaccessible to SNA Server Admin.

The dialog box also shows the version number, as well as the number of each of the following: active users, 3270 sessions, APPC sessions, and LUA sessions. If the server is active, the number of licensed users and licensed sessions is also shown.

3.	When you are finished viewing the status, choose the Cancel button.

To view the status of a connection

In the Servers and Connections window, view the connection status displayed to the right of the connection name.

For connections other than those configured as On Demand or Inactive, the connection status can be Active, Pending, Stopping, or Inactive. On Demand connections can have all of those statuses plus On Demand (available to be started when needed). Incoming connections can have all of those statuses plus Incoming (available to receive incoming calls).

For information about changing the status of a connection, see: Chapter 11, "Managing SNA Server."

To view the status of an LU other than an APPC LU

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

Status possibilities for LUs other than APPC LUs are Inactive, In Session, SSCP, Available, or Pending; a downstream LU can also have a status of Unavailable. The SSCP status indicates that the LU is in use but is not yet bound to a specific host application. The Available status indicates that the LU is recognized by the host as an available LU. The Pending status indicates that a user is trying to access the LU, but either the connection is inactive, or the host does not recognize the LU.

To view the status of an APPC LU-LU pair

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

2.	From the Services menu, choose Properties.

The APPC LU Properties dialog box appears.

3.	Choose the Status button.

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 the Zoom button.

A second APPC LU Status dialog box appears, showing the user, computer, and executable using the session, as well as the time that the session started.

5.	When you are finished viewing the status, choose the Close button or the Cancel button until the dialog boxes have all been closed.

To view the 3270 LUs being used by an active user

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.


Configuring for NetView
Using Diagnostic Tools	3 of 12

Configuring for NetView

NetView sends alerts back and forth between a host system and PCs. You can specify connection through which NetView alerts should be sent. This can be any host connection except a DFT connection.

NetView functionality can also be extended with the use of the NVAlert and NVRunCmd services. For information, see: Appendix C, "SNA Server NetView Extensions."

To specify the connection to which NetView data should be sent

1.	From the Options menu, choose NetView.

The NetView Options dialog box appears.

2.	In the Send NetView Management Data to Connection box, select a connection.

This can be any host connection except a DFT connection.

3.	Choose the OK button.


Using Event Logs
Using Diagnostic Tools	4 of 12

Using Event Logs

You can use information from Windows NT event logs as you test a configuration or diagnose problems. Event logs can tell you the sequence and type of events that led up to a particular state or situation.

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 later in this chapter.

For details about other kinds of diagnostic information available for SNA Server, see: "Collecting Traces and Other Detailed System Information" later in this chapter.

An event log differs from a security log, which records actions related to security, such as reading from or writing to the SNA Server configuration file. For information about events recorded in the security log, see: Chapter 12, "Setting Up Security with SNA Server."

You can specify the following parameters for event logs:

The server on which event logs will be stored.

The types of events to record in logs: all events that can be recorded, general-activity events, or significant system events.

A server to which pop-up error messages should be routed, in addition to appearing on the local server. These messages include warnings and errors related to activity on the SNA network. The routed messages do not include messages about an invalid parameter having been typed, or other SNA Server Admin messages.

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.

To store the event logs for this server on this server, select [Local System].

3.	Under Default Audit Log Level, select a level:

Detailed problem analysis:  To record all events that can be recorded, select this option button.

 General information messages: To record general activity but not all events, select this option button.

Significant system events: To record only major events, select this option button.

Audit logging disabled: To turn off audit logging, select this option button.

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.

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

To have pop-up messages for this server display only on this server, select [Local System].

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

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.

3.	Under the Source heading, find events that have names starting with "SNA."

4.	To view more detail about an event, select the event and, from the View menu, choose Detail.

If you want to copy an event log, the log files are located in WindowsRoot\SYSTEM32\CONFIG, and have a filename extension of EVT.


Configuring RTM Settings
Using Diagnostic Tools	5 of 12

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.

To configure 3270 RTM settings

1.	From the Options menu, choose RTM Triggers.

The 3270 Response Time Monitor (RTM) dialog box appears.

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 check 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 check 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 at the moment when the local system sends data.) The possible stopping points are as follows:

First Data Reaches Screen: To stop timing when data reaches the local screen, select this option button.

Host Unlocks Keyboard: To stop timing when the host unlocks the local keyboard, select this option button.

Host Lets User Send: To stop timing when the host lets the local computer send more data, select this option button.

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.

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

Note

If the host RTM settings are different, they can override the SNA Server settings.

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


Performance Monitor Options for SNA Server
Using Diagnostic Tools	6 of 12

Performance Monitor Options for SNA Server

The Performance Monitor is 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. The following table shows the SNA Server counters that you can measure with the Performance Monitor. Before any SNA Server counters can be measured, one or more SNA servers must be 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.


Collecting Traces and Other Detailed System Information
Using Diagnostic Tools	7 of 12

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. SNA tracing is the action of recording activity between or within components of SNA Server. On an SNA server or Windows NT-based client, tracing is turned on with the snatrace utility. On other clients, tracing is turned on with special commands or with lines in an initialization file. For information about tracing, see the next section.

Windows NT event logs, which record system and application events, including errors. For information about event logs, see: "Using Event Logs" earlier in this chapter.

The current configuration file. For information about configuration files, see: "Working with Configuration Files" in Chapter 11.

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 more information about filenames for trace files created by the snatrace utility, see: "Files Created by the Snatrace Utility" later in this chapter.

For information about specifying the names of trace files on clients running Windows [image] version 3.x, MS-DOS [image], or OS/2 [image], see the sections on tracing for these clients later in this chapter.


Trace Files
Using Diagnostic Tools	8 of 12

Collecting Traces and Other Detailed System Information

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 information about event logs, see: "Using Event Logs" earlier in this chapter.


Tracing on SNA Servers or Windows NT-Based Clients
Using Diagnostic Tools	9 of 12

Collecting Traces and Other Detailed System Information

Tracing on SNA Servers or Windows NT-Based Clients

The following sections tell how to set up tracing on an SNA server or Windows NT-based client. For information about tracing on other types of clients, see: "Tracing on Clients Running Windows Version 3.x," "Tracing onMS-DOS – Based Clients," or "Tracing on OS/2-Based Clients" later in this chapter.

Types of Tracing for SNA Servers or Windows NT-Based Clients

Before setting up tracing, decide which software component(s) you want to trace. Trace files can record internal or external activity for the following software components:

SNA Applications.

SnaServer (PU 2.1 node), the component of SNA Server that interacts with clients and with other nodes on the SNA network.

SnaBase, the component of SNA Server that maintains lists of service names and statuses.

Link Services that have been installed with Setup.

When you decide which software component to trace, you will also need to decide which type of tracing to apply to that component. Table 13.1 describes the types of tracing available for an SNA server or a Windows NT-based client, and shows what each type applies to.

Table 13.1    Types of Tracing

Type of tracing		Activity traced	Applies to
Internal*		Activity within a software component of SNA Server	SnaBase, SnaServer (PU 2.1 node), SNA Applications, link services
Message		Messages passed into and out of a software component of SNA Server, including messages sent to and received from the SNA network	SnaBase, SnaServer (PU 2.1 node), SNA Applications, link services
API		Information passed into and out of an SNA Server DLL, such as the APPC DLL, as the DLL communicates with an application	SNA Applications
*  Internal tracing is intended for the use of product support technicians. Interpreting internal traces and certain types of message traces requires a specialized knowledge base.

Table 13.2 shows the information needed for interpreting each type of tracing.

Table 13.2    Information Needed for Interpreting Tracing

Type of tracing		Software component traced		Area of expertise needed		Information source for interpretation
APPC API		SNA Applications		APPC programming		Microsoft SNA Server APPC Programmer's Guide
CPI-C API		SNA Applications		CPI-C programming		Microsoft SNA Server CPI-C Programmer's Guide
LUA API		SNA Applications		LUA programming		Microsoft SNA Server LUA Programmer's Guide
SNA Formats		SnaServer (PU 2.1 Node)		SNA formats		IBM SNA: Formats
Data Link Control (messages)		SnaServer (PU 2.1 Node) or link service		DLC interface		SNA Device Interface Specification
Level 2 Messages		Link service		Link service interface		The interface specification for the link service
3270 Messages		SNA Applications, SnaServer (PU 2.1 Node), or SnaBase		3270 emulator interface		3270 Emulator Interface Specification
Admin Messages		All software components for SNA Server		Intended for product support personnel		Product support technician
LU 6.2 Messages		SNA Applications, SnaServer (PU 2.1 Node), or SnaBase		Intended for product support personnel		Product support technician
Internal		All software components for SNA Server		Intended for product support personnel		Product support technician
Table 13.3 provides examples of possible difficulties and the types of tracing that may be useful.

Table 13.3    Examples of Tracing for SNA Servers and Windows NT-Based Clients

Difficulty		What to trace
SNA Server can't connect to host		For the SnaServer (PU 2.1 node), traceData Link Control and 3270 Messages
SNA Server Admin doesn't reflect changes in network services		For the SnaServer (PU 2.1 node), trace Admin Messages; for SNA Server Admin, enable internal tracing
Windows NT-based client can't connect to an SNA resource		On any client: enable internal tracing On a 3270 or LUA client: For SNA Applications, trace 3270 messages On an APPC or CPI-C client: For SNA Applications, trace LU 6.2 messages

Table 13.3 shows examples of tracing for SNA servers or Windows NT-based clients. For information about tracing on other types of clients, see: "Tracing on Clients Running Windows Version 3.x," "Tracing on MS-DOS – based Clients," or "Tracing on OS/2-based Clients" later in this chapter.

Starting the Snatrace Utility

After you have decided which software component(s) and which type(s) of tracing can provide you with useful information, you can start the snatrace utility and configure trace options on an SNA server or a Windows NT-based client. The snatrace utility can be started locally or remotely for an SNA server. (For a Windows NT-based client, the snatrace utility can only be started locally.)

For information about tracing on other types of clients, see: "Tracing on Clients Running Windows Version 3.x," "Tracing on MS-DOS – based Clients," or "Tracing on OS/2-based Clients" later in this chapter.

To start the snatrace utility locally or remotely through SNA Server Admin on a server

1.	On an SNA server, start SNA Server Admin.

2.	In the Servers and Connections window, select the server that you want traces for.

3.	From the Services menu, choose Properties.

The Server Properties dialog box appears.

4.	Choose the Addons button.

The SNA Server Additions dialog box appears.

5.	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 configure trace options, see the next section.

To start the snatrace utility remotely using the command line on a server

1.	On an SNA server, switch to a command prompt.

2.	At the command prompt, type

snatrace \\servername

The SNA Server Trace Options dialog box appears, with the name of the affected server in the title bar. To configure trace options, see the next section.

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. To configure trace options, see the next section.

Enabling or Disabling Trace Options

After you start the snatrace utility on an SNA server or Windows NT-based client, you can use it to enable or disable trace options.

To enable or disable trace options with the snatrace utility

1.	Start the snatrace utility as described in the preceding section.

The SNA Server Trace Options dialog box appears.

2.	In the Service Name box, select a name from the list:

Service name		Kind of activity traced
SNA Applications		Activity generated by applications that use SNA APIs
SNA Server Admin		Activity generated by the SNA Server Admin interface
SnaBase		Activity generated by the SNA base, which maintains lists of service names and statuses
SnaServer		Activity generated as the local SNA server (PU 2.1 node) interacts with clients and other nodes on the SNA network
Name of link service(s) specified during setup		Activity between a link service and other software components
3.	Under Internal Tracing, drag the scroll box to the desired level of internal tracing for the selected service.

Internal tracing is intended for the use of product support technicians. Interpreting internal traces requires a specialized knowledge base. If a product support technician requests internal tracing, the level needed is generally Full Tracing.

Disabling internal tracing does not disable other trace options. For a description of internal tracing, see: "Types of Tracing for SNA Servers or Windows NT-Based Clients" earlier in this chapter.

4.	If available for the selected service, select options for message tracing:

To enable or modify message tracing, specify trace options according to the tables in the next section.

To disable message tracing, or to clear existing options from the dialog box, choose the Clear button.

For a description of message tracing, see: "Types of Tracing for SNA Servers or Windows NT-Based Clients" earlier in this chapter. For tables showing the effect of message tracing for different Service Names, see the next section.

5.	If the selected service is SNA Applications, select options for API tracing:

To enable or modify API tracing, specify trace options according to the tables in the next section.

To disable API tracing, or to clear existing options from the dialog box, choose the Clear button.

For a description of API tracing, see: "Types of Tracing for SNA Servers or Windows NT-Based Clients" earlier in this chapter. For tables showing the effect of API tracing, see the next section.

6.	Select or clear the Minimize Disk Access by Buffering Writes check box:

To minimize the writing of trace information to disk, and instead cause the information to be held in a memory buffer until it is efficient to write it to disk, select this box. This avoids unnecessary slowing of the system, but does not protect trace information from being lost if the system goes down.

To cause trace information to be written to disk as soon as it is generated, clear this box. This slows the system, but ensures that trace information is not lost if the system goes down.

7.	Repeat steps 2 – 6 for each service that you want to trace.

8.	Choose the OK button.

As trace files are created, they are stored in the TRACES subdirectory of the SNA Server root directory, with a filename extension of .TRC.

Files Created by the Snatrace Utility

The snatrace utility places trace files in the SnaRoot\TRACES subdirectory (where SnaRoot is the SNA Server root directory). The following table lists the filenames used by snatrace:

Service	Type of tracing	Filenames used
SNA Applications	Client API	API1.TRC	API2.TRC
	Internal	CLIENT1.TRC	CLIENT2.TRC
	Message	CLIMSG1.TRC	CLIMSG2.TRC
SNA Server Admin	Internal	CLIENT1.TRC	CLIENT2.TRC
SnaServer (PU 2.1 Node)	Internal	NODEINT1.TRC	NODEINT2.TRC
	Message	NODEMSG1.TRC	NODEMSG2.TRC
SnaBase	Internal	NAPINT1.TRC	NAPINT2.TRC
	Message	NAPMSG1.TRC	NAPMSG2.TRC
Link service	Internal	LINKINT1.TRC	LINKINT2.TRC
	Message	LINKMSG1.TRC	LINKMSG2.TRC
Available Trace Options for SNA Server and Windows NTBased Clients

The following tables describe the specific kinds of traces available for each service that can be traced: SNA Applications, SnaServer, SnaBase, and link services.

Table 13.4    SNA Applications Trace Options: Message Traces

Trace option	Activity traced for SNA Applications on the local system

Admin Messages	Messages between SNA Server Admin (considered as an "application"), and SnaBase and SnaServer (PU 2.1 node)

3270 Messages	Messages between 3270 applications (3270 emulators and/or LUA programs) on the local system and the SnaServer (PU 2.1 node)

LU 6.2 Messages	Messages between the APPC DLL on the local system and the SnaServer (PU 2.1 node)

Table 13.5    SNA Applications Trace Options: Client API Tracing

Trace option	Activity traced for SNA Applications

APPC API	Activity between APPC applications and the APPC DLL on the SNA server

CPI-C API	Activity between CPI-C applications and the CPI-C DLL on the SNA server

LUA API	Activity between LUA applications and the LUA DLL on the SNA server

CSV API	Activity between CSV applications and the CSV DLL on the SNA server

Table 13.6    SnaBase Trace Options

Trace option	Activity traced for SnaBase

Admin Messages	Messages between the SnaBase software, which maintains lists of service names and statuses, and SNA Server Admin

3270 Messages	Messages between the SnaBase software, which maintains lists of service names and statuses, and 3270 applications (3270 emulators and/or LUA programs)

LU 6.2 Messages	Messages between the SnaBase software, which maintains lists of service names and statuses, and the APPC DLL

Table 13.7    SnaServer (PU 2.1 Node) Trace Options

Trace option	Activity traced for the SnaServer (PU 2.1 node)

Admin Messages	Messages between the SnaServer (PU 2.1 node) and SNA Server Admin.

3270 Messages	Messages between the SnaServer (PU 2.1 node) and all 3270 clients (3270 emulators and/or LUA programs).

Data Link Control	Messages between the SnaServer (PU 2.1 node) and link services.

SNA Formats	Data link control messages that are in SNA formats. Such messages require a knowledge of SNA formats and protocols in order to be understood.

LU 6.2 Messages	Messages between the SnaServer (PU 2.1 node) and the APPC DLL.

Table 13.8    Link Service Trace Options

Trace option	Activity traced for the link service

Admin Messages	Messages between the link service and SNA Server Admin

Data Link Control	Activity between the link service and SnaServer (PU 2.1 node)

Level 2 Messages	Information related to Level 2 in the international standards organization (ISO) model


Tracing on Clients Running Windows Version 3.x
Using Diagnostic Tools	10 of 12

Collecting Traces and Other Detailed System Information

Tracing on Clients Running Windows Version 3.x

The following sections describe tracing on clients running Windows version 3.x. For general information about tracing, see: "Collecting Traces and Other Detailed System Information" and "Trace Files" earlier in this chapter. For information about tracing on other types of clients, see "Tracing on SNA Servers or Windows NT-Based Clients" earlier in this chapter, or "Tracing on MS-DOS – Based Clients" or "Tracing on OS/2-Based Clients" later in this chapter.

Using tracing on SNA Server clients running Windows version 3.x is similar to using tracing on an SNA server, except that:

Tracing on a client provides information about activity on the client only, not activity on the SNA server.

The software components that can be traced on an SNA Server client running Windows version 3.x are SNA applications (specifically, the APIs used by the applications) and the SnaBase.

The SnaBase software component maintains lists of service names and statuses for the client.

Tracing for SNA Server clients running Windows version 3.x is enabled or disabled by modifying the WIN.INI file.

Tracing cannot be carried out on a client running Windows version 3.x until certain files on the hard disk of the client are replaced with corresponding files from the SNA Server CD or the network share used to install SNA Server client software. For information about replacing the files, see: "Enabling or Disabling Tracing on Clients Running Windows Version 3.x," later in this chapter.

Types of Tracing for Clients Running Windows Version 3.x

The following table describes the types of tracing available for a client running Windows version 3.x and shows what each type applies to.

Type of tracing		Activity traced		Applies to
Internal		Activity within a software component of SNA Server		SnaBase, SNA Applications
Message		Messages passed into and out of a software component of SNA Server, including messages sent to and received from the SNA network		SnaBase, SNA Applications
API		Information passed into and out of an SNA Server DLL, such as WINAPPC.DLL, as the DLL communicates with an application		SNA Applications
Before setting up tracing, decide which software component(s) you want to trace, and which type(s) of tracing information will be useful. For example, to diagnose a situation where a client running Windows version 3.x cannot connect to an SNA resource, possible types of tracing to use are internal tracing and message tracing. With internal tracing, a product support technician will be needed to interpret the traces; with message tracing, product support may also be needed.

Available Trace Options for Clients Running Windows Version 3.x

Table 13.9 shows the trace options that can be activated and the corresponding lines to add to the [WNAP] section of the WIN.INI file. For instructions for adding the lines, see the next section.

Note

For all the following lines, filename1 and filename2 are names for two different files. Traces are written to filename1 until it reaches 250K, then to filename2 until it reaches 250K, and so on, alternating between the files. When adding lines specifying filenames for trace files, always add the lines in pairs (to include both filename1 and filename2) as shown, never as single lines alone.

Table 13.9     Trace Options for a Client Running Windows Version 3.x

Type of tracing		Lines to add to WIN.INI
Any type		TraceFlushing={ on | off }*
Internal		InternalTraceLevel= xwhere x is a value from 0 (full internal tracing)  through 16 (no internal tracing).
		InternalTraceFile1=path\filename1I nternalTraceFile2=path\filename2 (Include both these lines if either line is included.)
Message		InternalMessageTraceState={ on | off }
		FMITraceState={ on | off } (This line controls 3270 message tracing.)
		PVITraceState={ on | off } (This line controls LU 6.2 message tracing.)
		MessageTraceFile1=path\filename1 MessageTraceFile2=path\filename2 (Include both these lines if either line is included.)
SNA Applications (API tracing)		APITraceFile1=path\filename1 APITraceFile2=path\filename2 (Include both these lines if either line is included.)
		Specify the trace file names as shown in the  previous paragraph, and add one or more of the  following lines:
		Type of tracing	Line to add to WIN.INI
		APPC	APPCTraceState={ on | off }
		CSV	CSVTraceState={ on | off }
		RUI	RUITraceState={ on | off }
		HLLAPI	HLLAPITraceState={ on | off }
		CPIC	CPICTraceState={ on | off }
* Setting TraceFlushing to on causes trace information to be written to disk as soon as it is generated. This slows the system, but ensures that trace information is not lost if the system goes down.

In contrast, if TraceFlushing is set to off, information is held in a memory buffer until it is efficient to write it to disk. This avoids unnecessary slowing of the system, but does not protect trace information from being lost if the system goes down.

The FMITraceState option shown in Table 13.9 enables tracing of communication between a 3270 emulator and the SNA Server 3270 client interface. The PVITraceState option shown in Table 13.9 enables tracing of LU 6.2 messages; it is generally used in combination with tracing of APPC and/or CPI-C.

Tracing Entry Example

The following lines might be added to the [WNAP] section of the WIN.INI file; the entries would start the tracing of APPC APIs on the client and specify path and file names for the trace files:

APPCTraceState=on

APITraceFile1=c:\traces\api_tr1.trc

APITraceFile2=c:\traces\api_tr2.trc

Enabling or Disabling Tracing on Clients Running Windows Version 3.x

By default, all tracing is disabled on an SNA Server client running Windows version 3.x. Three steps are needed to enable tracing: adding lines to the WIN.INI file, backing up certain files on the hard disk of the client, and replacing those files with corresponding files from the SNA Server CD or the share created for installing client software. The replacement files modify the way that the software works, so that tracing is possible. After tracing is no longer needed, recopy the original, nontracing files to the appropriate directory on the client. This returns the client system to a normal level of efficiency. For details, see the following two procedures.

To enable tracing on a client running Windows version 3.x

1.	Load the WIN.INI file into a text editor.

2.	Locate the [WNAP] section of the file.

3.	Add, modify, or remove lines under the [WNAP] section heading, as shown in Table 13.9.

If you are investigating a problem that may cause your system to go down, be sure to include TraceFlushing=on, so that trace information will be written to disk as soon as it is generated, as described in the footnote to Table 13.9.

4.	Save the WIN.INI file as plain (ASCII) text (that is, avoid saving the file in a special format specific to the text editor).

5.	Stop the SNA Server software and the Windows version 3.x software.

6.	On the client computer, back up the following files by copying them to a different directory:

WindowsRoot\SYSTEM\WDMOD.DLL

WindowsRoot\SYSTEM\LMCLI.DLL

WindowsRoot\SYSTEM\NWCLI.DLL

WindowsRoot\SYSTEM\BVCLI.DLL

WindowsRoot\SYSTEM\IPCLI.DLL

SNAroot\WNAP.EXE

You will need to restore these files to their original location after you finish with tracing on the client.

7.	Access the installation medium (SNA Server CD or network share) for client software:

To access the CD, insert it in a CD-ROM drive.

To access the network share, connect to it. (For information about how to create a share for installation of clients over the network, see: Chapter 3 of the Microsoft SNA Server Installation Guide.)

8.	Change to the appropriate directory on the CD or network share:

On the CD, change to the \CLIENTS\WIN3X\TRACE directory.

On the network share, change to the \WIN3X\TRACE directory.

9.	Copy the appropriate files to the hard disk of the client computer, as described in the following table:

Type of tracing		Source file on the CD or network share	Destination directory on the hard disk of the client computer
Message or API		WDMOD.DLL	WindowsRoot\SYSTEM
Internal		LMCLI.DLL	WindowsRoot\SYSTEM
		NWCLI.DLL	WindowsRoot\SYSTEM
		BVCLI.DLL	WindowsRoot\SYSTEM
		IPCLI.DLL	WindowsRoot\SYSTEM
		WNAP.EXE	SNAroot
Note that internal tracing is intended for the use of product-support technicians; interpreting these traces requires a specialized knowledge base.

10.	Remove the CD from the drive, or disconnect from the network share.

11.	Restart the SNA Server software and the Windows version 3.x software.

As trace files are created, they are stored in the path(s) specified by the lines in the WIN.INI file.

To disable tracing on a client running Windows version 3.x

1.	Load the WIN.INI file into a text editor.

2.	Locate the [WNAP] section of the file.

3.	Add, modify, or remove lines under the [WNAP] section heading, as shown in Table 13.9.

4.	Save the WIN.INI file as plain (ASCII) text (that is, avoid saving the file in a special format specific to the text editor).

5.	Stop the SNA Server software and the Windows version 3.x software.

6.	On the client computer, locate the copies of the files that were backed up during the preceding procedure. The filenames are as follows:

WDMOD.DLL

LMCLI.DLL

NWCLI.DLL

BVCLI.DLL

IPCLI.DLL

WNAP.EXE

7.	Copy the files to destination directions as follows:

Filename	Destination directory on the hard disk
of the client computer

WDMOD.DLL	WindowsRoot\SYSTEM

LMCLI.DLL	WindowsRoot\SYSTEM

NWCLI.DLL	WindowsRoot\SYSTEM

BVCLI.DLL	WindowsRoot\SYSTEM

IPCLI.DLL	WindowsRoot\SYSTEM

WNAP.EXE	SNAroot

8.	Restart the SNA Server software and the Windows version 3.x software.


Tracing on MS-DOS Based Clients
Using Diagnostic Tools	11 of 12

Collecting Traces and Other Detailed System Information

Tracing on MS-DOS Based Clients

The following sections describe tracing on MS-DOS – based clients. For general information about tracing, see: "Collecting Traces and Other Detailed System Information" and "Trace Files" earlier in this chapter. For information about tracing on other types of clients, see "Tracing on SNA Servers or Windows NTBased Clients" or "Tracing on Clients Running Windows Version 3.x" earlier in this chapter, or "Tracing on OS/2-based Clients" later in this chapter.

Using tracing on MS-DOS – based clients is similar to using tracing on an SNA server, except that:

Tracing on a client provides information about activity on the client only, not activity on the SNA server.

The software components that can be traced on an MS-DOS – based client are SNA applications (specifically, the APIs used by the applications) and the SnaBase.

The SnaBase software component maintains lists of service names and statuses for the client.

Tracing for an MS-DOS – based client is enabled or disabled by modifying the SNA.INI file.

Tracing cannot be carried out on an MS-DOS – based client until certain executable files on the hard drive of the client are replaced with corresponding files from the SNA Server CD or the network share used to install SNA Server client software. For information about replacing the files, see: "Enabling or Disabling Tracing on MS-DOS – Based Clients," later in this chapter.

For general information about tracing, see: "Collecting Traces and Other Detailed System Information" and "Trace Files" earlier in this chapter.

Types of Tracing for MS-DOS – Based Clients

The following table describes the types of tracing available for MS-DOS – based clients, and shows what each type applies to.

Type of tracing		Activity traced		Applies to
Internal*		Activity within a software component of SNA Server		SnaBase, SNA applications
API		Information passed into and out of an SNA Server DLL, such as the APPC DLL, as the DLL communicates with an application		SNA applications
*  Internal tracing is intended for the use of product-support technicians; interpreting these traces requires a specialized knowledge base.

Before setting up tracing, decide which software component(s) you want to trace, and which type(s) of tracing information will be useful. Note that with internal tracing, a product support technician will be needed to interpret the traces.

Available Trace Options for MS-DOS – Based Clients

Table 13.10 shows the trace options that can be activated, and the corresponding lines to add to the [SNABASE] section of the SNA.INI file. For instructions for adding the lines, see the next section.

Note

For all the following lines, filename1 and filename2 are names for two different files. Traces are written to filename1 until it reaches 250 K, then to filename2 until it reaches 250 K, and so on, alternating between the files. When adding lines specifying filenames for trace files, always add the lines in pairs (to include both filename1 and filename2) as shown, never as single lines alone.

Table 13.10    Trace Options for an MS-DOS – Based Client

Type of tracing		Lines to add to SNA.INI
Any type		TraceFlushing={ on | off }*
Internal		InternalTraceLevel=x where x is a value from 0 (full internal tracing) through 16 (no internal tracing).
		InternalTraceFile1=path\filename1 InternalTraceFile2=path\filename2 (Include both these lines if either line is included.)
SNA Applications (API tracing)		APITraceFile1=path\filename1 APITraceFile2=path\filename2 (Include both these lines if either line is included.)
		Specify the trace file names as shown in the previous paragraph, and add one or more of the following lines:
		Type of tracing	Line to add to SNA.INI
		APPC	APPCTraceState={ on | off }
		CSV	CSVTraceState={ on | off }
		RUI	RUITraceState={ on | off }
		HLLAPI	HLLAPITraceState={ on | off }
*  Setting TraceFlushing to on causes trace information to be written to disk as soon as it is generated. This slows the system, but ensures that trace information is not lost if the system goes down.

In contrast, if TraceFlushing is set to off, information is held in a memory buffer until it is efficient to write it to disk. This avoids unnecessary slowing of the system, but does not protect trace information from being lost if the system goes down.

Tracing Entry Example

The following lines might be added to the [SNABASE] section of the SNA.INI file; the entries would start the tracing of APPC APIs on the client and specify path and file names for the trace files:

APPCTraceState=on

APITraceFile1=c:\traces\api_tr1.trc

APITraceFile2=c:\traces\api_tr2.trc

Enabling or Disabling Tracing on MS-DOS – Based Clients

By default, all tracing is disabled on an MS-DOS  –  based client. Three steps are needed to enable tracing: adding lines to the SNA.INI file, backing up certain files on the hard disk of the client, and replacing those files with corresponding files from the SNA Server CD or the share created for installing client software. The replacement files modify the way that the software works, so that tracing is possible. After tracing is no longer needed, recopy the original, nontracing files to the appropriate directory on the client. This returns the client system to a normal level of efficiency. For details, see the following two procedures.

To enable trace options on an MS-DOS – based client

1.	Load the SNA.INI file into a text editor.

2.	Locate the [SNABASE] section of the file.

3.	Add, modify, or remove lines under the [SNABASE] section heading, as shown in Table 13.10.

If you are investigating a problem that may cause your system to go down, be sure to include TraceFlushing=on, so that  trace information will be written to disk as soon as it is generated, as described in the footnote to Table 13.10.

4.	Save the SNA.INI file as plain (ASCII) text (that is, avoid saving the file in a special format specific to the text editor).

5.	Stop the SNA Server client software by typing:

snabase /d

6.	On the client computer, back up the following files by copying them to a different directory:

SNAroot\BVBASE.EXE

SNAroot\LMBASE.EXE

SNAroot\NWBASE.EXE

You will need to restore these files to their original location after you finish with tracing on the client.

7.	Access the installation medium (SNA Server CD or network share) for client software:

To access the CD, insert it in a CD-ROM drive.

To access the network share, connect to it. (For information about how to create a share for installation of clients over the network, see: Chapter 3 of the Microsoft SNA Server Installation Guide.)

8.	Change to the appropriate directory on the CD or network share:

On the CD, change to the \CLIENTS\MSDOS\TRACE directory.

On the network share, change to the \MSDOS\TRACE directory.

9.	Copy files to the hard disk of the client computer, as shown in the following table:

Source file on the CD or network share		Destination directory and filename on the hard disk of the client computer
TBVBASE.EXE		SNAroot\BVBASE.EXE
TLMBASE.EXE		SNAroot\LMBASE.EXE
TNWBASE.EXE		SNAroot\NWBASE.EXE
Note

The destination filename is different from the source filename. Be sure to type the names as shown in the table.

10.	Remove the CD from the drive, or disconnect from the network share.

11.	Restart the SNA Server client software by typing:

snabase

As trace files are created, they are stored in the path(s) specified by the lines in the SNA.INI file.

To disable tracing on an MS-DOS – based client

1.	Load the SNA.INI file into a text editor.

2.	Locate the [SNABASE] section of the file.

3.	Add, modify, or remove lines under the [SNABASE] section heading, as shown in Table 13.10.

4.	Save the SNA.INI file as plain (ASCII) text (that is, avoid saving the file in a special format specific to the text editor).

5.	Stop the SNA Server client software by typing

snabase /d

6.	On the client computer, locate the copies of the files that were backed up during the preceding procedure. The filenames are as follows:

BVBASE.EXE

LMBASE.EXE

NWBASE.EXE

7.	Copy the files to the SNA Server root directory on the client.

8.	Restart the SNA Server client software by typing

snabase


Tracing on OS/2-Based Clients
Using Diagnostic Tools	12 of 12

Collecting Traces and Other Detailed System Information

Tracing on OS/2-Based Clients

The following sections describe tracing on OS/2-based clients. For general information about tracing, see: "Collecting Traces and Other Detailed System Information" and "Trace Files" earlier in this chapter. For information about tracing on other types of clients, see: "Tracing on SNA Servers or WindowsNT – Based Clients," "Tracing on Clients Running Windows Version 3.x," or "Tracing on MS-DOS – Based Clients" earlier in this chapter.

Using tracing on OS/2-based clients is similar to using tracing on an SNA server, except that:

Tracing on a client provides information about activity on the client only, not activity on the SNA server.

Tracing for OS/2-based clients is enabled or disabled with the set command, as described in "The Set Command" later in this chapter. The set command sets environment variables for the operating system, including the variables for tracing for SNA Server. You can type the set command at the command prompt, or include it in an initialization file.

Tracing cannot be carried out on a client running OS/2 until certain files on the hard disk of the client are replaced with corresponding files from the SNA Server CD or the network share used to install SNA Server client software. For information about replacing the files, see: "Enabling or Disabling Tracing on Clients Running OS/2," later in this chapter.

For general information about tracing, see: "Collecting Traces and Other Detailed System Information" and "Trace Files" earlier in this chapter.

Types of Tracing for OS/2-Based Clients

The following table describes the types of tracing available for OS/2-based clients, and shows what each type applies to.

Type of tracing		Activity traced		Applies to
Internal*		Activity within a software component of SNA Server		SnaBase, SNA applications
Message		Messages passed into and out of a software component of SNA Server, including messages sent to and received from the SNA network		SnaBase, SNA applications
API		Information passed into and out of an SNA Server DLL, such as the APPC DLL, as the DLL communicates with an application		SNA applications
* Internal tracing is intended for the use of product-support technicians; collecting these traces requires special SNA Server files, and interpreting these traces requires a specialized knowledge base.
Before setting up tracing, decide which software component(s) you want to trace, and which type(s) of tracing information will be useful. Table 13.11 shows the information needed for interpreting the types of tracing available for OS/2-based clients.

Table 13.11    Information Needed for Interpreting Tracing on OS/2-Based Clients

Type of tracing	Software component traced	Area of expertise needed	Information source for interpretation
APPC API	SNA applications	APPC programming	Microsoft SNA Server APPC Programmer's Guide
CPI-C API	SNA applications	CPI-C programming	Microsoft SNA Server CPI-C Programmer's Guide
3270 Messages	SNA applications, or SnaBase	3270 emulator interface	3270 Emulator Interface Specification
LU 6.2 Messages	SNA applications, SnaBase	Intended for product support personnel	Product support technician
Internal	All software components for SNA Server	Intended for product support personnel	Product support technician
The Set Command

On OS/2-based clients, the first step in enabling or disabling tracing is to specify options with the set command. The set command can be run in the following ways:

You can type the set command at the command prompt, and then press ENTER. At that point, tracing will be available in that screen group.

The trace option remains in effect until changed by another set command, or until the system is restarted.

You can add the set command to an initialization file, and reference the initialization file in CONFIG.SYS. To do this, make sure the following string is added to the end of the protshell command in CONFIG.SYS:

/k c:os2init.cmd

Then type the set command(s) into a file named OS2INIT.CMD (in the root directory of the C drive) and save the file. The trace option takes effect when the system is restarted. If a set command is then typed at a command prompt, it will override the command in the initialization file, until the system is restarted once more.

To see a listing of current environment variables on an OS/2-based system — that is, to see the latest values specified with set commands — at the command prompt, type set without options.

Available Trace Options for OS/2-Based Clients

Table 13.12 shows the trace options that can be specified on an OS/2-based client, and the corresponding syntax to use in the set command. As trace files are created, they are stored in the path(s) specified in the set command(s).

Note

For all the following lines, filename1 and filename2 are names for two different files. Traces are written to filename1 until it reaches a specified size, then to filename2 until it reaches that size, and so on, alternating between files. By default, the files can grow to 250K each; other sizes can be specified with the set comflip command, as described in "Other Tracing Options" later in this chapter. When specifying trace files, always include a pair of filenames (filename1 and filename2 as shown), never just one filename alone.

Table 13.12    Trace Options for an OS/2-Based Client

Type of tracing		Syntax to use with set command
Internal*		set comint=tracelevel/path\filename1/path\filename2 where tracelevel is an even number from 0 (full internal tracing) through 16 (no internal tracing).
SNA applications (API tracing)		set comtrc =path\filename1/path\filename2/
All messages		set comsna=path\filename1/path\filename2/a
3270 messages,LUA messages		set comsna=path\filename1/path\filename2/f
LU 6.2 messages		set comsna=path\filename1/path\filename2/p
* Internal tracing is intended for the use of product-support technicians; collecting these traces requires special SNA Server files, and interpreting these traces requires a specialized knowledge base. If a product-support technician requests internal tracing, the level needed is generally level 0 (full tracing).

Other Tracing Options

In addition to the tracing options shown in the preceding table, there are a number of modifications that can be made to tracing on an OS/2-based client, as shown in the following list.

set comflip=filesize

Changes the size of the two trace files (which have path and filenames as specified in another set command). For filesize, substitute a decimal value, representing a file size in bytes. Traces are written to one file until it reaches the specified size, then to the other until it reaches that size, and so on, alternating between files. The default file size is 250000 bytes (250K).

set comflush

Causes trace information to be written to disk as soon as it is generated. This slows the system, but ensures that trace information is not lost if the system goes down.

In contrast, if the set comflush command is not used, information is held in a memory buffer until it is efficient to write it to disk. This avoids unnecessary slowing of the system, but does not protect trace information from being lost if the system goes down.

set comtrunc=recordsize

Specifies the maximum number of bytes allowed for each trace record (each record of a single system event). For recordsize, substitute a decimal value from 0 through 65535. If you are interested in the identifying information at the beginning of a traced system event, but not all the data transferred during the event, decrease recordsize; a few hundred bytes is enough to store much of the important identifying information in each trace record. The default record size is 65535.

Tracing Examples for OS/2-Based Clients

To trace 3270 messages for SNA applications on a 3270 or LUA client, you could use the following set command:

set comsna=\traces\3270msg1.trc/\traces\3270msg2.trc/f

To trace LU 6.2 messages for SNA applications on an APPC or CPI-C client, you could use the following set command:

set comsna=\traces\lu62msg1.trc/\traces\lu62msg2.trc/p

To trace the APPC API on an APPC client, you could use the following set command:

set comtrc=\traces\appc1.trc/\traces\appc2.trc/

Enabling or Disabling Tracing on Clients Running OS/2

By default, tracing is disabled on an OS/2-based client. Three steps are needed to enable tracing: running appropriate set commands, backing up certain files on the hard disk of the client, and replacing those files with corresponding files from the SNA Server CD or the share created for installing client software. The replacement files modify the way that the software works, so that tracing is possible. After tracing is no longer needed, stop running the set commands, and recopy the original, nontracing files to the appropriate directory on the client. This returns the client system to a normal level of efficiency. For details, see the following two procedures.

To enable tracing on a client running OS/2

1.	Run appropriate set commands, as described in "The Set Command," "Available Trace Options for OS/2-Based Clients," and "Other Tracing Options," earlier in this chapter.

If you are investigating a problem that may cause your system to go down, be sure to use the set comflush command, so that  trace information will be written to disk as soon as it is generated, as described in "Other Tracing Options," earlier in this chapter.

Note that internal tracing is intended for the use of product-support technicians; interpreting these traces requires a specialized knowledge base.

2.	Stop the SNA Server software.

3.	On the client computer, back up the following files by copying them to a different directory:

SNAroot\COMDMOD.DLL

SNAroot\COMNAP.EXE

You will need to restore these files to their original location after you finish with tracing on the client.

4.	Access the installation medium (SNA Server CD or network share) for client software:

To access the CD, insert it in a CD-ROM drive.

To access the network share, connect to it. (For information about how to create a share for installation of clients over the network, see: Chapter 3 of the Microsoft SNA Server Installation Guide.)

5.	Change to the appropriate directory on the CD or network share:

On the CD, change to the \CLIENTS\OS2\TRACE directory.

On the network share, change to the \OS2\TRACE directory.

6.	Copy files to appropriate filenames in the SNA Server root directory, as shown in the following table:

Source file on the CD or network share		Destination directory and filename on the hard disk of the client computer
TRCDMOD.DLL		SNAroot\COMDMOD.DLL
TRCNAP.EXE		SNAroot\COMNAP.EXE
Note

The destination filename is different from the source filename. Be sure to type the names as shown in the table.

7.	Remove the CD from the drive, or disconnect from the network share.

8.	Restart the SNA Server client software.

As trace files are created, they are stored in the path(s) specified by the set commands.

To disable tracing on a client running OS/2

1.	Avoid running set commands that enable tracing, as described in "The Set Command."

You may need to restart your computer to do this. To see the latest values specified with set commands, at the command prompt, type set without options.

2.	Stop the SNA Server software.

3.	On the client computer, locate the copies of the files that were backed up during the preceding procedure. The filenames are as follows:

COMDMOD.DLL

COMNAP.EXE

4.	Copy the files to the SNA Server root directory on the client.

5.	Restart the SNA Server software.


Guidelines for Specific Configurations
Appendix A	1 of 9

Guidelines for Specific Configurations

This appendix contains configuration information that is specific to certain types of installations, including installations that use modems that can accept a phone number from SNA Server. The following table lists the topics covered in this appendix:

Topic		Section title
Maximum number of connections and sessions allowed		SNA Server Adapter and Connection Capacities
Modems		Phone Number Storage and Modem Types
Using the snadftlu utility to determine which LUs are assigned to a given DFT adapter		Determining the LUs Assigned to a DFT Adapter
Determining the link role for a connection		Determining a Connection’s Link Role
For information about Registry and environment variables, which may be needed for certain installations, see: the Microsoft SNA Server Reference.


SNA Server Adapter and Connection Capacities
Guidelines for Specific Configurations	2 of 9

SNA Server Adapter and Connection Capacities

The SNA Server software has the following upper limits for use:

A maximum upper limit of 10,000 concurrent 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 maximum number of connections and sessions that can be set up for each connection type on a given computer:

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
* “Maximum sessions” are 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.

Note

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


Phone Number Storage and Modem Types
Guidelines for Specific Configurations	3 of 9

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 SDLC adapter to which the modem is attached have a built-in serial (COM) port (like the SDLC adapters from Microgate).

For information about specifying dial data to be sent to the modem or to be displayed in a pop-up message, see: “List of Basic SDLC Settings” in Chapter 3. In addition, there are two connection parameters that must be set to match your modem: the Encoding (NRZ/NRZI) and Duplex parameters. For information, see “List of Advanced SDLC Settings” in Chapter 3.


Changing the SNA Server Dialing Method
Guidelines for Specific Configurations	4 of 9

Phone Number Storage and Modem Types

Changing the SNA Server Dialing Method

To change the SNA Server dialing method for a modem, use the SNA Server Setup program; then restart SNA Server Admin and, from the File menu, choose Save Configuration. For information about Setup, see the Microsoft SNA Server Installation Guide or the Setup online Help.


Modem Requirements for Accepting a Phone Number from SNA Server
Guidelines for Specific Configurations	5 of 9

Phone Number Storage and Modem Types

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 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
Guidelines for Specific Configurations	6 of 9

Phone Number Storage and Modem Types

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 following modem interface signals to off:

Select Standby

DSR

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 the call is connected.

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

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


Command String Examples
Guidelines for Specific Configurations	7 of 9

Phone Number Storage and Modem Types

Command String Examples

In the Microgate Dialer Setup dialog box in SNA Server Setup, the following command string is the default for outgoing calls. As described in the preceding section, the command string forms the base onto which the phone number is appended when SNA Server sends a dial string to a modem.

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

The elements in the command string have the following effects:

AT is the standard modem command prefix.

&F resets the modem to the factory defaults.

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

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

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

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

Q1 turns off modem result codes.

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

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

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

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

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


Determining the LUs Assigned to a DFT Adapter
Guidelines for Specific Configurations	8 of 9

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 services are stopped; this includes all connections, link services, and the server. To stop a connection or the server, select it and then, from the Services menu, select Stop Services.

2.	Switch to a command prompt.

3.	At the command prompt, 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.


Determining a Connection’s Link Role
Guidelines for Specific Configurations	9 of 9

Determining a Connection’s Link Role

SNA Server assigns a link role to a connection according to the type of system at the remote end (host or peer). The following table shows the link role that SNA Server assigns:

Remote end		Assigned link rolefor connection
Host		Secondary
Peer (other than multidrop)		Negotiable
Peer, with local server as the SDLC Multidrop Primary *		Primary
Downstream		Primary
*  For information about multidrop, see the sections about SDLC in Chapter 3, “Configuring Servers and Connections.”


SNA Server Preparation Forms
Appendix B	1 of 17

SNA Server Preparation Forms

This appendix provides forms that may be useful for gathering configuration information for SNA Server. For an overview of configuration for SNA Server, see:Chapter 1, “Getting Started.” For details about configuring the settings shown in the forms, see the chapters and sections listed in the following tables.

Table B.1	Forms for Configuring the Server and Connections

Form		Related chapter number and name			Related section
Server Resources Planning		1	Getting Started		Basic Tasks
Server Information		1	Getting Started		Gathering Information
Initial Connection Settings		3	Configuring Servers and Connections		List of Connection Properties
802.2 Settings		3	Configuring Servers and Connections		List of Basic 802.2 SettingsList of Advanced 802.2 Settings
SDLC Settings		3	Configuring Servers and Connections		List of Basic SDLC Settings List of Advanced SDLC Settings
X.25 Settings		3	Configuring Servers and Connections		List of Basic X.25 Settings List of Advanced X.25 Settings
Channel Settings		3	Configuring Servers and Connections		List of Basic Channel Settings List of Advanced Channel Settings
Table B.2	Forms for Configuring LUs

Form		Related chapter number and name			Related section
3270 LUs (Individual)		4	Configuring for 3270		Configuring Individual 3270 LUs
3270 LUs (Ranges)		4	Configuring for 3270		Configuring a Range of 3270 LUs
Users and Groups		4	Configuring for 3270		Setting Up User and Group Access
Local APPC LUs		6	Configuring LUs for APPC		Configuring Local APPC LU Properties
Remote APPC LUs		6	Configuring LUs for APPC		Configuring Remote APPC LU Properties
Mode Properties for LU-LU Pairs		6	Configuring LUs for APPC		Mode Properties
CPI-C Properties		6	Configuring LUs for APPC		Configuring Properties for CPI-C
		7	Configuring for 5250 Emulation in the AS/400 Environment		Configuration Steps for the AS/400 Environment
		7	Configuring for 5250 Emulation in the AS/400 Environment		Configuration Steps for the AS/400 Environment
3270 LU Pools		10	Using LU Pools to Maximize Access		3270 LU Pools
Table B.3	Forms for Configuring Diagnostics

Form		Related chapter number and name			Related section
RTM Settings3270		13	Using Diagnostic Tools		Configuring RTM Settings


Server Resources Planning Form
SNA Server Preparation Forms	2 of 17

Server Resources Planning Form

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
SNA Server Preparation Forms	3 of 17

Server Information Form

Server Information Form

Server Name: ___________________   Server location:___________________

Machine manufacturer:_______________ Type: [  ] Intel  [  ] MIPS  [  ]Alpha

Machine model: ____________ RAM (megabytes): _______ Speed: ________

Network 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       [  ] AppleTalk

[  ] NetWare [image], version ___________        [  ] Banyan VINES, version ________

Transport:

[  ] NetBEUI   [  ] TCP/IP   [  ] IPX/SPX   [  ] DECnet [image]   [  ] RAS   [  ] Other

Role:	    Domain:   [  ] Primary controller    [  ] Backup controller    [  ] Server

            Replication:    [  ] Export    [  ] Import    [  ] Both

SNA server:    [  ] Primary    [  ] Backup    [  ] Member

Installation support:  Supports network installation  [  ] Yes    [  ] No


Initial Connection Settings Form
SNA Server Preparation Forms	4 of 17

Initial Connection Settings Form

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
SNA Server Preparation Forms	5 of 17

802.2 Settings Form

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:  [  __ __ __  ]  [  __ __ __ __ __  ]

Connection Activation:

Maximum number of 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
SNA Server Preparation Forms	6 of 17

SDLC Settings Form

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:  [  __ __ __  ]  [  __ __ __ __ __  ]

Connection Activation:

Maximum number of 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:  _____________ s

Multidrop Primary:	[  ] Yes	[  ] No
Select Standby:	[  ] Yes	[  ] No

Switched Connection Establishment Timeout:  _________________________


X.25 Settings Form
SNA Server Preparation Forms	7 of 17

X.25 Settings Form

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:  [  __ __ __  ]  [  __ __ __ __ __  ]

Connection Activation:

Maximum number of 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
SNA Server Preparation Forms	8 of 17

Channel Settings Form

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)
SNA Server Preparation Forms	9 of 17

3270 LUs Form (for Individual LUs)

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)
SNA Server Preparation Forms	10 of 17

3270 LUs Form (for Ranges of LUs)

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

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
SNA Server Preparation Forms	11 of 17

3270 LU Pools Form

3270 LU Pools Form

Pool Name:  ___________________  Comment:  ________________________

LU type:	[  ] Display	Display Model:	[  ] 2 (24x80)
	[  ] Printer		[  ] 3 (32x80)
			[  ] 4 (43x80)
			[  ] 5 (27x132)
		Model can be overridden:	[  ] Yes  [  ] No
LUs in Pool:

_______________  ______________  _______________  _____________

_______________  ______________  _______________  _____________

_______________  ______________  _______________  _____________

_______________  ______________  _______________  _____________

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- - - - - - - -

Pool Name:  ___________________  Comment:  ________________________

LU type:	[  ] Display	Display Model:	[  ] 2 (24x80)
	[  ] Printer		[  ] 3 (32x80)
			[  ] 4 (43x80)
			[  ] 5 (27x132)
		Model can be overridden:	[  ] Yes  [  ] No
LUs in Pool:

_______________  ______________  _______________  _____________

_______________  ______________  _______________  _____________

_______________  ______________  _______________  _____________

_______________  ______________  _______________  _____________


Users and Groups Form
SNA Server Preparation Forms	12 of 17

Users and Groups Form

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:  _______________________


Local APPC LUs Form
SNA Server Preparation Forms	13 of 17

Local APPC LUs Form

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: _______________________________________

Time-out for Starting TPs:  __________________________________________

Partner LUs:   _________________   _________________   ________________

_________________   _________________   ________________

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

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: _______________________________________

Time-out for Starting TPs:  __________________________________________

Partner LUs:   _________________   _________________   ________________

_________________   _________________   ________________


Remote APPC LUs Form
SNA Server Preparation Forms	14 of 17

Remote APPC LUs Form

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: ___________________________________________

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Connection:  ______________________________________________________

LU Alias:  ___________________  LU Name:  __________________________

Network Name:_______________  Uninterpreted LU Name:  _____________

Comment:  _____________________________________________________

Supports Parallel Sessions:	[  ] Yes	[  ] No
Enable Automatic Partnering:	[  ] Yes	[  ] No
Implicit Incoming Mode: ___________________________________________


Mode Properties for LU-LU Pairs Form
SNA Server Preparation Forms	15 of 17

Mode Properties for LU-LU Pairs Form

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
SNA Server Preparation Forms	16 of 17

CPI-C Properties Form

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: ______________________________________________________


3270 RTM Settings Form
SNA Server Preparation Forms	17 of 17

3270 RTM Settings Form

3270 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


SNA Server NetView Extensions
Appendix C	1 of 7

SNA Server NetView Extensions

The NetView reporting system sends alerts and other information back and forth between a host (mainframe) and computers that connect to it. 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.

For information about the logging of system events on the SNA server, see: Chapter 13, “Using Diagnostic Tools.” For information about NetView options and functionality, see: Chapter 4, “Configuring for 3270,” and Chapter 13, “Using Diagnostic Tools.”

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 next 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” later in this chapter.


Code Page Settings for NVAlert and NVRunCmd
SNA Server NetView Extensions	2 of 7

Code Page Settings for NVAlert and NVRunCmd

You can control the host code page and local code page used by NVAlert and NVRunCmd. NVAlert and NVRunCmd use the same host code page as is set in the SNA Server 3270 Applet; the default is United States (037).

To change the host code page for NVAlert and NVRunCmd

1.	On the server on which NVAlert and NVRunCmd are run, start the SNA Server 3270 Applet by double-clicking the icon.

2.	From the Session menu, choose Session Configuration.

3.	In the 3270 Settings dialog box, select the intended Host Code Page.

4.	Choose OK.

The new host code page takes effect for NVAlert and NVRunCmd when they are restarted.

NVAlert and NVRunCmd use the same local code page as is set in Windows NT.  To change the local code page, see the instructions for the Language field in the International option of the Control Panel, as described in your Windows NT documentation.


The NVAlert Service
SNA Server NetView Extensions	3 of 7

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.

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

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, as described in the next section.

The NVAlert service runs as a background process waiting for an event to be recorded in a log file, and compares each logged event to the 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.


Modifying NVALERT.INI
SNA Server NetView Extensions	4 of 7

The NVAlert Service

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 following sections. For information about standard code points and values used by NetView, see your IBM NetView documentation.

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 “Using Event Logs” in Chapter 13.

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 event detail 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. The detailed data lines are described in the next section.

Providing Detailed Data Information

This section 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
SNA Server NetView Extensions	5 of 7

The NVAlert Service

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.

Such an alert has the following characteristics:

The source is Srv.

The type is 2 (warning).

The eventid is 2013.

The description in the Windows NT event log is “The C: disk is at or near capacity. You may need to delete some files.”

The following NVALERT.INI section would forward the Windows NT-based alert to a host system, and 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
SNA Server NetView Extensions	6 of 7

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


How NVRunCmd Runs
SNA Server NetView Extensions	7 of 7

The NVRunCmd Service

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 (in 256-byte segments), 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.

Typing a Command at the Host Console

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

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 64K. Any additional information returned by the command will be lost.


Offline Configuration
Appendix D	1 of 7

Offline Configuration

You can create or modify a configuration file for another SNA site. Such a file is called an offline configuration file. Offline configuration files and backup configuration files use the same filename extension, .SNA. A file is called “offline” if it is created or modified at one site and used at another.

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 work on an offline configuration file by using the command-line interface, see both this appendix and Appendix E, “The Command-Line Interface.”

This appendix describes differences between offline configuration and on-site configuration, and tells how to use the offline version of SNA Server Admin.


Differences Between Offline Configuration and OnSite Configuration
Offline Configuration	2 of 7

Differences Between Offline Configuration and OnSite 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 are typed incorrectly, the offline configuration file will work incorrectly at the remote site.

In addition, 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 user /validate command to process the file, as described in the next section. This command attempts to fill in SIDs that are missing from user or group listings in the SNA Server configuration. For more information, see: snacfg user in Appendix E.

Important

Server names, link service names, adapter properties, and user names must be correct in an offline configuration file. The most reliable way to ensure correctness is to 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. For more information about creating a backup configuration file, see: “Starting the Offline Version of SNA Server Admin” later in this appendix.


Guidelines for Offline Configuration
Offline Configuration	3 of 7

Guidelines for Offline Configuration

The following guidelines give the sequence of steps for creating and using an offline configuration file. The 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 instead. For information about the command-line interface, see: Appendix E, “The Command-Line Interface.”

To create and use an offline configuration file, take the following steps:

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.

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.

For more information, see the previous section, and “Using the Offline Version of SNA Server Admin” later in this appendix.

2.	Start the offline version of SNA Server Admin, and modify the configuration file created in step 1, or create a new configuration file. For more information, see: “Starting the Offline Version of SNA Server Admin” later in this appendix.

3.	Send the offline configuration file to the site where it will be used.

4.	At the site where the configuration will be used, 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.

This command causes any missing user SIDs to be added to the configuration file. These SIDs are not added during the offline configuration process.

6.	Start SNA Server Admin in the domain where the configuration file will be used.

7.	From the File menu, choose Restore.

8.	In the Restore Configuration From dialog box, select the drive, directory, and filename of the offline configuration file.

9.	Choose the OK button.

The configuration is now available to be used in SNA Server Admin.

10.	If needed, modify the configuration.

11.	Save the configuration file:

To save the configuration file as the active configuration file, from the File menu, choose Save Configuration.

To save the configuration file as a backup configuration file, from the File menu, choose Backup, specify a directory and filename, and choose the OK button.


Starting the Offline Version of SNA Server Admin
Offline Configuration	4 of 7

Starting the Offline Version of SNA Server Admin

The cue that starts the offline version of SNA Server Admin is a filename extension of “.SNA” (the extension used for both backup and offline configuration files). The procedures in this section tell how to do the following:

Create a backup configuration file to use with the offline version of SNA Server Admin

Start the offline version of SNA Server Admin with a backup configuration file

    Start the offline version of SNA Server Admin without a backup configuration fileconfiguration file before starting the offline version of SNA Server Admin, see: “Differences Between Offline Configuration and On-Site Configuration” earlier in this appendix.

To create a backup configuration file to use with the offline version of SNA Server Admin

Note

If possible, arrange for the backup configuration file to be created at the remote site — the intended site for the offline configuration. Also, arrange for the backup file to be created with the intended SNA servers already installed and the intended users already added to the configuration.

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 the OK button.

To start the offline version of SNA Server Admin with a backup configuration file

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.	Create the offline configuration:

To use the backup configuration as a base for the offline configuration, leave the backup configuration displayed and make changes as necessary.

To build a new offline configuration not based on the backup configuration, from the File menu, choose New. Then create the offline configuration.

For more information about creating offline configurations, see: “Using the Offline Version of SNA Server Admin” later in this appendix.

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 the OK button.

To start the offline version of SNA Server Admin without a backup configuration file

1.	Switch to a command prompt.

2.	At the command prompt, type

snaadmin *.sna

A message box appears, saying “Configuration file not found.”

3.	In the message box, choose the OK button.

The offline version of SNA Server Admin is now running.


Using the Offline Version of SNA Server Admin
Offline Configuration	5 of 7

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. For important information about these items, see: “Differences Between Offline Configuration and On-Site Configuration” earlier in this appendix.

In addition, 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. For important information about entering server names for offline configurations, see: “Differences Between Offline Configuration and On-Site Configuration” earlier in this appendix.

Adapters and link service properties can be specified, by using the Adapters button in the Server Properties dialog box. For important information about entering link service information for offline configurations, see: “Differences Between Offline Configuration and On-Site Configuration” earlier in this appendix, and “Specifying Adapter Properties in an Offline Configuration” later in this appendix.

Services cannot be started; they can only be configured. Menu commands applying to starting, stopping, and resetting are not available. The Toolbar buttons for starting and stopping are dimmed.

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, domains and security IDs for offline configurations, see: “Differences Between Offline Configuration and On-Site Configuration” earlier in this appendix.

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. The only File menu commands for creating or opening a file are New and Open.


Adding a Server to an Offline Configuration
Offline Configuration	6 of 7

Using the Offline Version of SNA Server Admin

Adding a Server to an Offline Configuration

You can add a server to an offline configuration.

Important

When you specify a server name in the offline version of SNA, 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: “Differences Between Offline Configuration and On-Site Configuration” earlier in this appendix.

To add a server to an offline configuration

1.	Start the offline version of SNA Server Admin, as described in: “Starting the Offline Version of SNA Server Admin” earlier in this appendix.

The offline version of SNA Server Admin appears.

2.	In the Servers and Connections window, select any line.

3.	From the Services menu, choose New Server.

The Server Properties dialog box appears.

4.	In the Server Properties dialog box, type a server name for the new server.

The server 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 Help for the SNA Server Setup program.

5.	If desired, specify a Control Point Name, Network Name, and/or Comment for the server, as described in: “Configuring Servers” in Chapter 3.

6.	Choose the Adapter button, and configure one or more adapters for the SNA Server, as described in the next section.

7.	Choose the OK button.


Specifying Adapter Properties in an Offline Configuration
Offline Configuration	7 of 7

Using the Offline Version of SNA Server Admin

Specifying Adapter Properties in an Offline Configuration

You can specify adapter or link service properties in an offline configuration.

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: “Differences Between Offline Configuration and On-Site Configuration” earlier in this appendix.

To specify adapter properties in an offline configuration

1.	Start the offline version of SNA Server Admin, as described in: “Starting the Offline Version of SNA Server Admin” earlier in this appendix.

The offline version of SNA Server Admin appears.

2.	In the Servers and Connections window, select the server for which you want to specify adapter properties.

3.	From the Services menu, choose Properties.

The Server Properties dialog box appears.

4.	In the Server Properties dialog box, choose the Adapters button.

5.	Configure adapter properties as described in: the Microsoft SNA Server Installation Guide.

6.	Choose the OK button.


The Command-Line Interface
Appendix E	1 of 27

The Command-Line Interface

In addition to the graphical interfaces provided by SNA Server Setup and SNA Server Admin, there is a command-line interface available with SNA Server. The command-line interface can be useful for certain situations, such as when you want to view a configuration setting quickly without starting the graphical interface, or when you want to store configuration commands in a command file, so that they can be carried out easily in the future. (Command files are described later in this appendix.)

Before using the command-line interface, you must install SNA Server with SNA Server Setup, and run SNA Server Admin at least once. This initializes important elements of the SNA Server configuration that cannot be controlled with the command-line interface.

For information about accessing the command prompt, see your Windows NT documentation.

You can use the command-line interface to modify an offline configuration file (as well as a regular on-site configuration file). However, when you work with an offline configuration file, validation of server names, link names, and user names cannot take place, and errors may result. For important information about working with offline configuration files, see: Appendix D, “Offline Configuration.”For information about specifying the name of the configuration file to modify with the command-line interface, see: “Specifying the Configuration File” later in this appendix.

Some other actions are also not available. For example, you cannot use the command-line interface to configure ranges of LUs, or to configure LUs for a DFT connection.


Avoiding Critical Errors in Commands
The Command-Line Interface	2 of 27

Avoiding Critical Errors in Commands

Certain SNA Server commands must be used with great care if the /add option is used with them. With these commands — snacfg server, snacfg link, and snacfg user — the information you type must match existing information in your system or on the domain.

Important

If you specify server names, link service names, adapter properties, or user names by using the /add option with snacfg server, snacfg link, or snacfg user, these names or properties must match existing names and properties in your installation, or a nonfunctioning configuration may result. To protect against errors with these commands, use the SNA Server graphical interfaces instead. Use SNA Server Setup instead of using snacfg server or snacfg link with the /add option. Use SNA Server Admin instead of using snacfg user with the /add option.


Task Order
The Command-Line Interface	3 of 27

Task Order

Just as with SNA Server Setup and SNA Server Admin, configuration tasks must be carried out in a certain order with the command-line interface. For example, before configuring an LU, you must configure the connection that the LU will use. You can vary the interface you use for each configuration task, as long as you carry out the tasks in order, and as long as you have already installed SNA Server with SNA Server Setup and then run SNA Server Admin. For example, you can carry out tasks using SNA Server Setup, then SNA Server Admin, then the command-line interface, then SNA Server Admin again, as long as the tasks are done in the correct order.

The following table shows the order in which configuration tasks must be carried out, and the command used to carry out the task.

Table E.1    Task Order for Configuration Tasks

Configuration task (in order)		Command that carries out task
1	Add an SNA Server to the configuration		snacfg server*
2	Configure link service(s) for the server(s)		snacfg link*
3	Configure connection(s) for the server(s)		snacfg connection
4	Configure LU(s) for the connection(s)		snacfg appcllu,  snacfg appcrlu,  snacfg lu,  snacfg lua,  or  snacfg lud
5	Create LU pool(s)  (optional)		snacfg pool,  snacfg poola,  or  snacfg poold
6	Assign LUs to pool(s)  (optional)		snacfg lu,  snacfg lua,  or  snacfg lud
7	Add users to the list used by SNA Server		snacfg user†
8	Assign LU(s) or LU pool(s) to users		snacfg user
* It is recommended that you use SNA Server Setup, not the command-line interface, for these tasks. Any errors in the typing of commands for these tasks can result in a nonfunctioning configuration.

† It is recommended that you use SNA Server Admin, not the command-line interface, for this task. Any errors in typing this command can result in a nonfunctioning configuration.


Getting Help with the Command-Line Interface
The Command-Line Interface	4 of 27

Getting Help with the Command-Line Interface

To see the syntax for a particular snacfg command, follow the command with the /? option.

For example, to get a listing of the words that can follow snacfg in the command line, type

snacfg /?

To get a listing of the options that can follow snacfg connection, type

snacfg connection /?


Specifying the Configuration File
The Command-Line Interface	5 of 27

Specifying the Configuration File

Within an SNA Server command (a snacfg command), you can specify the path of the configuration file to access, or you can omit the path. If you omit the path, SNA Server attempts to access the configuration file in the normal location on the local system: \SNAroot\SYSTEM\CONFIG\COM.CFG, where SNAroot is the SNA Server root directory.

To specify the path of the configuration file to access, type the snacfg command with the following syntax:

snacfg #configpath command options

That is, follow the snacfg command with a space, a pound sign, then the configuration path, then any additional command syntax.

For example, to view a listing of the connections stored in \SNA\SYSTEM\CONFIG\BACKUP.SNA, type

snacfg #\sna\system\config\backup.sna connection /list


Using a Command File
The Command-Line Interface	6 of 27

Using a Command File

If you want to run a series of SNA Server configuration commands, you can remove the word snacfg from each command, place them in a file called a command file, then use a single snacfg command to run the entire command file. This is similar to the way a batch file works; however, a command file opens and closes the configuration file fewer times than a batch file. When a command file is run, the configuration file is opened only once, at the beginning. Then all the commands are carried out, and the configuration file is closed. In contrast, when a batch file containing snacfg commands is run, the configuration file is opened and closed multiple times, once for every command in the file.

When creating a command file, do not include the following:

The word snacfg

A path for a configuration file

A command path for another command file

A backslash inside the text string for a comment

Also, you can include long, multiline commands in a command file by ending lines with a backslash ( \ ). The backslash indicates that the string in the next line should be appended to the current command.

There are two steps for using a command file. First, create the file, either by typing the configuration commands into a plain text file, or by using the /print option as described in the next section. Then run the command file from the command prompt by typing a line with the following syntax:

snacfg [#configpath] @commandpath [/v]

In the preceding syntax line, configpath is the path of the configuration file on which commands should be carried out; precede this path with the # symbol. Similarly, commandpath is the path of the command file; precede this path with the @ symbol. Use the /v (verbose) option to cause all informational messages (not just error messages) to be displayed when the command file is running; without the /v option, only error messages are displayed.

For example, to run a series of commands that result in a listing of the links and connections in a configuration file, create a file called SNA_CMD1.TXT, containing the following lines:

To run the SNA_CMD1.TXT file, you would determine the path of the configuration file on which to run the commands; for example, \SNA\SYSTEM\CFG1.SNA. Then you would determine the path of the command file itself, for example, \SNA\TEMP\SNA_CMD1.TXT. With these paths, you would type the following at the command prompt:

snacfg #\sna\system\cfg1.sna @\sna\temp\sna_cmd1.txt

For information about using the /print option to create a command file, see the next section.


Creating a Snacfg Command File from a Configuration File
The Command-Line Interface	7 of 27

Creating a Snacfg Command File from a Configuration File

To create lines for a snacfg command file, you can type them, or you can generate them by using the /print option. The /print option accesses an existing configuration file and generates the command line(s) required to add an individual resource or (depending on syntax) the entire configuration file.

The output generated by the /print option does not contain the word snacfg. This means that the output can be included in a snacfg command file.


General Syntax for the /print Option
The Command-Line Interface	8 of 27

Creating a Snacfg Command File from a Configuration File

General Syntax for the /print Option

The syntax lines in this section and the next section show ways to use the /print option. By default, the output is sent to the screen. To capture the output in a file, redirect it in the standard way, by adding a greater-than sign (>) to the end of the command, followed by the name of the file in which you want to capture the output.

With all the syntax lines, if the source configuration file is not in the default path, \SNAroot\SYSTEM\CONFIG\COM.CFG, then for #configpath, substitute a path, preceded by the pound sign (#). Do not type the square brackets. After the greater-than sign (>), type the name of the command file you want to create. (For information about using the greater-than sign or other methods of redirection, see your Windows NT documentation.)

The general syntax for the /print option is:

snacfg [#configpath] [resource [location:]resourcename] /print > cmdfile.ext

For resource, substitute the second word of a snacfg command (for example, appcllu, connection, or server). For location, if needed, substitute the server or connection name that uniquely locates a resource; for resourcename, substitute the name of the resource.


Examples of Syntax for the /print Option
The Command-Line Interface	9 of 27

Creating a Snacfg Command File from a Configuration File

Examples of Syntax for the /print Option

The following examples illustrate the use of the /print option.

To create a command file that can recreate an entire configuration file, type a command of the following form:

snacfg [#configpath] /print > cmdfile.ext

To create a command file from a particular connection in an existing configuration, type a command of the following form, substituting the name of the connection for connectionname:

snacfg [#configpath] connection connectionname /print > cmdfile.ext

To create a command file from a particular 3270 LU in an existing configuration, type a command of the following form, substituting the name of the LU for luname:

snacfg [#configpath] lu luname /print > cmdfile.ext

After generating snacfg command files, you can modify them and then use them like any other snacfg command file.


Ways of Using the /print Option
The Command-Line Interface	10 of 27

Creating a Snacfg Command File from a Configuration File

Ways of Using the /print Option

The /print option can make it easier to carry out repetitive configuration actions, if you have a detailed understanding of SNA Server configurations and of the snacfg command. Here are some ways of using the /print option:

Creating a new configuration

You can generate a snacfg command file corresponding to an entire configuration file, modify the command file, and use it to create a new configuration file for another domain or site. To generate the commands for an entire configuration file, use the syntax shown in the first example in the previous section, that is, omit all snacfg modifiers (such as connection or lu).

Creating a template to use for expanding one or more configurations

You can generate a snacfg command file that corresponds to a useful element of an existing configuration (for example, a 3270 LU in a configuration). Then you can modify the file and use it to add one or many similar elements to an existing configuration. Such a command file acts as a template for the element it contains.

Modifying a configuration

You can generate a snacfg command file that corresponds to some part of an existing configuration (for example, an 802.2 connection in a configuration), modify the command file, and use it to modify the configuration file that it came from. This involves removing the /add option from lines in the command file, and making other changes that require a detailed understanding of the commands in the file.


Displaying the Contents of a Configuration File
The Command-Line Interface	11 of 27

Displaying the Contents of a Configuration File

You can create a display of the entire contents of a configuration file, by using the /display option with the following syntax:

snacfg [#configpath] /display

When you use the /display option, all the resources in the configuration file are displayed. For each resource, the display is the same as that from typing snacfg resource resourcename, where resource is the second word of a snacfg command (for example, appcllu, connection, or server), and resourcename is the name of the corresponding resource. (The exception to this is that the display of the “diagnostic” resource is the same as that from snacfg diagnostic /list.)

Optionally, you can redirect the output of any of these commands, as described in “General Syntax for the /print Option,” earlier in this appendix.


Document Conventions
The Command-Line Interface	12 of 27

Document Conventions

In this appendix, the following conventions distinguish elements of text:

Convention	Purpose

UPPERCASE	Represents filenames and paths.

italic	Represents variables that appear in syntax and text.

bold	Represents portions of syntax that must be typed exactly as shown.

monospace	Represents examples and program code.

{ braces }	Enclose required items in syntax statements. For example, { yes | no } indicates that you must specify yes or no when  using the command. Type only the information within the braces,  not the braces themselves.

[ brackets ]	Enclose optional items in syntax statements. For example, [servername] indicates that you can choose to type a server name with the command. Type only the information within the brackets, not the brackets themselves.

| (vertical bar)	Stands for “or” and separates items within braces or brackets. For example, { high | low } means you must type high or low.

... (ellipsis)	In syntax statements, indicates that you can repeat the previous item(s). For example, /remove:LUname[,...] indicates that you can specify more than one LU name, separating the LU names with commas.


Snacfg APPCLLU
The Command-Line Interface	13 of 27

Snacfg APPCLLU

Purpose

Allows you add, delete, modify, or view a local APPC LU. Also allows you to view the command that would create a specified local APPC LU.

Note

Configuration settings specified with snacfg appcllu correspond to local APPC LU settings configured with SNA Server Admin. For detailed information about the settings, see: Chapter 6, “Configuring LUs for APPC.”

Syntax

snacfg [#configpath] appcllu /list

Recommended Syntax

snacfg [#configpath] appcllu servername:LUalias

snacfg [#configpath] appcllu LUalias /add /server:servername [options]

snacfg [#configpath] appcllu servername:LUalias [options]

snacfg [#configpath] appcllu servername:LUalias /delete

snacfg [#configpath] appcllu servername:LUalias /print

Other Available Syntax

snacfg [#configpath] appcllu /list

snacfg [#configpath] appcllu LUalias

snacfg [#configpath] appcllu LUalias [options]

snacfg [#configpath] appcllu LUalias /delete

snacfg [#configpath] appcllu LUalias /print

where

#configpath

Specifies the path of the configuration file to view or change. If the configuration path is omitted, SNA Server will attempt to access the configuration file on the local system, using the path \SNAroot\SYSTEM\CONFIG\COM.CFG, where SNAroot is the SNA Server root directory.

/list

Generates a list of configured local APPC LUs.

servername:LUalias

Specifies the server name and LU alias of the local APPC LU on which to carry out actions. It is recommended that servername: be included in snacfg appcllu commands (other than /add commands) that include LUalias. Without servername:, if there is more than one local LU called LUalias in the domain, it is difficult to predict which of these LUs will be affected by the command. The snacfg appcllu command does not necessarily default to the local server if servername is omitted.

See the following paragraphs for details about characters permitted in the LU alias.

If no options are specified after LUalias, the configuration settings, partner LUs, and modes are displayed for the specified LU.

LUalias

Specifies the LU alias of the local APPC LU on which to carry out actions. See the previous paragraphs and the syntax lists for recommendations about using the server name with the LU alias.

The LU alias 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.

Note that LUalias is used as the default LU name if /luname:text is not specified.

If no options are specified after LUalias, the configuration settings, partner LUs, and modes are displayed for the specified LU.

/add

Adds a local APPC LU called LUalias. To configure the LU, either specify other options after /add, or specify configuration options in additional snacfg appcllu commands (using the same LUalias).

/delete

Deletes the LU called LUalias.

/print

Causes the display of the snacfg command that would create the specified local APPC LU. The displayed command does not contain the word snacfg, so that it can be redirected to a command file.

options

Are as shown in the following list.

Options for Local APPC LUs

/server:servername

Specifies the server to which to assign or move the APPC LU. When /add is used, this option is required.

/lunumber:value

Specifies the LU number. If an LU number of 0 is specified, the LU is configured as an independent local APPC LU.

/netname:text

Specifies a name for the network of this LU. The name can be from one through eight characters long, and can contain alphanumeric characters and the special characters $, #, and @.

If /netname:text is not specified, the network name of the SNA server on which the LU is located is used as the default. Note that /luname:text also has a default (the LU alias). Therefore, the fully qualified LU name (network name plus LU name) can potentially be created by default, if the LU alias and local network name are configured appropriately. A fully qualified LU name is required for an APPC LU.

/luname:text

Specifies the LU name. 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 fully qualified LU Name (Network Name plus LU Name) must be unique on the server.

If /luname:text is not specified, LUalias is used as the default LU name. Note that /netname:text also has a default (the network name of the server on which the LU is located). Therefore, the fully qualified LU name (network name plus LU name) can potentially be created by default, if the LU alias and local network name are configured appropriately. A fully qualified LU name is required for an APPC LU.

/comment:"text"

Adds an optional comment for the LU. The comment can contain as many as 25 characters; enclose the comment in quotes.

/autopartner:{ yes | no }

Specifies whether this LU will automatically be partnered with other APPC LUs. For information on automatic partnering, see: Chapter 6, “Configuring LUs for APPC.”

If automatic partnering is left unspecified, the default is yes.

/defaultpool:{ yes | no }

Specifies whether this LU will be in the default outgoing local APPC LU pool. This pool makes LUs available for invoking TPs that do not specify a local LU. For more information, see: Chapter 6, “Configuring LUs for APPC.”

/impremotelu:remoteLUname

Specifies an existing remote LU to be used as an implicit incoming remote LU for the local LU. For information about implicit incoming remote LUs, see: Chapter 6, “Configuring LUs for APPC.”

/tptimeout:value

Specifies the number of seconds that SNA Server should wait for the invokable TP to respond to a start request from the invoking TP.

/addpartner:LUalias,mode[,connection]

Partners the local LU with the specified LU and the specified mode. Both LUalias and mode must exist before they can be specified as partners. If LUalias specifies a remote LU that is not unique on the server, the connection used by the remote LU must also be specified; otherwise, SNA Server will randomly choose one of the remote LUs called LUalias to act on.

Only one /addpartner option can be used in each command.

/delpartner:LUalias,mode[,connection]

Deletes the pair-listing that includes this local LU, the specified partner LU, and the specified mode. (Does not delete any LUs or modes themselves.) If LUalias specifies a remote LU that is not unique on the server, the connection used by the remote LU must also be specified; otherwise, SNA Server will randomly choose one of the remote LUs called LUalias to act on.

Only one /delpartner option can be used in each command.


Snacfg APPCRLU
The Command-Line Interface	14 of 27

Snacfg APPCRLU

Purpose

Allows you add, delete, modify, or view a remote APPC LU. Also allows you to view the command that would create a specified remote APPC LU.

Note

Configuration settings specified with snacfg appcrlu correspond to remote APPC LU settings configured with SNA Server Admin. For detailed information about the settings, see: Chapter 6, “Configuring LUs for APPC.”

Syntax

snacfg [#configpath] appcrlu /list

Recommended Syntax

snacfg [#configpath] appcrlu connectionname:LUalias

snacfg [#configpath] appcrlu LUalias /add /connection:connectionname [options]

snacfg [#configpath] appcrlu connectionname:LUalias [options]

snacfg [#configpath] appcrlu connectionname:LUalias /delete

snacfg [#configpath] appcrlu connectionname:LUalias /print

Other Available Syntax

snacfg [#configpath] appcrlu LUalias

snacfg [#configpath] appcrlu LUalias [options]

snacfg [#configpath] appcrlu LUalias /delete

snacfg [#configpath] appcrlu LUalias /print

where

#configpath

Specifies the path of the configuration file to view or change. If the configuration path is omitted, SNA Server will attempt to access the configuration file on the local system, using the path \SNAroot\SYSTEM\CONFIG\COM.CFG, where SNAroot is the SNA Server root directory.

/list

Generates a list of configured remote APPC LUs.

connectionname:LUalias

Specifies the connection and LU alias of the remote APPC LU on which to carry out actions. It is recommended that connectionname: be included in snacfg appcrlu commands (other than /add commands) that include LUalias. Without connectionname:, if there is more than one remote LU called LUalias in the domain, it is difficult to predict which of these LUs will be affected by the command. The snacfg appcrlu command does not necessarily default to a connection on the local server if connectionname is omitted.

See the following paragraphs for details about characters permitted in the LU alias.

If no options are specified after LUalias, the configuration settings, partner LUs, and modes are displayed for the specified LU.

LUalias

Specifies the LU alias of the remote APPC LU on which to carry out actions. See the previous paragraphs and the syntax lists for recommendations about using the connection name with the LU alias.

The LU alias 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 remote APPC LU, the LU alias must be unique on the connection, and must not match that of a local LU on that server.

If no options are specified after LUalias, the configuration settings, partner LUs, and modes are displayed for the specified LU.

/add

Adds a remote APPC LU called LUalias. To configure the LU, either specify other options after /add, or specify configuration options in additional snacfg appcrlu commands (using the same LUalias).

/delete

Deletes the LU called LUalias.

/print

Causes the display of the snacfg command that would create the specified remote APPC LU. The displayed command does not contain the word snacfg, so that it can be redirected to a command file. See the information about command files earlier in this appendix.

options

Are as shown in the following list.

Options for Remote APPC LUs

/connection:connectionname

Specifies the connection to which to assign or move the APPC LU. When /add is used, this option is required.

/netname:text

Specifies a name for the network of this LU. The name can be from one through eight characters long, and can contain alphanumeric characters and the special characters $, #, and @.

If /netname:text is not specified, the remote network name configured for the connection supporting this LU is used as the default. Note that /luname:text also has a default (the LU alias). Therefore, the fully qualified LU name (network name plus LU name) can potentially be created by default, if the LU alias and remote network name are configured appropriately. A fully qualified LU name is required for an APPC LU.

/luname:text

Specifies the LU name. 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 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.

If /luname:text is not specified, LUalias is used as the default LU name. Note that /netname:text also has a default (the remote network name configured for the connection supporting this LU). Therefore, the fully qualified LU name (LU name plus network name) can potentially be created by default, if the LU alias and remote control point name are configured appropriately. A fully qualified LU name is required for an APPC LU.

/comment:"text"

Adds an optional comment for the LU. The comment can contain as many as 25 characters; enclose the comment in quotes.

/autopartner:{ yes | no }

Specifies whether this LU will automatically be partnered with other APPC LUs. For information on automatic partnering, see: Chapter 6, “Configuring LUs for APPC.”

If automatic partnering is left unspecified, the default is yes.

/parallelsess:{ yes | no }

Specifies whether the remote LU supports parallel sessions.

/uninterpname:text

Specifies the uninterpreted LU name, which is required only when using dependent APPC. The name can be from one through eight characters long, and can contain alphanumeric characters and the special characters $, #, @ and period (.).

/impmode:modename

Designates modename as the implicit incoming mode for this LU. A mode must exist before being specified as an implicit incoming mode. For more information about implicit incoming modes, see: Chapter 6, “Configuring LUs for APPC.”

/security:{ none | hex,text | char,text }

Configures session security for a remote LU. The none option turns off session-level security. The hex,text option specifies a 16-digit security key in hexadecimal. The char,text option specifies an eight-character security key that can include uppercase and lowercase alphanumeric characters, and the special characters $, @, #, and the period (.).

/addpartner:LUalias,mode

Partners the remote LU with the specified local LU and the specified mode. Both the local LU and the mode must exist before they can be specified as partners. LUalias should specify a local LU, not a remote LU; otherwise, an error message is displayed, indicating that no such local LU can be found.

Only one /addpartner option can be used in each command.

/delpartner:LUalias,mode

Deletes the pair-listing that includes this remote LU, the specified local LU, and the specified mode. (Does not delete any LUs or modes themselves.)

Only one /delpartner option can be used in each command.


Snacfg Connection
The Command-Line Interface	15 of 27

Snacfg Connection

Purpose

Allows you to view, add, delete, or modify connections, including peer connections (necessary for APPC LUs) or downstream connections.

Before configuring a connection, you must configure the SNA server and link service the connection will use. For more information, see: “Task Order” earlier in this appendix.

Note

Configuration settings specified with snacfg connection correspond to connection settings configured with SNA Server Admin. For detailed information about the settings, see: Chapter 3, “Configuring Servers and Connections,” and Chapter 9, “Configuring Downstream Connections and LUs.”

Syntax

snacfg [#configpath] connection /list

snacfg [#configpath] connection connectionname

snacfg [#configpath] connection connectionname /add /server:servername
/conntype:{ 802.2 | sdlc | x25 | dft } [options]

snacfg [#configpath] connection connectionname [options]

snacfg [#configpath] connection connectionname /delete

where

#configpath

Specifies the path of the configuration file to view or change. If the configuration path is omitted, SNA Server will attempt to access the configuration file on the local system, using the path \SNAroot\SYSTEM\CONFIG\COM.CFG, where SNAroot is the SNA Server root directory.

/list

Generates a list of configured connections.

connectionname

Specifies a name for the connection to be configured or viewed. 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. A new connection name cannot be the same as any other connection name in the installation, and cannot be the reserved name SNASERVR.

If no options are specified after connectionname, the command-line interface displays a list of the configuration settings for the specified connection.

/add

Adds a connection called connectionname. To configure the connection, either specify other options after /add, or specify configuration options in additional snacfg connection commands (using the same connectionname).

/delete

Deletes connectionname.

options

Are as shown in the following lists.

Options Used with All Connection Types

/server:servername

Specifies the server to which to assign or move the connection. When /add is used, this option is required.

/conntype:{ 802.2 | sdlc | x25 | dft }

Specifies the connection type. When /add is used, this option is required.

/comment:"text"

Adds an optional comment for the specified connection. The comment can contain as many as 25 characters; enclose the comment in quotes.

/linkservice:linkname

Specifies the name of the link service to be used by connectionname. The link service type must match the connection type (802.2, SDLC, X.25, or DFT), or the snacfg command will not run.

In order for the link service to function correctly, it must be installed with SNA Server Setup, and then SNA Server Admin must be run once. Link services can also be installed with snacfg link; however, SNA Server Setup is the recommended interface for installing link services, because it helps ensure that the resulting configuration is functional.

/activation:{ onserverstartup | ondemand | byadministrator }

For outgoing calls on connectionname, tells how the connection will be activated: on server startup, on demand, or by the administrator. (For incoming calls, activation is irrelevant, since the connection always begins listening for calls on server startup.)

If no value has been specified for /activation, the default for 802.2 (token ring or Ethernet) and DFT connections is onserverstartup. For all other connections, the default is ondemand.

/localblockno:hexdigits

Specifies the local block number, a three-digit hexadecimal number. The local block number forms the first part of the Local Node ID, an eight-digit hexadecimal number that identifies the local system.

Do not use 000 or FFF for the local block number. These values are reserved.

For connections to host systems, the local block number should match IDBLK in VTAM.

/localnodeno:hexdigits

Specifies the local node number, a five-digit hexadecimal number. The local node number forms the last part of the Local Node ID, an eight-digit hexadecimal number that identifies the local system.

For connections to host systems, the local node number should match IDNUM in VTAM.

/cpname:text

Specifies the control point name of the remote node, as it is represented 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 control point name of the remote node works together with netname. If either of these parameters is supplied, the other should also be supplied.

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

/netname:text

Specifies the name of the network for the remote node, as it is represented 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 netname parameter works together with the control point name of the remote node. If either of these parameters is supplied, the other should also be supplied.

/remoteblockno:hexdigits

Specifies the remote block number, a three-digit hexadecimal number. The remote block number forms the first part of the Remote Node ID, an eight-digit hexadecimal number that identifies the remote system.

Do not use 000 or FFF for the remote block number. These values are reserved.

/remoteend:{ host | peer | downstream }

Specifies whether the connection is to be a host or peer connection.

/remotenodeno:hexdigits

Specifies the remote node number, a five-digit hexadecimal number. The remote node number forms the last part of the Remote Node ID, an eight-digit hexadecimal number that identifies the remote system.

/xidtype:{ format0 | format3 }

Specifies the XID type, the type of identifying information for SNA Server to send. The choices are format0 (Format 0) and format3 (Format 3). Format 0 sends only the Node ID. Format 3 sends up to 100 bytes of identifying information, including the local node ID and control point name. For a DFT connection, the xidtype option is ignored by SNA Server.

If no XID type has been specified, the default is format3.

Options Used with Downstream Connections

/insert:LUorPool[,...]

Assigns a downstream LU or pool to a downstream connection. Separate multiple LU or pool names with commas.

The downstream LU or pool named by LUorPool must already exist. (A downstream LU can be created with snacfg LUD, and a downstream pool can be created with snacfg poold.) The connection named by connectionname must be a downstream connection. If these conditions are not met, the command is not processed.

/remove:LUorPool[,...]

Removes the assignment of a downstream LU or pool to a downstream connection. Separate multiple LU or pool names with commas.

Options Used with 802.2 (Token Ring or Ethernet) Connections

/remotenetaddr:hexdigits

Specifies the 12-digit hexadecimal network address of the remote host that this connection provides access to.

If no remote network address has been specified, the default is 400000000000.

/remotesapaddr:hexdigits

Specifies the remote SAP address, which is a 2-digit hexadecimal number, a multiple of 4, between 04 and EC. A value of 04 is recommended for most installations.

If no remote SAP address has been specified, the default is 04.

/maxbtulen:value

Specifies the maximum length for the BTU, which is the number of bytes that can be transmitted in a single data-link control frame.

The range is from 265 through 16393. If no maximum BTU length has been specified, the default is 1929.

/receiveackthresh:value

Specifies the receive ACK threshold, the maximum number of frames that the local system can receive from the remote system before sending a response.

The range is from 1 through 127. If no receive ACK threshold has been specified, the default is 2.

/naksendlimit:value

Specifies the unacknowledged send limit, the maximum number of frames that the local system can send without receiving a response from the remote system.

The range is from 1 through 127. If no unacknowledged send limit has been specified, the default is 1.

/retrylimit:value

Specifies the retry limit, the number of times that the local system should retransmit a frame if no response is received from the remote system.

The range is from 0 through 255. A value of 0 means the system uses its internal default retry limit. If no retry limit has been specified, the default is 10.

/xidretries:value

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

The range is from 0 through 30. If no XID retries value has been specified, the default is 3.

/t1timeout:{ Default | 200ms | 400ms | 600ms | 800ms | 1s | 2s | 3s | 5s }

Specifies 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. For details about 802.2 time-outs, see: “List of Advanced 802.2 Settings” in Chapter 3.

The values used for Default for t1timeout are 400 milliseconds for a local ring and 2 seconds for a remote ring.

/t2timeout:{ Default | 40ms | 80ms | 120ms | 160ms | 200ms | 400ms | 800ms 	| 1200ms | 1600ms | 2000ms }

Select the maximum amount of time that should be allowed before the local system sends an acknowledgment of a received transmission. For details about 802.2 time-outs, see: “List of Advanced 802.2 Settings” in Chapter 3.

The values used for Default for t2timeout are 80 milliseconds for a local ring and 800 milliseconds for a remote ring.

/titimeout:{ Default | 1s | 2s | 3s | 4s | 5s | 10s | 15s | 20s | 25s }

Select the amount of time that the link can be inactive before the local system treats it as nonfunctioning and shuts it down. For details about 802.2 time-outs, see: “List of Advanced 802.2 Settings” in Chapter 3.

The values used for Default for titimeout are 5 seconds for a local ring and 25 seconds for a remote ring.

Options Used with SDLC Connections

/dialdata:value

Specifies the phone number stored for this connection. 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 — the dial data specifies the telephone number for SNA Server to send to the modem. In this case, the number should be in the format expected by the modem. For manually dialed modems, the dial data is displayed in a pop-up message when the connection is started, and can be in any format.

/encoding:{ nrzi | nrz }

Specifies the encoding scheme to be used by the modem. The choices are nrzi, nonreturn to zero inverted, and nrz, nonreturn to zero.

The modem must use the same encoding scheme as the modem at the remote computer. For connections to host systems, the encoding scheme must match the value in the LINE/GROUP definition in VTAM.

If no encoding scheme has been specified, the default is NRZI.

/duplex:{ half | full }

Specifies the modem duplex setting. The choices are half, for a half-duplex modem, and full, for a full-duplex modem. If you want to use the full-duplex setting, one or more of your adapters must have the constant carrier option set. The constant carrier option is set in SNA Server Setup, and takes effect after SNA Server Admin has been run once. The constant carrier option can also be set with snacfg link; however, SNA Server Setup is the recommended interface for setting the constant carrier option and other link service options.

Most SNA Server computers will use the default for duplex, half.

/datarate:{ high | low }

Specifies the data rate for transmissions between the SNA Server communications adapter and the modem. This rate can only be set for certain kinds of modems and adapters; for specific information, see the adapter and modem documentation.

A data rate of high gives faster transmissions; low gives more reliable transmissions and prevents the transmission errors sometimes caused by poor-quality lines at the high rate.

If no data rate has been specified, the default is high.

/polladdress:hexdigits

Specifies the poll address, a two-digit hexadecimal number. For connections to a host, the local poll address should match the VTAM PU definition for the ADDR= parameter.

Do not use 00 or FF for the poll address; these values are reserved. If no poll address has been specified, the default is C1.

/idletimeout:value

Specifies, in tenths of a second, the idle time-out. The idle time-out is the length of time that the local system should wait for the host to respond to a transmission, before the local system tries again. Too small a time-out can cause connection problems.

The range is from 1 (one-tenth of a second) through 300 (30 seconds). If no idle time-out has been specified, the default is 300 (30 seconds).

/idleretrylimit:value

Specifies the idle retry limit, the number of times the local system should try to poll or send data to the host if there is no response.

The range is from 1 through 255. If no idle retry limit has been specified, the default is 10.

/contacttimeout:value

Specifies the contact time-out: 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.

The range is from 5 (five-tenths of a second) through 300 (30 seconds). If no contact time-out has been specified, the default is 300 (30 seconds).

/contactretrylimit:value

Specifies contact retry limit, the maximum number of times the local system should attempt to make a given connection.

The range is from 1 through 20. If no contact retry limit has been specified, the default is 10.

/switchedconntimeout:value

Specifies the switched connection establishment time-out; used for switched SDLC lines (standard telephone lines) only. The switched connection establishment time-out is the number of seconds that will be allowed for the user or modem to dial the remote computer’s number.

This parameter is ignored by incoming calls.

The range is from 10 through 500 seconds. If no switched connection establishment time-out has been specified, the default is 300.

/multidropprimconn:{ yes | no }

Specifies whether this connection will be a multidrop primary connection.

A multidrop connection is one in which a primary node communicates with multiple secondary nodes concurrently over the same physical transmission medium.

/selectstandby:{ yes | no }

Specifies whether the modem’s standby line is set to on. Standby can only be set for certain kinds of modems; for specific information, see the modem documentation.

If no setting has been specified for standby, the default setting is no.

/sdlcmaxbtu:value

Specifies the maximum length for the BTU, which is the number of bytes that can be transmitted in a single data-link information frame.

The range is from 265 through 16393. If no maximum BTU length for SDLC has been specified, the default is 265.

Options Used with SDLC Peer Connections

/multidropprimconn:{ yes | no }

Specifies whether this server is to be the primary station for a multidrop connection on a leased SDLC line. For more information about multidrop connections, see: Chapter 3, “Configuring Servers and Connections.”

/pollrate:value

Specifies the poll rate in polls per second.

The range is from 1 through 50. If no poll rate has been specified, the default is 5.

Options Used with X.25 Connections

/remotex25addr:hexdigits

Specifies the remote X.25 address, which identifies the remote system on an X.25 network. The address usually consists of 12 hexadecimal digits, but can contain up to 15 hexadecimal digits.

/x25maxbtu:value

Specifies the maximum length for the BTU, which is the number of bytes that can be transmitted in a single data-link information frame.

The range is from 265 through 16393. If no maximum BTU length for X.25 has been specified, the default (for host connections) is 265.

/virtualcircuit:{ perm | switched }

Specifies the type of virtual circuit used by the connection. The choices are perm and switched. A perm circuit is constantly active and uses a preset destination address. A switched circuit is called and cleared dynamically, and uses a destination address that is supplied when the circuit is called.

If no virtual circuit type has been specified, the default is switched.

/pvcalias:value    (for PVC only)

Specifies the PVC alias, the number that identifies the PVC channel: 1 for the first channel, 2 for the second, and so on. Used for PVCs only.

The range is from 1 through the number of configured PVC channels. If no PVC alias has been specified, the default is 1.

/packetsize:value    (for PVC only)

Specifies packet size, the maximum number of data bytes (not header bytes) to be sent in a frame on this X.25 network. Used for PVCs only.

The possible values are 64, 128, 256, 512, and 1024. If no packet size has been specified, the default is 128.

/windowsize:value    (for PVC only)

Specifies window size, the maximum number of frames that the local system can send without receiving a response from the remote system, on this X.25 network. Used for PVCs only.

The range is from 1 through 7. If no window size has been specified, the default is 2.

/facilitydata:text    (for SVC only)

Specifies the codes for any facility data required by the network provider or by the administrator of the remote system. Used for SVCs only. Facility data can include as many as 126 hexadecimal characters (63 hexadecimal bytes).

Facility data is a coded string of information often used to request nondefault functions from the X.25 network for a particular SVC connection.

/userdata:text    (for SVC only)

Specifies the codes for any user data required by the network provider. Used for SVCs only. The user data must be an even number of hexadecimal characters, up to the maximum of 32 characters.

User data is 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).

The default for user data is C3; this specifies the QLLC protocol.


Snacfg CPIC
The Command-Line Interface	16 of 27

Snacfg CPIC

Purpose

Allows you add, delete, modify, or view a CPI-C symbolic destination name. Also allows you to view the command that would create a specified CPI-C symbolic destination name.

Note

Settings specified with snacfg cpic correspond to CPI-C symbolic destination names configured with SNA Server Admin. For detailed information about the settings, see: Chapter 6, “Configuring LUs for APPC.”

Syntax

snacfg [#configpath] cpic /list

snacfg [#configpath] cpic cpicname

snacfg [#configpath] cpic cpicname /add
{ /appltpname:text  |  /svcetpname:hexstring }
{ /b:text /luname:text  |  /lualias:text }
/modename:text
/seckeytype:{ none | same | program }
[/secuserid:text] [/secpassword:text] [/comment:"text"]

snacfg [#configpath] cpic cpicname [options]

snacfg [#configpath] cpic cpicname /delete

snacfg [#configpath] cpic cpicname /print

where

#configpath

Specifies the path of the configuration file to view or change. If the configuration path is omitted, SNA Server will attempt to access the configuration file on the local system, using the path \SNAroot\SYSTEM\CONFIG\COM.CFG, where SNAroot is the SNA Server root directory.

/list

Generates a list of configured symbolic destination names.

cpicname

Specifies the symbolic destination name on which to carry out actions. A symbolic destination name can be from one through eight characters long, and can contain alphanumeric characters and the special characters $, #, and @.

If no options are specified after cpicname, the configuration settings for the specified symbolic destination name are displayed.

/add

Adds a symbolic destination name called cpicname. When you use the /add option, you must include the other options shown in the preceding syntax.

/delete

Deletes cpicname.

/print

Causes the display of the snacfg command that would create the specified symbolic destination name. The displayed command does not contain the word snacfg, so that it can be redirected to a command file. See the information about command files earlier in this appendix.

options

Are as shown in the following list.

Options for CPI-C Commands

/comment:"text"

Adds an optional comment for the symbolic destination name. The comment can contain as many as 25 characters; enclose the comment in quotes.

Partner TP options (use one or the other, but not both):

/appltpname:text

Specifies that the partner TP is an application TP, and provides the name. 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.

If you specify both an application TP name and a service TP name in the same command, the command is rejected. If you specify an application TP for an existing symbolic destination name, it overrides any previous TP name (whether application TP or service TP).

/svcetpname:hexstring

Specifies that the partner TP is a service TP, and provides the hexadecimal string identifying the TP. The string can be from one through eight hexadecimal digits long.

If you specify both a service TP name and an application TP name in the same command, the command is rejected. If you specify a service TP for an existing symbolic destination name, it overrides any previous TP name (whether application TP or service TP).

Partner LU options (use one or the other, but not both):

/netname:text /luname:text

Identifies the partner LU by fully qualified LU name (network name plus LU name). Each part of the fully qualified 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.

If you specify both a fully qualified LU name and an LU alias in the same command, the command is rejected. If you specify a fully qualified LU name for an existing symbolic destination name, it overrides any previous LU setting (whether name or alias).

/lualias:text

Identifies the partner LU by LU alias. The alias can be from one through eight characters long, and can contain alphanumeric characters and the special characters %, $, #, and @. Lowercase letters are converted to uppercase.

If you specify both an LU alias and a fully qualified LU name in the same command, the command is rejected. If you specify an LU alias for an existing symbolic destination name, it overrides any previous LU setting (whether name or alias).

/modename:text

Specifies the mode. The mode must already exist.

/seckeytype:{ none | same | program }

Sets the conversation security type. If program is specified, one or both of the following options can be set:

/secuserid:text

Specifies the user ID to use when the security type is program. The ID can contain from 1 through 10 characters.

/secpassword:text

This parameter is optional; it specifies the password to use with the user ID. The password can contain from 1 through 10 characters. A password need not be specified even if the security type is program and the user ID is set. If a display is created showing the symbolic destination name, the password will not be displayed.


Snacfg Diagnostic
The Command-Line Interface	17 of 27

Snacfg Diagnostic

Purpose

Allows you to view and configure settings for event logging (auditing), and view or change the connection designated to receive NetView alerts.

Note

Configuration settings specified with snacfg diagnostic correspond to diagnostic settings configured with SNA Server Admin. For detailed information about the settings, see: Chapter 13, “Using Diagnostic Tools.”

Syntax

snacfg [#configpath] diagnostic /list

snacfg [#configpath] diagnostic [options]

where

#configpath

Specifies the path of the configuration file to view or change. If the configuration path is omitted, SNA Server will attempt to access the configuration file on the local system, using the path \SNAroot\SYSTEM\CONFIG\COM.CFG, where SNAroot is the SNA Server root directory.

/list

Generates a list that tells the settings for event logs (auditing), the name of the NetView management connection (if one has been specified), and the default connection for the DISPLAY verb (if one has been specified).

/logserver:servername

Specifies a centralized server on which event logs for this SNA Server installation should be stored.

If /logserver: is typed without servername, the setting reverts to the default, which is to store event logs for the local server on the local server.

/auditlevel:{ 6 | 8 | 10 | off }

Sets the level of SNA Server events to be recorded in the Windows NT event log. These events can be viewed with the Windows NT Event Viewer, which is described in the Windows NT documentation. The following table describes  the available levels:

Level		Description		Events to be recorded
6		Detailed problem analysis		All events that can be recorded
8		General information messages		General activity but not all events
10		Significant system events		Major events only
off		Auditing disabled		No events
/popupserver:servername

Specifies the server to which pop-up error messages for this SNA Server installation should be routed.

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

If /popupserver: is typed without servername, the setting reverts to the default, which is the local server.

/netviewconn:connectionname

Specifies the name of the connection through which NetView alerts are sent. The connection called connectionname must already exist.

If /netviewconn: is typed without connectionname, the setting is cleared, so that the configuration contains no NetView connection name.

/cnosdisplayconn:connectionname

Specifies the default connection to be used for the DISPLAY verb when no connection is provided. The connection called connectionname must already exist.

If /cnosdisplayconn: is typed without connectionname, the setting is cleared, so that the configuration contains no default connection for the DISPLAY verb.


Snacfg Link
The Command-Line Interface	18 of 27

Snacfg Link

Purpose

Allows you to view, delete, or modify link services. Can also be used to add link services, although SNA Server Setup is the recommended interface for adding link services.

Important

If you specify link service names or adapter properties with snacfg link, these names or properties must match existing names and properties in your installation, or a nonfunctioning configuration may result. To protect against errors with snacfg link, use SNA Server Setup instead.

Before configuring link services, you must use SNA Server Setup to add the SNA server on which the link services will be located. For more information, see: “Task Order” earlier in this appendix.

Note

Configuration settings specified with snacfg link correspond to link service settings configured with SNA Server Setup. For detailed information about SNA Server Setup, see: the Microsoft SNA Server Installation Guide.

Syntax

snacfg [#configpath] link /list

Recommended Syntax

snacfg [#configpath] link servername:linkname

snacfg [#configpath] link servername:linkname /add [options]

snacfg [#configpath] link servername:linkname [options]

snacfg [#configpath] link servername:linkname /delete

Other Available Syntax

snacfg [#configpath] link linkname

snacfg [#configpath] link linkname /add [options]

snacfg [#configpath] link linkname [options]

snacfg [#configpath] link linkname /delete

where

#configpath

Specifies the path of the configuration file to view or change. If the configuration path is omitted, SNA Server will attempt to access the configuration file on the local system, using the path \SNAroot\SYSTEM\CONFIG\COM.CFG, where SNAroot is the SNA Server root directory.

/list

Generates a list of configured link services.

servername

Specifies the name of the server on which to view or change link services. Separate the name of the server from the name of the link service with a colon (:). It is recommended that servername be included in every snacfg link command that includes linkname. Without servername, if there is more than one link service called linkname in the installation, it is difficult to predict which link service called linkname will be affected by the command. The snacfg link command does not necessarily default to the local server if servername is omitted.

linkname

Specifies the name of the link service to view, modify, or delete. Link services names can contain from one through eight alphanumeric characters.

For adding link services, the recommended method is to use SNA Server Setup, not snacfg link.

If no options are specified after linkname, the result is a list of the configuration settings for the specified link.

/add

Adds a link service called linkname. To configure the link service, either specify other options after /add, or specify configuration options in additional snacfg link commands (using the same servername:linkname combination).

For adding link services, the recommended method is to use SNA Server Setup, not snacfg link.

/delete

Deletes linkname.

options

Are as shown in the following list.

Options for Link Services

/server:servername

Specifies the server on which to install the link service.

/linktype:{ token | ether | sdlc | x25 | dft }

Specifies the type of adapter that linkname works with. The types are as follows: token corresponds to token ring, ether corresponds to Ethernet, sdlc corresponds to SDLC, x25 corresponds to X.25, and dft corresponds to DFT.

/linetype:{ leased | softdial | manual }    (for SDLC lines only)

Specifies the type of SDLC line (and, where applicable, the modem) that the link service will use:

A leased line is a telecommunications line committed solely to SDLC communications with a particular remote system.

A softdial line is a switched SDLC line on which the modem is dialed automatically by SNA Server. Such a modem must be attached to an SDLC adapter with a built-in serial (COM) port. Otherwise it is considered a manual modem.

A manual line is a switched SDLC line on which the modem stores a phone number, or on which the modem is dialed manually.

/carrier:{ on | off }    (for SDLC lines only)

Specifies whether the constant carrier option for an SDLC line is on or off.


Snacfg LU
The Command-Line Interface	19 of 27

Snacfg LU

Purpose

Allows you to view, add, delete, or modify 3270 LUs, on three types of connections: 802.2, SDLC, and/or X.25. Also allows you to assign 3270 LUs to LU pools that have already been configured.

Before configuring an LU, you must configure the connection that the LU will use. Also, before assigning an LU to an LU pool, you must create the LU and the LU pool. For more information, see: “Task Order” earlier in this appendix.

Note

Configuration settings specified with snacfg lu correspond to 3270 LU settings configured with SNA Server Admin. For detailed information about the settings, see: Chapter 4, “Configuring for 3270.”

Syntax

snacfg [#configpath] lu /list

snacfg [#configpath] lu luname

snacfg [#configpath] lu luname /add /connection:connectionname
/lunumber:value [options]

snacfg [#configpath] lu luname [options]

snacfg [#configpath] lu luname /delete

where

#configpath

Specifies the path of the configuration file to view or change. If the configuration path is omitted, SNA Server will attempt to access the configuration file on the local system, using the path \SNAroot\SYSTEM\CONFIG\COM.CFG, where SNAroot is the SNA Server root directory.

/list

Generates a list of configured 3270 LUs.

luname

Specifies the name of the 3270 LU to view, add, modify, or delete. A 3270 LU 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. A 3270 LU name cannot be the same as any other LU name or pool name (except for APPC LU names) on the server.

If no options are specified after luname, the result is a list of the configuration settings for the specified LU.

/add

Adds a 3270 LU called luname. To configure the 3270 LU, either specify other options after /add, or specify configuration options in additional snacfg lu commands (using the same luname).

/delete

Deletes luname.

options

Are as shown in the following list.

Options for 3270 LUs

/connection:connectionname

Specifies the connection to which the 3270 LU should be assigned or moved. When /add is used, this option is required.

/lunumber:value

Specifies the LU number, which identifies the LU on its connection. When /add is used, this option is required. 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 the NCP Gen on the host.

If the number you specify has already been assigned to an LU or an APPC LULU pair on the intended connection, the command fails.

The range is from 1 through 254.

/pool:poolname

Assigns or moves the 3270 LU to poolname. A 3270 LU can be assigned to only one pool.

The pool specified with poolname must already exist. A 3270 LU pool can be created with the snacfg pool command.

If /pool: is typed without poolname, the specified LU is removed from whichever pool it is assigned to.

/lutype:{ display | printer }

Specifies whether the 3270 LU will be used for display (terminal emulation) or a printer (that is, a local printer or a local-area network printer, attached to a PC).

If no LU type has been specified, the default is display.

/displaymodel:{ mod2 | mod3 | mod4 | mod5 | 2 | 3 | 4 | 5 }

Specifies the display model; applies only when the lutype is display. The following display types are available:

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.

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

When a 3270 display LU is assigned to a 3270 LU pool, the display model setting of the pool overrides the setting of the LU.

If no display model has been specified, the default is Model 2.

/allowmodeloverride:{ yes | no }

Specifies whether the user is allowed to override the display model type by using the 3270 terminal emulation program.

When a 3270 display LU is assigned to a 3270 LU pool, the model override setting of the pool overwrites the setting of the LU.

If no setting has been specified for this parameter, the default is no.

/comment:"text"

Adds an optional comment for the specified LU. The comment can contain as many as 25 characters; enclose the comment in quotes.


Snacfg LUA
The Command-Line Interface	20 of 27

Snacfg LUA

Purpose

Allows you to view, add, delete, or modify LUA LUs, on three types of connections: 802.2, SDLC, and/or X.25. Also allows you to assign LUA LUs to LU pools that have already been configured.

Before configuring an LU, you must configure the connection that the LU will use. Also, before assigning an LU to an LU pool, you must create the LU and the LU pool. For more information, see: “Task Order” earlier in this appendix.

Note

Configuration settings specified with snacfg lua correspond to LUA LU settings configured with SNA Server Admin. For detailed information about the settings, see: Chapter 8, “Configuring LUs for LUA.”

Syntax

snacfg [#configpath] lua /list

snacfg [#configpath] lua luname

snacfg [#configpath] lua luname /add /connection:connectionname
/lunumber:value [options]

snacfg [#configpath] lua luname [options]

snacfg [#configpath] lua luname /delete

where

#configpath

Specifies the path of the configuration file to view or change. If the configuration path is omitted, SNA Server will attempt to access the configuration file on the local system, using the path \SNAroot\SYSTEM\CONFIG\COM.CFG, where SNAroot is the SNA Server root directory.

/list

Generates a list of configured LUA LUs.

luname

Specifies the name of the LUA LU to view, add, modify, or delete. An LUA LU 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. An LUA LU name cannot be the same as any other LU name or pool name (except for APPC LU names) on the server.

If no options are specified after luname, the result is a list of the configuration settings for the specified LU.

/add

Adds an LUA LU called luname. To configure the LUA LU, either specify other options after /add, or specify configuration options in additional snacfg lua commands (using the same luname).

/delete

Deletes luname.

options

Are as shown in the following list.

Options for LUA LUs

/connection:connectionname

Specifies the connection to which the LUA LU should be assigned or moved. When /add is used, this option is required.

/lunumber:value

Specifies the LU number, which identifies the LU on its connection. When /add is used, this option is required. 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 the NCP Gen on the host.

If the number you specify has already been assigned to an LU or an APPC LULU pair on the intended connection, the command fails.

The range is from 1 through 254.

/pool:poolname

Assigns or moves the LUA LU to poolname. An LUA LU can be assigned to only one pool. The pool specified with poolname must already exist. An LUA LU pool can be created with the snacfg poola command.

If /pool: is typed without poolname, the specified LU is removed from whichever pool it is assigned to.

/highpriority:{ yes | no }

Specifies whether this LU will be given priority over low-priority LUs.

When an LUA LU is assigned to an LUA LU pool, the priority setting of the pool overwrites the priority setting of the LU.

/comment:"text"

Adds an optional comment for the specified LU. The comment can contain as many as 25 characters; enclose the comment in quotes.


Snacfg LUD
The Command-Line Interface	21 of 27

Snacfg LUD

Purpose

Allows you to view, add, delete, or modify downstream LUs. Also allows you to assign downstream LUs to LU pools that have already been created, and allows you to view the command that would create a specified downstream LU.

Note

Configuration settings specified with snacfg lud correspond to downstream LU settings configured with SNA Server Admin. For detailed information about the following settings, see: Chapter 9, “Configuring Downstream Connections and LUs.”

Syntax

snacfg [#configpath] lud /list

snacfg [#configpath] lud luname

snacfg [#configpath] lud luname /add /connection:connectionname
/lunumber:value [options]

snacfg [#configpath] lud luname [options]

snacfg [#configpath] lud luname /delete

snacfg [#configpath] lud luname /print

where

#configpath

Specifies the path of the configuration file to view or change. If the configuration path is omitted, SNA Server will attempt to access the configuration file on the local system, using the path \SNAroot\SYSTEM\CONFIG\COM.CFG, where SNAroot is the SNA Server root directory.

/list

Generates a list of configured downstream LUs.

luname

Specifies the name of the downstream LU to view, add, modify, or delete. A downstream LU 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 pool name that uses this connection.

If no options are specified after luname, the result is a list of the configuration settings for the specified LU.

/add

Adds a downstream LU called luname. To configure the downstream LU, either specify other options after /add, or specify configuration options in additional snacfg lud commands (using the same luname).

/delete

Deletes luname.

/print

Causes the display of the snacfg command that would create the specified downstream LU. The displayed command does not contain the word snacfg, so that it can be redirected to a command file. See the information about command files earlier in this appendix.

options

Are as shown in the following list.

Options for Downstream LUs

/connection:connectionname

Specifies the connection to which the downstream LU should be assigned or moved. When /add is used, this option is required.

/lunumber:value

Specifies the LU number, which identifies the LU on its connection. When /add is used, this option is required. Check with the administrator of the host system for the correct value; it should match the LOCADDR= parameter of the LU definition in VTAM [image] or in the NCP Gen.

The LU number identifies the LU to the host system. To adjust the number that identifies the LU to the downstream system, use SNA Server Admin, as described in Chapter 9, “Configuring Downstream Connections and LUs.”

If the number you specify has already been assigned to an LU or an APPC LULU pair on the intended connection, the command fails.

The range is from 1 through 254.

/pool:poolname

Assigns or moves the downstream LU to poolname. A downstream LU can be assigned to only one pool. The pool specified with poolname must already exist. A downstream LU pool can be created with the snacfg poold command.

If /pool: is typed without poolname, the specified LU is removed from whichever pool it is assigned to.

/comment:"text"

Adds an optional comment for the specified LU. The comment can contain as many as 25 characters; enclose the comment in quotes.


Snacfg Mode
The Command-Line Interface	22 of 27

Snacfg Mode

Purpose

Allows you add, delete, modify, or view an APPC mode. Also allows you to view the command that would create a specified mode.

Note

Configuration settings specified with snacfg mode correspond to APPC mode settings configured with SNA Server Admin. For detailed information about the settings, see: Chapter 6, “Configuring LUs for APPC.”

Syntax

snacfg [#configpath] mode /list

snacfg [#configpath] mode modename

snacfg [#configpath] mode modename /add [options]

snacfg [#configpath] mode modename [options]

snacfg [#configpath] mode modename /delete

snacfg [#configpath] mode modename /print

where

#configpath

Specifies the path of the configuration file to view or change. If the configuration path is omitted, SNA Server will attempt to access the configuration file on the local system, using the path \SNAroot\SYSTEM\CONFIG\COM.CFG, where SNAroot is the SNA Server root directory.

/list

Generates a list of configured modes.

modename

Specifies the name of the mode on which to carry out actions. A mode 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 mode name cannot be the same as any other mode name in the domain of the server.

If no options are specified after modename, the configuration settings for the specified mode are displayed.

/add

Adds a mode called modename. To configure the mode, either specify other options after /add, or specify configuration options in additional snacfg mode commands (using the same modename).

/delete

Deletes modename.

/print

Causes the display of the snacfg command that would create the specified mode. The displayed command does not contain the word snacfg, so that it can be redirected to a command file. See the information about command files earlier in this appendix.

options

Are as shown in the following list.

Options for APPC Modes

/comment:"text"

Adds an optional comment for the mode. The comment can contain as many as 25 characters; enclose the comment in quotes.

/sessionlim:value

Specifies the parallel session limit.

The range is from 1 through 254. If no parallel session limit has been specified, the default is 1.

/conwin:value

Specifies the minimum contention winner limit.

The range is from 0 through the parallel session limit. If no minimum contention winner limit has been specified, the default is 0.

/conlose:value

Specifies the partner minimum contention winner limit.

The range is from 0 through the parallel session limit. If no partner minimum contention winner limit has been specified, the default is 0.

/autoact:value

Specifies the automatic activation limit.

The range is from 0 through the minimum contention winner limit.

/autopartner:{ yes | no }

Specifies whether this mode will be used in automatic partnering of APPC LUs. For information on automatic partnering, see: Chapter 6, “Configuring LUs for APPC.”

If automatic partnering is left unspecified, the default is yes.

/highpriority:{ yes | no }

Specifies whether communication with this mode will be given preference over low-priority communication.

If the high-priority setting is left unspecified, the default is yes.

/pacesendcnt:value

Specifies the pacing send count. A value of 0 represents an unlimited number of frames.

The range is from 0 through 63. If no pacing send count has been specified, the default is 4.

/pacerecvcnt:value

Specifies the pacing receive count. A value of 0 represents an unlimited number of frames.

The range is from 0 through 63. If no pacing receive count has been specified, the default is 4.

/maxsendru:value

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

The range is from 256 through 16384. If no maximum send RU size has been specified, the default is 1024.

/maxrecvru:value

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

The range is from 256 through 16384. If no maximum receive RU size has been specified, the default is 1024.


Snacfg Pool
The Command-Line Interface	23 of 27

Snacfg Pool

Purpose

Allows you to view, add, delete, or modify 3270 LU pools.

To assign existing 3270 LUs to a 3270 LU pool, first configure the pool with the snacfg pool command (including options), then add the LUs with the snacfg lu command (using the /pool:poolname option).

Note

Configuration settings specified with snacfg pool correspond to 3270 LU pool settings configured with SNA Server Admin. For detailed information about the settings, see: Chapter 10, “Using LU Pools to Maximize Access.”

Syntax

snacfg [#configpath] pool /list

snacfg [#configpath] pool poolname

snacfg [#configpath] pool poolname /add [options]

snacfg [#configpath] pool poolname [options]

snacfg [#configpath] pool poolname /delete

where

#configpath

Specifies the path of the configuration file to view or change. If the configuration path is omitted, SNA Server will attempt to access the configuration file on the local system, using the path \SNAroot\SYSTEM\CONFIG\COM.CFG, where SNAroot is the SNA Server root directory.

/list

Generates a list of configured 3270 LU pools.

poolname

Specifies the name of the 3270 LU pool to view, add, modify, or delete. 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 pool name or LU name (other than APPC LU names) in the installation.

If no options are specified after poolname, the result is a list of the configuration settings for the specified pool.

/add

Adds a 3270 LU pool called poolname. To configure the 3270 LU pool, either specify other options after /add, or specify configuration options in additional snacfg pool commands (using the same poolname).

/delete

Deletes poolname.

options

Are as shown in the following list.

Options for 3270 LU Pools

/displaymodel:{ mod2 | mod3 | mod4 | mod5 | 2 | 3 | 4 | 5 }

Specifies the model number of the LUs that will be added to this pool. (Only display LUs can be pooled; printer LUs cannot be pooled.) The following display models are available:

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.

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

The display model setting of a pool overwrites the setting of any 3270 LU assigned to the pool.

If no display model has been specified for a pool, the default is Model 2.

/allowmodeloverride:{ yes | no }

Specifies whether the user is allowed to override the display model type of the LU by using the 3270 terminal emulation program.

The model override setting of a pool overwrites the setting of any 3270 LU assigned to the pool.

If no setting has been specified for this parameter, the default is no.

/comment:"text"

Adds an optional comment to the specified 3270 LU pool. The comment can contain as many as 25 characters; enclose the comment in quotes.


Snacfg PoolA
The Command-Line Interface	24 of 27

Snacfg PoolA

Purpose

Allows you to view, add, delete, or modify LUA LU pools.

To assign existing LUA LUs to an LUA LU pool, first configure the pool with the snacfg poola command (including options), then add the LUs with the snacfg lua command (using the /pool:poolname option).

Note

Configuration settings specified with snacfg poola correspond to LUA LU pool settings configured with SNA Server Admin. For detailed information about the settings, see: Chapter 10, “Using LU Pools to Maximize Access.”

Syntax

snacfg [#configpath] poola /list

snacfg [#configpath] poola poolname

snacfg [#configpath] poola poolname /add [options]

snacfg [#configpath] poola poolname [options]

snacfg [#configpath] poola poolname /delete

where

#configpath

Specifies the path of the configuration file to view or change. If the configuration path is omitted, SNA Server will attempt to access the configuration file on the local system, using the path \SNAroot\SYSTEM\CONFIG\COM.CFG, where SNAroot is the SNA Server root directory.

/list

Generates a list of configured LUA LU pools.

poolname

Specifies the name of the LUA LU pool to view, add, modify, or delete. 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 pool name or LU name (other than APPC LU names) in the installation.

If no options are specified after poolname, the result is a list of the configuration settings for the specified pool.

/add

Adds an LUA LU pool called poolname. To configure the LUA LU pool, either specify other options after /add, or specify configuration options in additional snacfg poola commands (using the same poolname).

/delete

Deletes poolname.

options

Are as shown in the following list.

Options for LUA LU Pools

/highpriority:{ yes | no }

Specifies whether LUs in this pool will be given priority over low-priority LUs. The priority setting of a pool overwrites the setting of any LUA LU assigned to the pool.

/comment:"text"

Adds an optional comment to the specified LUA LU pool. The comment can contain as many as 25 characters; enclose the comment in quotes.


Snacfg PoolD
The Command-Line Interface	25 of 27

Snacfg PoolD

Purpose

Allows you to view, add, or delete downstream LU pools. Also allows you to view the command that would create a specified downstream LU pool.

To assign existing downstream LUs to a downstream LU pool, first configure the pool with the snacfg poold command; then add the LUs with the snacfg lud command (using the /pool:poolname option).

Syntax

snacfg [#configpath] poold /list

snacfg [#configpath] poold poolname

snacfg [#configpath] poold poolname [/add] [/comment:"text"]

snacfg [#configpath] poold poolname /delete

snacfg [#configpath] poold poolname /print

where

#configpath

Specifies the path of the configuration file to view or change. If the configuration path is omitted, SNA Server will attempt to access the configuration file on the local system, using the path \SNAroot\SYSTEM\CONFIG\COM.CFG, where SNAroot is the SNA Server root directory.

/list

Generates a list of configured downstream LU pools.

poolname

Specifies the name of the downstream LU pool to view, add, or delete. 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 pool name or LU name (other than APPC LU names) in the domain.

If no options are specified after poolname, the result is a list of the configuration settings for the specified pool.

/add

Adds a downstream LU pool called poolname.

/delete

Deletes poolname.

/print

Causes the display of the snacfg command that would create the specified downstream LU pool. The displayed command does not contain the word snacfg, so that it can be redirected to a command file. See the information about command files earlier in this appendix.

/comment:"text"

Adds an optional comment to the specified downstream LU pool. The comment can contain as many as 25 characters; enclose the comment in quotes.


Snacfg Server
The Command-Line Interface	26 of 27

Snacfg Server

Purpose

Allows you to view or change settings for SNA servers. Can also be used to add an SNA server, although SNA Server Setup is the recommended interface for adding servers.

Note

Configuration settings specified with snacfg server correspond to server settings configured with SNA Server Setup and SNA Server Admin. For detailed information about the settings, see: Chapter 3, “Configuring Servers and Connections,” and the Microsoft SNA Server Installation Guide.

Syntax

snacfg [#configpath] server /list

snacfg [#configpath] server servername

snacfg [#configpath] server servername /add  [options]

snacfg [#configpath] server servername  [options]

snacfg [#configpath] server servername /delete

where

#configpath

Specifies the path of the configuration file to view or change. If the configuration path is omitted, SNA Server will attempt to access the configuration file on the local system, using the path \SNAroot\SYSTEM\CONFIG\COM.CFG, where SNAroot is the SNA Server root directory.

/list

Generates a list of the SNA servers on the local domain.

servername

Specifies the computer name of the server on which settings will be viewed or changed.

/add

Adds an SNA server called servername. For adding a server, the recommended method is to use SNA Server Setup, not snacfg server.

Before the SNA server can have connections added to it, link services must also be configured for the server. The recommended interface for configuring link services is SNA Server Setup, which is described in: the Microsoft SNA Server Installation Guide.

/delete

Deletes servername.

Options for Servers

/netname:text

Specifies the local network name, which identifies the SNA network of the local SNA server. 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. If the local network name is specified, the local control point name must also be specified (using the /cpname option).

/cpname:text

Specifies the local control point name, which identifies the local system to other control points (nodes) on the SNA network. The name can be from one through eight characters long, and can contain alphanumeric characters and the special characters $, #, and @. If the local control point name is specified, the local network name must also be specified (using the /netname option).

When connecting to a host system and using a local control point name, the name should match the CPNAME = parameter in the host’s PU definition.

/comment:"text"

Adds an optional comment for the specified SNA server. The comment can contain as many as 25 characters; enclose the comments in quotes.


Snacfg User
The Command-Line Interface	27 of 27

Snacfg User

Purpose

Allows you to view, modify settings for, or delete users recognized by SNA Server. Also allows you to assign LUs or LU pools to 3270 users, or assign default LUs to 5250 users.

In addition, snacfg user allows you to add users to the list recognized by SNA Server. However, it is recommended that you use SNA Server Admin, not snacfg user, when adding users.

Important

If you add user names by using the /add option with snacfg user, these names must match existing user account names in the domain, or a nonfunctioning configuration may result. To protect against errors with snacfg user, use SNA Server Admin instead.

Before assigning LUs or LU  pools to users, you must first configure the LUs or LU  pools. For more information, see: “Task Order” earlier in this appendix.

Note

Configuration settings specified with snacfg user correspond to user or group settings configured with SNA Server Admin. For detailed information about the settings, see: Chapter 4, “Configuring for 3270,” or Chapter 6, “Configuring LUs for APPC.”

Syntax

snacfg [#configpath] user /list

snacfg [#configpath] user username

snacfg [#configpath] user username /add [options]

snacfg [#configpath] user /validate

snacfg [#configpath] user username [options]

snacfg [#configpath] user username /delete

where

#configpath

Specifies the path of the configuration file to view or change. If the configuration path is omitted, SNA Server will attempt to access the configuration file on the local system, using the path \SNAroot\SYSTEM\CONFIG\COM.CFG, where SNAroot is the SNA Server root directory.

/list

Generates a list of the 3270 users recognized by SNA Server.

username

Specifies the name of the user to view, change settings for, or delete.

For adding 3270 users, the recommended method is to use SNA Server Admin, not snacfg user. If you are adding a user, username must match the name in the user’s account on the domain or on the local system.

/add

Adds a user called username to the list of 3270 users recognized by SNA Server. The user must already have an account on the domain or on the local system.

For adding 3270 users, the recommended method is to use SNA Server Setup, not snacfg user.

/validate

Attempts to fill in any SIDs that are missing from user or group listings in the SNA Server configuration file. If the SIDs can be obtained from user accounts in the domain for each user, the SIDs will be added to the listings in the SNA Server configuration.

Run snacfg user /validate after working offline and adding users to the configuration, so that the user listings in SNA Server will be functional.

/delete

Deletes username.

options

Are as shown in the following list.

Options for Users of 3270 Emulators

/insert:LUorPool[,...]

Assigns the specified 3270 LU or LU pool to the user. Separate multiple LU or LU pool names with commas.

/remove:LUorPool[,...]

Deletes the assignment of a 3270 LU or LU pool to a user. Separate multiple LU or LU pool names with commas.

/domain:domainname

Specifies the domain in which the user account is found. For all actions involving the domain name associated with a user account, the recommended method is to use SNA Server Admin, not snacfg user. If an incorrect domain name is specified with snacfg user, a nonfunctioning configuration may result.

/comment:"text"

Adds an optional comment for the specified user. The comment can contain as many as 25 characters.

Options for Users of TPs or 5250 Emulators

/defloclu:LUalias

Specifies the default local APPC LU for this user or group. Both the user (or group) name and the LU alias must already be configured in SNA Server. If /defloclu: is typed without LUalias, the user or group record is cleared of any default local LU.

/defremlu:LUalias

Specifies the default remote APPC LU for this user or group. Both the user (or group) name and the LU alias must already be configured in SNA Server. If /defremlu: is typed without LUalias, the user or group record is cleared of any default remote LU.