Copyright: TN3270 Service
Citation: TN3270 Service


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


TN3270 Service Contents
Microsoft SNA Server

TN3270 Service

Contents

Before You Begin

Chapter 1    Overview

Chapter 2    Installing TN3270 Service

Chapter 3    Configuring TN3270 Service

Chapter 4    Specifying Administrative Options

Chapter 5    Administering TN3270 Service

Chapter 6    Using TN3270 Trace Option

Appendix A    Server and Connection User Fields

Appendix B    Troubleshooting

Appendix C    Messages

Appendix D    IBM Terminal Type Support

Appendix E    Performance Counters

Appendix F    Registry Value Entries


TN3270 Service, Welcome
Microsoft SNA Server

TN3270 Service

Contents

Before You Begin

Document Conventions

Common Abbreviations

Finding Further Information

Chapter 1    Overview

Chapter 2    Installing TN3270 Service

Chapter 3    Configuring TN3270 Service

Chapter 4    Specifying Administrative Options

Chapter 5    Administering TN3270 Service

Chapter 6    Using TN3270 Trace Option

Appendix A    Server and Connection User Fields

Appendix B    Troubleshooting

Appendix C    Messages

Appendix D    IBM Terminal Type Support

Appendix E    Performance Counters

Appendix F    Registry Value Entries


TN3270 Service, Chapter 1
Microsoft SNA Server

TN3270 Service

Contents

Before You Begin

Chapter 1    Overview of TN3270 Service

Overview of TN3270 Service Installation

System Requirements

Pre-Installation Considerations

SNA Server and Host Configuration

TN3270 Service and Host Configuration

Chapter 2    Installing TN3270 Service

Chapter 3    Configuring TN3270 Service

Chapter 4    Specifying Administrative Options

Chapter 5    Administering TN3270 Service

Chapter 6    Using TN3270 Trace Option

Appendix A    Server and Connection User Fields

Appendix B    Troubleshooting

Appendix C    Messages

Appendix D    IBM Terminal Type Support

Appendix E    Performance Counters

Appendix F    Registry Value Entries


TN3270 Service, Chapter 2
Microsoft SNA Server

TN3270 Service

Contents

Before You Begin

Chapter 1    Overview

Chapter 2    Installing TN3270 Service

Setup Versus TN3270 Service Admin

Components Installed by Setup

Installing TN3270 Service

Starting the TN3270 Service Setup Program

Specifying the Installation Path

Exiting Setup

Removing TN3270 Service

Chapter 3    Configuring TN3270 Service

Chapter 4    Specifying Administrative Options

Chapter 5    Administering TN3270 Service

Chapter 6    Using TN3270 Trace Option

Appendix A    Server and Connection User Fields

Appendix B    Troubleshooting

Appendix C    Messages

Appendix D    IBM Terminal Type Support

Appendix E    Performance Counters

Appendix F    Registry Value Entries


TN3270 Service, Chapter 3
Microsoft SNA Server

TN3270 Service

Contents

Before You Begin

Chapter 1    Overview

Chapter 2    Installing TN3270 Service

Chapter 3    Configuring TN3270 Service

Viewing SNA Resource Information

Adding an LU

Editing a TN3270 LU Configuration

Deleting an LU

Reopening a TN3270 Configuration

Backing Up a TN3270 Configuration

Restoring a TN3270 Configuration

Chapter 4    Specifying Administrative Options

Chapter 5    Administering TN3270 Service

Chapter 6    Using TN3270 Trace Option

Appendix A    Server and Connection User Fields

Appendix B    Troubleshooting

Appendix C    Messages

Appendix D    IBM Terminal Type Support

Appendix E    Performance Counters

Appendix F    Registry Value Entries


TN3270 Service, Chapter 4
Microsoft SNA Server

TN3270 Service

Contents

Before You Begin

Chapter 1    Overview

Chapter 2    Installing TN3270 Service

Chapter 3    Configuring TN3270 Service

Chapter 4    Specifying Administrative Options

Chapter 5    Administering TN3270 Service

Chapter 6    Using TN3270 Trace Option

Appendix A    Server and Connection User Fields

Appendix B    Troubleshooting

Appendix C    Messages

Appendix D    IBM Terminal Type Support

Appendix E    Performance Counters

Appendix F    Registry Value Entries


TN3270 Service, Chapter 5
Microsoft SNA Server

TN3270 Service

Contents

Before You Begin

Chapter 1    Overview

Chapter 2    Installing TN3270 Service

Chapter 3    Configuring TN3270 Service

Chapter 4    Specifying Administrative Options

Chapter 5    Administering TN3270 Service

Viewing TN3270 Service Session Status

Starting TN3270 Service

Pausing TN3270 Service

Continuing TN3270 Service

Stopping TN3270 Service

Chapter 6    Using TN3270 Trace Option

Appendix A    Server and Connection User Fields

Appendix B    Troubleshooting

Appendix C    Messages

Appendix D    IBM Terminal Type Support

Appendix E    Performance Counters

Appendix F    Registry Value Entries


TN3270 Service, Chapter 6
Microsoft SNA Server

TN3270 Service

Contents

Before You Begin

Chapter 1    Overview

Chapter 2    Installing TN3270 Service

Chapter 3    Configuring TN3270 Service

Chapter 4    Specifying Administrative Options

Chapter 5    Administering TN3270 Service

Chapter 6    Using TN3270 Trace Option

Enabling TN3270 Service Trace Option

Disabling TN3270 Service Trace Option

Appendix A    Server and Connection User Fields

Appendix B    Troubleshooting

Appendix C    Messages

Appendix D    IBM Terminal Type Support

Appendix E    Performance Counters

Appendix F    Registry Value Entries


TN3270 Service, Appendix A
Microsoft SNA Server

TN3270 Service

Contents

Before You Begin

Chapter 1    Overview

Chapter 2    Installing TN3270 Service

Chapter 3    Configuring TN3270 Service

Chapter 4    Specifying Administrative Options

Chapter 5    Administering TN3270 Service

Chapter 6    Using TN3270 Trace Option

Appendix A    Server and Connection User Fields

Appendix B    Troubleshooting

Appendix C    Messages

Appendix D    IBM Terminal Type Support

Appendix E    Performance Counters

Appendix F    Registry Value Entries


TN3270 Service, Appendix B
Microsoft SNA Server

TN3270 Service

Contents

Before You Begin

Chapter 1    Overview

Chapter 2    Installing TN3270 Service

Chapter 3    Configuring TN3270 Service

Chapter 4    Specifying Administrative Options

Chapter 5    Administering TN3270 Service

Chapter 6    Using TN3270 Trace Option

Appendix A    Server and Connection User Fields

Appendix B    Troubleshooting

TN3270 Protocol Overview

Session Initiation

Ignore Error Message

Appendix C    Messages

Appendix D    IBM Terminal Type Support

Appendix E    Performance Counters

Appendix F    Registry Value Entries


TN3270 Service, Appendix C
Microsoft SNA Server

TN3270 Service

Contents

Before You Begin

Chapter 1    Overview

Chapter 2    Installing TN3270 Service

Chapter 3    Configuring TN3270 Service

Chapter 4    Specifying Administrative Options

Chapter 5    Administering TN3270 Service

Chapter 6    Using TN3270 Trace Option

Appendix A    Server and Connection User Fields

Appendix B    Troubleshooting

Appendix C    Messages

Event Log Messages

Client Messages

Appendix D    IBM Terminal Type Support

Appendix E    Performance Counters

Appendix F    Registry Value Entries


TN3270 Service, Appendix D
Microsoft SNA Server

TN3270 Service

Contents

Before You Begin

Chapter 1    Overview

Chapter 2    Installing TN3270 Service

Chapter 3    Configuring TN3270 Service

Chapter 4    Specifying Administrative Options

Chapter 5    Administering TN3270 Service

Chapter 6    Using TN3270 Trace Option

Appendix A    Server and Connection User Fields

Appendix B    Troubleshooting

Appendix C    Messages

Appendix D    IBM Terminal Type Support

Appendix E    Performance Counters

Appendix F    Registry Value Entries


TN3270 Service, Appendix E
Microsoft SNA Server

TN3270 Service

Contents

Before You Begin

Chapter 1    Overview

Chapter 2    Installing TN3270 Service

Chapter 3    Configuring TN3270 Service

Chapter 4    Specifying Administrative Options

Chapter 5    Administering TN3270 Service

Chapter 6    Using TN3270 Trace Option

Appendix A    Server and Connection User Fields

Appendix B    Troubleshooting

Appendix C    Messages

Appendix D    IBM Terminal Type Support

Appendix E    Performance Counters

TN3270 Service Object

TN3270 Session Object

TN3270 SNA Resource Object

Appendix F    Registry Value Entries


TN3270 Service, Appendix F
Microsoft SNA Server

TN3270 Service

Contents

Before You Begin

Chapter 1    Overview

Chapter 2    Installing TN3270 Service

Chapter 3    Configuring TN3270 Service

