Copyright: Managing SNA Server
Citation: Managing SNA Server


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


Managing Microsoft SNA Server Contents
Microsoft SNA Server

Managing Microsoft SNA Server

Contents

Chapter 1	IBM Systems Network Architecture

Chapter 2	Microsoft SNA Server Overview

Chapter 3	Designing the Configuration

Chapter 4	Installing the Microsoft SNA Server

Chapter 5	Configuring the Microsoft SNA Server

Chapter 6	Installing the Client

Chapter 7	Diagnostic Tools


Managing Microsoft SNA Server Contents
Microsoft SNA Server

Managing Microsoft SNA Server

Contents

Chapter 1	IBM Systems Network Architecture

Overview

What You Will Learn

IBM Systems Network Architecture

The Evolution of SNA

SNA and Microsoft Windows NT Technology

SNA Model #1: Hierarchical SNA

The Hierarchical Model

SNA Server in the Hierarchical Model

SNA Model #2: Peer-Oriented SNA

The Peer-Oriented Model

Advanced Peer-to-Peer Networking

Microsoft SNA Server in the Peer-Oriented SNA Model

Finding More Information

Chapter 2	Microsoft SNA Server Overview

Chapter 3	Designing the Configuration

Chapter 4	Installing the Microsoft SNA Server

Chapter 5	Configuring the Microsoft SNA Server

Chapter 6	Installing the Client

Chapter 7	Diagnostic Tools


Managing Microsoft SNA Server Contents
Microsoft SNA Server

Managing Microsoft SNA Server

Contents

Chapter 1	IBM Systems Network Architecture

Chapter 2	Microsoft SNA Server Overview

What You Will Learn

The Microsoft SNA Server

Connecting to the Network

Data Link Types

Microsoft SNA Server Functions

IBM SNA Network Access

IBM Mainframe Access

IBM AS/400 Access

SNA Server Components

Server Side Architecture

Client Side Architecture

Finding Additional Information

Chapter 3	Designing the Configuration

Chapter 4	Installing the Microsoft SNA Server

Chapter 5	Configuring the Microsoft SNA Server

Chapter 6	Installing the Client

Chapter 7	Diagnostic Tools


Managing Microsoft SNA Server Contents
Microsoft SNA Server

Managing Microsoft SNA Server

Contents

Chapter 1	IBM Systems Network Architecture

Chapter 2	Microsoft SNA Server Overview

Chapter 3	Designing the Configuration

Overview

What You Will Learn

Planning

Defining Server Goals

The Sample Installation

Verifying Compliance with System Requirements

Preparing the IBM SNA Host for Installation

Completing the Forms

Finding Additional Information

Chapter 4	Installing the Microsoft SNA Server

Chapter 5	Configuring the Microsoft SNA Server

Chapter 6	Installing the Client

Chapter 7	Diagnostic Tools


Managing Microsoft SNA Server Contents
Microsoft SNA Server

Managing Microsoft SNA Server

Contents

Chapter 1	IBM Systems Network Architecture

Chapter 2	Microsoft SNA Server Overview

Chapter 3	Designing the Configuration

Chapter 4	Installing the Microsoft SNA Server

Overview

What You Will Learn

Installation Overview

The Setup Program

Using the SNA Server Setup Program

Installing an SNA Server

Installing a Link Service

Chapter 5	Configuring the Microsoft SNA Server

Chapter 6	Installing the Client

Chapter 7	Diagnostic Tools


Managing Microsoft SNA Server Contents
Microsoft SNA Server

Managing Microsoft SNA Server

Contents

Chapter 1	IBM Systems Network Architecture

Chapter 2	Microsoft SNA Server Overview

Chapter 3	Designing the Configuration

Chapter 4	Installing the Microsoft SNA Server

Chapter 5	Configuring the Microsoft SNA Server

Overview

What You Will Learn

The Configuration Process

Configuring Servers

Configuring Connections

Connection Properties

Basic 802.2 Settings

After Configuring Basic Settings

Basic SDLC Settings

After Configuring Basic Settings

Basic X.25 Settings

After Configuring Basic Settings

Configuring LUs

Configuring 3270 LUs

Configuring Properties for a 3270 LU

Configuring a Range of 3270 LUs

User and Group Access for 3270

Configuring Properties for a 3270 User or Group

Using 3270 LU Pools

LU Pooling

Configuring for APPC (LU6.2)

Assigning a Local APPC LU

Configuring Local APPC LU Properties

Assigning a Remote APPC LU

Configuring Remote APPC Properties

Configuring Modes

Mode Properties

User and Groups Designation and Assigning Default APPC

AS/400 Configuration Considerations for APPC

Configuring Downstream Connections and LUs

Configuring Individual Downstream LUs

Configuring Properties for a Downstream LU

Associating Downstream LUs with a Downstream Connection

Management of the SNA Server

Starting and Stopping SNA Servers and Connections

Changing the Domain of Focus

Configuring for NetView

Chapter 6	Installing the Client

Chapter 7	Diagnostic Tools


Managing Microsoft SNA Server Contents
Microsoft SNA Server

Managing Microsoft SNA Server

Contents

Chapter 1	IBM Systems Network Architecture

Chapter 2	Microsoft SNA Server Overview

Chapter 3	Designing the Configuration

Chapter 4	Installing the Microsoft SNA Server

Chapter 5	Configuring the Microsoft SNA Server

Chapter 6	Installing the Client

Windows NT-Based Client Installation

Installing a Client Running Windows Version 3.1

OS/2 Client Installation

Installing an MS-DOSBased Client

Client Option Modification

Modifying a Client Running Windows NT or Windows Version 3.1

Modifying a Client Running MS-DOS or OS/2

Removing Clients

Finding Additional Information

Chapter 7	Diagnostic Tools


Managing Microsoft SNA Server Contents
Microsoft SNA Server

Managing Microsoft SNA Server

Contents

Chapter 1	IBM Systems Network Architecture

Chapter 2	Microsoft SNA Server Overview

Chapter 3	Designing the Configuration

Chapter 4	Installing the Microsoft SNA Server

Chapter 5	Configuring the Microsoft SNA Server

Chapter 6	Installing the Client

Chapter 7	Diagnostic Tools

Overview

What You Will Learn

Diagnostic Information Tools

SNA Server Admin

Windows NT Event Viewer Utility

SNA Server Trace

Windows NT Performance Monitor Utility

Response Time Monitor (RTM)

SNA Server NetView Options

Example of NVALERT.INI Section


IBM Systems Network Architecture
Chapter 1	1 of 6

IBM Systems Network Architecture

Overview

This chapter introduces the IBM [image] Systems Network Architecture (SNA) and how the Microsoft [image] SNA Server (SNA Server) fits into an SNA network. This information will provide you with the knowledge base to prepare, configure, and manage your SNA Server installation.


What You Will Learn
IBM Systems Network Architecture	2 of 6

Overview

What You Will Learn

After completing this chapter, you will be able to:

Describe what SNA is and its place within the realm of computer networking.

Describe the two major directions of evolution in SNA.

Understand and position the unique elements within each architecture.

Understand what functions the SNA Server can provide in accessing SNA networks.

Position the SNA Server within an SNA environment.


IBM Systems Network Architecture
IBM Systems Network Architecture	3 of 6

Overview

IBM Systems Network Architecture

IBM SNA is a computer networking architecture defined and developed by IBM to allow the networking of IBM hardware and software into integrated systems.

Originally defined in the early 1970s, SNA was well received and widely implemented. Today, there are more than 50,000 SNA-based networks in operation globally. As an architecture, SNA defines a set of standards for communication protocols and message formats.

This definition allows for the development of compatible software and hardware products, which can then be integrated into SNA networks.

Although the architecture is proprietary (that is, it was defined and is controlled by a single vendor, IBM), it is well documented and widely understood. This documentation level enables vendors other than IBM to design and create SNA-compatible devices. The Microsoft SNA Server is such a product.

The Evolution of SNA

SNA was originally designed in the era defined by very expensive computing hardware. In the 1970s, data processing environments were characterized by centrally located mainframe processors, whose resources were shared among networks of dumb, single-purpose devices such as CRT terminals, line printers, and card readers. By sequentially utilizing slices of the Central Processing Unit (CPU), called time-sharing, each of these dumb devices could inexpensively share in the intelligence provided by the CPU. The original and traditional architectural direction of SNA is based upon this model, in which economically precious CPU resources are shared among less intelligent, less expensive attached devices. This can be regarded as a hierarchical model.

In the 1980s, new, radically cheaper CPUs were developed and introduced, making possible the success of the personal computer (PC) and of midrange, department-oriented, multiuser computers.

This revolution brought the price range of computing resources to a level at which the intelligent desktop became possible. No longer did an individual user or department need to depend upon time-sharing of a central CPU for their computer needs.

To share information among intelligent desktops, new computer networking models have been developed. These new models utilize distributed processing rather than central processing, and so are peer-oriented rather than hierarchical.

IBM SNA architecture has evolved along with the evolution of contemporary, peer-oriented networks. Current SNA models, and IBM's announced future evolution of the SNA, emphasize this peer-oriented model of communication and of distributed computing.

SNA and Microsoft Windows NT Technology

Today, an enormous legacy exists in the form of existing IBM SNA networks, of the software applications developed to run within the IBM hosts in SNA networks, and of the data stored in those IBM hosts. While industry analysts differ in their opinion of the long-term future of the traditional IBM-style mainframe, they agree on this: For the foreseeable future, IBM mainframe environments will continue to play a key role within business, industry, and government, partly because of the difficulties and expenses entailed by the migration of these applications and data to other computer environments.

The Microsoft SNA Server allows users and programs within a contemporary, distributed network to access IBM SNA networks and computers.

Specifically, existing SNA Server and client applications provide the following functionality for accessing IBM SNA networks and computers:

Access to IBM S/370 [image] and S/390 [image] mainframes by emulation of the standard IBM 3278 Terminal

Access to IBM AS/400 [image] computers by emulation of the standard IBM 5250 Terminal

The ability to print data from the IBM SNA host at a local printer, or at a network printer within the Windows NT [image] environment

The ability to transfer files to and from the IBM host environment via the standard IND$FILE file transfer protocol

Direct program-to-program communications between applications running in the Windows NT environment and applications running in the SNA environment

Future enhancements to the SNA Server family of products, provided by Microsoft or by third-party vendors, could provide:

Very high-speed file transfer.

Transparent interaction between databases in the Windows NT and SNA environments.

The ability for IBM users to log on to Windows NT-based applications.

Other services to provide full, bidirectional communications.


SNA Model #1: Hierarchical SNA
IBM Systems Network Architecture	4 of 6

Overview

SNA Model #1: Hierarchical SNA

The Hierarchical Model

A hierarchical model is the traditional SNA. It is a vertical architecture, in which each device talks to a more intelligent device above it and a less intelligent device below it. This is the model that evolved as a solution to how best to share expensive computing resources.

At the top of the hierarchy is the traditional IBM mainframe. In the standard terminology of SNA, the mainframe is a Physical Unit Type 5 (PU5). The actual computing in a traditional SNA network happens in the PU5; applications run here, such as:

TSO (Time Sharing Option).

