Copyright: Enhancements Guide
Citation: Enhancements Guide


Microsoft SNA Server Master Table of Contents
Microsoft SNA Server

Master Table of Contents

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


Enhancement Guide Contents
Microsoft SNA Server

Enhancements Guide

Contents

Chapter 1    New Features

Chapter 2    Enhancements to the Microsoft SNA Server Installation Guide

Chapter 3    Enhancements to the Microsoft SNA Server Administration Guide

Chapter 4    Enhancements to the Microsoft SNA Server Reference

Chapter 5    Enhancements to the 3270/5250 Applet Users Guide and Managing SNA Server

Chapter 6    Enhancements to the SDK Documentation

Chapter 7    Additional Notes

Chapter 8    SNA Remote Access Service

Chapter 9    ODBC/DRDA Drivers

Chapter 10    Introduction to AFTP

Chapter 11    The AFTP Program

Chapter 12    AFTP Server


Enhancement Guide, Chapter 1
Microsoft SNA Server

Enhancements Guide

Contents

Chapter 1    New Features

New Capabilities

Architectural Overview of New Components

New Documentation

Contents of the CD

Changes to Product Support Information

Chapter 2    Enhancements to the Microsoft SNA Server Installation Guide

Chapter 3    Enhancements to the Microsoft SNA Server Administration Guide

Chapter 4    Enhancements to the Microsoft SNA Server Reference

Chapter 5    Enhancements to the 3270/5250 Applet Users Guide and Managing SNA Server

Chapter 6    Enhancements to the SDK Documentation

Chapter 7    Additional Notes

Chapter 8    SNA Remote Access Service

Chapter 9    ODBC/DRDA Drivers

Chapter 10    Introduction to AFTP

Chapter 11    The AFTP Program

Chapter 12    AFTP Server


Enhancement Guide, Chapter 2
Microsoft SNA Server

Enhancements Guide

Contents

Chapter 1    New Features

Chapter 2    Enhancements to the Microsoft SNA Server Installation Guide

Selecting and Accepting an Appropriate Licensing Mode

Per Server Option

Per Seat Option

Examples of When To Use Each Mode

Example One: Business Critical Applications

Example Two: Remote Access Service

Example Three: Switching to Per-Seat Mode

Selecting Client/Server Protocols

Enabling SPXII Protocol Communication

Banyan VINES

Specifying the Network Domain Name

Support for 16-bit SNA Applications on Windows NT

Link Services

Channel-Attached Link Services

Twinax (TDLC) Link Services

Software Setup for Twinax Adapters on AS/400

DEMO SDLC Link Service

Installing DEMO SDLC Link Service

Further Configuration for DEMO SDLC Link Service

Operating the DEMO SDLC Link Service

Installing Online Documentation

New Features Installed by Setup

SNA Monitor

Default APPC LUs

Installing a Windows NT-Based Client

Installing a Client Running Windows Version 3.x

EHNAPPC API Support

CA/400 Support

Installing an MSDOS  Based Client

Chapter 3    Enhancements to the Microsoft SNA Server Administration Guide

Chapter 4    Enhancements to the Microsoft SNA Server Reference

Chapter 5    Enhancements to the 3270/5250 Applet Users Guide and Managing SNA Server

Chapter 6    Enhancements to the SDK Documentation

Chapter 7    Additional Notes

Chapter 8    SNA Remote Access Service

Chapter 9    ODBC/DRDA Drivers

Chapter 10    Introduction to AFTP

Chapter 11    The AFTP Program

Chapter 12    AFTP Server


Enhancement Guide, Chapter 3
Microsoft SNA Server

Enhancements Guide

Contents

Chapter 1    New Features

Chapter 2    Enhancements to the Microsoft SNA Server Installation Guide

Chapter 3    Enhancements to the Microsoft SNA Server Administration Guide

SNA Server Adapter and Connection Capacities

The Command-Line Interface

snacfg connection

Chapter 4    Enhancements to the Microsoft SNA Server Reference

Chapter 5    Enhancements to the 3270/5250 Applet Users Guide and Managing SNA Server

Chapter 6    Enhancements to the SDK Documentation

Chapter 7    Additional Notes

Chapter 8    SNA Remote Access Service

Chapter 9    ODBC/DRDA Drivers

Chapter 10    Introduction to AFTP

Chapter 11    The AFTP Program

Chapter 12    AFTP Server


Enhancement Guide, Chapter 4
Microsoft SNA Server

Enhancements Guide

Contents

Chapter 1    New Features

Chapter 2    Enhancements to the Microsoft SNA Server Installation Guide

Chapter 3    Enhancements to the Microsoft SNA Server Administration Guide

Chapter 4    Enhancements to the Microsoft SNA Server Reference

Revisions to Error Messages

New Error Messages

Registry and Environment Variables

Registry Variables Used Only on an SNA Server

SnaServer Service: Location and Names of Variables

Registry Variables Used on an SNA Server or a Windows NTBased Client

SnaBase: Location and Names of Variables

Environment Variables Used on Clients Running Windows Version 3.x, MSDOS, or OS/2

SnaBase

Chapter 5    Enhancements to the 3270/5250 Applet Users Guide and Managing SNA Server

Chapter 6    Enhancements to the SDK Documentation

Chapter 7    Additional Notes

Chapter 8    SNA Remote Access Service

Chapter 9    ODBC/DRDA Drivers

Chapter 10    Introduction to AFTP

Chapter 11    The AFTP Program

Chapter 12    AFTP Server


Enhancement Guide, Chapter 5
Microsoft SNA Server

Enhancements Guide

Contents

Chapter 1    New Features

Chapter 2    Enhancements to the Microsoft SNA Server Installation Guide

Chapter 3    Enhancements to the Microsoft SNA Server Administration Guide

Chapter 4    Enhancements to the Microsoft SNA Server Reference

Chapter 5    Enhancements to the 3270/5250 Applet Users Guide and Managing SNA Server

3270/5250 Applet Users Guide

Keyboard Mapping Tables

Managing SNA Server

Windows NT Event Viewer Utility

Chapter 6    Enhancements to the SDK Documentation

Chapter 7    Additional Notes

Chapter 8    SNA Remote Access Service

Chapter 9    ODBC/DRDA Drivers

Chapter 10    Introduction to AFTP

Chapter 11    The AFTP Program

Chapter 12    AFTP Server


Enhancement Guide, Chapter 6
Microsoft SNA Server

Enhancements Guide

Contents

Chapter 1    New Features

Chapter 2    Enhancements to the Microsoft SNA Server Installation Guide

Chapter 3    Enhancements to the Microsoft SNA Server Administration Guide

Chapter 4    Enhancements to the Microsoft SNA Server Reference

Chapter 5    Enhancements to the 3270/5250 Applet Users Guide and Managing SNA Server

Chapter 6    Enhancements to the SDK Documentation

APPC Programmers Guide

Addition to Chapter 1, Introduction to APPC

Addition to Chapter 2, Transaction Programs

Correction to Chapter 3, APPC Management Verbs

Addition to Chapter 6, APPC Extensions for the Windows Environment

Correction to Chapter 8, Common Service Verbs

Addition to Chapter 9, CSV Extensions for the Windows Environment

Correction to Appendix C, Sample APPC TPs in the SDK

CPI-C Programmers Guide

Correction to Chapter 1, Introduction to CPI-C

Correction to Appendix B, Sample CPI-C TPs in the SDK

LUA Programmers Guide

Additions to Chapter 2, Writing LUA Applications

Additions to Chapter 4, LUA SLI Verbs

Correction to Appendix A, SNA Server Enhancements to the Windows Environment

3270 Emulator Interface Specification

Change to Chapter 4, FMI Message Formats

Addition to Chapter 3, The Function Management Interface

SNA Device Interface Specification

Addition to Chapter 2, The BASE/DMOD Interface

SNALinkTerminateTerminate SNA Link

Changes to Chapter 4, Message Formats

Change to Chapter 8, Compiling and Linking with SNA Server

Changes to the Appendix

Function 0x41: Set Event/Semaphore Handle

Function 0x42: Set Link Characteristics

Function 0x43: Set V.24 Output Status

Function 0x44: Transmit Frame

Function 0x45: Abort Transmitter

Function 0x46: Abort Receiver

Function 0x47: Off-Board Load

Function 0x61: Get/Set Interface Record

Function 0x62: Get V.24 Status

Function 0x63: Receive Frame

Function 0x64: Get/Set Interface Record

Chapter 7    Additional Notes

Chapter 8    SNA Remote Access Service

Chapter 9    ODBC/DRDA Drivers

Chapter 10    Introduction to AFTP

Chapter 11    The AFTP Program

Chapter 12    AFTP Server


Enhancement Guide, Chapter 7
Microsoft SNA Server

Enhancements Guide

Contents

Chapter 1    New Features

Chapter 2    Enhancements to the Microsoft SNA Server Installation Guide

Chapter 3    Enhancements to the Microsoft SNA Server Administration Guide

Chapter 4    Enhancements to the Microsoft SNA Server Reference

Chapter 5    Enhancements to the 3270/5250 Applet Users Guide and Managing SNA Server

Chapter 6    Enhancements to the SDK Documentation

Chapter 7    Additional Notes

Licensing and License Manager

Licensing

License Manager

Saving Security Information on the Config File

Automatic Termination of the WNAP Process

Chapter 8    SNA Remote Access Service

Chapter 9    ODBC/DRDA Drivers

Chapter 10    Introduction to AFTP

Chapter 11    The AFTP Program

Chapter 12    AFTP Server


Enhancement Guide, Chapter 8
Microsoft SNA Server

Enhancements Guide

Contents

Chapter 1    New Features

Chapter 2    Enhancements to the Microsoft SNA Server Installation Guide

Chapter 3    Enhancements to the Microsoft SNA Server Administration Guide

Chapter 4    Enhancements to the Microsoft SNA Server Reference

Chapter 5    Enhancements to the 3270/5250 Applet Users Guide and Managing SNA Server

Chapter 6    Enhancements to the SDK Documentation

Chapter 7    Additional Notes

Chapter 8    SNA Remote Access Service

SNA Remote Access Service Overview

Installing SNA Remote Access Service

Starting the SNA Remote Access Service Setup Program

Specifying the Number of Ports

Adding SNA Remote Access Service Ports

Configuring an SNA Remote Access Service Server

Configuring RAS to Allow Remote Users to Connect

Configuring SNA Server to Allow RAS Clients to Connect

Setting Up a Peer Incoming Connection

Setting Up a Remote APPC LU on the Server

Setting up a Local APPC LU on the Server

Configuring an SNA Remote Access Service Client

Configuring SNA Server to Connect as a RAS Client via SNA Remote Access Service

Setting Up a Peer Outgoing Connection

Setting Up a Remote APPC LU on the Client

Setting Up a Local APPC LU on the Client

Configuring RAS to Allow the Client to Connect to Remote Servers

Connecting to a Remote Server Using SNA Remote Access Service

Removing SNA Remote Access Service Software

Chapter 9    ODBC/DRDA Drivers

Chapter 10    Introduction to AFTP

Chapter 11    The AFTP Program

Chapter 12    AFTP Server


Enhancement Guide, Chapter 9
Microsoft SNA Server

Enhancements Guide

Contents

Chapter 1    New Features

Chapter 2    Enhancements to the Microsoft SNA Server Installation Guide

Chapter 3    Enhancements to the Microsoft SNA Server Administration Guide

Chapter 4    Enhancements to the Microsoft SNA Server Reference

Chapter 5    Enhancements to the 3270/5250 Applet Users Guide and Managing SNA Server

Chapter 6    Enhancements to the SDK Documentation

Chapter 7    Additional Notes

Chapter 8    SNA Remote Access Service

Chapter 9    ODBC/DRDA Drivers

Adding and Setting Up a Data Source

Connecting to a Host Database

Supported Applications and Programming Environments

Supported ODBC Functions and Data Types

About ODBC

ODBC Functions

ODBC Data Types

System Messages

Using SQLError

SQLSTATE

SQLCODE

International Considerations

Using the ODBC/DRDA Driver in Non-English Environments

CCSID Selection for Server-Bound Data in the ODBC/DRDA Driver

Chapter 10    Introduction to AFTP

Chapter 11    The AFTP Program

Chapter 12    AFTP Server


Enhancement Guide, Chapter 10
Microsoft SNA Server

Enhancements Guide

Contents

Chapter 1    New Features

Chapter 2    Enhancements to the Microsoft SNA Server Installation Guide

Chapter 3    Enhancements to the Microsoft SNA Server Administration Guide

Chapter 4    Enhancements to the Microsoft SNA Server Reference

Chapter 5    Enhancements to the 3270/5250 Applet Users Guide and Managing SNA Server

Chapter 6    Enhancements to the SDK Documentation

Chapter 7    Additional Notes

Chapter 8    SNA Remote Access Service

Chapter 9    ODBC/DRDA Drivers

Chapter 10    Introduction to AFTP

An APPC Primer

APPC

Transaction Programs And Conversations

Logical Units And Sessions

Mode

CPI-C Side Information

Clients And Servers

APPC Security

Specifying Destinations in the AFTP Program

Specifying Security In the AFTP Program

AFTP Security

AFTP Server

AFTP Client

AFTP Security Summary

Default Security Processing

Understanding AFTP Basic Concepts

File Transfer Types

Special File Structure

Working With AFTP Directories

MVS Directories

VM Directories

Windows NT Directories

OS/2 Directories

Using File and Directory Specifications in Commands

AFTP Common Naming Format

MVS File Specifications

VM File Specifications

Windows NT File Specifications

OS/2 File Specifications

AFTP Wildcard Characters

Setting File Transfer Defaults

Additional Information

Chapter 11    The AFTP Program

Chapter 12    AFTP Server


Enhancement Guide, Chapter 11
Microsoft SNA Server

Enhancements Guide

Contents

Chapter 1    New Features

Chapter 2    Enhancements to the Microsoft SNA Server Installation Guide

Chapter 3    Enhancements to the Microsoft SNA Server Administration Guide

Chapter 4    Enhancements to the Microsoft SNA Server Reference

Chapter 5    Enhancements to the 3270/5250 Applet Users Guide and Managing SNA Server

Chapter 6    Enhancements to the SDK Documentation

Chapter 7    Additional Notes

Chapter 8    SNA Remote Access Service

Chapter 9    ODBC/DRDA Drivers

Chapter 10    Introduction to AFTP

Chapter 11    The AFTP Program

Using the AFTP Client Program

Enter and Exit AFTP

Start or End a Connection to the AFTP Server

Transfer Files

Setting Up The AFTP.INI File

Directory and File Manipulation on the AFTP Server Computer

Local Commands on the Client Computer

Get Help for AFTP Commands

Troubleshooting

Error Log

Trace Tools

Log Trace Data

AFTP Program Command Reference

AFTP

!

?

ALLOC

ASCII (ASC)

BINARY (BIN)

BLOCK

BYE

CD

CLOSE

DATE

DELETE (DEL)

DIR

DISCONNECT (DISC)

EXIT

GET

HELP

LCD

LPWD

LRECL

LS

LSD

MKDIR (MD)

MODENAME

OPEN

PROMPT

PUT

PWD

QUIT

RECEIVE (RECV)

RECFM

RENAME (REN)

RMDIR (RD)

SEND

STATUS (STAT)

SYSTEM (SYS)

TRACE

TPNAME

TYPE

Chapter 12    AFTP Server


Enhancement Guide, Chapter 12
Microsoft SNA Server

Enhancements Guide

Contents

Chapter 1    New Features

Chapter 2    Enhancements to the Microsoft SNA Server Installation Guide

Chapter 3    Enhancements to the Microsoft SNA Server Administration Guide

Chapter 4    Enhancements to the Microsoft SNA Server Reference

Chapter 5    Enhancements to the 3270/5250 Applet Users Guide and Managing SNA Server

Chapter 6    Enhancements to the SDK Documentation

Chapter 7    Additional Notes

Chapter 8    SNA Remote Access Service

Chapter 9    ODBC/DRDA Drivers

Chapter 10    Introduction to AFTP

Chapter 11    The AFTP Program

Chapter 12    AFTP Server

Installation of AFTP Server

Configuration of APPC Resources in SNA Server Admin

Configuring a Local LU

Configuring a Remote LU

Configuration of AFTP Server

Setting Up The AFTPSERV.INI File

User Permissions

Setting Up File Transfer Defaults

SAMPLE AFTPSERV.INI FILE

Environment Settings for SNA Server

Starting and Stopping AFTP Server

Diagnostics


New Features
Chapter 1	1 of 6

New Features

The Microsoft SNA Server Enhancements Guide for Version 2.11 describes new features with this release, and additions or corrections to the documentation set provided with Version 2.1 of SNA Server.

This section describes the new features available with Microsoft SNA Server version 2.11.

Important

Microsoft SNA Server version 2.11 is supported on Microsoft [image] Windows NT [image] Server version 3.5, 3.51, and higher versions.

For computers running Windows NT version 3.5 Server, Service Pack 1 and Service Pack 2, before installing SNA Server version 2.11, please see the README file included on this CD for important instructions on updating the RDR.SYS files.


New Capabilities
New Features	2 of 6

New Capabilities

This version of SNA Server includes:

PowerPC platform support.

SNA Server 2.11 adds support for the PowerPC architecture, enabling customers to run SNA Server on new systems based on the PowerPC processors from IBM [image], Motorola [image] and others. Combined with the current support for Intel [image], MIPS [image] - and Alpha-based systems, SNA Server now supports the widest variety and the most scalable set of hardware platforms of all the SNA gateways on the market today.

Support for TN3270 clients.

SNA Server 2.11 includes a TN3270 Service which runs on the same computer as SNA Server and allows any client running a TN3270 emulator, such as a UNIX [image] -based workstation, to connect to the IBM mainframe through SNA Server. This feature allows customers to use TN3270 emulators on their desktops, yet keep the hosts running the native and optimized SNA protocols, saving the cost and the performance penalty of installing and running TCP/IP on the mainframe.

The TN3270 Service supports 10,000 sessions (up to 2000 users running multiple sessions), making this the highest capacity TN3270 gateway on the market. The TN3270 Service allows TN3270 clients to connect to a host through any of the connections supported by SNA Server. It communicates with TN3270 clients via TCP/IP sessions running the TN3270 option of the Telnet protocol and does not require installation of an SNA Server client on the user’s workstation. The TN3270 Service gives administrators more control over resources by allowing specific IP addresses to be assigned to LUs. The TN3270 Service supports any third-party TN3270 emulator that uses the DO TERMTYPE option of Telnet, for any client operating system.

ODBC/DRDA drivers.

SNA Server 2.11 includes Open Database Connectivity/Distributed Relational Database Architecture (ODBC/DRDA) drivers for Windows [image] operating system- and Windows NT-based clients, enabling standard desktop applications that support database connectivity via ODBC, such as Microsoft [image] Excel and Microsoft [image] Access, to access IBM host databases without an expensive host-based database gateway. These drivers support connectivity to the following IBM host databases: DB2 [image] for MVS, SQL/DS [image] for VM, and DB2/400 for OS/400 [image]. A single-user ODBC/DRDA license is included with SNA Server 2.11. See the enclosed license card for instructions on obtaining additional licensing.

SNA Remote Access Service.

The prior versions of SNA Server already support the full SNA client functionality for remote clients dialing into the LAN using the Remote Access Service (RAS) of Windows NT Server. SNA Server version 2.11 adds a feature that allows administrators to create virtual LAN connections between Windows NT systems across an existing SNA network. This is achieved by integrating SNA Server’s LU6.2 transport with the RAS architecture, allowing the use of familiar RAS tools to initiate remote network connections across the SNA network and to benefit from the data compression, administration, and security features built into RAS. Customers with large SNA wide-area backbones now can access remote LANs and servers without setting up redundant LAN-to-LAN networks or having to install a dial-up modem in each remote branch office. This feature is particularly useful for network administrators who need to manage remote branch offices connected to the corporation’s mainframe or AS/400 [image] only through low-speed synchronous data-link control (SDLC) lines.

Support for IBM’s new Client Access/400 product.

SNA Server 2.11 adds support for IBM’s new CA/400 product, which is a Windows-based front-end package to access AS/400 applications and data. The Windows-based client component of SNA Server 2.11 is enhanced to be compatible with the CA/400 router, allowing users to replace the CA/400 router and connect to the AS/400 via an SNA Server. Users benefit from using an IBM-endorsed client package to access the new OS/400 V3R1 operating system for the AS/400, while getting the benefits of the leading SNA gateway to offload communications processing from the AS/400, saving CPU and memory resources on the host. When using Windows [image] for Workgroups or the upcoming Windows [image] 95 operating system, SNA Server allows the Windows-based desktops to run protected-mode LAN protocols only, saving precious MS-DOS [image] operating system-based memory and making the overall Windows environment more stable. Network administrators will benefit from the reduced administration requirements for both the AS/400 and the Windows-based desktops.

EHNAPPC API support.

SNA Server 2.11 adds support for the EHNAPPC application programming interface (API) which is the Windows-based APPC API supported by IBM’s PC Support and Client Access/400 (CA/400) products. IBM has presented EHNAPPC API to its independent software vendor (ISV) community as the way to write Windows-based applications that integrate with the AS/400. There are estimated to be more than 60 applications that utilize this API as a way to connect to the AS/400 data and applications. These ISV applications will work unchanged with SNA Server 2.11.

Support for 16-bit SNA applications on Windows NT.

A set of new Dynamic-Link Libraries (DLLs) included with SNA Server version 2.11 maps the 16-bit SNA API to native 32-bit SNA APIs, allowing users to run all the 16-bit Windows-based applications that work with SNA Server in the 32-bit Windows NT environment. This feature brings the Windows NT-based clients to parity with Windows-based clients for running SNA applications.

Drivers for IBM and Andrew twinaxial adapters.

New drivers included with SNA Server 2.11 allow SNA Servers to be connected to AS/400s using twinaxial cabling, the native way to connect to an AS/400. These drivers, developed for Microsoft by Andrew Corp., provide a cost-effective option to connect the PC LANs to the AS/400s for the estimated 70 percent of the 300,000 AS/400s installed worldwide that do not yet have LAN adapters. Instead of spending as much as $3,200 for a token ring adapter for the AS/400, a $350 twinaxial adapter can be installed on the SNA Server computer, providing up to 512 host sessions for the LAN clients attached to the SNA Server.

The Andrew Twinax link service supports the Andrew 3xTwin Adapter, and is available in this beta release for the Intel [image] platform.

The IBM Twinax link service supports the IBM 5250 Enhanced Adapter, or compatible, and is available in this beta release for the Intel platform. (There are register-compatible cards from independent hardware vendors, such as DCI.)

For a full list of and contact information for third-party vendors providing adapters, see the SNA Server Companion Product Catalog, ISVCATAL.DOC, in the \COLLATRL\GENERAL directory on the SNA Server CD. Updates to this catalog are distributed on the Microsoft TechNet CD and posted on the MSSNA CompuServe [image] forum.

Drivers for Barr Systems and Bus-Tech channel adapters.

SNA Server 2.11 includes drivers for Barr Systems and Bus-Tech channel adapters, which allow the SNA Server to be directly connected to an IBM mainframe channel. The direct channel attachment can provide a significant improvement in performance compared to other ways of attaching SNA Servers to the host. An SNA Server running on a multiprocessor Pentium or RISC system with two LAN and two channel adapters installed can challenge the overall performance and capacity of some of the fastest IBM controllers and front-end processors.

The Barr channel link service supports the Barr S/370 Channel adapter, available for the Intel, MIPS [image], and Alpha AXP [image] platforms.

The Bus-Tech channel link service supports the BTI Channel adapter, available for the Intel platform.

Additional SDLC driver support.

Link services have been added for Attachmate SDLC and Attachmate Advanced SDLC cards for the Intel platform, and for a Barr SDLC card for the MIPS and Alpha AXP [image] platforms.

AFTP Client and Server utilities.

SNA Server version 2.11 includes a set of utilities that enable high-speed file transfer between Windows NT-based systems and IBM hosts. APPC File Transfer Protocol (AFTP) is an IBM-developed protocol that duplicates for the SNA environment the function of the popular FTP utility in the TCP/IP environment. IBM now is offering the host component of AFTP at a nominal cost for most of the host operating systems. AFTP allows customers to perform multi-megabyte file transfers between the host and the Windows NT-based system quickly using native SNA protocols, eliminating the need to install the expensive and CPU-intensive TCP/IP stack for the host in order to perform FTP file transfers. The AFTP feature is based on IBM source code that Microsoft recently licensed as part of the APPC Application Suite from IBM.

The AFTP Client and Server programs will be installed automatically during setup of an SNA Server version 2.11 client or server on a computer running Windows NT version 3.5x.

SNA Server AFTP Client will work on a Windows NT client or server as a command-line utility, which can be used to create batch jobs. SNA Server AFTP Server is a Windows NT service that will allow AFTP clients to initiate file transfer (for example, from a host computer). AFTP provides generic filename mapping support for consistency between different operating systems’ file systems.

Demo host facility.

This new software feature, included with SNA Server 2.11, allows resellers, trainers, consultants, and customers to evaluate and demonstrate nearly all SNA Server features and capabilities without a live host connection or any special hardware. Previously, resellers had to purchase expensive access time from host service providers in order to train their own personnel on the features of a given SNA gateway product, or had to purchase a separate hardware-based host simulator at a significant cost. The demo host facility included with SNA Server can act both as a mainframe host and an AS/400 host and exercises the core functionality of SNA Server, including 3270 and 5250 sessions with multiple host connections, in an identical fashion to the live host environment.

For detailed information, see the “DEMO SDLC Link Service” section later in this guide.

SNA Monitor

This new monitor, which is similar to the monitor in Remote Access Service, can be used to monitor the status of an SDLC connection. The SNA Server 2.11 Setup program will create an icon for this utility in the Microsoft SNA Server program group. From the SNA Monitor Setting menu, you can specify options such as sound, update interval, and which link service to monitor.

Default APPC LUs

SNA Server 2.11 will create default Local and Remote APPC LUs.

During Setup of an SNA Server 2.11, a Local APPC LU will be created on the server node with suggested default values.

When you configure a new link service, if the connection is configured as a peer connection, and if a remote APPC LU is not detected, the New APPC Remote LU Properties dialog box will appear with suggested default values when the OK button is chosen.

Remember to change the default values if they do not match your needs.

Planning Guide

A new document, called the SNA Server Planning Guide, is provided at no charge with SNA Server version 2.11. This document contains information to help resellers and users implement SNA Server in existing networks such as NetWare [image], Banyan [image] and TCP/IP environments. Among the topics covered are server sizing recommendations for CPU types, and memory for various usage patterns, preinstallation guidelines, enterprise rollout information, and maintenance and troubleshooting tips collected from current users of SNA Server.

Concurrent licensing option

Customers will continue to be able to license SNA Server on a per-client and per-server basis, which allows any client to access any SNA Server on the network. This is the most affordable licensing option when deploying multiple SNA Servers for extra capacity, load balancing and hot backup, because each extra server only costs approximately $409. SNA Server 2.11 adds the option to license SNA Server for concurrent use, which the user can choose at the time of installation. With this option, customers are required to purchase only as many client licenses as there are simultaneous users accessing a given SNA Server. This option is suitable for single-server installations or when only infrequent access to the host resources is required.

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


Architectural Overview of New Components
New Features	3 of 6

Architectural Overview of New Components

The following illustration shows how the components of SNA Server 2.11 fit into SNA Server’s overall architecture.

The new features shown are:

TN3270 Service communicates at the SNA Server layer with TN3270 clients over TCP/IP protocol, and the TN3270 Service communicates with the SNA Server via the LUA/RUI API at the server (not shown due to space limitations).

AFTP is a transaction program that flows through CPI-C into APPC and across a client/server protocol to an AFTP program running on a host computer.

EHNAPPC API provides support for IBM’s CA/400 product and other EHNAPPC applications, which flow though this layer into the APPC API.

ODBC/DRDA drivers provide database connectivity via ODBC for standard desktop applications that use ODBC (for example, Microsoft Access and Microsoft Excel) through the APPC API.

Demo Host facility, a link service compatible with the SNA Device Interface Specification (SNADIS) layer, emulates both mainframe host and AS/400 host connectivity.

Channel and Twinax drivers offer new options for direct connections of host computers to SNA Server, though the SNADIS layer.


New Documentation
New Features	4 of 6

New Documentation

In addition to this book, documentation for SNA Server 2.11 includes the following new components, delivered in printed form and as Books Online:

Microsoft SNA Server Planning Guide

This guide will provide server sizing information and preinstallation guidelines.

Microsoft SNA Server TN3270 Service

This is a guide to the installation and operation of the TN3270 Service.

Microsoft SNA Server Comprehensive Index

This comprehensive index covers all books provided with SNA Server 2.11.

Microsoft SNA Server Installation Guide

This book contains an updated chapter on Microsoft Support Services. Changes that affect other information in this document are covered in the next chapter of this book.


Contents of the CD
New Features	5 of 6

Contents of the CD

The CD in the SNA Server version 2.11 package includes all of the components listed in the Microsoft SNA Server Installation Guide version 2.1, and includes the additional SNA Server version 2.11 components listed below.

PPC directory. This contains the directories and files for installing SNA Server on a PowerPC platform.

TN3270 directory. This contains the directories and files for installing TN3270 service.

RASSNA directory. This contains the directories and files for installing SNA Remote Access Service.

DOCS\211 directory. Subdirectories of this directory contain electronic versions of the printed documents for this release:

Microsoft SNA Server Enhancements Guide

Microsoft SNA Server Planning Guide

Microsoft SNA Server TN3270 Service

Microsoft SNA Server Comprehensive Index

DOCS\HELP directory. This contains the SNA Server documentation set online. These Windows Help files (with the same text as the printed documents) can be used to view the printed documentation online. This is a convenient alternative to the print-based versions of the documentation. SNA.HLP is the master Help file from which you can view and search for information in any of the 11 books provided. In addition to search capabilities, you can print topics.

SNA Server Setup optionally installs the online documentation. If you did not choose to install the online documentation, you can copy the Help files yourself. The files to copy depend on the operating system running on the computer you will use to view them. If the computer is running Windows NT version 3.5 or earlier, Windows 3.x, or Windows for Workgroups 3.x, copy all files with the following extensions:

 .HLP

 .IND

 .DLL