Chapter 4    Specifying Administrative Options

Chapter 5    Administering TN3270 Service

Chapter 6    Using TN3270 Trace Option

Appendix A    Server and Connection User Fields

Appendix B    Troubleshooting

Appendix C    Messages

Appendix D    IBM Terminal Type Support

Appendix E    Performance Counters

Appendix F    Registry Value Entries

Entry Value Descriptions


Before You Begin
1 of 4

Before You Begin

Microsoft SNA Server TN3270 Service explains how to install and administer Microsoft SNA Server TN3270 Service.


Document Conventions
2 of 4

Document Conventions

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

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


Common Abbreviations
3 of 4

Common Abbreviations

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

Abbreviation	Description
API	application programming interface
APPC	Advanced Program-to-Program Communications
DLC	data link control
DLL	dynamic-link library
DSR	data-set-ready
DTR	data-terminal-ready
EBCDIC	Extended Binary Coded Decimal Interchange Code
LU	logical unit
LUA	conventional Logical Unit Application programming interface
MB	megabyte
NCP	Network Control Panel
PU	physical unit
RU	request/response unit
RUI	Request Unit Interface
SNA	Systems Network Architecture
SNA Server	Microsoft [image] SNA Server for SNA Server
SSCP	system services control point
TCP/IP	Transmission Control Protocol/Internet Protocol
TN3270 Service	TN3270 Service for Windows NT
VTAM	Virtual Telecommunications Access Method


Finding Further Information
4 of 4

Finding Further Information

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

Microsoft SNA Server Planning Guide

Microsoft SNA Server Enhancements Guide

Microsoft SNA Server Installation Guide

Microsoft SNA Server Administration Guide

Microsoft SNA Server Reference

Microsoft SNA Server 3270/5250 Applet User’s Guide

Microsoft SNA Server APPC Programmer’s Guide

Microsoft SNA Server CPI-C Programmer’s Guide

Microsoft SNA Server LUA Programmer’s Guide

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

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

IBM 3270 Information Display System: Color and Programmed Symbols

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

IBM Systems Network Architecture: Technical Overview

IBM Systems Network Architecture: Concepts and Products

IBM Advanced Communications Function Products Installation Guide

IBM Installation and Resource Definition

IBM 9370 LAN Token Ring Support

IBM SNA Format and Protocol Reference Manual: Architectural Logic


Overview
Chapter 1	1 of 6

Overview of TN3270 Service

TN3270 Service combines client/server architecture with the power and productivity of the Windows NT [image] operating system. By using TN3270 Service you can provide access to your host mainframe environment for TN3270 clients performing 3270 terminal emulation.

TN3270 Service is implemented as a Windows NT service similar to SNA Server. SNA Server and TN3270 Service communicate through the Logical Unit Application (LUA) programming interface. TN3270 Service communicates with TN3270 clients over TCP/IP connections using the TN3270 protocol.

TN3270 Service is a client to the SNA server and a server to TN3270 clients.


Overview of TN3270 Service Installation
Overview	2 of 6

Overview of TN3270 Service Installation

To install TN3270 Service, do the following in the order given

1.	Install SNA Server(s).

2.	Install TN3270 Service.

3.	Install TN client(s).

If TN clients are already installed, you do not have to reinstall them.

Note

Before using the TN3270 Service Setup program, be sure to read the following section, “Pre-Installation Considerations,” and the TN3270 Service README file.


System Requirements
Overview	3 of 6

System Requirements

The TN3270 Service system requirements are as follows:

Windows NT operating system version 3.1.

Microsoft SNA Server version 2.11.

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

Minimum of 5 MB free hard-disk space.

Network adapter.

Supported SNA communications adapter(s). SNA communications adapter and network adapter may be the same device.

TN3270 Service supports the full complement of Windows NT-based hardware.


Pre-Installation Considerations
Overview	4 of 6

Pre-Installation Considerations

TN3270 Service utilizes the features of SNA Server to obtain host access and address issues such as security and redundancy. In turn, SNA Server utilizes the features of the Windows NT operating system to help address similar issues.

Host access is obtained by creating PU and LU definitions on the host that map to Connection and LU definitions configured for SNA Server. The LUs defined for the SNA server(s) can then be assigned to the TN3270 Service. When the system is activated, these LUs become available for TN3270 clients to access host applications.

Security issues are handled primarily by the Windows NT operating system. You will find more information regarding Security in your Microsoft SNA Server Administration Guide.

Redundancy involves SNA Local Nodes and Link Services. If you use the Windows NT Advanced Server, a domain can be created with one SNA server executing on each computer in the domain. LUs can be created on each server and then assigned to a Pool. SNA clients (such as TN3270 Service) then request a Pool rather than a specific LU. This results in client sessions distributed among the participating servers in the domain, balancing the load over multiple computers. If a computer becomes unavailable, another computer in the domain picks up the load of the unavailable computer.

Similarly, a server can be configured with redundant host links to increase fault tolerance and bandwidth. This is true whether or not the server is a member of a domain.


SNA Server and Host Configuration
Overview	5 of 6

Pre-Installation Considerations

SNA Server and Host Configuration

Link Services are installed and configured using SNA Server Setup tool. The link address specified during configuration will be used by the host to reference a PU definition in the VTAM Gen.

A Link Service can then be assigned to an SNA server using SNA Server Admin tool. This is done from the Servers and Connections window by selecting a server from the Service list and then configuring a new Connection service. At this point LUs can be assigned to the Connection. Each LU defined for the connection will correlate to an LU definition in the VTAM Gen. The LU number defined for the connection matches the LOCADDR value in the VTAM LU definition. Because TN3270 communicates with SNA Server using the LUA API, all LUs configured for use with the TN3270 Service must be set up as LUA LUs.


TN3270 Service and Host Configuration
Overview	6 of 6

Pre-Installation Considerations

TN3270 Service and Host Configuration

Each LU defined in the host VTAM Gen references a logmode entry. The logmode entry defines device attributes to be associated with an LU. When LUs are assigned to TN3270 Service using TN3270 Service Admin tool, LU definitions must be created that match the parameters in the host’s logmode entry for the LU. Whether a TN3270 client can access the host using a given LU depends on whether it can emulate the attributes defined for that LU. If none of the LUs are configured with attributes that the client can emulate, a host connection will not be possible.

For more information regarding logmode entries, see Appendix D, “IBM Terminal Type Support.”


Installing TN3270 Service
Chapter 2	1 of 8

Installing TN3270 Service

Setup is a graphical interface that allows you to install and remove TN3270 Service. To use Setup, you must have administrator privileges for your Windows NT system. For information on how to add administrator privileges, see your Windows NT documentation.

If you are installing TN3270 Service for the first time, you make selections and enter information in the dialog boxes that Setup presents to you. If you have already installed TN3270 Service, Setup presents dialog boxes for removing TN3270 Service.

The following table provides a summary of the command buttons provided by Setup. In certain dialog boxes, you may have only three of the four command buttons to choose from.

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


Setup Versus TN3270 Service Admin
Installing TN3270 Service 	2 of 8

Setup Versus TN3270 Service Admin

Setup copies files and updates Registry value entries. The Config option (TN3270 Service Admin) allows you to select available LUA LUs and LU Pools, configure them, and make them available to TN3270 Service.

The following section describes the components of a TN3270 Service system. The remainder of this chapter provides the procedures to install TN3270 Service and to remove TN3270 Service.


Components Installed by Setup
Installing TN3270 Service 	3 of 8

Components Installed by Setup

Setup installs the following software components on your computer:

Windows NT Service

The TN3270 Service application, which is registered with the Windows NT operating system as a service.

TN3270 Admin

The TN3270 Service application Administration Tool that allows you to configure available LUs and Pools.

Remove Tool

The tool that facilitates removal of the TN3270 Service application and its associated data.


Installing TN3270 Service
Installing TN3270 Service 	4 of 8

Installing TN3270 Service

To install TN3270 Service you must:

Start TN3270 Service Setup.

Specify an installation path.

Exit TN3270 Service Setup.


Starting the TN3270 Service Setup Program
Installing TN3270 Service 	5 of 8

Installing TN3270 Service

Starting the TN3270 Service Setup Program

To start Setup

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

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

3.	Change to the TN3270 directory.

4.	Start Setup:

To start Setup from File Manager, double-click the SETUP.BAT file in the TN3270 directory.

To start Setup from the command prompt, type

setup

A Welcome to TN3270 Service Setup dialog box appears.

Note

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

5.	Choose the Continue button to begin installing TN3270 Service.

The Installation Path dialog box appears.


Specifying the Installation Path
Installing TN3270 Service 	6 of 8

Installing TN3270 Service

Specifying the Installation Path

Setup provides a default installation path for the directory in which you will install TN3270 Service. This default path is C:\TN3270.

It is recommended that you first determine if this directory already exists on your computer. If so, make sure there are no files in this directory. This ensures that Setup will not inadvertently overwrite a file needed by another program when it copies the TN3270 Service files.