NetView [image] (IBM's SNA network management package).

VTAM [image] (Virtual Telecommunications Access Method).

Databases such as DB2 [image], and so on.

User developed applications.

The next level in the hierarchy is typically an IBM front end processor (FEP). In the standard terminology of an SNA, the FEP is a Physical Unit Type 4 (PU4). The FEP is dedicated to managing the telecommunications networking by which the PU5 communicates to users, devices, and applications throughout the SNA network. The FEP is directly cabled to the PU5 via a high-speed electrical or optoelectrical channel connection. The PU4 contains a high level of computer intelligence, all of which is dedicated to managing I/O to the PU5 CPU.

Next in a typical SNA hierarchy would be found an IBM cluster controller, known as a Physical Unit Type 2 (PU2). The cluster controller communicates with the PU4 via a datalink over a telephone line, token ring, local cable, or other physical medium. The cluster controller provides the last and least concentration of intelligence in the hierarchical SNA network, directly controlling attached unintelligent devices, such as CRT terminals and printers.

At the end of the SNA chain are terminals, printers, card punches, and other devices. Although these are actual hardware devices, to the SNA network software (VTAM) they are known only as logical addresses; therefore, they are collectively referred to as logical units. These LUs are of different types; each type communicates via a unique set of protocols defined under SNA. Common LU types are:

LU2 = CRT Terminal

The LU2 protocol allows for support of standard monochrome (IBM 3278) terminals, color terminals (IBM 3279 / 3179), and graphics terminals.

LU1 and LU3 = IBM 3287 Printer

SNA Server in the Hierarchical Model

The Microsoft SNA Server belongs to a category of computer networking devices called internetworking gateways.

The common characteristic of these devices is that they concurrently run two different networking protocols. This, in effect, allows an internetworking gateway to belong to each of at least two different networks. The internetworking gateway unites the networks by providing very high-speed translation between the protocols of each network.

The Microsoft SNA Server fits into the hierarchical SNA network by emulating a standard IBM PU2, or cluster controller, and multiple LUs of type 1, 2, or 3. Thus, the SNA Server appears to the SNA network as a standard IBM PU2 device with associated LUs.

This allows client software applications, running within the Windows NT network and emulating IBM terminals and printers, to communicate through the SNA Server via the IBM FEP (PU4) onward to the IBM host (PU5).


SNA Model #2: Peer-Oriented SNA
IBM Systems Network Architecture	5 of 6

Overview

SNA Model #2: Peer-Oriented SNA

The Peer-Oriented Model

A peer-oriented model is a more horizontal model in which computers communicate directly. This is the general direction in which standard computer network architectures are evolving.

In a peer-oriented network, each computer depends primarily upon its own intelligence and does not rely heavily upon help from, or constant access to, a centrally located host computer.

IBM's SNA architecture has evolved peer-oriented features, and IBM's stated direction for evolution of SNA networks is via advanced peer-to-peer networking (APPN [image]).

Advanced Peer-to-Peer Networking

APPN networks are flattened, but not truly horizontal.

The larger computers in an IBM APPN network are, typically, IBM AS/400s. These machines handle all network routing functions, as well as normal computing activities. These network peers are Physical Units Type 2.1 (PU2.1) devices under standard SNA terminology. Within an APPN network, each PU2.1 may offer various levels of service and network intelligence.

A PU2.1 device also has special associated LUs that are of a type called LU6.2. Devices or programs in an APPN network appear as LU6.2 entities; these entities communicate via LU6.2 - LU6.2 sessions by using a set of protocols collectively called APPC, or Advanced Program to Program Communication.

The smaller computers within an IBM SNA APPN network are often PCs. These computers, which appear as LU6.2 sessions to a PU2.1 host, provide terminal access, printer support, and so forth. Two independent programs running within an APPN network may also communicate directly by using APPC; in this case, each program appears as an LU6.2 session.

To provide backward compatibility with traditional SNA networks, APPC provides two varieties of LU6.2 architecture.

In full peer-oriented APPN networks, typically implemented in AS/400 environments or under the most modern evolution of mainframe technology, the independent APPC model applies; in older mainframe networks, a reduced-function model called dependent APPC applies.

Independent APPC provides the ability to run multiple, concurrent parallel sessions between a single pair of LUs. Dependent APPC allows only a single session between a given pair of LUs.

The programs that utilize APPC LUs are called transaction programs (TPs). A TP may provide any type of service: terminal emulation, data transfer, data base query or update, and so on.

The characteristics that govern the interactions between TPs by using an LU6.2 - LU6.2 connection are determined by the mode associated with the connection. The mode may be associated in a fixed manner with a given LU, or may be supplied by the invoking TP when a session is first initiated. The SNA defines a number of standard modes for APPC communications.

Microsoft SNA Server in the Peer-Oriented SNA Model

As in the hierarchical model, the Microsoft SNA Server functions as an internetworking gateway in an APPN network. In this instance, it belongs to the SNA APPN network via the emulation of a standard IBM PU2.1 node, with associated LU6.2 sessions.

As such, it allows client software applications within the Windows NT network that emulate LU6.2 devices or applications to communicate with other PU2.1 entities or LU6.2 applications within the APPN network.


Finding More Information
IBM Systems Network Architecture	6 of 6

Overview

Finding More Information

Microsoft's document Microsoft SNA Server Reference (Document No. SY57264) contains detailed technical information on how the SNA Server communicates within an SNA network, on SNA sense codes for error diagnosis of the SNA Server, and a list of relevant technical manuals published by IBM.


Microsoft SNA Server Overview
Chapter 2	1 of 7

Microsoft SNA Server Overview

This chapter introduces the Microsoft SNA Server. You will learn the general architecture of the SNA Server, the component modules that make up SNA Server, and the functions provided by the SNA Server.


What You Will Learn
Microsoft SNA Server Overview	2 of 7

What You Will Learn

After completing this chapter, you will be able to:

Describe the purpose of the SNA Server.

Describe the basic software and hardware architecture of the SNA Server.

Describe the general functions of the SNA Server.


The Microsoft SNA Server
Microsoft SNA Server Overview	3 of 7

The Microsoft SNA Server

The Microsoft SNA Server is an internetworking gateway composed of both software and hardware components.

It is a server process, running in the Windows NT Advanced Server and the Windows NT Server environment.

SNA Server concurrently runs two protocolsthe native communication protocol for Windows NT environments and IBM SNAenabling it to belong to both worlds. In addition, the SNA Server provides extensions to other networking protocols, such as TCP/IP and IPX.

It provides high-speed protocol conversion between these two protocols, creating a window between the two worlds that allows for bidirectional communication to provide terminal emulation, printer emulation, file transfer, and program-to-program communications.

It supports connections from client processes running within the Windows NT environment, or from other environments, including MS-DOS [image], Windows [image] 3.x, and OS/2 [image].


Connecting to the Network
Microsoft SNA Server Overview	4 of 7

Connecting to the Network

The SNA Server connects to an IBM SNA network via a data link. This data link is provided by a combination of hardware and software within the SNA Server, with the hardware providing the physical link and the software providing the communication protocol to run over that physical link.

Data Link Types

The IBM SNA supports many types of data links, including:

S/370 block multiplex channel.

S/390 serial optoelectrical channel.

SDLC (Synchronous Data Link Control) via leased or dial-up telephone lines.

DLC (data link control) via token ring or ethernet.

X.25 (private or public packet switched network).

DFT (locally attached distributed function terminal)

Currently, the Microsoft SNA Server supports a subset of these SNA Data Links:

SDLC

DLC over token ring or ethernet

X.25

DFT

It is probable that other SNA Server data links will be provided in the future by Microsoft or by third-party vendors.


Microsoft SNA Server Functions
Microsoft SNA Server Overview	5 of 7

Microsoft SNA Server Functions

The SNA Server emulates IBM SNA devices, allowing client software applications (which may run on the same hardware as does the SNA Server package, or may run on another computer within the Windows NT network served by the Windows NT server) to emulate IBM terminals and printers, to transfer files to and from the IBM host, or to contact other software applications running with the SNA network.

IBM SNA Network Access

The Microsoft SNA Server provides access into IBM SNA networks by emulating IBM devices. To access a traditional IBM mainframe, the Microsoft SNA Server will typically emulate a certain subset of IBM devices; to access an IBM AS/400, a different subset is emulated.

IBM Mainframe Access

The SNA Server provides access into IBM mainframe environments by emulating the function of a traditional IBM cluster controller (PU2), and the various types of devices (LUs) that a PU2 can support:

LU2, for emulation of an IBM 3270 terminal. The SNA Server receives LU2 data from the mainframe and then passes this data via a Windows NT sponsor pipe to a client application within the Windows NT domain; this client application provides the actual IBM 3270 terminal emulation.

LU1 and LU3, for emulation of an IBM 3287 printer. The flow of data is as described above. The client application, which emulates the IBM 3287 printer, may route its print output to a locally attached printer, or to a remote printer within the Windows NT domain.

LU6.2, for program-to-program communications. The flow of data is as described above; however, in this instance, the client is typically a program developed by the end-user or an application program supplied by a third-party vendor.

IBM AS/400 Access

For access to an IBM AS/400 environment, the SNA Server provides two models:

S/370 emulation model

APPN model

The AS/400 supports an S/370 (mainframe) emulation subsystem, allowing terminals and printers connected to true IBM PU2 cluster controllers to access the AS/400. The SNA server may be configured as described above to utilize this method of providing access to an AS/400.

However, the native mode of accessing an AS/400 is inherently more efficient. To utilize this native mode, the SNA server emulates an IBM "peer" node, or PU2.1. When SNA Server emulates a PU2.1 device, it appears to the AS/400 as another AS/400 within an APPN network.

As a PU2.1 device, the SNA Server supports multiple logical units of the type LU6.2. These LU6.2 connections are used for both terminal emulation and program-to-program communications.

For terminal emulation, the SNA Server receives LU6.2 data streams that contain data to drive IBM 5250 terminals. SNA Server forwards this data, again via the Windows NT sponsor pipes mechanism, to client applications within the Windows NT domain that provide IBM 5250 terminal emulation.

For program-to-program communications, the flow of data is as above. The client application (TP) may be a user-developed program or an application supplied by a third-party vendor.


SNA Server Components
Microsoft SNA Server Overview	6 of 7

SNA Server Components

Server Side Architecture

Description of SNA Server Components:

IBMSYNC.SYS -  Device driver for IBM SDLC adapters.

IBMDFT.SYS -  Device driver for IBM DFT adapters.

Link Services -  SNA Server link services for each SNA link type, which provide a SNADIS (user-mode) interface to the SNA Server. Link services are implemented as Windows NT services, though autostarted by SnaBase.

SNASERVR.EXE -  The SNA Server PU2.1 node. This is the SNA protocol engine of an SNA Server.

SNADMOD.DLL -  Provides isolation layer between the SNA server and the clients. Provides message passing layer (for 3270, LU6.2, Admin messages) between the server and the clients.

SNABASE.EXE -  Dynamically maintains a service table of other SNA Servers, links, and invokable TPs in the domain. Supports client sponsor pipes where the server list is sent to the client, either over IPX or named pipes.

SNANW.DLL -    The SNA Server interface to SNA Server clients attached over SPX/IPX. Uses Windows socket interface to NWLINK transport to communicate with clients over SPX/IPX session. Provides security interface to Windows NT local security authority via impersonated client logon.

SNALM.DLL -  The SNA Server interface to SNA Server clients attached over named pipes, supported by the Windows NT server.

Client Side Architecture

Description of SNA Server Client Components:

3270/5250 -  SNA Server 3270 Applet. Uses Emulator Interface Spec (EIS) to talk to server via the DMOD. SNA Server 5250 Applet uses APPC.

LUA SLI, RUI APIs-  API interface to data stream. Session-Level Interface (SLI) provides high-level interface, talks through lower-level Request Unit Interface (RUI).

APPC API -  Advanced Program-to-Program Communication interface.

CPIC API -  Common Programming Interface for Communications. Newer, higher-level peer interface; used by APPC and available for application programs.

NetView Services -  Alert service talks to NetView via Common Service Verbs API.

CSV API -  Common Service Verbs API; miscellaneous functions used by SNA applications.

Admin -  SNA Server admin tool, which runs on Win32 [image] only, and which talks to the SNA server SNAMANAG.DLL internal interface (and to the CONFIG file via SNACFG.DLL).

DMOD -  Isolation layer that provides 3270, LU6.2, and Admin message passing interface between the SNA client and Server. Win32 uses SNADMOD.DLL; Windows version 3.1 uses WDMOD.DLL; MS-DOS uses SNABASE.EXE; OS/2 uses COMDMOD.DLL.

SNABASE/WNAP -  Maintains client service table via sponsor pipe to a server.

NWCLI.DLL -  Provides the SNA Server client interface over IPX/SPX interface via IPX/SPX session to the server. Windows version 3.1 uses NWCLI.DLL; MS-DOS uses SNABASE.EXE; OS/2 is not supported.

LMCLI.DLL -  Provides the SNA Server client interface over named pipes to the server. Windows version 3.1 uses LMCLI.DLL; MS-DOS uses SNABASE.EXE; OS/2 uses COMDMOD.DLL.


Finding Additional Information
Microsoft SNA Server Overview	7 of 7

Finding Additional Information

Microsoft publishes a number of documents dealing specifically with SNA Server. Among this family of manuals, the following are particularly useful in developing an understanding of the SNA Server:

Microsoft SNA Server Installation Guide (Document No. SY57266)

Microsoft SNA Server Administration Guide (Document No. SY57265)

Microsoft SNA Server Reference (Document No. SY57264)


Designing the Configuration
Chapter 3	1 of 6

Designing the Configuration

Overview

This chapter discusses the theory and practice of planning and preparing the network and the host system for the installation of the Microsoft SNA Server.

A sample configuration is described, which will be the basis of the demonstrations shown in the video. By following a similar sequence of operations, you will be able to complete these phases of an installation of the SNA Server in your own unique configuration.


What You Will Learn
Designing the Configuration	2 of 6

Overview

What You Will Learn

After completing this chapter, you will be able to:

Describe minimum system software requirements for the SNA Server.

Describe minimum system hardware requirements for the SNA Server.

Gather all the information necessary to plan a successful SNA Server installation.

Manage the configuration process required to prepare IBM SNA hosts to communicate with the SNA Server.


Planning
Designing the Configuration	3 of 6

Overview

Planning

Defining Server Goals

The first step in planning a successful installation is to explicitly define the goals you want to achieve with the SNA Server. These goals determine the architecture of your network, the configuration of your SNA server, and the preparations needed within the IBM host.

Typical questions to be considered in defining your goals would be: How many servers will be installed? Which will be the primary server? What are the downstream systems that will use the servers? What type of access will each user require?

A typical goal might be to provide seven Windows version 3.1 users, currently in an Ethernet network, the ability to access an IBM ES/9000 [image] host and an AS/400 host on a token ring network, along with a remote IBM ES/9000 host with a dial-up connection for backup.

The requirements might be:

Each user must maintain two concurrent sessions to the IBM ES/9000 host for access to two different applications.

Each session must emulate a standard IBM 3278-2 terminal.

Each of the seven Windows version 3.1 users also needs to log on to a departmental IBM AS/400.

These requirements are used in the following sample installation.

The Sample Installation

To satisfy the previous goals, the sample installation will include the following components and environmental conditions.

A Microsoft SNA server running within a Windows NT Advanced Server or a Windows NT Server environment.

The server is running on an Intel486 [image] with an IBM token ring data communications card and an Ethernet data communications card.

The Intel486 is connected to a 16 megabit token ring.

An IBM 3745 front end processor (PU4) is attached to the token ring.

The IBM 3745 front end processor (PU4) is channel-attached to an IBM ES/9000 host, running the MVS operating system.

An IBM AS/400 attached to the token ring.

A remote IBM ES/9000 host with a dial-up connection.

Windows 3.1 client software will also be installed to provide terminal and printer emulation for the system.

To provide the necessary services, the SNA Server is configured to provide:

14 IBM 3278-2 terminal emulation sessions.

1 IBM LU6.2 session.

7 IBM 5250 terminal emulation sessions by emulating the functions of a traditional:

IBM PU2 (cluster controller)

IBM PU2.1 (peer node)

and supporting:

14 IBM LU2 devices.

1 IBM LU6.2 session for program-to-program communication.

7 IBM LU6.2 sessions for terminal emulation.

Verifying Compliance with System Requirements

System Hardware Requirements

System hardware requirements will vary, depending upon the configuration you plan. For the sample installation, the SNA Server minimum requirements are sufficient. The minimum hardware requirements are:

16 MB system RAM.

20 MB free hard-disk space (minimum).

2 network adapters (one for IBM token ring and one for Ethernet).

An SNA communications adapter (in this case, the above IBM token ring adapter).

Client software on the machines running Windows 3.x will also be installed. Minimum hardware requirements for running the client software are:

4 MB system RAM.

5 MB free hard-disk space (minimum).

A network adapter.

System Software Requirements

If you have the Microsoft Windows NT Advanced Server or Windows NT Server already installed, you will need one additional software package:

The Microsoft SNA Server.

If you do not have the Microsoft Windows NT Advanced Server or Windows NT Server already installed, you will need three software packages:

The Microsoft Windows NT operating system version 3.1 or later.

The Microsoft Windows NT Advanced Server or Windows NT Server.

The Microsoft SNA Server.


Preparing the IBM SNA Host for Installation
Designing the Configuration	4 of 6

Overview

Preparing the IBM SNA Host for Installation

The SNA communications software on the IBM host must be configured to communicate with the SNA server. This communication is enabled whenever a device is added in an IBM SNA network. Typically, this configuration is performed by a systems specialist who maintains the IBM host computer or who specializes strictly in communications for that host computer. In a mainframe environment, this specialist is typically referred to as a Virtual Telecommunications Access Method (VTAM) systems programmer; in an AS/400 environment, as a systems manager.

Unless you are knowledgeable about the IBM system, you might not be one to handle the IBM configuration: Rather, you might communicate your needs to the IBM communications specialist, who performs the configuration. When the configuration is complete, the specialist will supply you with the specific resource names and addresses that have been generated on the IBM system. You will use these names to complete the SNA Server configuration. The details you need to communicate to the IBM systems programmer vary, depending upon your configuration.

To aid you in gathering the necessary information, the following detailed planning forms are available:

SNA Server Resources Planning Form

This form details what adapters are installed in your SNA server, what type of SNA connection will be used, what IBM system you will be connecting to, and so on.

Server Information Form

This form details the actual hardware configuration of your SNA server and the nature of your Windows NT environment.

Initial Connection Settings Form

This form details what type of data communications link you will use to access the SNA network, when the link will be activated, and so on.

These forms can be found in Appendix B of the Microsoft SNA Server Administration Guide. The specific forms used to complete the sample installation have been reproduced in this workbook for your use while completing the following exercises.


Completing the Forms
Designing the Configuration	5 of 6

Overview

Completing the Forms

This portion of the installation process is critical. Obtaining accurate and complete information before installation and configuration saves you time and frustration. Begin by completing these three forms:

SNA Server Resources Planning Form

Server Information Form

Initial Connection Settings Form

Because you will be connecting to two separate IBM environments, you will begin to develop two separate sets of information for your SNA Server configuration. The first set is for the connection to the ES/9000 MVS host; the second is for the AS/400.

1.	Fill out the Host Systems Information form.

2.	Choose the correct Data Link Settings Form. For this example, use the 802.2 Settings Form.

3.	Obtain information from your IBM systems administrator. The systems administrator provides you with the information you need to complete the Settings portion of this, or any other, Data Link Settings Form.

4.	Choose the correct LU Form. For this example, use the 3270 LU form.

The administrator generates the appropriate number and type of LUs for the configuration, supplying you with LU Number and LU Name values that you use in configuring the SNA Server.

5.	Fill out the APPC LU forms.

Three forms are used to complete the description of the APPC LU6.2 to be configured. They describe the local (on the SNA server) LU, the remote (on the SNA host) LU, and the mode (properties that govern a session between the two).

The IBM system administrator generates the remote LU; you generate the local LU on the SNA server. The SNA Server maintains a listing of standard modes; you can assign one of these standard modes to the LU. If the remote TP does not specify an explicit mode statement at session startup, this associated mode is used as the default. If you need to create pools of dedicated LUs within the SNA server, complete the 3270 LU Pools form.

For an AS/400 host, you repeat the same process. You fill out not only the AS/400 host information form, but also another copy of the 802.2 Settings form, the LU forms, and so on.


Finding Additional Information
Designing the Configuration	6 of 6

Overview

Finding Additional Information

The Microsoft SNA Server Administration Guide (Document No. SY57265) provides detailed information on both AS/400 and Mainframe configurations in Appendix A, "Guidelines for Specific Configurations."


Installing the Microsoft SNA Server
Chapter 4	1 of 7

Installing the Microsoft SNA Server

Overview

This module describes the installation of the Microsoft SNA Server on the Windows NT Advanced Server or the Windows NT Server platform, and the installation of SNA Server client software, both on the local Windows NT Advanced Server or Windows NT Server and on other platforms served by these systems.


What You Will Learn
Installing the Microsoft SNA Server  	2 of 7

Overview

What You Will Learn

After completing this chapter, you will be able to:

Install the Microsoft SNA Server.

Install the appropriate data links for the server.

Configure the installed data links for the server.

Install a Windows NT-based client.

Install a client running Windows version 3.1.

Install an MS-DOS – based client.

Modify client options.


Installation Overview
Installing the Microsoft SNA Server  	3 of 7

Overview

Installation Overview

The SNA Server is installed via a graphical interface program that prompts you to supply specific installation details, such as the directory in which you want the SNA Server files installed, the role of the SNA Server, the specific client environments, and so forth. When the SNA Server software (which is supplied in compact disc and 3.5-inch diskette formats) has been copied to its permanent location, you are prompted to install the necessary data links for the SNA Server to communicate with the installed hardware interfaces. After configuring the data links, you have the option of exiting the completed installation process or continuing with the customization of the SNA Server for your site by using the SNA Admin Utility.


The Setup Program
Installing the Microsoft SNA Server  	4 of 7

Overview

The Setup Program

Setup provides the interface for installation of the SNA Server, for installation, configuration, and removal of data link services, and for removal of the SNA Server. In using Setup, you make selections and enter site-specific information via dialog boxes provided by Setup. Based upon your choices, Setup copies files from the distribution media, configures your SNA Server within the Windows NT Advanced Server or Windows NT Server environment, and installs data links. In addition to dialog boxes, Setup provides informational windows that keep you informed of the progress of the installation. Setup installs these specific software packages:

SnaBase

SnaServer

SnaNMVT

NVRunCmd

NVAlert

Link services as required

Clients as required


Using the SNA Server Setup Program
Installing the Microsoft SNA Server  	5 of 7

Overview

Using the SNA Server Setup Program

To start the Setup program

1.	Insert the SNA Server distribution media into the appropriate drive. In this example, install from compact disc via drive E.

2.	Choose the RUN command from the FILE menu of the standard Windows menu bar, and then type e:\setup

The Welcome To SNA Server Setup dialog box appears.

Note

At this point and with any future dialog box, you may request help by choosing the Help button displayed on your screen.

3.	Choose Continue to begin the SNA Server installation.

An Installation Path dialog box appears.

You now have the option of accepting the default installation path (C:\SNA) by choosing Continue, or of changing the path to install in another directory.

To change the installation path

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

2.	In the Install To box, type the new destination path, and choose Continue.

Setup copies the files to configure the SNA Server and creates the registry entries for all subservices.


Installing an SNA Server
Installing the Microsoft SNA Server  	6 of 7

Overview

Installing an SNA Server

Setup prompts you to choose one of three SNA Server roles for this installation:

Primary Configuration Server

A primary server contains the domain-wide configuration file. This file reflects the SNA resources for the domain. There can only be one primary server in the domain.

Backup

A backup server holds a copy of the configuration file. There can be more than one backup server on an SNA Server system. The backup server allows the SNA Server system to continue working if the primary service goes down.

Member server (no configuration)

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

The default configuration for the SNA Server is primary; use the default setting for the sample installation. Backup and member servers are covered in the Microsoft SNA Server Installation Guide (Document No. SY57266).

To install a primary server

Choose Continue to install the SNA Server as the Primary Configuration Server.

To select the network operating system

1.	From the Select Network Operating System dialog box, select either Microsoft LAN Manager, Novell NetWare, or both.

For Windows version 3.1 systems, you can also select Windows for Workgroups.

2.	Choose Continue.

3.	If you selected Novell NetWare, the NetWare Domain Name dialog box appears.

Setup now allows you to review your selections or to continue with the SNA Server installation.

Once you have selected Continue, Setup copies all the necessary files for the SNA Server from the distribution compact disc to the permanent installation directory and creates the various services registry entries needed for the SNA Server. Informational boxes keep you informed of the progress of the installation. When this is completed, Setup pauses to allow you to select and configure link services.


Installing a Link Service
Installing the Microsoft SNA Server  	7 of 7

Overview

Installing a Link Service

Link services define the protocol used between the SNA Server software and the communications adapters installed in a computer, including drivers written to the SNADIS interface.

Setup leads you through the dialog boxes to first install and then configure a link service. You repeat this process for as many link services as you need.

To install a link service

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

2.	Choose install.

3.	Select them by choosing Continue.

Setup completes installation of this link service and returns to the Link Service Configuration screen with a message that the link service has been installed.

To install other link services

1.	From the Link Service Installation dialog box, choose Configure. You are not installing additional links in this sample, so choose Continue.

Setup now configures network settings; when complete, Setup prompts you with a message.

2.	Proceed by choosing OK. The link service is now correctly installed. However, to make it usable, the SNA Server must be customized to configure connections.

The installation of the SNA Server is complete. Setup displays a screen informing you that the SNA Server has been successfully installed.

You have the option of exiting the Setup program (the default), or of continuing with the configuration and customization of the SNA Server via the SNA Server Admin program.

3.	Press ENTER to exit Setup.


Configuring the Microsoft SNA Server
Chapter 5	1 of 19

Configuring the Microsoft SNA Server

Overview

This chapter introduces the SNA Server Administration Utility (SNA Server Admin). After installation of the Microsoft SNA Server and the link support, the SNA Server Admin program is used to configure connections (Physical Units [PUs]) and Logical Units (LUs). The SNA Server Admin program provides a graphical interface for easy operation.


What You Will Learn
Configuring the Microsoft SNA Server	2 of 19

Overview

What You Will Learn

After completing this chapter, you will be able to:

Configure servers and connections

802.2

SDLC

X.25

Configure LUs for 3270

Configure LUs

Assign users and groups

Use LU pools

Configure LUs for APPC

Configure LUs

Configure modes

Assign users and groups

Assign defaults

Configure downstream connections and LUs

Manage the server

Start and stop servers and connections

Change the domain of focus

Configure for NetView


The Configuration Process
Configuring the Microsoft SNA Server	3 of 19

Overview

The Configuration Process

At this point, you have gathered information regarding local software, hardware, the configuration of the remote host, peer, or downstream system, and understand the way the SNA Server will be used. You are now ready to configure the SNA Server. This includes:

Configuring server(s).

Configuring connections.

Configuring LUs.

Defining LUs into pools.

Assigning pools to users and groups.

Configuring downstream connections.

Note

Most configuration changes in the SNA Server take effect the next time the server is started. After making changes to servers and connections, stop and restart the affected servers.

The first two steps in configuring the SNA Server are to define the configuration for the server(s) and configure the connections. Once the servers and connections are defined, you assign and configure the appropriate LUs (3270, APPC, LUA, or downstream) to the associated connections (PUs). LUs contain all the information needed for a user or program to use a connection. Next, you can pool your LUs. LUs, other than APPC LUs, can be pooled to make them readily available to multiple users, applications, or downstream systems.

Before you begin, make sure that you have all the required information about local and remote computers available.


Configuring Servers
Configuring the Microsoft SNA Server	4 of 19

Overview

Configuring Servers

If an SNA Server is to accept incoming calls, accept host initiated connections, or be used for LU6.2, you must configure two parameters for the server: the local Network Name and Control Point Name. Together, these parameters identify the server to the network.

To specify parameters for an SNA server that will accept incoming calls or be used for LU6.2 (APPC)

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

2.	From the Services menu, choose Properties, or double-click on the highlighted server.

3.	In the Network Name box, type a name identifying the SNA network of the local SNA server. The Server Properties dialog box appears.

Note

For an AS/400 connection, type the Network Name of the local SNA server in the Network Name box.

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

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

6.	Choose the OK button.


Configuring Connections
Configuring the Microsoft SNA Server	5 of 19

Overview

Configuring Connections

You use the SNA Server Admin program to configure settings for new and existing connections. Each connection depends on the communications adapter and lines used by the server. Each connection accesses the communications adapter via the link service.

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 Type, select the type of connection.

4.	Choose the OK button. The Connection Properties dialog box appears.

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, or double-click on the highlighted connection. The Connections Properties dialog box appears.

Connection Properties

The Connection Properties dialog box will vary depending on your connection choice. You will need to consider the following:

Connection Name

Type a name identifying the connection.

The name can be 18 characters long, containing alphanumeric and special characters.

Link Service

Select the Link Service.

The link service enables the connection to access a particular communications adapter. If the link service you want is not on the list, cancel and use Setup to install the service.

Remote End

Select the type of remote system for this connection from the Remote End menu:

Host System: A system, usually a mainframe, that controls interactions between it and PCs connecting to it. If you will be using dependent APPC, select Host, not Peer.

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

Downstream System: A client, such as an Apple [image] Macintosh [image] that does not use the SNA Server client/server interface, but that can access host connections available on the SNA server.

Activation

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

On Server Startup (default for 802.2 and DFT)

On Demand (default all other connection types)

By Administrator

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

Allowed Direction

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

After initial connection settings are made, choose a button according to the following:

Setup Button to continue configuring basic settings for an 802.2, SDLC, or X.25 connection.

OK Button to accept settings or to complete the configuration for a DFT connection, which requires only the setting in the Connection Properties dialog box.


Basic 802.2 Settings
Configuring the Microsoft SNA Server	6 of 19

Overview

Basic 802.2 Settings

Once you choose the Setup button with an 802.2 connection, the 802.2 Setup dialog box appears.

Identify the appropriate items for you configuration and provide information as follows:

Remote Network Address

Type the 12-digit hexadecimal network address of the remote host, peer, or downstream system to which this connection will communicate.

3174: Value in the configuration response 900 of the controller's customization program.

3720, 3725, or 3745: MACADDR = parameter in NCP configuration

IBM 9370: VTAM PORT definition for the MACADDR = parameter

Another SNA Server

The Remote Network Address default is 400000000000.

Local Node ID

The Local Node ID is 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 (the node number) in the second box.

Note

Do not use 000 or FFF for the first three digits for the Local Node ID; do not use 00000 for the last five digits. These values are reserved.

The default for Local Node ID is 05D FFFFF.

Network Name (Remote Node)

Type the name identifying the SNA network of the remote host. The name should match the NODEID parameter in the VTAM Start command for the remote SSCP. For AS/400 connections, enter the Network Name of the AS/400 (the RMTNETID).

Control Point Name (Remote Node)

Type the name that identifies the remote system on the SNA network. The name should match the SSCPNAME parameter in the VTAM Start command for the remote SSCP. For AS/400, enter the name of the AS/400.

Remote Node ID

Type the first three digits (the block number) in the first box and the last five digits (the node number) in the second.

Note

Do not use 000 or FFF for the first three digits for the Local Node ID; do not use 00000 for the last five digits. These values are reserved.

After Configuring Basic Settings

The SNA Server is designed to provide appropriate defaults for all advanced settings. You can select the Advanced button to accept defaults or modify the settings.

Choose a button according to the following:

Advanced Button to configure advanced settings.

OK Button To accept settings and use advanced settings set by default or previously configured.

For further information regarding advanced settings, refer to the Microsoft SNA Server Administration Guide (Document No. SY57265).


Basic SDLC Settings
Configuring the Microsoft SNA Server	7 of 19

Overview

Basic SDLC Settings

When you choose the Setup button with an SDLC connection, the SDLC Setup dialog box appears.

Dial Data

Type the information used when dialing if this connection uses a switched line. Be sure to refer to the modem's dialing method.

Local Node ID

Type the Local Node ID (an 8-digit hexadecimal number that identifies the local system) if this connection is to a host system. Enter the first three digits (the block number) in the first box and the last five (the node number) in the second box.

Note

Do not use 000 or FFF for the first three digits for the Local Node ID; do not use 00000 for the last five digits. These values are reserved.

The default for is 05D FFFFF.

Network Name (Remote Node)

Type the name identifying the SNA network of the remote host. The name should match the NODEID parameter in the VTAM Start command for the remote SSCP. For AS/400 connections, enter the Network Name of the AS/400 (the RMTNETID).

Control Point Name (Remote Node)

Type the name that identifies the remote system on the SNA network. The name should match the SSCPNAME parameter in the VTAM Start command for the remote SSCP. For AS/400, enter the name of the AS/400.

Remote Node ID

Type the first three digits (the block number) in the first box and the last five digits (the node number) in the second.

Note

Do not use 000 or FFF for the first three digits for the Local Node ID; do not use 00000 for the last five digits. These values are reserved.

The default for Local Node ID is 05D FFFFF.

After Configuring Basic Settings

The SNA Server is designed to provide appropriate defaults for all advanced settings. You can either select the Advanced button to accept defaults, or modify the settings.

Choose a button according to the following:

Advanced Button to configure advanced settings.

OK Button to accept settings and use advanced settings set by default or previously configured.

For further information regarding advanced settings, refer to the Microsoft SNA Server Administration Guide (Document No. SY57265).


Basic X.25 Settings
Configuring the Microsoft SNA Server	8 of 19

Overview

Basic X.25 Settings

When you choose the Setup button with an X.25 connection, the X.25 Setup dialog box appears.

Remote X.25 Address

Type the address specifying the X.25 remote system. For connections to a host using VTAM, use the value in the VTAM PORT definition for the DIALNO = parameter.

Local Node ID

If this connection is using SVC, type the Local Node ID (an 8-digit hexadecimal number that identifies the local system) if this connection is to a host system. Enter the first three digits (the block number) in the first box and the last five (the node number) in the second box. For host systems, the numbers should match the VTAM definition for IDBLK and IDNUM.

Note

Do not use 000 or FFF for the first three digits for the Local Node ID; do not use 00000 for the last five digits. These values are reserved.

The default for is 05D FFFFF.

Network Name (Remote Node)

Type the name identifying the SNA network of the remote host. The name should match the NODEID parameter in the VTAM Start command for the remote SSCP. For AS/400 connections, enter the Network Name of the AS/400 (the RMTNETID).

Control Point Name (Remote Node)

Type the name that identifies the remote system on the SNA network. The name should match the SSCPNAME parameter in the VTAM Start command for the remote SSCP. For AS/400, enter the name of the AS/400.

Remote Node ID

Type the first three digits (the block number) in the first box and the last five digits (the node number) in the second.

Note

Do not use 000 or FFF for the first three digits for the Local Node ID; do not use 00000 for the last five digits. These values are reserved.

The default for Local Node ID is 05D FFFFF.

After Configuring Basic Settings

The SNA Server is designed to provide appropriate defaults for all advanced settings. You can either select the Advanced button to accept defaults, or modify the settings.

Choose a button according to the following:

Advanced Button to configure advanced settings.

OK Button to accept settings and use advanced settings set by default or previously configured.

For further information regarding advanced settings, refer to Microsoft SNA Server Administration Guide (Document No. SY57265).


Configuring LUs
Configuring the Microsoft SNA Server	9 of 19

Overview

Configuring LUs

It is important to match parameters on the remote host and peer systems with those on the SNA server. Be sure to check with the systems administrator of the remote host, peer, and/or downstream system before proceeding with the configuration of the server.

Configuring 3270 LUs

A 3270 LU provides a vehicle for a user to access an IBM host by using a 3270 terminal emulation software program. LUs can be created individually, or in a consecutively numbered range, and LUs can be defined specifically for 3270 display or for printing. Once the LUs have been created, they can be grouped into pools, then assigned to users and/or groups. Before you begin, make sure that both the server(s) and connection(s) that the 3270 LU(s) will use are configured.

To assign a single 3270 LU

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

2.	From the Services menu, choose Assign LUs.

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

4.	Choose the OK button.

Configuring Properties for a 3270 LU

When you assign or access a 3270 LU for viewing or modifying, you will need to provide information regarding the properties associated with the LU. You can copy properties from one LU to another by clicking on the LU in the Users And Groups dialog box and dragging the icon to the intended Users. When configuring properties for a 3270 LU, consider the following:

LU Number

Enter a number identifying the LU to its connection. It should match the LOCADDR=parameter of the LU definition in VTAM or in the NCP Gen.

The range for the LU Number is 1–254.

Note

If the LU is on a DFT connection, it does not use an LU number. See the Microsoft SNA Server Administration Guide (Document No. SY57265) for details.

LU Name

Name identifying the LU.

Connection

The connection for this LU. The connection designation cannot be changed. You can move an LU from one connection to another by clicking on the LU in the Servers And Connections dialog box and dragging the icon to the intended Connection.

Pool

The pool name will appear if the LU has been assigned to a pool. Assigning LUs to pools will be discussed later in this chapter.

LU Type

Select the Display option button if the LU will be used for terminal emulation, or select the Printer option button if the LU will be used for host printing.

Display Model

If Display was selected, select one of the following display sizes:

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.

Choose the OK button to accept settings.

Configuring a Range of 3270 LUs

You can configure multiple LUs at once (except DFT) by configuring them as a consecutively numbered range.

To configure multiple 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.

2.	From the Services Menu, choose Assign LUs. The Insert LU dialog box 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.

6.	To configure the numbering for an LU Range, find the items appropriate to your network and complete as follows:

Base LU

First LU Number

Number of LUs

Selected LU Range

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

After assigning and numbering a range of 3270 LUs, you can configure the LUs in the range. All the LUs will be configured the same in the range, but you can modify individual LUs after configuring the range. For more information on configuring 3270 LU range properties, see the Microsoft SNA Server Administration Guide (Document No. SY57265) for details.


User and Group Access for 3270
Configuring the Microsoft SNA Server	10 of 19

Overview

User and Group Access for 3270

For users to be recognized by the SNA Server, they must have accounts on the local network. Once users and/or groups of users have network accounts, you can add them to the list used by the SNA Server. Once added, you can assign 3270 LUs and/or 3270 LU pools to the users. Once the configured 3270 LUs or LU pools are assigned to users, the users gain access to the host system(s) to which the LUs connect.

To add a user or group

You must first set up accounts for the users on the 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.

Configuring Properties for a 3270 User or Group

When you access an existing user or group, the User Properties or Group Properties dialog box appears. You can configure properties for each user or group, or you can copy properties from one user or group to another.

Comment

Optional. Type a comment of up to 25 characters.

Default Local APPC LU

If this user will be utilizing APPC programs (TPs, 5250 emulators, or APPC applications), you can choose a default APPC LU to be used when the user starts such programs.

Default Remote APPC LU

If this user will be utilizing APPC programs (TPs, 5250 emulators, or APPC applications), you can choose a default APPC LU to be used when the user starts such programs.

After Configuring Settings

Choose the OK button.


Using 3270 LU Pools
Configuring the Microsoft SNA Server	11 of 19

Overview

Using 3270 LU Pools

LU pools are groupings of 3270, LUA, and/or downstream LUs that allow maximum access to the LUs in the pools. A user using the pool can get LU access as long as one of the pooled LUs is available. If one or more of the LUs in the pool are not functioning, the user will not be affected, as long as another LU in the pool is functioning. LU pooling is a way to build in a vehicle for fault tolerance in the network. LU pools maximize access by:

Allowing groups of intermittent users to use resources efficiently. For example, 20 users may find that 10 LUs are sufficient for them to share.

Providing a hot backup through distribution of a single LU pool across more than one server or adapter.

Load balancing between servers.

Note

You cannot pool APPC LUs.

LU Pooling

To create an LU Pool, you must follow these basic steps.

Configure the LUs that the pool will contain.

Create the pool.

Configure the properties for the 3270 LU pool.

Assign the intended LUs to the pool.

Assign the pool to a user.

To create a 3270 pool

1.	In the LU Pools Window, select any item.

2.	From the Pools menu, choose New Pool. The New Pool dialog box appears.

3.	Enter 3270.

4.	Once a pool is created, double-click on the new LU pool, and the 3270 LU Pool Properties dialog box appears.

To configure properties of a 3270 pool

1.	Enter Pool Name identifying the LU pool.

2.	Select a size for the display. Default is Model 2.

3.	Select Model can be overridden if you want to allow users to override the display model type.

4.	Choose OK button.

To assign users to 3270 LUs and LU pools

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

2.	Select the user or group to which you want to assign one or more LUs or LU pools.

3.	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 on the first item you want, hold down the SHIFT key, and click on the last item you want.

5.	Choose the OK button.


Configuring for APPC (LU6.2)
Configuring the Microsoft SNA Server	12 of 19

Overview

Configuring for APPC (LU6.2)

The type of LU used for Advanced Program-to-Program communications (APPC) is LU6.2. APPC provides a transport vehicle for programs on peer systems to communicate with each other over the SNA network. Programs that use LU6.2 are referred to as transaction programs (TPs). There are two kinds of TPs: TPs that can invoke a conversation, and TPs that can be invoked.

APPC generally uses a local LU and one or more remote LUs. A local APPC LU can be independent or dependent. Independent LUs can support multiple parallel sessions.

Local and remote APPC LUs work together in pairs. The local APPC LU is assigned to a server (unlike other LU types, which are assigned to connections).

Assigning a Local APPC LU

To assign a local APPC LU

1.	In the Servers And Connections window, select a server.

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.

Configuring Local APPC LU Properties

When you assign or access a local APPC LU, the New APPC LU Properties dialog box or the APPC LU Properties dialog box appears.

LU 6.2 Type

Select the Independent or Dependent option button.

LU Alias

Type a name that identifies the LU to local TPs. Note that the LU Alias and LU Name can match each other, or differ.

Network Name

Type a name identifying the SNA network. For independent LUs, the Network Name is required; for dependent LUs, it is recommended for tracing events in the Windows NT event log. For an AS/400 configuration, specify the name of the network. Generally, this is the same network name as the RMTNETID setting on the AS/400.

LU Name

Type a name identifying the LU. For an independent LU, the LU Name identifies the LU to other components on the SNA network and is required. For a dependent LU, the LU Name identifies the LU to local software and is recommended for tracing events in the Windows NT event log.

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.

Implicit Incoming Remote LU

To specify an incoming remote LU (a remote LU to use with the local LU) when the SNA Server does not recognize an incoming remote LU name, choose an existing remote LU name from the list.

LU Number

For dependent LUs, type the number identifying the LU on its connection. It should match the LOCADDR=parameter for the LU definition in VTAM or in the NCP Gen. For independent LUs, this setting is unavailable.

To accept the settings, choose the OK button.

Assigning a Remote APPC LU

To assign a remote APPC LU

Local and remote APPC LUs work in pairs. The remote APPC LU is assigned to a connection that can have a Remote End of Host or a Remote End of Peer.

1.	In the Servers And Connections window, select the connection to which the LU is to be assigned.

2.	From the Services Menu, choose Assign LUs.

3.	In the Insert LU dialog box, select APPC (Remote).

4.	Choose the OK button.

Configuring Remote APPC Properties

When you assign or view a remote APPC LU, the New APPC Remote LU Properties dialog box or the APPC Remote LU Properties dialog box appears.

LU Alias

Type a name that identifies the LU to local TPs. Note that the LU Alias and the LU Name can match each other, or differ.

Network Name

Type a name identifying the SNA network.

LU Name

Type a name identifying the LU. 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 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 and is recommended for tracing events in the Windows NT event log.

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 System Services Control Point (SSCP). The name is required when using dependent APPC.

Supports Parallel Sessions

If this LU will be used with an independent local LU and parallel sessions will be used, select this check box. If this LU will be used with a dependent local APPC LU, do not select this check box. Note that if a remote LU supports parallel sessions, it can only be used with a mode that has a value greater than the one for the parallel session limit.

Enable Automatic Partnering

To designate the LU as a local 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.

Implicit Incoming Mode

To designate a mode as the implicit incoming mode for this LU, select a mode name from the list. The implicit incoming mode is used by APPC LUs when the SNA Server does not recognize the mode name specified by the remote TP. If this remote LU will be used as an implicit incoming remote LU for a local APPC LU, select a mode from the list.

Note

An implicit incoming remote LU requires an implicit incoming mode.

To accept the setting, choose the OK button.


Configuring Modes
Configuring the Microsoft SNA Server	13 of 19

Overview

Configuring Modes

A mode is associated with an LU-LU pair and determines session properties for that pair. A number of standard modes are provided with the SNA Server. You configure modes only after you have configured local and remote APPC LUs.

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 assigned. 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 selected in step 1, either the APPC LU Properties or the APPC Remote LU Properties dialog box will appear.

3.	From the Properties dialog box for the LU, choose the Partners button. The LU6.2 Partner LUs dialog box appears.

4.	In the LU6.2 Partner LUs dialog box, choose the Modes button. The APPC Mode Properties dialog box appears.

To add a mode to the list in the APPC Mode Properties dialog box

1.	In the Mode Name box, type a name identifying the mode.

2.	Specify parameters as described in the following list.

3.	Choose the Add button.

4.	Choose the Close button.

Mode Properties

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

Parallel Session Limit

Specify the maximum number of sessions allowed with this mode. To allow only a single session, specify 1. To allow parallel sessions, specify a value greater than 1. If the local APPC LU to be used with this mode is dependent, specify 1; dependent local APPC LUs cannot have parallel sessions. The maximum is 254; 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 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.

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

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.

High Priority Mode

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

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. The range is 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. The range is 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. The range 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. The range is from 256 through 16384; the default is 1024.


User and Groups Designation and Assigning Default APPC
Configuring the Microsoft SNA Server	14 of 19

Overview

User and Groups Designation and Assigning Default APPC

For a user or group that 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 (TP, 5250 emulator, or APPC application) and the program does not specify LU aliases.

Before assigning default APPC LUs to a user or group, make sure the user or group has an account on the SNA Server or on the local area network, and be sure to add the user or group to the list used by the SNA Server.

To add a user or group to the list used by the 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.

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.

3.	From the Users menu, choose Properties. The User Properties or Group Properties dialog box appears.

4.	In the Default Local APPC LU box, select a local APPC LU.

5.	In the Default Remote APPC LU box, select a remote APPC LU.

6.	Choose the OK button.

AS/400 Configuration Considerations for APPC

Notes have been interspersed throughout this workbook to draw your attention to special considerations when connecting the SNA Server to an AS/400 system. The table below can be used as a quick reference for configuring for an AS/400 system.

SNA Server	Parameter Name	Reminders
Server	Network Name (Local)	Generally the same as the RMTNETID on AS/400
Server	Control Point Name (Local)0	Specify one of your choosing
Connection	Remote End	Select Peer System
Connection	Local Node ID	Required for all connections
Connection	Control Point Name (Remote)	AS/400 system name
Connection	Network Name (Remote)	Specified as RMTNETID
Remote APPC LU	LU Name	Name of AS/400
Mode	Mode Name	QPCSSUP for all LU-LU pairs
User or Group	Default Local APPC LU	Assign a default
User or Group	Default Remote APPC LU	Assign a default


Configuring Downstream Connections and LUs
Configuring the Microsoft SNA Server	15 of 19

Overview

Configuring Downstream Connections and LUs

Downstream connections and LUs allow an SNA Server to support communication between hosts and clients such as Macintosh systems or 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. To the downstream system, there appears to be a direct connection to the host, passing information through the SNA Server. Included in the information being passed is the LU information. Therefore, the SNA Server does not store detailed LU configuration information for downstream LUs. However, the 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 the SNA Server is always dependent and is controlled by the host.

To configure downstream LUs and connections

1.	Configure the host connection. When specifying the Remote End, in the Connections Properties dialog box, select Host System.

2.	Configure the connection as downstream, in the Connection Properties dialog box, select Downstream.

Note

Downstream connections cannot be DFT.

3.	Select the host connection and assign one or more new downstream LUs to that connection.

4.	Optionally, pool downstream LUs to maximize the access available.

5.	Select the downstream connection and associate the downstream LUs (from step 3) and/or the LU pools (from step 4) with that connection.

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

To configure a new downstream connection (802.2 example)

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.

4.	Choose the OK button. The Connections Properties dialog box appears. The dialog is slightly different for each type of connection.

5.	In the Connection Properties dialog box, specify an appropriate connection name and primary link service.

6.	For an 802.2 connection, select the appropriate DLC type.

7.	Under Remote End, select the Downstream option button.

8.	Under Allowed Directions, clear Incoming Calls or Outgoing Calls, as required. For a downstream connection, the standard choice for Allowed Directions is both Outgoing and Incoming Calls.

9.	If the Allowed Directions include Outgoing Calls, under Activation, make any necessary changes.

10.	Choose the Setup button. The 802.2 Setup dialog box appears.

11.	Specify any other connection parameters according to the hardware and software between the downstream system and the SNA server.

12.	When the 802.2 Setup dialog box is complete, choose the OK button.


Configuring Individual Downstream LUs
Configuring the Microsoft SNA Server	16 of 19

Overview

Configuring Individual Downstream LUs

Once the host connection that the LU will use has been defined, you can create a new downstream LU. You can assign and configure new downstream LUs one at a time or as a consecutively numbered range.

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.

2.	From the Services menu, choose Assign LUs.

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

4.	Choose the OK button. The New Downstream LU Properties dialog box appears.


Configuring Properties for a Downstream LU
Configuring the Microsoft SNA Server	17 of 19

Overview

Configuring Properties for a Downstream LU

LU Number

Type a number identifying the LU to the host. It should match the LOCADDR= parameter of the LU definition in VTAM or in NCP Gen.

The range is from 1 through 254.

Downstream LU Number

This number is assigned by the SNA Server when the LU is associated with a downstream connection. This 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 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 and cannot be changed in this dialog box.

Pool

The pool name will appear if the LU has been assigned to a pool.

To accept settings, choose the OK button.


Associating Downstream LUs with a Downstream Connection
Configuring the Microsoft SNA Server	18 of 19

Overview

Associating Downstream LUs with a Downstream Connection

The connection and the LUs must be configured before you can associate downstream LUs with a downstream connection.

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.

3.	Under Available LUs and Pools, choose one or more downstream LUs and/or pools.

4.	Choose the OK button. The LUs associated with the downstream connection are listed to the right of the connection.

5.	Stop and restart the servers and connections to activate the changes.


Management of the SNA Server
Configuring the Microsoft SNA Server	19 of 19

Overview

Management of the SNA Server

You can manage services on the SNA network by starting and stopping the SNA Server, starting and stopping connections, and resetting LUs. In addition, the SNA Administration facility allows you to:

Stop services.

Reset LUs.

Change the domain of focus.

Delete SNA resources, such as connections or LUs.

Save and reopen a configuration.

Back up and restore configuration information.

All of these topics are discussed in the Microsoft SNA Server Administration Guide (Document No. SY57265). The three that will be covered in the workbook are:

Starting and stopping SNA servers and connections.

Changing the domain of focus.

Configuring for NetView.

Starting and Stopping SNA Servers and Connections

To start an SNA server or a connection

1.	In the Servers And Connections window, select the SNA Server or connection you want.

2.	From the Services menu, choose Start Services.

You should see the server become active.

To stop an SNA server or a connection

1.	Ask all users to log off from the host.

2.	In the Servers And Connections window, select the SNA Server or connection you want to stop.

3.	From the Services menu, choose Stop Services.

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

Changing the Domain of Focus

This function allows you to work with servers in different domains by changing the domain focus as required.

To change the domain of focus of the SNA Server Admin

1.	From the File Menu, choose Select Domain. The Select Domain dialog box appears.

2.	Select the intended domain, either from the list of recently selected domains (Select Domain) or from the complete list of domains (Domains).

3.	Choose OK.

Configuring for NetView

NetView sends status information in the form of alerts between a host and its attached devices. Specifications can be made for the connection to receive NetView alerts sent from a host system (any host but a DFT connection).

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.

3.	Choose the OK button.


Installing the Client
Chapter 6	1 of 4

Installing the Client

Client software must be installed on the client computer. You can install the client software either locally, via disk, or over the network. Once it is installed, you can execute Setup to install client software. You must also specify whether the server(s) the client will be communicating with is in the local or remote domain. Local indicates that the primary server containing the configuration file is located on the same network domain. Remote indicates that the server resides on a different domain. For remote, you need to indicate the primary server name.

Windows NT-Based Client Installation

To install over the network

1.	Close any Windows NT-based applications that are running.

2.	Establish a share, and type net use x:\\servername\clients

where x represents the unused logical drive on the computer on which you are installing the client software, and servername is the name of the server.

3.	Type x:\WinNT\setup and press ENTER

To install from disk

1.	Type a:\setup and press ENTER.

The SNA Server Dialog box appears.

2.	Choose Continue.

The Client/Server Selection dialog box appears,

3.	Choose Client.

The Installation Path Dialog Box appears.

4.	To accept the default path, choose Continue.

To change the path, in the Install To box, delete the default and type the new path (using the full path), and then choose Continue.

The SNA Server Location Dialog box appears.

5.	To specify the location of the SNA server in the domain as local, choose Continue.

To specify the location of the SNA server in the domain as remote:

a.	Under SNA Server Domain, choose Remote Domain.

b.	In the Primary box, type the name of the primary server where the remote client resides.

If you want to designate a backup server, in the Backup Server box, type the name of the backup server. Type only the name; omit backslashes.

c.	Choose Continue.

The Setup Complete Dialog box appears after the files are copied.

6.	Choose OK.

Installing a Client Running Windows Version 3.1

To install over the network a client running Windows version 3.1

1.	Close any Windows applications that are running.

2.	Establish a share, x:\\servername\clients

where x represents the unused logical drive on the computer on which you are installing the client software and servername is the name of the server.

3.	In the File Run dialog box, type x:\Win16\setup and press ENTER.

To install from disk a client running Windows version 3.x

1.	Close any Windows applications that are running.

2.	In the File Run dialog box, type a:\setup and press ENTER.

The SNA Server Dialog box appears.

3.	Choose Continue.

The Client/Server Selection dialog box appears.

4.	Choose Client.

The Installation Path dialog box appears.

5.	To accept the default path, choose Continue.

To change the path, in the Install To box, delete the default and type the new path (using the full path), and then choose Continue.

The SNA Server Location dialog box appears.

6.	To specify the location of the SNA Server in the domain as local, choose Continue.

To specify the location of the SNA Server in the domain as remote:

a.	Under SNA Server Domain, choose Remote Domain.

b.	In the Primary box, type the name of the primary server where the remote client resides.

If you want to designate a backup server, in the Backup Server box, type the name of the backup server. Type only the name; omit backslashes.

c.	Choose Continue.

The Setup Complete dialog box appears after the files are copied.

7.	Choose OK.

OS/2 Client Installation

To install an OS/2 Client

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

2.	Establish a share, x:\\servername\clients

where x represents the unused logical drive on the computer on which you are installing the client software and servername is the name of the server.

3.	Type x:\os2\setup (from disk, type a:\setup), and press ENTER.

The SNA Server dialog box appears.

4.	Choose Continue.

The Client/Server Selection dialog box appears.

5.	Choose Client.

The Installation Path dialog box appears. To accept the default path, choose Continue.

6.	To change the path, in the Install To box, delete the default and type the new path (using the full path), and then choose Continue.

The SNA Server Location dialog box appears.

7.	To specify the location of the SNA server in the domain as local, choose continue.

To specify the location of the SNA server in the domain as remote:

a.	Under SNA Server Domain, choose Remote Domain.

b.	In the Primary box, type the name of the primary server where the remote client resides.

If you want to designate a backup server, in the Backup Server box, type the name of the backup server. Type only the name; omit backslashes.

c.	Choose Continue.

The Setup Complete dialog box appears.

8.	Choose OK.

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

Installing an MS-DOS–Based Client

To install an MS-DOSbased client

1.	Establish a share by typing:

net use x:\\servername\clients

where x represents the unused logical drive on the computer on which you are installing the client software and servername is the name of the server.

2.	Type:

x:\dos\setup

To install an MS-DOSbased client from a disk

1.	Type a:\setup, and then press ENTER.

The SNA Server dialog box appears.

2.	Choose Continue.

The Client/Server Selection dialog box appears.

3.	Choose Client.

The Installation Path dialog box appears.

4.	To accept the default path, choose Continue.

To change the path, in the Install To box, delete the default and type the new path (using the full path), and then choose Continue.

The SNA Server Location Dialog box appears.

5.	To specify the location of the SNA servers in the domain as local, choose continue.

6.	To specify the location of the SNA servers in the domain as remote:

a.	Under SNA Server Domain, choose Remote Domain.

b.	In the Primary box, type the name of the primary server where the remote client resides.

If you want to designate a backup server, in the Backup Server box, type the name of the backup server. Type only the name; omit backslashes.

7.	Choose Continue

The Setup Complete dialog box appears.

8.	Choose OK.

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


Client Option Modification
Installing the Client 	2 of 4

Client Option Modification

Once a client is installed, you may want to change the options selected during Setup, such as changing the server operation from local to remote. When Setup is run, it determines whether a version of the SNA Server is already installed. If so, Setup assumes that you want to modify or remove the client software.

Modifying a Client Running Windows NT or Windows Version 3.1

To modify a client running Windows NT or Windows version 3.1

1.	Invoke the Setup utility (as you did during installation).

2.	When the SNA Server Setup dialog box appears, choose Continue.

The Setup Options dialog box appears.

3.	Choose Reinstall. Setup will present the same dialog boxes as those used to install the SNA Server client.

4.	Complete the dialog boxes with the chosen modifications to the client configuration.

The Setup Complete dialog box appears.

5.	Choose OK.

6.	Restart your computer to put the changes into effect.

Modifying a Client Running MS-DOS or OS/2

To modify a client running MS-DOS or OS/2

1.	Invoke the Setup utility (as you did during installation).

2.	When the SNA Server Setup dialog box appears, choose Continue.

The Setup Options dialog box appears.

3.	Choose Reinstall. Setup will present the same dialog boxes as those used to install the SNA Server client.

4.	Complete the dialog boxes with the chosen modifications to the client configuration.

The Setup Complete dialog box appears.

5.	Choose OK.

6.	Restart your computer to put the changes into effect.


Removing Clients
Installing the Client 	3 of 4

Removing Clients

Once a client is installed, you may want to remove it.

To remove a client running Windows NT or Windows version 3.1

1.	Invoke the Setup utility (as you did during installation).

2.	When the SNA Server Setup dialog box appears, choose Continue.

3.	When the Setup Options dialog box appears, choose Remove The SNA Client.

4.	Choose Continue.

5.	At the confirm prompt, choose Continue.

6.	After all the files have been deleted, exit Setup.

7.	Restart your computer to put the changes into effect.

To remove a client running MS-DOS or OS/2

1.	Invoke the Setup utility (as you did during installation).

2.	When the SNA Server Setup dialog box appears, choose Continue.

3.	When the Setup Options dialog box appears, choose Remove The SNA Client.

4.	Choose Continue.

5.	At the confirm prompt, choose Continue.

6.	After all the files have been deleted, exit Setup.

7.	Restart your computer to put the changes into effect.


Finding Additional Information
Installing the Client 	4 of 4

Finding Additional Information

The Microsoft SNA Server Installation Guide (Document No. SY57266) gives detailed information on the installation procedure.


Diagnostic Tools
Chapter 7	1 of 3

Diagnostic Tools

Overview

This chapter introduces the diagnostic tools and trace facilities in Windows NT and SNA Server. These tools provide you with means to collect general troubleshooting information regarding problem events and system status as they relate to servers, connections, LUs, NetView interfaces, and general system events. There are a variety of sources from which to collect trace and detailed system information to assist you in troubleshooting problems with the SNA Server. The type of information you will need will dictate the tool you will use to collect the data. This information is useful when you are working to improve performance or solve a difficult problem in your SNA installation. Product support technicians may also request this level of detail when working with you to solve a problem.


What You Will Learn
Diagnostic Tools	2 of 3

Overview

What You Will Learn

After completing this chapter, you will be able to:

Check the status of the SNA Server, including the number of active users and session information.

Check the status of connections.

Check the status of the LUs.

View access application events.

Configure to provide detailed NetView data.

Collect trace information.

Configure for response and performance monitoring.


Diagnostic Information Tools
Diagnostic Tools	3 of 3

Overview

Diagnostic Information Tools

SNA Server provides several tools that allow you to collect information about events prior to a system difficulty and the state of your system when the difficulty occurred. The following diagnostic tools are available to you:

SNA Server Admin

Event View Utility

SNA Server Trace

Performance Monitor Utility

Response Time Monitor

NetView

SNA Server Admin

When a service appears to be having difficulty, it may be helpful to gather status information before making the decision about starting, stopping, resetting, or modifying the service.

To view the status of the SNA Server

1.	In the Servers And Connections menu, select the server you want to view.

2.	From the Services menu, choose Properties, or double-click on the highlighted server.

3.	The Server Properties dialog box appears, showing the status of the server and the session.

4.	When viewing is complete, choose the Cancel button.

To view the status of a connection

1.	In the Servers And Connections window, select the connection you want to view. Under the Status column, the connection will show active, inactive, not configured, or N/A (not available).

2.	From the Services menu, choose Properties. The Connection Properties dialog box appears.

3.	When viewing is complete, choose the Cancel button.

To view the status of an LU (non-APPC)

1.	In the Servers And Connections window, select the connection used by the LU.

2.	Find the LU listed and view the Status column (inactive, in session, and so on).

To view the status of an APPC LU

1.	In the Servers And Connections window, select the local or remote APPC LU you want to view.

Under the Status column, the LU will show active, inactive, not configured, or N/A.

2.	From the Services menu, choose Properties, or double-click on a highlighted LU. The APPC LU Properties dialog box or the APPC Remote LU Properties dialog box appears.

3.	In the APPC LU Properties dialog box, choose the Status button. The APPC LU Status dialog box appears.

4.	Select the LU-LU pair your are investigating, and then choose the Zoom button. The APPC LU Status dialog box appears and will show status as inactive or will indicate the number of active sessions.

5.	When viewing is complete, choose the Close or Cancel button.

To view the 3270 LUs being used by an active user

1.	From the View menu in the Users And Groups window, choose Active Users.

2.	Select the active user.

3.	View the LUs listed in the LU or LU Pool column.

Windows NT Event Viewer Utility

This is a Windows NT utility that provides information on the sequence and type of events that led up to a particular state or situation. To assist in testing configurations and diagnosing problems, Windows NT keeps event log files, which are stored in WindowsRoot\SYSTEM32\CONFIG\*.EVT.

You may specify parameters for event logs that include the server on which event logs are to be stored, the types of events to be recorded, and any additional servers to which pop-up error messages should be routed.

To specify event types and servers for event logging

1.	Bring up the Windows NT Event Viewer.

2.	From the Options Menu, choose Logs. The Error/Audit Logging And Popups dialog box appears.

3.	In the Centralized Event Log Server dialog box, type the name of the server on which event logs should be stored (or select the server from the list that appears). To store event logs for this server on this server, select [Local System].

4.	Under the Default Audit Log Level select:

Detailed Problem Analysis: This log level records all events that can be recorded.

General Information Messages: This log level records general activity, but not all possible events.

Significant System Events: This log level records major system events.

Audit Logging Disabled: This option turns off all audit logging.

5.	In the Route All Server Popup Messages To box, type or select the additional server(s) to which pop-up error messages will be sent.

6.	When all settings are correct, choose the OK button.

To view the SNA Server Event Logs

1.	Start the Windows NT Event Viewer.

2.	From the Log Menu, choose Application.

3.	Under the Source heading, the SNA events are events whose names begin with SNA.

4.	Select an event, and from the View menu, choose Detail. Or double-click on the highlighted event to view additional information on an event.

SNA Server Trace

SNA Server Trace (snatrace) turns on tracing for SNA Server and Windows NT-based clients. For other clients, tracing is turned on with special commands or with lines in an initialization file. Trace files record activity between or within components of the SNA Server. The 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 The trace files containing diagnostic information are located at SNAroot\TRACES\*.TRC

First, decide which software components you need information about to determine what type of trace you will need to run. This table will help you decide what type of trace to apply to gather the needed information.

Trace	Traced Activity		Applies to
Internal	Within a software component of SNA Server		SnaBase, SnaServer (PU2.1 node) SNA Applications, link services
Message	Messages passed into and out of a software component of the SNA Server		SnaBase, SnaServer (PU2.1 node), SNA Applications, link services
API	Information passed into and out of an SNA Server DLL, for example, APPC DLL		SNA Applications
SNA Server Trace Options

You can enable or disable trace options on an SNA server or a Windows NT-based client.

To set trace options

1.	Switch to command prompt.

2.	At the command prompt, type:

snatrace

The SNA Server Trace Options dialog box appears.

3.	In the Service Name box, select a service name from the list:

Service Name	Activity traced
SNA Applications	Activity generated by applications that use SNA APIs
SnaServer	Activity generated as the local SNA Server (PU2.1) interacts with clients and other nodes on the SNA network
Name of link	Activity between link service and other software components
4.	Under SnaBase Internal Tracing, drag the scroll box to the level of internal tracing you want for the selected service.

Trace Option	Activity for SNA application on the local system
Admin Messages	Messages between Server Admin and SnaBase and SnaServer
3270 Messages	Messages between 3270 applications and the SnaServer
LU6.2	Messages between the APPC DLL on the local system and the SnaServer
To disable message tracing, choose the Clear button.

5.	If the selected service is SNA Applications, select options for API tracing:

Trace Option	Activity traced for the SnaServer (PU2.1 node)
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/SLI and LUA/RUI applications and the LUA DLL on the SNA Server
CSV API	Activity between CSV applications and the CSV DLL on the SNA Server
For the selected service, select options for message tracing:

Trace Option	Activity traced for the SnaServer (PU2.1 node)
Admin Messages	Messages between Server Admin and SnaBase and SnaServer
3270 Messages	Messages between 3270 applications and the SnaServer
LU6.2	Messages between the APPC DLL on the local system and the SnaServer
To disable message tracing, choose the Clear button.

6.	Select or clear the Minimize Disk Access By Buffering Writes check box:

To minimize the writing of trace information to disk and cause the information to be held in a memory buffer until it is efficient to write it to disk, select this box.

To cause trace information to be written to disk, clear this box.

7.	Repeat steps 3-6 for each service you want to trace.

8.	Choose the OK button.

Tracing for Clients Running Windows Version 3.1

Tracing for SNA Server clients running Windows version 3.1 is similar to using tracing on an SNA server, except:

Tracing on a client provides information about the activity of the client only, not activity on the SNA server.

The software components that can be traced on an SNA Server client running Windows 3.1 are SNA applications, specifically the APIs used by the applications and SnaBase.

Tracing for SNA Server clients running Windows 3.1 is enabled or disabled by modifying the WIN.INI file.

Internal tracing cannot be carried out on a client running Windows 3.1 until certain files on the hard disk of the client are replaced with corresponding files from the floppy disk for installing SNA Server client software. The files modify the way that the software works, so that internal tracing is possible.

First, decide which software components you need information about to determine what type of trace you will need to run. This table will help you decide what type of trace to apply to gather the needed information.

Traced	Traced activity		Applies to
Internal	Within a software component of SNA Server		SnaBase, SNA Applications
Message	Messages passed into and out of a software component of the SNA Server		SnaBase, SNA Applications
API	Information passed into and out of an SNA Server DLL, for example, APPC DLL		SNA Applications
SNA Server Trace Options for Running Windows 3.1 Clients

You can enable or disable trace options for clients running Windows 3.1.

To set trace options

1.	Load the WIN.INI file into a text editor.

2.	Locate the [WNAP] section of the file.

3.	Add, modify, or remove lines in the [WNAP] section heading as shown:

Trace	Lines to add to WIN.INI
Internal	InternalTraceLevel=xwhere x is a value from 0 (full internal tracing) through 16 (no internal tracing) InternalTraceFile1=path\filename1 InternalTraceFile1=path\filename2 InternalMessageTraceState-{on|off}
Message	MessageTraceFile1=path\filename1 MessageTraceFile1=path\filename2
SNA APPLs	APITraceFile1=path\filename1 APITraceFile2=path\filename2
	Specify the trace filenames as shown above and add one or more of the following items:
	Trace		Line to add to WIN.INI
	APPC		APPCTraceState={on|off}
	CSV		CSVTraceState={on|off}
	RUI		RUITraceState={on|off}
	FMI		FMITraceState={on|off}
	PVI		PVITraceState={on|off}
	HLLAPI		HLLAPITraceState={on|off}
	CPIC		CPICTraceState={on|off}
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 filenames for the trace files.

APPCTraceState=on
APITraceFile1=c:\traces\api_tr1.trc
APITraceFile2=c:\traces\api_tr2.trc

4.	Save the WIN.INI file as plain (ASCII) text.

5.	Copy files to the hard disk of the client if you are using internal tracing (see the following procedure).

6.	Stop and restart the Windows 3.1 software.

Note

Created trace files will be stored in the path(s) specified by the lines in the WIN.INI file.

Required Files for a Client Running Windows 3.1

For tracing clients on Windows 3.1, you need to replace certain files on the hard disk of the client with corresponding files from the floppy disk for installing SNA Server client software. The files modify the way that the software operates to enable internal tracing. Once tracing is no longer required, recopy originals to restore the user to a normal level of efficiency.

To copy files needed for enabling internal tracing

1.	Stop the SNA Server and the Window 3.1 software on the client computer.

2.	Locate the floppy disk for installing SNA Server client software, and insert the floppy disk into a drive.

3.	On the client computer, change to the SYSTEM subdirectory of the Windows root directory.

4.	Copy the following files from the TRACE directory on the floppy disk to the SYSTEM subdirectory of the Windows root directory:

LMCLI.DLLWINAPPC.DLLWINCPIC.DLL

WDMOD.DLLWINCSV.DLLWINTRC.DLL

WLOGTR.DLLWNAP.EXE

5.	Remove the floppy from the drive and restart the SNA Server and Windows 3.1 software.

Tracing for Clients Running MS-DOS

Tracing for SNA Server clients running MS-DOS is similar to using tracing on an SNA server, except:

Tracing on a client provides information about the activity of 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 SnaBase.

Tracing for an MS-DOS–based client is enabled or disabled by modifying the SNA.INI file.

Internal tracing cannot be carried out on an MS-DOS–based client until certain files on the hard disk of the client are replaced with corresponding files from the floppy disk for installing SNA Server client software. The files modify the way that the software works, so that internal tracing is possible.

First, decide which software components you need information about to determine what type of trace you will need to run. This table will help you decide what type of trace to apply to gather the needed information.

Trace	Traced activity		Applies to
Internal	Within a software component of SNA Server		SnaBase, SNA Applications
API	Information passed into and out of an SNA Server DLL, for example, APPC DLL		SNA Applications
SNA Server Trace Options for Running MS-DOS Clients

You can enable or disable trace options for clients running MS-DOS.

To set trace options

1.	Load the SNA.INI file into a text editor.

2.	Locate the [SNABASE] section of the file.

3.	Add, modify, or remove lines in the [SNABASE] section heading as shown:

Trace		Lines to add to WIN.INI
Internal		InternalTraceLevel=x where x is a value from 0 (full internal tracing) through 16 (no internal tracing) InternalTraceFile1=path\filename1 InternalTraceFile1=path\filename2 InternalMessageTraceState-{on|off}
Message		MessageTraceFile1=path\filename1 MessageTraceFile1=path\filename2
SNA APPLs		APITraceFile1=path\filename1 APITraceFile2=path\filename2
			Specify the trace filenames as shown above and add one or more of the following items:
APPC		APPCTraceState={on|off}
CSV		CSVTraceState={on|off}
RUI		RUITraceState={on|off}
HLLAPI		HLLAPITraceState={on|off}
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 filenames for the trace files.

APPCTraceState=on
APITraceFile1=c:\traces\api_tr1.trc
APITraceFile2=c:\traces\api_tr2.trc

4.	Save the SNA.INI file as ASCII text.

5.	Copy files to the hard disk of the client, if you are using internal tracing.

6.	Restart the computer.

Note

Created trace files will be stored in the path(s) specified by the lines in the SNA.INI file.

Required Files for Clients Running MS-DOS

For tracing clients on MS-DOS, you need to replace certain files on the hard disk of the client with corresponding files from the floppy disk for installing SNA Server client software. The files modify the way that the software operates to enable internal tracing. Once tracing is no longer required, recopy originals to restore the user to a normal level of efficiency.

To copy files needed for enabling internal tracing

1.	Stop the SNA Server software on the MS-DOSbased client computer.

2.	Locate the floppy disk for installing SNA Server client software, and insert the floppy disk into a drive.

3.	On the client computer, change to the SNA Server root directory.

4.	Copy the following files from the TRACE directory on the floppy disk to the SNA Server root directory:

LMBASE.EXENEWBASE.EXE

5.	Remove the floppy from the drive and restart the SNA Server client software.

Tracing for Clients Running on OS/2

Tracing for SNA Server clients running OS/2 is similar to using tracing on an SNA server, except:

Tracing on a client provides information about the activity of the client only, not activity on the SNA Server.

Tracing for an OS/2-based client is enabled or disabled by modifying the set command. The set command sets environment variables for the operating system, including the variables for tracing for the SNA Server. You can type the set command at the command prompt, or include it in the STARTUP.CMD file.

First, decide which software components you need information about to determine what type of trace you will need to run. This table will help you decide what type of trace to apply to gather the needed information.

Trace	Traced activity		Applies to
Internal	Within a software component of SNA Server		SnaBase,SNA Applications
Message	Messages passed into and out of a software component of the SNA Server		SnaBase,SNA Applications
API	Information passed into and out of an SNA Server DLL, for example, APPC DLL		SNA Applications
SNA Server Trace Options for Running OS/2 Clients

You can enable or disable trace options for clients running in an OS/2 environment by using the set command.

To set trace options

The set command can be run in the following ways:

1.	Type set at the command prompt, and then press ENTER. At that point, tracing will be available in that screen group. The option remains in effect until changed by another set command, or until the system is restarted.

2.	Type the set command into an initialization file and reference the initialization file in CONFIG.SYS. This can be done by adding the following string to the end of the protshell command in CONFIG.SYS: /k c:os2init.cmd

3.	Type the set command(s) into a file named OS2INIT.CMD and save the file. The trace option takes effect when the system is restarted.

Note

Created trace files are stored in the path(s) specified in the set command.

Trace Options

Following are trace options and the corresponding syntax to use in the set command.

Trace	Syntax to use with set command
Internal	set comint=tracelevel/path\filename1/path\filename2 where tracelevel is an even number 0 (full internal tracing) through 16 (no internal tracing)
SNA APPLs	set comtrc=path\filename1/path\filename2
All messages	set comsna=path\filename/path\filename2/a
3270 & LUA	set comsna=path\filename/path\filename2/f messages
LU6.2	set comsna=path\filename/path\filename2/p messages
Example

3270 client tracing 3270 messages for SNA applications:

set comsna=\traces\3270msg1.trc/\traces\3270msg2.trc/f

LU6.2 messages for SNA applications:

set comsna=\traces\lu62msg1.trc/\traces\LU62msg2.trc/p

Windows NT Performance Monitor Utility

The Performance Monitor is a graphical tool that allows you to measure the performance of computers in the network. The Performance Monitor oversees SNA objects as configured by the user. You can select counters that you want to measure. It is important to note that before any SNA Server counters can be measured, one or more SNA servers must be operating. Counters available are shown in the following table:

Object available for monitoring	Counters available
SNA Connections	Data Bytes Received/Sec Data Bytes Transmitted/Sec Throughput Bytes/Sec
SNA LU Sessions	Data Bytes Received/Sec Data Bytes Transmitted/Sec Throughput Bytes/Sec
Data Bytes Received/Sec	Adapter Failures Data Bytes Received/Sec Data Bytes Transmitted/Sec Throughput Bytes/Sec Throughput Frames/Sec Frames Received/Sec Frames Transmitted/Sec Successful Connects
Response Time Monitor (RTM)

The Response Time Monitor (RTM) is an IBM function that measures the length of time host responses take during a 3270 session. The SNA Server Administration Tool allows you to specify the times at which RTM should send data and define the triggers that will cause RTM to register that the host has responded. Note that the emulator that your 3270 users have must support RTM for these settings to be meaningful.

To configure 3270 RTM Settings

1.	From the Options menu, choose RTM Triggers. The 3270 RTM dialog box appears.

2.	Specify the following:

RTM Data Sent at

Select one or both.

Counter Overflow causes RTM data to be sent to the host when the number of host responses in a given period overflows the size of the available counter. End Of Session waits until a session has ended.

RTM Timers Run Until

Select the point on which the host is to register response.

First Data Reaches Screen  To stop timing when data reaches the local screen, select this button.

Host Unlocks Keyboard  To stop timing when the host unlocks the local keyboard, select this button.

Host Lets User Send  To stop timing when the host lets the local computer send more data, select this button.

RTM Thresholds  Specify the cutoff times in tenths of a second at which RTM saves its count response and restarts count.

3.	Accept the settings by choosing the OK button.

SNA Server NetView Options

NetView is a reporting system that runs on the IBM host that supports a reporting system that sends alerts and other information back and forth between the host mainframe and computers connected to it. The SNA Server can forward alerts that help the SNA network manager diagnose problems and improve system performance, and 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. Through the support of the NVRunCmd, commands can be forwarded from a NetView console to be run on the SNA Server.

Configuring NetView Alerts

This function allows the user to send NetView alerts to a host operator, assuming the emulator in use is capable of sending such alerts.

To configure NetView alerts

1.	From the Options menu, choose NetView.

2.	Select the alert you want to configure in the NetView Alerts box.

3.	Choose the Edit button.

4.	Configure the following:

Alert Descriptions

Type in an alert description as specified by the host operator.

Parameter1, Parameter2, and Parameter3

If you want the server to prompt the user for additional information when the user requests the specified alert, enter the appropriate prompt(s) in the Parameter 1, Parameter 2, and/or Parameter 3 fields.

5.	When all the settings are correct, choose the OK button.

NVAlert Service

With NVAlert, events on the Windows NT system can be sent to NetView as generic alerts. By itself, NetView can forward SNA Server alerts to the host system. With NVAlert, two more categories of alerts can also be forwarded:

Alerts generated by the Windows NT operating system, such as a disk becoming full.

Alerts generated by the Windows NT-based applications, such as an application failure.

The NVAlert service is installed by the SNA Server Setup program, at which time an NVAlert configuration file, NVALERT.INI, is created in the SERVICES subdirectory of the SNA Server root directory. In order to control the NVAlert service, you must modify the NVALERT.INI file to specify the Windows NT-based alerts that you want forwarded to the host. The NVAlert service runs as a background process waiting for an event to be recorded in the 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 to the host.

NVALERT.INI Modification

To add alerts that will be sent by NVAlert, add sections to the NVALERT.INI file found in the SERVICES subdirectory of the SNA Server root directory. It is most efficient to copy and then modify the existing sections.

To add required lines for alerts in NVALERT.INI

1.	Add a section to NVALERT.INI for each alert, beginning with the heading [source.type.eventid].

For source, substitute the name that appears beneath the Source heading in the Windows NT Event Viewer.

For type, find the Type listing in the Windows NT Event Viewer and substitute one of the following values:

Success	0
Information	1
Warning	2
Error	3
For eventid, substitute the decimal number that appears beneath the EventID heading in the Windows NT Event Viewer.

2.	Beneath each bracketed heading, type the following lines:

AlertType=xx

AlertDescription=xxxx

ProbableCauses=xxxx[,...]

Each letter x represents a hexadecimal digit; the digits specify NetView code points. For information about the appropriate values to provide, refer to the IBM NetView technical 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.

3.	Optional Lines for Alerts in NVALERT.INI

You can also add the following optional lines to the entry for each alert. Note that RecAct stands for recommended action and DetData:

UserCauses=xxxx[,...]

UserDetData=xx,yy,string[;...]

UserRecAct=xxxx[,...]

UserRecActDetData=xx,yy,string[;...]

FailureCauses=xxxx[,...]

FailureDetData=xx,yy,string[;...]

FailureRecAct=xxxx[,...]

FailureRecActDetData=xx,yy,string[;...]

InstallCauses=xxxx[,...]

InstallDetData=xx,yy,string[;...]

InstallRecAct=xxxx[,...]

InstallRecActDetData=xx,yy,string[;...]

Example of NVALERT.INI Section

This example warns that a hard disk is nearly full. This alert has the following characteristics:

The source is Srv
The type is 2 (warning)
The eventid is 2013

The event description in the Windows NT log is:

The C: disk is at or near capacity. You may need to delete some files.

The NVALERT.INI should be set up as follows to forward the alert to the host:

[Srv.2.2013]	Source Srv, type 2 (warning), EventID 2013

AlertType = 11	Impending problem

AlertDescription = 5002Resource nearing capacity

ProbableCauses = 5001Media DASD device

UserCauses = 0102,F0A0Insufficient storage media space available

UserDetData = 29,95,%C

NVRunCmd Service

The NVRunCmd runs as a background process on the SNA server, providing a vehicle for commands typed at a host-system NetView console to be carried out on the SNA server, with command results sent back to the host. The NVRunCmd uses the NetView reporting system for transferring information between the host and the SNA server.

Commands are typed in at the NetView console and case is ignored, so the command can be uppercase, lowercase, or a combination. The structure is:

runcmd sp=servicepoint,appl=NVRunCmd cmd WinNTcommand

Supply the following values:

service point = PU name on which WinNTcommand should be run (Control Point Name for the server).

WinNTcommand = any command that can be processed by the Windows NT system and does not return a graphical output.

parameters = substitute any parameters needed for running the command on the SNA server.

Note

At the SNA server named by servicepoint, NVRunCmd receives the information in WinNTcommand, and passes it to the Windows NT system.

Functionality Review of NVRunCmd

NVRunCmd can process any command entered at a host-system console, within the following limitations:

The maximum amount of information that can be returned to NetView is 64K.

Case is ignored; lowercase is automatically 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.