If you will view these files using a computer running Windows NT version 3.51 or later or Windows 95, copy all files with these extensions:

 .HLP

 .CNT

 .FTS

You can safely copy all files if you want to support all versions of Windows and Windows NT.

Important

To create a Windows icon for the online books, specify the path for the SNA.HLP file in the Command Line text box of the Program Item Properties dialog box for the icon. For example, to create an icon in Windows NT to activate the online books help files located in the C:\SNABOOKS directory, in the command line text box, type:

C:\snabooks\sna.hlp

If the correct path has not been entered when the icon is activated, an error message may appear indicating that the help file cannot be found (unless the online book files are in the same directory as the WINHELP.EXE or WINHLP32.EXE file).

Please see the README.TXT file in the DOCS\HELP directory for additional information.

COLLATRL\GENERAL directory. The SNA Server Companion Product Catalog, ISVCATAL.DOC, has been updated in this directory.


Changes to Product Support Information
New Features	6 of 6

Changes to Product Support Information

Product support information has been updated. Please see the Microsoft SNA Server Installation Guide shipping with this release for the latest information.


Enhancements to the Microsoft SNA Server Installation Guide
Chapter 2	1 of 23

Enhancements to the Microsoft SNA Server Installation Guide

The following additions and corrections apply to the Microsoft SNA Server Installation Guide.

This chapter describes the changes that have occurred in the Setup process for SNA Server version 2.11. They include the following:

Server Setup Changes

Selecting and accepting an appropriate licensing mode.

Selecting client/server protocols.

Selecting and configuring new link services.

Client Setup Changes

Installing clients on a TCP/IP network.

Enabling EHNAPPC API support.


Selecting and Accepting an Appropriate Licensing Mode
	Enhancements to the Microsoft SNA Server Installation Guide	2 of 23
Selecting and Accepting an Appropriate Licensing Mode

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

For more detailed information about and an exact description of either the Per Server or Per Seat licensing modes, see the Microsoft license agreement in your product package or in the online Help for Licensing or License Manager.

Note

License Manager is available only with Windows NT Server version 3.51 or later.

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


Per Server Option
	Enhancements to the Microsoft SNA Server Installation Guide	3 of 23
Selecting and Accepting an Appropriate Licensing Mode

Per Server Option

With Per Server licensing, each SNA Server Client Access License is assigned to a particular server and allows one connection to that server. Notice that a connection, in this case, is to a server and not just to an individual share point or printers on that server. If you connect to \\SNASERV\SHARE_1 and \\SNASERV\SHARE_2, that is considered as only one connection for licensing purposes.

You must have at least as many Client Access Licenses dedicated to that server as the maximum number of client computers that will connect to that server at any point in time. If you select the Per Server option, you must specify during Setup the number of Client Access Licenses (which corresponds to the number of concurrent connections) that you have purchased for that server.

Note

When a computer running SNA Server 2.11 licensed in the Per Server mode reaches the maximum number of concurrent connections, this server will not allow any more computers to connect. The next SNA Server client attempting to connect will receive a pop-up error message, and the server will log an error message to the event log. Administrators also receive a warning message when this situation happens and are allowed to connect and fix the lockout situation.

This mode of licensing is available for Microsoft SNA Server 2.11 or higher, Microsoft SQL Server 4.21a or higher, and Microsoft Windows NT Server 3.51 or higher. It is not available for Microsoft Systems Management Server or the Microsoft BackOffice Client Access License. The Per Server option is often more economical for networks in which clients tend to connect to only one occasional-use or special-purpose server.