To accept the default path

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

The Review Settings dialog box appears.

2.	To review the installation path setting and repeat step 1, choose the Review button.

3.	When satisfied with the installation path, choose the Continue button of the Review Settings dialog box.

Setup copies the files to configure TN3270 Service and creates the registry entries.

Upon completion, the TN3270 Service Setup Finished dialog box appears.

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 using the full path.

3.	Choose the Continue button.

The Review Settings dialog box appears.

To review the installation path setting and repeat steps 1 through 3, choose the Review button. When satisfied with the installation path, choose the Continue button. Setup copies the files to the specified directory and creates the registry entries. Upon completion, the TN3270 Service Setup Finished dialog box appears.


Exiting Setup
Installing TN3270 Service	7 of 8

Installing TN3270 Service

Exiting Setup

From the TN3270 Service Setup Finished dialog box, you can either exit the Setup program or proceed directly to TN3270 Service Administration to configure LUs and Pools. For information on TN3270 Service’s use of the Registry see Appendix F, “Registry Value Entries.”

To exit Setup without going to TN3270 Service Administration

From the TN3270 Service Setup Finished dialog box, choose the Exit button.

To exit Setup and proceed to TN3270 Service Administration

From the TN3270 Service Setup Finished dialog box, choose the Admin button.

The Configure LUs for TN3270 dialog box appears.

Note

TN3270 Service is started by Setup. It is configured as an automatic service that will invoke when Windows NT is invoked.

If additional telnet servers are loaded on SNA Server a conflict will occur, generating the following error message (Error 205).

Windows sockets API call BIND for port (port number) failed with return code WSAEADDRINUSE.

See Appendix C, “Messages,” for more information about this message.


Removing TN3270 Service
Installing TN3270 Service	8 of 8

Removing TN3270 Service

You can remove TN3270 Service anytime you wish to do so. However, removing TN3270 Service deletes all of the directories and files from your TN3270 Service directory, including TN3270 Service configuration data. To use TN3270 Service again, you must run Setup to reinstall TN3270 Service files.

To remove TN3270 Service, you must:

Pause TN3270 Service.

Back up current configuration in a separate directory.

Remove the TN3270 Service software from the computer.

To remove TN3270 Service

1.	Pause TN3270 Service.

Pausing TN3270 Service allows you to notify connected users to disconnect from TN3270 Service before you stop and remove the application.

2.	Stop TN3270 Service.

If TN3270 Service is running, a warning is displayed in the SNA TN3270 Service dialog box. This warning informs you that TN3270 is running and instructs you to choose the Stop button, which stops TN3270 Service and then proceeds with removing the application.

3.	Select the Remove TN3270 tool, by double-clicking the icon.

The TN3270 Service Setup dialog box appears.

4.	Choose the Continue button.

The Confirm SNA TN3270 Service Removal dialog box appears.

5.	Choose the Continue button.

The Setup Message dialog box appears, confirming the intent to remove TN3270 Service from the computer.


Configuring TN3270 Service
Chapter 3	1 of 8

Configuring TN3270 Service

The Config option is used to select available LUA LUs and Pools, configure them, and make them available to TN3270 Service. Remember, LUs must be configured prior to establishing a connection to the TN3270 Service.

This chapter provides instructions for each element of configuration, including:

Viewing SNA Resource Information for an available LU

Adding an LU

Deleting an LU

Editing an LU configuration

Reopening a configuration

Backing up a configuration

Restoring a backup configuration

For more information about configuring LUs for LUA refer to your Microsoft SNA Server Administration Guide, Chapter 8, “Configuring LUs for LUA.”


Viewing SNA Resource Information
Configuring TN3270 Service	2 of 8

Viewing SNA Resource Information

The Zoom option is used to view SNA Resource Information. You cannot choose the Zoom button when multiple LUs or Pools are selected.

To view SNA Resource Information for an available LU or Pool

1.	From the TN3270 Administration dialog box, choose the Config button.

2.	From the Available LUs and Pools list, select a single LU or Pool.

3.	Choose the Zoom button (unavailable if multiple LUs are selected).

The SNA Resource Information dialog box appears.

To make changes to SNA Resource Information, see the “Editing a TN3270 LU Configuration” section later in this chapter.


Adding an LU
Configuring TN3270 Service	3 of 8

Adding an LU

By adding an LU you are defining SNA resource access to TN3270 Service and you are defining logmode entries that are associated with an SNA resource.

The default IP address settings assigned to an LU or Pool will allow any TN3270 client to connect to that LU or Pool.

If you would like to restrict an LU or Pool to one or more specific TN3270 client(s), then before adding LUs or Pools, you should determine the IP address of the client(s) that will use these LUs or Pools.

To determine the IP address of client computers

From the command prompt of the client computer, type:

ipconfig

The IP Address and Subnet mask values are reported.

To add a single LU or Pool to TN3270 Service

1.	From the TN3270 Administration dialog box, choose the Config button.

2.	From the Available LUs and Pools list on the left, select an LU or Pool.

3.	Choose the Add button.

The LU or Pool will move into the TN3270 LUs and Pools list box on the right. By default, the LU or Pool will be assigned an IP address of 0.0.0.0 and a subnet mask of 0.0.0.0. This will allow any TN3270 client to use this LU or Pool.

4.	To specify one or more client IP address(es) for this LU or Pool, see the next section.

To add multiple LUs or Pools to TN3270 Service

1.	From the TN3270 Administration dialog box, choose the Config button.

2.	From the Available LUs and Pools list, select multiple LUs or Pools.

A contiguous range of LUs or Pools can be selected by selecting the first item in the range you wish to add, holding down the SHIFT key, and selecting the last item in the range you wish to add.

A range of LUs that are not contiguous can be selected by single-clicking each LU or Pool in turn.

3.	Choose the Add button.

The LUs or Pools will move into the TN3270 LUs and Pools list box on the right. By default, the LUs or Pools will be assigned an IP address of 0.0.0.0 and a subnet mask of 0.0.0.0. This will allow any TN3270 client to use these LUs or Pools.

4.	To specify a client IP address(es) for these LUs or Pools, see the next section.


Editing a TN3270 LU Configuration
Configuring TN3270 Service	4 of 8

Editing a TN3270 LU Configuration

To edit a TN3270 LU configuration

1.	From the TN3270 Administration dialog box, choose the Config button.

2.	From the TN3270 LUs and Pools list, select an LU or Pool.

Note

Select a single LU or Pool to change any SNA resource information, including IP address assigned to that LU or Pool.

Selecting multiple LUs or Pools will allow you to change Terminal Model and Terminal Name Strings for those LUs or Pools, but will not allow you to make changes to the IP addresses.

3.	Choose the Edit button.

4.	In the dialog box that appears, select the Help button for specific instructions on editing an LU or Pool.

Note

Configuration changes are apparent only to users who establish a connection after the configuration changes are saved. Users who were connected at the time the configuration changes were made will not be affected.


Deleting an LU
Configuring TN3270 Service	5 of 8

Deleting an LU

To delete a single LU or Pool from TN3270 Service

1.	From the TN3270 Administration dialog box, choose the Config button.

2.	From the TN3270 LUs and Pools list, select an LU or Pool.

3.	Choose the Delete button.

The selected LU or Pool reappears in the Available Pools list.

4.	Choose the Save button to save your configuration changes.

5.	Choose the Close button.

To delete multiple LUs or Pools from TN3270 Service

1.	From the TN3270 Administration dialog box, choose the Config button.

2.	From the TN3270 LUs and Pools list, select LUs or Pools you wish to delete.

A range of LUs or Pools may selected by selecting the first item in the range you wish to delete, holding down the SHIFT key, and selecting the last item in the range you wish to delete.

The selected LUs or Pools are reinstalled in the Available Pools list.

3.	Choose the Delete button.

The selected LU or Pool reappears in the Available Pools list.

4.	Choose the Save button to save your configuration changes.

5.	Choose the Close button.

Note

Configuration changes are apparent only to users who establish a connection after the configuration changes are saved. Users who were connected at the time the configuration changes were made will not be affected.


Reopening a TN3270 Configuration
Configuring TN3270 Service	6 of 8

Reopening a TN3270 Configuration

Reopen allows you to revert to the last saved configuration. This can be useful when making configuration changes that you are unsure of. If a mistake is made, you can choose Reopen and start again without closing and restarting the configuration dialog.

To reopen a TN3270 configuration

1.	From Configuration Options area of the Configure LUs for TN3270 dialog box, choose the Reopen button.

TN3270 Service will revert to the last saved LU Definition information.

2.	Choose the Save button to save your configuration changes.


Backing Up a TN3270 Configuration
Configuring TN3270 Service	7 of 8

Backing Up a TN3270 Configuration

Backup provides the ability to write your current configuration to a specific file, as opposed to Save, which writes your current configuration to the default config file. You can use Backup to:

Back up your configuration to removable media

Store your configuration while reinstalling TN3270 Service

Maintain multiple configurations

To back up a TN3270 configuration

1.	From the TN3270 Administration dialog box, choose the Config button.

2.	From Configuration Options, choose the Backup button.

3.	Type the name of the backup.

To avoid configuration data loss, you may want to save your configuration to a directory other than the default TN3270 directory.

If you reinstall TN3270 Service, all data within the TN3270 directory will be deleted.

4.	Choose the OK button.

5.	Choose the Save button to save your configuration changes.


Restoring a TN3270 Configuration
Configuring TN3270 Service	8 of 8

Restoring a TN3270 Configuration

Restore allows you to retrieve a configuration from a backup file created by the Backup option.

To restore a TN3270 configuration

1.	From the TN3270 Administration dialog box, choose the Config button.

2.	From Configuration Options, choose the Restore button.

3.	Select the file you wish to restore.

4.	Choose the OK button.

The restored configuration will overwrite current LU Definition information.

5.	Choose the Save button to save your configuration changes.


Specifying Administrative Options
Chapter 4	1 of 1

Specifying Administrative Options

The Options feature allows you to customize your TN3270 environment by:

Specifying how events are logged within the SNA server.

Setting time limits for Idle Timeout, Init Status Delay, and Message Close Delay.

Choosing to use Name Resolution.

Specifying inbound and outbound RU size.

To specify Adminstration Options

1.	From the TN3270 Administration dialog box, choose the Options button.

2.	Select Log Normal Audit Events and/or Use SNA Event Log.

This instructs TN3270 Service to log events in the SNA Server Event Log for diagnostic purposes.

3.	Specify time limits for Idle Timeout, Init Status Delay, and Message Close Delay.

4.	Specify the use of Name Resolution.

Name Resolution should only be selected if you are running a domain name resolver. A domain name resolver catalogs the IP addresses and corresponding network names of connected computers. The domain name resolver allows you to enter the network name of a computer rather than the IP address when an IP address is required.

5.	Specify Inbound and Outbound RU size.

The minimum value for inbound or outbound RU size is 256 bytes. Adapting this value to the requirements of your TN3270 Service environment will ensure the most effective use of your computer memory.

6.	Choose the OK button.

7.	Choose the Save button to save your configuration changes.


Administering TN3270 Service
Chapter 5	1 of 6

Administering TN3270 Service

The chapter provides instructions for:

Viewing TN3270 Service Session Status

Starting TN3270 Service

Pausing TN3270 Service

Continuing TN3270 Service

Stopping TN3270 Service


Viewing TN3270 Service Session Status
Administering TN3270 Service	2 of 6

Viewing TN3270 Service Session Status

Client Address, LU Name, and State of each defined client is displayed in the Session Status area of the TN3270 Administration Display. When you are making a decision about stopping, pausing, or modifying the TN3270, it may be helpful to view Session Status information.

To view the Session Status

Double-click the TN3270 icon.

The TN3270 Administration dialog box, which contains Session Status information, appears.

From the TN3270 Administration dialog box, you can monitor network activity, including the State of each LU. An LU or Pool will display one of the following States:

State	Description
CONNECTED	The TN client has established a connection to TN3270 Service.
SSCP-LU	The TN client has established a connection to VTAM.
LU-LU	The LU is bound to a host application.
TERM	The connected session is terminating.
You can initiate any of the following actions from the TN3270 Service Administration dialog box:

Option	Description
Close	TN3270 Session Administration dialog box closes.
Refresh	Information displayed in the Session Status dialog box is updated.
Config	Define TN3270 LUs dialog box appears, allowing you to proceed with LUA LU and Pool configuration.
Options	TN3270 Options dialog box appears, allowing you to define additional administrative features such as idle time out.
Trace	Trace Parameters Modification dialog box appears, allowing you to define and initiate a trace.
Help	TN3270 Service help text is activated.
About	TN3270 Service version and release information is displayed.


Starting TN3270 Service
Administering TN3270 Service	3 of 6

Starting TN3270 Service

The TN3270 Service is invoked at system startup. However, you may need to restart the TN3270 Service after you have paused or stopped it.

To start TN3270 Service from Control Panel

1.	In Control Panel, choose the Service icon.

A blank in the status column indicated that the service has stopped.

2.	In the Services dialog box, select TN3270.

3.	Choose the Start button.

4.	In the Services dialog box, choose the Close button.


Pausing TN3270 Service
Administering TN3270 Service	4 of 6

Pausing TN3270 Service

Pausing allows you to prevent new users from establishing connections with TN3270 Service without disconnecting current users. You can then view TN3270 Service Session Status and notify connected users to disconnect from TN3270 Service.

To pause TN3270 Service from Control Panel

1.	Select the Services option in Control Panel.

2.	In the Services dialog box, select TN3270.

3.	Choose the Pause button.

4.	Choose the Close button.


Continuing TN3270 Service
Administering TN3270 Service	5 of 6

Continuing TN3270 Service

To continue TN3270 Service from Control Panel

1.	Select the Services option in Control Panel.

2.	In the Services dialog box, select TN3270.

3.	Choose the Continue button.

4.	Choose the Close button.


Stopping TN3270 Service
Administering TN3270 Service	6 of 6

Stopping TN3270 Service

Caution

Stopping TN3270 Service will disconnect all users without notice.

To stop TN3270 Service from Control Panel

1.	Use the Services option in Control Panel to pause TN3270 Service.

2.	Notify all connected users that they will be disconnected within a specified time period.

3.	After expiration of your warning period, use the Services option in Control Panel to stop TN3270 Service.

To Stop TN3270 Service from an MS-DOS command prompt, type

net stop tn3270

Once TN3270 Service has stopped, it can no longer be accessed. TN3270 Service can only be restarted on the local system.


Using TN3270 Trace Option
Chapter 6	1 of 3

Using TN3270 Trace Option

If you seek product support, the support technician may work with you to collect trace file information. Trace files contain records of internal activities on the TN3270 Service. These files describe events leading up to a difficulty and the exact state of the system when the difficulty occurred. Trace files are created when TN3270 Service tracing is enabled and then stored in the TRACES subdirectory of the TN3270 Service root directory with the filename extension TRC.

Note

When gathering information about system difficulties, it is best to start with event log information. Event log information is generally more straightforward to interpret than tracing information. Contact your support technician regarding tracing information if event logs do not provide needed detail.

For information about event logs, see “Using Event Logs” in Chapter 13 of the Microsoft SNA Server Administration Guide.


Enabling TN3270 Service Trace Option
Using TN3270 Trace Option	2 of 3

Enabling TN3270 Service Trace Option

To enable TN3270 Service trace option

1.	From the TN3270 Administration dialog box, choose the Trace button.

The Trace Options dialog box appears.

2.	Select Active option.

3.	Verify the Trace Directory.

4.	Enter the suggested Wrap Size.

5.	Choose OK.


Disabling TN3270 Service Trace Option
Using TN3270 Trace Option	3 of 3

Disabling TN3270 Service Trace Option

To disable TN3270 Service trace option

1.	From the TN3270 Administration dialog box, choose the Trace button.

The Trace Options dialog box appears.

2.	Deselect Active option.

3.	Choose OK.


Server and Connection User  Fields
Appendix A	1 of 1

Server and Connection User  Fields

The SNA server displays connection status for each configured LU in the Servers and Connections window of the SNA Server Admin utility. A User field containing the user ID of the connected client is included in the status display. For client applications that directly connect an individual user to the SNA server, the User field reflects the Logon ID of the application user of the application connected to the SNA server.

However, when client connections are made to the SNA server through another server, such as the TN3270 Service, the User field becomes less meaningful. Rather than displaying the logon ID of the end user, the User field displays the logon ID of the TN3270 Service application. The default display is Windows NT AUTHORITY/SYSTEM.

The SNA server can be instructed to display something more meaningful for the connecting client application (TN3270 Service), such as the client application name. To do this you must:

Create a new user account for the service (TN3270 Service).

Add the logon ID for the new account to the service (TN3270 Service).

Stop and restart the service (TN3270 Service).

Once the service is restarted, all new connections through the service to SNA Server will display the logon ID for the service in the User field.

To create a new user account for TN3270 Service

1.	From the Administrative Tools group, select User Manager for Domain.

The user name should be modified to reflect the service name (that is, OC/TN3270).

After you create the new user ID, it will appear in the user list.

2.	From the Policies menu, select the User Rights dialog box, then choose the Show Advanced User Rights button.

3.	From the Right pull-down list, select Logon As A Service, then choose the Add button.

The Add Users and Groups dialog box appears.

4.	Choose the Show Users button.

Individual user names appear in the Name list.

5.	Select the newly created user name from this list, then choose the Add button.

The selected user name appears in the Add Names list.

6.	Choose the OK button.

The previous dialog box appears. The new user name now appears in the Grant To list for the Logon As A Service right.

7.	Choose the OK button to activate changes.

To add a new logon ID to TN3270 Service

1.	In the control panel window choose the Services icon.