Also, if you are unsure which licensing mode to choose, select the Per Server option. You are legally permitted to convert from Per Server mode to Per Seat mode at no additional cost. (Use the Licensing option in Control Panel for a server on which you are working and License Manager in the Network Administration program group for local or remote servers. License Manager is available only with Windows NT Server 3.51 or later. For more information on how to use these new licensing tools, see Chapter 5 of the Microsoft [image] Windows NT Server Update Information for Version 3.51. This is a one-time, one-way conversion option. It is not necessary for you to notify Microsoft if you elect to make this  change. You are not legally permitted to change the licensing mode from Per Seat to Per Server.


Per Seat Option
	Enhancements to the Microsoft SNA Server Installation Guide	4 of 23
Selecting and Accepting an Appropriate Licensing Mode

Per Seat Option

The Per Seat licensing mode requires an SNA Server Client Access License for each computer that will access SNA Server. Once a computer is licensed, it may be used to access any SNA Server computer at no additional charge.

If you select the Per Seat licensing mode, any number of licensed computers can be used to connect at the same time to any SNA Server. However, remember that you must purchase a separate SNA Server Client Access License for each computer even if you use client operating-system software from Microsoft (including Microsoft Windows for Workgroups or Microsoft Windows NT Workstation), from a third-party vendor, or any of the other client software supported by SNA Server. The Per Seat option is often the more economical one for networks in which clients tend to connect to more than one server.

Note

A Client Access License is not included when you acquire Windows for Workgroups, Windows NT Workstation, and (when released) Windows 95. The license must be purchased separately in addition to the operating-system software.


Examples of When To Use Each Mode
	Enhancements to the Microsoft SNA Server Installation Guide	5 of 23
Selecting and Accepting an Appropriate Licensing Mode

Examples of When To Use Each Mode

The following examples are designed to help clarify the situations under which you would use each licensing mode.

Example One: Business Critical Applications

This first example describes a company that uses SNA Server for business-critical applications. The company has three servers and 100 employees. In this example, all the employees log on to a “home” server and, normally, access one additional server during the day.

If the Per Seat licensing mode is selected, the company would purchase 100 Client Access Licenses, and the employees could access all the servers. If the Per Server licensing mode is selected, the company would have to determine the maximum number of concurrent connections to any one server to guarantee access for all users. Depending on the demand, this may require them to purchase more than 100 Client Access Licenses.

For example, if 33 employees use one of the servers as their home server but, on average, 20 employees normally connect to an additional server, then the maximum number of concurrent connections for each server might be 53. That would require the purchase of 159 Client Access Licenses or 53 for each of the three computers. In general, the Per Seat option is the more economical one to choose when the use of a server is pervasive or guaranteed access is needed to business-critical applications.

Example Two: Remote Access Service

In another situation, a company is planning to use SNA Server for remote access services. The company has 200 employees but anticipates that only 50 employees will dial in at any one time.

In this case, the company should license SNA Server in the Per Server mode and purchase 50 SNA Server Client Access Licenses for that server. The Per Server option is the more economical one to choose for occasional-use servers, such as when a great number of clients will only access a server on an occasional basis.

Example Three: Switching to Per-Seat Mode

In contrast with example two, when the number of Client Access Licenses in the Per Server mode approaches or is greater than the total number of clients in an organization, then switching to the Per Seat mode becomes more cost effective.

For example, consider a company that has a total of 200 workstations and four SNA Server computers, each with 50 Client Access Licenses, for a total of 200 Client Access Licenses in the Per Server mode. The company would want to switch the servers to the Per Seat mode to reduce administrative overhead costs and guarantee access to business-critical applications on all the servers.

For more information about these licensing options, see the online help obtained by selecting the Help button of the Choose Licensing Mode dialog box, or Chapter 7 of this book, or the “Before You Begin” chapter of the Microsoft SNA Server Planning Guide.

After accepting the Client Licensing agreement in the Per Seat Licensing dialog box or the Per Server Licensing dialog box, the Software Licensing dialog box appears, as shown under “Recording Identifying Information” in the Microsoft SNA Server Installation Guide, prompting you for name, company, and product ID number.


Selecting Client/Server Protocols
	Enhancements to the Microsoft SNA Server Installation Guide	6 of 23
Selecting Client/Server Protocols

During installation of SNA server or client software, if you have selected the Novell NetWare (IPX/SPX) protocol and want to enable communication over the SPXII protocol, you will need to add a registry entry as described in the following section.


Enabling SPXII Protocol Communication
	Enhancements to the Microsoft SNA Server Installation Guide	7 of 23
Selecting Client/Server Protocols

Enabling SPXII Protocol Communication

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

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

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

HKEY_LOCAL_MACHINE

SYSTEM

CurrentControlSet

Services

SnaBase

Parameters

SnaSpx

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

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

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

Note

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


Banyan VINES
	Enhancements to the Microsoft SNA Server Installation Guide	8 of 23
Selecting Client/Server Protocols

Banyan VINES

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

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


Specifying the Network Domain Name
	Enhancements to the Microsoft SNA Server Installation Guide	9 of 23
Specifying the Network Domain Name

This section replaces the same section in the Microsoft SNA Server Installation Guide, Chapter 2, and applies if you are selecting TCP/IP as the protocol and will be specifying a network domain name.

If you did not select Microsoft Networking (Named Pipes) as one of your client/server protocols, you must specify the name of the network domain. If your operating system is Banyan VINES (and not Microsoft Networking), you must also specify the Banyan StreetTalk [image] group name.

To specify the domain name

1.	Complete the procedures in the previous sections.

If you did not select Microsoft Networking (Named Pipes) in the Select Client/Server Protocols dialog box, a dialog box similar to the one shown below appears.

Network Domain Name Dialog Box

2.	In the appropriate box, type the network domain name.

3.	Choose the Continue button.

If you are using Banyan VINES (and not Microsoft Networking), the StreetTalk Group Name dialog box appears.

Otherwise, the Change SNA Server Role dialog box, shown in Figure 2.4 of the Microsoft SNA Server Installation Guide appears; continue with “Selecting the Server Role,” later in that chapter.


Support for 16-bit SNA Applications on Windows NT
	Enhancements to the Microsoft SNA Server Installation Guide	10 of 23
Support for 16-bit SNA Applications on Windows NT

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

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

Important

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

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


Link Services
	Enhancements to the Microsoft SNA Server Installation Guide	11 of 23
Link Services

The Link Service Installation dialog box now contains several new link services.


Channel-Attached Link Services
	Enhancements to the Microsoft SNA Server Installation Guide	12 of 23
Link Services

Channel-Attached Link Services

See Help for information on configuring these link services.


Twinax (TDLC) Link Services
	Enhancements to the Microsoft SNA Server Installation Guide	13 of 23
Link Services

Twinax (TDLC) Link Services

See Help for information on configuring these link services.

Software Setup for Twinax Adapters on AS/400

Setup is the same on AS/400 for both IBM and Andrew adapters, and is identical to the configuration for PC Support over twinax adapters.

Note that AS/400s can autoconfigure these settings, if permitted in AS/400 system settings. This is the least troublesome way to configure the connection.

On the AS/400, you must configure an APPC “logical” controller and device in addition to the twinax-attached “physical” controller. The APPC resources are necessary to support APPC sessions over twinax (which is the only way SNA Server can communicate with the AS/400). The same APPC resources are used to support a connection to the AS/400 via 802.2 or SDLC from the same SNA server.


DEMO SDLC Link Service
	Enhancements to the Microsoft SNA Server Installation Guide	14 of 23
Link Services

DEMO SDLC Link Service

This section is intended for those who will be using the DEMO SDLC Link Service to demonstrate some of the features of SNA Server. It includes a brief description of the DEMO SDLC Link Service as well as detailed instructions covering installation, configuration, and operation in conjunction with supplied scripts.

DEMO SDLC Link Service is an SNA Server link service. Usually, an SDLC link service communicates between the SNA 2.1 node (SNASERVR.EXE) and an SDLC adapter. The DEMO SDLC Link Service receives messages from SNA Server and responds to them itself, reading the responses from a script file. DEMO SDLC Link Service is capable of emulating a 3270 host or an AS/400, depending on the script file you choose and the SNA Server configuration.

Script files are provided for emulations of sessions with a 3270 host or an AS/400 computer.

Installing DEMO SDLC Link Service

DEMO SDLC Link Service is installed in the same way as an SDLC link service, but rather than selecting and configuring an SDLC card type, you specify a script file that contains the messages the DEMO SDLC Link Service needs to send to SNA Server. A link service can be installed when installing SNA Server, or after SNA Server setup is complete.

To install the DEMO SDLC Link Service when installing SNA Server

1.	If this is a new installation or reinstallation of SNA Server, complete the procedures in Chapter 2 of the SNA Server Installation Guide up to the section called “Installing a Link Service.”

The Link Service Installation dialog box appears.

2.	In the Available Link Services box of the Link Service Installation dialog box, select the DEMO SDLC Link Service.

3.	Choose the Install button.

The following DEMO SDLC Link Service Setup dialog box appears.

4.	Select the script file that you would like to install for this SDLC connection:

3270 Continuous Demo

Choose this option for an emulation of 3270 flash. (Flash is a test transaction program which runs on the host, continuously sending screenfuls of data at the emulator. The 3270 continuous demo script emulates this behavior.)

3270 Logon Demo

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

AS/400 Demo

Choose this option for a demonstration of a 5250 emulation session on an AS/400 computer. This demo script provides demonstrations of both a 5250 loop script and a SQL Query to a database on an AS/400.

Important

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

5.	Choose the Continue button.

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

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

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

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

Note

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

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

To add or configure this link service after SNA Server has been installed

1.	Follow the procedures on pages 59 – 61 of the SNA Server Installation Guide under the section “Modifying or Removing SNA Servers.”

2.	Configure the link service as described in the preceding procedure.

Further Configuration for DEMO SDLC Link Service

This section will deal specifically with configuration and use of the demonstration scripts provided with the DEMO SDLC Link Service. This configuration is done in the SNA Server Admin graphical interface.

3270 Continuous Demo

To configure the DEMO SDLC Link Service for the 3270 Continuous Demo

1.	In the Servers and Connections window, select the connection associated with this script in the previous section.

2.	From the Services menu, choose Properties.

The following Connection Properties dialog box appears.

Important

Confirm that the link service associated with the 3270 Continuous Demo script is listed in the Link Service box. For example, SnaDEMO1 will be the name of the first demo link service installed, and will be associated with the script chosen for that link service.

3.	Select the Host System and On Demand options.

4.	Choose the Setup button.

The SDLC Setup dialog box appears.

5.	Choose the OK button to close the SDLC Setup dialog box.

Important

Although the default values are not modified, steps 4 and 5 must be performed to properly configure the connection.

6.	Choose the OK button to close the Connection Properties dialog box.

7.	From the Services menu of SNA Server Admin, choose Assign LUs.

The Insert LU dialog box appears.

8.	Select 3270 as the New Logical Unit.

9.	Choose the OK button.

The New 3270 LU Properties dialog box appears, as shown below.

10.	Configure the options as follows:

LU Number must be 2.

Choose any LU Name (for example, DEMOLK1).

Select LU Type Display.

Select Display Model 2.

11.	Choose the OK button to close the dialog box.

12.	In the Users menu of the Users and Groups window, select New User.

The Add Users and Groups dialog box appears.

13.	Select a suitable user or group (for example, Everyone) from the available list.

A user or group is suitable if your logon gives you access to the LUs for that user or group.

14.	Choose the Add button.

15.	Choose the OK button to close the Add Users and Groups dialog box.

16.	With this user or group highlighted, select Assign LUs from the Users menu.

The Assign User LU/Pool Sessions dialog box appears.

17.	Select the LU assigned to this connection.

18.	Choose the OK button to close the dialog box and add the LU connection to this user.

3270 Logon Demo

To configure the DEMO SDLC Link Service for the 3270 Logon Demo

Follow the procedure “To configure the DEMO SDLC Link Service for the 3270 Continuous Demo,” except for step 10, where you need to choose a different LU Name (for example, DEMOLK2).

AS/400 Demo

To configure the DEMO SDLC Link Service for the AS/400 Demo

1.	In the Servers and Connections window, select the connection for the link service that you installed for the AS/400 Demo.

2.	From the Services menu, choose Properties.

The Connection Properties dialog box appears.

3.	Select the Peer System and On Demand options.

4.	Choose the Setup button.

The SDLC Setup dialog box appears.

Type APPN in the Network Name text box and REMOTE in the Control Point Name text box, as shown.

5.	Choose the OK button to close the SDLC Setup dialog box.

6.	Choose the OK button to close the Connection Properties dialog box.

Note

New functionality has been added to SNA Server Admin to automatically assign a new APPC (Remote) LU when the Connection Properties dialog box is closed, if the connection has been configured for Peer System.

The New APPC Remote LU Properties dialog box appears.

7.	Accept the default LU Alias or enter a different LU Alias into the text box shown below and press the tab key.

The LU Name and Uninterpreted LU Name text boxes are automatically filled in.

Leave other settings at the default values.

8.	Check the partnerships of Local LUs with this Remote LU.

Caution

This APPC Remote LU must only be partnered with one APPC Local LU. You can use the default APPC (Local) LU that was assigned to the SNA server by the Setup program or create a new Local LU for this connection.

To create a new Local LU, follow the remainder of this procedure.

To check partnerships, select the Partners button in the APPC Remote LU Properties dialog box. The LU 6.2 Partner LUs dialog box appears. Highlight and delete all partners except for the Local LU which has been configured for the AS/400 Demo script. Do not remove the Remote LU.

9.	Choose the OK button to close the dialog box.

Caution

The remainder of this procedure is to be followed only once. Do not repeat these steps if you have already set the network and control point names and configured a Local LU to run the AS/400 Demo script.

If you have not configured a Local LU for the AS/400 Demo, then proceed with the remaining steps of this procedure.

10.	Select the server, and from the Services menu choose Properties.

The Server Properties dialog box will appear.

11.	Configure the Server Properties network and control point names.

It does not matter what you set them to, but they should be configured.

12.	Choose the OK button to close the dialog box.

13.	From the Services menu, choose Assign LUs.

The Insert LU dialog box appears.

14.	Select APPC (Local) as the New Logical Unit.

15.	Choose OK.

The New APPC Local LU Properties dialog box appears.

16.	Select Independent for the LU 6.2 Type, and select both Enable Automatic Partnering and Member of Default Outgoing Local APPC LU Pool options.

17.	Type LOCAL (or any name of your choice) in the LU Alias text box.

18.	Press the TAB key.

The LU Name and Uninterpreted LU Name text boxes are automatically filled in.

19.	Choose the OK button to close the dialog box.

20.	In the Users and Groups window, select a suitable user or group.

21.	From the Users menu, choose Properties.

The Group Properties dialog box appears.

22.	Configure the Local and Remote LU Aliases as LOCAL and REMOTE (or whatever names you assigned to these LUs), respectively.

23.	Choose the OK button to close the dialog box.

Operating the DEMO SDLC Link Service

3270 Continuous Demo

To run the 3270 Continuous Demo

1.	Start SNA Server Admin by double-clicking the SNA Server Admin icon in the Microsoft SNA Server group window.

2.	Start the server by selecting it in the Servers and Connections window and selecting Start Services from the Service menu.

3.	Start the 3270 Applet by double-clicking the SNA Server 3270 Applet icon in the Microsoft SNA Server group window.

4.	From the Session menu, choose Session Configuration.

Ensure that the correct LU is selected (that is, the LU that has been configured for the 3270 continuous demo script).

5.	From the Session menu, choose Connect.

The SDLC connection activates (changing from On Demand to Active in SNA Admin) and the host subsystem selection screen appears.

6.	Type vm and press Enter.

The host logon screen appears.

7.	Type your user ID and password and press Enter.

The host logon sequence completes and the ready prompt appears.

8.	Type flash and press Enter.

Flash will run indefinitely. (Flash is a test transaction program that runs on the host, continuously sending screenfuls of data to the emulator. The 3270 Continuous Demo script emulates this behavior.)

9.	From the Session menu of the 3270 Applet window, choose Disconnect.

The emulator disconnects and the SDLC connection returns to an On Demand condition.

3270 Logon Demo

To run the 3270 Logon Demo

1.	Start SNA Server Admin by double-clicking the SNA Server Admin icon in the Microsoft SNA Server group window.

2.	Start the server by selecting it in the Servers and Connections window and selecting Start Services from the Service menu.

3.	Start the 3270 Applet by double-clicking the SNA Server 3270 Applet icon in the Microsoft SNA Server group window.

4.	From the Session menu, choose Session Configuration.

Ensure that the correct LU is selected (that is, the LU that has been configured for the 3270 Logon Demo script).

5.	From the Session menu, choose Connect.

The SDLC connection activates (changing from On Demand to Active in SNA Admin) and the first host logon screen appears.

6.	Enter a user ID and password, and press ENTER.

The host subsystem selection screen appears.

7.	Type vm and press ENTER.

The host will then prompt you for a password.

8.	Type your password again and press Enter.

The host logon sequence completes and the ready prompt appears.

9.	Type logoff and press Enter.

The first logon screen reappears.

10.	From the Session menu of the 3270 Applet, choose Disconnect.

The emulator disconnects and the SDLC connection returns to an On Demand condition.

Important

If any keyboard strokes are entered after step 9, the prompt may freeze. From the Connect menu, choose Disconnect to reset the session.

This sequence can be repeated (steps 5 – 10) as often as is necessary.

AS/400 Demo

To run the 5250 continuous demo

1.	Start SNA Server Admin by double-clicking the SNA Server Admin icon in the Microsoft SNA Server group window.

2.	Start the server by selecting it in the Servers and Connections window and selecting Start Services from the Service menu.

3.	Start the 5250 Applet by double-clicking the SNA Server 5250 Applet icon in the Microsoft SNA Server group window.

4.	From the Session menu, choose Session Configuration.

5.	Type the name of the APPC Local LU alias (for example, BOBDADOM) in the Local LU Alias text box.

6.	Select the name of the Partner LU Alias (APPC Remote LU alias) that was defined for this connection (for example, REMOTE) in the Partner LU Alias text box. Choose the OK button to close the dialog box.

7.	From the Session menu, choose Connect.

The SDLC connection activates (changing from On Demand to Active in SNA Admin), and the Sign-On dialog box with the user ID/password selection appears, as shown in the following illustration.

8.	Enter a user ID and password and press Enter.

The AS/400 Sign On screen appears.

9.	Enter a user ID and password, and press Enter.

The AS/400 Main Menu appears.

10.	Type one of the following numbers and press enter to run the available demonstrations:

10. Run 5250 loop script

This will start a demonstration of 5250 flash. The 5250 Applet will cycle between the User Tasks and Display Messages screens indefinitely.

Press the ESC key to stop this emulation and return to the AS/400 Main Menu.

20. SQL Query

Starts a demonstration of running a SQL Query on a database located on an AS/400 named Rainier.

Press enter after each screen of information to step through the demonstration and return to the AS/400 Main Menu.

90. Sign off

Returns to the AS/400 Sign On screen. Begin at step 9 to repeat demo.

Note

Entering any other number or characters other than those listed above will have no effect on the demonstration.

11.	To stop the demonstration at any point, from the Session menu of the 5250 Applet, choose Disconnect.

The emulator disconnects and the SDLC connection returns to an On Demand condition.


Installing Online Documentation
	Enhancements to the Microsoft SNA Server Installation Guide	15 of 23
Installing Online Documentation

If you are installing SNA Server from a CD or network shared directory, Setup will offer to install an online version of the SNA Server documentation, including SNA Server documentation for software developers. These files require approximately 18 to 20 MB free space on the hard drive, depending on which version of Windows NT is running. If you choose to install the online documents, SNA Server Setup adds a program item to the Microsoft SNA Server program group for the master table of contents of the online documents.


New Features Installed by Setup
	Enhancements to the Microsoft SNA Server Installation Guide	16 of 23
New Features Installed by Setup

The following new features will be installed automatically by the  SNA Server 2.11 Setup program.


SNA Monitor
	Enhancements to the Microsoft SNA Server Installation Guide	17 of 23
New Features Installed by Setup

SNA Monitor

This new monitor, which is similar to the monitor in Remote Access Service, can be used to monitor the status of an SDLC connection. The SNA Server 2.11 Setup program will create an icon for this utility in the Microsoft SNA Server program group. From the SNA Monitor Setting menu, you can specify options such as sound, update interval, and which link service to monitor.


Default APPC LUs
	Enhancements to the Microsoft SNA Server Installation Guide	18 of 23
New Features Installed by Setup

Default APPC LUs

SNA Server 2.11 will create default Local and Remote APPC LUs.

During Setup of an SNA Server 2.11, a Local APPC LU will be created on the server node with suggested default values.

A default Remote APPC LU is not created during Setup, but during configuration of a peer connection. When you configure a new link service as a peer connection, and if a remote APPC LU is not detected, the following dialog box appears:

If you choose the YES button, the New APPC Remote LU Properties dialog box will appear with suggested default values.

Remember to change the default values and options if they do not match your needs.


Installing a Windows NT-Based Client
	Enhancements to the Microsoft SNA Server Installation Guide	19 of 23
Installing a Windows NT-Based Client

If you are installing on a TCP/IP network, the procedure “To install a Windows NT-based client” has been updated beginning with step 4. Please see Appendix A of the Microsoft SNA Server Planning Guide for complete details and correct procedures.


Installing a Client Running Windows Version 3.x
	Enhancements to the Microsoft SNA Server Installation Guide	20 of 23
Installing a Client Running Windows Version 3.x

If you are installing on a TCP/IP network, the procedure “To install client software to run locally on a computer running Windows version 3.x” has been updated beginning with step 5. Please see Appendix A of the Microsoft SNA Server Planning Guide for complete details and the correct procedures to follow.


EHNAPPC API Support
	Enhancements to the Microsoft SNA Server Installation Guide	21 of 23
Installing a Client Running Windows Version 3.x

EHNAPPC API Support

SNA Server version 2.11 includes a new version of EHNAPPC.DLL for Win16, which will provide native Windows support for applications written to the IBM PC Support EHNAPPC API and compatible (for example, NetSoft [image] provides a compatible API for PC Support).

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

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

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

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

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

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


CA/400 Support
	Enhancements to the Microsoft SNA Server Installation Guide	22 of 23
Installing a Client Running Windows Version 3.x

CA/400 Support

If you want to use the new IBM Client Access/400 (CA/400) for Windows product with SNA Server version 2.11, you must change entries in the WIN.INI file and rename two files in the local directory in which CA/400 is installed. This procedure is as follows:

To use CA/400 Shared Folders with SNA Server 2.11

1.	Install CA/400 Shared Folders and SNA Server version 2.11 on the computer running Windows 3.x client.

2.	Open the WIN.INI file in the WINDOWSROOT directory with Notepad or other suitable text editor.

3.	Locate the following line in the [WNAP] section of the file:

CA400SharedFolders=NO

4.	Change this to:

CA400SharedFolders=YES

5.	Locate the EHNAPPC.DLL and EHNRTRW.DLL files in the local directory in which CA/400 is installed, and rename these files to EHNAPPC.IBM and EHNRTRW.IBM (or any name different from the original).

Important

Do not rename the EHNAPPC.DLL and EHNRTRW.DLL files that SNA Server Setup has copied into the WINDOWSROOT\SYSTEM directory to enable EHNAPPC API support.

To use CA/400 with SNA Server 2.11

1.	Install CA/400 and SNA Server version 2.11 on the computer running Windows 3.x client.

2.	Open the WIN.INI file in the WINDOWSROOT directory with Notepad or other suitable text editor.

3.	Locate the following line in the [WNAP] section of the file:

CA400=NO

4.	Change this to:

CA400=YES

5.	Locate the EHNAPPC.DLL and EHNRTRW.DLL files in the local directory in which CA/400 is installed, and rename these files to EHNAPPC.IBM and EHNRTRW.IBM (or any name different from the original).

Important

Do not rename the EHNAPPC.DLL and EHNRTRW.DLL files that SNA Server Setup has copied into the WINDOWSROOT\SYSTEM directory to enable EHNAPPC API support.


Installing an MS-DOS - Based Client
	Enhancements to the Microsoft SNA Server Installation Guide	23 of 23
Installing an MS-DOS - Based Client

If you are installing on a TCP/IP network, the procedure “To install an MS-DOS – based client” has been updated beginning with step 4. Please see Appendix A of the Microsoft SNA Server Planning Guide for complete details and correct procedures.


Enhancements to the Microsoft SNA Server Administration Guide
Chapter 3	1 of 4

Enhancements to the Microsoft SNA Server Administration Guide

The following new information supplements existing information in the Microsoft SNA Server Administration Guide for version 2.1.


SNA Server Adapter and Connection Capacities
	Enhancements to the Microsoft SNA Server Administration Guide	2 of 4
SNA Server Adapter and Connection Capacities

Please note the following correction in this section of Appendix A.

The maximum number of sessions per connection for Twinax is 512, not 20.


The Command-Line Interface
	Enhancements to the Microsoft SNA Server Administration Guide	3 of 4
The Command-Line Interface

The following new options for configuring connections to the server(s) have been added to the snacfg connection (see Appendix E of the Microsoft SNA Server Administration Guide):


snacfg connection
	Enhancements to the Microsoft SNA Server Administration Guide	4 of 4
The Command-Line Interface

snacfg connection

/activatedelay:{ Default | 5s | 10s | 15s | 20s | 25s | 30s | 35s | 40s | 45s | 50s | 55s | 60s | 65s | 70s | 75s | 80s | 85s | 90s | 95s | 100s | 105s | 110s | 115s | 120s | 125s | 130s | 135s | 140s | 145s | 150s | 155s | 160s | 165s | 170s | 175s | 180s | 185s | 190s | 195s | 200s | 205s | 210s | 215s | 220s | 225s | 230s | 235s | 240s | 245s | 250s | 255s }

This value specifies the delay between successive attempts to activate a SNA Server connection. It is valid for SDLC, X.25, DLC 802.2, and Channel connection types.

/activateretrylimit:{ None | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 15 | 20 | 25 | 30 | 35 | 40 | 45 | 50 | 55 | 60 | 65 | 70 | 75 | 80 | 85 | 90 | 95 | 100 | 105 | 110 | 115 | 120 | 125 | 130 | 135 | 140 | 145 | 150 | 155 | 160 | 165 | 170 | 175 | 180 | 185 | 190 | 195 | 200 | 205 | 210 | 215 | 220 | 225 | 230 | 235 | 240 | 245 | 250 | 255 }

This option specifies the number of times the SNA server will try to activate a connection. It is valid for SDLC, X.25, DLC 802.2, and Channel connection types.

/calldirection:{ Incoming | Outgoing | Both }

This option specifies the call direction.

/channeladdress:hex string

Specifies the channel sub address for channel attach connections. Hex string is a two-digit hexadecimal number, valid range 00..FF.


Enhancements to the Microsoft SNA Server Reference
Chapter 4	1 of 7

Enhancements to the Microsoft SNA Server Reference

The following information supplements the existing information in the Microsoft SNA Server Reference.


Revisions to Error Messages
	Enhancements to the Microsoft SNA Server Reference	2 of 7
Revisions to Error Messages

The following error messages have been revised (see Chapter 3 of the Microsoft SNA Server Reference):

Under Message 23, the section entitled “Token Ring Connections” should read “Token Ring/802.2 Connections.”

Message 597

User limit of value exceeded: client connection rejected

EXPLANATION: The maximum number of licensed users (shown) has been reached and another cannot be added.

ACTION: Purchase additional licenses and increase the user count using the Control Panel Licensing dialog.


New Error Messages
	Enhancements to the Microsoft SNA Server Reference	3 of 7
New Error Messages

The following error messages have been added (see Chapter 3 of the Microsoft SNA Server Reference):

Message 690

SNA Server licensed session limit value exceeded. Number of active sessions is value.

EXPLANATION: Text to explain how the session limit is calculated and what action you should take.

ACTION: Contact your support personnel.

Message 691

Number of pending writes value exceeded the upper threshold value.

EXPLANATION: The number of pending writes has exceeded the configured upper threshold. The service which logged this event will stop sending new messages until the number of pending writes drops below the lower threshold.

ACTION: Contact your support personnel.

Message 692

Number of pending writes value has dropped below the lower threshold value.

EXPLANATION: The number of pending writes has dropped below the configured lower threshold. The service which logged this event will resume sending new messages.

ACTION: None required.

Message 693

Service Table Update to clients.

Reason  = value

EXPLANATION: The service or application which logged this event generated a service table update to all clients.

ACTION: None required.

Message 694

SNA Server failed to add a PC-based service value. The VnsAddSvc() function failed with VINES error value.

EXPLANATION: SnaBase failed to create a Banyan VINES PC-based service. This step is necessary for the SNA Server to function correctly in a Banyan VINES network.

Most common error codes:

155  = The net/host is unreachable, communication problem between SNA Server machine and VINES Server.

1001 = Bad name, incorrect syntax appeared in a StreetTalk name.

1013 = No such object, StreetTalk cannot find this object.

1015 = Object already exists, an object with the same name already exists in the network.

1016 = Not an object name, the name specified is not a name StreetTalk knows.

1033 = Access denied, a user tried to change StreetTalk information without proper authorization.

1801 = User has not logged on to the VINES network.

ACTION: Contact your support personnel. The most common cause for this error is that the currently logged on user has not enough privileges to create a new VINES service, or there already exists another StreetTalk object with the same name.

Message 695

SNA Server failed to set the SPP port for service value. The VnsSetSSppPort() function failed with VINES error value.

EXPLANATION: SnaBase failed to set its own SPP port number. This step is necessary for the SNA Server to function correctly in a Banyan VINES network.

Most common error codes:

155  = The net/host is unreachable, communication problem between SNA Server machine and VINES Server.

1001 = Bad name, incorrect syntax appeared in a StreetTalk name.

1013 = No such object, StreetTalk cannot find this object.

1015 = Object already exists, an object with the same name already exists in the network.

1016 = Not an object name, the name specified is not a name StreetTalk knows.

1033 = Access denied, a user tried to change StreetTalk information without proper authorization.

1801 = User has not logged on to the VINES network.

ACTION: Contact your support personnel.

Message 696

SNA Server failed to add a StreetTalk list value. The VnsAddSStList() function failed with VINES error value.

EXPLANATION: SnaBase failed to create a StreetTalk list. This step is necessary for the SNA Server to function correctly in a Banyan VINES network.

Most common error codes:

155  = The net/host is unreachable, communication problem between SNA Server machine and VINES Server.

1001 = Bad name, incorrect syntax appeared in a StreetTalk name.

1013 = No such object, StreetTalk cannot find this object.

1015 = Object already exists, an object with the same name already exists in the network.

1016 = Not an object name, the name specified is not a name StreetTalk knows.

1033 = Access denied, a user tried to change StreetTalk information without proper authorization.

1801 = User has not logged on to the VINES network.

ACTION: Contact your support personnel. The most common cause for this error is that the currently logged on user has not enough privileges to create a new StreetTalk list or there already exists an other StreetTalk object with the same name.

Message 697

SNA Server failed to add the service value to the list value. The VnsAddSStMember() function failed with VINES error value.

EXPLANATION: SnaBase failed to add its name to the list of SNA Servers in the Windows NT domain. This step is necessary for the SNA server to function correctly in a Banyan VINES network.

Most common error codes:

155  = The net/host is unreachable, communication problem between SNA Server machine and VINES Server.

1001 = Bad name, incorrect syntax appeared in a StreetTalk name.

1013 = No such object, StreetTalk cannot find this object.

1015 = Object already exists, an object with the same name already exists in the network.

1016 = Not an object name, the name specified is not a name StreetTalk knows.

1033 = Access denied, a user tried to change StreetTalk information without proper authorization.

1801 = User has not logged on to the VINES network.

ACTION: Contact your support personnel.

Message 698

Invalid Destination L-value. Parameter: value , Message: value , Valid range value  - value

EXPLANATION: This was caused by an internal error in SnaServer. This error is usually followed by a more specific error message 699.

ACTION: Provide network support personnel with the event log file(s) related to SNA, and SNA internal trace file(s). For information about SNA log and trace files, see the “Microsoft SNA Server Administration Guide."

Message 699

Invalid message: MsgType value , MhType value

  Message Header: value

EXPLANATION: This was caused by an internal error in SnaServer.

ACTION: Provide network support personnel with the event log file(s) related to SNA, and SNA internal trace file(s). For information about SNA log and trace files, see the “Microsoft SNA Server Administration Guide.”

Message 1020

The SnaBase was unable to generate a valid SID for initial ownership of the SNA Domain. The Final Windows NT Error that occurred was value.

The text of the error is: value.

Message 1021

The SnaBase received a duplicate RU message number value from DLC.

Message 3065

A Bind sent by the host for a 3270 session was rejected

EXPLANATION: This was caused by an internal error in SnaServer.

ACTION: Report this error to SnaServer Support.


Registry and Environment Variables
	Enhancements to the Microsoft SNA Server Reference	4 of 7
Registry and Environment Variables

All of the registry and environment variables listed in Appendix C of the Microsoft SNA Server Reference for version 2.1 apply to this release, with the following additions and modifications.

To access or modify these variables, use the Registry Editor, REGEDT32. For information about the Registry Editor, see your Windows NT documentation.

Caution

You should not make changes to the Registry unless directed by a technical support engineer.


Registry Variables Used Only on an SNA Server
	Enhancements to the Microsoft SNA Server Reference	5 of 7
Registry and Environment Variables

Registry Variables Used Only on an SNA Server

SnaServer Service: Location and Names of Variables

The Registry variables that affect the SnaBase service on an SNA server are found in the following location in the Registry:

HKEY_LOCAL_MACHINE

SYSTEM

CurrentControlSet

Services

SnaServr

Parameters

The changes to the variables that affect the SnaServer service are as follows:

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

The default for this variable has been changed to YES.

The following replace the descriptions for these variables listed in the Microsoft SNA Server Reference.

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

When this variable is defined (with any value), the node will allocate pooled LUs even if they are inactive LUs on a connection that was activated on server startup or by an administrator. If this variable is not explicitly defined, among pooled LUs on such a connection, only active LUs are allocated.

Setting this variable means that when users cannot get host access, they can use the OIA status line (in a 3270 emulator) to distinguish between two possible causes: all LUs are in use, or the host connection is down.

Note that in Comm Server 1.x, there was a similar environment variable, ALLOCACT, which had the opposite sense. That is, ALLOCACT prevented the allocation of inactive LUs; if ALLOCACT was not set, inactive LUs on activated connections were always allocated.

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

When this variable is defined (with any value), the node allows Begin Bracket, Exception Response (BB RQE) on any request, even on requests that do not contain End Bracket (EB). If this variable is not explicitly defined, requests containing BB RQE but not EB are rejected with sense code 2003, in accordance with SNA protocols.

Note that BB RQE is allowed if Change Direction (CD) is set.

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

When this variable is defined (with any value), the local LU deactivates sessions by directly sending UNBIND (cleanup). If this variable is not explicitly defined, when LU 6.2 sessions are deactivated, the two LUs exchange BIS requests before UNBIND is sent. Setting this variable is a workaround for a possible host problem in which the LU is erroneously marked inactive.

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

When this variable is defined (with any value), it causes the SNA server to ignore sense code 4004. In other words, it causes CEB (conditional end bracket) to be accepted when EC (end chain) is not set, and EB (end bracket) to be accepted when BC (begin chain) is not set. If this variable is not explicitly defined, there is a normal response to sense code 4004.

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

When this variable is defined (with any value), SNA Server will perform CNOS negotiation for APPC LUs only when sessions are required. If this variable is not explicitly defined, SNA Server performs these negotiations when the connection is started.

Note that with autoactivated sessions, regardless of the NOINITCNOS setting, CNOS negotiation must always be performed when the connection is started.

Setting this variable speeds up the starting process for connections that have large numbers of LUs.

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

When this variable is defined (with any value), the SNA server does not retry a BIND request when the response to the BIND is an UNBIND cleanup request. This prevents repetitive BIND failures when routing LU 6.2 sessions through a host.

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

When this variable is defined (with any value), 3270 sessions are terminated directly by sending UNBIND (cleanup). If this variable is not explicitly defined, a TERM-SELF is sent to solicit UNBIND from host. Setting this variable is a workaround for host-based session monitors that mark the LU as inactive after the TERM-SELF sequence.


Registry Variables Used on an SNA Server or a Windows NTBased Client
	Enhancements to the Microsoft SNA Server Reference	6 of 7
Registry and Environment Variables

Registry Variables Used on an SNA Server or a Windows NTBased Client

SnaBase: Location and Names of Variables

For an SNA server or a Windows NT-based client, the Registry variables that affect the SnaBase are found in the following location in the Registry:

HKEY_LOCAL_MACHINE

SYSTEM

CurrentControlSet

Services

SnaBase

Parameters

The following SnaBase registry entry name is incorrect in the Microsoft SNA Server Reference and should be corrected as follows.

LOCALLUS:REG_SZ:localLUname has been changed and should be corrected to LOCALLUS:REG_MULTI_SZ:localLUname. This change occurs in Table C.1 (page 191), Table C.2 (page 192), and on page 204.


Environment Variables Used on Clients Running Windows Version 3.x, MS-DOS, or OS/2
	Enhancements to the Microsoft SNA Server Reference	7 of 7
Registry and Environment Variables

Environment Variables Used on Clients Running Windows Version 3.x, MS-DOS, or OS/2

The environment variables in the following section can be set on an SNA Server client running the Windows version 3.x, MS-DOS, or OS/2 operating systems. For information about accessing or modifying these variables, see “Setting Variables on Different Operating Systems” in Appendix C of the Microsoft SNA Server Reference.

SnaBase

The following SnaBase registry entry has been added and relates to the automatic termination of the wnap process, and applies only to clients running Windows version 3.x:

AutoTerminate={YES | NO}    Default: NO

When this variable is set to YES, wnap is automatically closed when the Windows 3.x application session is closed. Wnap must be automatically started for the automatic termination to be enabled. If wnap is manually started, wnap will not terminate, even if set to Yes.

For more information on this topic, see the section "Automatic Termination Of The WNAP Process" in the chapter entitled "Additional Information."


Enhancements to the 3270/5250 Applet User’s Guide and Managing SNA Server
Chapter 5	1 of 5

Enhancements to the 3270/5250 Applet User’s Guide and Managing SNA Server

The following additions and corrections apply to the 3270/5250 Applet User’s Guide and Managing SNA Server for SNA Server version 2.1.


3270/5250 Applet User’s Guide
	Enhancements to the 3270/5250 Applet User’s Guide and Managing SNA Server	2 of 5
3270/5250 Applet User’s Guide

The following addition applies to this book.


Keyboard Mapping Tables
	Enhancements to the 3270/5250 Applet User’s Guide and Managing SNA Server	3 of 5
3270/5250 Applet User’s Guide

Keyboard Mapping Tables

The following addition applies to the keyboard map for the 3270 Applet.

3270 Applet Keyboard Map

3270 keyboard	Enhanced 101 keyboard

|	shift + \


Managing SNA Server
	Enhancements to the 3270/5250 Applet User’s Guide and Managing SNA Server	4 of 5
Managing SNA Server

The following correction applies to this book.


Windows NT Event Viewer Utility
	Enhancements to the 3270/5250 Applet User’s Guide and Managing SNA Server	5 of 5
Managing SNA Server

Windows NT Event Viewer Utility

Please correct Step one of the following procedure, as shown here:

To specify event types and servers for event logging

Start SNA Server Admin by double-clicking the SNA Server icon in the SNA Server group window.


Enhancements to the SDK Documentation
Chapter 6	1 of 24

Enhancements to the SDK Documentation

The following additions and corrections apply to the books in software development kit (SDK) for SNA Server version 2.1, including:

APPC Programmer’s Guide

CPI-C Programmer’s Guide

LUA Programmer’s Guide

3270 Emulator Interface Specification

SNA Device Interface Specification


APPC Programmer’s Guide
Enhancements to the SDK Documentation	2 of 24

APPC Programmer’s Guide

The following sections correct or clarify information in the APPC Programmer’s Guide.


Addition to Chapter 1, "Introduction to APPC"
Enhancements to the SDK Documentation	3 of 24

APPC Programmer’s Guide

Addition to Chapter 1, "Introduction to APPC"

In the section entitled “MS-DOS Considerations,” add the following to the definition of Partner TPs:

SNA Server invokable TPs cannot be run on MS-DOS–based clients.


Addition to Chapter 2, "Transaction Programs"
Enhancements to the SDK Documentation	4 of 24

APPC Programmer’s Guide

Addition to Chapter 2, "Transaction Programs"

In the section entitled “Invokable TPs,” add the following note after the first paragraph in this section:

Note

SNA Server invokable TPs cannot be run on MS-DOS–based clients.


Correction to Chapter 3, "APPC Management Verbs"
Enhancements to the SDK Documentation	5 of 24

APPC Programmer’s Guide

Correction to Chapter 3, "APPC Management Verbs"

In the sema parameter description of [MC_]RECEIVE_AND_POST, replace the final sentence with the following:

On OS/2, the sema parameter is either a RAM or system semaphore. On Windows NT, the sema parameter is an event handle obtained by calling either the CreateEvent or OpenEvent Win32 function.


Addition to Chapter 6, "APPC Extensions for the Windows Environment"
Enhancements to the SDK Documentation	6 of 24

APPC Programmer’s Guide

Addition to Chapter 6, "APPC Extensions for the Windows Environment"

Add the following to the description of the wVersionRequired parameter of the WinAPPCStartup function:

The current version of the Windows APPC API is 1.0.


Correction to Chapter 8, "Common Service Verbs"
Enhancements to the SDK Documentation	7 of 24

APPC Programmer’s Guide

Correction to Chapter 8, "Common Service Verbs"

In the description of the source_cp parameter of GET_CP_CONVERT_TABLE, replace the sentence “This value is user defined; it can range from 65280 through 65534” with the following:

User-defined code page in the range from 65280 through 65535


Addition to Chapter 9, "CSV Extensions for the Windows Environment"
Enhancements to the SDK Documentation	8 of 24

APPC Programmer’s Guide

Addition to Chapter 9, "CSV Extensions for the Windows Environment"

Add the following to the description of the wVersionRequired parameter of the WinCSVStartup function:

The current version of the Windows CSV API is 1.0.


Correction to Appendix C, "Sample APPC TPs in the SDK"
Enhancements to the SDK Documentation	9 of 24

APPC Programmer’s Guide

Correction to Appendix C, "Sample APPC TPs in the SDK"

In the section entitled “Building the TPs,” replace the equivalent text with the following:

For example, if you copy the contents of \SDK directory of the SNA Server CD-ROM to C:\SNASDK, use the following lines to set the variables:

ISVLIBS=C:\SNASDK\LIB\WINNT

ISVINCS=C:\SNASKD\INC

SAMPLEROOT=C:\SNASDK\SAMPLES


CPI-C Programmer’s Guide
Enhancements to the SDK Documentation	10 of 24

CPI-C Programmer’s Guide

The following sections correct or clarify information in the CPI-C Programmer’s Guide.


Correction to Chapter 1, "Introduction to CPI-C"
Enhancements to the SDK Documentation	11 of 24

CPI-C Programmer’s Guide

Correction to Chapter 1, "Introduction to CPI-C"

In the section entitled “Ending a Conversation.” the Terminate_Application (cmterm) call is no longer supported and should be deleted.


Correction to Appendix B, "Sample CPI-C TPs in the SDK"
Enhancements to the SDK Documentation	12 of 24

CPI-C Programmer’s Guide

Correction to Appendix B, "Sample CPI-C TPs in the SDK"

In the section entitled “Building the TPs,” replace the equivalent text with the following:

For example, if you copy the contents of \SDK directory of the SNA Server CD-ROM to C:\SNASDK, use the following lines to set the variables:

ISVLIBS=C:\SNASDK\LIB\WINNT

ISVINCS=C:\SNASKD\INC

SAMPLEROOT=C:\SNASDK\SAMPLES


LUA Programmer’s Guide
Enhancements to the SDK Documentation	13 of 24

LUA Programmer’s Guide

The following sections correct or clarify information in the LUA Programmer’s Guide.


Additions to Chapter 2, "Writing LUA Applications"
Enhancements to the SDK Documentation	14 of 24

LUA Programmer’s Guide

Additions to Chapter 2, "Writing LUA Applications"

Add the following to the section entitled “Windows NT System Considerations”:

Restrictions on 3270-type LUs

A Windows NT process cannot access 3270-style LUs from both the FMI and LUA APIs at the same time. The process can use the LUA APIs to access LUA LUs while using FMI APIs to access 3270-style LUs, however.

In the section entitled “SNA Considerations,” add the following to the last paragraph under “Courtesy acknowledgments”:

Note that the application does not need to send a courtesy acknowledgment for each exception-response-only request. For efficiency, the application can respond less frequently. The node treats a courtesy acknowledgment as an implicit acknowledgment for all prior pending requests.


Additions to Chapter 4, "LUA SLI Verbs"
Enhancements to the SDK Documentation	15 of 24

LUA Programmer’s Guide

Additions to Chapter 4, "LUA SLI Verbs"

Add the following to the section entitled “Primary with SSCP Access” in the description of the SLI_OPEN verb and to the description of the SLI_SEND verb:

When issuing SLI_SEND, an application should not specify any flow flag unless the application is sending a response, as specified in the lua_message_type parameter of SLI_OPEN.


Correction to Appendix A, "SNA Server Enhancements to the Windows Environment"
Enhancements to the SDK Documentation	16 of 24

LUA Programmer’s Guide

Correction to Appendix A, "SNA Server Enhancements to the Windows Environment"

On page 151, the syntax shown for the GetLuaReturnCode function is incorrect. The following shows the correct syntax:

int WINAPI GetLuaReturnCode (struct LUA_COMMON FAR * vpb, UINT buffer_length, unsigned char FAR * buffer_addr)


3270 Emulator Interface Specification
Enhancements to the SDK Documentation	17 of 24

3270 Emulator Interface Specification

The following sections provide information about changes and clarifications in 3270 Emulator Interface Specification.


Change to Chapter 4, "FMI Message Formats"
Enhancements to the SDK Documentation	18 of 24

3270 Emulator Interface Specification

Change to Chapter 4, "FMI Message Formats"

In section 4.1.1, “Open(SSCP) Request,” remove the cross reference to section 3.1 from the eleventh bulleted item in the section entitled “Notes.”


Addition to Chapter 3, "The Function Management Interface"
Enhancements to the SDK Documentation	19 of 24

3270 Emulator Interface Specification

Addition to Chapter 3, "The Function Management Interface"

Add the following to the end of section 3.3.2, “Closing the PLU Connection”:

When an application is using the LUA variant of the FMI, issuing a Close (PLU) request causes the node to immediately unbind the PLU session by sending an UNBIND request to the PLU. The Close(PLU) Response is returned to the application on receipt of the UNBIND response (see figure 3.3.9).

Figure 3.3.9.    Closing the PLU connection using the LUA variant of the FMI.


SNA Device Interface Specification
Enhancements to the SDK Documentation	20 of 24

SNA Device Interface Specification

The following sections provide information about changes and clarifications in SNA Device Interface Specification.


Addition to Chapter 2, "The BASE/DMOD Interface"
Enhancements to the SDK Documentation	21 of 24

SNA Device Interface Specification

Addition to Chapter 2, "The BASE/DMOD Interface"

Add the following entry-point description to section 2.9.1, SNALink Entry Points

SNALinkTerminate—Terminate SNA Link

The BASE will call this routine, when present, during service shutdown. This allows the DLL to free memory, release system resources (such as events), close drivers.

C Declaration

void SNALinkTerminate (void)

Usage Notes

This routine must not send messages to other SNA components.


Changes to Chapter 4, "Message Formats"
Enhancements to the SDK Documentation	22 of 24

SNA Device Interface Specification

Changes to Chapter 4, "Message Formats"

In section 4.9, “Send-XID,” change the description of the numelts field to the following:

Number of buffer elements

In the same section, add the following to the Note:

The Send-XID message can contain zero elements (numelts = 0) or a single, empty element (hdreptr->startd < hdreptr->endd). In these cases, the link service is expected to transmit a NULL XID.


Change to Chapter 8, "Compiling and Linking with SNA Server"
Enhancements to the SDK Documentation	23 of 24

SNA Device Interface Specification

Change to Chapter 8, "Compiling and Linking with SNA Server"

In section 8.4, “Compiler Options,” in the description of the /D WIN32_SUPPORT option, change NT_SUPPORT to WIN32_SUPPORT.

In section 8.5, “Linking,” change SNALINK.LIB to IHVLINK.LIB.


Changes to the Appendix
Enhancements to the SDK Documentation	24 of 24

SNA Device Interface Specification

Changes to the Appendix

Replace section A.3.4, “IOCTL Commands,” with the following:

The parameters to the IOCtl request packet are stored in the following fields in the associated I/O request packet (IRP).

IRP.CurrentStackLocation->IOControlCode	Function Code

IRP.SystemBuffer	Address of Parameter Buffer (if used)

IRP.CurrentStackLocation->InputBufferLength	Length of Parameter buffer

IRP.UserBuffer	Address of Data Buffer

IRP.CurrentStackLocation->OutputBufferLength	Length of Data Buffer

Note that under Windows NT, the operating system reserves the low nibble of IOCtl function codes to determine the method used to map the various buffers passed on the DeviceIoControl function call into the drivers address space. The various options available to device drivers writers are:

Low nibble	IOCtl definition

0	METHOD_BUFFERED

1	METHOD_IN_DIRECT

2	METHOD_OUT_DIRECT

3	METHOD_NEITHER

For further details of the memory mapping performed by these various options, refer to the Windows NT DDK documentation.

For a driver function code of ZZ, using memory mapping code M, the IOCtl code passed on the DeviceIoControl function call will therefore be 0xZZM.

The Function Codes are set out as shown below. Note that all other Function codes will be returned with the error “ERROR_INVALID_DEVICE_REQUEST” in the field IoStatus.Status. The Windows NT I/O System validates the address and length of the areas passed as parameter and data packets. If the address validation fails, an exception will be raised.

All requests must return immediately. In general, they are simple, immediate operations anyway, but in the cases of Transmit Frame and Receive Frame, the driver must not suspend the calling SNALink thread while waiting for I/O to complete — a relevant return code should be sent instead, allowing the SNALink to retry.

The complete list of functions is:

Function	Function Code	Windows NT IOCtl Code
Set Event/Semaphore Handle	0x41	0x410
Set Link Characteristics	0x42	0x420
Set V24 Output Status	0x43	0x430
Transmit Frame	0x44	0x441
Abort Transmitter	0x45	0x450
Abort Receiver	0x46	0x460
Get V24 Status	0x62	0x622
Receive Frame	0x63	0x632
Read Interface Record	0x64	0x642
Function 0x41: Set Event/Semaphore Handle

Purpose

This supplies the driver with the handle of an event that can be used for signaling the SNALink software.

Parameter taken from IoCtl Call:

IRP.UserEvent	Event Handle

Where

The handle must refer to an Event/Semaphore owned by the SNALink process. The driver will set the event to indicate the completion of a transmission or the availability of received data or status. Although not required by the driver, the event passed here by the SNALink will normally be the global Base event.

Notes

This function should be called once only, immediately after the OPEN has been issued. The event will be set when:

Frames are transmitted from the driver buffers.

Frames are received into the driver buffers.

Status information is updated in the Interface Record (see function 64H).

Returns

If the supplied parameter is NULL, the function will return a status of STATUS_INVALID_PARAMETER, with additional information of INFO_SET_EVENT_NO_EVENT. For any other illegal parameter, an exception will be raised.

Function 0x42: Set Link Characteristics

Purpose

This request sets the link protocol parameters required by the driver.

Parameter Packet Format:

WORD	Frame Size

DWORD	Data rate

BYTE	Station address 1

BYTE	Station address 2

BYTE	Link Options

BYTE	Reserved

Where

Frame Size indicates to the driver the minimum amount of contiguous receiver buffering that must be available for any individual frame.

Data Rate is the line speed in bits per second. If Link Options bit 3 is not set, this field is ignored.

Station Addresses 1 and 2 are the station addresses the user wishes to receive on if “selective” reception is to be used (typically for multi-dropped secondaries). Only frames of data commencing with either of these values will be passed up to the user — others are ignored or discarded.

If the SNALink wishes to listen on only one station address, station address 2 should be set to 0.

A value of 0 in both fields indicates that all error-free received frames are to be passed to the SNALink, regardless of the contents of their first address byte.

Link Options is a bit map. The default is all values set to 0. The bits are used as follows:

Bit 7 set to	1 = Four Wire (constant RTS/CTS) 0 = Two Wire (switched RTS/CTS)

Bit 6 set to	1 = NRZI encoding 0 = NRZ encoding

Bit 5 set to	1 = HDLC level 1 conventions 0 = SDLC level 1 conventions

Bit 4 set to	1 = Full duplex (simultaneous 2-way) data 0 = Half duplex (alternating 1-way) data

Bit 3 set to	1 = Generate internal clocking  0 = Take external clocking

Bit 2 set to 	1 = Use DMA if available 0 = Do not use DMA on this link

Bit 1 set to	1 = Reset all statistics to 0 0 = Leave accumulated statistics as is

Bit 0 reserved.

Note

Not all of the preceding options are supported by the standard SNA Server synchronous card drivers.

Notes

The driver should always start the receiver at the end of processing this request. If either the transmitter or receiver is active when this request is issued, the driver aborts the current frame before resetting the link characteristics, then restarts the previous operation.

Returns

IoStatus.Status		IoStatus.Information		Description
STATUS_INVALID_PARAMETER		IO_ERR_LINKCHARBUF_WRONG_SIZE
STATUS_INVALID_PARAMETER		IO_ERR_FRAME_BUF_TOO_SMALL		Buffer must be at least 268 bytes
STATUS_INVALID_PARAMETER		IO_ERR_FRAME_BUF_TOO_BIG		Buffer maximum size is 2048 bytes
STATUS_INVALID_PARAMETER		IO_ERR_NO_CLOCKS		No internal clocking available
STATUS_DATA_ERROR		IO_ERR_HARDWARE_8273CMD_TIMEOUT
STATUS_SUCCESS		IO_ERR_NO_DMA_FDX		DMA requested, but cannot be used
Function 0x43: Set V.24 Output Status

Purpose

This call allows the SNALink software to alter the modem output status on the adapter V.24 interface. There is no parameter or data packet on this request. The relevant V.24 settings are put into the driver Interface Record (see Function 61H) by the SNALink prior to calling the driver.

Error returns

IoStatus.Status	IoStatus.Information
STATUS_DATA_ERROR	IO_ERR_HARDWARE_8273CMD_TIMEOUT
Function 0x44: Transmit Frame

Purpose

The SNALink calls this function to transfer a frame of data to the driver.

Parameters

IRP.CurrentStackLocation.OutputBufferLength	Frame Length

IRP.UserBuffer	Frame data

whereFrame Length is the size of the frame pointed to by the data buffer pointer. The frame includes the control, address and information field (if present), but no allowance should be made for flags or CRC bytes.

Where

Frame Data is the contents of the frame being transmitted. Frame Length is the number of bytes in the frame contents.

Notes

In two-wire configurations, the driver must raise RTS and wait for CTS from the modem before initiating a transmission. The driver should then drop RTS when all frames have been transmitted. The driver assumes that the transmission is complete when both of the following are true:

The transmit buffer becomes empty (if the link is configured as half duplex)

The last frame transmitted had the Poll/Final bit set in the second byte.

Returns

IoStatus.Status	IoStatus.Information
STATUS_BUFFER_TOO_SMALL	IO_ERR_TX_BUFFER_FULL
STATUS_INVALID_PARAMETER	IO_ERR_TX_FRAME_TOO_BIG
Refer also to the description of the interface record — the driver updates a field within the interface record reflecting the amount of buffer space available.

Function 0x45: Abort Transmitter

Purpose

The SNALink calls this function to clear down the driver’s transmitter.

Notes

This request causes the driver to abort the current frame transmission and to flush its internal buffers of any further data pending transmission. In two-wire configurations, the driver should also drop RTS.

Function 0x46: Abort Receiver

Purpose

The SNALink calls this function to clear down the driver’s receiver.

Notes

This request causes the driver to stop the receiver and to flush its internal buffers of any received data. It should be used to clear down the receiver, for instance, before altering the Link Characteristics.

Function 0x47: Off-Board Load

Not supported.

Function 0x61: Get/Set Interface Record

This function has been superseded by Function 0x64: Get/Set Interface Record

Function 0x62: Get V.24 Status

Purpose

The SNALink calls this function to read the current state of the modem interface lines. No parameter or data packet is passed. This request causes the driver to update the Input V.24 Status field in the driver interface record.

Function 0x63: Receive Frame

Purpose

The SNALink calls this function to read a data frame from the driver’s buffers.

Parameters

IRP.CurrentStackLocation.OutputBufferLength	Frame Length

IRP.UserBuffer	Frame Data ()

Frame Length is the size of the frame transferred into the data buffer by the driver. The frame includes the control, address and information field (if present), but no flags or CRC bytes. When the request is issued, Frame Length is set to the maximum length of the buffer addressed by the Data Packet pointer.

Frame Data is the contents of the frame that has been received. Frame Length is the number of bytes in the frame contents.

Notes

The driver will transfer the next available received frame to the supplied buffer. Note that if the buffer is not large enough, a “buffer overflow” error is returned, which allows the application to decide if “oversize” frames are an error. If not, then a second attempt to read should be made, using a buffer at least Frame Length bytes long. A length of 0 is returned if there are no frames ready to be received.

Returns

IoStatus.Status	IoStatus.Information

STATUS_BUFFER_TOO_SMALL	n/a

Function 0x64: Get/Set Interface Record

Purpose

This function reads the driver’s Interface Record, and copies into the buffer passed by the SNALink. The buffer must be allocated by the SNALink prior to making this call.

Parameters

IRP.SystemBuffer	Interface Record Address (IN)
Where

Interface Record Address is a 32-bit pointer to the driver’s interface record area.

The interface record format is as follows:

Description	Type

Received Frames 	int

Transmit Buffer Space	int

Status Events 	int

Input V.24 Status	UCHAR

Output V.24 Status	UCHAR

Statistics Counters 	int[11]

Received Frames is the number of frames currently queued in the driver receive buffers.

Transmit Buffer Space is used to signal to the SNALink:

Whether more frames can be provided to the driver.

Whether the driver still has frames waiting to be sent.

The transmit Buffer Space field indicates the maximum frame size that the driver can currently accept. This is updated after each successful Transmit Frame IoCtl, and should be checked by the SNALink before sending further frames to the driver.

Status Events is a count of the total number of increments made to the Statistics Counters.

Input V.24 Status is a bitmap of the current logical state of the input interface lines, a value of 1 meaning ON and a value of 0 meaning OFF. The pins are mapped as follows:

Bit No.	V.24 Circuit Name	Circuit No.	RS-232C Pin

7 - 5 	Reserved	142	25

4	Test Indicator	125	22

3	Calling Indicator	125	22

2	RLSD (commonly DCD)	109	8

1	Data Set Ready (DSR)	107	6

0	Ready For Sending (CTS)	106	5

Output V.24 Status is a bitmap of the current logical state of the output interface lines, a value of 1 meaning ON and a value of 0 meaning OFF. The pins are mapped as follows:

Bit No.	V.24 Circuit Name	Circuit No.	RS-232C Pin

7 - 5 	Reserved

4	Maintenance Test	140	18

3	Select Standby	116	11

2	Data Signal Rate Selector	111	23

1	Data Terminal Ready (DTR)	108/2	22

0	Request to Send (RTS)	105	4

Note that the driver will raise and lower RTS as necessary while transmitting, reflecting the state of RTS in the output V.24 status field. The application should not, therefore, try to manipulate RTS itself.

The Statistics Counters are running counts of various kinds of link status information. The events they relate to are:

Counter 1	Frames received with incorrect CRC

Counter 2	Frames larger than the maximum size received

Counter 3	Frames smaller than 32 bits received

Counter 4	Frames received that are not a multiple of 8 bits

Counter 5	Aborted frames received

Counter 6	Transmitter underruns

Counter 7	Receiver overruns

Counter 8	RLSD drops in mid-reception

Counter 9	CTS drops in mid-transmission

Counter 10	DSR drops

Counter 11	Hardware failures (adapter or modem).

Notes

The interface record provides a fast mechanism to use to decide whether a frame can be transmitted, whether there are any frames to be received, and so on. The driver maintains this information. Each time the SNALink requires this information, it calls Read Interface Record to get a copy of the current Interface Record. After each call, the driver clears the statistics counters in its own Interface record. The V.24 status and transmit and receive data information are unchanged.


Licensing and License Manager
Additional Notes	1 of 5

Licensing and License Manager

Network solutions generally have the following two components:

Servers that contain information and provide services

Clients that access information and services

With the Microsoft BackOffice licensing model, these components are licensed separately, so you purchase only what you need to build a network solution for your company’s particular requirements. Each server requires a license and each client computer accessing a server also requires a license (called a Client Access License).

The license agreements for certain Microsoft BackOffice server products (such as SNA Server, Windows NT Server, and SQL Server) also provide the flexibility of two licensing modes: Per Server and Per Seat. With Per Server licensing, each SNA Server Client Access License is assigned to a particular server and allows one connection to that server. The Per Seat Licensing mode requires an SNA Server Client Access License for each computer that accesses SNA Server. Once a computer is licensed in the Per Seat mode, it may access any computer running SNA Server installed on the network at no additional charge.

SNA Server Client Access Licenses are separate from the desktop operating system software you use to connect to Microsoft server products. Purchasing Microsoft Windows for Workgroups, Windows NT Workstation, or any other desktop operating system (such as Macintosh [image]) that connects to Microsoft server products does not constitute a legal license to connect to those Microsoft server products. In addition to the desktop operating system, SNA Server Client Access Licenses must also be purchased.

During SNA Server Setup, a detailed Choose Licensing Mode dialog box appears that enables administrators to do the following activities:

Obtain online Help describing the two licensing modes: Per Server and Per Seat

View online versions of the SNA Server 2.11 Client Access License and Server License agreements

Select the licensing mode that best suits their network or business requirements

Agree to the terms and conditions of the license agreement

For more information on changes to Setup in SNA Server 2.11 and for definitions with graphic descriptions of the Per Server and Per Seat licensing modes, and examples of when to use each mode, see Chapter 2, “Enhancements to the Microsoft SNA Server Installation Guide.”

Tracking licenses manually on local computers or within a small domain is time consuming but possible. Tracking licenses without the assistance of automated tools across an entire organization or enterprise with multiple domains can be very difficult, extremely costly, and overly time consuming. A tool that manages and tracks licenses and usage throughout an organization can help contain these costs. A tool that automatically replicates licensing data from all the primary domain controllers (PDCs) in the organization to a centralized database on a specified master server can also make it easier for a company to comply with legal requirements.

SNA Server 2.11 installed on a Windows NT Server 3.51 includes the following two new administrative tools that help to reduce these costs and the administrative overhead of license tracking:

The Licensing option in Control Panel

The License Manager program in the Network Administration program group

Note

License Manager is available only with Windows NT Server version 3.51 or later.

These tools provide a way for administrators to track Client Access Licenses across an organization and ensure compliance with the requirements of the Microsoft BackOffice family license agreements.

After the initial Setup process, administrators can use the Licensing option in Control Panel if they need to change the licensing mode on that local computer from Per Server to Per Seat (a one-time-only option). They can also use it to configure licensing replication for that computer.

Administrators can use the License Manager program to obtain a centralized view of Per Seat and Per Server licenses across the organization, manage the purchasing or deleting of licenses for products on network servers over which they have administrative rights, view usage statistics per user, and balance the licensing replication load across the network.

Note

Licensing replication does not depend on nor does it use the server replication process.


Licensing
Additional Notes	2 of 5

Licensing

When SNA Server 2.11 is installed on a computer running Windows NT Server 3.5x, a Licensing icon is added to Control Panel. If you have administrative authority for your local server or for your server’s domain, you can double-click the Licensing icon to display the Choose Licensing Mode dialog box. In this dialog box, you can perform a one-time, one-way licensing mode change from Per Server to Per Seat. This change is currently possible only with SNA Server, SQL Server, and Windows NT Server 3.51. You cannot legally change the licensing mode from Per Seat to Per Server.

Notice that, if you select the Per Server licensing mode for those server products, you must specify the number of computers that can concurrently connect to the server on which the product is installed.

The online Help for the Choose Licensing Mode dialog box provides descriptions of these two licensing modes, the dialog-box options, and online versions of the license agreements. It also has an overview of Microsoft’s licensing model and provides answers to frequently asked questions regarding Client Access Licenses.

License tracking can be local, by domain, or across an entire organization or enterprise. By maintaining a reasonably up-to-date historical database of all purchases and deletions on a centralized master server, an administrator can ensure the company’s legal compliance with license agreements for the various software products on their network. To do this task, they need to be able to replicate licensing information on a regular basis from each server to this master server.

Choosing the Replication button displays the Replication Configuration dialog box. In this dialog box, you can either accept the default values shown or specify the master server to which all licensing information for that domain will be replicated and how frequently that will happen.

The master server is a server in an organization that has been designated as the final centralized repository of all licensing data for that organization. It can be either the PDC for that individual domain or a specified enterprise server. An enterprise server is the server to which multiple PDCs in a large organization will replicate. (In the box next to Enterprise Server, you need to type a network name for that server, such as ENTERPRISE, without two backslashes [\\].)

The primary domain controller is the default master server for all servers in a domain and all backup domain controllers. Those servers will replicate automatically to this PDC. Selecting and specifying a different enterprise server will not change that automatic functionality. You should select the Enterprise Server option only if your computer is one of the following:

A stand alone server in its own domain, but still part of a larger organization or enterprise

The PDC for that domain, and you want to replicate to a higher server.

For more details on replication, see the “Server Browser” section later in this chapter, or the online Help files.


License Manager
Additional Notes	3 of 5

License Manager

SNA Server 2.11 installed on a computer running Windows NT Server 3.51, or higher, provides a new tool, License Manager, in the Network Administration program group to assist administrators in managing licensing for computers running SNA Server on which they have administrative rights. With License Manager, administrators can remotely change the licensing mode of products, such as SNA Server, SQL Server, and Windows NT Server 3.51, from Per Server to Per Seat, and add or delete Client Access Licenses for the Microsoft BackOffice family of server products.

For more information on License Manager, see Chapter 5 of the Microsoft Windows NT Server Update Information for Version 3.51.


Saving Security Information on the Config File
Additional Notes	4 of 5

Saving Security Information on the Config File

If a user without “Manage auditing and security log” user rights attempts to make changes to the SNA Server configuration files on a computer running Windows NT, the following error is displayed:

Error: 4006

Unable to get or set security information on the config file.

If the user chooses to save the configuration file after receiving this error, the file will be saved, but will not have any auditing information set by that user.

To grant a user the “Manage auditing and security log” right:

1.	Run Windows NT User Manager for Domains.

2.	Select Policies / User Rights.

3.	Focus on the following User Right: “Manage auditing and security log”.

4.	Grant the specific user this user right.

Note

The “Manage auditing and security log” user right is granted by default to all members of the administrator group on that computer.


Automatic Termination of the WNAP Process
Additional Notes	5 of 5

Automatic Termination of the WNAP Process

This is an update to the SNA Server 2.1 Windows client that supports automatic termination of the WNAP process.

To use this feature you'll need to add a new entry into the [WNAP] section of the WIN.INI file.

To enable automatic termination of the WNAP process on a client running Windows version 3.x

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

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

3.	Type the following on a new line below [WNAP]:

AutoTerminate=Yes

4.	Save the WIN.INI file as plain (ASCII) text (that is, avoid saving the file in a special format specific to the text editor).

WNAP must be automatically started through the starting of an SNA application (if it's started manually, WNAP will not terminate, even if AutoTerminate is set to Yes).

With some emulators the WNAP will go away when the last connection is disconnected, but with others you must exit from the emulator. This behavior depends on how the emulator is implemented. (With the SNA Server applets, the WNAP will not terminate until you exit from the applet.)


SNA Remote Access Service
Chapter 8	1 of 14

SNA Remote Access Service

SNA Remote Access Service (RAS) integrates the LU6.2 transport of SNA Server with Windows NT RAS, allowing administrators to create virtual LAN connections between Windows NT systems across an existing SNA network without having to set up redundant LAN-to-LAN networks or install dial-up modems at each site. Administrators can use the familiar RAS tools to initiate remote network connections across the SNA network and take advantage of the data compression, administration, and security features built into RAS.

This chapter explains how to install and configure software that allows RAS to communicate over an SNA network. For more information about RAS, see Microsoft Windows NT Server Remote Access Service.

This chapter covers the following information:

Overview of SNA Remote Access Service

Installing SNA Remote Access Service software

Configuring the RAS server

Configuring the RAS client

Making a RAS connection over an SNA network

Removing SNA Remote Access Service software


SNA Remote Access Service Overview
SNA Remote Access Service	2 of 14

SNA Remote Access Service Overview

SNA Remote Access Service allows Windows NT Server and Windows NT Workstation to access remote network servers through an SNA connection as though the remote network server were connected directly to the local area network (LAN). The functions available with SNA as the RAS transport are the same as those with RAS over ISDN or X.25 except for Dial Back, which is not supported by SNA Remote Access Service.

An SNA Server communicating via SNA Remote Access Service can act as a RAS server (that is, accept “dial-in” requests), a RAS client (that “dials out” to a RAS server to connect to the RAS server’s LAN), or both. In addition, a Windows NT Workstation running SNA Server client software and SNA Remote Access Service software can “dial out” through an SNA Server that is also running SNA Remote Access Service Software.

A common use of SNA Remote Access Service is to enable an administrator to manage SNA Servers remotely via the SNA network itself. As shown in Figure 6.1, an administrator working at a Windows NT Workstation running SNA Server client software and SNA Remote Access Service can use SNA Remote Access Service to connect to and administer SNA Servers at branch locations on the SNA wide area network.

Figure 6.1   Remote SNA Server Administration via SNA Remote Access Service

Figure 6.2 shows a simplified view of the RAS architecture of Windows NT versions 3.5 and later. A key component of this architecture is the asynchronous media-access control (ASYNCMAC) that mediates between the RAS protocol in kernel address space and transport-specific media/device DLLs in user address space.

Figure 6.2   Remote Access Server Architecture

SNA Server works with RAS by providing a transport (SNARAS) that provides the following interfaces:

SNARAS supports the Media/Device control interface of the RAS Connection Manager (RASMAN). This interface handles all commands to list, connect, and disconnect through a RAS port.

SNARAS supports the device I/O control (DevIoCtl) interface of ASYNCMAC. This interface allows SNA Remote Access Service to open, close, send, and receive data across a RAS connection.

SNARAS supports the WinAPPC interface to provide SNA Server access to the transport.

Figure 6.3 shows how SNARAS transport supports these interfaces.

Figure 6.3   SNARAS Transport Interfaces

The SNARAS transport is implemented as two DLLs, RASSNA.DLL (that provides the Media/Device and the DevIoCtl interfaces) and SNARAS.DLL (that provides the WinAPPC interface). These DLLs communicate through the SnaRas Interface (SRI). Figure 6.4 shows how the DLLs implement the SNARAS transport.

Figure 6.4   SNARAS DLL Implementation


Installing SNA Remote Access Service
SNA Remote Access Service	3 of 14

Installing SNA Remote Access Service

Before installing SNA Remote Access Service on an SNA Server, make sure the following software has been installed on the computer:

Microsoft Windows NT Server version 3.5 or later

Remote Access Service

SNA Server version 2.1 or later

In addition, the computer must contain a network adapter card with a certified Network Driver Interface Specification (NDIS) driver and, as needed, a network adapter for connecting to the SNA network via the desired link service. SNA Remote Access Service requires approximately 250 kilobytes of free disk space.

If you want to configure a computer running Windows NT Workstation to communicate via SNA Remote Access Service, the workstation must be running the following software before you install SNA Remote Access Service:

Microsoft Windows NT Workstation version 3.5 or later

Remote Access Service

SNA Client version 2.1 or later

The client workstation must be connected to a LAN containing at least one SNA Server running SNA Remote Access Service.

When you install and configure SNA Remote Access Service, you must restart the computer before the software can be used. Be sure the computer is ready to be restarted (that is, there are no active connections to the server) before beginning the installation procedure.


Starting the SNA Remote Access Service Setup Program
SNA Remote Access Service	4 of 14

Installing SNA Remote Access Service

Starting the SNA Remote Access Service Setup Program

This section tells how to start the SNA Remote Access Service setup program from the SNA Server CD.

To start the SNA Remote Access Service setup program

1.	Insert the SNA Server CD into the appropriate drive.

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

3.	Change to the appropriate directory:

For an Intel processor, change to the \RASSNA\I386 directory.

For a MIPS processor, change to the \RASSNA\MIPS directory.

For a Digital Alpha AXP processor, change to the \RASSNA\ALPHA directory.

For a Motorola [image] PowerPC processor, change to the \RASSNA\PPC directory.

4.	Start Setup:

To start Setup from File Manager, double-click SETUP.EXE.

To start setup from the command prompt, type

setup


Specifying the Number of Ports
SNA Remote Access Service	5 of 14

Installing SNA Remote Access Service

Specifying the Number of Ports

An SNA Remote Access Service port must be specified for each client or server connection that the computer will support. For example, to support one client and four server connections, five SNA Remote Access Service ports must be specified.

To specify the number of SNA Remote Access Service ports

1.	Start SNA Remote Access Service Setup, as described in the previous section.

The SNARAS Ports dialog appears.

2.	In the box marked Ports, type the number of ports you want to make available for SNA Remote Access Service connections.

3.	Choose the Continue button.

Setup copies the files needed by SNA Remote Access Service and opens the Network Settings dialog box.


Adding SNA Remote Access Service Ports
SNA Remote Access Service	6 of 14

Installing SNA Remote Access Service

Adding SNA Remote Access Service Ports

You must add and configure each SNA Remote Access Service port before it can be used by SNA Remote Access Service. This section describes how to add and configure each port.

To add and configure SNA Remote Access Service ports

1.	Complete the procedures in the previous sections.

The Network Settings dialog box appears.

2.	In the Installed Network Software list box, select Remote Access Service, then choose the Configure button.

The Remote Access Setup dialog appears.

3.	Choose the Add button.

The Add Port dialog appears.

4.	In the Port drop-down list box, select the port you want to configure. For example, to configure the first SNA Remote Access Service port, select RasSna1. Then choose the OK button.

The Configure Port dialog appears.

5.	Choose the Dial Out Only option or the Receive Calls Only option, depending on whether you want the port to be used by a RAS client to connect to a remote server, or to be used by the RAS server to accept a connection from a remote client. (Do not choose Dial Out And Receive Calls because the port will only be able to receive incoming requests.) Then choose the OK button.

6.	Repeat steps 3 through 5 for each additional SNA Remote Access Service port.

7.	When all SNA Remote Access Service ports have been added and configured, choose the Continue button in the Remote Access Setup dialog box, then choose the OK button in the Network Settings dialog box.

For these changes to take effect, you must restart your computer.


Configuring an SNA Remote Access Service Server
SNA Remote Access Service	7 of 14

Configuring an SNA Remote Access Service Server

This section describes the steps required to configure a server to accept requests from remote clients to connect over an SNA network. These steps include configuring RAS to enable specific users to connect via RAS, and configuring SNA Server to define the necessary LUs through which the connection is to be made.


Configuring RAS to Allow Remote Users to Connect
SNA Remote Access Service	8 of 14

Configuring an SNA Remote Access Service Server

Configuring RAS to Allow Remote Users to Connect

Before a server can accept connection requests from remote SNA Remote Access Service clients, each remote user must be given permission to “dial in.” For information about creating user accounts, see Windows NT Server System Guide.

To allow remote users to connect to the server

1.	Start the Remote Access Administrator utility by double-clicking the Remote Access Admin icon in the Remote Access Service program group.

2.	From the Users menu, choose Permissions.

The Remote Access Permissions dialog appears.

3.	For each user you want to be able to connect to the server, select the user name, then choose the Grant Dialin Permission To User check box.

4.	Choose the OK button.

Note

SNA Remote Access Service does not support the callback feature of RAS. Do not assign callback permissions to users who will connect to the server via SNA Remote Access Service.


Configuring SNA Server to Allow RAS Clients to Connect
SNA Remote Access Service	9 of 14

Configuring an SNA Remote Access Service Server

Configuring SNA Server to Allow RAS Clients to Connect

Before RAS clients can connect through SNA Remote Access Service, SNA Server must be configured to provide the following items for each client system that can connect via SNA Remote Access Service:

A peer incoming connection

A remote APPC LU for the client

In addition, each SNA Server must be configured with at least one local APPC LU for use by SNA Remote Access Service when communicating with a client. One local LU is required for each SNA RAS port to be used.

This section describes how to configure each of these elements.

Setting Up a Peer Incoming Connection

A connection defines a data communication path between two computers on an SNA network using a specific link service. The following steps describe how to set up a connection to permit a system running SNA Server to receive connection requests via SNA Remote Access Service from a remote computer running SNA Server.

To set up an SNA Server connection for SNA Remote Access Service

1.	Start SNA Server Admin by double-clicking the SNA Server Admin icon in the Microsoft SNA Server program group.

2.	Select the server on which to add the connection.

3.	From the Services menu, choose New Connection.

The Insert Connection dialog box appears.

4.	Under Connection, select the type of connection, then choose the OK button.

The Connection Properties dialog box appears.

5.	In the Connection Name box, type a name identifying the connection.

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

7.	From the Link Service drop-down list box, choose the link service that the connection will use to access the communications adapter.

8.	Under Remote End, select Peer System.

9.	Under Allowed Directions, clear the Outgoing Calls check box, and, if necessary, select (check) the Incoming Calls check box.

10.	To continue configuring an 802.2, SDLC, X.25, or Channel connection, choose the Setup button. Otherwise, skip to step 12.

The setup dialog box for the connection type appears.

11.	Supply the information required for the setup dialog for the connection type, then choose the OK button. For information about setting up a particular connection type, see Chapter 3, “Configuring Servers and Connections,” in Microsoft SNA Server Administration Guide.

12.	In the Connection Properties dialog box, choose the OK button.

Note

If you create an SNA Remote Access Service connection between a RAS client and a RAS server that are also connected by a LAN (for example, when testing a RAS connection over a token ring or Ethernet network), you must disable the bindings between the Remote Access Server service and the adapter to prevent RAS from attempting to insert the RAS client into the LAN.

Setting Up a Remote APPC LU on the Server

For each connection that is set up for use by SNA Remote Access Service, one remote APPC LU must be set up. This remote LU defines the local LU on the RAS client that will be used to connect to the server via SNA Remote Access Service. This section describes how to set up a remote APPC LU.

To set up a remote APPC LU for use by SNA Remote Access Service

1.	In SNA Server Admin, select the connection for which the remote APPC LU is to be added.

2.	From the Services menu, choose Assign LUs.

The Insert LU dialog box appears.

3.	Choose the OK button.

The New APPC Remote LU Properties dialog box appears.

4.	In the LU Alias box, type a name to identify the LU. To simplify administering the connection, use a name based on the name of the client system.

5.	In the Network Name box, type the network name of the client system.

6.	In the LU Name box, type the LU name of the local LU of the client system.

6.	Optionally, in the Comments box type a comment up to 25 characters long.

7.	Clear the Enable Automatic Partnering check box.

8.	Choose the OK button.

Setting up a Local APPC LU on the Server

SNA Remote Access Service also requires one local APPC LU for each SNA RAS port. The following procedure describes how to set up a local APPC LU for use by SNA Remote Access Service.

To set up the local APPC LU

1.	In SNA Server Admin, select the server for which to assign the LU.

2.	From the Services menu, choose Assign LUs.

The Insert LU dialog box appears.

3.	Select APPC [Local], then choose the OK button.

The New APPC LU Properties dialog appears.

4.	Under LU 6.2 Type, select Independent.

5.	In the LU Alias box, type an alias for the LU.

6.	If necessary, type the network name of the server in the Network Name box.

7.	In the LU Name box, type the name of the LU. This name identifies the LU on the network.

8.	Optionally, in the Comment box type a comment up to 25 characters long.

9.	Clear the Enable Automatic Partnering check box.

10.	To add partner remote LUs for the local LU, choose the Partners button.

The LU 6.2 Partner LUs dialog box appears.

11.	Choose the Add button.

The Add APPC LU Partner dialog appears.

12.	Select the partner LU.

13.	Select an appropriate mode. For remotely administering a domain, #INTER is suggested, although #BATCH might be more appropriate for file transfers or other functions that involve transmitting large amounts of data.

14.	Choose the OK button.

15.	Repeat steps 11 through 14 for each additional remote LU to be paired with the local LU. Every SNA Remote Access Service remote LU must be paired with the local LU.

16.	In the LU 6.2 Partner LUs dialog box, choose the Close button.

17.	In the APPC LU Properties dialog box, choose the OK button.


Configuring an SNA Remote Access Service Client
SNA Remote Access Service	10 of 14

Configuring an SNA Remote Access Service Client

This section describes the steps necessary to configure a system running SNA Server to connect to a remote RAS server over SNA. In addition to configuring SNA Server to create peer outgoing connections and to set up local and remote LUs, configuring an SNA Remote Access Service client requires configuring Remote Access Service to add phone book entries for each server to which the RAS client can connect. Only this last step is required to configure a Windows NT Workstation as an SNA Remote Access Service client.


Configuring SNA Server to Connect as a RAS Client via SNA Remote Access Service
SNA Remote Access Service	11 of 14

Configuring an SNA Remote Access Service Client

Configuring SNA Server to Connect as a RAS Client via SNA Remote Access Service

SNA Server must be configured in much the same way for the RAS client as for the RAS server to allow communication over SNA. That is, a connection must be defined for each RAS server to which the RAS client can connect, a remote LU (corresponding to the local LU on the RAS server) must be set up for each connection, and a local LU must be set up on the client system.

Setting Up a Peer Outgoing Connection

A RAS client must have a peer outgoing SNA connection defined for each RAS server to which it can connect.

Setting up connections on a RAS client is identical to the procedure for setting up connections on a RAS server, except that, in the Connection Properties dialog box, you must clear the Incoming Calls check box and select (check) the Outgoing Calls check box. For complete instructions for setting up an SNA Server connection, see “Setting Up a Peer Incoming Connection” earlier in this chapter.

Setting Up a Remote APPC LU on the Client

For each connection you must assign one remote APPC LU. The remote LU specifies the local APPC LU on the server through which the connection is to be made.

The procedure for setting up a remote APPC LU on the client is identical to the procedure for performing the same task on the server. When doing so, remember that the fully qualified LU name (that is, the combination network name and LU name) of the remote LU must match exactly the fully qualified LU name of the local APPC LU on the server for which the connection has been established. The LU alias of each remote LU should be based upon the name of the associated server to simplify administering the connection.

For complete instructions for setting up a remote LU, see “Setting Up a Remote APPC LU on the Server” earlier in this chapter.

Setting Up a Local APPC LU on the Client

SNA Remote Access Service requires one local APPC LU one the client to be able to connect to a remote RAS server. The LU alias of the local LU must be SNARASLU. Setting up a local LU on the client requires the same procedures as setting up a local LU on a server. When specifying the network name and LU name of the remote LU, make sure the fully qualified LU name of the local LU matches exactly the fully qualified LU name of a remote LU on the server to which the client will connect using that local LU.

For complete instructions for setting up a local LU, see “Setting Up a Local APPC LU on the Server” earlier in this chapter.


Configuring RAS to Allow the Client to Connect to Remote Servers
SNA Remote Access Service	12 of 14

Configuring an SNA Remote Access Service Client

Configuring RAS to Allow the Client to Connect to Remote Servers

The final step in setting up a system to allow it to connect to a remote server using SNA Remote Access Service is to create a phone book entry for each connection. (If you have configured more than one port for use by SNA Remote Access Service, you can create an additional set of phone book entries associating the same connection with the additional ports.) The following procedure creates a phone book entry for connecting a client using SNA Remote Access Service.

To create a phone book entry for SNA Remote Access Service

1.	Start the Remote Access client utility by double-clicking the Remote Access icon in the Remote Access Service program group.

If you have not yet created any phone book entries, Remote Access informs you that the phone book is empty. Choose the OK button.

If the phone book already contains at least one entry, choose the Add button.

The Add Phone Book Entry dialog box appears.

2.	In the Entry Name box, type a name for the entry. Although the name need not match any network name, the entry name should reflect the name of the server that you will connect to using this entry.

3.	Choose the ellipsis (...) button next to the Phone Number box.

The Phone Numbers for Entry Name dialog box appears.

4.	In the New Phone Number box, type the LU alias of the client remote LU through which the connection is to be made, followed by a space and the connection mode. For example, to define a phone book entry for a remote LU named RASSERV using #INTER mode, type RASSERV #INTER.

5.	Choose the Add button.

6.	Repeat steps 4 and 5 for each additional remote LU assigned to the connection.

7.	When you have finished adding phone numbers, choose the OK button to close the Phone Numbers for Entry Name dialog box.

8.	Optionally, in the Description box type a comment.

9.	Clear the Authenticate Using Current User Name and Password check box.

10.	Choose the Advanced button.

11.	From the Port drop-down list box, select the SNA Remote Access Service port to be used for the connection.

12.	Choose the OK button.


Connecting to a Remote Server Using SNA Remote Access Service
SNA Remote Access Service	13 of 14

Connecting to a Remote Server Using SNA Remote Access Service

You connect a RAS client to a remote RAS server when you want to be able to access the resources on the remote server and, optionally, on the  LAN of the remote server. The following procedure connects a RAS client to a RAS server using SNA Remote Access Service.

To connect a RAS client to a RAS server

1.	Start the Remote Access client utility by double-clicking the Remote Access icon in the Remote Access Service program group.

2.	Double-click the entry for the server you want to connect to.

The Authentication dialog box appears.

3.	In the User Name box, type the user name of a user account on the remote server or on the domain to which the server belongs. The administrator of the server or domain must have given permission for the account to access the server using RAS. For more information, see “Configuring RAS to Allow Remote Users to Connect” earlier in this chapter.

4.	In the Password box, type the password of the user account. Windows NT displays each character as an asterisk (*).

5.	In the Domain box, type the server or domain where the user account is located.

6.	Choose the OK button.

Once your computer is connected to the remote RAS server, you can access resources on the server and, if allowed by the server administrator, on the network(s) to which the server belongs.

Before establishing a connection, you can use the rasping utility to verify that an SNA Remote Access Service connection is available. Rasping is an SNA Server APPC application that runs on Windows NT. Rasping requires SNA Remote Access Service on the server, but the potential client does not have to have RAS installed to run rasping. SNA Remote Access Service Setup installs RASPING.EXE in the SNA\SYSTEM directory. If you want to run rasping before installing SNA Remote Access Service, you can copy RASPING.EXE from the SNA Server CD.

The following shows the syntax for rasping:

rasping partner_LU_alias [mode] [/t] [/q]

The partner_LU_alias parameter specifies the local alias of the remote APPC LU for which you want to test the availability of an SNA Remote Access Service connection. This alias must be paired with a local APPC LU named SNARASLU.

The mode parameter specifies an existing mode for the connection. If the mode parameter is not supplied, the connection is made using the #INTER mode.

The /t option increases the timeout period to 60 seconds from the default 15 seconds. The /q option specifieS quiet mode, which suppresses all console output.

When you use rasping without the /q option, rasping displays information similar to the following when testing for an available connection:

RasPing attempting to locate RAS server using RASSERVLU / #INTER

In this example, rasping was testing a potential connection BY using a remote APPC LU with the alias RASSERVLU (using #INTER mode).

If the test is successful, rasping displays information similar to the following:

Response from server SNAMPC running SNARAS version 1.0

Rasping sets an errorlevel of zero if it successfully establishes communication with an SNA Remote Access Service server. Otherwise, it sets an errorlevel greater than zero. You can take advantage of this in batch files to perform unattended operations (scheduled using the at command, for example) using SNA Remote Access Service. The following example shows how to use rasping and rasdial (a component of Windows NT Remote Access Service) to set up a RAS connection and then copy a file using that connection.

@echo off

echo /*****************************************************************/

echo  This batch file tests for SNARAS connectivity to \\RASSERV,

echo  then dials the server and retrieves the latest update.txt file

echo /*****************************************************************/

pause

:test

rasping  RASSERV  #INTER

if  errorlevel  1  goto  fail

:good

rasdial  RASSERVPHONE

copy  \\RASSERV\public\update.txt

rasdial  RASSERVPHONE  /disconnect

goto exit

:fail

echo ERROR - failed to connect to RASSERV

:exit

For more information about using the Windows NT Remote Access Service rasdial utility, see Remote Access Service Help.


Removing SNA Remote Access Service Software
SNA Remote Access Service	14 of 14

Removing SNA Remote Access Service Software

Removing SNA Remote Access Service software from a computer requires that you stop SNA Server (if you are removing SNA Remote Access Service from an SNA Server), stop RAS, and then restart the computer. Be sure the computer is ready to be restarted before beginning the removal procedure.

To remove SNA Remote Access Service software

1.	Disconnect any outgoing RAS connection to a remote server:

1.	If necessary, start the Remote Access utility by double-clicking the Remote Access icon in the Remote Access Service program group.

2.	Select the phone book entry for the active connection.

3.	Choose the Hang Up button.

4.	From the Options menu, choose the Exit command.

2.	Disconnect any incoming RAS connection to a remote client:

1.	Start Remote Access Administrator by double-clicking the Remote Access Admin icon in the Remote Access Service program group.

2.	Select the server from which you are removing the SNA Remote Access Service software.

3.	From the Users menu, choose the Active Users command.

The Remote Access Users dialog box appears.

4.	Select each user and then choose the Disconnect User button to disconnect the user.

5.	When all users have been disconnected, choose the OK button to close the Remote Access Users dialog box.

6.	From the Server menu, choose the Exit command.

3.	Stop SNA Server (if you are removing SNA Remote Access Service software from an SNA Server):

1.	Start SNA Server Admin by double-clicking the SNA Server Admin icon in the Microsoft SNA Server program group.

2.	Select the server to be stopped.

3.	From the Services menu, choose the Stop Service command.

A message box appears, asking you to confirm that you want to stop the server.

4.	Choose the OK button.

5.	When the server status is Inactive, close SNA Server Admin by choosing the Exit command from the File menu.

4.	Stop the Remote Access Service:

1.	Start Control Panel by double-clicking the Control Panel icon in the Main program group.

2.	Double-click the Services icon.

The Services dialog appears.

3.	Select Remote Access Server.

4.	Choose the Stop button.

5.	When the service has stopped, choose the Close button.

5.	Remove all SNA Remote Access Service ports:

1.	In Control Panel, double-click the Network icon.

2.	In the Installed Network Software list box, select Remote Access Service.

3.	Choose the Configure button.

The Remote Access Setup dialog box appears.

4.	For each SNA Remote Access Service port, select the port and choose the Remove button.

5.	To close the Remote Access Setup dialog box, choose the Continue button.

6.	To close the Network Settings dialog box, choose the OK button.

A message box appears suggesting that you restart your system.

7.	Choose the Don’t Restart Now button.

8.	To close Control Panel, choose the Exit command from the Settings menu.

6.	Remove the SNA Remote Access Service software:

1.	Start the SNA Remote Access Service setup program as described in “Starting the SNA Remote Access Service Setup Program” earlier in this chapter.

A message appears, asking you to confirm that you want to remove the SNA Remote Access Service.

2.	Choose the OK button.

A message appears, suggesting that you restart the system.

3.	Choose OK to restart the system.

This procedure does not remove connections or LUs from the SNA Server configuration, nor does it remove phone book entries from the Remote Access client configuration. To remove these, use the SNA Admin and RAS Administrator utilities.


ODBC/DRDA Drivers
Chapter 9	1 of 13

ODBC/DRDA Drivers

A need faced by many organizations is to make data stored in IBM host databases available to Windows- and Windows NT–based applications. Many such applications use the Open Database Connectivity (ODBS) programming interface to access local and server-based databases, while distributed databases on IBM hosts are usually managed through the Distributed Relational Database Architecture (DRDA) protocol defined by IBM.

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

DB2 [image] for MVS

SQL/DS{bmc tm.bmp} for VM and VSE

DB2/400 for OS/400

Figure 7.1 shows how a Windows or Windows NT application works with SNA Server to access a remote database.

Figure 7.1 Application Access to Remote Databases

As shown in figure 7.2, the ODBC/DRDA driver (shaded in gray) accepts SQL requests from the client application, translates them to DRDA commands and transmits them via SNA Server to the IBM host. The host processes the DRDA commands and returns the results, again via SNA Server, to the ODBC/DRDA driver on the client system. The driver converts the returned DRDA information to SQL data, which the driver then forwards to the client application.

Figure 7.2 ODBC/DRDA Driver Role

The drivers are installed as an integral part of the SNA Server client software.

This chapter provides the following information about the ODBC/DRDA drivers:

How to add and set up a data source

How to connect to a database

Supported applications and programming environments

Supported ODBC functions and data types

System messages

International considerations


Adding and Setting Up a Data Source
ODBC/DRDA Drivers	2 of 13

Adding and Setting Up a Data Source

In order to access a host-based database, the user must specify the database as an ODBC data source by using the ODBC Administrator. Typically, an ODBC-enabled application provides a method for accessing the ODBC Administrator, which is also available as a Program Manager program item or Control Panel option, depending on the operating system and the ODBC driver(s) that have been installed.

To add and set up a data source

1.	Start ODBC Administrator.

The Data Sources dialog box appears.

Figure X.1 Data Sources Dialog Box

2.	To add a new data source, choose the Add button.

The Add Data Source dialog box appears.

3.	Select StarSQL and choose the OK button.

The StarSQL Data Source Setup dialog box appears.

Figure X.2 StarSQL Data Source Setup Dialog Box

To set up the data source, perform the following procedure.

To configure an existing data source

1.	Start ODBC Administrator.

The Data Sources dialog box (shown in figure X.1) appears.

2.	Select the data source you want to configure, then choose the Setup button.

The StarSQL Data Source Setup dialog box (shown in figure X.2) appears.

In the StarSQL Data Source Setup box, supply information as follows:

Name

Type a name for the data source. Your application uses this name to find the appropriate driver for the data connection. The name can contain up to 32 characters.

Description

Type a description for the data source.

Database Server Name

Type the name of the relational database (RDB).

SQL Catalog Qualifier

Type the name of the SQL catalog qualifier. If you do not enter a value, the ODBC/DRDA driver uses a default value, depending on the type of host database. For a DB2/400 database, the default value is your user ID. For a DB2 database, the default value is SYSIBM.

SQL Package Collection

Type the name of the SQL package collection. If you do not enter a value, the ODBC/DRDA driver uses your user ID.

Read-Only

Choose this check box if you do not want to change information in the database.

If you are adding a new data source, you must set up the connection. If you are configuring an existing data source, you can change the connection setup.

To set up an ODBC/DRDA driver connection

1.	In the StarSQL Data Source Setup dialog box (shown in Figure X.2), choose the Setup button.

The StarSQL Connection Setup dialog box appears.

2.	In the Local LU box, enter the name of a local LU. The name must identify an existing local LU.

3.	In the Remote LU box, enter the name of a remote LU. The name must identify an exsiting LU.

4.	In the Mode Name box, enter a valid mode name. The default mode name is QPCSUPP.

5.	To close the StarSQL Data Source Setup dialog box and accept changes, choose the OK button. To close the dialog box without accepting the changes, choose the Cancel button.


Connecting to a Host Database
ODBC/DRDA Drivers	3 of 13

Connecting to a Host Database

The actual method you use to select a data source and initiate a connection to a database on an IBM host depends on the application you are using. For example, to select a data source using Microsoft Query (provided with such applications as Microsoft Access and Microsoft Excel), choose the New Query or Open Query command from the File menu.

When you select a StarSQL data source, the StarSQL connection dialog box may appear, depending on host security.

To connect to the data source, enter your user ID and password. To change settings for the data source, choose the Options button. When you are finished entering the information, choose the Connect button to establish the connection, or choose the Cancel button if you do not want to connect to the host database.


Supported Applications and Programming Environments
ODBC/DRDA Drivers	4 of 13

Supported Applications and Programming Environments

SNA Server ODBC/DRDA drivers support virtually all ODBC-enabled applications and programming environments. Examples of these include:

Microsoft Access (version 2.0 and later)

Microsoft Excel (version 4.0 and later)

Microsoft FoxPro

Microsoft Visual Basic [image] (version 3.0 and later)

Microsoft Word (version 6.0 and later)

In addition to these, many other applications support the ODBC programming interface and so can access host-based databases through the ODBC/DRDA drivers.


Supported ODBC Functions and Data Types
ODBC/DRDA Drivers	5 of 13

Supported ODBC Functions and Data Types

This section provides general information about the ODBC interface and lists the Open Database Connectivity (ODBC) functions and data types supported by the SNA Server ODBC/DRDA drivers.


About ODBC
ODBC/DRDA Drivers	6 of 13

Supported ODBC Functions and Data Types

About ODBC

ODBC is a call-level interface for applications that accesses multiple databases by using a single set of function calls, providing a standard database access through a common client-side interface.

Applications interact with the ODBC Driver Manager, which is a Windows Dynamic-Link Library (DLL). The Driver Manager (ODBC.DLL) interprets the application calls to the database using the ODBC/DRDA driver included with SNA Server client software. The Driver Manager loads and unloads the driver, performs status checking, and manages multiple connections between applications and data sources. The ODBC/DRDA driver manages the data source and processes the ODBC calls and SQL statements. The driver interprets the calls and issues the appropriate DRDA commands.

ODBC supports transaction commit and rollback, asynchronous processing, canceled queries, primary and foreign keys, and four levels of transaction isolation.

The ODBC/DRDA driver also supports the ability to pass SQL strings to the remote database without translation or modification. You can use native SQL features specific to the IBM databases you access as well as the ODBC extensions.


ODBC Functions
ODBC/DRDA Drivers	7 of 13

Supported ODBC Functions and Data Types

ODBC Functions

The ODBC/DRDA driver supports the following ODBC functions.

Core	Description

SQLAllocConnect	Allocates a database connection handle

SQLAllocEnv	Allocates an environment handle

SQLAllocStmt	Allocates an SQL statement handle

SQLBindCol	Binds a column to an application variable

SQLCancel	Cancels the current asynchronous function

SQLColAttributes	Returns descriptors for a result

SQLConnect	Connects to a data source

SQLDescribeCol	Describes column characteristics

SQLDisconnect	Disconnects from a data source

SQLError	Returns error and state information

SQLExecDirect	Executes statements

SQLExecute	Executes a prepared SQL statement

SQLFetch	Returns a result row

SQLFreeConnect	Releases the connection handle

SQLFreeEnv	Releases the environment handle

SQLFreeStmt	Releases a statement handle

SQLGetCursorName	Returns the cursor name for a statement

SQLNumResultsCol	Returns the number of columns in a result set

SQLPrepare	Prepares an SQL request for execution

SQLRowCount	Returns the number of rows affected by UPDATE, DELETE, and INSERT statements

SQLSetCursorName	Associates a cursor name with an SQL statement handle

SQLTransact	Commits or rolls back a transaction

Level 1	Description

SQLBindParameter	Binds a buffer to a parameter marker in an SQL statement

SQLColumns	Returns the list of column names in specfied tables

SQLDriverConnect	Extends connection options and driver prompts

SQLGetConnectOption	Returns the value of a connection option

SQLGetData	Returns result data for a single unbound column in the current row

SQLGetFunctions	Describes functions supported by StarSQL driver

SQLGetInfo	Returns general information about the driver and data source associated with a connection handle

SQLGetTypeInfo	Returns information about data types supported by the data source

SQLParamData	Provides parameter data at run time

SQLPutData	Sends data for a parameter at run time

SQLGetStmtOption	Returns the value of a statement option

SQLSetConnectOption	Sets connection options

SQLSetStmtOption	Sets SQL statement options

SQLSpecialColumns	Returns information about the optimal set of columns that uniquely identifies a row in a specified table and about columns that are automatically updated when any value in the row is updated by a transaction

SQLStatistics	Returns statistics about a table and the indices associated with the table.

SQLTables	Returns the list of table names stored in a specific data source

Level Two	Description

SQLDataSources	Lists data source names


ODBC Data Types
ODBC/DRDA Drivers	8 of 13

Supported ODBC Functions and Data Types

ODBC Data Types

The ODBC/DRDA driver supports the following ODBC data types.

ODBC SQL Data Type		Grammar
SQL_CHAR		Minimum
SQL_DECIMAL		Core
SQL_DOUBLE		Core
SQL_FLOAT		Core
SQL_INTEGER		Core
SQL_NUMERIC		Core
SQL_REAL		Core
SQL_SMALLINT		Core
SQL_VARCHAR		Core
SQL_BINARY		Extended
SQL_DATE		Extended
SQL_LONGVARBINARY		Extended
SQL_LONGVARCHAR		Extended
SQL_TIME		Extended
SQL_TIMESTAMP		Extended
SQL_VARBINARY		Extended


System Messages
ODBC/DRDA Drivers	9 of 13

System Messages

This section discusses the formats of system messages that the ODBC/DRDA driver returns. The driver provides error messages from its operations as well as host error messages. Your application may show some or all of the error message information the driver provides.

Applications you write, using Microsoft Visual Basic or other application development systems or languages, can access the error messages. These messages contain host information that is useful for diagnosing SQL errors or interpreting SQL statement results.

The ODBC/DRDA driver returns two kinds of messages, those that the driver generates locally, and those generated by the host database server. Also, two kinds of messages occur: informational messages and error messages.

The ODBC/DRDA driver returns SQL_SUCCESS_WITH_INFO for an informational message and SQL_ERROR for an error message. In either case, the application can call the ODBC function SQLError to obtain more specific information.


Using SQLError
ODBC/DRDA Drivers	10 of 13

System Messages

Using SQLError

When the application calls the SQLError function, the ODBC/DRDA driver returns an error message string along with an SQLSTATE string, a native error code, and a text message.

SQLSTATE

The SQLSTATE is a five-character string that the ODBC/DRDA driver returns from the following three sources:

ODBC 2.0 return codes from the ODBC interface

Host SQLSTATE return codes for errors on the host side, which may not match the ODBC SQLSTATE return codes

ODBC/DRDA driver SQLSTATE return codes, which follow the SQL92 standard

SQLCODE

The native error code that the ODBC/DRDA driver returns is the SQLCODE reported by the host. If the error occurred locally, the error code is zero.

If you are using DB2/400 or DB2, the SQLCODE return message provides more information for these hosts.

The ODBC/DRDA driver conforms to the ODBC driver specifications by prefixing this string with information that identifies the vendor:

[Vendor][ODBC Driver] message text

For an error from a remote host, the ODBC/DRDA driver also inserts the host database name, such as:

[Vendor][ODBC Driver][DB2]message text

or

[Vendor][ODBC Driver][DB2/400]message text

For local errors, the ODBC/DRDA driver returns the value zero. For remote host errors, the ODBC/DRDA driver returns a SQLCODE from the host if the host returns an error, or zero if not.

The message text for local errors is from the messages supplied by the ODBC/DRDA driver. The message text for remote errors is from the host.


International Considerations
ODBC/DRDA Drivers	11 of 13

International Considerations

This section provides special instructions for using the ODBC/DRDA driver in non-English environments.


Using the ODBC/DRDA Driver in Non-English Environments
ODBC/DRDA Drivers	12 of 13

International Considerations

Using the ODBC/DRDA Driver in Non-English Environments

The ODBC/DRDA driver includes conversion tables that automatically translate between the ANSI code pages and the host code pages, if the host supports code pages.

DRDA uses the capabilities of other architectures to provide the full range of functionality needed for a distributed database. In the area of character representation, Character Data Representation Architecture (CDRA) handles many of the complex issues that arise due to the various representations of character data throughout the world. Like DRDA, CDRA is a part of SAA, the IBM System Application Architecture.

CDRA uses the Coded Character Set Identifier (CCSID) to represent a character set, a code page, an encoding scheme, and additional coding-related information. CDRA uses the 16-bit CCSID to communicate this information about character data transferred over a DRDA connection. By using this information, the ODBC/DRDA driver performs the necessary conversions between host-based data and data represented on your PC.

CDRA has organized the different character sets into groups. Group 1 covers the Latin Alphabet Number 1 for North and South America, Western Europe, Australia, New Zealand, and Hong Kong. The ODBC/DRDA driver supports all SAA CCSIDs for this group.

The ODBC/DRDA driver supports translation to and from the following CCSIDs:

CCSID	Description

37	CECP: USA, Canada, Netherlands, Portugal, Brazil, Australia, New Zealand

273	CECP: Austria, Germany

277	CECP: Denmark, Norway

278	CECP: Finland, Sweden

280	CECP: Italy

284	CECP: Spain, Latin America (Spanish)

285	CECP: United Kingdom

297	CECP: France

500	CECP: Belgium, Switzerland, International Latin-1

871	CECP: Iceland

850	CECP: PCData-190: Latin Alphabet Number 1

819	ISO 8859-1

If the ODBC/DRDA driver receives an unknown CCSID from the host, your application returns the following message:

Unable to convert character data using CCSID nnnn.

The ODBC/DRDA driver does not contain support for Group 1A, which covers Greek, Turkish, Cyrillic, Arabic scripts, and Hebrew; or Group 2, which covers double-byte coding for Japan, Korea, the People’s Republic of China, the Republic of China, and Thailand.

The ODBC/DRDA driver does not support multibyte character sets or non-Latin character sets.


CCSID Selection for Server-Bound Data in the ODBC/DRDA Driver
ODBC/DRDA Drivers	13 of 13

International Considerations

CCSID Selection for Server-Bound Data in the ODBC/DRDA Driver

The ODBC/DRDA driver translates character data between the local Windows character set and the host character set. The host character set is identified by a CCSID(). For data received from the host, the host chooses the CCSID it uses for character data. For data sent to the host, the ODBC/DRDA driver must choose a CCSID to use. When the data source connects to the host, the host reports the CCSID that it will use. The ODBC/DRDA driver automatically matches the CCSID chosen by the host; therefore no manual configuration is needed for the ODBC/DRDA driver data source.

For example, if the CCSID used by the host is 280 (CECP Italy), the ODBC/DRDA driver automatically uses CCSID 280 when translating from the local Windows character set for host-bound SQL data on that connection.

The CCSID used by the ODBC/DRDA driver for host-bound data is automatically configured per connection, and is not necessarily the same on each connection even to the same host using the same data source. The CCSID used depends on the CCSID selected by the host for the given connection. (Configuration options on the host may allow the CCSID to be overridden for a specific user ID, for example.)


Introduction to AFTP
Chapter 10	1 of 19

Introduction to AFTP

Note

If you are already familiar with APPC and want to start using AFTP, please skip to the “Using the AFTP Program” and “AFTP Program Command Reference” sections in the next chapter.

The APPC File Transfer Protocol (AFTP) client is a transaction program that provides file manipulation and transfer services to application programs and users in both traditional SNA networks and peer APPN networks. The AFTP program runs on advanced program-to-program communications (APPC) sessions. With AFTP, you can copy text and binary files between your computer and any computer running the AFTP server.

AFTP allows you to manage files on a server computer. You can copy files to or from the AFTP server, rename server files, and even erase server files.

Using AFTP, you can distribute files for:

Use on different platforms

You can share files among different platforms that support AFTP if the format of your files is supported by the operating system on each platform. Text files are supported by many different operating systems, so text files can often be shared among different platforms. Binary files can only be shared if the operating system on each platform supports a common binary format, and your binary files conform to that format.

Storage on different platforms

You can store files on different platforms that support AFTP if the files can be represented as a binary stream of bytes, even if the computer's operating system cannot use the file. For example, you can transfer a DOS program to an AIX or mainframe computer for storage, even though the operating systems cannot use DOS programs. You can then redistribute the file to other DOS computers, where the file can again be used.

If you want to store files that have unique file system encodings, you must convert the files into a new file that can be treated as a binary stream. You can convert your files using an archiving program such as COPYFILE with the PACK option on VM.

To simplify the task of remembering your file names, AFTP supports a directory file organization scheme on all platforms. Commands are provided to create and remove directories on the AFTP server. Commands are also provided to list directory contents on either the AFTP client or AFTP server, and to identify the directory in which you wish to work (current directory).

AFTP provides the AFTP program, opened by the aftp command. Once you have opened the AFTP program you can use the full set of AFTP commands to manipulate files and directories. Only AFTP commands are accepted in this environment. A prompt on your display reminds you that you are in the AFTP program.

See “AFTP Program Command Reference” in the next chapter for information about the commands available.

Regarding the AFTP information presented in this book, it is assumed that you know how to perform basic APPC configuration tasks for the operating system platform you are using.


An APPC Primer
Introduction to AFTP 	2 of 19

An APPC Primer

This section briefly introduces some of the terminology and concepts of advanced program-to-program communication (APPC). For more details on APPC, check the Microsoft SNA Server documentation.


APPC
Introduction to AFTP 	3 of 19

An APPC Primer

APPC

APPC is software that enables high-speed communications between programs on different computers — from portables and workstations to midrange and host computers. APPC software is available for many different IBM and non-IBM operating systems, either as part of the operating system or as a separate software package.

APPC serves as a translator between application programs and the network. When an application on your computer passes information to the APPC software, APPC translates the information and passes it to a network interface, such as a local area network (LAN) adapter card. The information travels across the network to another computer, where the APPC software receives the information from the network interface. APPC translates the information back into its original format and passes it to the corresponding partner application.


Transaction Programs And Conversations
Introduction to AFTP 	4 of 19

An APPC Primer

Transaction Programs and Conversations

The part of an application that initiates or responds to APPC communications is called a transaction program (TP). A transaction program on your workstation is not an entire, stand-alone program. Instead, it is the part of the program that handles transactions (exchanges of data) with another program.

When people talk with each other, they are having a conversation. Likewise, the communication between two transaction programs is called a conversation. The two programs having the conversation are said to be partners.

A conversation between two programs is similar to conversation between two people. When you talk with another person, you follow unwritten rules that govern how you begin and end the conversation, take turns speaking, and exchange information. Similarly, APPC is called a protocol because it provides the rules that govern how conversations between transaction programs start and stop, which program speaks first, and how data is exchanged.

A program in your computer can have several conversations active at one time, with the same transaction program or with different transaction programs.


Logical Units And Sessions
Introduction to AFTP 	5 of 19

An APPC Primer

Logical Units And Sessions

When two people in different buildings want to talk to each other, they must use their telephones. Similarly, transaction programs in different computers cannot talk directly to each other. Instead, they converse over sessions between two logical units.

A logical unit (LU) is APPC software that serves as an interface or translator between a transaction program and the network. A logical unit manages the exchange of data between transaction programs.

An LU is located on your computer. A partner LU is located on a partner computer.

Before a transaction program can start a conversation with a partner transaction program, APPC must establish a session that connects the local LU and the partner LU.

There is a one-to-one relationship between a conversation and a session. A session can support only one conversation at a time. However, as soon as that conversation ends, another conversation can use the session. So, compared to conversations, sessions are long-lived connections.


Mode
Introduction to AFTP 	6 of 19

An APPC Primer

Mode

A mode is a set of parameters that defines the characteristics of a session between two LUs. There are four modes predefined that can be used by most applications. (There is one additional mode defined, SNASVCMG, but this mode is not used directly by applications.) The SC suffix in the mode name means that the definitions require a secure transmission route.

#INTER — for interactive jobs; minimal delay

#BATCH — for batch jobs; delay is acceptable, but high bandwidth may be required

#INTERSC — for interactive jobs with security

#BATCHSC — for batch jobs with security

Note

The different characteristics of the four modes are only relevant if the sessions are going across an APPN network, where a choice of routes is possible.

By default used by AFTP clients is the #BATCH mode.

Contact the person who installed your APPC software if you need information about the supported mode values, or about how your system is configured to respond if an unsupported value is used.


CPI-C Side Information
Introduction to AFTP 	7 of 19

An APPC Primer

CPI-C Side Information

CPI-C, Common Programming Interface Communications, provides a consistent application programming interface for network applications.

CPI-C programming provides a mechanism, called side information, which associates a set of parameters with a specified symbolic destination name. The CPI-C program then uses the symbolic destination name to initialize a conversation. This information includes:

CPI-C symbolic destination name

The name used to refer to the CPI-C side information entry

TP name

The name used to identify which program to start on the partner computer

LU

The name of the partner LU

mode name

The characteristics associated with the session between the LUs

For more information on CPI-C configuration and symbolic destination names, see “Configuring Properties for CPI-C” in Chapter 6 of the Microsoft SNA Server Administration Guide.


Clients And Servers
Introduction to AFTP 	8 of 19

An APPC Primer

Clients And Servers

Clients and servers are special transaction programs that interact with each other. The client program provides the user interface. The server program provides the services requested by the user. Typically a server program is a central resource accessed by many users.


APPC Security
Introduction to AFTP 	9 of 19

An APPC Primer

APPC Security

Owners of APPC server transaction programs may want to allow only a limited set of users to start the program. APPC provides a mechanism by which the client transaction program identifies its user to the server system. This is called APPC conversation security.

APPC defines three levels of security for client programs:

None

The client system sends no security information (user ID or password).

Same

APPC tries to determine a user ID for the client program. If the server system requires a password and the client system permits APPC to retrieve one for the user ID, APPC will also send the password to the server system. If no user ID is available, or if the server requires a password but the client system does not allow APPC to retrieve a password, then no security information is sent to the server. (This is sometimes called “downgraded to security NONE.”)

Program

The client transaction program will override any security information the local system may provide. The client program must supply both a user ID and a password. CPI-C programs may get the user ID and password from one of two sources:

Prompting the user to enter the information

Checking the CPI-C side information

Note

Not all systems allow this option.

If the client program uses security=same or security=program, APPC on the server must check the user ID and password regardless of the server transaction's security requirements. This requirement can cause some unexpected problems.


Specifying Destinations in the AFTP Program
Introduction to AFTP 	10 of 19

Specifying Destinations in the AFTP Program

Several of the commands in the AFTP program require you to specify the destination address of the server you want to access. The destination address you specify may be in one of the following formats:

Fully qualified LU name

Every resource in the SNA network has a unique address in the format “NETID.LUNAME”. This network address is known as the fully qualified LU name. This address is defined when the resource is added to the network.

Locally defined LU alias or CPI-C symbolic destination name

You can associate easy-to-remember aliases with the fully qualified LU names (network addresses) that you access most often. The methods used vary by operating system, but usually involve either locally defined LU aliases or CPI-C symbolic destination names.

The table of personal aliases you create is stored on your system and is accessible only by you.

Each of your personally defined aliases (locally defined LU aliases and CPI-C symbolic destination names) must be unique.

Note

On host systems, a single LU can represent multiple users. On those systems, you must also specify a user ID and password. See “Specifying Security in the AFTP Program” for more information.


Specifying Security In the AFTP Program
Introduction to AFTP 	11 of 19

Specifying Security In the AFTP Program

The AFTP open command allows you to explicitly specify the conversation security if the default security level fails.

For a brief description of security levels, see “APPC Security.”

The security requirements for a transaction program may depend on:

The client’s operating system and its configuration

The server’s operating system and its configuration

The configuration of server software

This section describes the typical security processing for the AFTP program. The actual security requirements on your system may be different because of the configuration of the systems involved.


AFTP Security
Introduction to AFTP 	12 of 19

Specifying Security In the AFTP Program

AFTP Security

In AFTP, security is checked when a client requests a connection to the AFTP server.

AFTP Server

If the AFTP server is on VM, the client must provide a user ID and password. The AFTP server cannot be a VM shared user ID.

Security requirements for other platforms depend on the configuration of those systems.

AFTP Client

With the AFTP client (the AFTP program ), the connection is requested by specifying a destination on the aftp command or by issuing the open command.

Before attempting to make the connection, the AFTP client will prompt you for a user ID and password. This user ID is used by the AFTP server for file permissions (different users have different permissions), and it is used for APPC conversation security.

A user who enters the user ID Anonymous is not prompted for a password. No APPC conversation security is specified on the ALLOCATE flowing from the AFTP client, and the AFTP server treats this as “no user ID.”

If the user just presses the ENTER key when prompted for a user ID, then one of two things can happen. If the user has issued an open command to a remote LU, then this is treated as a user ID of Anonymous. If the user has issued an open command to a symbolic destination name, then whatever user ID and password is configured for the symbolic destination name is used (if none is configured, this is treated as a user ID of Anonymous).

A user who enters a user ID other than Anonymous is also prompted for a password. This user ID and password flow on the ALLOCATE to the AFTP server. If the AFTP server is configured to use APPC conversation security, then matching is done to see whether the AFTP server can be invoked for this user ID. Also, the user ID is used by the AFTP server to allow file permissions.

Note

The password is not checked by the AFTP server, but by the underlying SNA stack at the AFTP server when the conversation security is checked.

AFTP Security Summary

The following table summarizes the security restrictions for AFTP:

Platform	Component	Requirements	Restrictions
VM	AFTP server	user ID and password	user ID and password must be uppercase cannot be shared user ID
VM	AFTP client		access from shared user ID is limited
Default Security Processing

The default security level used for the AFTP open command depends on the way you specify the destination value on the command and what is coded in your CPI-C side information file:

If destination is a symbolic destination name

The default security is the security level specified in the CPI-C side information file for that symbolic destination name.

If no security is specified, security=same will be used.

If destination is a fully qualified LU name

If the CPI-C side information file contains a symbolic destination definition for the server transaction program name (AFTPD), use the security defined on that definition.

If you are already logged on with a user ID and password, use security=same.

Otherwise, use security=none.


Understanding AFTP Basic Concepts
Introduction to AFTP 	13 of 19

Understanding AFTP Basic Concepts

Before you start using the AFTP program, you need to understand a few basic concepts.


File Transfer Types
Introduction to AFTP 	14 of 19

Understanding AFTP Basic Concepts

File Transfer Types

The AFTP program supports both text and binary file transfers.

In a binary file transfer, the file is treated as a stream of bytes. None of the characters within the file are interpreted. Executable programs and other nontext files are usually transferred as binary files.

In an ASCII file transfer, files are transferred using ASCII characters, and the text file format is preserved. If either the source or destination is an EBCDIC computer (for example, an IBM host system), AFTP on the EBCDIC computer will do ASCII-to-EBCDIC translation when it receives a file, and EBCDIC-to-ASCII translation when it sends a file.

Note

Text files on some systems contain an end-of-file (EOF) character, which is the last character in the file. When AFTP transfers a text file containing an EOF character, AFTP does not send the EOF character, so the file appears to be one character smaller when it is received by the server. If the file is transferred in binary mode, AFTP sends the EOF character.

See “Setting File Transfer Defaults” for information about setting default transfer types based on filename patterns.


Special File Structure
Introduction to AFTP 	15 of 19

Understanding AFTP Basic Concepts

Special File Structure

If the file you want to transfer has special file structure based on record format and record length, you might be limited in your ability to transfer that file.

If you want to send the file to a system that supports the record formats and record length of the file, use the recfm and lrecl commands first to ensure the file is correctly transferred.

If you send the file to a system that does not maintain the record format and length, you may lose that critical information and not be able to restore it when you receive the file back on the client.

Note

You might be able to use an archiving tool to convert the file into a format that can be transferred to other platforms. When you want to use the file again on the original platform, use the archive tool to restore the file to its original format.


Working With AFTP Directories
Introduction to AFTP 	16 of 19

Understanding AFTP Basic Concepts

Working With AFTP Directories

In AFTP, directories represent the structures used to subset a file system into multiple portions. An AFTP directory can contain one or more files. Directories are organized in a hierarchical structure.

The top-most node in the directory structure is called the root. AFTP allows you to designate a directory as the current directory. The primary advantage to setting a current directory is that when you work with those files, you are not required to type out their full directory specification in commands.

For example, assume that your root directory contains two directories called Dir1 and Dir2, and that Dir2 contains a subdirectory called Subdir2a. To transfer five files named FILE1 through FILE5 to the server from Subdir2a:

You can enter the fully qualified file specification in each command, by typing:

put /dir2/subdir2a/file1

put /dir2/subdir2a/file2

put /dir2/subdir2a/file3

put /dir2/subdir2a/file4

put /dir2/subdir2a/file5

Or you can designate Subdir2a as your current directory, and use just the filenames in your commands, by typing:

cd /dir2/subdir2a

put file1

put file2

put file3

put file4

put file5

MVS Directories

In MVS, you can set your current directory to be a complete partitioned data set name or you can set it to be one or more qualifiers of a data set name. The current directory is used to create a file prefix that can be used with both partitioned data sets and sequential file names.

For an MVS-based AFTP client or server, the root represents the list of all partitioned data sets and sequential files.

VM Directories

In VM, filemodes act as a simple directory structure. A current directory in VM is a filemode letter. Multiple directory levels are not supported.

For a VM-based AFTP client or server, the root directory represents the list of all accessed mini-disks (filemodes).

RESTRICTION: VM shared file system (SFS) is not supported.

Windows NT Directories

The native Windows NT operating system has a directory structure. AFTP builds on that structure by making the drive the first segment of the directory path. For a Windows NT-based AFTP client or server, the AFTP root directory represents all of the drives available.

In the native Windows NT operating system, a current directory setting is maintained for each drive. For example, the following series of commands will delete the files in the C:\WORK\AFTP directory:

[C:\]  cd \work\aftp

[C:\WORK\AFTP\]  cd e:\new\data\

[C:\WORK\AFTP\]  erase C:*.*

AFTP, however, uses a virtual root that encompasses all of the drives, and the drive is treated as the first segment of a path. Only one current directory setting is kept. If a path is not specified for the inactive drive, the root directory of that drive is used. The same set of commands, issued in AFTP, will actually result in the files of the C:\ directory being erased:

aftp> cd  c:\work\aftp

aftp> cd  e:\new\data

aftp> delete c:*.*

If you want to use files on a drive other than the one set in the current directory, always use fully qualified filenames to ensure that the correct directory and files are used.

OS/2 Directories

The native OS/2 operating system has a directory structure. AFTP builds on that structure by making the drive the first segment of the directory path. For an OS/2-based AFTP client or server, the AFTP root directory represents all of the drives available.

In the native OS/2 operating system, a current directory setting is maintained for each drive. For example, the following series of commands will delete the files in the C:\WORK\AFTP directory:

[C:\]  cd \work\aftp

[C:\WORK\AFTP\]  cd e:\new\data\

[C:\WORK\AFTP\]  erase C:*.*

AFTP, however, uses a virtual root that encompasses all of the drives, and the drive is treated as the first segment of a path. Only one current directory setting is kept. If a path is not specified for the inactive drive, the root directory of that drive is used. The same set of commands, issued in AFTP, will actually result in the files of the C:\ directory being erased:

aftp> cd  c:\work\aftp

aftp> cd  e:\new\data

aftp> delete c:*.*

If you want to use files on a drive other than the one set in the current directory, always use fully qualified filenames to ensure that the correct directory and files are used.


Using File and Directory Specifications in Commands
Introduction to AFTP 	17 of 19

Understanding AFTP Basic Concepts

Using File and Directory Specifications in Commands

Some AFTP commands require you to indicate which files or directories you want to use. The AFTP facility was designed to offer flexibility in how you specify these files:

You can enter the fully qualified name by using the syntax native to the operating system being accessed or by using AFTP common naming format.

You can set a current directory and then use a partial filename (either in native or AFTP common naming format).

You can use wildcard characters to specify a list of related files.

This section discusses particular rules you must follow when specifying file and directory names for different operating systems. The section discusses:

AFTP common naming format

AFTP wildcard characters

MVS file specifications

VM file specifications

Windows NT file specifications

OS/2 file specifications

AFTP Common Naming Format

Different operating systems use different file naming conventions, file attributes, and file directory structures. AFTP provides a common file naming format that allows you to locate and transfer files without knowing how the files are actually named and stored on the server computer.

A file specification is a combination of directory name and filename. The following example illustrates how to specify a file specification using AFTP's common naming format:

/dir1/dir2/filepart1.filepart2

These are the syntax rules for the AFTP common naming format:

Forward slashes (/) are used to separate the various levels of directories and the filename. The forward slash used as the first character of a file specification represents the AFTP root directory.

The filename may contain one or more parts. Those parts must be joined by periods, not spaces or parentheses.

A backslash (\) can be used to represent the highest-level directory of the current directory.

In MVS, the backslash represents the highest-level qualifier of the current directory.

In the Windows NT operating system, the backslash represents the current drive.

In OS/2, the backslash represents the current drive.

For specific examples of how to use this notation, see the following sections on the file specifications for each operating system.

MVS File Specifications

MVS data files fall into two distinct categories:

Partitioned data set members

Physical sequential files

Restriction

AFTP does not support VSAM data sets or load module libraries (LOADLIBs).

Partitioned data sets can be viewed as directories that contain a list of members or files. The usual MVS syntax for naming a member in a partitioned data set is “neals.src.c(aping)”. In common format, the data set name becomes the directory and the member name becomes the filename:

MVS native  AFTP Common Name

neals.src.c(aping)   <------------>   /neals.src.c/aping

A sequential file is a flat file that is not a member of a partitioned data set. Since sequential files are not organized into any structure analogous to a directory, all sequential files are treated as if they reside in the root directory:

MVS native  AFTP Common Name

neals.src.c.a    <------------>   /neals.src.c.a

AFTP makes a distinction between a directory (a partitioned data set) and a data set qualifier. AFTP makes this distinction by terminating partitioned data sets with a slash (/) as a directory, and by terminating data set qualifiers with a period (.) as a partial filename.

VM File Specifications

Native filenames in VM are: “filename filetype filemode”.

Filemodes in VM represent its directory structure. The filename and filetype are joined with a period (.) to create the filename field in the common naming convention.

VM native  AFTP Common Name

ELAINE.TEXT.A  <-------->  /A/ELAINE.TEXT

Note

In AFTP, spaces are not permitted in file specifications. Use periods to join the parts of a VM native file specification.

Windows NT File Specifications

Filenames in Windows NT already use a directory structure. In the AFTP common naming syntax, the drive designation is used as the first segment of the common name.

Windows NT native	AFTP common name

c:\d1\d2\filename.ext	/c:/d1/d2/filename.ext

AFTP supports both the file allocation table (FAT) and high performance file system (NTFS) file systems of the Windows NT operating system.

OS/2 File Specifications

Filenames in OS/2 already use a directory structure. In the AFTP common naming syntax, the drive designation is used as the first segment of the common name.

OS/2 native	AFTP common name

c:\d1\d2\filename.ext	/c:/d1/d2/filename.ext

AFTP supports both the file allocation table (FAT) and high performance file system (HPFS) file systems of OS/2.

AFTP Wildcard Characters

You can use wildcard characters in your file specifications to request that certain commands be issued against multiple files. If you are using native naming conventions, use the wildcard characters supported by the native operating system.

AFTP common naming format defines three sets of wildcard characters:

*	Global match in a single naming segment, for zero or more characters

In MVS, a naming segment can be any qualifier or PDS member.

In VM, a naming segment can be the directory, filename, or filetype.

In the Windows NT operating system, a naming segment can only be the filename or extension. You cannot use wildcard characters in directory names.

In OS/2, a naming segment can only be the filename or extension. You cannot use wildcard characters in directory names.

**	In MVS only, global match across multiple segments, for one or more characters. See “Using Wildcards on the MVS File System” for specific examples on using this wildcard character.

?	Global match for a single character

In MVS, you can also use the % character which is native to MVS.

Using Wildcards on the MVS File System

In the MVS file system, wildcards are used a little differently than in the other AFTP operating systems. When using wildcards for specifying data set names, a single asterisk (*) represents any group of characters of any length within a single qualifier level. A double asterisk (**) is used to specify zero or more qualifiers. The double asterisk (**) must either immediately precede a period (.) delimiter, or follow a period (.) delimiter, and cannot be used with other characters.

Note

If you use the double asterisk as the highest-level qualifier you refer to all sequential files and partitioned data sets to which you have access. The command you have issued, for example a dir command, can take a long time to complete.

Both the percent sign (%) and question mark (?) can be used to represent a single wildcard character. The question mark (?) is part of the AFTP common format, and the percent sign (%) is supported native MVS syntax.

The following table provides some detailed examples of how to use the MVS wildcards. For the purposes of the examples, assume that you have the following list of files:

NEALS.A

NEALS.S

NEALS.SECOND.FILE

NEALS.SRC.C.APPL

NEALS.SRC.C(APPFTPD)

NEALS.SRC.C(BFILE)

NEALS.SRC.H

NEALS.SRC.NEW.FILE

NEALS.SYSFILE

NEALS.SYSTEM.LOG.FILE

SYS1.PARMLIB

Examples of Using Wildcard Characters in MVS File Specifications

File Specification with Wildcard Character		Files included		Files not included
/NEALS.SRC.*   (all files with 3 qualifiers where the first 2 qualifiers are NEALS.SRC)		NEALS.SRC.C NEALS.SRC.H		NEALS.A NEALS.S NEALS.SECOND.FILE NEALS.SRC.NEW.FILE NEALS.SYSFILE NEALS.SYSTEM.LOG.FILE SYS1.PARMLIB
/NEALS.S*.FILE (all files with 3 qualifiers where the first qualifier is NEAL, the second qualifier starts with S, and the third qualifier is FILE)		NEALS.SECOND.FILE		NEALS.A NEALS.S NEALS.SRC.C(APPL) NEALS.SRC.C(BFILE) NEALS.SRC.H NEALS.SRC.NEW.FILE NEALS.SYSFILE NEALS.SYSTEM.LOG.FILE SYS1.PARMLIB
/NEALS.SRC.C/A* (members of the partitioned data set NEALS.SRC.C beginning with A)		NEALS.SRC.C(APPFTPD)		NEALS.A NEALS.S NEALS.SECOND.FILE NEALS.SRC.C.APPL NEALS.SRC.C(BFILE) NEALS.SRC.H NEALS.SRC.NEW.FILE NEALS.SYSFILE NEALS.SYSTEM.LOG.FILE SYS1.PARMLIB
/NEALS.* (all files with first qualifier NEALS and one additional qualifier)		NEALS.A NEALS.S NEALS.SYSFILE		NEALS.SECOND.FILE NEALS.SRC.C.APPL NEALS.SRC.C.(APPFTPD) NEALS.SRC.C(BFILE) NEALS.SRC.H NEALS.SRC.NEW.FILE NEALS.SYSTEM.LOG.FILE SYS1.PARMLIB
/NEALS.S* (all files with first qualifier NEALS and one additional qualifier starting with the letter S)		NEALS.S NEALS.SYSFILE		NEALS.A NEALS.SECOND.FILE NEALS.SRC.C.APPL NEALS.SRC.C.(APPFTPD) NEALS.SRC.C(BFILE) NEALS.SRC.H NEALS.SRC.NEW.FILE NEALS.SYSFILE NEALS.SYSTEM.LOG.FILE SYS1.PARMLIB
/NEALS.** (all files with the first qualifier NEALS, and one or more additional qualifiers)		NEALS.A NEALS.S NEALS.SECOND.FILE NEALS.SRC.C.APPL NEALS.SRC.C.(APPFTPD) NEALS.SRC.C(BFILE) NEALS.SRC.H NEALS.SRC.NEW.FILE NEALS.SYSFILE NEALS.SYSTEM.LOG.FILE		SYS1.PARMLIB
/NEALS.S*.** (all files with first qualifier NEALS, second qualifer beginning with the letter S, and one or more additional qualifiers)		NEALS.SECOND.FILE NEALS.SRC.C NEALS.SRC.H NEALS.SRC.NEW.FILE NEALS.SYSTEM.LOG.FILE		NEALS.A NEALS.S NEALS.SYSFILE SYS1.PARMLIB
/NEALS.S*.* (all files with first qualifier NEALS, second qualifier beginning with the letter S, and one additional qualifier)		NEALS.SECOND.FILE NEALS.SRC.C NEALS.SRC.H		NEALS.A NEALS.S NEALS.SRC.NEW.FILE NEALS.SYSFILE NEALS.SYSTEM.LOG.FILE SYS1.PARMLIB
/NEALS.S**		Not valid; the double asterisk does not immediately follow or precede a period.


Setting File Transfer Defaults
Introduction to AFTP 	18 of 19

Understanding AFTP Basic Concepts

Setting File Transfer Defaults

As you have already seen in this chapter, different operating systems have different naming conventions. As you transfer files between your client computer and your server, you will probably want to establish a set of consistent filename transformations. You may even want to associate default file transfer characteristics (ASCII or binary) with certain types of files.

For example, you might have a set of executable files on the Windows NT operating system (*.EXE) that you want to store on a VM server. You always want those files transferred in binary and you want the filetype in VM to be EXEBIN to reflect the binary content. You can use the AFTP type command to specify the file transfer type and always give the complete file specification of both the source and target files each time you transfer a file. Or, you can create a set of personal defaults based on filename patterns.

AFTP lets you create a set of default filename mappings and transfer defaults in the AFTP initialization (INI) file.

The SNA Server Setup program copies an AFTP.INI file into the same directory as the AFTP client binaries. This file contains default values. If desired, you change these values to customize you filename mapping and transfer defaults. Your system administrator may have already created such a file for your use and placed it in a common location for all users to access.

For specific information on filename mapping, see the “Setting Up File Transfer Defaults” section in the “AFTP Server Configuration” chapter.


Additional Information
Introduction to AFTP 	19 of 19

Additional Information

This section lists some other sources of information that may assist you.

Microsoft SNA Server documentation (provided on this CD)

The Best of APPC, APPN, and CPI-C, SK2T-2013, a CD-ROM available from IBM, provides softcopy publications and papers, sample programs, and demonstrations.

The APPC Info Exchange Forum (GO APPC) on CompuServe

This forum is managed by the IBM APPC Market Enablement team.

IBM C/370 Programming Guide, SC09-1384

IBM Systems Network Architecture: Formats, GA27-3136

IBM SAA CPI-C Reference, SC26-4399.


The AFTP Program
Chapter 11	1 of 51

The AFTP Program

The AFTP program gives you control over some file transfer characteristics (for example, record format and length). It also contains a set of commands for managing directories and files on the server. See “Using the AFTP Command Environment” for an overview of the commands available in the AFTP program.

The following list summarizes the capabilities of the AFTP program:

Send file from client to server

Receive file from server to client

Control file transfer characteristics: ASCII/binary, record length, date format, modename, prompting for multiple files

Set and use current directory

Create or remove directories on server

Rename or delete files on server

List files on server

Trace operations for debugging


Using the AFTP Client Program
The AFTP Program	2 of 51

Using the AFTP Client Program

Typically you will enter the AFTP environment, establish a connection to a server, transfer several files, issue other AFTP commands, and then exit the AFTP environment.

AFTP supports a wide variety of commands. With commands you can:

Enter and exit the AFTP environment

Start or end a connection to the AFTP server

Set or query AFTP file transfer attributes

Transfer files

Manipulate directories and files on the AFTP server

Manipulate directories and files and issue miscellaneous local commands on the AFTP client computer

Get help for AFTP commands

Log trace data to diagnose problems

Each of these command sets is described in the next several sections. “AFTP Command Reference” is an alphabetical command reference of all of the commands that can be issued in the AFTP program.


Enter and Exit AFTP
The AFTP Program	3 of 51

Using the AFTP Client Program

Enter and Exit AFTP

The AFTP environment is opened with a simple aftp command. Once AFTP is started, a prompt (aftp>) is displayed on your screen to remind you that you are in the AFTP environment. (See AFTP in the following section, “AFTP Command Reference,” for the full syntax and description of the aftp command.)

The bye, exit, and quit, commands will close the AFTP program. If you have an open connection to an AFTP server when you exit from AFTP, AFTP will close the connection for you before exiting.


Start or End a Connection to the AFTP Server
The AFTP Program	4 of 51

Using the AFTP Client Program

Start or End a Connection to the AFTP Server

Before you can use AFTP commands on an AFTP server computer, you must first open a connection to that computer. From the AFTP client, you can connect to only one AFTP server at a time. However, it is possible to start and run multiple AFTP clients which can be connected to the same or different AFTP servers.

The user must have a local LU configured and partnered with a remote LU. When the user issues the open command, he can open to the remote LU (either its alias or the fully qualified remote LU name). By default, the AFTP client uses the mode #BATCH and the invokable TP name AFTPD. These defaults can be changed by using the modename and tpname commands.

Alternatively, the user can issue the open command to a symbolic destination name he has configured. In this case, the AFTP client finds the remote LU, the mode name, and the invokable TP name from the symbolic destination information. Again, the mode name and the TP name can be overridden with the modename and tpname commands.

For more information on CPI-C configuration and symbolic destination names, see “Configuring Properties for CPI-C” in Chapter 6 of the Microsoft SNA Server Administration Guide.

After issuing the open command, the user is prompted for a user ID. This user ID is used by the AFTP server for file permissions (different users have different permissions), and it is used for APPC conversation security.

If the user enters the user ID Anonymous, then he is not prompted for a password. No APPC conversation security is specified on the ALLOCATE flowing from the AFTP client, and the AFTP server treats this as “no user ID.”

If the user just presses the ENTER key when prompted for a user ID, then one of two things can happen. If the user has issued an open command to a remote LU, then this is treated as a user ID of Anonymous. If the user has issued an open command to a symbolic destination name, then whatever user ID and password is configured for the symbolic destination name is used (if none is configured, this is treated as Anonymous).

A user who enters a user ID other than Anonymous is also prompted for a password. This user ID and password flow on the ALLOCATE to the AFTP server. If the AFTP server is configured to use APPC conversation security, then matching is done to see whether the AFTP server can be invoked for this user ID. Also, the user ID is used by the AFTP server to allow file permissions.

Note

The password is not checked by the AFTP server, but by the underlying SNA stack at the AFTP server when the conversation security is checked.

The following example opens a connection to a server computer without specifying a user ID and password. The netid.remotelu represents the fully qualified LU name of a computer in your APPC network that is running the AFTP server program:

aftp> open netid.remotelu

userid:

Connected to netid.remotelu

aftp>

To close the connection to the current remote computer, but remain in the AFTP environment, use the close command:

aftp> close

Goodbye.

aftp>

At this point you can either open a new connection to a different partner or exit AFTP.

See “Specifying Security in the AFTP Program” for more information on security requirements and restrictions.

Following is a summary of the AFTP commands associated with opening and closing a connection to a partner computer:

AFTP Command	Description

close	Closes the current open AFTP session without exiting from the AFTP environment.

disconnect	Alias for close.

open	Opens a connection to an AFTP server computer.


Transfer Files
The AFTP Program	5 of 51

Using the AFTP Client Program

Transfer Files

AFTP provides commands that allow you to transfer files between your client computer and an AFTP server computer to which you are connected. You can transfer a single file at a time, multiple files by listing them explicitly, or multiple files by using wildcards. You can issue transfer commands only after you have opened a connection with an AFTP server. Following is a summary of the AFTP commands that transfer files:

AFTP Command	Description

get	Transfers one or more files from the server computer to the client computer.

put	Transfers one or more files from the client computer to the server computer.

receive	Alias for get.

send	Alias for put.

Setting Up The AFTP.INI File

Using the AFTP initialization file allows you to set file transfer defaults though the map verb. For the AFTP client, the AFTP.INI file is read in from the directory in which the AFTP.EXE file is located. The AFTP client program does not require the initialization file, but if the file is not found, file transfer defaults will not be defined.

For more information on setting file transfer defaults, see the section “Setting Up File Transfer Defaults” in the “AFTP Server Configuration” chapter.


Directory and File Manipulation on the AFTP Server Computer
The AFTP Program	6 of 51

Using the AFTP Client Program

Directory and File Manipulation on the AFTP Server Computer

Additional commands provided by AFTP are used for directory and file manipulation on the AFTP server computer. These include functions such as making and removing directories, listing the contents of directories, and renaming files. Following is a summary of the AFTP commands used for directory and file manipulation on the server computer:

AFTP Command	Description

cd	Sets the current directory on the server computer.

delete 	Deletes files on the server computer.

dir	Provides a full directory listing (files and their attributes) from the server computer.

ls	Displays a short directory listing (files only) from the server computer.

lsd	Provides a short directory listing from the server computer that contains only directories.

mkdir	Creates a new directory on the server computer.

pwd	Displays the current directory of the server computer.

rename	Renames a file on the server computer.

rmdir	Removes a directory on the server computer.


Local Commands on the Client Computer
The AFTP Program	7 of 51

Using the AFTP Client Program

Local Commands on the Client Computer

You can perform commands on the local computer while in AFTP. Local commands can be issued at any time during an AFTP session. It is not necessary to be connected to an AFTP server to issue non-AFTP commands using the ! command. Following is a summary of the AFTP commands that affect the local computer:

AFTP Command	Description

!	Issues a miscellaneous non-AFTP command on the local computer.

lcd	Changes the current directory on the local client computer.

lpwd	Displays the current directory of the local client computer.


Get Help for AFTP Commands
The AFTP Program	8 of 51

Using the AFTP Client Program

Get Help for AFTP Commands

You can access Help within the AFTP environment by issuing either of the following commands:

AFTP Command	Description

?	Alias for help.

help	Provides a list of topics for which help is available, or provides help on a specific AFTP command.


Troubleshooting
The AFTP Program	9 of 51

Troubleshooting

This section describes the various tools and logs available to help in diagnosing problems with the AFTP program.


Error Log
The AFTP Program	10 of 51

Troubleshooting

Error Log

The AFTP client logs error messages to the Windows NT event log. For more information on using event logs, see Chapter 13 of the Microsoft SNA Server Administration Guide.


Trace Tools
The AFTP Program	11 of 51

Troubleshooting

Trace Tools

AFTP provides trace tools that are used when a support organization needs trace information to help diagnose a problem. The AFTP client has built-in tracing, which writes to a file called AFTP.TRC.

Log Trace Data

You can capture trace data for the AFTP programs by setting the trace level to a nonzero value. The trace level determines how much trace data is captured during AFTP command processing. Your support organization will give you the trace value to use when trace data is needed to diagnose a problem.

Tracing is turned on by issuing the trace command with a nonzero value. See the trace command for information and usage.

Tracing is started immediately after issuing the trace command with a nonzero value and continues until the AFTP program is stopped, or until the trace command is reissued with a value of zero (0). Trace is not activated again the next time the AFTP program is started.


AFTP Program Command Reference
The AFTP Program	12 of 51

AFTP Program Command Reference

The following section provides information on all of the AFTP commands available in the command environment, including syntax, examples, and important platform-specific restrictions.


AFTP
The AFTP Program	13 of 51

AFTP Program Command Reference

AFTP

Use this command to start the AFTP program, in which you can use AFTP commands to manipulate files and directories.

The aftp command cannot be used inside the AFTP program.

Syntax

aftp [-h | destination]

where

-h

Help; brief help on the aftp command.

destination

The network address of the destination computer. A network address can be a fully qualified LU name or a CPI-C symbolic destination name. See “Specifying Destinations in the AFTP Program” in the previous chapter for more information on specifying this parameter.

Specifying the destination on the aftp command takes the place of using the open command. You are prompted for a user ID and password. See “Specifying Security in the AFTP Program” for more information on responding to these prompts.

Examples

Start the AFTP environment.

aftp

IBM AFTP version 1.0.

Licensed Materials - Property of IBM

5654-025

(C) Copyright 1994 by IBM Corp. All rights reserved.

Opening INI file from DD:APPFTPI.  INI load successful.

aftp>

Start the AFTP environment and connect to the server MYPC. The server does not require security, so press ENTER when prompted for the user ID.

aftp mypc

IBM AFTP version 1.0.

Licensed Materials - Property of IBM

5654-025

(C) Copyright 1994 by IBM Corp. All rights reserved.

Opening INI file from DD:APPFTPI.  INI load successful.

userid:

Connected to mypc

aftp>

Related Commands

exit, open


!
The AFTP Program	14 of 51

AFTP Program Command Reference

!

Use this command to execute non-AFTP commands on the client.

This command is valid only within the AFTP program.

Syntax

! [command]

where

command

A command and its arguments, to be issued on the client computer. The arguments are passed to the specified command uninterpreted and unchanged by AFTP. If a nonzero return code is returned by the operating system, it will be reported.

Platform Restriction

In Windows NT, you cannot use ! cd to set the current directory; you must use the lcd command.

Examples

If you are a Windows NT user and want to check the attributes on files in the current directory (C:\SNA) on your client computer, use ! to precede the attrib command.

!.attrib

A          C:\sna\file1.exe

A          C:\sna\file2.hlp

A          C:\sna\file3.inf

The aftp dir command will display a directory listing from the AFTP server. If you are a Windows NT user and want to list the directory structure on your client computer, use ! to precede the dir command.

!.dir

 Volume in drive C is BOBDA2

 Volume Serial Number is 256F-13FB

 Directory of C:\temp

05/09/95  11:02a        <DIR>          .

05/09/95  11:02a        <DIR>          ..

05/09/95  11:02a        <DIR>          subdir1

05/09/95  11:02a        <DIR>          subdir2

05/08/95  04:25p                   100 file1.exe

10/18/94  03:33p                   100 file2.hlp

04/05/95  11:32a                   100 file3.inf

05/10/95  03:25p                     0 dir.txt

               3 File(s)           300 bytes

                            363,650,304 bytes free

Related Commands

lcd, lpwd


?
The AFTP Program	15 of 51

AFTP Program Command Reference

?

Use this command to get help information about AFTP commands.

This command is an alias of the help command. See the help comand for detailed information.

This command is valid only within the AFTP program.

Syntax

? [command | commands]

where

command

Requests specific help for an AFTP command.

commands

Requests a list of the AFTP commands.


ALLOC
The AFTP Program	16 of 51

AFTP Program Command Reference

ALLOC

Use this command to set the allocation size to use when creating files or data sets (partitioned or sequential).

Platform Restriction

This command is used only by AFTP servers running on MVS.

This command is valid only within the AFTP program. You must have an open connection to the server to issue this command.

Syntax

alloc [size]

where

size

The number of bytes to be allocated for primary and secondary extents. AFTP will divide this value by the current block size value to determine the number of allocation units to be used.

The initial setting is 0, which sets the allocation size to the default used by C/370 runtime. See the IBM C/370 Programming Guide for specific information on the default value used.

If no parameter is specified, the current setting is displayed.

Examples

Set the allocation size to 4096:

aftp> alloc 4096

Allocation size set to 4096.

Reset the allocation size to the default:

aftp> alloc 0

Allocation size set to 0

Related Commands

block, lrecl, recfm, status


ASCII (ASC)
The AFTP Program	17 of 51

AFTP Program Command Reference

ASCII (ASC)

Use this command to change the transmission data type to ASCII. All subsequent transmissions following this command will be transferred with a data type of ASCII until the setting is explicitly changed, or the connection ends. Refer to “File Transfer Types” for more information on the ASCII transmission type.

Accepted abbreviation: asc

This command is valid only within the AFTP program. You must have an open connection to the server to issue this command.

Syntax

ascii

asc

Example

aftp> ascii

Data type set to ASCII.

Related Commands

binary, status, type


BINARY (BIN)
The AFTP Program	18 of 51

AFTP Program Command Reference

BINARY (BIN)

Use this command to change the transmission data type to binary. All subsequent transmissions following this command will be transferred with a data type of binary until the setting is explicitly changed or the connection ends. Refer to “File Transfer Types” for more information on the binary transfer data type.

Accepted abbreviation: bin

This command is valid only within the AFTP program. You must have an open connection to the server to issue this command.

Syntax

binary

bin

Example

aftp> binary

Data type set to BINARY.

Related Commands

ascii, status, type


BLOCK
The AFTP Program	19 of 51

AFTP Program Command Reference

BLOCK

Use this command to set the block size to use when writing files (get to the AFTP client or put to the AFTP server).

This command is valid only within the AFTP program. You must have an open connection to the server to issue this command.

Syntax

block [size]

where

size

The amount of space to block for the data set.

The initial setting is 0, which sets the block size to the default used by C/370 runtime. See the IBM C/370 Programming Guide for specific information on the default value used.

If no parameter is specified, the current setting is displayed.

Examples

Set the block size to 1024:

aftp> block 1024

Block size set to 1024.

Reset the block size to the default:

aftp> block 0

Block size set to 0

Related Commands

block, lrecl, recfm, status


BYE
The AFTP Program	20 of 51

AFTP Program Command Reference

BYE

Use this command to exit the AFTP program.

This command is an alias of the exit command. See the exit command for detailed information.

This command is valid only within the AFTP program.

Syntax

bye


CD
The AFTP Program	21 of 51

AFTP Program Command Reference

CD

Use this command to change the current directory on the server.

This command is valid only within the AFTP program. You must have an open connection to the server to issue this command.

Syntax

cd {directory_spec | ..}

where

directory_spec

Any valid native or common syntax directory specification. You can provide either a fully qualified specification or a partial specification. See “Using File and Directory Specifications in Commands” for specific examples.

..

Parent directory; changes directory to the next higher directory in the directory chain. You cannot use this value if the current directory is already set to the root directory.

Examples

This example uses the fully qualified native directory name for OS/2:

aftp> cd c:\cmlib

CD command successful.

This example uses the fully qualified AFTP common naming format for an MVS partitioned data set:

aftp> cd /neals.src.c/

CD command successful.

This example uses two steps to set the current directory to the neals.src.c PDS, using partial directory specifications:

aftp> cd /neals.

CD command successful.

aftp> cd src.c/

CD command successful.

This example uses the special double period (..) value to change to a higher-level directory. After the commands are complete, the current directory will be set to /neals.src. :

aftp> cd /neals.src.c/

CD command successful.

aftp> cd ..

CD command successful.

Related Commands

pwd, lcd


CLOSE
The AFTP Program	22 of 51

AFTP Program Command Reference

CLOSE

Use this command to close an AFTP session with a server without exiting from the AFTP program.

This command is valid only within the AFTP program. You must have an open connection to the server to issue this command.

Syntax

close

Example

aftp> close

Goodbye.

aftp>

Alias

disconnect

Related Command

open


DATE
The AFTP Program	23 of 51

AFTP Program Command Reference

DATE

Use this command to set how the file date will be handled during file transfers.

This command is valid only within the AFTP program. You must have an open connection to the server to issue this command.

Syntax

date [new | old]

where

new

Assign the current time and date to the newly copied file. This is the initial setting on MVS.

old

The copied files will inherit the date of the original file. This is the initial setting on VM.

If no parameter is specified, the current setting is displayed.

Platform Restriction

The old parameter is not supported on MVS.

Examples

View the current date mode setting:

aftp> date

Date Mode

: OLD

aftp>

Set the date mode to NEW:

aftp> date new

Date Mode set to NEW.

aftp>

Related Command

status


DELETE (DEL)
The AFTP Program	24 of 51

AFTP Program Command Reference

DELETE (DEL)

Use this command to delete one or more files on the server computer. If you want confirmations before you delete the files, set the prompt command to ON. (See the prompt command for more information.)

Platform Restriction

The delete command cannot be used to remove an MVS PDS. The rmdir command must be used to remove an MVS PDS.

Accepted abbreviation: del

This command is valid only within the AFTP program. You must have an open connection to the server to issue this command.

Syntax

delete file_spec

del file_spec

where

file_spec

The file specification of the file to be deleted on the server computer. You can use native or common format, and either fully qualified names or partially specified names for files in the current directory. See “Using File and Directory Specifications in Commands” for specific examples.

Wildcards are permitted in the file name.

Examples

Delete a VM file using fully qualified native file name:

aftp> delete elaine.letter.d

Deleting /D/ELAINE.LETTER

Delete a PDS member using fully qualified AFTP common file naming format:

aftp> delete /neals.src.c/test4

Deleting /NEALS.SRC.C/TEST4

Turn prompting on and delete a set of Windows NT files in the D:\TEMP\NEW directory (the current directory has been set to: D:\TEMP\NEW):

aftp>

prompt on

delete aftp*.*

Delete AFTP_PC.CON? (Yes,No,Go,Quit)

y

Deleting /d:/temp/new/AFTP_PC.CON

Delete AFTP.TRC? (Yes,No,Go,Quit)

y

Deleting /d:/temp/new/AFTP.TRC

aftp>

Related Commands

prompt, rmdir


DIR
The AFTP Program	25 of 51

AFTP Program Command Reference

DIR

Use this command to display a directory listing from the server. Directories and files are displayed, along with attributes.

Use the ls command to list filenames and directory entries without the attributes. Use the lsd command to list only directory entries.

This command is valid only within the AFTP program. You must have an open connection to the server to issue this command.

Syntax

dir [* | file_spec]

where

*

Default: list files in the current directory on the AFTP server.

file_spec

The file specification of the files to be listed on the server computer. You can use native or common format, and either fully qualified names or partially specified names for files in the current directory. See “Using File and Directory Specifications in Commands” for specific examples.

Wildcards are permitted in the file name.

If the file specification is a directory name, a listing of the files under that directory will be listed.

Examples

The exact output of this command depends on the AFTP server’s operating system.

MVS EXAMPLES

With the current directory set to “/NASRIN.”, list directory contents (same as “dir *”). This command will list partitioned data sets (PO) and sequential files (PS) that meet the criteria:

aftp> dir

directory for /nasrin.

Volser   Date   Org Recfm Lrecl Ext  Blks Cyls Dataset Name

APPC01 94/05/18 PO  FB      80    1  6160    9 CLIST

APPC01 94/05/18 PO   U    3120   16  3120  135 LOADLIB

WORK02 94/05/16 PS   F      80    1    80    0 MIS

APPC01 94/05/17 PO  VB     132    1 3120     0 MISC

ESAWK2 94/05/16 PO  VB     255    1 3280     0 NEWDIR

Directory listing complete.

aftp>

The following example also uses the current directory “/NASRIN.”, but uses the double asterisk wildcard (MVS only) to extend the list to include multiple qualifiers. MVS wildcards are described in the preceding section, “Using Wildcards on the MVS File System.”

Caution

If you use the double asterisk wildcard when the current directory is set to the root, you will be requesting that AFTP list all files that you have access to. This may take a long time.

aftp> dir **   directory for /nasrin.

Volser Date		Org	Recfm	Lrecl	Ext	Blks	Cyls	Dataset Name
APPC01 94/05/17		PO	FB	80	2	3120	33	C.OBJ
APPC01 94/05/18		PO	FB	80	1	6160	9	CLIST
WORK01 94/05/16		PO	FB	80	1	6160	0	ISPF.ISPPROF
WORK02 94/05/16		PO	FB	80	1	3120	1	JCL.CNTL
APPC01 94/05/18		PO	U	3120	16	3120	135	LOADLIB
FRE2AF 94/05/18		PS	VB	132	1	3120	0	LOGS.APPCOPYE
ESAWRK 94/04/26		PS	VB	132	1	3120	0	LOGS.APPCOPYT
ESAWRK 94/04/26		PS	VB	132	1	3120	0	LOGS.APPFTPE
ESAWRK 94/05/16		PS	VB	132	1	3120	0	LOGS.APPFTPT
WORK02 94/05/16		PS	F	80	1	80	0	MIS
APPC01 94/05/17		PO	VB	132	1	3120	0	MISC
ESAWK2 94/05/16		PO	VB	255	1	3280	0	NEWDIR
APPC01 94/05/13		PO	VB	256	1	6233	0	NEWDIR2.CLIST
APPC01 94/05/02		PO	FB	80	1	3120	29	SOURCE.ASM
APPC01 94/05/18		PO	FB	80	1	3120	29	SOURCE.C
APPC01 94/05/13		PO	FB	80	1	3120	9	SOURCE.H
APPC01 94/05/13		PO	FB	80	1	3120	29	SOURCE.INC
ESAWRK 94/05/16		PS	VA	125	1	129	0	SPFLOG1.LIST
ESAWK2 94/05/16		PS	FB	80	1	800	0	SPFTEMP0.CNTL
ESAWK2 94/03/15		PS	FB	80	1	800	0	SPFTEMP1.CNTL
ESAWRK 94/03/15		PS	FBA	121	1	3146	0	SPFTEMP1.LIST
WORK02 94/05/17		PS	VB	1028	1	6144	0	TESTDIR.PDS .TESTFIL6

Directory listing complete.

aftp>

With the current directory set to /NASRIN.CLIST/, which is a PDS, the directory list will show members of the PDS:

aftp>   dir

directory for /nasrin.clist/

Name    VV.MM  Created   Changed  Time   Size  Init  Mod  ID

ACOPY   01.05  94/02/25  94/03/04 09:38    69    70    0  NASRIN

AFTP    01.08  94/02/25  94/03/15 15:08    70    71    0  NASRIN

ANAME   01.04  94/02/25  94/03/04 09:41    85    86    0  NASRIN

APING   01.04  94/02/25  94/03/04 09:41    68    69    0  NASRIN

A3270   01.03  94/02/25  94/03/04 09:42    68    69    0  NASRIN

MEMTEST 01.00  94/02/25  94/02/25 19:43     2     2    0  MEM

Directory listing complete.

aftp>

VM EXAMPLES

With the current directory set to /A/, list all files beginning with the characters “ANY:”

aftp> dir any*.*

directory for /a/

ANYNET    NOTEBOOK  A0 V     83   7902     84  7/23/93 16:32:40

ANYNETCD  SCRIPT    A1 V     97   4154     23  7/13/93 19:07:32

ANYNET2   NOTEBOOK  A0 V     79    140      2  6/30/93 14:48:17

ANYONE    TXT       A1 V     14      1      1  5/05/94 13:25:40

ANYTWO    TXT       A1 V     14      1      1  5/05/94 13:25:40

ANY3      TXT       A1 V     14      1      1  5/05/94 13:25:40

ANY4      SCRIPT    A1 V     14      1      1  5/05/94 13:25:40

Directory listing complete.

aftp>

The following example lists the contents of the root directory (/) on an AFTP server on VM. The root directory on VM contains a list of directories (filemodes) but does not contain files.

aftp> dir /*

directory for /

LABEL  VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) BLKS LEFT BLK TOTAL

EBP191 191  A R/W  20  3380 4096  613  2832-94  168  3000

EPE192 192  B R/W  20  3380 4096  237  2453-82  547  3000

IDT191 201  E R/O  150 3380 4096  1696  14618-65  7882  22500

IDP195 202  F R/O  60  3380 4096  884  6626-74  2374  9000

Directory listing complete.

aftp>

Windows NT EXAMPLES

With the current directory set to /D:/TEMP/, list all files in the directory.

aftp>

dir

directory for /d:/temp/

11-18-92   3:34p   <DIR>  .

11-18-92   3:34p   <DIR>  ..

 7-13-93   4:07p   93187  ANYNETCD.SCR

 5-05-94  10:25a      17  ANYONE.TXT

 5-05-94  10:25a      17  ANYTWO.TXT

 5-05-94  10:25a      17  ANY3.TXT

 5-05-94  10:25a      17  ANY4.SCR

Directory listing complete.

aftp>

The following example lists the contents of the virtual root directory (/) on an AFTP server on Windows NT. The virtual root directory contains a list of drives available but does not contain files.

aftp>

dir /

directory for /

NTFS  81726    2104 97   C:

FAT   35736   12154 65   D:

FAT   77638   67312 13   E:

Directory listing complete.

aftp>

Note

NTFS and FAT refer to the file system. The three numbers following the file system indicator are, from left to right, the total disk capacity (measured in Kbytes), the free disk capacity (measured in Kbytes), and the percentage of the disk in use. The last letter is the drive or virtual drive.

Related Commands

ls, lsd


DISCONNECT (DISC)
The AFTP Program	26 of 51

AFTP Program Command Reference

DISCONNECT (DISC)

Use this command to close the AFTP session with a server without exiting the AFTP program.

This command is an alias of the close command. See the close command for detailed information.

Accepted abbreviation: disc

This command is valid only within the AFTP program. You must have an open connection to the server to issue this command.

Syntax

disconnect

disc


EXIT
The AFTP Program	27 of 51

AFTP Program Command Reference

EXIT

Use this command to exit from the AFTP program and return to the operating system prompt. If you currently have an open connection, it will be closed.

This command is valid only within the AFTP program.

Syntax

exit

Example

aftp> exit

Aliases

bye, quit


GET
The AFTP Program	28 of 51

AFTP Program Command Reference

GET

Use this command to copy one or more files from the AFTP server to the client. If you want confirmations before each file is transferred, turn prompting on (see the prompt command).

Before you use this command to transfer a file, you should make sure that you set the correct file transfer characteristics for that file (for example, ASCII or binary, record format, record length). See “File Transfer Types” and “Special File Structure” for additional information.

Platform Restriction

On MVS, a load module library PDS (LOADLIB PDS) must be archived before it can be transferred, to ensure that all data associated with that PDS is transferred.

This command is valid only within the AFTP program. You must have an open connection to the server to issue this command.

Syntax

get server_file [client_file | -]

where

server_file

The name of the file on the server to be copied. Wildcards are permitted in the name to generate the list of files to copy.

client_file

The name on the client to which the server files are copied. Wildcards are permitted in this parameter to specify a list of filenames.

Default: use the same filename as on the server.

-

Instead of creating a file on the client, display the contents of the file on the display screen.

Examples

The following example copies the server file to a client file in the current directory with the same name. The optional client file parameter is set to Off. Prompting is set to Off.

aftp> get any*.t*

Receiving “+/a/ANYONE.TXT".

File was transferred in ASCII and stored as "/d:/temp/ANYONE.TXT".

15 bytes received in 0.690 seconds (0.02 Kbytes/s)

Receiving "/a/ANYTWO.TXT".

File was transferred in ASCII and stored as "/d:/temp/ANYTWO.TXT".

15 bytes received in 0.720 seconds (0.02 Kbytes/s)

Receiving "/a/ANY3.TXT".

File was transferred in ASCII and stored as "/d:/temp/ANY3.TXT".

15 bytes received in 0.880 seconds (0.02 Kbytes/s)

aftp>

The following example copies a server file in the server current directory to a client file with a different name in the client current directory.

aftp>

get any4.scr newtest.txt

Receiving "/d:/temp/ANY4.SCR".

File was transferred in ASCII and stored as "/A/newtest.txt".

15 bytes received in 0.933 seconds (0.02 Kbytes/s)

aftp>

The following example copies the server file list to client files in the current directory with the same name. The prompting feature is turned on in this case. The optional client file parameter has been set to Off.

aftp>

get any*.*

Get ANYNETCD.SCR? (Yes,No,Go,Quit)

y

Receiving "/d:/temp/ANYNETCD.SCR".

File was transferred in ASCII and stored as "/A/ANYNETCD.SCRIPT".

89032 bytes received in 2.411 seconds (36.06 Kbytes/s)

Get ANYONE.TXT? (Yes,No,Go,Quit)

y

Receiving "/d:/temp/ANYONE.TXT".

File was transferred in ASCII and stored as "/A/ANYONE.TXT".

15 bytes received in 0.780 seconds (0.02 Kbytes/s)

Get ANYTWO.TXT? (Yes,No,Go,Quit)

n

Get ANY3.TXT? (Yes,No,Go,Quit)

g

Receiving "/d:/temp/ANY3.TXT".

File was transferred in ASCII and stored as "/A/ANY3.TXT".

15 bytes received in 0.838 seconds (0.02 Kbytes/s)

Receiving "/d:/temp/ANY4.SCR".

File was transferred in ASCII and stored as "/A/ANY4.SCRIPT".

15 bytes received in 0.793 seconds (0.02 Kbytes/s)

aftp>

The following example copies a server file list in the server current directory to a set of client files with a different names in the client's current directory. The prompting feature is turned off.

get any*.txt /b/any*.script

Receiving "/d:/temp/ANYONE.TXT".

File was transferred in ASCII and stored as "/b/anyONE.script".

15 bytes received in 0.848 seconds (0.02 Kbytes/s)

Receiving "/d:/temp/ANYTWO.TXT".

File was transferred in ASCII and stored as "/b/anyTWO.script".

15 bytes received in 0.736 seconds (0.02 Kbytes/s)

Receiving "/d:/temp/ANY3.TXT".

File was transferred in ASCII and stored as "/b/any3.script".

15 bytes received in 0.502 seconds (0.03 Kbytes/s)

aftp>

Alias

receive

Related Commands

alloc, ascii, binary, block, lrecl, prompt, put, recfm, type


HELP
The AFTP Program	29 of 51

AFTP Program Command Reference

HELP

Use this command to get a list of topics for which help is available. This command also can output a brief help message for the input command parameter. The text displays the correct command syntax.

This command is valid only within the AFTP program.

Syntax

help [command | commands]

where

command

Requests specific help for an AFTP command.

commands

Requests a list of the AFTP commands.

Examples

The following example displays the topics for which help is available:

aftp> help

Commands to get you started:

  OPEN   - connect to the AFTPD server on a partner system

  GET    - copy files from the server to the client

  PUT    - copy files from the client to the server

  TYPE   - change the data type for file transfers to either

           BINARY or ASCII

  DIR    - list files that are on the server

  CLOSE  - end your connection to the server

  EXIT   - close any active connection and end AFTP

Help is available for all AFTP commands.

(enter HELP "command_name")

Help is available for the following topics:

(enter HELP "topic_name")

   COMMANDS  - Lists all available commands.

aftp>

The following example displays all available commands:

aftp> help commands

help commands

Help is available for the following commands:

(Enter HELP “command-name”)

Commands are:

!       close       lpwd      pwd      tpname

?       date        lrecl     quit     trace

alloc   delete      ls        receive  type

ascii   dir         lsd       recfm

bell    disconnect  mkdir     rename

binary  exit        modename  rmdir

block   get         open      send

bye     help        prompt    status

cd      lcd         put       system

aftp>

The following example retrieves the help text for the type command:

aftp> help type

TYPE [ascii|binary|default]

  Sets the data type.  If no argument is given, the current

  data type setting will be displayed.  The default is

  DEFAULT.

  The TYPE command can only be used when a connection is

  OPEN.  The default is reset during OPEN processing.

  See also: ASCII, BINARY, GET, PUT

aftp>

Alias

?


LCD
The AFTP Program	30 of 51

AFTP Program Command Reference

LCD

Use this command to change the current directory on the client. When this command is invoked without any parameters, the name of the client current directory is displayed.

This command is valid only within the AFTP program.

Syntax

lcd [directory_spec]

where

directory_spec

Any valid native or common syntax directory specification. You may provide a fully qualified specification or a partial specification. See “Using File and Directory Specifications in Commands” for specific examples.

Default: display the name of the client current directory.

Examples

The following example uses the fully qualified native directory name for Windows NT:

aftp> lcd c:\cmlib

 /c:/sna/system/  is the client's current directory.

The following example uses the AFTP common naming format for VM:

aftp> lcd /x

"/x/" is the client's current directory.

The following example uses two steps to set the current directory to the neals.src.c PDS, using partial directory specifications:

aftp> lcd /neals.

"/neals." is the client's current directory.

aftp> lcd src.c/

"/neals.src.c/" is the client's current directory.

Related Commands

lpwd, cd


LPWD
The AFTP Program	31 of 51

AFTP Program Command Reference

LPWD

Use this command to display the name of the current directory of the client. The output of the command uses the AFTP common naming format.

This command is the same as issuing the lcd command without any parameters.

This command is valid only within the AFTP program.

Syntax

lpwd

Example

Display the AFTP client's current directory:

aftp> lpwd

 /c:/sna/system/  is the client's current directory.

aftp>

Related Commands

lcd, pwd


LRECL
The AFTP Program	32 of 51

AFTP Program Command Reference

LRECL

Use this command to set the record length to use when writing files (get to the AFTP client or put to the AFTP server). This value only takes effect when the files are stored on a computer that handles record-oriented files (for example, VM and MVS). On other systems, this value is ignored.

This command is valid only within the AFTP program. You must have an open connection to the server to issue this command.

Syntax

lrecl [size]

where

size

The size of the record to write. The range of values varies by operating system.

The initial setting is 0, which sets the record length to the default record length used by C/370 runtime. See the IBM C/370 Programming Guide for specific information on the default value used.

Restriction: The maximum record length for binary files is 28672 (28K). If your file has a longer record length, use an archiving tool to pack it into smaller records.

If no parameter is specified, the current setting is displayed.

Examples

Set the record length to 132:

aftp> lrecl 132

Record length set to 132.

Reset the record length to the default:

aftp> lrecl 0

Record length set to 0

Related Commands

alloc, block, recfm, status


LS
The AFTP Program	33 of 51

AFTP Program Command Reference

LS

Use this command to display a directory listing from the AFTP server that contains the filenames and directory entries only (no file attributes).

Use the dir command to list filenames, directory entries, and attributes. Use the lsd command to list only directory entries.

This command is valid only within the AFTP program. You must have an open connection to the server to issue this command.

Syntax

ls [* | file_spec]

where

*

Default: list files in the current directory on the server.

file_spec

The file specification of the files to be listed on the server computer. You can use native or common format, and either fully qualified names or partially specified names for files in the current directory. See “Using File and Directory Specifications in Commands” for specific examples.

Wildcards are permitted in the filename.

If the file specification is a directory name, a listing of the files under that directory will be displayed.

Examples

MVS EXAMPLES

The following example shows the output of the ls command when the current directory is set to be a PDS:

aftp> ls

directory for /nasrin.clist/

ACOPY

AFTP

ANAME

APING

A3270

MEMTEST

Directory listing complete.

aftp>

The following example shows an ls command when the current directory is a file prefix:

aftp> LS **

directory for /nasrin.

AFTPD.JOBLOG

C.OBJ

CLIST

ISPF.ISPPROF

JCL.CNTL

LOADLIB

LOG.MISC

LOGS.APPCOPYE

LOGS.APPCOPYT

LOGS.APPFTPDE

LOGS.APPFTPDT

LOGS.APPFTPE

LOGS.APPFTPT

NEWDIR

NEWDIR2

NEWDIR2.CLIST

SOURCE.ASM

SOURCE.C

SOURCE.H

SPFLOG1.LIST

SPFTEMP0.CNTL

SPFTEMP1.CNTL

SPFTEMP1.LIST

Directory listing complete.

aftp>

VM EXAMPLES

The following example lists the files in the current directory /A/ with the filename “TEST” and any file type:

aftp> ls test.*

directory for /a/

TEST.LABELS

TEST.PACKAGE

TEST.SCRIPT

TEST.XEDIT

Directory listing complete.

aftp>

Windows NT EXAMPLES

The following example lists file with the extension “EXE” in the directory “E:\WORK\AFTP” on the AFTP server:

aftp> ls e:\work\aftp\*.exe

directory for /e:/work/aftp/

AFTP.EXE

AFTPD.EXE

ACOPY.EXE

Directory listing complete

aftp>

The following example lists all files in the current directory on the AFTP server:

aftp> ls

directory for /e:/work/

.

..

PING

TEMP

WORK

C600

QIK2.SCD

AFSDOC.PS

HEADER.DAT

Directory listing complete

aftp>

Related Commands

dir, lsd


LSD
The AFTP Program	34 of 51

AFTP Program Command Reference

LSD

Use this command to display a list of directories on the AFTP server. The listing will not contain files or file attributes.

Platform Difference

If the server is MVS, this command will list only the partitioned data sets which match the directory_spec. PDS members and sequential files will not be included in the output.

Use dir to display a full listing of file names, directories, and attributes. Use ls to list only the file names and directory entries.

This command is valid only within the AFTP program. You must have an open connection to the server to issue this command.

Syntax

ls [* | directory_spec]

where

*

Default: list files in the current directory on the AFTP server.

directory_spec

Any valid native or common syntax directory specification. You can provide a fully qualified specification or a partial specification. See “Using File and Directory Specifications in Commands” for specific examples.

Wildcards are permitted.

Examples

MVS EXAMPLES

In MVS, the lsd command will only display the partitioned data sets that match the directory_spec:

aftp> lsd **

directory for /nasrin.

C.OBJ

CLIST

ISPF.ISPPROF

JCL.CNTL

LOADLIB

NEWDIR

NEWDIR2

NEWDIR2.CLIST

SOURCE.ASM

SOURCE.C

SOURCE.H

Directory listing complete.

aftp>

VM EXAMPLES

VM only supports a single level directory structure. All directories are located at the root.

aftp> lsd /

directory for /

A

B

E

F

Q

R

S

T

U

X

Y

Directory listing complete.

aftp>

Windows NT EXAMPLES

The following example performs a lsd directory listing using a native syntax directory specification and wildcards, in Windows NT:

aftp> lsd e:\work\a*

directory for /e:/work/

AFTP

Directory listing complete

aftp>

The following example displays a lsd directory listing for the current directory on the server:

aftp> lsd

directory for /e:/work/

PING

TEMP

WORK

C600

AFTP

Directory listing complete

aftp>

Related Commands

dir, ls


MKDIR (MD)
The AFTP Program	35 of 51

AFTP Program Command Reference

MKDIR (MD)

Use this command to create a new directory on the server.

Accepted abbreviation: md

This command is valid only within the AFTP program. You must have an open connection to the server to issue this command.

Platform Differences:

This command is not supported on VM.

On MVS, this command can only be used to create partitioned data sets.

Syntax

mkdir directory_spec

md directory_spec

where

directory_spec

Any valid native or common syntax directory specification. You may provide a fully qualified specification or a partial specification. See “Using File and Directory Specifications in Commands” for specific examples.

Wildcard characters are not permitted in this value.

Examples

The following example creates a new MVS PDS whose parent is the current directory (\RLGRAY.) on the server:

aftp> mkdir testdir

Directory RLGRAY.TESTDIR created.

aftp>

The following example creates a new directory using a full path specification:

aftp> mkdir e:\work\testdir

Directory e:\work\testdir created.

aftp>

Related Commands

alloc, block, rmdir


MODENAME
The AFTP Program	36 of 51

AFTP Program Command Reference

MODENAME

Use this command to change the mode used for the APPC conversation.

See “Mode” for more information on setting conversation modes.

This command is valid only within the AFTP program. You cannot have an open connection when you issue this command.

Syntax

modename [mode_name]

where

If no parameter is specified, the current setting is displayed.

mode_name

The name associated with a set of properties to use for the APPC conversation.

The initial setting is #BATCH.

Platform Difference

On many VM systems, the # character is used as the logical line end character. If your VM system is set this way, use the cp terminal linend off command to disable the line end character before issuing a command to set a modename containing the # character.

Example

This example sets the conversation mode name to interactive.

aftp> modename #INTER

Mode Name set to “#INTER”.

aftp>

Related Command

status


OPEN
The AFTP Program	37 of 51

AFTP Program Command Reference

OPEN

Use this command to open a connection to a destination computer. If this command is invoked without any parameters you are prompted for the destination. Once the destination is entered, you will be prompted for your user ID and password. See “Specifying Security in the AFTP Program” for details on responding to the user ID and password prompts.

Platform Difference

On VM, a user ID and password must be provided. Shared user IDs are not supported.

This command is valid only within the AFTP program.

Syntax

open [destination]

where

destination

The network address of the destination computer. A network address may be a fully qualified LU name or a CPI-C symbolic destination name. See “Specifying Destinations in the AFTP Program” in the previous chapter for more information on specifying this parameter.

If this parameter is not entered after the open command, AFTP will prompt you for it.

Examples

Note

The password you type at the prompt may or may not be visible at the display, depending on the operating system.

In this example the destination is entered along with the open command. The destination in this case is a fully qualified LU name.

aftp> open USIBMNR.NR50FFFI

userid: MARKP

password: password

Connected to USIBMNR.NR50FFFI

aftp>

The following example prompts for the destination. The destination provided in this case is an LU alias.

aftp> open

(to) MY_SERVER

userid: MARKP

password: password

Connected to MY_SERVER

aftp>

Related Commands

close, disc


PROMPT
The AFTP Program	38 of 51

AFTP Program Command Reference

PROMPT

Use this command to set the prompt mode used when get, put, or delete commands are issued on multiple files. When prompting is turned on, AFTP will ask you to confirm the operation on each file.

This command is valid only within the AFTP program. You must have an open connection to the server to issue this command.

Syntax

prompt [off | on]

where

If no parameter is specified, the current setting is displayed.

on

Prompt user when multiple files are being processed, for example:

Get filename.ext? (Yes,No,Go,Quit)

You must respond to continue:

YES	Process this individual file, then prompt for the next file.

NO	Do not process this file, prompt for the next file.

GO	Process this and all remaining files with no further prompting.

QUIT	Do not process this or any other files; end the command.

See the get and put commands for examples of the different output caused by the prompt command.

off

Do not prompt user. This is the original setting.

Examples

The following example explicitly sets the value of the prompt to ON:

aftp> prompt ON

prompt is ON

Related Commands

delete, get, put


PUT
The AFTP Program	39 of 51

AFTP Program Command Reference

PUT

Use this command to copy one or more files from the AFTP client to the AFTP server. If you want a confirmation before each file is transferred, set the prompt command to on. (See the prompt command for more information.)

Before you use this command to transfer a file, you should make sure that you set the correct file transfer characteristics for that file (for example, ASCII or binary, record format, record length). See “File Transfer Types” and “Special File Structure” for additional information.

Platform Restriction

On MVS, a load module library PDS (LOADLIB PDS) must be archived before it can be transferred, to ensure that all data associated with that PDS is transferred.

This command is valid only within the AFTP program. You must have an open connection to the server to issue this command.

Syntax

put client_file [server_file]

where

client_file

The name of the AFTP client file to be copied. Wildcards are permitted in the name to generate a list of files to copy.

server_file

The name on the AFTP server to which the client files are copied. Wildcards are permitted in this parameter to specify a list of filenames.

Default: the client filename(s).

Examples

The following example copies a client file to a server file in the current directory with the same name. The optional server file parameter has been omitted.

aftp>

put /a/test.script

Sending "/a/TEST.SCRIPT".

File was transferred in ASCII and stored as "/d:/temp/new/TEST.SCR".

193 bytes sent in 0.689 seconds (0.27 Kbytes/s)

aftp>

The following example copies a client file which is not in the client current directory to a server file with a different name which is not in the server current directory:

aftp> put e:\work\aftp.doc n:\u\aftpdoc.txt

Sending "/e:/work/aftp.doc"

File was transferred in ASCII and stored as "/n:/u/aftpdoc.txt"

1232 bytes sent in 0.340 seconds (3.54 Kbytes/s)

aftp>

The following example copies a client file list to server files in the current directory with the same name. The prompting feature is turned on in this case. The optional server file parameter has been omitted.

aftp> put appfcd*.*

Put APPFCDRH.H? (Yes,No,Go,Quit) y

Sending "/E:/WORK/APPFCDRH.H".

File was transferred in ASCII and stored as "/D:/AFTP/SERVER/APPFCDRH.H".

10002 bytes sent in 0.280 seconds (34.88 Kbytes/s)

Put APPFCDRO.C? (Yes,No,Go,Quit) n

Put APPFCDRO.OBJ? (Yes,No,Go,Quit) g

Sending "/E:/WORK/APPFCDRO.OBJ".

File was transferred in BINARY and stored as "/D:/AFTP/SERVER/APPFCDRO.OBJ".

3157 bytes sent in 0.150 seconds (20.55 Kbytes/s)

aftp>

Alias

send

Related Commands

alloc, ascii, binary, block, get, lrecl, prompt, recfm, type


PWD
The AFTP Program	40 of 51

AFTP Program Command Reference

PWD

Use this command to display the current directory of the AFTP server computer.

This command is valid only within the AFTP program. You must have an open connection to the server to issue this command.

Syntax

pwd

Examples

The AFTP server is on MVS, and the current directory is a partitioned data set:

aftp> pwd

"/neals.src.c/" is the server's current directory.

aftp>

The AFTP server is on MVS, and the current directory is a file prefix for a PDS or sequential file:

aftp> pwd

"/elaine.letter." is the server's current directory.

aftp>

The AFTP server is on VM:

aftp> pwd

"/b" is the server's current directory.

aftp>

The AFTP server is on Windows NT:

  aftp> pwd

"/e:/work/aftp/" is the server's current directory.

Related Commands

cd, lpwd


QUIT
The AFTP Program	41 of 51

AFTP Program Command Reference

QUIT

Use this command to exit the AFTP program.

This command is an alias of the exit command. See the exit command for usage information.

This command is valid only within the AFTP program.

Syntax

quit


RECEIVE (RECV)
The AFTP Program	42 of 51

AFTP Program Command Reference

RECEIVE (RECV)

Use this command to copy a file from the AFTP server to the AFTP client.

This command is an alias of the get command. See get for usage information.

Accepted abbreviation: recv

This command is valid only within the AFTP program. You must have an open connection to the server to issue this command.

Syntax

receive server_file [client_file]

recv server_file [client_file]

where

server_file

The name of the file on the server to be copied. Wildcards are permitted in the name to generate the list of files to copy.

client_file

The name on the client to which the server files are copied. Wildcards are permitted in this parameter to specify a list of filenames.

Default: use the same filename as on the server.


RECFM
The AFTP Program	43 of 51

AFTP Program Command Reference

RECFM

Use this command to set the record format to use when writing files (get to the AFTP client or put to the AFTP server). This value only takes effect when the files are stored on a computer that handles record-oriented files (for example, VM and MVS). On other systems, this value is ignored.

This command is valid only within the AFTP program. You must have an open connection to the server to issue this command.

Syntax

recfm [0 | V | VA | VB | VM | VS | VBA | VBM | VBS | VSA | VSM | VBSA | VBSM | F | FA | FB | FM | FBA | FBM | FBS | FBSM | FBSA | U | UA | UM]

Parameters

If no parameter is specified, the current setting is displayed.

0	The initial setting; sets the record format to the default record format used by C/370 runtime. See the IBM C/370 Programming Guide for specific information on the default value used.

V	Variable length record, unblocked.

VA	Variable length record, unblocked, ASA print-control characters.

VB	Variable length record, blocked.

VM	Variable length record, unblocked, machine print-control codes.

VS	Variable length record, unblocked, spanned.

VBA	Variable length record, blocked, ASA print-control characters.

VBM	Variable length record, blocked, machine print-control codes.

VBS	Variable length record, blocked, spanned.

VSA	Variable length record, unblocked, spanned, ASA print-control characters.

VSM	Variable length record, unblocked, spanned, machine print-control codes.

VBSA	Variable length record, blocked, spanned, ASA print-control characters.

VBSM	Variable length record, blocked, spanned, machine print-control codes.

F 	Fixed length record, unblocked.

FA	Fixed length record, unblocked, ASA print-control characters.

FB	Fixed length record, blocked.

FM	Fixed length record, unblocked, machine print-control codes.

FBA	Fixed length record, blocked, ASA print-control characters.

FBM	Fixed length record, blocked, machine print-control codes.

FBS	Fixed length record, blocked, spanned.

FBSM	Fixed length record, blocked, spanned machine print-control codes.

FBSA	Fixed length record, blocked, spanned ASA print-control characters.

U 	Undefined length record.

UA	Undefined length record, ASA print control characters.

UM	Undefined length record, machine print control codes.

Examples

Set the record format to variable:

aftp> recfm V

Record Format set to V.

aftp>

Reset the record format to the default:

aftp> recfm 0

Record Format set to Default.

aftp>

Related Commands

alloc, block, lrecl, status


RENAME (REN)
The AFTP Program	44 of 51

AFTP Program Command Reference

RENAME (REN)

Use this command to move a file on the AFTP server computer to a new name or directory. The use of the AFTP rename command is subject to the same limitations of rename commands native to the AFTP server’s operating system.

Platform Differences:

On MVS, you cannot rename a sequential file to a partitioned data set member. You cannot rename a member of one PDS to be a member of another PDS.

On VM, you cannot rename a file from one filemode to another.

On Windows NT, you cannot rename a file from one drive to another.

Accepted abbreviation: ren

This command is valid only within the AFTP program. You must have an open connection to the server to issue this command.

Syntax

rename old_filename new_filename

ren old_filename new_filename

where

old_filename

The file specification of the file on the AFTP server computer that is to be renamed. Wildcard characters are not permitted in this value.

new_filename

The file specification to which the file is to be renamed. Wildcard characters are not permitted in this value.

Examples

The following example renames a file to a new name in the current directory:

aftp> rename aftp.doc userman.txt

Renamed aftp.doc to userman.txt

aftp>

The following example renames a file to a new name in a new directory:

aftp> rename userman.txt e:\work\aftp.doc

Renamed userman.txt to e:\work\aftp.doc

aftp>


RMDIR (RD)
The AFTP Program	45 of 51

AFTP Program Command Reference

RMDIR (RD)

Use this command to remove a directory on the AFTP server computer.

Platform Differences:

This command is not supported on VM.

On MVS, this command will delete a partitioned data set and its members.

Accepted abbreviation: rd

This command is valid only within the AFTP program. You must have an open connection to the server to issue this command.

Syntax

rmdir directory_spec

rd directory_spec

where

directory_spec

The directory specification of the directory which is to be removed. Wildcard characters are not permitted in this value.

Examples

The following example removes a directory with a fully qualified path:

aftp> rmdir e:\work\test

Directory e:\work\test removed.

aftp>

Related Command

mkdir


SEND
The AFTP Program	46 of 51

AFTP Program Command Reference

SEND

Use this command to copy a file on the AFTP client to the AFTP server.

This command is an alias of the put command. See put for usage information.

This command is valid only within the AFTP program. You must have an open connection to the server to issue this command.

Syntax

send client_file [server_file]


STATUS (STAT)
The AFTP Program	47 of 51

AFTP Program Command Reference

STATUS (STAT)

Use this command to output the current transfer characteristics set by the AFTP client. Items such as the data type and date mode are output.

Accepted abbreviation: stat

This command is valid only within the AFTP program.

Syntax

status

stat

Examples

The output of this command may vary slightly on different operating systems.

In the following example, there is no connection to an AFTP server:

aftp> status

AFTP version is 1.0

Operating system is MVS

Mode Name       : "#BATCH"

TP Name         : "AFTPD"

aftp>

In the following example, there is a connection to an AFTP server:

aftp> status

AFTP version is 1.0

Operating system is MVS

Data Type       : DEFAULT

Date Mode       : NEW

Record Format   : Default

Record Length   : 0

Block Size      : 0

Allocation Size : 0

Mode Name       : "#BATCH"

TP Name         : "AFTPD"

aftp>

Related Commands

alloc, ascii, binary, block, date, lrecl, modename, recfm, tpname, type


SYSTEM (SYS)
The AFTP Program	48 of 51

AFTP Program Command Reference

SYSTEM (SYS)

Use this command to output information about the AFTP server computer. This can include the type of computer you are communicating with and the operating system. The information displayed will be system specific.

Accepted abbreviation: sys

This command is valid only within the AFTP program. You must have an open connection to the server to issue this command.

Syntax

system

sys

Example

The following example outputs system information about the AFTP server. The output of this command may vary slightly on different operating systems.

aftp> system

Server information:

AFTPD Version is 1.0

Operating system is Windows NT

Logged in userid is steved

aftp>


TRACE
The AFTP Program	49 of 51

AFTP Program Command Reference

TRACE

Use this command to set or query the current trace level. The trace level determines how much data is written into the trace log during AFTP command processing.

Typically, you will use this command only when directed to do so by your system administrator or by other support personnel trying to diagnose a problem.

This command is valid only within the AFTP program.

See "Log Trace Data" for additional information about AFTP tracing.

Syntax

trace [level]

where

If no parameter is specified, display the current setting.

level

A numeric value indicating trace level. A value of 0 turns tracing off, and is the initial setting. Use other values as directed by service personnel.

Examples

The following example checks the current trace level:

aftp> trace

Trace level: 0

The following example sets a new trace level:

aftp> trace 100

Trace level: 100


TPNAME
The AFTP Program	50 of 51

AFTP Program Command Reference

TPNAME

Use this command to change the transaction program name to be started on the server.

This command is valid only within the AFTP program. You cannot have an open connection when you issue this command.

Syntax

tpname [tp_name]

where

If no parameter is specified, the current setting is displayed.

tp_name

The name of the transaction program to start.

The initial setting is AFTPD.

Example

This example sets the TP name to MYAFTP.

aftp> tpname MYAFTP

TP Name set to "MYAFTP".

aftp>

Related Command

status


TYPE
The AFTP Program	51 of 51

AFTP Program Command Reference

TYPE

Use this command to view the current data type used for file transfers, or to change the current data type used for transfers. See “File Transfer Types” for a description of the possible data types.

This command is valid only within the AFTP program. You must have an open connection to the server to issue this command.

Syntax

type [ascii | binary | default]

Parameters

If no parameter is specified, display the current setting.

ascii

Set transfer type to ASCII.

binary

Set transfer type to binary.

default

Set AFTP to check the .INI file for transfer type. If no value is specified in the .INI file, ASCII will be used.

Examples

The following example sets the data type to binary, and then views the current value.

aftp> type binary

Data Type set to BINARY.

aftp> type

data type: BINARY

aftp>

The following example sets the data type to ASCII, and then views the current value.

aftp> type ascii

Data Type set to ASCII.

aftp> type

data type: ASCII

aftp>

Related Commands

ascii, binary, status


AFTP Server
Chapter 12	1 of 10

AFTP Server

Installation and configuration of the AFTP Server is accomplished in the following steps:

1.	Install SNA Server

2.	Configure APPC resources in SNA Server Admin

2.	Configure the AFTP Server

3.	Start the AFTP Server service

These steps are described below in detail.


Installation of AFTP Server
AFTP Server 	2 of 10

Installation of AFTP Server

The AFTP Server (AFTPD) is a Windows NT service installed on an SNA Server or on a Windows NT client of SNA Server by the SNA Server Setup program.

After Setup installs the AFTP Server, there is still some manual configuration to be done as detailed in the following sections.

The limit to the number of clients which can connect to the AFTP Server is the number of sessions supported by SNA Server (10,000). In reality, the user will probably encounter resource problems (running out of virtual memory) before that point.


Configuration of APPC Resources in SNA Server Admin
AFTP Server 	3 of 10

Configuration of APPC Resources in SNA Server Admin

The following APPC resources used by AFTP Server are configured in SNA Admin:

Local LU

Remote LU

Partner Mode

Instructions for configuring these resources are detailed in the following sections.


Configuring a Local LU
AFTP Server 	4 of 10

Configuration of APPC Resources in SNA Server Admin

Configuring a Local LU

The simplest configuration is appropriate for a single AFTP Server in an SNA Server domain. Although you can run AFTP Server on a Windows NT client of SNA Server, the recommendation is to run the AFTP Server on the computer running SNA Server.

The administrator of SNA Server must set up a Local LU for the AFTP Server to use in accepting a conversation.

To configure a Local LU for an AFTP Server running in the domain

1.	Start SNA Server Admin.

2.	Highlight the SNA server and select Assign LUs from the Services menu.

The Insert LU dialog box appears.

Note

If you plan to use the default APPC (Local) LU, created by the Setup program, for AFTP Server, please check the properties of the Local LU and change as necessary to match the values detailed in this procedure.

3.	Select the APPC (Local) button, if it is not already selected.

4.	Choose the OK button to close the dialog box.

The New APPC LU Properties dialog box appears.

5.	Place cursor in the LU Alias text entry box and enter an LU Alias name.

Note

The recommended name for LU Alias is the server name for this SNA server.

6.	Press the TAB key.

The LU Name box will be automatically filled in with the LU Alias name by default.

7.	Clear the Enable Automatic Partnering button.

8.	Choose the OK button to close the dialog box.

For specific instructions on configuring LUs for APPC, see Chapter 6 of the Microsoft SNA Server Administration Guide.

To configure for running multiple AFTP Servers in the SNA domain

1.	Define separate Local LUs for each AFTP Server.

2.	Assign a specific Local LU to each AFTP Server in the AFTPD registry entry (see “AFTPD Service: Location and Names of Variables” later in this chapter).


Configuring a Remote LU
AFTP Server 	5 of 10

Configuration of APPC Resources in SNA Server Admin

Configuring a Remote LU

The steps in configuring a remote LU are:

1.	Define the connections to SNA nodes supporting AFTP clients.

2.	Define a Remote LU on one connection and partner this with all Local LUs in use by AFTP Server. When creating the partnering, define the mode on the Local LU partner as #BATCH (the mode used by default by AFTP clients).

Unless you assign an implicit incoming remote LU and an implicit incoming mode (see note below), these steps must be repeated for each Remote LU (connection) and each Local LU (SNA server) in the domain that you would like the AFTP TP to communicate on.

Important

If you want to allow any AFTP client to use the AFTP Server, you can simplify your task by specifying one of the remote LUs as the implicit incoming remote LU with implicit incoming mode of #BATCH for each of the Local LUs.

However if you must restrict particular AFTP Servers to only some of the AFTP clients in your network, you must configure Remote LUs on only those connections and you must explicitly partner the Local LU with these Remote LUs.

For specific instructions on configuring servers and connections and for configuring LUs for APPC, see Chapters 3 and 6 of the Microsoft SNA Server Administration Guide, respectively.


Configuration of AFTP Server
AFTP Server 	6 of 10

Configuration of AFTP Server

After Setup installs the AFTP Server, you must:

Set user permissions in the AFTPSERV.INI file, to provide users access to specific directories.

The following steps are optional:

Set up file transfer defaults in the AFTPSERV.INI file to specify file mapping parameters used by the system receiving the files during a file transfer.

Set up the SNA conversation security, if desired.

These steps are described in the following sections.


Setting Up The AFTPSERV.INI File
AFTP Server 	7 of 10

Configuration of AFTP Server

Setting Up The AFTPSERV.INI File

Use the AFTP initialization file to set user permissions through the provide_access verb, and file transfer defaults though the map verb. Each of these verbs is described, with examples, in the following sections.

Important

If the AFTPD service is running and changes are made to the AFTPSERV.INI file, you will need stop and restart the AFTPD service (see “Starting and Stopping AFTP Server” for instructions) before the changes will take affect.

User Permissions

Once a user connects to the AFTP Server, that user’s permissions to access files are determined by the provide_access entries in the AFTPSERV.INI file.

You must specify a provide_access verb for the users who will connect to the AFTP Server, or the files will not be accessible through the AFTP Server and the users will receive an error message indicating that access has been denied.

The sample AFTPSERV.INI file provided on the CD-ROM has several of these entries, and provides some documentation.

The syntax for this verb is as follows:

provide_access

users(username [...] | anonymous | *)

directory(drive:\directory | *)

permissions(read | write | read write | *)

;

where

username

Specify one or more users, separated by spaces, up to a maximum of 16. Only users logging on with this username will be granted permissions to the directory specified.

Specify * to give permission to the directory specified to any user who enters a valid user ID. User IDs are checked for validity by the SNA Server software. If conversation security is not specified, any user ID, in combination with any characters entered for the password, will be treated as a valid user. If conversation security is specified, then the SNA Server software only lets an AFTP client connect to an AFTP server if the user ID and password combination matches that specified in the AFTP Server’s registry entry.

Specify anonymous to give permission to any user who logs on to the AFTP Server, regardless of whether they enter a User ID and password, or use the anonymous logon. Note that if the AFTP Server is configured for conversation security, then the anonymous logon will not connect (since it provides no User ID and password), and any User ID and password will be checked for validity by the SNA Server software.

directory

Specify the path of the directory that this user will have access to, or specify the value “*” for access to all directories on the AFTP Server.

The AFTP Server will only let a client access hard drives and CD-ROM drives on the AFTP Server. It will not let the client access floppy drives or network drives.

Note

It is highly recommended that you do not use the value “*” and assign users access to all directories on the AFTP Server.

permissions

Specify the user (or users) permissions to read and/or write files in a certain directory, and all subdirectories of that directory.

A user can have more than one provide_access entry, to grant permission to access more than one directory.

In the AFTP initialization file, verbs are followed by parameter values. Parameter values are enclosed within parentheses. A semicolon (;) is used after the last parameter value to indicate the end of the verb. Verbs and parameters are not case sensitive. Blanks, carriage returns, and tabs are ignored. You can use comments in initializating the files (/* */), but comments cannot be nested (/* /* */ */).

For examples, see the sample AFTPSERV.INI file later in this chapter.

Setting Up File Transfer Defaults

Filename mapping defaults and transfer type defaults are defined using the map verb and are applied by the system receiving the file, whether client or server. When a file is transferred from one system to another, if the file specification on a source_mask parameter matches the name of the file being transferred, AFTP applies the defaults defined in the associated target_mask and options parameters. When the AFTP programs search for a match, each source_mask parameter is read until a match is found. All map verbs that follow the verb containing the match are ignored.

The syntax for this verb is as follows:

map source_mask(value) target_mask(value) options(value);

where

source_mask(value)

Specifies a filename or file type to map.

If the source_mask matches the name of the file being transferred, the file name mapping defaults defined on the target_mask and options parameters are applied.

The source_mask parameter value can contain any valid filename character and the wildcard characters asterisk (*) and question mark (?).

target_mask(value)

Specify how to name the file or files defined on the source_mask parameter on the target computer.

The target_mask parameter value can contain any valid filename character and the wildcard characters asterisk (*) and question mark (?). Characters or wildcards can be enclosed in brackets to indicate that those parts of the filename are to be omitted from the file name on the target system.

options(value)

The options parameter is optional and is used to specify which file transfer type to use when transferring a file that matches the source_mask parameter.

These are the values you can use on the options parameter:

binary

When the options parameter is set to binary, the file is transferred as a stream of binary bytes.

ASCII

When the options parameter is set to ascii, the file is transferred in ASCII.

Note

The filename mapping defaults are applied by the system receiving the file, whether client or server. This applies to the name mapping, and to the choice of whether to use binary, ASCII, or the default.

The client and server can use the same AFTP.INI file. By default the server will use the AFTPSERV.INI file, but that can be changed by editing the registry entry.

The client and server find their configuration files in this way:

The client always opens the AFTP.INI file in the directory where the AFTP.EXE binary is located (this is not necessarily the current directory).

The server picks up the name of its file from the registry entry AFTPIniFile, which is found in the HKEY_LOCAL_MACHINE registry, as described in the section “AFTPD Service: Location and Names of Variables”. The Setup program sets this to be drive:\SNARoot\SYSTEM\AFTPSERV.INI by default, where drive is the drive letter of the hard drive and SNARoot is the directory where SNA Server is being installed.

Examples

A few examples of file transfer default settings are shown in the following table.

Source file name	Source mask	Target mask	Mapped file name
INSTALL.SCRIPT	*.SCRIPT	*.SCR	INSTALL.SCR
PROGRAM.EXEBIN	*.*BIN	*.*[BIN]	PROGRAM.EXE
USER.DOCUMENT	*.DOCUMENT	*.DOC	USER.DOC
For more file transfer default examples, see the sample AFTP.INI file later in this chapter.

SAMPLE AFTPSERV.INI FILE

The following is a sample AFTPSERV.INI file, which is also included on the CD.

Note

All of the provide_access verbs have been commented out. Therefore, * by default no users will have access to any files.

/*****************************************************************/

/*	*/

/* aftpserv.ini	*/

/*	*/

/* Template for AFTP Server config file	*/

/*****************************************************************/

/*

This is an example of how to give the user "steved" read/write access to all the files on the c: drive and the d: drive

provide_access

    users(steved)

    directory(c:)

    permissions(read write)

    ;

provide_access

    users(steved)

    directory(d:)

    permissions(read write)

    ;

*/

/*****************************************************************/

/*****************************************************************/

/*

The following is an example of providing a user "daring" read/write access to the files in d:\myfiles (and any subdirectories).

provide_access

    users(daring)

    directory(d:\myfiles)

    permissions(read write)

    ;

*/

/*****************************************************************/

/*****************************************************************/

/*

The following example shows how to provide read-only access for all users other than "anonymous"

provide_access

    users(*)

    directory(d:\files\)

    permissions(read)

    ;

*/

/*****************************************************************/

/*****************************************************************/

/*

The following examples show how to provide access for people who connect without security information ("anonymous").

provide_access

    users(anonymous)

    directory(c:\public\)

    permissions(read)

    ;

provide_access

    users(anonymous)

    directory(c:\public\write\)

    permissions(read write)

    ;

*/

/*

 *

 * This list of mappings is used by the AFTP server when the client
 * sends a file.

 *

 */

map source_mask(*.NONE)     target_mask(*.)       options();

map source_mask(*.LABEL)    target_mask(*.LBL)    options();

map source_mask(*.NONEBIN)  target_mask(*.)       options(binary);

map source_mask(*.ASSEMBLE) target_mask(*.A37)    options();

map source_mask(*.LISTPS)   target_mask(*.PS)     options(binary);

map source_mask(*.APLTF   ) target_mask(*.ATF)    options(binary);

map source_mask(*.EXEC    ) target_mask(*.EXC)    options();

map source_mask(*.PACKAGE ) target_mask(*.PKG)    options();

map source_mask(*.SCRIPT  ) target_mask(*.SCR)    options();

map source_mask(*.NEWS )    target_mask(*.NEW)    options();

map source_mask(*.DOCUMENT) target_mask(*.DOC)    options();

map source_mask(*.BOOK    ) target_mask(*.BOO)    options(binary);

map source_mask(*.ARC     ) target_mask(*.*  )    options(binary);

map source_mask(*.*BIN    ) target_mask(*.*[BIN]) options(binary);

map source_mask(*.BAS     ) target_mask(*.*  )    options(binary);

map source_mask(*.CFG     ) target_mask(*.*  )    options(binary);

map source_mask(*.COM     ) target_mask(*.*  )    options(binary);

map source_mask(*.EXE     ) target_mask(*.*  )    options(binary);

map source_mask(*.FLS     ) target_mask(*.*  )    options(binary);

map source_mask(*.PRS     ) target_mask(*.*  )    options(binary);

map source_mask(*.LIB     ) target_mask(*.*  )    options(binary);

map source_mask(*.OBJ     ) target_mask(*.*  )    options(binary);

map source_mask(*.PIC     ) target_mask(*.*  )    options(binary);

map source_mask(*.RAM     ) target_mask(*.*  )    options(binary);

map source_mask(*.SYS     ) target_mask(*.*  )    options();

map source_mask(*.WKS     ) target_mask(*.*  )    options(binary);

map source_mask(*.WK1     ) target_mask(*.*  )    options(binary);

map source_mask(*.WK3     ) target_mask(*.*  )    options(binary);

map source_mask(*.ZIP     ) target_mask(*.*  )    options(binary);

map source_mask(*.AVAIL   ) target_mask(*.AVL)    options();

map source_mask(*.PLAS    ) target_mask(*.PLS)    options();

map source_mask(*.BMP     ) target_mask(*.*  )    options(binary);

map source_mask(*.DLG     ) target_mask(*.*  )    options(binary);

map source_mask(*.DLL     ) target_mask(*.*  )    options(binary);

map source_mask(*.ICO     ) target_mask(*.*  )    options(binary);

map source_mask(*.FNT     ) target_mask(*.*  )    options(binary);

map source_mask(*.PTR     ) target_mask(*.*  )    options(binary);

map source_mask(*.RES     ) target_mask(*.*  )    options(binary);

map source_mask(*.ANNOUNCE) target_mask(*.ANN)    options();

map source_mask(*.DOC     ) target_mask(*.DOC)    options();

map source_mask(*.CATALOG ) target_mask(*.CAT)    options();

map source_mask(*.IMG     ) target_mask(*.*  )    options(binary);

map source_mask(*.KPS     ) target_mask(*.*  )    options(binary);

map source_mask(*.KPL     ) target_mask(*.*  )    options(binary);

map source_mask(*.PAL     ) target_mask(*.*  )    options(binary);

map source_mask(*.PLX     ) target_mask(*.*  )    options();

map source_mask(*.R1P     ) target_mask(*.*  )    options(binary);

map source_mask(*.WRK     ) target_mask(*.*  )    options(binary);

map source_mask(*.TERSE   ) target_mask(*.TER)    options(binary);

map source_mask(*.TERS3820) target_mask(*.T38)    options(binary);

map source_mask(*.BKINDEX)  target_mask(*.BKI)    options(binary);

map source_mask(*.BKSHELF)  target_mask(*.BKS)    options();

map source_mask(*.CDR)      target_mask(*.*)      options(binary);

map source_mask(*.CGM)      target_mask(*.*)      options(binary);

map source_mask(*.RFT)      target_mask(*.*)      options(binary);

map source_mask(*.RFTD)     target_mask(*.RFT)    options(binary);

map source_mask(*.RFTF)     target_mask(*.RFT)    options(binary);

/*

 * The following line maps source filenames with extensions longer

 * than three characters to target names with truncated

 * three-character extensions compatible with FAT filesystems.  Files

 * with extensions not matching any of the above will be mapped

 * with this rule.

 * If you are using the NTFS filesystem and don't want truncated

 * extensions, comment out the following line.

 *

 * Note that this should be the LAST map command in this file. AFTP

 * scans the list of source masks in the order in which they are

 * given in this file, and stops at the first match. Since this map

 * command is intended to be used only when no other source masks are

 * matched, it must be the last map command in the file.

 */

map source_mask(*.???*)        target_mask(*.???[*]) options();


Environment Settings for SNA Server
AFTP Server 	8 of 10

Configuration of AFTP Server

Environment Settings for SNA Server

The AFTP Server is an operator started invokable APPC transaction program (TP). Registry settings allow you to specify the path and filename for the AFTP configuration file, and to set up conversation security.

AFTPD Service: Location and Names of Variables

The Registry variables that affect the AFTPD service on SNA Server are installed automatically by the Setup program. The settings are found in the following location in the Registry:

HKEY_LOCAL_MACHINE

SYSTEM

CurrentControlSet

Services

AFTPD

Parameters

The variables are as follows:

AFTPIniFile:REG_EXPAND_SZ:{ drive:\path\filename }     Default: C:\SNA\SYSTEM\AFTPSERV.INI

Use this variable to specify the path and name for the AFTPD configuration file.

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

This variable determines whether or not user passwords are checked when clients connect to the AFTP Server.

When this variable is set to YES the user password is checked before the TP is invoked.

Important

One of the side effects of the security/logon procedure is that if the AFTP Server is configured for conversation security, then users cannot use the anonymous logon.

When this variable is set to NO (default value) the user’s password is not checked before the TP is invoked. This has the result that the user can enter any password, and he will be logged on successfully.

The anonymous user does not enter a password when he logs on. Therefore anyone can connect to the AFTP Server as “anonymous.”

All other users are required by the AFTP client to enter a password. This password flows in the APPC ALLOCATE verb, and is checked by Windows NT at the AFTP Server. For this reason the AFTPSERV.INI file does not contain passwords.

LocalLU:REG_SZ:localLUalias      Default:

Specified Local LU alias that this server should use. If blank, which is the default, server accepts sessions from any client.

If not blank, server only accepts conversations from AFTP clients which allocate to this LU (by specifying the LU Name explicitly with the fully qualified LU Name, or implicitly using a symbolic destination name) on their open command.

Note

This is the standard way of invoking TPs on particular SNA Server clients. For more information, see the Microsoft SNA Server APPC Programmer’s Guide.


Starting and Stopping AFTP Server
AFTP Server 	9 of 10

Starting and Stopping AFTP Server

By default, the AFTPD service has a Startup setting of “Manual.” The service has to be started and stopped manually by the operator.

To start the AFTP Server:

Open the Services applet from the Control Panel program group of Microsoft Windows NT. Highlight the AFTPD service. Choose the Start button.

or

Type net start aftpd from the command line.

To stop the AFTP Server:

Open the Services applet from the Control Panel program group of Microsoft Windows NT. Highlight the AFTPD service. Choose the Stop button.

or

Type net stop aftpd from the command line.


Diagnostics
AFTP Server 	10 of 10

Diagnostics

The two main source of diagnostics are:

The event log.

APPC and CPIC API tracing.