2.	Select TN3270 from the Service list, then choose the Start button.

3.	From the Log On As dialog box, select This Account and enter the new logon ID and password.

To stop and restart TN3270 Service

1.	Pause TN3270 Service.

2.	Notify all connected users that they will be disconnected within a specified time period.

3.	After expiration of your warning period, use the Services option in Control Panel to stop TN3270 Service.


Troubleshooting
Appendix B	1 of 4

Troubleshooting

This appendix provides a technical overview of the TN3270 protocol and how the TN3270 Service maps it to the LUA API. Since the TN3270 Service appears to the SNA server as an LUA application, this information should be helpful in isolating a problem with the SNA server, the TN3270 Service, or the TN client.


TN3270 Protocol Overview
Troubleshooting	2 of 4

TN3270 Protocol Overview

The TN3270 protocol uses a subset of the telnet protocol (terminal negotiation, BINARY and EOR options) to communicate 3270 data streams to TN3270 clients. A TN3270 session consists of negotiating the terminal name and options, followed by exchanging records. The records correspond to SNA RU chains.


Session Initiation
Troubleshooting	3 of 4

Session Initiation

The following is a description of the TN3270 Service session initiation process.

1.	TN3270 client user causes the TN client to issue a connect to the TN3270 Service.

2.	The TCP/IP connection is accepted by the TN3270 Service.

3.	TN3270 Service may send:

Paused message (Informational 519)

TN3270 configuration error message (Error 504, 518, 521, or 527)

Session initiation error message (Error 502, 513–515, or 521)

Note

Any of the above will cause the TCP connection to be closed after the Message Close Delay (see Chapter 4, “Specifying Administrative Options”).

Telnet command DO TERMTYPE (asking if the client supports negotiating terminal type)

4.	Client, after receiving DO TERMTYPE, may send

Nothing

Note

The TN session will hang in this state until Idle Timeout terminates the TCP connection (see Chapter 4, “Specifying Administrative Options”).

Telnet command WONT TERMTYPE (if the client is not a TN3270 client)

Note

The TN session will be terminated with error (Warning 510) and closed after the message delay (see the procedure To specify Administration Options in Chapter 4, “Specifying Administrative Options”).

Telnet command WILL TERMTYPE

5.	TN3270 Service will now send the telnet command SUBNEG BEGIN TERMTYPE SEND SUBNEG END. This tells the client to send his terminal name string.

6.	Client, after receiving above, may send

Nothing

Anything other than SUBNEG BEGIN TERMTYPE IS “name” SUBNEG END

Note

These are inappropriate responses from a client that sent WILL TERMTYPE in response to DO TERMTYPE from TN3270 Service.

SUBNEG BEGIN TERMTYPE IS “name” SUBNEG END where “name” is the terminal name string.

7.	After the TN3270 Service receives the terminal name string, the following happens:

If the terminal string is the same as the previous one, and one of the terminal name strings received was in the TN3270 Service configuration, the session is terminated (Warning 511 or 516).

Note

Either message will cause the TCP connection to be closed after the message close delay (see the procedure To specify Administration Options in Chapter 4, “Specifying Administrative Options”).

If the terminal name string is not the same as the previous one, the TN3270 Service begins looking through the TN3270 Service configuration for an SNA resource with the received terminal name string. If an SNA resource is found, the number of available sessions for that resource is checked. If no sessions are available, the server keeps looking. If no available SNA resource is found, the server returns to Step 5.

If an SNA resource was found, the TN3270 Service issues an LUA RUI_INIT verb to request an LU session from SNA Server. The TN3270 Service also requests SNA server to notify the TN server of LU session initialization progress.

8.	Several things can happen now:

RUI_INIT can initially fail (SNA Server not active, for example).

Note

This causes RUI verb (Error 505) and TCP connection is closed after the message close delay (see the procedure To specify Administration Options Chapter 4, “Specifying Administrative Options”).

RUI_INIT can fail with SNA resource not available; this causes an event to be logged (Informational 305), and the server returns to Step 5.

The SNA server notifies the TN server that it has located an LU, but the RUI_INIT has not completed yet. The TN server then sends the TN client the telnet commands DO BINARY WILL BINARY DO EOR WILL EOR to complete the TN3270 negotiation process.

The RUI_INIT completes with an OK status. The TN server then sends the TN client the telnet commands DO BINARY WILL BINARY DO EOR WILL EOR to complete the TN3270 negotiation process.

Note

If the server receives WONT BINARY, DONT BINARY, WONT EOR or DONT EOR the server will send a negotiation error message (Error 506509) to the client and close the TCP connection after the message close delay (see the procedure To specify Administration Options in Chapter 4, “Specifying Administrative Options”).

9.	After the TN3270 Service receives DO BINARY WILL BINARY DO EOR WILL EOR from the client, the TN negotiation phase is complete. If the RUI_INIT verb has not completed at this point, a status message (Message 522526) is sent to the client after the Init Status delay period (See the procedure To specify Administration Options in Chapter 4, “Specifying Administrative Options”).

10.	Once the RUI_INIT completes normally, the next thing the user should see is the VTAM banner (Message 10) screen.

At this point, the TN3270 Service issues RUI_READ and RUI_WRITE verbs as required until the session is terminated.


Ignore Error Message
Troubleshooting	4 of 4

Ignore Error Message

If the TN3270 Service receives 3270 input from the TN client when data cannot be sent to the host, it ignores it and generates (Informational 306) in the event log. The server does not accept 3270 input from the client anytime the LU session is in RCV state, except from the time the server initiates a send to the client that includes EOR indicating end of chain.

For example, the host sends data in an RU chain to the terminal that unlocks the keyboard, but in the last RU of the chain, end bracket, or change direction is not specified. The host later sends an RU chain that contains end bracket or change direction. As below:

1.	Host sends RU begin chain Erase Write unlock keyboard.

2.	TN3270 Service sends data to client (no EOR).

3.	Send completes.

4.	Host sends RU end chain.

5.	TN3270 Service sends data to client (with EOR).

6.	Send completes.

7.	TN3270 Service +RSPs the RU chain.

8.	Host sends RU end chain with end bracket or change direction.

9.	Server sends data to client (with EOR).

10.	Send completes.

11.	Server +RSPs RU chain.

The server will queue input from the client from step 5 until step 11. The queued data will be sent to the host after step 11.


Messages
Appendix C	1 of 3

Messages

There are four (4) types of events that occur during the operation of TN3270 Service that will generate a displayed message.

Success

This type of message indicates that an event that was not an Error or a Warning executed in TN3270. Success-type messages are coded Message nnn in the following list.

Informational

Informational Messages provide details regarding events that are not Errors or Warnings. These messages are coded Informational nn in the following list.

Warning

Warnings are messages that are generated when the system detects a problem that could result in an Error. Warnings are coded Warning nnn in the following list.

Error

An Error indicates a serious problem has occurred. Errors are coded Error nnn in the following list.


Event Log Messages
Messages	2 of 3

Event Log Messages

Error 000

Unknown message number (number) with insertion strings.

1 - (string)

2 - (string)

3 - (string)

4 - (string)

5 - (string)

6 - (string)

7 - (string)

8 - (string)

9 - (string)

Explanation: An unknown message number was passed to the message formatting routine.

Action: Record message and contact technical support.

Message 001

The TN3270 Service has completed initialization using TCP/IP port (port number (service name)).

(ProductName)

(ProductVersion)

Version: (FileVersion)

(Copyright)

Explanation: The TN3270 Service has completed initialization.

Action: No action is necessary.

Informational 002

The TN3270 Service has been paused by an administrator.

Explanation: An administrator has signaled the TN3270 Service to stop incoming connections.

Action: No action is necessary.

Informational 003

The TN3270 Service has been returned to normal operation.

Explanation: An administrator has signaled the TN3270 Service to begin accepting incoming connections again.

Action: No action is necessary.

Informational 004

The TN3270 Service has been terminated by an administrator.

Explanation: An administrator has signaled the TN3270 Service to terminate.

Action: No action is necessary.

Informational 005

The TN3270 Service has abnormally terminated.

Explanation: An exception (system error) has occurred that has caused the TN3270 Service to terminate.

Action: Record message and contact technical support.

Error 101

Invalid Control Code (control code number) received by Handler function.

Explanation: An internal error has occurred.

Action: Record message and contact technical support.

Error 102

TN3270 Service initialization completed by (reason string).

Explanation: TN3270 Service initialization failed.

Action: Record message and contact technical support.

Error 103

TN3270 Service fatal error: (reason string).

Explanation: TN3270 Service encountered a fatal error.

Action: Record message and contact technical support.

Error 201

WSAStartup failed. The return code was (return code mnemonic). The version requested was (version number).

Explanation: The API call used to initiate the TCP/IP interface failed.

Action: If the return code was WSASYSNOTREADY, the TCP/IP network service is not ready for communications. Correct the TCP/IP service and restart the TN3270 Service.

If the return code was WSAVERNOTSUPPORTED or WSAEINVAL, you need to get matching versions of the TCP/IP service and the TN3270 Service.

Error 202

Windows socket version (version number) not supported. Version supported is (version number).

Explanation: The API call used to initiate the TCP/IP interface failed.

Action: Get matching versions of the TCP/IP service and the TN3270 Service.

Error 203

Windows sockets API call (API call name) failed in function (function name) with return code (return code mnemonic).

Explanation: An unexpected error was encountered on an Windows Sockets API call.

Action: Record message and contact technical support.

Informational 204

TCP/IP send blocked in function (function name). The send was for (number) bytes and only (number) bytes were sent.

Explanation: A TCP/IP send did not send all the bytes requested.

Action: No action is necessary.

Error 205

Windows sockets API call BIND for port (port number) failed with return code WSAEADDRINUSE.

Explanation: Port (port number) is in use by another Windows NT process.

Action: If there is another Telnet server running on this system, create an entry for the TN3270 Service in the (system directory)DRIVERS\ETC\SERVICES file. The service name should be TN3270. You must specify unique port numbers for the Telnet and TN3270 Service entries.

Error 304

WinRUIStartup failed. The return code was (return code mnemonic). The version requested was (version number).

Explanation: The API call used to initiate the SNA RUI interface failed.

Action: If the return code was WLUASYSNOTREADY, the SNA server is not ready for communications. Correct the SNA server and restart the TN3270 Service.

If the return code was WLUAVERNOTSUPPORTED or WLUAINVALID, you need to get matching versions of the SNA Server and the TN3270 Service.

Otherwise record message and contact technical support.

Informational 305

RUI_INIT specifying LU (LU name) failed with (primary return code)/ (secondary return code) for (client IP address) (port (client port number))

Explanation: An attempt to obtain an LU for a session failed.

Action: No action is required, but this Informational may be used to modify the TN3270 Service configuration to speed up the negotiation process.

Informational 306

Input from the TN3270 client (client IP address) (port (client port number)) using LU (LU name) was ignored.

Explanation: Data arrived from the TN3270 client at a time when it could not be processed or queued for transmission to the host.

Action: No action is required. The event is logged to assist in problem determination.

Error 307

Loading of the SNA interface module (DLL name) failed because (reason string).

Explanation: The TN3270 Service was unable to properly load the DLL required to communicate with the SNA Server.

Action: Install SNA Server and try to start the TN3270 Service again.

Error 308

SNA Server entry points could not be resolved.

Explanation: The new entry points associated with SNA Server could not be resolved. Enhanced status and error information will not be available.

Action: None required. Upgrade to SNA Server Version 2.11 for the enhanced functionality.

Warning 309

(verb) failed with (primary return code)/ (secondary return code) for (client IP address) (port (client port number))

Explanation: An SNA API call failed.

Action: No action is required. This information is logged for problem determination.

Informational 401

Session limit exceeded. Client connected from (client IP address).

Explanation: A client was rejected because no sessions were available.

Action: Increase number of sessions allowed.

Informational 601

TN3270 session established with client at (client IP address) (port (client port number) ) using LU (LU name).

Explanation: A TN3270 client has successfully established a session with an SNA host.

Action: No action is necessary.

Informational 602

TN3270 session terminated normally with client at (client IP address) (port (client port number)) using LU (LU name)

Explanation: A TN3270 client has ended its session with TN3270 Service.

Action: No action is necessary.

Warning 603

TN3270 session with client at (client IP address) (port (client port number)) using LU (LU name) terminated abnormally because: (termination reason)

Explanation: A TN3270 client session was terminated abnormally.

Action: No action is necessary.

Error 701

Version mismatch.

Explanation: A version mismatch has been detected between the Perfmon DLL and the TN3270 Service.

Action: Restart the performance monitor. If this does not work, restart Windows NT server.

Error 702

Windows API (API call id) failed with error code (error code number) ((error code description)) in function (function name).

Explanation: An unexpected error was encountered on a Windows API call.

Action: Record message and contact technical support.

Error 703

Sessions table / active session count error.

Explanation: The number of active sessions and the number of active entries in the session table do not agree.

Action: Record message and contact technical support.

Error 704

SNA resources table / SNA resource count error.

Explanation: The number of SNA resources and the number of used SNA resource entries in the SNA resource table do not agree.

Action: Record message and contact technical support.

Error 801

No configuration entries were found in (configuration file name).

Explanation: The configuration in the specified configuration file does not allow any clients access.

Action: Use the TN3270 Service administrative tool to configure TN3270 Service.

Error 802

An error was detected in configuration file (configuration file name), section (section name), key (key name).

Explanation: There is a problem with the above specified key in the configuration file.

Action: This error should not be generated if the TN3270 Service administrative tool has been used. If the configuration file has been edited by hand, correct the problem. If only the TN3270 Service administrative tool has been used, contact technical support.

Error 901

Memory allocation failed (id string).

Explanation: Memory allocation failed.

Action: Record message and contact technical support.

Error 902

Logic error in module (function name) identified by: (logic error id)

Explanation: An unexpected logic error has occured.

Action: Record message and contact technical support.

Error 903

Windows API (API call id) failed with error code (error code number) ((error code description)) in function (function name).

Explanation: An unexpected error was encountered on a Windows API call.

Action: Record message and contact technical support.

Error 904

Registry API (registry API call id) failed with error code (error mnemonic).

Explanation: An unexpected error was encountered on a registry API call.

Action: The information in the registry is in error. Reinstall the product.

Error 905

Registry value (value name) has a bad value.

Explanation: An unexpected error was encountered on a registry API call.

Action: The information in the registry is in error. Correct the value.

Error 906

Version mismatch.

Explanation: A version mismatch has been detected between the existing shared memory area and the TN3270 Service.

Action: Make sure all performance monitors are stopped and restart the TN3270 Service. If this does work, restart the NT Server.


Client Messages
Messages	3 of 3

Client Messages

Error 501

TN3270 Service Error 501

Internal error in (function name)- (reason string).

Error 502

TN3270 Service Error 502

Session initialization error.

Check the Application Event Log for errors.

Warning 503

TN3270 Service Error 503

Session terminated due to inactivity.

Error 504

TN3270 Service Error 504

SNA RUI interface failed to initialize. The return code was (return code mnemonic) The RUI version is (version number).

Error 505

TN3270 Service Error 505

SNA API verb (verb name) failed. Failure described as: (failure description)

Warning 506

TN3270 Service Error 506

Telnet negotiation failure: client sent DONT BINARY.

Warning 507

TN3270 Service Error 507

Telnet negotiation failure: client sent DONT EOR.

Warning 508

TN3270 Service Error 508

Telnet negotiation failure: client sent WONT BINARY.

Warning 509

TN3270 Service Error 509

Telnet negotiation failure: client sent WONT EOR.

Warning 510

TN3270 Service Error 510

Telnet negotiation failure: client sent WONT TERMTYPE.

Warning 511

TN3270 Service Error 511

Telnet negotiation failure: client did not send TN3270 terminal type.

Warning 512

TN3270 Service Error 512

Access for IP address (client IP address) port (client port number) is not configured.

Warning 513

TN3270 Service Error 513

Licensed number of sessions exceeded.

Errror 514

TN3270 Service Error 514

Unable to allocate session memory.

Error 515

TN3270 Service Error 515

Session schedule failed.

Warning 516

TN3270 Service Error 516

No SNA resources are available.

Informational 517

TN3270 Service Message 517

TN3270 Service is paused.

Warning 518

TN3270 Service Error 518

An error in the configuration does not allow access.

Informational 519

TN3270 Service Message 519

Initiation using (LU/Pool name) currently has a status of (status string).

You may continue to wait, or terminate your session.

Error 520

TN3270 Service Error 520

Internal LU session state error in (function name).

State error id - (error id).

Current state - (state id).

Error 521

TN3270 Service Error 521

SNA interface module failed to load properly.

Informational 522

TN3270 Service Message 522

The data link is inactive for LU (LU name).

You may continue to wait, or terminate your session.

Informational 523

TN3270 Service Message 523

The data link is activating for LU (LU name).

You may continue to wait, or terminate your session.

Informational 524

TN3270 Service Message 524

The PU is inactive for LU (LU name).

You may continue to wait, or terminate your session.

Informational 525

TN3270 Service Message 525

The PU is active for LU (LU name).

You may continue to wait, or terminate your session.

Informational 526

TN3270 Service Message 526

The LU (LU name) is inactive.

You may continue to wait, or terminate your session.

Warning 527

TN3270 Service Error 527

No SNA resources are configured for TN3270 Service.

Warning 528

TN3270 Service Error 528

Licensed user limit has been exceeded by user at IP address (client IP address).

Warning 529

TN3270 Service Error 529

Licensed session limit for IP address (client IP address) has been exceeded.


IBM Terminal Type Support
Appendix D	1 of 1

IBM Terminal Type Support

IBM terminal types are used to map TN client sessions to LUs that have unique sets of characteristics.

SNA LU characteristics are described in the VTAM definition via the default Logmode parameter. The only logmode definition (MODEENT macro) parameter of interest to TN is PSERVIC. A typical PSERVIC entry follows.

PSERVIC=x'02 00 00000000 18 50 00 00 7E 00'

Byte	0	=	02	Always LU type 2

Byte	1	=	00	No query support

0	Query support terminal types that end with-E or any IBM-3279

Byte	2-5	Not used

Byte	6	=	Default screen size, rows–Always 0x18 (24)

Byte	7	=	Default screen size, cols–Always 0x50 (80)

Screen size of (24 x 80) is Model2

Byte	8	=	Alternate screen size, rows–supported values

0x18  (24)

0x20  (32)

0x2B  (43)

0x1B  (27)

Byte	9	=	Alternate screen size, cols - supported values:

0x50  (80)

0x84  (132)

Model2	=	SCREEN 24 X 80 (1850)

Model3	=	SCREEN 32 X 80 (2050)

Model4	=	SCREEN 43 X 80 (2B50)

Model5	=	SCREEN 27 X 132(1B84)

Byte	10	=	Screen size–Supported values:

x7E–static, applies to model2 IBM terminal types

0x7F–dynamic, applies to all IBM terminal types

Byte	11	Not used

Note

All TN3270 clients assume Model 2 as the default screen size.

The following table describes the IBM terminal types supported by TN3270 Service.

Terminal Name	Primary Model	Alternative Model	Query Support
IBM-3275-2	Model2	None	NO
IBM-3276-2	Model2	None	NO
IBM-3277-2	Model2	None	NO
IBM-3278-2	Model2	None	NO
IBM-3278-2-E	Model2	None	YES
IBM-3279-2	Model2	None	YES
IBM-3279-2-E	Model2	None	YES
IBM-3276-3	Model2	Model3	NO
IBM-3278-3	Model2	Model3	NO
IBM-3278-3-E	Model2	Model3	YES
IBM-3279-3	Model2	Model3	YES
IBM-3279-3-E	Model2	Model3	YES
IBM-3276-4	Model2	Model4	NO
IBM-3278-4	Model2	Model4	NO
IBM-3278-4-E	Model2	Model4	YES
IBM-3279-4	Model2	Model4	YES
IBM-3279-4-E	Model2	Model4	YES
IBM-3278-5	Model2	Model5	NO
IBM-3278-5-E	Model2	Model4	YES
IBM-3279-5	Model2	Model4	YES
IBM-3279-5-E	Model2	Model4	YES


Performance Counters
Appendix E	1 of 4

Performance Counters

This appendix lists the TN3270 Service object types, performance counters, and explain text.

The section headings show where each object type begins. Within each section, each object type’s counters are listed in alphabetical order. The object types are also listed in alphabetical order.

For the listing of each counter, the following format is used.

Counter Name

Explain text

Counter Type:	Type

Default Scale:	Scale Factor	Counter Size:	Size

The following table explains the values in the counter listings.

Field	Explanation
Counter name	Name of the counter.
Explain text	Description of the counter.
Scale factor	Number that Performance Monitor multiplies.
Type	The type of this counter. For more on counter types, see Volume 3 of the Microsoft Windows NT Resource Kit.
Size	Size of the counter.


TN3270 Service Object
Performance Counters	2 of 4

TN3270 Service Object

Object:	TN3270 Service

The TN3270 Service object type describes counters associated with the TN3270 Service as a whole.

Connections Active

Connections Active is the number of TCP connections currently active in TN3270 Service.

Counter Type:	PERF_COUNTER_RAW_COUNT

Default Scale:	1	Counter Size:	4 bytes

RU Throughput

RU Throughput is the total number of RUs sent and received by TN3270 Service.

Counter Type:	PERF_COUNTER_RAW_COUNT

Default Scale:	1	Counter Size:	4 bytes

RU Throughput/sec

RU Throughput/sec is the rate at which RUs are being sent and received by TN3270 Service.

Counter Type:	PERF_COUNTER_COUNTER

Default Scale:	1	Counter Size:	4 bytes

RUs Inbound

RUs Inbound is the total number of RUs sent to the IBM host by TN3270 Service.

Counter Type:	PERF_COUNTER_RAW_COUNT

Default Scale:	1	Counter Size:	4 bytes

RUs Inbound/sec

RUs Inbound/sec is the rate at which RUs are being sent to the IBM host by TN3270 Service.

Counter Type:	PERF_COUNTER_COUNTER

Default Scale:	1	Counter Size:	4 bytes

RUs Outbound

RUs Outbound is the total number of RUs received from the IBM host by TN3270 Service.

Counter Type:	PERF_COUNTER_RAW_COUNT

Default Scale:	1	Counter Size:	4 bytes

RUs Outbound/sec

RUs Outbound/sec is the rate at which RUs are being received from the IBM host by TN3270 Service.

Counter Type:	PERF_COUNTER_COUNTER

Default Scale:	1	Counter Size:	4 bytes

Sessions Active

Sessions Active is the number of TN3270 clients currently using an LU.

Counter Type:	PERF_COUNTER_RAW_COUNT

Default Scale:	1	Counter Size:	4 bytes

Sessions Configured

Sessions Configured is the number of sessions available to TN3270 Service.

Counter Type:	PERF_COUNTER_RAW_COUNT

Default Scale:	1	Counter Size:	4 bytes

Sessions Ended LULU

Sessions Ended LULU is the number of TN3270 client sessions that were terminated while in session with an IBM host application.

Counter Type:	PERF_COUNTER_RAW_COUNT

Default Scale:	1	Counter Size:	4 bytes

Sessions Ended Normal

Sessions Ended Normal is the number of TN3270 client sessions that were terminated normally.

Counter Type:	PERF_COUNTER_RAW_COUNT

Default Scale:	1	Counter Size:	4 bytes

Sessions Failed

Sessions Failed is the number of TCP connections that were actively terminated by TN3270 Service.

Counter Type:	PERF_COUNTER_RAW_COUNT

Default Scale:	1	Counter Size:	4 bytes

Sessions Failed Inactivity

Sessions Failed is the number of TCP connections that were actively terminated by TN3270 Service due to inactivity.

Counter Type:	PERF_COUNTER_RAW_COUNT

Default Scale:	1	Counter Size:	4 bytes

Sessions Failed No Resource

Sessions Failed No Resource is the number of TN3270 client sessions that were rejected because no SNA Resource could be obtained.

Counter Type:	PERF_COUNTER_RAW_COUNT

Default Scale:	1	Counter Size:	4 bytes

Sessions Succeeded

Sessions Succeeded is the number of TN3270 client sessions that have successfully obtained an LU since TN3270 Service was started.

Counter Type:	PERF_COUNTER_RAW_COUNT

Default Scale:	1	Counter Size:	4 bytes

TCP Bytes Received

TCP Bytes Received is the total number of TCP bytes received by TN3270 Service.

Counter Type:	PERF_COUNTER_RAW_COUNT

Default Scale:	1	Counter Size:	4 bytes

TCP Bytes Received/sec

TCP Bytes Received/sec is the rate at which TCP bytes are being received by TN3270 Service.

Counter Type:	PERF_COUNTER_COUNTER

Default Scale:	1	Counter Size:	4 bytes

TCP Bytes Sent

TCP Bytes Sent is the total number of TCP bytes sent by TN3270 Service.

Counter Type:	PERF_COUNTER_RAW_COUNT

Default Scale:	1	Counter Size:	4 bytes

TCP Bytes Sent/sec

TCP Bytes Sent/sec is the rate at wich TCP bytes are being sent by TN3270 Service.

Counter Type:	PERF_COUNTER_COUNTER

Default Scale:	1	Counter Size:	4 bytes

TCP Throughput

TCP Throughput is the total number of TCP bytes received and sent by TN3270 Service.

Counter Type:	PERF_COUNTER_RAW_COUNT

Default Scale:	1	Counter Size:	4 bytes

TCP Throughput/sec

TCP Throughput/sec is the rate at wich TCP bytes are being received and sent by TN3270 Service.

Counter Type:	PERF_COUNTER_COUNTER

Default Scale:	1	Counter Size:	4 bytes

Users Active

Users Active is the number of different TCP/IP addresses currently active in the TN3270 Service.

Counter Type:	PERF_COUNTER_RAW_COUNT

Default Scale:	1	Counter Size:	4 bytes


TN3270 Session Object
Performance Counters	3 of 4

TN3270 Session Object

Object:	TN3270 Session

A TN3270 Session object type is an active TN3270 session. Each instance is identified by the LU name being used by that session.

RU Throughput

RU Throughput is the number of RUs sent and received on behalf of this session.

Counter Type:	PERF_COUNTER_RAW_COUNT

Default Scale:	1	Counter Size:	4 bytes

RU Throughput/sec

RU Throughput/sec is the rate at wich RUs are sent and received on behalf of this session.

Counter Type:	PERF_COUNTER_COUNTER

Default Scale:	1	Counter Size:	4 bytes

RUs Inbound

RUs Inbound is the number of RUs sent to the IBM host on behalf of this session.

Counter Type:	PERF_COUNTER_RAW_COUNT

Default Scale:	1	Counter Size:	4 bytes

RUs Inbound/sec

RUs Inbound/sec is the rate at wich RUs are being sent to the IBM host on behalf of this session.

Counter Type:	PERF_COUNTER_COUNTER

Default Scale:	1	Counter Size:	4 bytes

RUs Outbound

RUs Outbound is the number of RUs received on behalf of this session.

Counter Type:	PERF_COUNTER_RAW_COUNT

Default Scale:	1	Counter Size:	4 bytes

RUs Outbound/sec

RUs Outbound/sec is the rate at wich RUs are received on behalf of this session.

Counter Type:	PERF_COUNTER_COUNTER

Default Scale:	1	Counter Size:	4 bytes

TCP Bytes Received

TCP Bytes Received is the number of TCP bytes received on behalf of this session.

Counter Type:	PERF_COUNTER_RAW_COUNT

Default Scale:	1	Counter Size:	4 bytes

TCP Bytes Received/sec

TCP Bytes Received/sec is the rate at wich TCP bytes are being received on behalf of this session.

Counter Type:	PERF_COUNTER_COUNTER

Default Scale:	1	Counter Size:	4 bytes

TCP Bytes Sent

TCP Bytes Sent is the number of TCP bytes sent on behalf of this session.

Counter Type:	PERF_COUNTER_RAW_COUNT

Default Scale:	1	Counter Size:	4 bytes

TCP Bytes Sent/sec

TCP Bytes Sent/sec is the rate at wich TCP bytes are being sent on behalf of this session.

Counter Type:	PERF_COUNTER_COUNTER

Default Scale:	1	Counter Size:	4 bytes

TCP Throughput

TCP Throughput is the number of TCP bytes received and sent on behalf of this session.

Counter Type:	PERF_COUNTER_RAW_COUNT

Default Scale:	1	Counter Size:	4 bytes

TCP Throughput/sec

TCP Throughput/sec is the rate at wich TCP bytes are being received and sent on behalf of this session.

Counter Type:	PERF_COUNTER_COUNTER

Default Scale:	1	Counter Size:	4 bytes


TN3270 SNA Resource Object
Performance Counters	4 of 4

TN3270 SNA Resource Object

Object:	TN3270 SNA Resource

A TN3270 SNA Resource object type is an SNA LU or Pool that has been configured for use with TN3270 Service. Each instance is identified by the LU/Pool name.

Sessions Active

Number of TN sessions currently associated with this SNA LU or Pool.

Counter Type:	PERF_COUNTER_RAW_COUNT

Default Scale:	1	Counter Size:	4 bytes

Sessions Configured

Number of TN sessions currently configured for the SNA LU or Pool.

Counter Type:	PERF_COUNTER_RAW_COUNT

Default Scale:	1	Counter Size:	4 bytes


Registry Value Entries
Appendix F	1 of 2

Registry Value Entries

This appendix lists value entries from the Windows NT Registry that are used by the TN3270 Service. These values are set to appropriate defaults when the TN3270 Service is installed, and in almost all cases you do not need to change them.

All of the TN3270 Service value entries appear under the following Registry path.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TN3270 \Parameters

Not all entries that appear here may be found in the Registry for a particular computer. For many entries, the TN3270 Service uses the default value unless you add the entry to the Registry and specify another value.

To add or change entry values you can use the Registry Editor. Using the Registry Editor can cause serious problems, including corruptions that may make it necessary to reinstall the TN3270 Service. Whenever possible, you should use the TN3270 Administration tool to manipulate the entry values.

For the listing of each value entry, the following format is used.

Entry Name	REG_type	Range for value entry

Explain text.

Default: value	Takes affect: when

The following table explains the values in the counter listings.

Field	Explanation
Entry name	Name of the entry value.
Explain text	Description of the entry, usually including the conditions under which you might change the value.
REG_type	The type of this entry value.
When	When changing this value will take effect.


Entry Value Descriptions
Registry Value Entries	2 of 2

Entry Value Descriptions

AuditEvents	REG_EXPAND_SZ	ON or OFF

Specifies whether or not the normal audit events (Message 601 and Message 602) are generated or not. You would change this to OFF if you do not want the audit events to be logged to the event log.

Default: OFF

Takes effect: when changed

ConfigFile	REG_EXPAND_SZ	TN Config File Name

Specifies the name of the TN3270 Service configuration file. There is no reason you should need to change this entry.

Default: C:\TN3270\TNSVRCFG.TNC

Takes effect: server startup

ConnectionTimeout	REG_DWORD	1 to 1440 minutes

Specifies the length of time a session is allowed to remain connected without any activity. You would change this if you want to free up sessions sooner than two hours, or you want to allow sessions to remain idle for longer than two hours.

Default: 120 minutes

Takes effect: server startup

DefaultInboundRUSize	REG_DWORD	256 to 32768 bytes

Specifies the amount of memory the TN3270 Service allocates for RUs bound for the host. To use bigger RU sizes, you do not need to change this parameter; the TN3270 Service will free the default memory if the BIND specifies a larger RU size.

Default: 1024 bytes

Takes effect: session startup

DefaultOutboundRUSize	REG_DWORD	256 to 32768 bytes

Specifies the amount of memory the TN3270 Service allocates for RUs coming from the host. To use bigger RU sizes you do not need to change this parameter; the TN3270 Service will free the default memory if the BIND specifies a larger RU size.

Default: 2048 bytes

Takes effect: session startup

GetClientHostName	REG_EXPAND_SZ	ON or OFF

Specifies if the TN3270 Service should use the gethostbyaddr() call to determine the host name associated with the TN client. You would change this value to OFF if your installation does not have name resolution facilities.

Default: OFF

Takes effect: when changed

InitStatusDelay	REG_DWORD	0 to 86400 seconds

Specifies the minimum time between notifications of initialization status changes. During SNA session initialization a number of status changes can take place, often in rapid succession. This value is designed to cut down on the number of status messages sent to the TN client. If you are seeing a significant number of the messages (Message 522–Message 526), you would increase this value.

Default: 2 seconds

Takes effect: server startup

LogToSNAEventLog	REG_EXPAND_SZ	ON or OFF

Specifies whether the SNA event log is to be used for event logging.

Default: OFF

Takes effect: when changed

MaxConnections	REG_DWORD	1 to infinite (-1)

Specifies the maximum number of sessions the TN3270 Service will allow.

Default: -1 (no limit)

Takes effect: server startup

MessageCloseDelay	REG_DWORD	0 to 86400 seconds

Specifies the ammount of time the TN3270 Service will delay after sending a fatal error message to the TN client before closing the TCP connection.

Default: 15 seconds

Takes effect: server startup

PerfmonMaxSessions	REG_DWORD	1 to 32767

Specifies the maximum number of sessions that can be monitored with a performance monitor. It is used only when the maximum number of sessions licensed is resource limited.

Default: 1000

Takes effect: server startup when no performance monitors are active

PerfmonMaxSNAResources	REG_DWORD	1 to 32767

Specifies the maximum number of SNA resources that can be monitored with a performance monitor. It is used only when the maximum number of sessions licensed is resource limited.

Default: PerfmonMaxSessions value

Takes effect: server startup when no performance monitors are active

SessionsPerThread	REG_DWORD	1 to 31

Specifies the number of TN client sessions handled by each TN3270 Service thread.

Default: 8

Takes effect: server startup

TCPBufferSize	REG_DWORD	2 to 32767 bytes

Specifies the size of the TCP buffers used by the TN3270 Service.

Default: 2032 bytes

Takes effect: server startup

TCPIPServiceName	REG_EXPAND_SZ	TCP/IP service name

Specifies the TCP service name that the TN3270 Service will look for prior to using the telnet entry.

Default: tn3270

Takes effect: server startup

TraceBufferSize	REG_DWORD	16 to 16384 K bytes

Specifies the size of the internal trace buffer.

Default: 64 K bytes

Takes effect: server startup

TraceDir	REG_EXPAND_SZ	Directory path

Specifies the directory path for the TN3270 Service trace files.

Default: C:\TN3270\TRACES

Takes effect: server startup or when TraceState changes from OFF to ON

TraceFiles	REG_DWORD	2 to 100

Specifies the number TN3270 Service trace files that are maintained.

Default: 10

Takes effect: server startup or when TraceState changes from OFF to ON

TraceFileSize	REG_DWORD	16 to 1048576 K bytes

Specifies the size at which a trace file change takes place.

Default: 1024 K bytes

Takes effect: server startup or when TraceState changes from OFF to ON

TraceState	REG_EXPAND_SZ	ON or OFF

Specifies whether or not the TN3270 Service is to perform tracing.

Default: OFF

Takes effect: server startup or when TraceState changes from OFF to ON