Quick Beggin Ers

IBM Communications Server for AIX
Quick Beginnings
V6. 4
GC31-8583-04
IBM Communications Server for AIX
Quick Beginnings
V6. 4
GC31-8583-04
Note: Before using this information and the product it supports, be sure to read the general information under Notices, on page 109.
Fifth Edition (May 2009) This edition applies to Version 6 Release 4 of Communications Server for AIX (5765-E51) and to all subsequent releases and modifications until otherwise indicated in new editions or technical newsletters. Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address below. IBM welcomes your comments. You may send your comments to the following address: International Business Machines Corporation Attn: Communications Server for AIX Information Development Department AKCA, Building 501 P.O. Box 12195, 3039 Cornwallis Road Research Triangle Park, North Carolina 27709-2195 U.S.A. You can send us comments electronically by using one of the following methods: v Fax (USA and Canada): 1+919-254-4028 Send the fax to Attn: Communications Server for AIX Information Development v Internet e-mail: comsvrcf@us.ibm.com When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Copyright International Business Machines Corporation 2000, 2009. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
Tables . . . . . . . . . . . . . . . v Figures . . . . . . . . . . . . . . vii Welcome to IBM Communications Server for AIX . . . . . . . . . . . . ix
How to Use This Book . . . . . . . . . . . ix Road Map . . . . . . . . . . . . . . ix Typographic Conventions . . . . . . . . . x Abbreviations Used in This Book . . . . . . x Whats New . . . . . . . . . . . . . . xi New Functions . . . . . . . . . . . . xii Functions That Have Been Retired. . . . . . xii Where to Find More Information . . . . . . . xiii Installing Data Link Control Filesets . . . . Displaying Product Installation Details . . . Changing the Language Environment Variable Migrating from previous levels of CS/AIX . . . Considerations . . . . . . . . . . . Installing the CS/AIX Licensed Program . . . Installation Methods . . . . . . . . . Configuring WebSphere Application Server . . . Setting up the WebSphere Application Servers secure certificate . . . . . . . . . . . Configuring WebSphere Application Server . . Installing the server configuration file . . . Post-Installation Procedures . . . . . . . . Client/Server Operation . . . . . . . . Viewing PDF Books . . . . . . . . . Reviewing Current Release Information . . . Configuring SSL for use with TN Server or TN Redirector . . . . . . . . . . . . . Configuring a Web Server for the Web Administration Program . . . . . . . . Host Access Class Library . . . . . . . Backing Up CS/AIX Configuration Files. . . Restoring a Backup Copy of CS/AIX Configuration Files . . . . . . . . . . Reinitializing Configuration Files . . . . . . . . . . . . . . . . . . . . 31 31 31 32 32 32 33 36 36 36 37 37 38 38 38
Chapter 1. About IBM Communications Server for AIX . . . . . . . . . . . . 1

IBM Communications Server for AIX Features and Packaging . . . . . . . . . . . . . . IBM Communications Server for AIX V6.4 . . Advanced Networking Features . . . . . . Features and Benefits . . . . . . . . . . Versatile Building Blocks . . . . . . . . Client/Server Operation . . . . . . . . Easy Configuration . . . . . . . . . . Additional User Interface Choices for Administration . . . . . . . . . . . Better Performance . . . . . . . . . . Security Options. . . . . . . . . . . Network Management Flexibility . . . . . Reliability, Availability, and Serviceability . . Network Integration, Growth, and Change . . . 1 . 1 . 6 . 11 . 11 . 12 . 12 . . . . . . 13 13 14 14 15 15
. 38 . 39 . 39 . 39 . 40 . 40
Chapter 4. Installing IBM Remote API Clients on Linux . . . . . . . . . . 43

Hardware and Software Requirements . . . . Hardware Requirements . . . . . . . . Linux Operating System Version . . . . . Java . . . . . . . . . . . . . . . GSKIT . . . . . . . . . . . . . . Displaying Product Installation Details . . . Setting the Language Environment Variable . Installing the Remote API Client on Linux . . . Setting up HTTPS security certificates using GSKIT Uninstalling the Remote API Client on Linux . . . . . . . . . . 43 43 44 44 44 44 44 45 46 . 47
Chapter 2. Planning for Your Network and IBM Communications Server for AIX . . . . . . . . . . . . . . . . 17
Stages of Network Planning . . . . . . . Identifying Functional Requirements for the Network . . . . . . . . . . . . Determining How to Configure CS/AIX . . Identifying Resource Requirements for Installation and Operation . . . . . . IPv4 and IPv6 Addressing . . . . . . . Ensuring Compatibility among Cross-Platform Configurations . . . . . . . . . . . Naming Conventions . . . . . . . . . . . . . . . . . 17 . 17 . 18 . 18 . 23 . 25 . 25
Chapter 5. Installing IBM Remote API Clients on Linux for System z . . . . . 49

Hardware and Software Requirements . . . . Hardware Requirements . . . . . . . . Linux Operating System Version . . . . . Java . . . . . . . . . . . . . . . GSKIT . . . . . . . . . . . . . . Displaying Product Installation Details . . . Setting the Language Environment Variable . Installing the Remote API Client on Linux for System z . . . . . . . . . . . . . . Setting up HTTPS security certificates using GSKIT Uninstalling the Remote API Client on Linux for System z . . . . . . . . . . . . . . . . . . . . . 49 49 49 49 49 50 50
Chapter 3. Installing CS/AIX on AIX Servers . . . . . . . . . . . . . . 27

CS/AIX Licensing and Packaging . . CS/AIX Licensing Mechanisms . . How the CS/AIX Licensed Program Preparing for CS/AIX Installation . .
Copyright IBM Corp. 2000, 2009
. . Is .
. . . . . . . . Packaged . . . .
27 27 29 30
. 50 52 . 53
iii
Chapter 6. Installing IBM Remote API Clients on AIX Systems . . . . . . . 55

Hardware and Software Requirements . . . . . Hardware Requirements . . . . . . . . . Operating System Version . . . . . . . . Java . . . . . . . . . . . . . . . . GSKIT . . . . . . . . . . . . . . . Changing the Language Environment Variable . Installing the Remote API Client on AIX. . . . . Installing the Remote API Client by copying files to your AIX workstation . . . . . . . . . Installing the Remote API Client from the CD . . Setting up HTTPS security certificates using GSKIT Uninstalling the Remote API Client on AIX. . . . 55 55 55 55 55 55 56 56 57 57 58
Chapter 7. Planning for and Installing the Remote API Client on Windows . . 59
Hardware and Software Requirements . . . . . Accessing the Setup Program . . . . . . . . Installing Remote API Client on Windows Using the Setup Program . . . . . . . . . . . . . Advanced Options for Remote API Client Configuration . . . . . . . . . . . . . Installing Remote API Client Software from the Command Line . . . . . . . . . . . . . Setting up HTTPS security certificates using GSKIT Customizing the Remote API Client Software after Installation . . . . . . . . . . . . . . Reinstalling the Remote API Client Software . . . Uninstalling the Remote API Client Software . . . Uninstalling the Remote API Client Software from the Command Line . . . . . . . . . . . . Help. . . . . . . . . . . . . . . . . 59 60 61 64 64 66 67 67 68 68 69
Configuring an Enterprise Extender Link . . Configuring Type 03 LUs . . . . . . . . Defining Type 03 LUs . . . . . . . . Defining an LU Pool . . . . . . . . . Configuring APPC Communication . . . . . Configuring a Simple APPN Network . . . Configuring Dependent APPC . . . . . . Configuring for CPI Communications . . . . Configuring LUA . . . . . . . . . . . Configuring SNA Gateway . . . . . . . . Supporting Implicit Downstream LUs . . . Defining Downstream LUs . . . . . . . Configuring DLUR . . . . . . . . . . . Configuring DLUR Support on the Local Node Configuring Passthrough DLUR Support for Downstream Nodes . . . . . . . . . Configuring TN Server . . . . . . . . . Defining 3270 LUs . . . . . . . . . . Defining an LU Pool . . . . . . . . . Configuring TN3270 Server. . . . . . . Configuring TN Redirector . . . . . . . . Configuring TN Redirector . . . . . . . Configuring AnyNet . . . . . . . . . . Configuring APPC over TCP/IP . . . . . Disabling CS/AIX . . . . . . . . . . .
. . . . . . . . . . . . .
83 84 84 85 86 87 91 91 92 92 94 94 95 96
. 97 . 97 . 99 . 100 . 101 . 102 . 102 . 103 . 103 . 105
Chapter 9. Information Resources for CS/AIX and SNA . . . . . . . . . . 107

SNA Library. . . . . . . . Network-Accessible Information . Suggested Reading . . . . . . . . . . . . . . . . . . . . . 107 . 107 . 108
Appendix. Notices . . . . . . . . . 109

Trademarks . . . . . . . . . . . . . . 111
Chapter 8. Configuring and Using CS/AIX . . . . . . . . . . . . . . . 71

Planning for CS/AIX Configuration . . . . . . Planning Worksheets . . . . . . . . . . Task Sheets . . . . . . . . . . . . . Using the Motif Administration Program . . . . Specifying the Path to CS/AIX Programs . . . Enabling CS/AIX . . . . . . . . . . . Managing CS/AIX with the Motif Administration Program . . . . . . . . . . . . . . Configuring Client/Server Functions . . . . . . Configuring the Node . . . . . . . . . . . Configuring Connectivity . . . . . . . . . . Configuring an SDLC Link for Dependent Traffic Configuring an Ethernet Link to Support Dependent and Independent Traffic . . . . . 72 72 73 73 73 73 74 78 79 80 81 82
Bibliography . . . . . . . . . . . . 113
CS/AIX V6.4 Publications . . . . . . . . IBM Redbooks . . . . . . . . . . . . AIX Operating System Publications . . . . . Systems Network Architecture (SNA) Publications Host Configuration Publications . . . . . . z/OS Communications Server Publications . . TCP/IP Publications . . . . . . . . . . X.25 Publications . . . . . . . . . . . APPC Publications . . . . . . . . . . Programming Publications . . . . . . . . Other IBM Networking Publications . . . . . . 113 . 114 . 114 115 . 115 . 115 . 115 . 116 . 116 . 116 . 116
Index . . . . . . . . . . . . . . . 117
iv
IBM Communications Server for AIX Quick Beginnings
Tables
1. Getting Started Road Map . . . . . . . . ix 2. Typographic Conventions . . . . . . . . x
vi
Figures
1. 2. 3. 4. 5. 6. SNA Gateway Linking Multiple Downstream AIX Computers to a Host Computer . . . Branch Extender . . . . . . . . . . TN Server . . . . . . . . . . . . Node Window . . . . . . . . . . CS/AIX Tool Bar . . . . . . . . . . CS/AIX Node That Communicates Directly with a Host . . . . . . . . . . . . 7 . 8 . 10 . 75 . 77 . 79 7. 8. 9. 10. 11. 12. 13. CS/AIX Nodes in an APPN Network . . SNA Gateway . . . . . . . . . . CS/AIX Node Providing DLUR . . . . CS/AIX Node Configured for TN Server TN Server . . . . . . . . . . . AnyNet APPC over TCP/IP Access Node AnyNet APPC over TCP/IP Gateway . . . . . 80 . 93 . 96 98 . 99 103 103
vii
viii
Welcome to IBM Communications Server for AIX

This book introduces IBM Communications Server for AIX, an IBM software product that enables a server running IBMs Advanced Interactive Executive (AIX) operating system to exchange information with other nodes in a Systems Network Architecture (SNA) network. It is the most comprehensive SNA networking product currently available for workstations running the AIX operating system. IBM Communications Server for AIX is designed to run on an AIX workstation connected to one or more networks. CS/AIX V6.4 will run on any IBM RISC System/6000or eServer pSeries system that is supported by AIX Version 5.2, 5.3 or 6.1. In this book, the term AIX workstation is used to indicate any of these systems with the AIX operating system installed. CS/AIX provides building blocks for a wide variety of networking needs and solutions. They can be used to exchange information with nodes in SNA networks, Transmission Control Protocol/Internet Protocol (TCP/IP) networks, and integrated SNA-TCP/IP networks.
How to Use This Book

This section explains how information is organized and presented in this book.
Road Map
This book is for management and technical personnel involved in network planning, and for anyone interested in Communications Server for the AIX operating system. To find the information you need to get started with CS/AIX, use Table 1.
Table 1. Getting Started Road Map If you want to... Read about CS/AIX Refer to... Chapter 1, About IBM Communications Server for AIX, on page 1 Chapter 2, Planning for Your Network and IBM Communications Server for AIX, on page 17 Chapter 3, Installing CS/AIX on AIX Servers, on page 27 Chapter 4, Installing IBM Remote API Clients on Linux, on page 43 Chapter 5, Installing IBM Remote API Clients on Linux for System z, on page 49 Chapter 6, Installing IBM Remote API Clients on AIX Systems, on page 55
Plan how to use CS/AIX in your network
Install CS/AIX on AIX servers Install Remote API Clients on Linux (32bit Intel, 64bit Intel/AMD, or pSeries) Install Remote API Clients on Linux for System z
Install Remote API Clients on AIX
ix

Table 1. Getting Started Road Map (continued) If you want to... Install Remote API Clients on Windows Refer to... Chapter 7, Planning for and Installing the Remote API Client on Windows, on page 59 Chapter 8, Configuring and Using CS/AIX, on page 71 Chapter 9, Information Resources for CS/AIX and SNA, on page 107 Notices, on page 109
Configure CS/AIX Find information about the CS/AIX documentation and other publications, including online information Read notices and trademark information
Typographic Conventions
The typographic styles used in this document are shown in Table 2.
Table 2. Typographic Conventions Special Element Emphasized words Document title File or path name Program or application User input Computer output Sample of Typography back up files before deleting IBM Communications Server for AIX Administration Guide /usr/spool/uucp/myfile.bkp snaadmin 0p1 CLOSE
Abbreviations Used in This Book

This book uses the following abbreviations:
AIW AIX ANR API APPC APPN ATM BOS BrNN CICS COS CPI-C CSV DB2 DDDLU DES DLC DLUR DLUS FDDI FTP HPR APPN Implementers Workshop Advanced Interactive Executive Automatic network routing Application Programming Interface advanced program-to-program communication Advanced Peer-to-Peer Networking Asynchronous Transfer Mode Base operating system Branch Network Node Customer Information Control System Class of Service Common Programming Interface for Communications Common Service Verb DATABASE 2 Dynamic Definition of Dependent LUs data encryption standard Data link control Dependent LU Requester Dependent LU Server Fiber Distributed Data Interface File Transfer Protocol High-Performance Routing

IEEE IETF ISO ISR LAN LDAP LEN LLC2 LU LUA MDS-NMVT MPC MPQP MPTN MS NMVT NOF OS/2 OSI PU RFC RISC RLE RTP SAA SAP SDLC SLP SMIT SMP SNA SNMP-MIB SSL TCP/IP TN TP VT VTAM WAN Institute of Electrical and Electronics Engineers Internet Engineering Task Force International Organization for Standards Intermediate session routing Local area network Lightweight Directory Access Protocol Low-entry networking Logical Link Control 2 Logical unit Conventional LU Application Programming Interface Multiple Domain SupportNetwork Management Vector Transport MultiPath Channel Multiprotocol Quad Port Multiprotocol Transport Networking Management Services Network Management Vector Transport Node Operator Facility Operating System/2 Open Systems Interconnection Physical unit Request For Comments Reduced Instruction Set Computer Run-Length Encoding Rapid Transport Protocol Systems Application Architecture Service access point Synchronous Data Link Control Service Location Protocol Systems Management Interface Tool Symmetric multiprocessing Systems Network Architecture Simple Network Management ProtocolManagement Information Base Secure Sockets Layer Transmission Control Protocol/Internet Protocol Telnet Transaction program Virtual Terminal Virtual Telecommunications Access Method Wide area network
Whats New
Communications Server for AIX V6.4 replaces Communications Server for AIX V6.3.1. Releases of this product that are still supported are: v Communications Server for AIX V6.3.1 v Communications Server for AIX V6.3.0 The following releases of this product are no longer supported: v Communications Server for AIX Version 6.1 (V6.1) v Communications Server for AIX Version 6 (V6) v Communications Server for AIX Version 5 (V5)
xi
Whats New
v v v v v Communications Server for AIX Version 4 Release 2 (V4R2) Communications Server for AIX Version 4 Release 1 (V4R1) SNA Server for AIX Version 3 Release 1.1 (V3R1.1) SNA Server for AIX Version 3 Release 1 (V3R1) AIX SNA Server/6000 Version 2 Release 2 (V2R2)
v AIX SNA Server/6000 Version 2 Release 1 (V2R1) on AIX 3.2 v AIX SNA Services/6000 Version 1 Communications Server for AIX V6.4 operates with the IBM Remote API Client Version 6.4.0, 6.3.1 or 6.3.0.
New Functions
The following functions have been added to CS/AIX in this release: v You can specify a mapping between TN3270 device types and the LU models that CS/AIX should request from the host when these devices connect through CS/AIX TN Server using DDDLU. This allows you to use the most appropriate LU model for each type of device. v High Performance Routing (HPR) now includes additional configuration options: ARB progressive mode operation (also known as ARB-P), which improves HPR flow control when dealing with response time variations on virtual and remote systems. A configurable path switch delay timer, which helps to avoid unnecessary path switches caused by transient delays in network traffic. v The APPC interface includes a new verb CANCEL_CONVERSATION, which allows you to deallocate a conversation even if other verbs are still outstanding. This verb operates in a similar way to the CPI-C Cancel_Conversation (cmcanc) call, and is available on AIX, Linux and Windows. v On an IBM Remote API Client for Windows, you can now run utility programs (the Client Configuration Utility sxclconf, the Client Monitor sxclappl, and the command-line utility tpinst32 for configuring an invokable TP) in any supported language; you are not restricted to the language that you used when installing the client. v On an IBM Remote API Client for Windows, the Client Configuration Utility sxclconf now allows you to enable or disable exception logging, audit logging, and tracing (API tracing on all APIs, and client/server tracing on messages between the client and the server). v Java CPI-C applications are now supported on an IBM Remote API Client for Windows, as well as on AIX and Linux.
Functions That Have Been Retired

The AnyNet APPC over TCP/IP function is still supported in this release, but only on 32bit systems with IPv4 interfaces, and not on 64bit systems nor with IPv6 interfaces. It will not be supported in future releases. In V6.4, the AnyNet driver is not loaded by default. If you need to use AnyNet APPC over TCP/IP, edit the file /etc/rc.sna, and follow the comments at the start of the file to enable AnyNet.
xii
Where to Find More Information
Where to Find More Information

The Bibliography identifies other books in the CS/AIX library, as well as books that contain additional information about SNA, the AIX operating system, and other related products.
xiii
xiv
Chapter 1. About IBM Communications Server for AIX

This chapter explains how CS/AIX is packaged and describes its functions, features, and benefits.
IBM Communications Server for AIX Features and Packaging

CS/AIX V6.4 is communication software that runs on the AIX operating system. It consists of the features described in IBM Communications Server for AIX V6.4 and Advanced Networking Features on page 6.
IBM Communications Server for AIX V6.4

IBM Communications Server for AIX V6.4 connects applications across SNA and TCP/IP networks. It converts a workstation running AIX into an SNA node by equipping it with SNA resources and protocols; this enables the workstation to communicate with other computers in an SNA network, including host computers. It also provides TCP/IP functions to allow IBM Communications Server for AIX to be used within your TCP/IP network or at the boundary between TCP/IP and SNA networks. CS/AIX provides the following services: Network Support CS/AIX supports subarea and peer-to-peer networks: SNA Subarea Networks These networks (also known as host-mediated networks) are hierarchically organized, with one or more host computers controlling communication between computers, managing the network, and providing processing services and high-capacity data storage. All other nodes in the network are dependent on the control of a host. AIX computers can participate in a subarea network by being configured as host-dependent nodes. Peer-to-Peer Networks For distributed processing environments, CS/AIX V6.4 supports APPN and TCP/IP networks. In these peer-to-peer networks, AIX computers retain processing functions and communicate directly with each other as peers. Peer-to-peer networks fully use the capability of the AIX computer, which today rivals that of expensive host computers. An APPN network consists of peer nodes of the following types: v APPN network node (which provides traffic control, dynamic route computation and selection services, and network management services) v APPN end node (which uses APPN network node services to communicate with peer nodes) v LEN node (which communicates directly with adjacent nodes or nodes configured to appear adjacent)

Note: Host computers can function as peer nodes in an APPN network by using independent LU 6.2 to communicate with AIX computers and other hosts in the network. Providing Subarea Functions in an APPN Network The dependent LU requester (DLUR) function enables traffic between hosts and host-dependent nodes to be carried in an APPN network. Data Link Control Options At the link level, CS/AIX offers many connectivity options to help you meet your networks size, speed, security, and cost considerations. (For a detailed list of the link types supported, see Installation Requirements on page 20.) It supports data links for different network types, as follows: Local Area Networks For LAN connectivity, you can install the appropriate links to communicate using token ring, standard Ethernet, and 802.3 Ethernet protocols. (ATM support can be provided using an emulated LAN interface on a token ring or Ethernet network.) Wide Area Networks For WAN connectivity, you can select from the following synchronous links to communicate over established telephone lines: v EIA-232D v v v v v Smart modem X.21 EIA-422A V.25 bis V.35
CS/AIX also supports X.25 packet-switched data link control.(These link types require additional separately orderable products.) IP Integration If your corporate backbone network is based on IP, you can use the Enterprise Extender (HPR/IP) feature of CS/AIX to integrate this with SNA, allowing your SNA applications to communicate over the IP network. LU Support Logical units (LUs) are application-specific network resources that reside on each node in an SNA network. Each LU acts as an interface that applications use to access links in order to communicate over the network with partner applications on other nodes. CS/AIX supports different types of LUs for different classes of applications. v In a subarea network, CS/AIX supports dependent LUs, which can be any of the following types: LU LU LU LU LU 0 1 2 3 6.2

LU 0 supports primitive program-to-program communication, typically used at point-of-sale transactions in retail and banking. LU 2 supports terminal emulation applications that enable the AIX computer to emulate an IBM 3270-family terminal. The other LU types enable applications to participate in distributed processing or to communicate with various printers or interactive display terminals. CS/AIX supports host systems that use dynamic definition of dependent LUs (DDDLU), a host feature that enables dependent LUs on the SNA system to be added to the host configuration when the communication link from the SNA system to the host is established. With DDDLU, LUs do not have to be configured statically at the host. (You must still define dependent LUs on the CS/AIX node.) This reduces the initial configuration required at the host, and makes later expansion easier. CS/AIX can communicate with both DDDLU-capable and non-DDDLU-capable hosts, with no difference in the configuration required. When the communications link from the CS/AIX node to the host is established, a DDDLU-capable host informs the node that it supports DDDLU; the node then sends the required information to define the dependent LUs that use the link. If the host is not DDDLU-capable, CS/AIX does not send this information; it assumes that the LUs have already been defined statically at the host. v Independent LU 6.2 supports independent traffic in APPN networks. Independent LU 6.2 supports autonomous communication and network management, as well as distributed processing. In addition, the DLUR function of CS/AIX enables traffic from dependent LUs to travel over an APPN network. v Primary RUI support provides the ability for a CS/AIX application to manage downstream LAN/WAN attached dependent LU devices as though it were a mainframe. This function has some restrictions for connectivity, but allows applications to pass data between dependent LU devices without the need for a full mainframe application. Session Support A session is a temporary logical channel between partner LUs. Ordinarily, partner applications associated with each LU communicate over the session. CS/AIX can support thousands of sessions. CS/AIX can also support U-shaped sessions (also known as local/remote transparency), in which both primary and secondary LUs reside in the same AIX computer. This enables you to develop and test a pair of source and target transaction programs in one computer without requiring a link connection. The data flowing on a session between two partner LUs may be compressed, to reduce the bandwidth required. v For LU type 6.2, CS/AIX allows you to specify the use of compression in the configuration of the mode that the session uses. You can specify different compression algorithms to be used, each of which provides a different level of compression (RLE, LZ9, or LZ10). You can also specify different compression levels for data flowing in different directions on the session, or specify compression in one direction but not the other. v For LU types 03, CS/AIX allows you to specify the use of compression in the configuration of the link station or PU that the session uses. RLE compression is used for the inbound direction, and LZ9 for the outbound direction. API Support CS/AIX includes application programming interfaces (APIs) for developing

applications for certain types of LUs, for distributed processing, for network management, and for administration of CS/AIX itself. In this release, CS/AIX provides a range of APIs that are compatible with the APIs provided by members of the Communications Server family running on other operating systems. An API is an interface that enables a transaction program (TP) to communicate with its supporting LU. It consists of a library of verbs (also called functions, calls, and subroutines) from which the TP selects those it needs to pass to its LU to request an action, such as SEND_DATA. The LU, in turn, processes the verbs and builds a data stream according to the appropriate protocol, appends a header indicating the destination address, and sends the data over the link to partner LUs. Common Programming Interface for Communications (CPI-C) is one of the most powerful of the APIs because of its portability. Introduced to support dependent and independent LU 6.2, CPI-C complies with Systems Application Architecture (SAA) mandates to unify different platforms and operating systems. CPI-C uses a set of syntax rules that is common to all systems. It has thus become a standard. As well as the standard C-language CPI-C API, CS/AIX also includes a CPI-C API for use by Java applications. For more information, refer to IBM Communications Server for AIX or Linux CPI-C Programmers Guide. In the CS/AIX books, all references to CPI-C include Java CPI-C unless stated otherwise. Other CS/AIX APIs include: v APPC API for peer-to-peer communications between application programs using LU 6.2. The API has the option of being nonblocking. When a TP uses nonblocking verbs, the API can return control to the TP before the requested action has completed. Later, the TP is informed when the action has completed. v LUA API for communications with host applications. v CSV (Common Service Verb) API for utility functions such as character translation and application trace control. In addition, CS/AIX includes the following proprietary programming interfaces: v MS (Management Services) API for network messaging functions. v NOF (Node Operator Facility) API for applications that configure and manage CS/AIX resources. Applications using the CS/AIX APIs can be compiled and linked to run in either 32bit mode or 64bit mode. For more detailed information about an API, refer to the programming guide for the API (see the Bibliography). Client/Server Support Computers running CS/AIX can be configured to communicate using client/server protocols. When client/server protocols are used in a network, all the computers using client/server protocols to communicate in that network are referred to as a domain. The computers running CS/AIX in a client/server configuration can take the following roles:

v A server contains an SNA node and its associated connectivity components. The server provides SNA connectivity to applications on the local system or on other computers in the CS/AIX domain. Servers must be AIX systems. v A Remote API client does not contain SNA node components, but accesses them through a server. A client can access one or more servers at the same time, and can run concurrent applications as needed. Clients can be running AIX, Linux, or Windows. (An AIX computer can be either a server or a client, but not both; you cannot install both the server and the client on the same computer.) Servers and clients communicate across the CS/AIX domain using TCP/IP. Alternatively, they can communicate using HTTPS via a WebSphere server, which uses security certificates to authenticate the client connections. You will normally want to use HTTPS if the clients connect across a public network. In a domain with multiple CS/AIX servers, one server holds the master copy of the CS/AIX domain configuration file. This server is known as the master server. You can define other servers in the domain to be backup servers, or leave them as peer servers. The domain configuration file is copied to backup serverseither when they are started, or when the master copy is changedso that all backup servers hold a copy of the latest information. A peer server obtains domain configuration information from the master server as required, but cannot act as a backup server. If the master server fails, the first backup server on the list of servers defined for the domain takes over as the master. The domain configuration file on this server is used as the master copy, and is copied to other servers as necessary. When the master server is restarted, it receives a copy of the domain configuration from the backup server currently acting as master, and then takes over as the master. Support for Distributed Applications In a Client/Server CS/AIX system, applications running on Remote API Clients cooperate with connectivity resources on servers to execute a single task. Applications running on other (non-CS/AIX) computers can also cooperate with applications on CS/AIX computers to perform distributed processing. CS/AIX supports the following types of distributed applications: v APPC applications (APPC is also known as LU 6.2) v Support of two popular distributed processing applications: Customer Information Control System (CICS) DATABASE 2 ( DB/2), developed for LU 6.2 (dependent and independent). CICS and DB2 (a relational database management system) are SAA-compliant applications that can be readily customized for any environment. CICS and DB2 applications are used together by 90% of the Fortune 500 companies. They are powerful transaction programs that can service thousands of nodes simultaneously. Typically, CICS and DB2 are used to access data from multiple locations, update it, and store it in a central repository. Host Access Class Library Host Access Class Library (Host Access API), which is included on the CS/AIX installation media, allows you to develop Java applications to

access 3270, 5250, or VT applications on a host system. It provides a core set of classes and methods for you to develop platform-independent applications that can access host information at the data stream level. For example, you can develop a graphical interface (accessed using a Web browser) to an existing character-based host application, to make it easier to use.
Advanced Networking Features

Included in the CS/AIX V6.4 base product is a set of features that add advanced networking capabilities to it. These features include the following: v SNA gateway connects LANs to subarea SNA networks. v Primary LU support provides support for controlling downstream dependent LU devices in the same way as a host mainframe application. v Branch Extender simplifies large APPN networks by separating out resources in different locations (for example in separate branches of a large organization). This reduces the amount of topology information that must be stored, while still allowing efficient resource location. v APPC Application Suite provides selected applications for use in APPN networks. v Enterprise Extender (EE, also known as HPR/IP) allows SNA traffic to be transported natively over IP networks. v TN Server provides host access over SNA to TN3270 and TN3270E clients, referred to collectively as TN3270 clients. v TN Redirector provides passthrough TCP/IP host access to TN3270, TN3270E, TN5250 and VT clients, referred to collectively as Telnet clients.
SNA Gateway
A gateway is a user-transparent device that connects dissimilar networks or computer systems, supporting both of the environments that it connects. End users perceive each other as residing in the same network. SNA gateway enables a CS/AIX computer to act as a gateway that links multiple downstream computers in an SNA network to one or more host physical units (PUs), as illustrated in Figure 1 on page 7. To simplify host connectivity, and to eliminate excess links, SNA gateway acts as a PU concentratorit treats the multiple computers as a single PU (that appears to reside on the SNA gateway node) and communicates with the host over a single physical connection.

System z Host
SNA Gateway
SNA Network
Downstream Computers
Figure 1. SNA Gateway Linking Multiple Downstream AIX Computers to a Host Computer
Primary LU Support
Primary LU support allows a AIX application to control downstream dependent LU devices as though it were a host mainframe application. LUA applications usually connect to host mainframes as secondary LUs, so that the host application controls the definition for the sessions and is responsible for sending the BIND to start a session. CS/AIX also includes the ability to act as a primary LU to downstream dependent SNA devices over a LAN, using the Primary RUI interface. Using this interface, an application can connect downstream dependent LU sessions without the need for a host mainframe. To use Primary LU applications, the node must be configured with downstream LUs (or a Downstream PU template) using a host LU name of #PRIRUI#. This indicates to the server that the applications using Primary RUI will control these PUs and the LU resources assigned to them. The PUs can be used on both LAN and WAN ports. Refer to IBM Communications Server for AIX or Linux LUA Programmers Guide for information about programming applications to use Primary RUI.
Branch Extender
Network nodes in an APPN network need to maintain topology information (about the location of other nodes in the network and the communications links between them), and to forward this information around the network when the topology changes. As the network grows in size, the amount of stored information and topology-related network traffic can become large and difficult to manage. It is possible to avoid these problems by separating the network into subnetworks, so that each node only needs to maintain topology information about the nodes in its own subnetwork. However, this results in increased network traffic when trying to locate resources in other subnetworks.

The Branch Extender feature of APPN, illustrated in Figure 2, provides a solution to these problems.
Network Node Server
APPN Backbone Network
Branch Network Node
End Nodes
Figure 2. Branch Extender
As the name implies, Branch Extender is designed for networks that can be divided into distinct areas such as separate branches of a large organization. It works by separating out branches from the main backbone APPN network (for example, the network in the organizations headquarters). Each branch contains a node of a new type called Branch Network Node (BrNN), which is connected to a Network Node in the main APPN backbone network. The BrNN combines the functions of an APPN network node and an APPN end node. v To the backbone network, the BrNN appears as an End Node, connected to its Network Node Server (NNS) in the backbone network: The nodes in the backbone network are not aware of the nodes within the branch, reducing the amount of topology information that must be stored. Because the BrNN appears as an End Node, it does not receive topology information from the backbone network (topology information is transmitted only between Network Nodes). The BrNN registers all resources in the branch with its NNS as though they were located on the BrNN itself. This means that the nodes in the backbone network can locate resources in the branch without having to be aware of the separate nodes in the branch. v To the branch network, the BrNN appears as a Network Node, acting as the NNS for End Nodes in the branch. Each node in the branch sees the rest of the network as being connected through its NNS, in the same way as for a standard NNS.
APPC Application Suite

APPC Application Suite is a set of applications that demonstrates the distributed processing capabilities of APPN networks, and can be helpful in configuration

verification and problem determination. APPC Application Suite can be used to provide support for operations such as file transfers, which are frequently performed across a network. APPC Application Suite contains the following applications: v ACOPY (APPC COPY) v AFTP (APPC File Transfer Protocol) v ANAME (APPC Name Server) v APING (APPC Ping) v AREXEC (APPC Remote EXECution) v ATELL (APPC TELL) These applications can be accessed from a server or from a AIX or Windows client.
Enterprise Extender
Enterprise Extender (also known as HPR/IP) provides a mechanism for integrating SNA applications with an IP network. SNA applications are designed to use SNA protocols to communicate over SNA networks with other SNA applications. When installed in a TCP/IP network using Enterprise Extender, SNA applications can still communicate; the Enterprise Extender function provides a mechanism for transporting SNA protocols over the IP network. In particular, it provides APPN High-Performance Routing (HPR) functionality, giving the applications the benefits of both APPN and IP connectivity. Enterprise Extender in CS/AIX is implemented simply as a communications link. To connect two SNA applications over IP, you define an Enterprise Extender link, in the same way as for any other link type such as SDLC or Ethernet.
TN Server
3270 emulation programs that communicate over TCP/IP (rather than over an SNA network) are referred to as TN3270 programs (Telnet 3270 emulation programs). TN3270 programs can also include support for TN3270E (Telnet 3270 standard extensions). TN3270E supports 3270 device emulation (including both terminals and printers) using Telnet. It enables a Telnet client to select a particular device (by specifying the LU name or the name of an LU pool), and provides enhanced support for various functions, including the ATTN and SYSREQ keys and SNA response handling. Note: This guide uses the term TN3270 for information that applies equally to the TN3270, TN3287, and TN3270E protocols. CS/AIX TN server provides access to 3270 host computers for TN3270 users on other computers. TN server enables TN3270 users to share a host connection with CS/AIX or with other TN3270 users, instead of requiring a direct link. TN server also enables TN3270 users to access hosts that are not running TCP/IP. The CS/AIX TN server function is illustrated in Figure 3 on page 10.
TN Server Configuration Host
Host View of the Configuration Host
TN3270 Program View of the Configuration
SNA Node Running TN Server
SNA Node Running Multiple 3270 Sessions TCP/IP Network
Host
TCP/IP Network
Clients Running TN3270 and TN3270E Programs
Figure 3. TN Server
The CS/AIX TN server feature provides an association between a TN3270 user and CS/AIX 3270 LU. All data from the TN3270 user is routed to the LU. This means that the configuration for both the host and the TN3270 user is as though they were connected directly; neither needs to be aware that data is being routed through TN server. CS/AIX TN server supports all TN3270 client emulation programs that correctly implement the protocols defined in IETF RFCs 1123, 1576, 1646, 1647, and 2355. Security Features: CS/AIX TN Server supports data encryption, server authentication, client authentication, and Express Logon, using Secure Sockets Layer (SSL) software: v Data encryption means that the data flowing between the TN Server and the TN3270 emulator is in encrypted form. v Server authentication allows a TN3270 client to verify that the TN Server it is connected to is the one it expects. v Client authentication allows a TN Server to verify that the TN3270 client connecting to it is the one it expects. The TN Server can also check a revocation list on an external directory server to ensure that the clients authorization has not been revoked. v Express Logon operates in conjunction with client authentication to remove the requirement for TN3270 clients to provide a user ID and password when connecting to the host. Instead, the clients security certificate is used to retrieve the necessary user ID and password information. These features are available only on AIX 4.3.1 and above, and require some additional software in addition to the standard CS/AIX product. See Installation Requirements on page 20 for more information. Service Location Protocol (SLP): CS/AIX TN Server also supports Service Location Protocol (SLP), providing service location and load balancing functions. If you use SLP, each TN Server advertises:
10

v the functions it supports (in this case TN3270) v its current load; this is based on the percentage of its available host LUs that are currently in use, but can be factored to allow for other differences between TN Servers. An SLP-capable TN3270 client can then select the best server to connect to (the least loaded server that provides the functions it requires). It does this either by querying TN Servers directly, or by querying a Directory Agent that in turn collects information advertised by TN Servers. A large SLP network can be divided into scopes (typically based on departments or geographical areas), so that information about a TN Server is advertised only to TN3270 clients and Directory Agents that have the same scope as the TN Server. This allows you to control the range of TN3270 clients that can use the services of each TN Server. Note: The server on which the TN Server runs must support IPv4 addressing: that is, it must have an IPv4 address (although it may also have an IPv6 address). This is because SLP uses UDP broadcasts, which are not available in an installation that supports only IPv6.
TN Redirector
The CS/AIX TN Redirector feature provides passthrough services for 3270, 5250 or VT sessions over TCP/IP. The Telnet user communicates with CS/AIX over a TCP/IP connection; CS/AIX then communicates with the host over another TCP/IP connection. CS/AIX TN Redirector supports data encryption, server authentication, and client authentication, using Secure Sockets Layer (SSL) software, in the same way as for TN Server for 3270. This allows you to use Secure Sockets Layer (SSL) security checking where necessary, and not on the complete user-to-host connection. For example: v If clients are connecting to CS/AIX over a TCP/IP LAN where checking is not required, but are connecting to a remote host that requires SSL, you can use SSL over the TCP/IP connection between CS/AIX and the host. This means that security is checked once for all clients, and individual clients do not have to provide security information. v If CS/AIX is installed on the same site as the host, but clients are connecting in from external sites, you can use SSL over the client connections to CS/AIX without having to install SSL software on the host.
Features and Benefits

CS/AIX has features and benefits that range from simplifying configuration to improving problem diagnosis to enhancing network performance.
Versatile Building Blocks

CS/AIX supports most environments and node functions. In any type of network, subarea or APPN, it enables the AIX computer to function as any one of, or a combination of, the following: v Host-dependent node v Peer node (for a description of APPN peer nodes, see the discussion of peer-to-peer networks in IBM Communications Server for AIX V6.4 on page 1) v Partner (either source or destination) in distributed applications
11

v Gateway node that interconnects SNA networks v Gateway node that interconnects SNA and TCP/IP networks Through network management APIs, the AIX computer can also be configured to function as a Management Services (MS) entry point to provide support for distributed network management. At the link level, the AIX computer can be connected to various LANs and WANs by using any of the supported link types (described in IBM Communications Server for AIX V6.4 on page 1 and Installation Requirements on page 20).
Client/Server Operation
Client/server configuration provides the following benefits: v Concentrating SNA resources on servers reduces the load on clients, improving client performance and minimizing the storage needed to provide SNA services to clients. v A single data link can be shared by multiple users on different machines, eliminating the need for each machine to have a physical SNA network connection. v Multiple servers can provide redundant connectivity (for example, by having multiple servers providing access to the same host). Having multiple paths to an SNA resource enables load balancing across the different servers and provides immediate backup in the event that a particular server or link fails. v By using LU pools across multiple servers, the administrator can easily configure and add servers and users. v Having fewer links and PUs for host connectivity reduces the size of the host VTAM definition. v Administration utilities can be used to configure and manage both node resources (for any computer in the domain) and shared resources. The client/server support provided by CS/AIX administration tools enables transparent administration of all domain resources from any computer in the domain. v SNA applications can be connected over Internet Protocols using TCP/IP and HTTPS for traversing firewalls and for authentication and security.
Easy Configuration
CS/AIX is designed with configuration options and capabilities that reduce configuration time and network complexity. For example: Motif Administration Program The easiest way to define and modify the CS/AIX configuration is to use the Motif administration program (xsnaadmin). This program provides a graphical user interface from which you can view and manage CS/AIX resources. This program also simplifies configuration by exposing only the fields whose values typically vary from one installation to another, using default values for other fields. The Motif administration program includes help screens that provide overview information for SNA and CS/AIX, reference information for CS/AIX dialogs, and guidance for performing specific tasks. Web Administration Program CS/AIX also includes a Web Administration program, providing similar functions to the Motif administration program. This allows you to administer CS/AIX from your browser without the need to start an X
12

session or telnet session to the CS/AIX server, and is particularly useful when connecting over slow or unreliable links. Dynamic Configuration in APPN Networks Configuring a node or network is also made easier through the APPN networks dynamic configuration. For example, APPN end nodes and applications dynamically register configuration data to support LU 6.2 sessions, thus making session configuration optional. Further, by having the node control point act as the default local LU, you can avoid LU 6.2 configuration altogether. APPN also supports dynamic link station configuration in the absence of configured link stations.
Additional User Interface Choices for Administration

The Motif administration program is the recommended interface for configuring and managing CS/AIX. However, you have a choice of interfaces for CS/AIX, which enables you to work with the one that suits your equipment, needs, and preferences. Command-Line Administration Program The command-line administration program (snaadmin) can be used to issue commands to manage individual CS/AIX resources. You can use snaadmin either directly from the AIX command prompt or from within a shell script. Web Administration Program The Web Administration program allows you to administer CS/AIX from your browser. System Management Interface Tool (SMIT) The SMIT interface is available in the graphic Motif version for AIXwindows environments and the character version for ASCII terminals. In both versions, SMIT displays dialogs for easy entry of configuration and operational data. NOF API The CS/AIX NOF API provides the same management functions as the command-line administration program, providing an interface suitable for use within a program (rather than a command script). You can use the NOF API to write your own application programs to administer CS/AIX.
Better Performance
CS/AIX enhances the inherently high performance of SNA networks and uses class of service operation. CS/AIX also optimizes network speed through SNA data compression for LU 03 session data, and through different traffic-management methods that balance traffic flow according to network size: v In APPN networks, CS/AIX supports both High-Performance Routing (HPR) and intermediate session routing (ISR), and provides connection network options. While ISR works efficiently for small networks, it degrades the performance of larger ones. v For larger networks using LAN connectivity options (such as Token Ring or ethernet) or using Enterprise Extender, you can also use the connection network option to improve communication efficiency. The connection network option creates a communications path directly between nodes. This enables traffic to bypass intermediate network nodes.
13

v Another traffic control mechanism, adaptive session-level pacing, automatically adjusts congestion by regulating the rate at which LUs send message units to partner LUs.
Security Options
With networks becoming more complex and moving to an open architecture, security emerges as a major issue. In SNA networks running CS/AIX, you can protect your assets by defining various levels of security through configuration and by implementing certain types of links. For example: v In a client/server system, you can set up a WebSphere server to provide HTTPS access from Remote API Clients to the servers. This means that the client connections are authenticated using security certificates. (This feature requires some additional software in addition to the standard CS/AIX product. See Installation Requirements on page 20 for more information.) v LU 6.2 users can define up to three levels of securitysession, resource, and conversation. Respectively, one ensures that the proper LUs are engaged in a session, one restricts access to all applications associated with a particular LU, and one restricts access to a particular application. Additional security is possible through data encryption routines. v At the link level, fiber optic links provide extra security as a medium that (unlike electrical cabling) does not leak signals and therefore cannot be easily tapped. v CS/AIX TN Server and TN Redirector can provide data encryption, server authentication, and client authentication between the CS/AIX server and TN3270 or Telnet clients, using Secure Sockets Layer (SSL) software. (This feature requires some additional software in addition to the standard CS/AIX product. See Installation Requirements on page 20 for more information.)
Network Management Flexibility

CS/AIX uses two types of network management schemes: v Multiple Domain Support-Network Management Vector Transport (MDS-NMVT) can work as a centralized, distributed, or hierarchical management scheme. It is based on a focal point/entry point architecture that gives you a high degree of flexibility. Focal points are control nodes that manage the network according to the data they collect from entry points (management applications that reside on all other nodes in the network). In centralized management, a single focal point acts as a control point for the entire network. In distributed management, several focal points share in managing the network. In hierarchical management, focal points are nested according to function. MDS-NMVT can thus be adapted to manage subarea, standard APPN, and very large APPN networks. v Simple Network Management Protocol-Management Information Base (SNMP-MIB), which is adapted for APPN networks from TCP/IP, is a distributed management service based on an agent-manager architecture. This management scheme consists of several components: one or more SNMP agents, a manager, and a MIB database, all of which typically reside on different nodes. An SNMP agent is a process that runs on and monitors the status of the system being managed. The agent maintains a MIB database for that system.
14

The manager (an application) queries the agent for MIB information and processes the response. The manager can also receive unsolicited data (SNMP traps) from the agent. The manager and agent communicate with each other by using the SNMP protocol. APPN network managers can use APPN SNMP-MIB to gather information to analyze the network and correct problems. CS/AIX uses agent software that supports the APPN MIB. For more information about the APPN MIB, see IBM Communications Server for AIX Administration Guide and the AIW IBM home page at http://www.networking.ibm.com/app/ aiwhome.htm.
Reliability, Availability, and Serviceability

To help you maintain reliable system operation, CS/AIX provides a range of display functions and problem-diagnosis tools. v The Motif administration program provides enhanced configuration and management tools, including the following: Immediate updates of configuration information Status information for links, sessions, and node resources v Query and status commands provide you with information about: LU-LU sessions APPN intermediate sessions Active links APPN topology databases, which store link information v Problem-diagnosis tools are available to help you during the different stages of configuration and operation. They include the following: Diagnostics information collection tool (snagetpd) to enable you to collect service information easily Status and error messages to help resolve problems with configuration routines and system operation Logs for collecting network error, failure, and audit information Trace facilities for gathering and formatting detailed problem information Other utilities help you test for link connectivity and communication between applications. CS/AIX also includes the Management Services API, which is used to develop tools for sending and receiving network alerts and problem data. All of these management and problem-diagnosis tools are fully integrated into the CS/AIX Client/Server model, so you can manage the entire CS/AIX domain or collect diagnostics information from a single point in the network.
Network Integration, Growth, and Change

To support network integration, growth, and change, the CS/AIX APIs can be used to develop applications for a particular LU, platform, or operating system as your business needs dictate. CPI-C is an especially important API because it is consistent across different platforms and operating systems. It is used to develop applications that can run on any system. Enterprise Extender also provides a mechanism for integrating SNA and TCP/IP networks.
15
16
Chapter 2. Planning for Your Network and IBM Communications Server for AIX
This chapter provides an overview of the stages of planning a network that runs CS/AIX. It also summarizes the functions that you can configure for the AIX computer and presents guidelines for estimating the resources required to support the functions.
Stages of Network Planning

This section presents some general guidelines for planning, configuring, and managing networks through the use of various CS/AIX and AIX utilities. Planning a network involves balancing function, performance, resources, and cost. Although there is no single best plan for a network, some general guidelines and techniques can help ensure that your plan meets your needs. To plan a network, perform the following tasks: v Determine the functions the network should provide (such as file transfer or 3270 emulation) and your performance requirements. v Determine how CS/AIX can be configured to provide the functions you need. v Estimate the resources needed to install CS/AIX, to support your performance and capacity requirements, and to support CS/AIX functions, and identify the associated costs.
Identifying Functional Requirements for the Network

To determine the functions your network should provide, you need to consider the following questions: v Do I need to run APPC applications over a TCP/IP network? v Is the network to be APPN? v Will CS/AIX run as a client/server system? If so, will all computers operate in a single CS/AIX domain, or do I need to define two or more separate domains? v Do I need more than one server in the CS/AIX domain to provide load balancing for connectivity resources? If so, which server will be the master configuration server? Do I need to provide one or more backup configuration servers? v Do I need to support Remote API Clients connecting to CS/AIX servers using HTTPS? v Will user applications run on the server or on AIX client computers? v Will the server provide connectivity resources for Windows applications (such as API transaction programs) running on Windows clients? v Is each server to be an end-point for sessions or is it to be one of the following types of gateways? APPN LU 0 LU 2 TN Server or TN Redirector v What types of physical links will the network use? v Will CS/AIX need to support IPv4, IPv6 or both types of connections?
17

The answers to these kinds of questions help you determine which CS/AIX functions the network requires.
Determining How to Configure CS/AIX

To determine how CS/AIX is to function, you should first decide how work is to flow through the network. The following questions should be considered: v What resources (such as applications) should be available through the network? v How many users need access to remote resources? v How frequently is each resource accessed? v How can users get access to the network? v How will user requests be routed through the network? You can configure CS/AIX to support many functions, including, for example, the following: v APPN network node for intermediate session routing (ISR) v APPN end node (which communicates autonomously with adjacent nodes but uses APPN network node services to communicate with nonadjacent peer nodes) v Low-entry network (LEN) node (which communicates directly with adjacent nodes or nodes configured to appear adjacent) v Host terminal emulation using LU 2 v Use of LU 0, LU 1, LU 2, LU 3, and LU 6.2 (dependent and independent) v SNA gateway connection to a host One or more functions can be configured for a given node, depending on your needs. For example, you can configure CS/AIX as an APPN network node to provide routing services and ISR, and use the same node for SNA gateway to route dependent LU sessions, such as LU 0 and LU 2. Similarly, you can configure CS/AIX to run TN Server and support a shared database, as well as an independent LU 6.2 connection to MQSeries on the host.
Identifying Resource Requirements for Installation and Operation

To estimate support for the functions of CS/AIX, the following questions must be answered: v What personnel skills do I need? v What model of AIX workstation do I need? v What transport media do I anticipate using? v What are the installation requirements for the configuration I select? v How much memory and paging space do I need for operation? v What response time can I expect with the anticipated traffic level? Answering these questions helps you identify the types of resources that CS/AIX uses when it is configured to support any one or more of the many functions described in Identifying Functional Requirements for the Network on page 17. Answering the questions also helps you to understand the relationship between CS/AIX functions, AIX resources, and network resources. How you allocate resources to nodes determines how the network will perform.
18
Personnel Requirements
Installing, operating, and tuning CS/AIX requires the following personnel: v Network administrators, who plan the network, add new devices, and maintain or enhance overall network performance v System administrators, who install and maintain CS/AIX and the hardware on which it operates, and who configure systems for network connection v Programmers, who develop customized applications such as transaction programs or network management routines Network and system administrators should be thoroughly familiar with the hardware on which CS/AIX operates and with the AIX operating system. They must know the networks to which various systems are connected and understand SNA concepts in general. They should also be familiar with the following: v The Motif interface or the System Management Interface Tool (SMIT) for AIX v TCP/IP, if they plan to use Client/Server functions, TN server, Enterprise Extender, or AnyNet v The Linux operating system, if the CS/AIX system includes Remote API Clients on Linux v The Windows 2000, Windows XP, Windows 2003 Server, Windows Vista, or Windows Server 2008 operating system, if the CS/AIX system includes Remote API Clients on Windows v WebSphere Application Server, if the CS/AIX system includes Remote API Clients that connect to servers using HTTPS Programmers who develop customized applications for SNA should be experienced with the C language (or Java if they are using Java CPI-C), and should be familiar with the APIs that are available in CS/AIX.
IBM eServer pSeries Models

IBM Communications Server for AIX is designed to run on an AIX workstation connected to one or more networks. CS/AIX V6.4 will run on any IBM RISC System/6000 or eServer pSeries system that is supported by AIX Version 5.2, 5.3 or 6.1. (For AIX V6.1, the server must run in the Global Environment, not in a system or application WPAR.) IBM pSeries workstations are available in many models that have different capacities for memory, disk space, I/O adapters, and CPU speeds. They are packaged as follows: v Blade center models, such as the JS20. The blade center models have the smallest capacity for memory, disk drives, and I/O adapters (such as ethernet). They are best suited as client or end-point systems. v Deskside or rack mount models, such as the p5 520. The deskside and rack mount models have more capacity for memory, disk drives, and I/O adapters. They are suitable for small- to medium-sized server or multi-user environments. Some of these systems can also be LPARed to create multiple OS instances on the same hardware. v Frame mount models, such as the p5 590. The frame mount models have the most memory, disk, and I/O capacity, and are suitable for large server or multi-user environments. These models can also be LPARed. For information about the relative CPU speeds of the different IBM eServer pSeries systems, refer to http://www.ibm.com.eserver/pseries.
19
Transport Media
CS/AIX might need to share the underlying transport medium (such as SDLC, token ring) with other communication protocols. Therefore, physical layer bandwidth requirements must accommodate all the protocols and applications sharing the transport medium. Note: CS/AIX can share the token ring, Ethernet, and X.25 adapters with other protocols such as TCP/IP. You might need to specify unique service access point (SAP) addresses for each protocol to use. CS/AIX can also share a Multiprotocol Quad Port (MPQP) adapter, but not an MPQP port.
Installation Requirements
The functions that you assign to CS/AIX (from Identifying Functional Requirements for the Network on page 17) also determine the installation requirements. This section provides an overview of the computer resources required for installing CS/AIX. For more information, see the documentation supplied with each product (see the Bibliography for a list of the books). Link hardware Link hardware is required only on a server, and not on a client. Installing an AIX workstation or Power Series workstation in one or more networks requires links that conform to the selected networks communication protocol. Link hardware consists of a communication adapter that is installed into the computer and a matching cable for attachment to the network (you also need device driver software). Note: 1. Communication adapters must be installed with matching cables. For example, an Ethernet adapter requires an Ethernet cable in order for the link to function. 2. If you are using Enterprise Extender as your only link type, or if you are only using the AnyNet APPC over TCP/IP feature of CS/AIX, the adapters listed in this section are not required; but you must have one of the adapters required by AIX TCP/IP. CS/AIX supports communication adapters for the following link protocols: v Token Ring v Ethernet (standard or IEEE 802.3) v SDLC IBM 2 port PCI IBM 4 port MPQP The following link protocols require additional products or features that are not included with CS/AIX: v X.25 (requires the AIXLink/X.25 product) v ATM using an emulated LAN (token ring or Ethernet) interface over an IBM AIX ATM adapter v Frame Relay using an emulated token ring interface For information about adapters that have been tested with CS/AIX, see http://www.ibm.com/software/network/commserver/about/ comp_products/adapter_csaix.html. If you have any questions about the appropriate adapter or hardware for your needs, call your IBM Sales Representative.
20

Software: AIX server Before you can install and use CS/AIX on your AIX workstation, the workstation must have the following software: v AIX Base Operating System (BOS), one of the following versions: AIX v5.2ML7 or later AIX v5.3ML3 or later AIX 6.1 or later v Appropriate DLC support (not necessary for installation, but required to use CS/AIX). For more information about DLCs, see Installing Data Link Control Filesets on page 31. v Motif level 1.2 support (part of the AIX base operating system; required if you want to use the Secure Sockets Layer functions of CS/AIX TN Server and/or TN Redirector, or if you want to use the Motif administration program). v Java software (required if you want to use Java CPI-C). The latest Java SDK available from http://www.ibm.com/developerworks/java/jdk satisfies all the requirements. Install the Java SDK package with the installp command. v The AIX option bos.64bit is a prerequisite if you intend to run applications using the CS/AIX APIs in 64bit mode. As well as installing this option, you need to configure it using the command smit load64bit, to ensure that it is loaded before you try to run 64bit applications. If you intend to compile and link 64bit applications on this computer but run them on a different computer (for example if you use separate computers for developing and testing applications), the option bos.64bit is not required. v A Web server that supports Java servlets (required for the Web administration program). The IBM HTTP Server (IHS) v6.0.1 has been tested with CS/AIX. If you intend to use another Web server, or if you are installing one of these Web servers after installing CS/AIX, you will need to set up links between CS/AIX directories and the Web servers directories; see Configuring a Web Server for the Web Administration Program on page 39 for details. (If one or more of the above Web servers is already installed, the CS/AIX installation process sets up the required links automatically.) v A Web browser that supports Java (required for the Web administration program). The following Web browsers have been tested with CS/AIX: Microsoft Internet Explorer v4 SP1 or later Netscape Navigator v4.06 or later WebSphere Application Server (for HTTPS access) If you will be running a client/server system in which Remote API Clients connect to CS/AIX servers using HTTPS, you will need to run WebSphere Application Server to provide HTTPS access from these clients to the servers. CS/AIX operates with WebSphere Application Server Version 5, which can be installed on a computer running any operating system supported by WebSphere. (If necessary it can be installed on the same AIX computer as a CS/AIX server.) Refer to the WebSphere Application Server documentation for more information about installing it. You will also need to install an
21

additional CS/AIX plug-in on this computer to use WebSphere with CS/AIX, as described in Configuring WebSphere Application Server on page 36. Memory and Storage To support a full range of configurations and services, a workstation running CS/AIX needs the minimum memory required by the AIX operating system plus 64MB, and 200 MB of disk space. In addition, 250 MB of temporary storage is required during installation. Messages and help text are supplied in several different national language versions. You must install the filesets for at least one national language; you can install more than one if required. You need 2.5 to 4.0 MB of disk space per language (the amount varies with different languages). If you decide to install the documentation for CS/AIX in softcopy (PDF) form, you need additional fixed-disk storage. Again, different national language versions are available. You need 28 MB of disk space to install the US English manuals, and up to 17 MB for each additional language version. Note: Memory and fixed-disk requirements for other licensed programs, user applications, and data are not included in these requirements; carefully review all system, memory, and fixed-disk requirements with your IBM representative or authorized industry remarketer.
Advanced Configurations
If you expect to run applications that require more than a basic configuration, you need to plan for extra computer resources. In general, memory and storage requirements for running CS/AIX depend on many different factors that vary with the function of the AIX workstation and its environment. Nevertheless, by using the rule of thumb that LUs, active links, and ongoing sessions are the dominant consumers of computer resources, you can estimate the amount of additional memory and disk space that is required to support the most demanding applications. For further information about resource usage, allocation, and optimization with respect to node function, refer to http://www.ibm.com/software/network/ commserver.
Memory and Storage Requirements for Operation

This section describes the memory and storage requirements of a workstation running CS/AIX. Memory Buffers (Mbufs) AIX uses memory buffers (mbufs) to enable communication between the communication subsystems and the AIX DLCs. The mbuf pool is a shared resource that must be managed at the system level. CS/AIX uses mbufs to send and receive data across the network, but it is just one of the subsystems that uses mbufs. CS/AIXs mbuf resource utilization can affect the performance of other subsystems, such as TCP/IP, NFS, or DCE. Coordinate with your network administrator in determining mbuf requirements. Memory, Disk, and Paging Storage CS/AIX uses primary storagealso known as main memory and random access memory (RAM)permanent disk storage, and paging disk storage (also known as paging space):
22

v Control blocks for SNA resourcessuch as LUs, links, and sessionsconsume primary storage. v Memory buffers consume only primary storage. v CS/AIX executables, configuration files, and softcopy publications consume permanent disk storage. v Application programs, sessions, and related processes have paging space requirements that consume permanent disk storage. Memory and disk storage requirements depend on various factors that widely differ from one environment to another. Transaction programs (TPs) and SNA sessions are the dominant consumers of memory and disk storage. A TP is a program that uses the SNA application programming interface (API) to access the network. A session is a temporary logical channel between two LUs on partner nodes. TPs use this channel to communicate with each other. The consumption of memory and disk storage is largely affected by the overall number of sessions, the number of allocated sessions (conversations), the traffic intensity of the conversations, and the number of active user TPs. Memory requirements are mostly affected by the data-traffic intensity and the resulting usage of mbufs. Disk storage requirements stem from the paging space requirements of the TPs, sessions, and related processes. For all LU types, a distinction is made between an idle session and an allocated session. An idle session is an active session that is not being used by TPs. An allocated session is one that supports an ongoing conversation. To estimate the total memory requirement, you need to estimate the traffic intensity and the portion of the overall number of sessions that will be allocated, on average, at any one time. You can also choose to configure the system to handle peak demand. These estimates vary among environments. If you increase the session load beyond system memory capacity, you incur the cost of paging. Processes CS/AIX requires a minimum of 20 AIX processes.
Response Time
Estimating response time for anticipated traffic levels is an impossible task because of the large number of networking conditions that exist. Because response time also cannot be expressed in a concise formula, it is best obtained from experimental data, which you can extrapolate to your network. To help you in your estimates, the IBM Communications Server web pages at http://www.ibm.com/software/network/commserver present different network configurations, and show how the response time of each network is affected by such factors as the model of the AIX workstation and the number of ongoing sessions.
IPv4 and IPv6 Addressing

Computers running CS/AIX V6.4 can use either IPv4 or IPv6 addresses, with the following constraints.
23

v All servers in a Client/Server domain must use the same addressing format (IPv4 or IPv6). If the servers use IPv4, clients must also use IPv4. If the servers use IPv6, clients can use either IPv6 or IPv4. v For TN Server, if CS/AIX uses IPv4, TN clients connecting to the TN Server must also use IPv4. If CS/AIX uses IPv6, TN Clients can use either IPv6 or IPv4. By default the TN Server accepts connections from both types of clients, but you can configure it to listen on a particular IP address (using the listen_local_address parameter in the command-line administration program or a NOF application) in order to restrict it to one type of client connection. v For TN Redirector, if CS/AIX uses IPv4, both TCP/IP connections (from the client to CS/AIX and from CS/AIX to the host) must also use IPv4. If CS/AIX uses IPv6, the TCP/IP connection from the client to CS/AIX follows the same rules as for TN Server. The connection from CS/AIX to the host can use either IPv6 or IPv4. There is no requirement for the two connections to use the same addressing format. v If you are using SLP, the TN Server must support IPv4 addressing: that is, the server must have an IPv4 address (although it may also have an IPv6 address). This is because SLP uses UDP broadcasts, which are not available in an installation that supports only IPv6. v For Enterprise Extender (HPR/IP), the ports at both ends of a link must use the same addressing format (IPv4 or IPv6). If CS/AIX uses IPv4, it can connect only to remote systems that are configured to support IPv4. If CS/AIX uses IPv6, you can configure it to use either IPv4 or IPv6 on an Enterprise Extender link. The option you choose must match the configuration at the remote system. In addition, all links on the same Enterprise Extender port must use the same addressing format (IPv4 or IPv6). If you need to support links with different addressing formats, you must use separate ports. Similarly, all Enterprise Extender ports on the same connection network must use the same addressing format. To check whether a CS/AIX server is running IPv4 or IPv6, use the command ifconfig -a and look at the IP address or addresses in the output. These will be IPv4 dotted-decimal addresses, IPv6 hexadecimal addresses, or both. For a Remote API Client on Windows, the equivalent command is ipconfig (with no command-line options).If you need to change the computers IP addressing format, refer to your operating system documentation. If you are upgrading an existing CS/AIX system to V6.4 as described in Migrating from previous levels of CS/AIX on page 32, and you also want to change to IPv6 addressing, you can do the two processes in either order. However, you cannot use the new IPv6 addressing capabilities in V6.4 until both processes are complete. v For a Client/Server system, you must change all the servers in the domain from IPv4 to IPv6 at the same time; do not attempt to run a mixed domain of IPv4 and IPv6 servers. v Because the upgrade to CS/AIX V6.4 also requires you to upgrade all the servers at the same time, you may choose to make the change to IPv6 addressing at the same time as upgrading each server. Alternatively, you can change all the servers to IPv6 either before or after the upgrade to V6.4, whichever is more convenient.
24

v After all the servers have been changed to use IPv6 addressing, you can change Remote API Clients to use IPv6 addressing as required. IPv4 clients can continue to operate with IPv6 servers, so there is no need to change all the clients at the same time. If you are installing a new CS/AIX system, you can install it with only IPv6 addressing on all servers and clients if appropriate, or you can use IPv4 addressing initially and then move to IPv6 later(subject to the restrictions above for Client/Server domains).
Ensuring Compatibility among Cross-Platform Configurations

SNA products running on different platformssuch as IBM Personal Communications or Communications Server for Windows, or VTAM NCP on a hostcan function with CS/AIX if certain requirements are met. In general, the current release of an SNA networking product can function with CS/AIX as long as it supports PU 2.1 nodes and at least one of the link types supported by CS/AIX. However, some very old releases (such as VTAM V2) might not function reliably. The capabilities of each networking product are documented in its corresponding users guide. Other factors to consider include the following: v If you are using independent LU 6.2 and your network is not APPN, you need to make sure that partner LUs are defined to the local system. v Because default values for DLC window sizes and timers vary from device to device, you must ensure that your remote devices use the correct value. For example, a DLC window size that gives good performance with a Communications Server for Windows node might not perform well with a 3172 node. For more information about window size performance considerations, refer to the IBM Communications Server web pages at http://www.ibm.com/ software/network/commserver. v When working in a heterogeneous environment (TCP/IP and SNA protocols on the same LAN) with multiple LAN segments, make sure that your LAN interconnect devices can route TCP/IP and bridge SNA frames at the same time.
Naming Conventions
You can use network IDs to logically segment your physical network. Also, if you plan to connect to other networks, it is highly recommended that you register your network IDs to avoid network name conflicts. You can define network and LU names as follows: Network names You can define different network names (network IDs) to provide segmentation of APPN networks. Segmentation limits the size of network topology databases and the frequency of broadcast LOCATE requests through each network. To ensure the uniqueness of a network ID, a network administrator can register the networks ID with the IBM worldwide registry. The IBM registry ensures that each network ID is unique among those registered with it. Registry standards are consistent with Open Systems Interconnection (OSI) standards, including OSI country codes, as
25
Naming Conventions
established by the International Organization for Standards (ISO). For more information about registration, see Users Guide for SNA Network Registry. LU names You can use wildcards for LU names to minimize system definition and network searches.
26
Chapter 3. Installing CS/AIX on AIX Servers

This chapter describes how to install CS/AIX on AIX computers. This chapter also provides instructions for maintaining your CS/AIX configuration information. Note: 1. You must have root privileges in order to install CS/AIX. 2. You must add a data link control (DLC) before you can use CS/AIX. The DLC manages the communication adapter. For more information, refer to the description of the mkdev command in AIX Commands Reference, or use the Communications option on the Devices menu in System Management Interface Tool (SMIT). (For more information, refer to AIX Communications Programming Concepts.) 3. For AIX V6.1, the server must run in the Global Environment, not in a system or application WPAR.
CS/AIX Licensing and Packaging

This section explains how the CS/AIX product is licensed and packaged.
CS/AIX Licensing Mechanisms

This section is intended to provide the reader with a high-level understanding of the licensing mechanisms. The CS/AIX License Information document provides the complete terms and conditions for the product. In addition, sample scenarios are available for further clarification of licensing for many of the different types of connectivity and functionality provided by CS/AIX. Refer to http:// www.ibm.com/software/network/commserver for this information. CS/AIX includes several components, described below. IBM Communications Server for AIX Program product A separate Program license for CS/AIX is required for each machine or SP node on which any or all of the included components are installed. Licensing for CS/AIX includes the Program (server) license and user licenses. v A User is defined as a person. You must purchase a User authorization for every concurrent User that will access and use CS/AIX, either directly or indirectly. As an example of indirect usage, if a multiplexing program or application server (for example, CICS, DB2, WebSphere, or your own business application) connects to CS/AIX providing access on behalf of multiple concurrent Users, then a User license is required for each of the concurrent users. v In addition, for application programs that are not associated with actual users, a User authorization is required for each active upstream or downstream connection established to the CS/AIX node. In an APPN environment, a connection is an active link to an adjacent node.
Enabling CS/AIX Using a Nodelock License

CS/AIX uses nodelock licenses to enable or disable the product. (Nodelock licenses are licenses managed at a specific node instead of by a network license server.)
27

A nodelock license can be either a permanent license or a temporary key that grants the operator use of CS/AIX for a limited time (for example, for an introductory offer or for demonstration purposes). Purchase of the CS/AIX product includes the permanent nodelock license, which is installed automatically into the systems nodelock license file during product installation. If CS/AIX is installed from demonstration media, such as CD Showcase media, it is installed with a temporary key. To fully enable the product, you must purchase a CS/AIX license using your traditional IBM marketing channels. To upgrade from a temporary key, you can simply install the permanent key from the CS/AIX installation media. You do not need to reinstall the product. To extract the key from the CS/AIX installation CD, use the following procedure: 1. Issue the command smit bffcreate, and use the resulting SMIT dialog to extract the LPP image from the installation media. Note the name of the file that is created; this should be sna.6.4.0.0.I or similar. 2. Use the following commands to extract the key from the LPP image: cd /tmp restore -f /usr/sys/inst.images/installp/ppc/filename ./usr/lib/sna/install/license.sna Replace filename with the filename that you noted in step 1. 3. Use the following command to copy the key to the /var/ifor/nodelock file. Be sure to use the append operator >> to concatenate the key into the file (do not use the > operator, which overwrites all old keys). cat /tmp/usr/lib/sna/install/license.sna >> /var/ifor/nodelock
Monitoring Usage of CS/AIX Resources

While CS/AIX licenses are based on concurrent users of the product, it is difficult for CS/AIX to actually measure or report the number of users for many of the different types of communications resources it provides. However, it may be useful to be able to monitor the usage of the different types of resources as an indicator of changes in overall usage or peak usage that may occur. This information may be useful as you work with the sample scenarios shown at http://www.ibm.com/ software/network/commserver to better understand the number of concurrent CS/AIX User licenses that are required. CS/AIX monitors the usage of the following types of communications resources it provides: v Applications which use the APPC or CPI-C APIs (for example, DB2 or WebSphere) v Applications which use the LUA API (usually user developed) v Active link stations (may be to a host, adjacent APPN node or LEN node, Enterprise Extender, or downstream DLUR or SNA gateway client) v Telnet sessions connecting to the TN3270E server component of CS/AIX, whether or not they use SSL data encryption or client / server authentication v Telnet sessions connecting to the TN Redirector component of CS/AIX (for example VT sessions that are redirected) in order to use SSL data encryption or client / server authentication v Active SNA data sessions (Active sessions to LUs of type 1, 2 or 3. Active LU6.2 sessions, excluding those used for control of the network.)
28

The utilization of each resource is measured at periodic intervals in time, and the usage of CS/AIX measured at that time is recorded in a usage log file which is then available for your analysis and use. At each sampling time, both the current usage of the resource and the peak usage (since the last reboot of the system) are recorded. For more information about usage logging, refer to IBM Communications Server for AIX Diagnostics Guide.
How the CS/AIX Licensed Program Is Packaged

The CS/AIX Licensed Program Product (LPP) consists of several packages (installable images), which each contain one or more filesets. A fileset is the smallest installable unit of the product. AIX maintains release and level information for each fileset (see the AIX lslpp command in Displaying Product Installation Details on page 31). The licensed program can also contain update files. Note: For storage requirements, see Installation Requirements on page 20. The following filesets are required when you install CS/AIX: sna package sna.rte CS/AIX base program. sna.msg.Language package CS/AIX message catalog, containing messages and dialog help files in the specified language for the run-time environment. The following fileset is required: sna.msg.Language .rte Messages and dialog help files for the base CS/AIX features. Language indicates the language in which the messages are to be displayed. Choose one of the following language identifiers:
Identifier en_US Ja_JP de_DE es_ES fr_FR ko_KR pt_BR zh_CN zh_TW Language English (United States) Japanese (PC) German Spanish French Korean Portuguese Chinese (Simplified EUC) Chinese (Traditional)
If you install multiple languages for a product, be sure that you install the preferred (or primary) language first. For example, to install U.S. English as the primary language, specify: sna.msg.en_US.rte sna.rte is a prerequisite for sna.msg.Language.rte. Filesets for SSL support The following filesets are included for Secure Sockets Layer (SSL) support with TN Server or TN Redirector:
29

gskta.rte AIX Certificate and SSL Base Runtime.
Features Included with CS/AIX

The following features are included as part of CS/AIX. You can choose to install them or not. sna.xsna Motif administration program. sna.rte, X11.base.rte, and X11.Dt.helprun are prerequisites for sna.xsna. sna.wa Web administration program. sna.rte is a prerequisite for sna.wa. sna.lu0 LU 0 facilities. sna.rte is a prerequisite for sna.lu0. sna.docs.Language.data Online documentation. Language indicates the language in which the documents are to be displayed (for example, fr_FR for French). sna.man.en_US.rte.data, sna.man.en_US.xsna.data, sna.man.en_US.lu0.data AIX manual pages for CS/AIX commands. sna.msg.Language.snapi, sna.msg.Language.xsna, sna.msg.Language.wa Messages and dialog help files for optional CS/AIX features. You need to install these filesets only if you are installing the corresponding filesets for the optional features. Language indicates the language in which the messages are to be displayed (for example, fr_FR for French). sna.snapi SNA Application Development Toolkit (SNAPI). sna.rte is a prerequisite for sna.snapi. sna.rte64 Filesets for 64bit API support. sna.rte is a prerequisite for sna.rte64. sna.dlcmpc SNA Channel Data Link. sna.ecl Host Access Class Library. Communications.Bnd Bundle definition for use with Easy-Install (as described in Installation Methods on page 33).
Preparing for CS/AIX Installation

Before installing CS/AIX, you must be running AIX Version 5.2, 5.3 or 6.1. (For AIX V6.1, the server must run in the Global Environment, not in a system or application WPAR.) Perform the following tasks: v Install and configure any DLCs needed for communication over the network as described in Installing Data Link Control Filesets on page 31. (DLCs must be installed and configured before you can use CS/AIX; but you can also install DLCs after installing CS/AIX.)
30
Preparing for CS/AIX Installation

v If you intend to use the Web administration program and have not yet installed a suitable Web server, install it now. The Web servers supported by CS/AIX are listed in Installation Requirements on page 20. Follow the installation instructions provided with the Web server software. v To ensure that product dialogs and messages are handled correctly, make sure that the LANG environment variable is set properly, as described in Changing the Language Environment Variable.
Installing Data Link Control Filesets

CS/AIX requires at least one AIX data link control (DLC) fileset in order to communicate over the network. The following is a list of these DLC filesets: v bos.dlc.token for token ring link stations v bos.dlc.ether for standard Ethernet link stations v bos.dlc.8023 for 802.3 Ethernet link stations v bos.dlc.qllc for X.25 link stations v bos.dlc.sdlc for SDLC link stations All bos.dlc filesets are provided as part of the bos.dlc.usr package in the AIX base operating system. DLCs must be installed separately. Note: For more information about AIX data link controls, refer to AIX Communications Programming Concepts.
Displaying Product Installation Details

You can display the installation history for CS/AIX (and for some related products) by entering one of the following commands:
Enter: lslpp -h sna.rte For Product: IBM Communications Server for AIX
To display the program temporary fixes (PTFs) that have been applied to the products since they were installed, enter the command with the -ha flag instead of the -h flag.
Changing the Language Environment Variable

When you use CS/AIX, make sure that the LANG variable is not set to C. Use the following procedure to show which LANG variable is in use or to change the LANG variable: 1. From the main SMIT menu, select System Environments. 2. From the next SMIT menu, select Manage Language Environment. 3. From the next SMIT menu, select Change/Show Primary Language Environment. 4. From the next SMIT menu, select Change/Show Cultural Convention, Language, or Keyboard. 5. Select the language you want to use. For example, if you are using U.S. English messages, select en_US.
31
Migrating from previous levels of CS/AIX
Migrating from previous levels of CS/AIX Considerations

If you are upgrading to CS/AIX V6.4 from an earlier version of CS/AIX, you need to consider the following. 1. If you are running CS/AIX in a Client/Server configuration with two or more servers, you are advised to upgrade all the servers to V6.4 at the same time, before upgrading the Remote API Clients. v While you are in the process of migrating the servers, you will not be able to use the Motif administration program or command-line administration program on a back-level server to view and manage resources on a server running V6.4. v Version 6.3.1.0 and later versions of the Remote API Client will work with an existing server, but only if the operating system on the client is not configured to use IPv6. v Earlier versions of the Remote API Client will work with CS/AIX V6.4. 2. Several data structures in the NOF API were modified in Version 6.2.3.0 to accept the longer address formats required for IPv6 addresses. This means that, if you use any of the following verbs and/or indications in an existing NOF application that was created before Version 6.2.3.0 (even if you are not using the new IPv6 addressing capabilities), you will need to recompile the application to use it with CS/AIX V6.4. v DEFINE_LS, DEFINE_PORT, QUERY_LS, QUERY_PORT when used with an Enterprise Extender (HPR/IP) LS or port v DEFINE_TN3270_ACCESS, DELETE_TN3270_ACCESS, QUERY_TN3270_ACCESS v DEFINE_TN3270_EXPRESS_LOGON, QUERY_TN3270_EXPRESS_LOGON v DEFINE_TN3270_SSL_LDAP, QUERY_TN3270_SSL_LDAP v DEFINE_TN_REDIRECT, QUERY_TN_REDIRECT_DEF v QUERY_LU_0_TO_3 (for any LU type) v TN_REDIRECTION_INDICATION 3. If you want to use the new IPv6 addressing capabilities of V6.4, you need to ensure that the CS/AIX servers are configured to use IPv6 addressing. See IPv4 and IPv6 Addressing on page 23 for more details.
Installing the CS/AIX Licensed Program

After you have installed the pre-requisite software, you are ready to install CS/AIX. Use the following procedure: 1. Log in with root privileges. 2. Install and configure the associated AIX DLC for the selected communication adapter. To configure the DLC, use the mkdev command (described in AIX Commands Reference) or the Communications option on the SMIT Devices menu (described in AIX Communications Programming Concepts). 3. Install CS/AIX as described in Installation Methods on page 33. Select the features you wish to install (including any applicable message filesets), or select all to install CS/AIX with all of its included features. If you select a feature and choose yes for the Install requisite software field, the system also installs sna.rte (the CS/AIX base program).
32

4. If you installed the AIX Certificate and SSL Base Runtime software in order to use TN Server or TN Redirector with the SSL feature, you need to configure the SSL software after you have installed CS/AIX. See Configuring SSL for use with TN Server or TN Redirector on page 38 for more information. 5. Customize CS/AIX configuration information as needed (see Chapter 8, Configuring and Using CS/AIX, on page 71, or refer to IBM Communications Server for AIX Administration Guide). 6. Start CS/AIX. Note that after installation this will happen automatically when the machine is rebooted. cd / sna start Note: 1. Installing CS/AIX automatically reconfigures the SNA device drivers on the local node. If you already had CS/AIX v6.1 installed on AIX 5.3 and are now upgrading to V6.4, you will need to reboot after installing CS/AIX before the SNA node can be started. Otherwise you do not need to reboot, restart, or reconfigure the kernel before starting CS/AIX. 2. You can install adapters after CS/AIX is installed. You do not need to reinstall CS/AIX after adding an adapter; but you cannot use the adapter until the appropriate DLC is installed.
Installation Methods
You can install the CS/AIX licensed program using one of the following methods: v Easy-install v On the local system v Over the network (if the local node is a network server)
Installing CS/AIX Using Easy-Install

You can install software more easily by using software bundles. A software bundle contains a list of software products that are suited for a particular use. The following sections shows how to install CS/AIX using this feature. Easy-Install can be run either at the system console or remotely, and run either under X-Windows or from an ASCII terminal. Install CS/AIX on the local node as described in Easy-Install Using SMIT or Easy-Install Using Common Desktop Environment. Easy-Install Using SMIT: 1. Log in with root privileges. 2. Enter the following command: v smit install_bundle 3. Press PF4, or click on the List button in Motif, to display a list of installation devices and directories for the installation media. 4. Select Media-defined, and press Enter. 5. Select your input device, and press Enter. Easy-Install Using Common Desktop Environment: 1. From the desktop launch pad, open the Tools Application Manager. 2. Open the System_Admin folder. 3. Open Easy Install.
33

4. Select your input device. 5. Select the Media-defined bundle. 6. Click the Install/Update button.
Installing Manually on the Local Node

Install CS/AIX on the local system as described in Installing Manually Using SMIT or Installing Manually Using Common Desktop Environment on page 35. Installing Manually Using SMIT: 1. Put the installation medium into the appropriate drive on the AIX workstation. 2. Log in with root privileges. 3. Make sure that the LANG environment variable on your system is not set to C. If you are selecting U.S. English messages, set the LANG variable to en_US. For more information about how to show or change the LANG environment variable, see Changing the Language Environment Variable on page 31. 4. Enter the following command on the AIX command line: smit install This command invokes SMIT, which provides a menu-driven environment for the installation. 5. Select the following options on SMIT installation menus to perform a standard installation of selectable software with updates: a. Install and Update Software b. Install/Update Selectable Software (Custom Install) c. Install/Update From All Available Software This sequence of menu selections is comparable to the following fastpath command: smit install_selectable_all On the resulting dialog, select the appropriate device name for the installation medium as the source device for the installation procedure. (To list the device names, use PF4 in the character interface for SMIT or the List button in Motif.) Select sna.rte, the CS/AIX base program, sna.msg.Language.rte (the CS/AIX message catalog), and any additional features and updates for the licensed program (including any other applicable message filesets). To install all of the features on the installation medium, select the all option. The installation utility displays status messages as each part successfully completes installing. To install the AIX Certificate and SSL Base Runtime software in order to use TN Server or TN Redirector with the SSL feature, also select the AIX Certificate and SSL Base Runtime fileset. The installation utility displays status messages as each part successfully completes installing. If you installed this software, you need to configure the SSL software after you have installed CS/AIX. See Configuring SSL for use with TN Server or TN Redirector on page 38 for more information. Customize CS/AIX configuration information (see Chapter 8, Configuring and Using CS/AIX, on page 71, or refer to IBM Communications Server for AIX Administration Guide).
6.
7.
8.
9.
Note:
34

1. Installing CS/AIX automatically reconfigures the SNA device drivers on the local node. If you already had CS/AIX v6.1 installed on AIX 5.3 and are now upgrading to V6.4, you will need to reboot after installing CS/AIX before the SNA node can be started. Otherwise you do not need to reboot, restart, or reconfigure the kernel before starting CS/AIX. 2. For information about user licensing for CS/AIX, see CS/AIX Licensing Mechanisms on page 27. Installing Manually Using Common Desktop Environment: 1. Put the installation medium into the appropriate drive on the AIX workstation. 2. Log in with root privileges. 3. Make sure that the LANG environment variable on your system is not set to C. If you are selecting U.S. English messages, set the LANG variable to en_US. For more information about how to show or change the LANG environment variable, see Changing the Language Environment Variable on page 31. 4. From the desktop launch pad, open the Tools Application Manager. 5. Open the System_Admin folder. 6. Open the Install Manager folder. 7. Select your input device. 8. Select every object shown to install everything on the medium, or expand and select individual objects to customize the Communications Server for AIX options to install. 9. Click on the Install icon to begin installation. 10. Customize CS/AIX configuration information (see Chapter 8, Configuring and Using CS/AIX, on page 71, or refer to IBM Communications Server for AIX Administration Guide). Note: 1. Installing CS/AIX automatically reconfigures the SNA device drivers on the local node. If you already had CS/AIX v6.1 installed on AIX 5.3 and are now upgrading to V6.4, you will need to reboot after installing CS/AIX before the SNA node can be started. Otherwise you do not need to reboot, restart, or reconfigure the kernel before starting CS/AIX. 2. For information about user licensing for CS/AIX, see CS/AIX Licensing Mechanisms on page 27.
Installing over a Network Using Network Installation Management

Use this procedure to install CS/AIX over a network: 1. Refer to AIX Version 5.3 Installation Guide and Reference for information about setting up the Network Installation server and downloading files to the client. 2. Make sure that the LANG environment variable on your system is not set to C. If you are selecting U.S. English messages, set the LANG variable to en_US. For more information about how to show or change the LANG environment variable, see Changing the Language Environment Variable on page 31. 3. Enter the following command on the AIX command line: smit nim This command invokes SMIT, which provides a menu-driven environment for the installation. 4. Follow the directions and answer the prompts on the SMIT installation menus for performing a network installation. Select the files that contain sna.rte and
35

any additional features and updates for the licensed program. The installation utility displays status messages as each part successfully completes installing. Note: 1. The CS/AIX message catalog, sna.msg.Language.rte, automatically installs with CS/AIX when the Include corresponding LANGUAGE filesets? option is set to yes (the default). 2. Installing CS/AIX automatically reconfigures the SNA device drivers on the local node. If you already had CS/AIX v6.1 installed on AIX 5.3 and are now upgrading to V6.4, you will need to reboot after installing CS/AIX before the SNA node can be started. Otherwise you do not need to reboot, restart, or reconfigure the kernel before starting CS/AIX. 3. For information about user licensing for CS/AIX, see CS/AIX Licensing Mechanisms on page 27.
Configuring WebSphere Application Server

If you will be running a client/server system in which Remote API Clients connect to CS/AIX servers using HTTPS, you will need a computer running WebSphere Application Server to provide HTTPS access from these clients to the servers, as described in Installation Requirements on page 20. This section describes how to set up WebSphere for use with CS/AIX: v Setting up a secure certificate on the WebSphere server that will be presented to clients v Configuring WebSphere Application Server to work with CS/AIX v Installing the server configuration file on the WebSphere server You will also need to set up the client security certificate and the client network data file on each Remote API Client to access the WebSphere Application Server. For more information, see the chapter on installing the appropriate client type.
Setting up the WebSphere Application Servers secure certificate

Refer to the WebSphere Application Server documentation for instructions on setting up a secure certificate on the server. This is the servers certificate that will be presented to a Remote API Client during the authentication process when it tries to connect using HTTPS. You are recommended to configure WebSphere so that it enforces client authentication; see the WebSphere Application Server documentation for more information. This means that WebSphere will request security certificates from Remote API Clients during the authentication process, and will accept an incoming connection from a Remote API Client only if it can verify the authenticity of the clients certificate.

To configure WebSphere Application Server to operate with CS/AIX, take the following steps. Refer to the WebSphere Application Server documentation for more information. 1. Copy or FTP the two files snahttpsrv.ear and snahttpsrv.cfg from the ibm-commserver-https directory on the Remote API Client installation CD to
36

a directory on the computer where the WebSphere administration console runs, or to a network directory that can be accessed from this computer. If the administration console is running on Windows, copying the files is not necessary because you can access the files direct from the CD. You just need to insert the Remote API Client installation CD into the Windows computers CD drive. Start the WebSphere administration console. Follow the WebSphere documentation to create a virtual host that is accessible only via an SSL secured connection. This virtual host will be used for the Java plug-in that manages SNA HTTPS connections. From the menu bar, choose Applications, Install New Application. Specify the location of the snahttpsrv.ear file. Choose the Next button. When prompted to specify a virtual host name in the first two screens, enter the name of the virtual host that you have set up for HTTPS. For all other parameters you can accept the default options unless you need to use any specific WebSphere configuration; choose the Next button on the following dialogs until it is replaced by a Finish button, and then choose the Finish button. The screen should then show Application installed successfully. Click on Save to Master Configuration, and then click on the Save button.
2. 3.
4. 5. 6.
7.
8. From the menu bar, choose Applications, Enterprise Applications. 9. Find SnaHttpTransport in the list of applications, click on the checkbox next to it, and click on the Start button to start the application. (After this, the application will be started automatically when WebSphere Application Server is started.) 10. From the menu bar, choose Environment, Update Web Server Plugin, and click the OK button. This updates the WebSphere configuration.
Installing the server configuration file

To operate with CS/AIX, the WebSphere Application Server requires a list of the CS/AIX servers that will be accessed using HTTPS. Create and install this list using the following steps. 1. In the WebSphere administration console menu bar, choose Environment, Manage WebSphere Variables. 2. Look for the USER_INSTALL_ROOT variable in this list, and note its value (which is the path of a directory on the WebSphere server). The list of environment variables may span two or more pages, so you may need to use the Next button to scroll through the list. 3. Copy the snahttpsrv.cfg file from the location where you saved it in Configuring WebSphere Application Server on page 36 (or from the installation CD) into the directory specified by the USER_INSTALL_ROOT variable, and then edit this file using a text editor to include a list of CS/AIX servers that can be accessed by Remote API Clients using HTTPS. Each server must be specified on a separate line of the file, in the following format: server=servername.domainname.com
Post-Installation Procedures
This section explains how to perform maintenance tasks that may be required after installing CS/AIX.
37
Client/Server Operation
After installation, CS/AIX initially operates as a standalone server (with all components on a single AIX system). If you want to run it as a server in a client/server domain, refer to the chapter on Managing CS/AIX Client/Server Systems in IBM Communications Server for AIX Administration Guide for instructions.
Viewing PDF Books

The manuals included on the installation media for this product are in Portable Document Format (PDF). Softcopy format enables you to search, browse, or print the information easily, using hypertext links for related information. It also makes it easier to share the library across your site, because PDF viewers are available for many different platforms. If you choose to install the PDF manuals when installing the product, they are installed in the directory /usr/share/man/info/Language/sna. The HTML file SNABOOKS.HTM in this directory provides a hypertext link to each manual. The manuals are also included in the directory /DOCS on the CS/AIX installation media. You can read the PDF manuals using any PDF viewer, such as Adobe Acrobat on Windows or xpdf on Intel Linux.
Reviewing Current Release Information

The latest update of the README file for the product, contained in the /usr/lpp/sna directory, contains information about any product changes following the publication of the CS/AIX library. Review the README file whenever you receive product updates. The README file can be accessed through SMIT, using the following procedure: 1. After installing CS/AIX V6.4, access the main SMIT menu for CS/AIX by entering the following command on the command line: smit sna The main SMIT menu for CS/AIX is displayed. 2. Select Product Information from the main SMIT menu for CS/AIX. SMIT displays the Product Information dialog. 3. Select one of the options on that menu to view the associated README file.
Configuring SSL for use with TN Server or TN Redirector

If you installed the AIX Certificate and SSL Base Runtime software in order to use TN Server or TN Redirector with the SSL feature, you need to configure the SSL software after you have installed CS/AIX. The SSL software requires two components: v A key pair is required to allow data encryption and decryption to be carried out. v A certificate is required to allow server authentication. The certificate and key pair make up a single record in a keyring database, which is stored on the CS/AIX server running TN Server or TN Redirector. CS/AIX uses the database to implement SSL. To manage the keyring database, type the following command at the AIX command prompt:
38
snakeyman The snakeyman command launches a Java program. See the help provided with this program for further instructions. Each record in the database is identified by a unique name known as a label. If you have two or more records to use on different TN Server or TN Redirector sessions, you need to make a note of the labels you assign when setting up the database; these labels are used to identify which record is to be used on each session. You can also identify one of the records as the default, so that sessions will use this record unless you explicitly specify the label of a different record. After using snakeyman to update the server certificates, you need to exit the snakeyman program and then stop and restart the CS/AIX node in order to use the updated certificates. Use the following commands to stop and restart the node: snaadmin term_node snaadmin init_node
Configuring a Web Server for the Web Administration Program

If you are using the Web administration program with a Web server that is not listed in Installation Requirements on page 20, or if you install the Web server after installing CS/AIX, you need to set up links between CS/AIX directories and the Web servers directories, so that the Web server can find the required files. Use the ln command to create these links. v The Web servers servlets directory must be linked to /usr/lib/sna/WebAdmin/ Server. v The subdirectory SnaAdmin in the Web servers public HTML directory must be linked to /usr/lib/sna/WebAdmin/Client. For more details of how to set up the Web server, refer to the text file /usr/lpp/sna.wa/README, which is installed when you install the CS/AIX Web Admin package.
Host Access Class Library

If you choose to install the Host Access Class Library files when installing the product, they are installed in the directory /usr/share/lib/sna/ecl. For more information about these files, see the file readme.htm in the same directory.
Backing Up CS/AIX Configuration Files

CS/AIX automatically backs up the node, domain, TN3270 device data (tn3270dev.dat), and TP configuration files whenever you make changes that affect those files (using any of the CS/AIX administration tools). For example, when you make a change that affects the node configuration file (sna_node.cfg), CS/AIX creates a backup file named sna_node.bkn, where n is either 1 or 2: v The first time you change the file, the existing configuration is saved to sna_node.bk1. v The second time you change the file, the existing configuration is saved to sna_node.bk2, leaving sna_node.bk1 unchanged. v The third time you change the file, and any subsequent times, sna_node.bk1 is discarded, sna_node.bk2 is renamed to sna_node.bk1, and the existing configuration is saved to sna_node.bk2.
39
This process means that there is a maximum of two backup files for the node configuration file at any time. The same process is used to generate filename extensions for other backup files. In addition to automatic backups, you should back up configuration files to protect against loss of data under any of the following conditions: v Before installing a new level of the AIX operating system v Before installing a new release of CS/AIX v After you create a new configuration You can back up configuration files using the following commands: cd /etc/sna /bin/ls -1 sna*cfg sna.net sna_tps ibmcs.* | backup -i -v -q -f Devicename In these commands, Devicename is the path and file name of a device to receive data from the files being backed up. Ideally, back up files to external media such as diskette or tape.
Restoring a Backup Copy of CS/AIX Configuration Files

To restore CS/AIX configuration files that were backed up as described in Backing Up CS/AIX Configuration Files on page 39, do the following: 1. Ensure that CS/AIX is not active. To determine whether it is, enter the following command: snaadmin status_node If CS/AIX is active, the command displays information about the local nodes status; otherwise it displays a message indicating that CS/AIX is inactive. If CS/AIX is active, enter the following command to deactivate it: sna stop 2. Enter the following commands: cd /etc/sna restore -x -f Devicename In this command, Devicename is the path and file name of the device you used when backing up the files. This command overwrites any existing configuration files with the same names in the /etc/sna directory.
Reinitializing Configuration Files

If CS/AIX configuration files are inadvertently modified so that the information in them can no longer be used, you may need to reinitialize the files so that you can reconfigure CS/AIX as though it were newly installed. This should be done only if you are sure the configuration information cannot be salvaged. Note: If you have backup configuration files that are valid, you can copy those files to the /etc/sna directory and use them to initialize the node using the sna start command. You can reinitialize the following configuration files: v Node configuration file sna_node.cfg
40
v Domain configuration file sna_domn.cfg v TP configuration file sna_tps v SSL keyring database file and password stash file Perform the following steps to reinitialize configuration files: 1. Exit the administration program if it is active, and disable CS/AIX by issuing the following command: sna stop 2. Back up the existing configuration files by copying any files you are reinitializing to a different location. 3. Delete the files you are reinitializing. 4. If you deleted the domain configuration file, issue the following command to recreate it (by copying from the empty domain configuration file delivered with CS/AIX): cp -p /usr/lib/sna/samples/empty.cfg /etc/sna/sna_domn.cfg This command creates a new domain configuration file, which is required to start CS/AIX. 5. If you deleted the SSL keyring database file, issue the following command to recreate it (by copying from the sample file delivered with CS/AIX): cp -p /usr/lib/sna/samples/ibmcs.* /etc/sna 6. Issue the following command to restart CS/AIX: sna start 7. Start the Motif administration program: xsnaadmin & If the sna_node.cfg file does not exist, the administration program prompts you to configure the node. You can continue by configuring the node and the other resources as described in Chapter 8, Configuring and Using CS/AIX, on page 71 or IBM Communications Server for AIX Administration Guide. If you used a valid sna_node.cfg file, the new configuration file is used to initialize the node.
41
42
Chapter 4. Installing IBM Remote API Clients on Linux

This chapter describes how to install the IBM Remote API Client on Linux, which enables a Linux workstation to run SNA applications without having a complete SNA stack installation. A Remote API Client on Linux can connect to one or more CS/AIX servers (or CS Linux servers, but not both at the same time) using a TCP/IP network. (CS Linux servers cannot operate in the same domain as CS/AIX servers.) This chapter applies to IBM Remote API Clients running on 32bit Intel (i686), 64bit AMD64/Intel EM64T (x86_64) and pSeries (ppc64) computers. If you are installing the IBM Remote API Client on a System z computer (s390 / s390x), refer to Chapter 5, Installing IBM Remote API Clients on Linux for System z, on page 49. The installation program and associated files, including the IBM Remote API Client README file, are located on the installation CD, in the appropriate directory for your client type:
Client Type 32bit Intel (i686) 64bit AMD64/Intel EM64T (x86_64) pSeries (ppc64) Directory On CD /ibm-commserver-clients/linux /ibm-commserver-clients/linux-x86_64 /ibm-commserver-clients/linuxppc64
You are recommended to read the IBM Remote API Client README file before installing the software. If you are upgrading from an earlier version of CS/AIX and the Remote API Clients, you are recommended to upgrade all the servers before upgrading the Remote API Clients. See Migrating from previous levels of CS/AIX on page 32 for more details.
Hardware and Software Requirements Hardware Requirements

The IBM Remote API Client requires a computer supported by one of the Linux distributions below. Use the command uname -m to verify the CPU class of your target computer. The following table shows the appropriate hardware for each client type and the response from the uname -m for this hardware.
Client Type 32bit Intel 64bit AMD64/Intel EM64T pSeries Hardware Pentium II or later 32bit Intel system, or Opteron-based system x86_64 (AMD64 or Intel EM64T) system pSeries POWER5 or OpenPower system uname response i686 x86_64 ppc64
43
Hardware and Software Requirements
Linux Operating System Version

The current version of the IBM Remote API Client has been tested with the following Linux operating system versions. It may also run satisfactorily on other Linux distributions. v v v v v RedHat Enterprise Linux 4 (RHEL4) RedHat Enterprise Linux 5 (RHEL5) SUSE Linux Enterprise Server 9 (SLES9) SUSE Linux Enterprise Server 10 (SLES10) SUSE Linux Enterprise Server 11 (SLES11)
Refer to the README file on the installation CD for details of which optional packages may be required.
Java
If you use the Java CPI-C API, you will require Java software. Refer to the README file on the installation CD for details.
GSKIT
If the client will connect to CS/AIX servers using HTTPS, you will require GSKIT software to enable HTTPS access to the servers through a WebSphere server. The GSKIT software is included on the installation CD, but some optional Linux operating system packages may be required in order to install it; refer to the README file on the installation CD for details of which optional packages may be required. If all of the prerequisite packages are installed when you run the client installation process, described later in this chapter, the GSKIT software is installed automatically as part of this process. Otherwise you can install it later.

You can display information about the Remote API Client and related software packages that are already installed. To list all the installed packages, use the following command: rpm -q -a To view more details of a specific package, use the following command: rpm -q -i packagename packagename is the base name of the installed package, for example ibm-commserver-client.
Setting the Language Environment Variable

Use the following command to change the LANG variable to indicate the language you want to use: export LANG=language Replace language with the identifier for the language you want to use, which can be one of the following:
44

Identifier en_US ja_JP de_DE es_ES fr_FR ko_KR pt_BR zh_CN zh_TW Language English (United States) Japanese (PC) German Spanish French Korean Portuguese Chinese (Simplified EUC) Chinese (Traditional)
Installing the Remote API Client on Linux

After you have installed the pre-requisite software, you are ready to install the IBM Remote API Client. If you have a previous level of IBM Remote API Client already installed, follow the steps in section Uninstalling the Remote API Client on Linux on page 47 to remove it before installing this new level. Any configuration information will be left in place for use by the new installation. 1. Log in with root privileges. 2. Mount the CD and make it the current directory. mount /dev/cdrom cd /media/cdrom The directory name /media/cdrom may be different if you have a DVD drive. Use the command df to see where Linux mounted the CD. 3. Change to the appropriate subdirectory on the CD, and run the shell script to install the client. The example below shows the /linux subdirectory for a 32bit Intel (i686) client; replace this with /linux-x86_64 or /linux-ppc64 if required. cd ibm-commserver-clients/linux ./installibmcscli The shell script will test for certain pre-requisites and issue warning messages if they are not met. You will be prompted to read and accept the license agreement, then the script will install the RPMs. If the appropriate pre-requisites are already installed, the script will also install the GSKIT software. 4. Add the IBM Remote API Client binary directories to your PATH. You may want to change your profile to do this automatically: export PATH=$PATH:/opt/ibm/sna/bin export LD_LIBRARY_PATH=/usr/lib:/opt/ibm/sna/lib export LD_RUN_PATH=/usr/lib:/opt/ibm/sna/lib For Java CPI-C applications you should also set the following environment variable: export CLASSPATH=$CLASSPATH:/opt/ibm/sna/java/cpic.jar For some applications you may also need to set the LD_PRELOAD environment variable, but you should not make this a global change in your profile: export LD_PRELOAD=/usr/lib/libpLiS.so
45
Installing the Remote API Client on Linux

5. Start the IBM Remote API Client. After installation this will happen automatically when the machine is rebooted. Make sure you are not still in the CDs directories when you do this. cd / sna start Note: Before the IBM Remote API Client can connect to servers using HTTPS, you need to use the GSKIT key manager program to set up the security certificate configuration on the client. See Setting up HTTPS security certificates using GSKIT for more information. You will also need to update the client network data file to specify the CS/AIX servers to which the client can connect and the name of the WebSphere server that provides HTTPS support. See the section on managing Remote API Clients in IBM Communications Server for AIX Administration Guide for more details.
Setting up HTTPS security certificates using GSKIT

If the client will connect to CS/AIX servers using HTTPS, it must have the GSKIT key manager software installed. This normally occurs as part of the client installation, provided that the necessary Linux operating system pre-requisites are installed as described in the README file on the installation CD. If GSKIT was not installed as part of the client installation but you have now installed the pre-requisites, you can install the GSKIT software using the following steps. 1. Log in with root privileges. 2. Mount the CD and make it the current directory. mount /dev/cdrom cd /media/cdrom The directory name /media/cdrom may be different if you have a DVD drive. Use the command df to see where Linux mounted the CD. 3. Change to the appropriate subdirectory on the CD, and run the shell script to install the GSKIT software. The example below shows the /linux subdirectory for a 32bit Intel (i686) client; replace this with /linux-x86_64 or /linux-ppc64 if required. cd ibm-commserver-clients/linux ./installgskit Before the IBM Remote API Client can connect to servers using HTTPS, you need to use the GSKIT key manager program to set up the security certificate configuration on the client. Take the following steps. 1. Run the GSKIT key manager using the following command: /opt/ibm/sna/bin/snakeyman From within the key manager user interface, open the key database file /etc/opt/ibm/sna/ibmcs.kdb, which is in CMS format. 2. The initial password for the key database is ibmcs. Before setting up the security certificates, you must change this password to keep your configuration secure. In the dialog for changing the password, you will need to mark the checkbox Stash the password to a file? to ensure that the new password is saved so that the client can open the key database.
46

3. Obtain a copy of the Certificate Authority (CA) certificate that was used to sign the Web Servers security certificate, and install it in the key database. To do this, select Signer Certificates from the key manager user interface and click on Add. 4. If the WebSphere server is configured to require client security certificates, the client must have a certificate issued by a CA whose own certificate is in the Web Servers security certificate database. To request a new certificate: a. Select Create, New Certificate Request from the key manager user interface, and fill in the requested details. b. Save the certificate, extract it to a file and send it to the CA. c. When the certificate is issued, store it in the Web Servers database. To do this, select Personal Certificates from the key manager user interface and click on Receive. As a temporary measure for your own internal testing, you can create a self-signed client certificate rather than obtaining a certificate from the CA. However, this does not provide the required level of security and must not be used in a live system. To create a self-signed certificate: a. Select Create, New Self-Signed Certificate from the key manager user interface, and fill in the requested details. b. Save the certificate and extract it to a file. c. Store the certificate file in the Web Servers database. To do this, select Personal Certificates from the key manager user interface and click on Receive. 5. Exit the GSKIT key manager when you have finished configuring certificates.
Uninstalling the Remote API Client on Linux

You can uninstall the Remote API Client on Linux by using the following commands. /usr/bin/sna stop rpm -e ibm-commserver-ptf rpm -e ibm-commserver-docs rpm -e ibm-commserver-ecl rpm -e ibm-commserver-cli rpm -e ibm-commserver rpm -e gsk7bas /sbin/shutdown -r now Not all of the packages listed in these commands will be installed on every system. Uninstalling IBM Remote API Client on Linux will leave any customized configuration information behind for use by a later installation.
47
48
Chapter 5. Installing IBM Remote API Clients on Linux for System z

This chapter describes how to install the IBM Remote API Client on Linux, which enables a System z mainframe to run SNA applications without having a complete SNA stack installation. A Remote API Client on Linux for System z can connect to one or more CS/AIX servers (or CS Linux servers) using a TCP/IP network. You are recommended to read the IBM Remote API Client README file before installing the software. This file is located in the /ibm-commserver-clients/linuxsystemz directory on the installation CD. If you are upgrading from an earlier version of CS/AIX and the Remote API Clients, you are recommended to upgrade all the servers before upgrading the Remote API Clients. See Migrating from previous levels of CS/AIX on page 32 for more details.

The IBM Remote API Client requires a 31bit or 64bit System z system supported by one of the Linux distributions listed in Linux Operating System Version. Use the command uname -m to verify the CPU class. It must report s390 to indicate a 31bit environment or s390x to indicate a 64bit environment.
Linux Operating System Version

The current version of the IBM Remote API Client has been tested with the following Linux operating system versions. It may also run satisfactorily on other Linux distributions. v RedHat Enterprise Linux 4 for S/390 (RHEL4s390) v RedHat Enterprise Linux 4 for zSeries (RHEL4s390x) v RedHat Enterprise Linux 5 for System z (RHEL5s390x) v SUSE Linux Enterprise Server 9 for IBM Mainframe (SLES9s390*) v SUSE Linux Enterprise Server 10 for IBM Mainframe (SLES10s390x) Refer to the README file on the installation CD for details of which optional packages may be required.
Java
If you use the Java CPI-C API, you will require Java software. Refer to the README file on the installation CD for details.
GSKIT
If the client will connect to CS/AIX servers using HTTPS, you will require GSKIT software to enable HTTPS access to the servers through a WebSphere server. The GSKIT software is included on the installation CD, but some optional Linux operating system packages may be required in order to install it; refer to the
49

README file in the /ibm-commserver-clients/linux-systemz directory on the installation CD for details of which optional packages may be required. If all of the prerequisite packages are installed when you run the client installation process, described later in this chapter, the GSKIT software is installed automatically as part of this process. Otherwise you can install it later.

You can display information about the Remote API Client and related software packages that are already installed. To list all the installed packages, use the following command: rpm -q -a To view more details of a specific package, use the following command: rpm -q -i packagename packagename is the base name of the installed package, for example ibm-commserver-client.
Setting the Language Environment Variable

Use the following command to change the LANG variable to indicate the language you want to use: export LANG=language Replace language with the identifier for the language you want to use, which can be one of the following:
Identifier en_US ja_JP de_DE es_ES fr_FR ko_KR pt_BR zh_CN zh_TW Language English (United States) Japanese (PC) German Spanish French Korean Portuguese Chinese (Simplified EUC) Chinese (Traditional)
Installing the Remote API Client on Linux for System z

After you have installed the pre-requisite software, you are ready to install the IBM Remote API Client. If you have a previous level of IBM Remote API Client already installed, follow the steps in section Uninstalling the Remote API Client on Linux for System z on page 53 to remove it before installing this new level. Any configuration information will be left in place for use by the new installation. 1. Copy or FTP the ibm-commserver-client6.4.0.0s390x.tgz file from the /ibm-commserver-clients/linux-systemz directory on the CD-ROM to the Linux System z system. Ensure that you use binary mode to copy or FTP the file.
50
Installing the Remote API Client on Linux for System z

2. Log into the Linux System z system as root. 3. Uncompress and unpack the tar file into an empty temporary directory: mkdir /tmp/ibmcs cd /tmp/ibmcs tar xzf ibm-commserver-client6.4.0.0s390x.tgz 4. Run the installibmcscli shell script: ./installibmcscli This shell script tests for certain pre-requisites and issues warning messages if they are not met. It also prompts you to confirm that you have read and accepted the CS/AIX license terms. You can override this prompt by specifying additional parameters on the installibmcscli command as described below. When you have responded to the prompt, the shell script installs the rpm packages. If the appropriate pre-requisites are already installed, the script will also install the GSKIT software. 5. Add the IBM Remote API Client binary directories to your PATH. You may want to change your profile to do this automatically: export PATH=$PATH:/opt/ibm/sna/bin export LD_LIBRARY_PATH=/usr/lib:/opt/ibm/sna/lib export LD_RUN_PATH=/usr/lib:/opt/ibm/sna/lib If you will be running 64bit applications, use the following: export LD_LIBRARY_PATH=/usr/lib64:/opt/ibm/sna/lib64 export LD_RUN_PATH=/usr/lib64:/opt/ibm/sna/lib64 For Java CPI-C applications you should also set the following environment variable: export CLASSPATH=$CLASSPATH:/opt/ibm/sna/java/cpic.jar For some applications you may also need to set the LD_PRELOADenvironment variable, but you should not make this a global change in your profile: export LD_PRELOAD=/usr/lib/libpLiS.so 6. Start the IBM Remote API Client. After installation this will happen automatically when the machine is rebooted. Make sure you are not still in the CDs directories when you do this. cd / sna start 7. When you are done with the installation, you can erase the tgz file and temporary directory that were created during the installation process. Note: Before the IBM Remote API Client can connect to servers using HTTPS, you need to use the GSKIT key manager program to set up the security certificate configuration on the client. See Setting up HTTPS security certificates using GSKIT on page 52 for more information. You will also need to update the client network data file to specify the CS/AIX servers to which the client can connect and the name of the WebSphere server that provides HTTPS support. See the section on managing Remote API Clients in IBM Communications Server for AIX Administration Guide for more details.
51

If the client will connect to CS/AIX servers using HTTPS, it must have the GSKIT key manager software installed. This normally occurs as part of the client installation, provided that the necessary Linux operating system pre-requisites are installed as described in the README file on the installation CD. If GSKIT was not installed as part of the client installation but you have now installed the pre-requisites, you can install the GSKIT software using the following steps. 1. Copy or FTP the ibm-commserver-client6.4.0.0s390x.tgz file from the /ibm-commserver-clients/linux-systemz directory on the CD-ROM to the Linux System z system. Ensure that you use binary mode to copy or FTP the file. 2. Log into the Linux System z system as root. 3. Uncompress and unpack the tar file into an empty temporary directory: mkdir /tmp/ibmcs cd /tmp/ibmcs tar xzf ibm-commserver-client6.4.0.0s390x.tgz 4. Run the installgskit shell script: ./installgskit 5. When you are done with the installation, you can erase the tgz file and temporary directory that were created during the installation process. Before the IBM Remote API Client can connect to servers using HTTPS, you need to use the GSKIT key manager program to set up the security certificate configuration on the client. Take the following steps. 1. Run the GSKIT key manager using the following command: /opt/ibm/sna/bin/snakeyman From within the key manager user interface, open the key database file /etc/opt/ibm/sna/ibmcs.kdb, which is in CMS format. 2. The initial password for the key database is ibmcs. Before setting up the security certificates, you must change this password to keep your configuration secure. In the dialog for changing the password, you will need to mark the checkbox Stash the password to a file? to ensure that the new password is saved so that the client can open the key database. 3. Obtain a copy of the Certificate Authority (CA) certificate that was used to sign the Web Servers security certificate, and install it in the key database. To do this, select Signer Certificates from the key manager user interface and click on Add. 4. If the WebSphere server is configured to require client security certificates, the client must have a certificate issued by a CA whose own certificate is in the Web Servers security certificate database. To request a new certificate: a. Select Create, New Certificate Request from the key manager user interface, and fill in the requested details. b. Save the certificate, extract it to a file and send it to the CA. c. When the certificate is issued, store it in the Web Servers database. To do this, select Personal Certificates from the key manager user interface and click on Receive. As a temporary measure for your own internal testing, you can create a self-signed client certificate rather than obtaining a certificate from the CA. However, this does not provide the required level of security and must not be used in a live system. To create a self-signed certificate:
52

a. Select Create, New Self-Signed Certificate from the key manager user interface, and fill in the requested details. b. Save the certificate and extract it to a file. c. Store the certificate file in the Web Servers database. To do this, select Personal Certificates from the key manager user interface and click on Receive. 5. Exit the GSKIT key manager when you have finished configuring certificates.
Uninstalling the Remote API Client on Linux for System z

You can uninstall the Remote API Client on Linux for System z by using the following commands. /opt/ibm/sna/bin/sna stop rpm -e ibm-commserver-ptf rpm -e ibm-commserver-docs rpm -e ibm-commserver-ecl rpm -e ibm-commserver-cli rpm -e ibm-commserver rpm -e gsk7bas /sbin/shutdown -r now Not all of the packages listed in these commands will be installed on every system. Uninstalling IBM Remote API Client on Linux for System z will leave any customized configuration information behind for use by a later installation.
53
54
Chapter 6. Installing IBM Remote API Clients on AIX Systems

This chapter describes how to install the IBM Remote API Client on AIX, which enables an AIX workstation to run SNA applications without having a complete SNA stack installation. A Remote API Client on AIX can connect to one or more CS/AIX servers (or CS Linux servers) using a TCP/IP network. You are recommended to read the IBM Remote API Client README file before installing the software. This file is located in the /ibm-commserver-clients/aix directory on the installation CD.If you are upgrading from an earlier version of CS/AIX and the Remote API Clients, you are recommended to upgrade all the servers before upgrading the Remote API Clients. See Migrating from previous levels of CS/AIX on page 32 for more details.

The IBM Remote API Client requires a pSeries system supported by one of the AIX operating systems listed in Operating System Version.
Operating System Version

The current version of the IBM Remote API Client has been tested with the following operating system versions. v AIX v5.2ML7 or later v AIX v5.3ML3 or later v AIX 6.1 or later The client can run in the Global Environment, or in a system or application WPAR. You must ensure that any WPAR in which the client runs has a unique hostname that DNS can resolve.
Java
If you use the Java CPI-C API, you will require Java software. The latest Java SDK available from http://www.ibm.com/developerworks/java/jdk satisfies all the requirements. Install the Java SDK package with the installp command.
GSKIT
If the client will connect to CS/AIX servers using HTTPS, you will require GSKIT software to enable HTTPS access to the servers through a WebSphere server. Refer to the README file in the /ibm-commserver-clients/aix directory on the installation CD for details. The GSKIT software is installed as part of the main client installation process, described later in this chapter.
Changing the Language Environment Variable

When you use the Remote API Client, make sure that the LANG variable is not set to C.
55

Use the following procedure to show which LANG variable is in use or to change the LANG variable: 1. From the main SMIT menu, select System Environments. 2. From the next SMIT menu, select Manage Language Environment. 3. From the next SMIT menu, select Change/Show Primary Language Environment. 4. From the next SMIT menu, select Change/Show Cultural Convention, Language, or Keyboard. 5. Select the language you want to use. For example, if you are using U.S. English messages, select en_US.
Installing the Remote API Client on AIX

After you have installed the pre-requisite software, you are ready to install the IBM Remote API Client. If you have a previous level of IBM Remote API Client already installed, follow the steps in section Uninstalling the Remote API Client on AIX on page 58 to remove it before installing this new level. Any configuration information will be left in place for use by the new installation.
Installing the Remote API Client by copying files to your AIX workstation
To install the Remote API Client, take the following steps. 1. Copy or FTP the sna.client.6.4.0.0.I file from the /ibm-commserver-clients/aix directory on the CD-ROM to the AIX workstation. Ensure that you use binary mode to copy or FTP the file. If the client will connect to CS/AIX servers using HTTPS, you also need to copy or FTP the two files gskta.*.I and gsksa.*.I from the same directory on the CD. These files contain the GSKIT software required for HTTPS access from the client. 2. Log into the AIX workstation as root. 3. Install the AIX Client using either smit or installp. For instructions on how to do this, see the README file in the /ibm-commserver-clients/aix directory on the installation CD. 4. If the client will connect to CS/AIX servers using HTTPS, install the GSKIT files according to the instructions in the README file. 5. When the installation process has completed, you can delete the sna.client.6.4.0.0.I file and the GSKIT files from the working directory. 6. Start the IBM Remote API Client. After installation this will happen automatically when the machine is rebooted. cd / sna start Note: Before the IBM Remote API Client can connect to servers using HTTPS, you need to use the GSKIT key manager program to set up the security certificate configuration on the client. See Setting up HTTPS security certificates using GSKIT on page 57 for more information. You will also need to update the client network data file to specify the CS/AIX servers to which the client can connect and the name of the
56
Installing the Remote API Client on AIX

WebSphere server that provides HTTPS support. See the section on managing Remote API Clients in IBM Communications Server for AIX Administration Guide for more details.
Installing the Remote API Client from the CD

To install the Remote API Client, take the following steps. 1. Log into the AIX workstation as root. 2. Mount the CD on the AIX workstation, using the following command. mount -o ro /dev/cd0 /mnt 3. Install the AIX Client using either smit or installp. For instructions on how to do this, see the README file in the /ibm-commserver-clients/aix directory on the installation CD. 4. If the client will connect to CS/AIX servers using HTTPS, install the GSKIT files according to the instructions in the README file. 5. When the installation process has completed, unmount the CD using the following command. unmount /mnt 6. Start the IBM Remote API Client. After installation this will happen automatically when the machine is rebooted. Make sure you are not still in the CDs directories when you do this. cd / sna start Note: Before the IBM Remote API Client can connect to servers using HTTPS, you need to use the GSKIT key manager program to set up the security certificate configuration on the client. See Setting up HTTPS security certificates using GSKIT for more information. You will also need to update the client network data file to specify the CS/AIX servers to which the client can connect and the name of the WebSphere server that provides HTTPS support. See the section on managing Remote API Clients in IBM Communications Server for AIX Administration Guide for more details.

Before the IBM Remote API Client can connect to servers using HTTPS, you need to use the GSKIT key manager program to set up the security certificate configuration on the client. Take the following steps. 1. Run the GSKIT key manager using the following command: /usr/bin/snakeyman From within the key manager user interface, open the key database file /etc/sna/ibmcs.kdb, which is in CMS format. 2. The initial password for the key database is ibmcs. Before setting up the security certificates, you must change this password to keep your configuration secure. In the dialog for changing the password, you will need to mark the checkbox Stash the password to a file? to ensure that the new password is saved so that the client can open the key database.
Chapter 6. Installing IBM Remote API Clients on AIX Systems
57

3. Obtain a copy of the Certificate Authority (CA) certificate that was used to sign the Web Servers security certificate, and install it in the key database. To do this, select Signer Certificates from the key manager user interface and click on Add. 4. If the WebSphere server is configured to require client security certificates, the client must have a certificate issued by a CA whose own certificate is in the Web Servers security certificate database. To request a new certificate: a. Select Create, New Certificate Request from the key manager user interface, and fill in the requested details. b. Save the certificate, extract it to a file and send it to the CA. c. When the certificate is issued, store it in the Web Servers database. To do this, select Personal Certificates from the key manager user interface and click on Receive. As a temporary measure for your own internal testing, you can create a self-signed client certificate rather than obtaining a certificate from the CA. However, this does not provide the required level of security and must not be used in a live system. To create a self-signed certificate: a. Select Create, New Self-Signed Certificate from the key manager user interface, and fill in the requested details. b. Save the certificate and extract it to a file. c. Store the certificate file in the Web Servers database. To do this, select Personal Certificates from the key manager user interface and click on Receive. 5. Exit the GSKIT key manager when you have finished configuring certificates.
Uninstalling the Remote API Client on AIX

You can uninstall the Remote API Client by using the following commands. 1. Stop the client software if it is running, using the following command. sna stop 2. Log in with root privileges. 3. Remove the Remote API Client package and associated software packages by using one of the following commands. To remove the package using installp: installp u sna.client To remove the package using smit: smit remove
58
Chapter 7. Planning for and Installing the Remote API Client on Windows
This chapter describes how to install the IBM Remote API Client on Windows, which enables a PC to run SNA applications without having a complete SNA stack installation on the PC. A Remote API Client on Windows can connect to one or more CS/AIX servers (or CS Linux servers) using a TCP/IP network. If you are upgrading from an earlier version of CS/AIX and the Remote API Clients, you are recommended to upgrade all the servers before upgrading the Remote API Clients. See Migrating from previous levels of CS/AIX on page 32 for more details. There are two variants of the IBM Remote API Client on Windows, depending on the specific hardware and Windows version you are using. The information in this chapter applies to both variants except where differences are noted explicitly. v The 32bit client runs on a 32bit Intel-based computer running Microsoft Windows 2000, Windows 2003, Windows XP, 32bit Windows Vista, or 32bit Windows Server 2008. v The x64 client runs on an AMD64 or Intel EM64T computer running Microsoft Windows 2003 Server x64 Edition, Windows XP Professional x64 Edition, 64bit Windows Vista, or 64bit Windows Server 2008. The interfaces provided by the IBM Remote API Client on Windows are broadly compatible with those provided by the IBM Communications Server for Windows and Microsoft Host Integration Server products. The IBM Remote API Client on Windows Software Development Kit (SDK) is an optional package that allows you to use the Remote API Client to develop application programs using the APPC, CPI-C, LUA, and CSV APIs. Refer to the appropriate programmers reference guide for more information about these APIs. You do not need to install this package if the Remote API Client will be used only to run existing applications (not to develop new ones).

To run the Setup program and the Remote API Client on Windows, the computer must meet the following requirements: v It must be running one of the following operating systems. For up-to-date information about specific version numbers that are supported for each operating system version, and any additional requirements for specific versions, please refer to the Windows client information in the README file on the installation CD for more details. : For the 32bit Windows client: - Windows 2000 - Windows XP - Windows 2003 - 32bit Windows Vista - 32bit Windows Server 2008
59

For the x64 Windows client: - Microsoft Windows XP Professional x64 Edition - Microsoft Windows 2003 Server x64 Edition - 64bit Windows Vista - 64bit Windows Server 2008 v It must have access to one or more CS/AIX servers using one of the following mechanisms: Access to the server over a TCP/IP network Access to a WebSphere server that provides HTTPS access to CS/AIX servers. Note: Depending on the Windows version that you are using, or the specific Remote API Client features tha you want to use, there may be some additional configuration that you need to perform before you can install and use the Remote API Client on Windows. Refer to the Windows client information in the README file on the installation CD for more details.
Accessing the Setup Program

The Remote API Client and SDK software, the GSKIT software, and the Setup program are included on the installation CD in Windows format, so that you can install them from the CD on the Windows computer. You must install the Remote API Client software on each Windows client PC; this also installs the GSKIT software automatically. The SDK is required only if you will be using the client to develop new applications using the Windows Remote APIs, and is not required if you will be using it only to run existing applications. The Remote API Client on Windows installation image is a self-extracting ZIP executable file, delivered on the installation CD. v For the 32bit client, it is i_w32cli.exe in the directory /ibm-commserver-clients/ windows on the CD. v For the x64 client, it is i_w64cli.exe in the directory /ibm-commserver-clients/ win-x64 on the CD. You can copy this file to other Windows PCs across the network, so that you can install them without direct access to the CS/AIX delivery CD. When you run this executable, it unzips the installation image and automatically runs the Setup program. If you simply want to unzip the installation image to a temporary directory, for example to run the Setup program from the command line, you can do so by loading the self-extracting ZIP executable into your unzip program. The first time you run the Setup program on a particular computer, the program runs from the selected source. The program handles the complete installation process, sets up a basic configuration, and also installs and creates an icon for itself. After installation is complete, you can use the Setup program (either by selecting it from the File Manager or by selecting its icon) if you need to reinstall the software. After you have extracted the Remote API Client installation image into a temporary directory, you can install the software in either of two ways: v Run the Setup program through Windows, as explained in Installing Remote API Client on Windows Using the Setup Program on page 61. You must use this method if you want to install the SDK.
60
Accessing the Setup Program

v Enter the setup command from the command line, as explained in Installing Remote API Client Software from the Command Line on page 64. This method does not allow you to install the SDK. Note: Before the IBM Remote API Client can connect to servers using HTTPS, you need to update the client network data file to specify the CS/AIX servers to which the client can connect and the name of the WebSphere server that provides HTTPS support. See the section on managing Remote API Clients in IBM Communications Server for AIX Administration Guide for more details.
Installing Remote API Client on Windows Using the Setup Program

Run the setup program, either automatically as part of executing the self-extracting ZIP executable i_w32cli.exe (32bit client) or i_w64cli.exe (x64 client), or manually from the command line. The program first displays a Choose Setup Language screen. 1. Select the language that you want to use for installing and configuring the Remote API Client, and choose OK. The program displays a Welcome screen that introduces you to the Setup program. 2. Choose Next to continue with the installation. The program displays the Software Licensing Agreement, which you should read and understand. 3. If you are happy to accept the licensing terms, choose Accept to continue. The program prompts you to specify a destination directory into which the files are to be installed. 4. Enter the destination directory. The program asks you to choose the type of installation you want: Standard Choose this option if you do not need to install the SDK. The SDK is required only if you will be using the client to develop new applications using the Windows Remote APIs, and is not required if you will be using it only to run existing applications. Developer Choose this option if you need to install the SDK: that is, if you will be using the client to develop new applications using the Windows Remote APIs. Note: If you want to install the SDK, you must choose Developer. 5. Choose the installation type. The program then asks you to enter the name of the program folder in which you wish icons for the Remote API Client on Windows to appear. 6. Enter the folder name. 7. If the System directory already contains .DLL files with names that are the same as files used by this Setup program but are not Remote API Client files (for example, files from some other SNA software), the program prompts you to do one of the following: v Copy the Remote API Client .DLL files over the existing .DLL files v Copy the existing .DLL files to a subdirectory named OTHERSNA within the installation directory, and then install the Remote API Client .DLL files. This option enables you to restore the original setup from before the
61

Remote API Client installation if you uninstall the files at a later time (see Uninstalling the Remote API Client Software on page 68). v Cancel the client software installation. If the Remote API Client .DLL files are already present, the Setup program displays a message indicating this. New .DLL files will overwrite the existing .DLL files only if the existing files have lower version numbers than the Setup program .DLL files. 8. At this point, the Setup program copies files from the specified source, and installs them in the appropriate places. During this process, an information bar displays what portion of the installation is complete. The .DLL files are copied into the System or equivalent directory, and the other files are copied into the destination directory you specified in Step 2. During each file transfer operation, a record is written to the setup.log file, which is created in the directory you specified. If any of the files to be written over is read only, or any file cannot be copied for any other reason, the new files are removed and you receive a message advising you to look at the setup.log file. 9. If the source from which you are running the Setup program does not contain all the required files, the program prompts you for a directory name. Enter the name of a directory in which the required files are located. If the information you specified is not sufficient to locate copies of the Remote API Client files, the program displays this screen again. 10. When the required files have been copied, the Setup program displays the Configuration window. Default configuration values are taken from the domain configuration file. For more information, see the IBM Communications Server for AIX Administration Guide. If you do not want to use these default values, you can configure them as shown below: Domain Specify the CS/AIX client/server domain name. If the client uses IPv6 addressing, you must configure the following settings. They are optional if the client uses IPv4 addressing. Server Name The screen shows a list of up to nine servers to which this client can connect. The order in which servers appear in this list is the order in which the client selects these servers. If the client cannot connect to the first server on the list, the next server is tried. If the client uses IPv6 addressing, you must configure at least one server. If the client uses IPv4 addressing, you do not need to specify any servers if you use the UDP broadcasts option; if you specify one or more servers, the client will try these in turn if it cannot contact a server using UDP broadcasts. v To add a new server to the list, use the Add button. v To remove a server from the list, select the server and use the Remove button. v To move a server up or down the list, select the server and use the slide buttons at the side of the list. If the client is on the same private network as its servers and accesses them using TCP/IP, each server is identified simply by its server name.
62

If the client uses HTTPS to access its servers, you need to identify each server by specifying the name of the WebSphere server that provides HTTPS support and the name of the CS/AIX server, in the following format: webservername : servername1 This assumes that WebSphere is set up to use the default port 443 for HTTPS connections. If your network administrator has configured WebSphere to use a different port number, include the port number in the following format: webservername : portnumber : servername1 For more details about configuring WebSphere to support HTTPS connections, refer to Configuring WebSphere Application Server on page 36. UDP broadcasts Specify whether this client will use UDP broadcasts to connect to a server. When this option is selected, the client sends UDP broadcasts over the network to locate a server connection instead of trying to connect directly to a specific server. The default setting is to use UDP broadcasts. To change this setting, click on the box. If the client uses IPv6 addressing, UDP broadcasts are not supported. Switch off the option to use UDP broadcasts, and specify at least one Server Name. The following settings are optional: Advanced To supply additional values in place of the defaults supplied by the Setup program, click on the Advanced button at the bottom of the window. The Setup program displays the Advanced Options window, which contains advanced settings for Windows client configuration. Most users can use the default settings for these parameters, so you probably do not need to alter the settings in that dialog. For more information about these parameters, see Advanced Options for Remote API Client Configuration on page 64. For more information about any of the configuration parameters or settings, click on Help. 11. When you have completed the Configuration window, click on OK. The Setup program displays a message if you have not completed this screen properly. 12. When the installation has successfully completed, the Finish window is displayed. You can select either or both of the following actions to be taken after you exit the installation program: View README file View the README file. Start client Begin running this CS/AIX client. Choose Finish to exit the installation program.
63
Advanced Options for Remote API Client Configuration
Advanced Options for Remote API Client Configuration

The Advanced Options window enables you to configure some advanced parameters for the Remote API Client. Most users do not need to alter these parameters, but you can adjust the default settings if necessary. LAN access time-out Specify the time in seconds that the clients connection to a server can remain idle before it is closed. When this check box is empty, no LAN access time-out has been specified (and so an infinite time-out will be used). If you check this box, you can enter a time-out value in seconds in the adjacent field. The minimum value is 60 (for 60 seconds); if you leave the box blank or specify a value lower than 60, the Remote API Client uses the minimum value 60. Max. broadcast attempts Specify the maximum number of times the client attempts to connect to a server by broadcast. When the Advanced Options window is opened, the default value of 5 is displayed. The value in this box is used only if the UDP broadcasts check box is checked on the main Configuration window. Reconnect time-out Specify the time in seconds that the client waits before attempting to reconnect to a server after the server has gone down. When the Advanced Options window is opened, the default value of 200 is displayed. For more information about these parameters, press Help. When you have completed the Advanced Options window, click on OK. If you have completed the screen properly, the Setup program returns to the Configuration window. If you are installing a new Remote API Client, return to Step 11 on page 63. Otherwise, click on the OK button in the Configuration dialog to complete the configuration.
Installing Remote API Client Software from the Command Line

Note: If you want to install the SDK, you must use the Setup program, as explained in Installing Remote API Client on Windows Using the Setup Program on page 61. You cannot install the SDK from the command line. After you have extracted the Remote API Client installation image into a temporary directory, you can install the Remote API Client software from the command line instead of using the Setup program through Windows. At the command line, enter the setup command with one or more options. You can enter these options in uppercase or lowercase, and can precede them with a / (slash) or - (hyphen). If a parameter, such as folder, is a string that contains a space, you must enclose the string inside double quotes. After you enter the setup command, the Setup program prompts you for any information you have not included on the command line, and displays confirmation messages at various stages of the setup. If you do not want the Setup program to prompt you, use the -accept -s option to run the program in silent mode, accepting the terms of the Software License Agreement. Following are the setup command options:
64

-? -h Display a list of the command line options. This is the same as the -h option. Display a list of the command line options. This is the same as the -? option.
-accept -s Run the installation in silent mode, accepting the terms of the Software License Agreement. This agreement can be found in the license subdirectory of the Windows installation image. The -s option must be the last one in the command line, and you must be sure you have specified the domain name (using the -i option) and any other parameters that you want to specify. When the installation runs in silent mode, it does not prompt you for any parameters or display confirmation messages. Any command-line arguments after -s are ignored. -f2 Specify the full pathname of the installation log file that is created during silent mode installation (using the -s option). If you do not specify this option, the file is created as setup.log in the directory from which you run the installation program. If you are installing in silent mode from the CD drive, you must specify this option to ensure that the file is created on your computer (because it cannot be created on the CD drive). -kfolder Specify the Program folder. -pdirectory Specify the install directory. -idomain Specify a domain name for this client. This parameter is required; there is no default. -wdirectory Specify the source directory containing CS/AIX client software files if the source is located on a disk or CD. Otherwise, use the -v option. -vserver Specify the server from which the client software files are to be downloaded. You can specify either the server name or TCP/IP address. If you are copying the source files from a disk or CD, use the -w option instead of the -v option. -lserver Specify a server to be included in the list of servers this client can access. If the client is on the same private network as its servers and accesses them using TCP/IP, each server is identified simply by its server name. If the client uses HTTPS to access its servers, you need to identify each server by specifying the name of the WebSphere server that provides HTTPS support and the name of the CS/AIX server, in the following format: webservername : servername1 This assumes that WebSphere is set up to use the default port 443 for HTTPS connections. If your network administrator has configured WebSphere to use a different port number, include the port number in the following format:
65

webservername : portnumber : servername1 For more details about configuring WebSphere to support HTTPS connections, refer to Configuring WebSphere Application Server on page 36. -o Overwrite existing .DLL files. If the Remote API Client .DLL files are already present, the Setup program overwrites these files even if they have a higher version number than the Setup program .DLL files. Save existing .DLL files. If the Remote API Client .DLL files already exist in the required directories, the Setup program copies the existing .DLL files to a subdirectory of the install directory, and then installs the Remote API Client .DLL files. The copies in the subdirectory ensure that if you uninstall the Remote API Client software, the uninstall process will be complete. Cancel the installation if existing Remote API Client .DLL files are found.
-y
-n
-atimeout Specify the LAN access time-out in seconds. This is the length of time the clients connection to a server can remain idle before being closed. The value 0 indicates no time-out. -bmax-broadcast Specify the maximum number of UDP broadcast attempts. A UDP broadcast is a clients attempt to connect to any server in the domain rather than to a specific server. The value 0 indicates no broadcast attempts are made. -jreconnect-timeout Specify the time in seconds that the client waits before attempting to reconnect to a server after the server has gone down. The following is an example command line to install the Remote API Client: setup -imy_domain -lserver1.company.com -lserver2.company.com -b0 -j30 -accept -s -f2C:\instrapi.log -y In this example: v The client is installed in the domain my_domain. v The client has access to two servers in the same private network as the client, and does not use UDP broadcasts to contact any other servers. It waits for 30 seconds before reconnecting if it loses contact with a server. v The installation runs in silent mode, writing its installation log information to the file C:\instrapi.log on the client. v Existing copies of Remote API Client .DLL files are saved to a subdirectory before the new files are installed.

Before the IBM Remote API Client can connect to servers using HTTPS, you need to use the GSKIT key manager program to set up the security certificate configuration on the client. Take the following steps. 1. Run the GSKIT key manager program, which is installdir\snakeyman.exe. installdir represents the directory in which you installed the client software, which is C:\IBMCS\w32cli (32bit client) or C:\IBMCS\w64cli (64bit client) unless you specified a different location during the client installation.
66

From within the key manager user interface, open the key database file installdir\ibmcs.kdb, which is in CMS format. The initial password for the key database is ibmcs. Before setting up the security certificates, you must change this password to keep your configuration secure. In the dialog for changing the password, you will need to mark the checkbox Stash the password to a file? to ensure that the new password is saved so that the client can open the key database. Obtain a copy of the Certificate Authority (CA) certificate that was used to sign the Web Servers security certificate, and install it in the key database. To do this, select Signer Certificates from the key manager user interface and click on Add. If the WebSphere server is configured to require client security certificates, the client must have a certificate issued by a CA whose own certificate is in the Web Servers security certificate database. To request a new certificate: a. Select Create, New Certificate Request from the key manager user interface, and fill in the requested details. b. Save the certificate, extract it to a file and send it to the CA. c. When the certificate is issued, store it in the Web Servers database. To do this, select Personal Certificates from the key manager user interface and click on Receive. As a temporary measure for your own internal testing, you can create a self-signed client certificate rather than obtaining a certificate from the CA. However, this does not provide the required level of security and must not be used in a live system. To create a self-signed certificate: a. Select Create, New Self-Signed Certificate from the key manager user interface, and fill in the requested details. b. Save the certificate and extract it to a file. c. Store the certificate file in the Web Servers database. To do this, select Personal Certificates from the key manager user interface and click on Receive. Exit the GSKIT key manager when you have finished configuring certificates.
2.
3.
4.
5.
Customizing the Remote API Client Software after Installation

You can change any of the customized settings any time after the initial installation by running the Configuration Utility program, located in the CS/AIX program group. The program displays the same Configuration window that was displayed in the initial install process. You can change the information in any field by following the procedure in Installing Remote API Client on Windows Using the Setup Program on page 61. If you did not install the SDK files during the initial installation and you now want to add them, you can do this by running the Setup program again and choosing Developer for the installation type.
Reinstalling the Remote API Client Software

You can reinstall the Remote API Client software at any time, for example when you wish to upgrade the software. To do this, run the Setup program as before, using the instructions in Installing Remote API Client on Windows Using the Setup Program on page 61 or Installing Remote API Client Software from the Command Line on page 64. The
67
Reinstalling the Remote API Client Software

Setup program displays the location from which the client software files were copied during the initial installation. Click on OK to get new copies of the files from this same location. When you click on OK, the Setup program copies the files and returns to the Options screen. Note: If you are reinstalling the Remote API Client software in silent mode (as described in Installing Remote API Client Software from the Command Line on page 64), you may need to restart the computer to complete the installation. This is because some of the program files may be in use during the installation process (for example if the Remote API Client is running), and so cannot be replaced by the new files. In this case, the new files are copied to a temporary directory, and will be moved into place automatically when the computer is next restarted. To check whether you need to restart the computer, use a text editor such as Notepad to view the contents of the installation log file when the installation process has completed. The installation log file is called setup.log and is created in the directory from which you run the Setup program, unless you use the -f2 command-line option to specify a different path and filename. At the end of the file, under the heading Response Result, the text Result Code should be followed by one of the two values 0 (zero) or -12. If the value is 0, there is no need to restart the computer; if the value is -12, restart the computer before attempting to use the Windows Client.
Uninstalling the Remote API Client Software

You can uninstall the Remote API Client software at any time, by using the Add/Remove Programs option from the Windows Control Panel. Once the uninstall process is confirmed, Windows does the following: v Deletes all installed files. v If any .DLL files were saved to a subdirectory during the initial installation, restores files to their original location. v Deletes the subdirectory in which the saved .DLL files were stored, as long as the subdirectory is empty. v Removes the Program folder and created directory if they are empty. v If the uninstallation is successful, deletes the setup.log file, which contains all file transfers and deletions. v Displays a message saying either that the uninstallation was successful, or that the user should check the setup.log file because some part of the installation failed. The Exit button returns you to Windows.
Uninstalling the Remote API Client Software from the Command Line
Instead of using the Add/Remove Programs option from the Windows Control Panel, you can uninstall the Remote API Client software from the command line. Use the following command: installdir\sxcluninst -y
68
Uninstalling the Remote API Client Software from the Command Line
v installdir represents the directory in which you installed the client software, which is C:\IBMCS\w32cli (32bit client) or C:\IBMCS\w64cli (64bit client) unless you specified a different location during the client installation. v The -y option is used for confirmation, to prevent accidental use of this command. The uninstall program completes without prompts and does not require any further input.
Help
You can access Help at any time by pressing the F1 key. The Configuration and Advanced Options windows each have Help buttons as well.
69
70
Chapter 8. Configuring and Using CS/AIX

The easiest way to define and modify the CS/AIX configuration is to use the Motif administration program (xsnaadmin). This program provides a graphical user interface from which you can view and manage SNA resources on the local node. You can also use other administration tools such as the Web administration program or command-line administration, but the Motif program is recommended. The Motif administration program includes help screens that provide overview information for SNA and CS/AIX, reference information for CS/AIX dialogs, and guidance for performing specific tasks. For each task (such as configuring the node) or type of communications (such as TN3270 or APPC), the program guides you in setting up the configuration of the required resources. The Motif administration program enables you to set up all required parameters for standard CS/AIX configurations. For advanced parameters, the Motif administration program supplies default values. You need to supply only the essential configuration information, which enables you to set up SNA communications quickly and easily. You can also use the Motif administration program to manage the running CS/AIX system. The administration program enables you to make and apply changes to the configuration while CS/AIX is active, and provides easy access to status information for node resources. The Motif administration program automatically displays status information for CS/AIX resources. Most of this information is shown on the Node window (see Managing CS/AIX with the Motif Administration Program on page 74). In addition, you can control certain resourcessuch as nodes and link stationsusing the Start and Stop buttons on the Node window. Other resources are always started and stopped automatically, so there is no need to control them manually. Note: 1. You must be a member of the login group system to define or modify resources for CS/AIX. 2. To use the Motif administration program, you must have a low-function terminal (LFT) or an X-terminal. Otherwise, you can use the System Management Interface Tool (SMIT) or the Web administration program, which provide facilities similar to those in the Motif program. For more information, see IBM Communications Server for AIX Administration Guide. 3. For more information about the Motif administration programs user interface, including the buttons and icons that appear in its windows, refer to the programs help screens or to IBM Communications Server for AIX Administration Guide. 4. The windows and dialogs in the Motif administration program may differ from those shown in this guide, depending on the choices you make on a particular dialog. For information about other CS/AIX administration tools, including Web administration, command-line administration and NOF application programs, refer
71
Configuring and Using CS/AIX

to IBM Communications Server for AIX Administration Guide, IBM Communications Server for AIX Administration Command Reference, or IBM Communications Server for AIX NOF Programmers Guide.
Planning for CS/AIX Configuration

Before you make any configuration changes it is very important to plan thoroughly. Changes that you make can cause disruption, not only to the users of your local node but possibly to users all around the network. You may find it useful to draw a diagram of any changes that you are making to the topology of the network. If you are adding or removing connections to other nodes, draw a picture showing your node and the other nodes. You can use the Motif administration program to gather configuration information about all of the existing connections and add that information to your diagram. When you add new resources to your diagram, it is easy to see whether they duplicate existing ones, or whether any names clash. Similarly, your diagram can help you decide which resources you need to remove and help you avoid deleting essential ones. If you are configuring a Client/Server CS/AIX system with more than one node, ensure that you include all the CS/AIX nodes and their connectivity resources in your diagram. You can then configure each node in turn as described in this chapter, in the same way as you would configure a standalone node. Once you determine the changes you need to make, collect the configuration information that you need. To guide you in collecting configuration information for specific CS/AIX functions, you can use the task sheets provided in the online help for the Motif administration program, or the planning worksheets provided in IBM Communications Server for AIX Administration Guide. This chapter provides instructions for configuring the most frequently used functions available in CS/AIX. For each configuration task, this guide also notes the information you need to gather before configuring the resource. Note: This guide does not provide detailed descriptions of the configuration information you need to enter on CS/AIX dialogs. For more information about the fields on a particular dialog, consult the online help for that dialog in the Motif administration program or SMIT.
Planning Worksheets
Before you begin to configure resources for CS/AIX, gather all of the configuration data for the new resources. To record all of the information for a particular function or application that you need to support, use the planning worksheets provided in IBM Communications Server for AIX Administration Guide. You will probably need to gather configuration information from several sources, such as network administrators, host administrators, application programmers, and end users. If you are trying to connect to another node, the administrator at that node is a key contact. The administrator for a node can tell you names, addresses and
72
Planning for CS/AIX Configuration

characteristics of all the resources on that node. Often, you will need to ensure that matching configuration parameters are entered at the local node and the remote node.
Task Sheets
The online help screens in the Motif administration program contain task sheets that provide guidance for specific configuration tasks. The task sheets contain pointers to all of the help screens for the dialogs that you will use to enter the configuration information. You can use these to browse the help and see exactly what data you must collect. The task sheets also refer to more detailed help for each of the individual windows and dialogs that you must use to enter configuration information. Those help screens explain each field that you must fill in or select.
Using the Motif Administration Program

Before you use the Motif administration program, you may want to add path information to your .login or .profile file to enable the system to find executable programs (see Specifying the Path to CS/AIX Programs). In addition, you must enable the CS/AIX software before you can use the administration program (see Enabling CS/AIX). For information about invoking the Motif administration program and an overview of using the program, see Managing CS/AIX with the Motif Administration Program on page 74.
Specifying the Path to CS/AIX Programs

To run CS/AIX programs, you must specify the path to the directory that contains the CS/AIX executable programs. You can specify the path either by adding the directory to your PATH environment variable before you run the programs for the first time, or by including the directory name each time you run the programs. The Motif administration program is stored in the directory /usr/bin/X11, and the other programs are stored in the directory /usr/bin. If you add these directories to the definition of the PATH environment variable in your .login or .profile file, CS/AIX locates the programs automatically. Alternatively, you can specify the directory name when you run the program, as in the following examples: /usr/bin/sna start /usr/bin/X11/xsnaadmin The sample command lines shown in this manual assume that you have added the directories to your PATH environment variable, and do not include the directory names.
Enabling CS/AIX
CS/AIX must be enabled on the local system before you can configure or manage the local node. As with any X/Motif application, you may also need to set up the DISPLAY environment variable to indicate a suitable X server.
73

Normally, CS/AIX is enabled automatically after you install the software. If CS/AIX has been disabled, you can re-enable it by entering the following command at the AIX command prompt: sna start Note: When you use the sna start command, the CS/AIX software uses the directory from which you issued the command as its current working directory, and maintains one or more open file descriptors in that directory. This means that you will not be able to unmount the file system containing that directory while the CS/AIX software is running. To avoid problems, you should start the CS/AIX software from a directory on a filesystem that does not need to be unmounted; for example, you could use cd / to change to the root directory before using the sna start command. When you install CS/AIX, the installation utility automatically updates the startup file /etc/inittab to add an entry for /etc/rc.sna, which includes the sna start command. This ensures that CS/AIX is started automatically at system startup. If you do not want CS/AIX to be started automatically, you can remove or comment out this line, and then follow the instructions in this section to enable the CS/AIX software manually. CS/AIX writes messages to standard error (normally your terminals screen) to indicate that it is initializing, and to indicate whether initialization completes successfully.
Managing CS/AIX with the Motif Administration Program

To use the Motif administration program for CS/AIX, first make sure that CS/AIX is initialized as described in Enabling CS/AIX on page 73. (You may also need to set up the DISPLAY environment variable to indicate a suitable X server.) To start the Motif administration program in the background, issue the following command: xsnaadmin & CS/AIX displays the Domain window. This window shows all defined nodes, and enables you to start and stop nodes. Double-clicking on any node brings up the Node window for that node, as shown in Figure 4 on page 75. The Node window shows information about the node and its resources. If you have not yet configured the node, the administration program prompts you to configure it as described in Configuring the Node on page 79. Note: This guide uses the term window to describe Motif windows that display information about CS/AIX resources. A window can contain one or more sections, or panes. A dialog is a Motif window on which you can enter information. The Node window shows most of the information you need, and gives easy access to everything else. It shows all the key resources on the local node. If you are configuring a Client/Server CS/AIX system with more than one node, follow the instructions in this chapter to configure each node in turn (returning to the Domain window to select the next node).
74

Other windows can be reached from the Windows menu in the Node window. These windows include the following: v LU Pools window v CPI-C Destination Names window The Services menu in the Node window provides a quick way to add resources and provides help for configuration and management tasks. The Diagnostics menu takes you to the Logging dialog and Tracing dialog.
Node Window
A sample Node window is shown in Figure 4. The title bar shows the name of the AIX system.
Figure 4. Node Window
From the Node window, you can configure and manage all of the resources and components for the CS/AIX node. v Ports v v v v Link stations LUs of type 0-3 and dependent LUs of type 6.2 DLUR internal PUs Independent local LUs
75

v Remote nodes v Partner LUs You can add, delete, modify and manage all of these resources from the Node window. The layout of the resources in the window shows the relationships among resources and enables you to control which resources are displayed. Ports, local LUs, and remote nodes are always displayed. The Node window shows each link station below its parent port, and each dependent LU below its parent link station. It also shows partner LUs below local LUs and below remote nodes. The Node window contains separate sections for the different types of resources for the node: v The Node box in the top-right corner of the Node window indicates whether the node is Active or Inactive. v The top pane of the Node window (the Connectivity pane) lists connectivity resources for the node, including ports, link stations or PUs on each port, and dependent LUs on a specific link station or PU. For each resource, this window shows current status information. v The middle pane (the Independent Local LUs pane) shows independent LUs defined on the local node. This window also displays information about sessions using a particular LU, and any records that define a partner LUs location by the link station that is used to access it. v The lower pane (the Remote Systems pane) shows information about remote nodes and partner LUs. It also shows session information for each remote node or partner LU. You can select any of these panes by clicking on the pane. You can also select specific resources within a pane by clicking on the line for the resource. To view or modify the configuration for an item, you can double-click on the item. (You can use the buttons and menus on this window to access configuration information for specific resources.) For each item listed, resources that belong to that item are nested within the information for that item. For example, link stations are grouped under the port to which they belong. You can click on the Expand button (+) next to an item to show the resources for that item if they are not currently displayed, or click on the Contract button () to hide the resources for an item. You can perform the following administration tasks from the Node window: Start or stop a resource Select the resource and click on the Start or Stop button. (Alternatively, you can select Start item or Stop item from the Selection menu.) Add a resource for an item Select the item and click on the New button (or select New from the Selection menu). For example, to add a link station for a port, select the port and click on the New button. Delete a resource Select the resource and click on the Delete button (or select Delete from the Selection menu).
76

View or modify the configuration for any resource Select the resource and click on the Properties button (or select Properties from the Selection menu). Get status information for any resource Select the resource and click on the Status button (or select Status from the Selection menu). Copy the configuration for any resource Select the resource and click on the Copy button (or select Copy from the Selection menu). In addition, you can choose specific configuration tasks for the node from the Services menu, control logging (for the domain) and tracing (for the node) from the Diagnostics menu, and view or modify domain resources by selecting one of the items on the Windows menu.
Resource Items
The layout of the resources in a window shows the relationships among them. If an item has one or more child items associated with it, an Expand symbol (+) or Contract symbol () appears next to it: v An Expand symbol indicates that the associated child items are hidden. You can click on the Expand symbol, or press the + key on the numeric keypad, to show them. v A Contract symbol indicates that the child items are shown. You can click on the Contract symbol, or press the key on the numeric keypad, to hide them. v If an item has neither symbol next to it, the item has no associated child resources. For example, a link station is associated with a particular port. In the Connectivity pane of the Node window, the link station is displayed below its parent port, along with all other link stations associated with that port. The port is always displayed, but you can choose whether the list of associated link stations is shown or hidden. Similarly, link stations with a list of associated LUs can be expanded to show the LUs, or contracted to hide them. A parent resource must always be configured before its child resources, and deleting the parent resource causes all its child resources to be deleted too.
Tool Bar Buttons

Resource windows include tool bar buttons to make it easy to perform common functions. A tool bar for CS/AIX is shown in Figure 5.
Figure 5. CS/AIX Tool Bar
Not all buttons appear in the tool bars of each resource window. If a buttons operation is not valid for the currently selected item (or an operation requires an item to be selected, but none is), the outline of the button is displayed in gray, and the function cannot be selected (clicking on the button has no effect). The following buttons can appear on resource windows: Start Starts the selected item.
77

Stop New Stops the selected item. Adds a new resource item.
Delete Deletes the selected resources. Properties Opens the dialog for the selected item to view or modify the items configuration. Status Displays the current status of the selected item. Copy Copies the selected item. Clicking on this button opens a dialog whose fields duplicate the configuration of the selected item. Complete the dialogs fields (filling in the new items name) to add the new resource.
Many resources, such as ports and link stations, cannot be modified while they are active. You can, however, view an active resources parameters by selecting the resource and clicking on the Properties button to open its dialog. Click on the Close button when you are finished.
Configuring Client/Server Functions

This section is relevant only if you installed CS/AIX to run in a client/server environment (with multiple CS/AIX nodes in the same network). In a client/server environment, a server can be marked as a configuration server; CS/AIX maintains a list of these configuration servers. The first server listed is the master server, and any other servers listed are backup servers. The servers are listed in order, so that the second server listed (the first backup server) takes over if the master server is unavailable, the third server listed (the second backup server) takes over if neither the master nor the first backup server is available, and so on. When any of the nodes in the domain are active, the first available configuration server in the domain (the first server that can be contacted and has CS/AIX software running) becomes the master server. If the current master becomes unavailable (because it cannot be contacted, perhaps due to a network failure, or because the SNA software running on it is stopped), the next available configuration server in the list becomes the new master. CS/AIX can run without a master. This happens if none of the servers in the configuration server list can be contacted. If this happens, you can view and configure node resources only on the servers that can be contacted. Note: You cannot directly indicate which node acts as the master server; the master server is selected based on the order in which nodes are added to the configuration server list. If you wish to move a server to the top of the list, remove all other nodes from the list and then add them again. In the Motif administration program Domain window, you can add a configuration server by selecting Make configuration server from the Selection menu. The server is added to the end of the list; it becomes the master server only if all other configuration servers are unavailable. To remove a server, select Remove configuration server from the Selection menu. Note: You cannot delete a server if it is the only server listed on which the CS/AIX software is running, because in this case there is no other server
78
Configuring Client/Server Functions

that can take over as the master server. At least one enabled master server is required in a client/server configuration. For more information about configuring and managing a Client/Server CS/AIX system, refer to IBM Communications Server for AIX Administration Guide. This manual also provides information about advanced Client/Server configuration, including how to move clients and servers into different CS/AIX domains and how to configure the details of client operation.
Configuring the Node

The first step in configuring CS/AIX on a system is to configure the local node. Node configuration provides the basic information that the node needs in order to communicate in an SNA network. You must configure the node before you can define connectivity or other resources for the node. If the node has already been configured, you can use the procedures described in this section to modify the node configuration; but you must stop the node before making configuration changes. Before configuring the node, decide whether to configure the node as an APPN node or as a non-APPN node. This decision depends on the capabilities of the other SNA nodes with which you are communicating. A CS/AIX node that communicates directly with a host computer is shown in Figure 6.
Host
SNA Node
Figure 6. CS/AIX Node That Communicates Directly with a Host
If the host does not support APPN, configure the CS/AIX node as a LEN node. If the host supports APPN, you can configure the CS/AIX node as either an APPN network node or an APPN end node (if CS/AIX uses SNA only for communication with the host, you probably want to configure the CS/AIX node as an end node or branch network node). Several CS/AIX nodes in an APPN network are shown in Figure 7 on page 80.
79
Configuring the Node
AS/400 Network Node
Network Node
LEN Node End Node Network Node
Figure 7. CS/AIX Nodes in an APPN Network
When the local node is part of an APPN network, configure it as an APPN network node if the node is to provide APPN routing services for other nodes. If other nodes provide routing services, configure the local node as an APPN end node. If the local node only communicates with one directly connected node (which can be of any type), configure the node as a LEN node. Before you begin the node configuration, gather the following information: v Type of APPN support (network node, branch network node, end node, or LEN node). v Control point name (and alias, if different). Consult with your network planner to determine this name. v Default Node ID. (You can override this default when configuring an individual communications link.) To configure the node, perform the following steps from the Node window: 1. Select Configure node parameters from the Services menu, or double-click on the Node box in the top-right corner of the Node window. CS/AIX displays the Node Parameters dialog. 2. Specify the level of APPN support, the control point name, and (if necessary) the default node ID. 3. Click on the OK button to define the node. When you define the node, CS/AIX automatically defines a default LU with the same name as the control point. To exit without saving the values you have entered, click on the Cancel button.
Configuring Connectivity
For a CS/AIX node to communicate with other nodes, you must configure connectivity with at least one adjacent node. A connecting link can be configured to carry dependent traffic, independent traffic, or both. You can have adapter cards for one or more link protocols installed in your computer. Much of the information you need to enter to configure connectivity depends on the link protocol you are using. For a list of the link protocols supported by CS/AIX, see Installation Requirements on page 20.
80
To configure a link, you need to define a port and (in most cases) a link station. When using the Motif administration program, a DLC (data link control) is automatically configured as part of the configuration for the port. In addition, you have the option of defining the port as part of a connection network. The links that you need to configure depend on what you are trying to achieve, and on whether your network is an APPN network. The information required depends on the link protocol, and on whether the link is for dependent traffic, independent traffic, or both. As examples, this section explains how to configure the following types of links: v Link supporting dependent traffic with a host system using an SDLC line. v Link supporting both dependent and independent traffic into an APPN network using the Ethernet link protocol. This example also defines a connection network on the Ethernet port. v Enterprise Extender link into an APPN network (note that Enterprise Extender links support only independent traffic). For other link protocols, refer to IBM Communications Server for AIX Administration Guide or the online help for the Motif administration program.
Configuring an SDLC Link for Dependent Traffic

For an SDLC (synchronous data link control) port, you need the following information: v SNA port name (you can generally use the default). You also need to supply the SDLC device number. v Whether the port should activate automatically when the node is started. v Line type (switched outgoing, switched incoming, or leased line). v Link role (primary, secondary, negotiable, primary multi-drop, or secondary multi-PU). v Poll address (only for a switched incoming line on a nonprimary port). For other types of ports, you configure the poll address on the link station. For switched incoming and leased lines, you also need the encoding (NRZ or NRZI) and the duplex setting (half or full). For other types of ports, you configure the encoding and duplex setting on the link station. v Physical link type (to identify the type of modem). v Dial string (only needed for a switched incoming line). For a switched outgoing line, configure the dial string on the link station. For an SDLC link station, you need the following additional information: v Activation method (by administrator, on node startup, or on demand). v Type of traffic supported (for this example, dependent only). v Remote node role (for this example, host). To configure the SDLC link, perform the following steps from the Node window: 1. Configure the port: a. Select the Connectivity pane of the window. b. Select New port from the Connectivity submenu on the Services menu (or click on the New button in the button bar). c. On the resulting dialog, select the protocol type from the option menu, then choose to define a port.
81
When you click on the OK button, CS/AIX displays the SDLC Port dialog. d. Enter appropriate values in the fields on the dialog. e. Click on the OK button to define the port. The port appears in the Connectivity pane of the Node window. 2. Define a link station on the port: a. Make sure you have selected the port to which the link station is being added in the Connectivity pane of the Node window. b. Select New link station from the Connectivity submenu on the Services menu (or click on the New button in the button bar). c. Click on the OK button. CS/AIX displays the SDLC Link Station dialog. d. Enter appropriate values in the fields on the dialog. e. Click on the OK button to define the link station. The link station appears beneath the port to which it belongs in the Connectivity pane of the Node window.
Configuring an Ethernet Link to Support Dependent and Independent Traffic

This example shows how to configure an Ethernet link supporting both dependent and independent traffic into an APPN network. In addition, it defines a connection network on the Ethernet port. For an Ethernet port, you need the following information: v SNA port name (you can generally use the default). If you have multiple Ethernet network adapter cards, you also need to supply the Ethernet card number. You also need to specify the local SAP (service access point) number (normally 04). v Whether the port should activate automatically when the node is started. v Connection network name (must be the same on all ports in the same connection network). For an Ethernet link station, you need the following additional information: v Activation method (by administrator, on node startup, or on demand). v Type of traffic supported (for this example, both dependent and independent). v Remote node control point name (only needed for a LEN node). v Remote node type (network node, end node, or discover). v Remote node role (for this example, downstream SNA gateway or passthrough DLUR). v To configure a selective link station, you need the MAC (medium access control) address and the SAP number (normally 04) for the remote station. If you do not supply address information and you specify By administrator for the Activation field, the link station is a nonselective listening link station. To configure the Ethernet link, perform the following steps from the Node window: 1. Configure the port: a. Select the Connectivity pane of the window. b. Select New port from the Connectivity submenu on the Services menu (or click on the New button in the button bar).
82
c. On the resulting dialog, select the protocol type from the option menu, then choose to define a port. When you click on the OK button, CS/AIX displays the Ethernet SAP dialog. d. Enter appropriate values in the fields on the dialog. e. Click on the OK button to define the port. The port appears in the Connectivity pane of the Node window. 2. Define a link station on the port: a. Make sure you have selected the port to which the link station is being added in the Connectivity pane of the Node window. b. Select New link station from the Connectivity submenu on the Services menu (or click on the New button in the button bar). c. Click on the OK button. CS/AIX displays the Ethernet Link Station dialog. d. Enter appropriate values in the fields on the dialog. e. Click on the OK button to define the link station. The link station appears beneath the port to which it belongs in the Connectivity pane of the Node window.
Configuring an Enterprise Extender Link

This example shows how to configure an Enterprise Extender link into an APPN network. Note that Enterprise Extender links support only Independent LU traffic. For an Enterprise Extender port, you need the following information: v SNA port name (you can generally use the default). If you have multiple network adapter cards running IP, you also need to supply the IP interface name you want to use (such as eth0). v Whether the port should activate automatically when the node is started. For an Enterprise Extender link station, you need the following additional information: v Activation method (by administrator, on node startup, or on demand). v Remote node type (network node, end node, or discover). v To configure a selective link station, you need the IP hostname or IP address for the remote station. If you do not supply this information and you specify By administrator for the Activation field, the link station is a nonselective listening link station. To configure the Enterprise Extender link, perform the following steps from the Node window: 1. Configure the port: a. Select the Connectivity pane of the window. b. Select New port from the Connectivity submenu on the Services menu (or click on the New button in the button bar). c. On the resulting dialog, select the protocol type from the option menu, then choose to define a port. When you click on the OK button, CS/AIX displays the IP Port dialog. d. Enter appropriate values in the fields on the dialog. e. Click on the OK button to define the port.
83
The port appears in the Connectivity pane of the Node window. 2. Define a link station on the port: a. Make sure you have selected the port to which the link station is being added in the Connectivity pane of the Node window. b. Select New link station from the Connectivity submenu on the Services menu (or click on the New button in the button bar). c. Click on the OK button. CS/AIX displays the IP Link Station dialog. d. Enter appropriate values in the fields on the dialog. e. Click on the OK button to define the link station. The link station appears beneath the port to which it belongs in the Connectivity pane of the Node window.
Configuring Type 03 LUs

To support user applications that use type 03 LUs, you must configure dependent LUs. Before doing so, you must perform the following configuration: v Configure the node as described in Configuring the Node on page 79. v Configure a link to support dependent LU traffic as described in Configuring Connectivity on page 80. You do not need to configure a direct link to the host if you have an upstream link to another node using SNA gateway, or if you are using DLUR. For more information, see Configuring SNA Gateway on page 92 and Configuring DLUR on page 95. You must configure dependent LUs of types 03 to support communication with a host system. You can use the information in this section to define an LU to support LUA, DLUR, or PU Concentration. You can also define a range of LUs, to configure multiple LUs of the same type in a single operation. In addition, you can define a pool of LUs to be used as required, either by assigning an LU to a pool when you define the LU or by assigning previously defined LUs to a pool.
Defining Type 03 LUs

Before configuring the 3270 LU, gather the following information: v LU name. (This is a local identifier, and does not have to match the host configuration.) v LU number (or numbers for a range of LUs). v LU type (3270 display model or 3270 printer). v Pool name (if you are adding the LU to a pool). To configure an LU of types 03 for a previously defined link station, perform the following steps from the Node window: 1. Select the link station to the host in the Connectivity pane of the window. 2. Click on the New button. 3. Select the LU type (New 3270 display LU or New 3270 printer LU) on the resulting dialog. When you select this item and click on OK, CS/AIX displays the LU Type 03 dialog.
84
Configuring Type 03 LUs

4. Enter appropriate values in the fields on the dialog. 5. Click on OK to define the LU. The LU appears in the Connectivity pane of the Node window, below the link station to the host.
Defining an LU Pool
For LU type 03, you can define LU pools to simplify user configuration and provide greater flexibility in establishing host sessions. For example, you can define several LUs in a single LU pool, then configure multiple users using this LU pool. This makes configuring the users sessions easier and enables any session to use any LU in the pool. Note: You can assign a users session either to a specific LU or to an LU pool. v If you assign the users session to a specific LU that is in a pool, the session uses this LU if it is available; otherwise it uses any free LU from the pool, as though you had assigned it to the LU pool instead of the specific LU. v If you want the user to use only a specified LU, so that the users session cannot be established if the LU is already in use, ensure that the LU is not in a pool. You can view the LU pools for the local CS/AIX node using the LU Pools window. This window lists the LU pools configured on the local system, and enables you to select LUs to add to an LU pool. You can add the following LU types to a pool (do not mix LUs of different types in the same pool): v 3270 display LU v Unrestricted LU Before you can add LUs to a pool, the LUs must be defined on the local node. To configure an LU pool, perform the following steps from the Node window: 1. Select LU Pools from the Windows menu. CS/AIX displays the LU Pools window. 2. Click on the New button. CS/AIX displays the LU Pool Configuration dialog. The box on the right lists LUs that are not yet allocated to any pool. Any of these LUs can be included in the new pool. 3. Select the LU or LUs you wish to add to the pool, and click on the New button to move the selected LUs to the box on the left. To remove an LU from the box on the left, select it and click on the Remove button. 4. Click on OK to define the LU pool. All of the LUs in the box on the left are added to the LU pool. The pool appears in the LU Pools window.
85
Configuring APPC Communication

APPC applications and CPI-C applications require that you configure APPC first. An APPC application uses the nodes LU type 6.2 resources to communicate with another APPC or CPI-C application on a host or peer computer, using a specified mode. Before you can configure APPC communication, you must perform the following configuration: 1. Configure the node as described in Configuring the Node on page 79. 2. Configure connectivity as described in Configuring Connectivity on page 80. The remaining configuration steps depend on whether the configuration supports dependent traffic, independent traffic, or both: Independent APPC Independent APPC uses independent LUs. Each LU-LU session involves a local LU and a partner LU. For the local LU, you can use the predefined default LU associated with the node control point, or you can configure new local LUs. The partner LU need not be configured at all if the CS/AIX node is an end node or network node in an APPN network, because APPN can locate partner LUs dynamically. However, you do have to configure the partner LU if your network is not an APPN network or if the node is a LEN node. In this case, you must configure the remote node where the partner LU resides, then define the partner LU on the remote node. Dependent APPC If the remote node is a host that does not support independent LU 6.2, configure for dependent traffic. For dependent APPC, you must configure a local LU. If the applications use CPI-C, you may need to do additional CPI-C configuration after configuring APPC (see Configuring for CPI Communications on page 91). A CPI-C application uses the nodes LU type 6.2 and mode resources to communicate with another APPC or CPI-C application on a host or peer computer. You define the same resources for a CPI-C application as for an APPC application. In addition, if the TP on the CS/AIX computer is the invoking TP, also known as the source TP (the TP that starts the conversation), you may need to define one or more side information entries for it, as described in Configuring for CPI Communications on page 91. Each of these entries provides information on a partner TP, the LU and mode resources used to access it, and any security information required. This section explains how to configure a simple APPN network (using independent LU 6.2) that consists of a network node, an end node, and a LEN node, as described in Configuring a Simple APPN Network on page 87. (This scenario also shows how you can get status information for CP-CP sessions between two nodes.) This section also explains how to configure dependent APPC communication, as described in Configuring Dependent APPC on page 91. Both of these scenarios assume that APPC sessions use a standard mode and class-of-service (COS).
86

For information about configuring additional APPC information, such as modes, security, and invokable (target) TPs, refer to IBM Communications Server for AIX Administration Guide.
Configuring a Simple APPN Network

The simplest APPN network you can configure includes only two nodes: an APPN network node and an APPN end node. The network node handles session routing for the end node.
Configuring a Network Node

This scenario assumes that you are using the control point LU and a standard mode, and that you are using a LAN link type (Token Ring, Ethernet). In this case, you can configure the network node simply by performing the following configuration tasks: 1. Configure the node as described in Configuring the Node on page 79. For the APPN support field, select the value Network node. Make a note of the control point name. 2. Configure connectivity as described in Configuring Connectivity on page 80. Configure the link to support independent traffic. To contact this network node from an adjacent end node, youll need to know the MAC address and SAP number of the port on the network node. You can use the following procedure to get the MAC address on a CS/AIX node: 1. Select the port on the Node window. 2. Click on the Start button to start the port. 3. Click on the Status button to get status information for the port. The Port Status dialog shows the MAC address and SAP number. 4. Make a note of the MAC address and SAP number so you can enter those values on the link station configuration dialog for the end node.
Configuring an End Node

This scenario assumes that you are using the control point LU and a standard mode, and that you are using a LAN link type (Token Ring, Ethernet). In this case, you can configure the network node simply by performing the following configuration tasks: 1. Configure the node as described in Configuring the Node on page 79. For the APPN support field, select the value End node. 2. Configure connectivity as described in Configuring Connectivity on page 80. Configure the link to support independent traffic, and supply the following information for the link station: v Enter the name of the network node (see Configuring a Network Node) as the value for the Remote node field. v Enter the MAC address and SAP number for the port on the network node in the Contact Information pane on the link station configuration dialog. In an APPN network, a single link station to an adjacent network node can be used to communicate with any remote node in the network, so you do not need to configure a separate link station to each remote node.
Verifying Connectivity between Two Nodes

This scenario assumes that you have configured a network node as described in Configuring a Network Node, and an end node as described in Configuring an End Node. You can perform the following procedure from the end node:
87

1. On the Node window, select the link station that connects to the adjacent network node. 2. Click on the Start button to start the link station. When the link station is started, the CP-CP sessions between the two nodes are established automatically. Those sessions are displayed in the Independent Local LUs pane of the Node window. 3. To get status information for a session, select the session on the Node window and click on the Status button.
Configuring an Independent APPC LU

In many cases, applications can use the local nodes control point LU, which is automatically defined when you configure the node. This is the default LUif your application does not specify a particular LU, it can use this one. If the application uses the default LU, you do not need to define a local LU. Check the documentation for your APPC application, or contact the application programmer. To configure an independent LU 6.2, you need the following information: v Local LU name. v Local LU alias (if an alias is used in a TP that this LU supports). To configure an independent local LU, perform the following steps from the Node window: 1. Select the Independent Local LUs pane of the window. 2. Select New independent local LU from the APPC submenu on the Services menu (or click on the New button). CS/AIX displays the Local LU dialog. 3. Enter appropriate values in the fields on the dialog. 4. Click on the OK button to define the local LU. The independent LU appears in the Independent Local LUs pane of the Node window.
Configuring Partner LUs for a LEN Node

You must define a remote node (and the partner LUs on the node) in the following situations: v If the local node is a LEN node, you must define all of the remote nodes and any partner LUs on the remote node with which it communicates using APPC. A LEN node is not able to dynamically locate partner LUs; the remote node definition enables it to do so. v If the local node is not part of an APPN network (for example, if you have two end nodes directly connected, with no network node server), LUs cannot be located dynamically. In this case, you must configure each partner LU. v If the remote node is a LEN node and the local node is a network node that acts as the LEN nodes network node server, you must define the LEN node (and its partner LUs) as a remote node on the network node server. This definition enables nodes in the rest of the APPN network to locate LUs on the LEN node. v If the remote node is in a different APPN network, you must define the remote node because it cannot be dynamically located. Do not define partner LUs if both the local and remote nodes are part of the same APPN network. When you add a remote node definition, a partner LU with the same name as the remote node is automatically added; this is the control point LU for the remote node. If your application uses this partner LU, you do not need to add another
88

partner LU, although you may want to add an LU alias for the partner LU. To add an alias, double click on the partner LU and enter the alias in the Partner LU Configuration dialog. If your application uses an LU alias to refer to its partner LU, you should add a partner LU alias definition. If either the local node or the remote node is a LEN node, you must define the partner LU as a child of the remote node, because a LEN node cannot take part in dynamic location of LUs. If your application uses the control point LU of the remote node as its partner LU, the control point LU was defined automatically when you defined the remote node. You can use the Motif administration program to add a partner LU alias (see Defining a Partner LU Alias), add a definition of a partner LU on a specific remote node (see Defining a Partner LU on a Remote Node), or define multiple partner LUs using wildcards (see Defining Multiple Partner LUs Using Wildcards on page 90). Defining a Remote Node: Before configuring a remote node, you need the following information: v Fully qualified SNA network name of the node. To configure a remote node, perform the following steps from the Node window: 1. Select the Remote Systems pane of the window. 2. Select New remote node from the APPC submenu on the Services menu (or click on the New button in the button bar, then select Define remote node). CS/AIX displays the Remote Node Configuration dialog. 3. Enter appropriate values in the fields on the dialog. 4. Click on the OK button to define the remote node. The remote node appears in the Remote Systems pane of the Node window. When you define a remote system, CS/AIX automatically defines the control point LU on the remote node as a partner LU on the local node. Defining a Partner LU Alias: To define a partner LU alias, you need the following information: v Fully qualified partner LU name (SNA network name and LU name) v Partner LU alias used by a local TP To add a partner LU alias, perform the following steps from the Node window: 1. Select the Remote Systems pane of the window. 2. Select APPC, New partner LUs, and Partner LU alias from the Services menu (or click on the New button in the button bar, and select Define partner LU alias). CS/AIX displays the Partner LU Alias Configuration dialog. 3. Enter the partner LU name and alias on the dialog. 4. Click on the OK button to define the partner LU alias. The partner LU alias appears in the Remote Systems pane of the Node window (as part of the Network definition). Defining a Partner LU on a Remote Node: To define a partner LU on a specific remote node, you need the following information:
89

v Fully qualified partner LU name. v Partner LU alias (if an alias is used by a local TP). v Fully qualified name of the node that contains directory information for the partner LU. v If the partner LU is located on a TCP/IP network, preferred routing method (APPN or AnyNet). To add a partner LU definition for a specific remote node, perform the following steps from the Node window: 1. Select the remote node. 2. Select APPC, New partner LUs, and Partner LU on remote node from the Services menu (or click on the New button in the button bar, and select Define partner LU on remote node). CS/AIX displays the Partner LU Configuration dialog. 3. Enter the appropriate values in the fields on the dialog. 4. Click on the OK button to define the partner LU. The partner LU alias appears in the Remote Systems pane of the Node window, under the remote system to which it belongs. Defining Multiple Partner LUs Using Wildcards: You can use wildcards to configure the location for a set of partner LUs that are all located on the same remote node and whose names start with the same characters. Using wildcards means that you do not need to configure each partner LU individually. When you define partner LUs using wildcards, you must supply the following information: v Wildcard partner LU name. The wildcard partner LU name consists of two type A EBCDIC strings, each of 18 characters, that match the fully qualified LU names of multiple partner LUs. The first string can be a complete SNA network name that matches the network name for the partner LUs exactly, or a wildcard prefix that matches the beginning of the network name. If you enter a wildcard prefix for the network name, leave the second string blank. If you supply a complete SNA network name for the first string, you can also enter a value for the second string. (You cannot enter the second string unless you supplied a valid SNA network name for the first string.) The second string is treated as a wildcard prefix, which must match the start of the second part of the fully qualified partner LU names. v Name of the node where the partner LUs are located. To add multiple partner LUs, perform the following steps from the Node window: 1. Select the remote node for which you are defining the partner LUs. 2. Select APPC, New partner LUs, and Wildcard partner LUs on remote node from the Services menu (or click on the New button in the button bar, and select Define wildcard partner LUs on remote node). CS/AIX displays the Wildcard Partner LU Configuration dialog. 3. Enter the appropriate information in the fields on the dialog. 4. Click on the OK button to define the partner LUs. The partner LUs appear in the Remote Systems pane of the Node window, under the remote node to which they belong.
90
Configuring Dependent APPC

To configure a dependent LU 6.2, you need the following information: v Local LU name. v Local LU alias (if an alias is used in a TP that this LU supports). v Name of the link station that provides the connection to the host. v LU number. v Whether the LU should be assigned to the default pool for dependent LU 6.2. If you are configuring dependent LUs of type 6.2 for use with APPC or CPI-C applications, you may wish to define them as members of the default pool. An application that does not specify a particular local LU is assigned an unused LU from the pool of LUs defined as default LUs. To configure a dependent local LU, perform the following steps from the Node window: 1. Select a link station in the Connectivity pane of the window. 2. Select New dependent local LU from the APPC submenu on the Services menu (or click on the New button in the button bar, and select New dependent local LU). CS/AIX displays the Local LU dialog. 3. Enter appropriate values in the fields on the dialog. 4. Click on the OK button to define the local LU. The dependent LU appears in the Connectivity pane, below the link station to which it belongs.
Configuring for CPI Communications

If you are supporting a CPI-C application that uses CPI-C symbolic destination names, you need to define the CPI-C side information. The side information associates the symbolic destination name with information about the partner TP, partner LU, mode, and security for the conversation. To determine the symbolic destination name for CPI-C, consult the application developer (or for a third-party application, consult the product documentation). Before configuring CPI-C side information, you need the following information: v Symbolic destination name used by the TP v Partner TP name v Partner LU name or alias v Mode name To configure CPI-C side information, perform the following steps from the Node window: 1. Select CPI-C from the APPC sub-menu in the Services menu. CS/AIX displays the CPI-C Destination Names window. 2. Click on the New button. CS/AIX displays the CPI-C Destination Configuration dialog. 3. Enter appropriate values in the fields on the dialog. 4. Click on the OK button to define the CPI-C side information.
91
Configuring LUA
Configuring LUA
The LUA API can be used for applications that use LU types 03 to communicate with a host computer. (For detailed information about the LUA API, refer to IBM Communications Server for AIX or Linux LUA Programmers Guide.) Before configuring LUA, perform the following configuration: 1. Configure the node as described in Configuring the Node on page 79. 2. Configure connectivity for dependent traffic as described in Configuring Connectivity on page 80. (If you are using upstream SNA gateway or DLUR, configure the link to the upstream node instead of a direct link to the host.) To configure LUA, you need the following information: v LU name or LU pool name. v LU number for each LU. The LU number must match the LU number configured on the host. To configure LUA, define the LU using the following procedure: 1. Select the link station to the host in the Connectivity pane of the Node window. 2. Click on the New button. 3. On the resulting dialog, select New LU for LUA. 4. Enter appropriate values in the fields on the dialog. Specify an LU type of Unrestricted. 5. Click on the OK button. The LU appears in the Connectivity pane of the Node window, beneath the link station to the host. 6. If you are going to use any LU pools, define them as described in Defining an LU Pool on page 85.
Configuring SNA Gateway

In addition to providing direct access to a host computer, CS/AIX can provide SNA gateway facilities. This feature enables other computers to access a host computer through a CS/AIX node, instead of requiring a separate connection to the host from each computer. The SNA gateway feature is shown in Figure 8 on page 93.
92
Host
SNA Node Providing SNA Gateway
Downstream Computers
Figure 8. SNA Gateway
The downstream computer must contain an SNA PU type 2.0 or 2.1 to support dependent LUs. For example, the downstream computer could be another CS/AIX computer or a PC running Communications Server for Windows. When the local CS/AIX node uses the SNA gateway feature, all the data transferred between the host and the downstream computer is routed through the local node. This enables a downstream computer to share a host connection with CS/AIX or with other downstream computers, instead of requiring a direct link. For example, you could set up several downstream computers connected to CS/AIX over a local token ring network, so that they could all access the same long-distance leased line from CS/AIX to the host. Using SNA gateway also simplifies the configuration at the host, because you do not need to define the downstream computers and the communication links to them. The host configuration needs to include only the CS/AIX computer and its host communication link; the LUs at the downstream computers are configured as part of the resources of the CS/AIX computer. The host computer is not aware that SNA gateway is being used. Before configuring SNA gateway, you must perform the following configuration tasks: v Define the local node as described in Configuring the Node on page 79. v Configure a port and link station for dependent traffic between the local node and the host, as described in Configuring Connectivity on page 80. Also, configure ports and link stations for dependent traffic between the local node and the downstream nodes. If you need to support downstream LUs that are not defined in advance, you can define a template on the port to support implicit PUs and downstream LUs (see Supporting Implicit Downstream LUs on page 94). v Define the LUs on the local node that are used for communication with the host (upstream LUs). Define the upstream LUs as LU type 03 with an LU type of Unrestricted (unknown). (The LUs on downstream nodes can be any LU type.)
93

v If you are going to use any LU pools, define them as described in Defining an LU Pool on page 85.
Supporting Implicit Downstream LUs

To support downstream LUs that are not predefined to CS/AIX, you can define a template on the port for implicit downstream PUs and LUs (for basic port configuration, see Configuring Connectivity on page 80). These templates provide support for downstream LUs without requiring that you configure an LU on the local node to support every LU on a downstream node. Before configuring a downstream LU for SNA gateway, you need the following information: v Range of LU numbers to support downstream LUs. v Host LU name. To define a template for implicit downstream LUs, perform the following steps: 1. If you have already configured the port, double-click on the port definition in the Connectivity pane of the Node window. CS/AIX displays the port configuration dialog. If you have not already configured the port, do so now: a. Select the Connectivity pane on the Node window. b. Click on the New button. c. On the resulting dialog, choose to define a port and select the link protocol type. CS/AIX displays the port configuration dialog. d. Enter the basic port parameters as described in Configuring Connectivity on page 80. 2. Click on the Advanced button at the bottom of the dialog. CS/AIX displays the Port Parameters dialog. The lower pane shows settings that affect downstream LU templates. 3. Select the Configure downstream LUs for implicit PU access option. 4. Click on OK. CS/AIX displays the Downstream LU Template Configuration dialog. 5. Enter appropriate values in the fields on the dialog. 6. Click on OK to define the implicit downstream LU template.
Defining Downstream LUs

Before configuring a downstream LU for SNA gateway, you need the following information: v LU name for each downstream LU. (This is a local identifier, and does not have to match the configuration of the downstream system.) v LU number for each downstream LU. v Link station to the downstream node. v Upstream LU name (for the host LU). To configure a downstream LU for SNA gateway, perform the following steps: 1. Select the link station to the downstream node in the Connectivity pane of the Node window. 2. Click on the New button.
94

3. Select New downstream LU and click on OK. CS/AIX displays the Downstream LU dialog. 4. Enter appropriate values in the fields on the dialog. 5. Click on OK to define the downstream LU. The LU definition appears in the Connectivity pane of the Node window, below the link station to the downstream node.
Configuring DLUR
In addition to providing direct access to a host computer, CS/AIX can provide dependent LU requester (DLUR) facilities. This feature enables sessions for dependent LUs to span multiple nodes in an APPN network, instead of requiring a direct connection to the host. Normally, a dependent LU session requires a direct communications link to the host computer. If many nodes (including a host node) are connected together in an APPN network, some of them may not have a direct connection to the host, but only an indirect connection through another node. It is not possible to establish dependent LU sessions to the host from LUs in these indirectly connected nodes. Dependent LU requester (DLUR) is an APPN feature designed to overcome this limitation. DLUR on an APPN node (such as a CS/AIX node) works in conjunction with dependent LU server (DLUS) at the host, to route sessions from dependent LUs on the DLUR node across the APPN network to the DLUS host. The route to the host can span multiple nodes and can take advantage of APPNs network management, dynamic resource location, and route calculation facilities. DLUR must be available on the node where the LUs are located, and DLUS must be available on the host node, but DLUR is not required on any intermediate nodes in the session route. If the CS/AIX DLUR node is a network node or a Branch Network Node, it can also provide passthrough DLUR facilities for dependent LUs on downstream computers connected to the CS/AIX node. These LUs can use DLUR on the CS/AIX node to access the host across the network, in the same way as for LUs internal to the node. The downstream computers do not run DLUR, and indeed do not need to be aware that DLUR is being used. Figure 9 on page 96 shows a CS/AIX server configured as an APPN network node, implementing passthrough DLUR to support sessions between LUs on the host (the upstream node) and LUs on the nodes in the APPN network (downstream nodes).
95
Configuring DLUR
Host
SNA Node Providing Passthrough DLUR
SNA Node with Dependent LUs
SNA Node with Dependent LUs
Figure 9. CS/AIX Node Providing DLUR
Note: 1. You cannot configure DLUR on a LEN node. 2. You can configure passthrough DLUR only on a network node or a Branch Network Node. 3. If you are using Branch Extender, you cannot configure DLUR on an end node in the branch (with a Branch Network Node as its network node server). However, you can support dependent LU applications from this node by configuring passthrough DLUR on the Branch Network Node (so that the end node in the branch does not run DLUR, but uses passthrough DLUR on the Branch Network Node). The tasks you need to perform to configure DLUR depend on whether the dependent LUs are on the local node or on downstream nodes.
Configuring DLUR Support on the Local Node

You need the following information for this task: v PU ID for the PU on the local node. v PU name. (This is a local identifier, and does not have to match the host configuration.) v Name of the DLUS on the host (and the name of the backup DLUS if there is one). v LU name, LU number, and LU type for each downstream LU. The LU number must match the number configured on the host. To configure DLUR support on the local node, you must perform the following configuration tasks: 1. Define the local node as described in Configuring the Node on page 79. If you are providing passthrough DLUR support for downstream nodes, define the node as an APPN network node or branch network node.
96
Configuring DLUR
2. Configure connectivity to the APPN network. APPN connectivity requires at least a port and link station for independent traffic between the local node and the adjacent APPN network node, as described in Configuring Connectivity on page 80. 3. Define a DLUR PU on the local node (the DLUR PU supports connectivity to the host). To configure the DLUR PU, perform the following steps from the Node window: a. Select the Services menu, then the Connectivity submenu, then New DLUR PU (or click on the New button in the button bar, then select DLUR PU). When you click on the OK button, CS/AIX displays the DLUR PU Configuration dialog. b. Enter appropriate values in the fields on the dialog. c. Click on the OK button to define the DLUR PU. The DLUR PU appears in the Connectivity pane below the DLUR item. 4. To configure DLUR to support LUs on the local node, you must add the LUs on the local node. The LUs must be configured to support LUA, as described in Configuring LUA on page 92. Depending on the requirements of the user applications supported by the LUs, you may also need to perform further configuration.
Configuring Passthrough DLUR Support for Downstream Nodes

You need the following information for this task: v Downstream PU name for each downstream node, or for each PU on the downstream node. (This is a local identifier, and does not have to match the host configuration.) v Name of the DLUS on the host. To configure passthrough DLUR support for downstream nodes, you must perform the following configuration tasks: 1. Define the local node as an APPN network node (see Configuring the Node on page 79). 2. Configure connectivity to the downstream nodes. Configure ports and link stations for dependent traffic between the local node and each downstream node, as described in Configuring Connectivity on page 80. (You do not need to define a DLUR PU to support passthrough DLUR for downstream nodes.) 3. A downstream node can support multiple PUs. In this case, each downstream PU is associated with a different link, so you need to configure multiple links between the CS/AIX DLUR node and the downstream node, and you need to know the downstream PU name for each link.
Configuring TN Server
3270 emulation programs that communicate over TCP/IP (rather than over an SNA network) are referred to as TN3270 programs (Telnet 3270 emulation programs). TN3270 programs can also include support for TN3270E (Telnet 3270 standard extensions). TN3270E is an open protocol that supports 3270 device emulation (including both terminals and printers) using Telnet. It enables a Telnet client to
97
select a particular device (by specifying the LU name), and provides enhanced support for various functions, including the ATTN and SYSREQ keys and SNA response handling. Note: This guide uses the term TN3270 for information that applies equally to the TN3270, TN3287, and TN3270E protocols. CS/AIX TN server provides access to 3270 host computers for TN3270 users on other computers. TN server enables TN3270 users to share a host connection with CS/AIX or with other TN3270 users, instead of requiring a direct link. TN server also enables TN3270 users to access hosts that are not running TCP/IP. A CS/AIX node that provides TN server support for TN3270 clients is shown in Figure 10. The TN server node and the clients communicate through the TCP/IP network.
Host
SNA Node Providing TN Server Support TCP/IP Network
TN3270 Client
TN3270E Client
TN3270E Client
Figure 10. CS/AIX Node Configured for TN Server
The CS/AIX TN server feature provides an association between a TN3270 user and CS/AIX 3270 LU. All data from the TN3270 user is routed to the LU. This means that the configuration for both the host and the TN3270 user is as though they were connected directly; neither needs to be aware that data is being routed through TN server. CS/AIX TN server supports all TN3270 client emulation programs that correctly implement the protocols defined in IETF RFCs 1123, 1576, 1646, 1647, and 2355. When a TN3270 program communicates with TN server, CS/AIX identifies the program by the TCP/IP address of the computer where the TN3270 program is running. CS/AIX cannot distinguish between two different TN3270 programs being used by different users on the same computer. In the CS/AIX manuals, the term TN server user refers to the computer where a TN3270 program is running, not to an individual user of that program.
98
As shown in Figure 11, the host and the TN server user view the TN server configuration differently.
TN Server Configuration Host Host View of the Configuration Host TN3270 Program View of the Configuration
SNA Node Running TN Server
SNA Node
Host
TCP/IP Network
TCP/IP Network
SNA Nodes Running 3270 Emulators
Figure 11. TN Server
Each TN server user connecting to CS/AIX using the TN3270 Server feature is normally configured to access a single 3270 LU, and so is restricted to one host session at a time. However, you can also configure a TN server user to access a pool of 3270 LUs, instead of having a single dedicated 3270 LU for each user. This enables users to access as many sessions as there are available LUs in the pool. Before you can configure TN server access, you must perform the following configuration tasks: v Define the local node as described in Configuring the Node on page 79. v Configure a port and link station for dependent traffic between the local node and the host, as described in Configuring Connectivity on page 80. To configure TN server access, you must perform the following configuration tasks: v Define the 3270 LUs on the local node that are used for communication with the host. To add the LUs, see Defining 3270 LUs. v If you are going to use any LU pools, define them as described in Defining an LU Pool on page 100.
Defining 3270 LUs

Before configuring the 3270 LU, gather the following information: v LU name. (This is a local identifier, and does not have to match the host configuration.) v LU number (or numbers for a range of LUs). v LU type (3270 display model or 3270 printer). v Pool name (if you are adding the LU to a pool). To configure an LU of types 03 for a previously defined link station, perform the following steps from the Node window:
99
1. Select the link station to the host in the Connectivity pane of the window. 2. Click on the New button. 3. Select the LU type (New 3270 display LU or New 3270 printer LU) on the resulting dialog. When you select this item and click on OK, CS/AIX displays the LU Type 03 dialog. 4. Enter appropriate values in the fields on the dialog. 5. Click on OK to define the LU. The LU appears in the Connectivity pane of the Node window, below the link station to the host.
Defining an LU Pool
For 3270, you can define LU pools to simplify user configuration and provide greater flexibility in establishing host sessions. For example, you can define several 3270 LUs in a single LU pool, then configure multiple TN3270 clients using this LU pool. This makes configuring the 3270 sessions easier and enables any client to use any LU in the pool. Note: You can assign a TN3270 client either to a specific LU or to an LU pool. v If you assign the client to a specific LU that is in a pool, the client uses this LU if it is available; otherwise it uses any free LU from the pool, as though you had assigned it to the LU pool instead of the specific LU. v If you want the client to use only a specified LU, so that the clients session cannot be established if the LU is already in use, ensure that the LU is not in a pool. You can view the LU pools for the local CS/AIX node using the LU Pools window. This window lists the LU pools configured on the local system, and enables you to select LUs to add to an LU pool. You can add the following LU types to a pool for use by 3270 (do not mix LUs of different types in the same pool): v 3270 display LU v Unrestricted LU Before you can add LUs to a pool, the LUs must be defined on the local node. To configure an LU pool, perform the following steps from the Node window: 1. Select LU Pools from the Windows menu. CS/AIX displays the LU Pools window. 2. Click on the New button. CS/AIX displays the LU Pool Configuration dialog. The box on the right lists LUs that are not yet allocated to any pool. Any of these LUs can be included in the new pool. 3. Select the LU or LUs you wish to add to the pool, and click on the New button to move the selected LUs to the box on the left. To remove an LU from the box on the left, select it and click on the Remove button. 4. Click on OK to define the LU pool. All of the LUs in the box on the left are added to the LU pool.
100
The pool appears in the LU Pools window.
Configuring TN3270 Server

Before configuring TN3270 server, you need the following information: v Whether the server supports only TN3270, or also TN3270E (which includes TN3270 support). v Whether a TN3270E client can request a specific LU. v Display and printer LU names (or LU pool names) for each client. (Printer LU names are needed only if you are supporting TN3270E.) v If only certain clients are permitted, or if you want to restrict certain clients to specific LUs, you need the TCP/IP name or address of the client. v TCP/IP port number on the TN server node. v Whether SSL data encryption, client authentication, and server authentication are required (this option is available only if you have installed the additional software required to support it). v Whether the TN3270 Server is operating in an SLP network. To associate a display LU and printer LU, you also need the names of those LUs. A TN server association record defines an association between a printer LU and display LU, so that the TN3270E protocol can connect the two. You do not need to define an association record if you are not supporting TN3270E or if you are not supporting printer LUs. The TN server defaults record defines parameters that are used on all TN3270 client sessions. You can define a single defaults record for each server. To configure TN3270 server, perform the following steps from the Node window: 1. Define a TN server access record: a. Select TN Server from the Services menu. CS/AIX displays the TN Server window, which lists all the configured TN server access records in the upper pane and TN server association records in the lower pane. b. Select the pane that contains TN3270 Server access records and click on the New button. CS/AIX displays the TN Server Access dialog. c. Enter appropriate values in the fields on the dialog. d. Click on OK to define the TN server access record. The record appears in the TN Server window. 2. Define a TN server association record: a. Select the pane that contains association records in the TN Server window and click on the New button. CS/AIX displays the TN Server Association Record dialog. b. Enter appropriate values in the fields on the dialog. c. Click on OK to define the TN server association record. The record appears in the TN Server window. 3. If you need to force printer responses, specify a keep-alive method for all TN3270 sessions, specify how to access the external LDAP server that holds a revocation list used to check authorization for TN3270 clients, or use TN3270 SLP (Service Location Protocol), use the TN Server Advanced Parameters dialog to do this.
101
For more information about configuring SSL support for TN Server, refer to the IBM Communications Server Support web pages at http://www.ibm.com/ software/network/commserver/support/.
Configuring TN Redirector
The CS/AIX TN Redirector feature provides passthrough TCP/IP host access to TN3270, TN3270E, TN5250 and VT clients, referred to collectively as Telnet clients. The Telnet user communicates with CS/AIX over a TCP/IP connection; CS/AIX then communicates with the host over another TCP/IP connection. This allows you to use Secure Sockets Layer (SSL) security checking where necessary, and not on the complete user-to-host connection. For example: v If clients are connecting to CS/AIX over a TCP/IP LAN where checking is not required, but are connecting to a remote host that requires SSL, you can use SSL over the TCP/IP connection between CS/AIX and the host. This means that security is checked once for all clients, and individual clients do not have to provide security information. v If CS/AIX is installed on the same site as the host, but clients are connecting in from external sites, you can use SSL over the client connections to CS/AIX without having to install SSL software on the host.
Before you can configure TN Redirector access, you must define the local node as described in Configuring the Node on page 79. You also need the following information: v If only certain clients are permitted, you need the TCP/IP name or address of the client. v TCP/IP port number used by the client to connect to the TN Redirector node. v TCP/IP name or address of the host. v TCP/IP port number used by the TN Redirector node to connect to the host. v Whether SSL data encryption, client authentication, and server authentication are required between the client and the TN Redirector node (this option is available only if you have installed the additional software required to support it). v Whether SSL data encryption is required between the TN Redirector node and the host. The TN redirector defaults record defines parameters that are used on all TN redirector client sessions. You can define a single defaults record for each client TCP/IP port number. To configure TN redirector, perform the following steps from the Node window to define a TN redirector access record: 1. Select TN Server from the Services menu. CS/AIX displays the TN Server window, which lists all the configured TN3270 server access records, TN3270 server association records, and TN Redirector access records. 2. Select the pane that contains TN Redirector access records and click on the New button. CS/AIX displays the TN Redirector Access dialog. 3. Enter appropriate values in the fields on the dialog. 4. Click on OK to define the TN Redirector access record. The record appears in the TN Redirector pane of the TN Server window.
102
Note: The SNA node must be active in order to use TN Redirector, although it does not use any of the nodes SNA resources.
Configuring AnyNet
CS/AIX includes the AnyNet APPC over TCP/IP function, which supports protocol conversion and communication between applications across a non-native network. The AnyNet APPC over TCP/IP access node function enables LU 6.2 (APPC) applications to communicate across a TCP/IP network, and the APPC over TCP/IP gateway function enables APPC applications to communicate over a network that is part TCP/IP and part SNA. AnyNet APPC over TCP/IP will run only in TCP/IP networks that support IPv4. For more information about APPC over TCP/IP, refer to IBM Communications Server for AIX AnyNet Guide to APPC over TCP/IP. Note: The AnyNet APPC over TCP/IP function does not support IPv6 addressing and is available only on 32bit systems (not on 64bit systems). It will not be supported in future releases. An APPC over TCP/IP access node is shown in Figure 12.
APPC Application
TCP/IP
APPC Application
APPC over TCP/IP
APPC over TCP/IP
Figure 12. AnyNet APPC over TCP/IP Access Node
An APPC over TCP/IP gateway is shown in Figure 13.
APPC Application
SNA
TCP/IP
APPC Application
APPC over TCP/IP Gateway Node
APPC over TCP/IP Access Node
Figure 13. AnyNet APPC over TCP/IP Gateway
Configuring APPC over TCP/IP

Before you can configure APPC over TCP/IP, you must perform the following configuration: 1. Configure the node as described in Configuring the Node on page 79. If you are configuring an APPC over TCP/IP access node, the node can be an APPN network node, end node, or LEN node. If you are configuring an APPC over TCP/IP gateway, the local node must be a network node. 2. If you are configuring an APPC over TCP/IP gateway, configure connectivity to the SNA network as described in Configuring Connectivity on page 80. (This step is not required for a APPC over TCP/IP access node.)
103
Configuring AnyNet
Before you configure APPC over TCP/IP, collect the following information: v Whether the local system will act as an APPC over TCP/IP access node or as a gateway. If the local system is connected both to an SNA network and to a TCP/IP network, it can be configured as a gateway to enable nodes in the two networks to communicate. v Domain name for the TCP/IP network. An LU name of the form NETWORKNAME.LUNAME is converted to a TCP/IP address of the form LUNAME.NETWORK.DOMAIN. The domain name is configured in an /etc/hosts or DNS entry on the local system. v Default routing preference used to search for LUs (only the SNA network, only the TCP/IP network, or both). v If the default routing preference does not include a search of the TCP/IP network, you need a list of the partner LUs to be located through the TCP/IP network. Partner LUs located through the TCP/IP network can be access nodes in a TCP/IP network, or LUs in an SNA network that is connected to the TCP/IP network by an APPC over TCP/IP gateway. v IP addresses for each LU to be located through the TCP/IP network. This information is configured in the /etc/hosts file or on the DNS server. To configure APPC over TCP/IP, use the following procedure: 1. Configure APPC over TCP/IP defaults: a. Select the AnyNet option from the Services menu on the Node window, and the AnyNet option on the AnyNet submenu. CS/AIX displays the AnyNet window. b. Select APPC over TCP/IP parameters option from the Selection menu CS/AIX displays the AnyNet APPC over TCP/IP Parameters dialog. c. Enter appropriate values in the fields on the dialog. d. Click on the OK button. The APPC over TCP/IP defaults definition appears in the APPC over TCP/IP Sessions pane of the AnyNet window. 2. If you have not defined a default routing preference that includes the TCP/IP network, you must configure each partner LU that is located through the TCP/IP network: a. Select the Remote Systems pane of the Node window and click on the New button. b. On the resulting dialog, select Partner LU on remote node and click on the OK button. c. Enter the fully qualified name for the partner LU, and select an AnyNet routing option that includes the TCP/IP network. d. Click on the OK button. The partner LU definition appears in the Remote Systems pane of the Node window. 3. Configure TCP/IP addresses for partner LUs. You can add an entry of the following form to the /etc/hosts file on the local system or to the DNS server for the TCP/IP network: dotted_decimal_address LUNAME.NETWORKNAME.DOMAINNAME For a partner LU located on an APPC over TCP/IP access node in the TCP/IP network, use the IP address of the access node. For a partner LU located in an SNA network and connected to the TCP/IP network by an APPC over TCP/IP gateway, use the IP address of the APPC over TCP/IP gateway.
104
Disabling CS/AIX
Disabling CS/AIX
Disabling the CS/AIX software automatically stops the CS/AIX node and its associated connectivity components. Disabling CS/AIX also stops any other processes (such as a 3270 emulation program) from using CS/AIX resources on this server. In general, you should stop individual services as users finish using them, and only disable the system when there is no CS/AIX activity. If you need to disable CS/AIX while users are active, warn users that CS/AIX is stopping, and give them time to finish their activities before you disable the software. If a 3270 emulation program is using LUs on the node when you disable the CS/AIX software, all 3270 emulation sessions using these LUs end. The program continues to run, but the user cannot use the sessions until the software is re-enabled. Applications using the APPC, CSV, LUA, NOF, or MS APIs are notified by a COMM_SUBSYSTEM_ABENDED return code and CPI-C applications by a CM_PRODUCT_SPECIFIC_ERROR return code. To disable the CS/AIX software, enter the following command at the AIX command prompt: sna stop If CS/AIX is disabled successfully, sna stop returns an exit code of 0. Any other exit code indicates that an error occurred and that the CS/AIX software was not disabled. Refer to IBM Communications Server for AIX Diagnostics Guide for more information about exit code values.
105
106
Chapter 9. Information Resources for CS/AIX and SNA

This chapter describes the resources in the SNA library that provide information about SNA technology and the many networking products and services that IBM offers. It also describes information that is available in network forums.
SNA Library
The SNA library includes marketing brochures, books, user guides, and tutorials that provide both introductory and in-depth information about the following topics: v v v v v v v SNA theory SNA products Product implementation Configuration of systems and networks SNA application programs and APIs Overall planning, performance, and tuning Problem diagnosis
v Network management v Network security All IBM publications can be ordered through your IBM representative, the IBM branch serving your locality, or by calling IBM directly at 1-800-879-2755. For a list of publications most relevant to CS/AIX, see the Bibliography at the end of this book. For information about additional publications, contact your IBM representative.
Network-Accessible Information
To promote information exchange, IBM sponsors electronic forums and bulletin boards. It posts home pages on the Internet and provides online documentation that is also accessible on CompuServe and the World Wide Web. Product Support over IBMLink The IBMLink forum is held over IBM-owned networks. It is designed to help customers with licensed IBM products solve technical problems and other issues related to their system and network. IBM personnel answer questions and mediate online discussions among IBM customers. For more information about IBMLink, use http://www.ibmlink.ibm.com. Information in IBM Home Pages On the Internet, various IBM home pages provide access to forums. For comprehensive help, the IBM main home page can be used to navigate to information centers on the Internet and the World Wide Web. The main home page can be accessed by using http://www.ibm.com. You can access information about IBM networking software, including CS/AIX, by using http://www.ibm.com/software/network. Information about CS/AIX is at http://www.ibm.com/software/network/commserver.
107
Network-Accessible Information
For more detailed information about support for CS/AIX, use http://www.ibm.com/software/network/commserver/support. Information for Downloading On the World Wide Web, users can download Redbook publications by using http://www.redbooks.ibm.com. Broad access to other helpful information (such as program code) is available through APPC Online on the CompuServe network (use GO APPC). Information on IBM software can be accessed at http://www.ibm.com/ software, where you can link to pages about CS/AIX and all of the IBM Software Servers. Trial Software In some countries, IBM offers trial SNA software free of charge for 90 days, including the latest version of CS/AIX. For details on how to obtain trial copies, contact your local IBM representative or see the CS/AIX page on the World Wide Web, at http://www.ibm.com/software/network/ commserver/downloads.
Suggested Reading
For those who want to strengthen their understanding of SNA, the following books cover SNA theory and the use of CS/AIX in practice. The books are helpful to both novices and experts who might need either a starting point for getting acquainted with SNA or an in-depth treatment of the subject. v v v v Systems Network Architecture: Technical Overview (GC303073) IBM Communications Server for AIX Administration Guide (SC318586) IBM Communications Server for AIX Version 6 (SG24-5947) IBM CS/AIX Understanding and Migrating to Version 5: Part 1 - Configuration and New Features (SG24-5215) v IBM CS/AIX Understanding and Migrating to Version 5: Part 2 - Performance (SG24-2136) v Multiprotocol Transport Networking Architecture: Technical Overview (GC317073) If you have more specific interests, see the Bibliography for other references, or contact your local IBM representative.
108
Appendix. Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the users responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
109
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation P.O. Box 12195 3039 Cornwallis Road Research Triangle Park, NC 27709-2195 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to IBMs application programming interfaces. Each copy or any portion of these sample programs or any derivative work must include a copyright notice as follows: (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. Copyright IBM Corp. 2000, 2005, 2006, 2007, 2008, 2009. All rights reserved.
110
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at Copyright and trademark information at www.ibm.com/legal/copytrade.shtml. Adobe is a registered trademark of Adobe Systems Incorporated in the United States, and/or other countries. Intel and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, or service names may be trademarks or service marks of others.
Appendix. Notices
111
112
Bibliography
The following IBM publications provide information about the topics discussed in this library. The publications are divided into the following broad topic areas: v CS/AIX, V6.4 v Redbooks v AIXoperating system v Systems Network Architecture (SNA) v Host configuration v v v v v v z/OS Communications Server Transmission Control Protocol/Internet Protocol (TCP/IP) X.25 Advanced Program-to-Program Communication (APPC) Programming Other IBM networking topics
For books in the CS/AIX library, brief descriptions are provided. For other books, only the titles and order numbers are shown here.
CS/AIX V6.4 Publications

The CS/AIX library comprises the following books. In addition, softcopy versions of these documents are provided on the CD-ROM. See IBM Communications Server for AIX Quick Beginnings for information about accessing the softcopy files on the CD-ROM. To install these softcopy books on your system, you require 915 MB of hard disk space (depending on which national language versions you install). v IBM Communications Server for AIX Migration Guide (SC31-8585) This book explains how to migrate from Communications Server for AIX Version 4 Release 2 or earlier to CS/AIX Version 6. v IBM Communications Server for AIX Quick Beginnings (GC31-8583) This book is a general introduction to CS/AIX, including information about supported network characteristics, installation, configuration, and operation. v IBM Communications Server for AIX Administration Guide (SC31-8586) This book provides an SNA and CS/AIX overview and information about CS/AIX configuration and operation. v IBM Communications Server for AIX Administration Command Reference (SC31-8587) This book provides information about SNA and CS/AIX commands. v IBM Communications Server for AIX or Linux CPI-C Programmers Guide (SC23-8591) This book provides information for experienced C or Javaprogrammers about writing SNA transaction programs using the CS/AIX CPI Communications API. v IBM Communications Server for AIX or Linux APPC Programmers Guide (SC23-8592) This book contains the information you need to write application programs using Advanced Program-to-Program Communication (APPC). v IBM Communications Server for AIX or Linux LUA Programmers Guide (SC23-8590)
113
v v
This book contains the information you need to write applications using the Conventional LU Application Programming Interface (LUA). IBM Communications Server for AIX or Linux CSV Programmers Guide (SC23-8589) This book contains the information you need to write application programs using the Common Service Verbs (CSV) application program interface (API). IBM Communications Server for AIX or Linux MS Programmers Guide (SC23-8596) This book contains the information you need to write applications using the Management Services (MS) API. IBM Communications Server for AIX NOF Programmers Guide (SC31-8595) This book contains the information you need to write applications using the Node Operator Facility (NOF) API. IBM Communications Server for AIX Diagnostics Guide (SC31-8588) This book provides information about SNA network problem resolution. IBM Communications Server for AIX or Linux APPC Application Suite Users Guide (SC23-8595) This book provides information about APPC applications used with CS/AIX.
v IBM Communications Server for AIX Glossary (GC31-8589) This book provides a comprehensive list of terms and definitions used throughout the CS/AIX library.
IBM Redbooks
IBM maintains an International Technical Support Center that produces publications known as Redbooks. Similar to product documentation, Redbooks cover theoretical and practical aspects of SNA technology. However, they do not include the information that is supplied with purchased networking products. The following books contain information that may be useful for CS/AIX: v IBM Communications Server for AIX Version 6 (SG24-5947) v IBM CS/AIX Understanding and Migrating to Version 5: Part 2 - Performance (SG24-2136) v Load Balancing for Communications Servers (SG24-5305) On the World Wide Web, users can download Redbook publications by using http://www.redbooks.ibm.com.
AIX Operating System Publications

The following books contain information about the AIX operating system: v AIX Version 5.3 System Management Guide: Operating System and Devices (SC23-4910) v AIX Version 5.3 System Management Concepts: Operating System and Devices (SC23-4908) v AIX Version 5.3 System Management Guide: Communications and Networks (SC23-4909) v AIX Version 5.3 Performance Management Guide (SC23-4905) v AIX Version 5.3 Performance Tools Guide and Reference (SC23-4906) v Performance Toolbox Version 2 and 3 Guide and Reference (SC23-2625) v AIX Version 5.3 Communications Programming Concepts (SC23-4894) v AIX Version 5.3 Installation Guide and Reference (SC23-4887)
114
v AIXlink/X.25 Version 2.1 for AIX: Guide and Reference (SC23-2520)
Systems Network Architecture (SNA) Publications

The following books contain information about SNA networks: v Systems Network Architecture: Format and Protocol Reference ManualArchitecture Logic for LU Type 6.2 (SC30-3269) v Systems Network Architecture: Formats (GA27-3136) v Systems Network Architecture: Guide to SNA Publications (GC30-3438) v Systems Network Architecture: Network Product Formats (LY43-0081) v Systems Network Architecture: Technical Overview (GC30-3073) Systems Network Architecture: Systems Network Architecture: Systems Network Architecture: Systems Network Architecture: Type 6.2 (GC30-3084) v Systems Network Architecture: v v v v APPN Architecture Reference (SC30-3422) Sessions between Logical Units (GC20-1868) LU 6.2 ReferencePeer Protocols (SC31-6808) Transaction Programmers Reference Manual for LU 3270 Datastream Programmers Reference (GA23-0059)
v Networking Blueprint Executive Overview (GC31-7057) v Systems Network Architecture: Management Services Reference (SC30-3346)
Host Configuration Publications

The following books contain information about host configuration: v ES/9000, ES/3090 IOCP Users Guide Volume A04 (GC38-0097) v 3174 Establishment Controller Installation Guide (GG24-3061) v 3270 Information Display System 3174 Establishment Controller: Planning Guide (GA27-3918) v OS/390 Hardware Configuration Definition (HCD) Users Guide (SC28-1848) v ESCON Director Planning (GA23-0364)
z/OS Communications Server Publications

The following books contain information about z/OS Communications Server: v z/OS V1R7 Communications Server: SNA Network Implementation Guide (SC31-8777) v z/OS V1R7 Communications Server: SNA Diagnostics (Vol 1: GC31-6850, Vol 2: GC31-6851) v z/OS V1R6 Communications Server: Resource Definition Reference (SC31-8778)
TCP/IP Publications
The following books contain information about the Transmission Control Protocol/Internet Protocol (TCP/IP) network protocol: v z/OS V1R7 Communications Server: IP Configuration Guide (SC31-8775) v z/OS V1R7 Communications Server: IP Configuration Reference (SC31-8776) v z/VM V5R1 TCP/IP Planning and Customization (SC24-6125)
Bibliography
115
X.25 Publications
The following books contain information about the X.25 network protocol: v AIXLink/X.25 for AIX: Guide and Reference (SC23-2520) v RS/6000 AIXLink/X.25 Cookbook (SG24-4475) v Communications Server for OS/2 Version 4 X.25 Programming (SC31-8150)
APPC Publications
The following books contain information about Advanced Program-to-Program Communication (APPC): v APPC Application Suite V1 Users Guide (SC31-6532) v APPC Application Suite V1 Administration (SC31-6533) v APPC Application Suite V1 Programming (SC31-6534) v APPC Application Suite V1 Online Product Library (SK2T-2680) v APPC Application Suite Licensed Program Specifications (GC31-6535) v z/OS V1R2.0 Communications Server: APPC Application Suite Users Guide (SC31-8809)
Programming Publications
The following books contain information about programming: v Common Programming Interface Communications CPI-C Reference (SC26-4399) v Communications Server for OS/2 Version 4 Application Programming Guide (SC31-8152)
Other IBM Networking Publications

The following books contain information about other topics related to CS/AIX: v SDLC Concepts (GA27-3093) v Local Area Network Concepts and Products: LAN Architecture (SG24-4753) v Local Area Network Concepts and Products: LAN Adapters, Hubs and ATM (SG24-4754) v Local Area Network Concepts and Products: Routers and Gateways (SG24-4755) v Local Area Network Concepts and Products: LAN Operating Systems and Management (SG24-4756) v IBM Network Control Program Resource Definition Guide (SC30-3349)
116
Index Numerics
3270 LU defining 99 for TN Server 10, 98 APPN (continued) routing 13 segmentation of networks subarea functions 2 25 configuration (continued) partner LUs for a LEN node 88 planning 72 port 81 remote node 89 TN redirector defaults 102 TN server association records 101 TN server defaults 101 viewing 77 configuration server 78 adding 78 removing 78 Configuration window, Remote API Client on Windows advanced parameters 64 parameters 62 connection network 13 connection network, configuration 82 connectivity configuration 80 options 2 CPI Communications (CPI-C) 4 CPI-C API 4 configuration 91 interoperability 15 Customer Information Control System (CICS) 5
A
adaptive session-level pacing 14 adding a resource 76 administration program command-line 13 Motif 12, 15 NOF API 13 SMIT 13 Web 12 advanced configurations, memory and storage requirements 22 Advanced Interactive Executive (AIX) 1 advanced program-to-program communication (APPC) 5 AIX hardware requirements for CS/AIX 19 manual pages 30 running CS/AIX on 1 alerts 15 alias, defining for partner LU 89 AnyNet APPC over TCP/IP configuration 103 API CS/AIX types 4 for CS/AIX administration 13 support 3 APPC application suite 6, 8 configuration 86 dependent LU 6.2 91 distributed application support 5 independent LU 6.2 88 Interactive Application Development Toolkit 30 online 108 APPC Application Suite 8 APPC over TCP/IP 103 configuration 103 application programming interface (API) 3 APPN applications for 6, 8 configuration 87 connection network 13 distributed management service 14 DLUR support 2 dynamic configuration 13 end node 1 host support for 2 independent LU support 3 network node 1 node types 1 Copyright IBM Corp. 2000, 2009
B
backup configuration files 39 restoring 40 backup master server 78 backup server 5 base operating system (BOS) 21 BOS (base operating system) 21 Branch Extender 7 Branch Network Node 7 buttons in resource windows 77
C
calls 4 CDE 33 CICS (Customer Information Control System) 5 client 5 client software customizing 67 reinstalling 67 uninstalling 68 upgrading 67 client/server configuration 78 client/server installation 38 client/server support 4 command-line administration program 13 Common Desktop Environment (CDE) 33 Common Programming Interface for Communications (CPI-C) 4 communication adapters 20 compatibility planning 25 component management 75 compression, on LU session data 3 configuration 18 APPC communication 86 APPC over TCP/IP 103 backup 39 connectivity 80 CPI-C side information 91 DLUR 95 downstream LUs for SNA gateway 92 examples 79, 95, 98 files 39, 40 implicit downstream LU 94 LU 6.2 88, 91 LU type 03 84 modifying 77 node 79
D
data link control (DLC) 27 data link control options 2 data stream 4 DATABASE 2 (DB2) 5 DB2 (DATABASE 2) 5 DDDLU (Dynamic definition of dependent LUs) 3 deleting a resource 76 dependent logical unit server (DLUS) dependent LU 6.2 91 dependent LU requester (DLUR) 2 dialog 74 directory for CS/AIX executable programs 73 disabling CS/AIX 105 discussion groups, online 107 disk storage 22 distributed processing application support 5 environment 1 DLC configuration 82, 83 in port configuration 81 installation 31 purpose 27 DLUR configuration 95 description 2 on the local node 96 PU configuration 97
95
117
DLUR (continued) support for downstream nodes 97 DLUS 95 documentation, online 107 domain 4 Domain parameter 62 downstream computer 93 downstream LU configuration 94 for SNA gateway 92 hardware examples 93 downstream node 95 dynamic configuration 13 Dynamic definition of dependent LUs (DDDLU) 3
E
Easy-Install using CDE 33 using SMIT 33 enabling CS/AIX on the local system 73 Enterprise Extender link configuration 83 overview 9 port dialog 83 entry point 14 Ethernet link configuration 82 SAP dialog 83
help Motif administration program 12 Web administration program 12 host in APPN network 2 in subarea network 1 LU support 2 Host Access Class Library files 39 fileset 30 overview 5 HPR compared to ISR 13 HPR/IP 9 HTTPS configuring 36 Remote API Client on AIX 57 Remote API Client on Linux 46 Remote API Client on Linux for System z 52 Remote API Client on Windows 66 requirements 21
L
LAN (local area network) 2 LAN access time-out parameter 64 language environment variable 31, 55 Remote API Client on Linux 44 Remote API Client on Linux for System z 50 LEN node description 1 partner LU configuration 88 remote node identification 82 licensed program 32 Remote API Client on AIX 56 Remote API Client on Linux 45 Remote API Client on Linux for System z 50 licensed program product (LPP) 29 licensing mechanisms 27 link hardware 20 link station defining on port 82 local area network (LAN) 2 local LU, defining 88 local/remote transparency 3 logical unit (LU) 2, 94 low-entry networking (LEN) node 82 LPP (licensed program product) 29 LU configuration 88, 91, 99 downstream 93, 94 naming conventions 26 partner, defining 88 pool 99, 100 support 2 LU pool configuration 85 defining 85 viewing 85 LU type 03 84
I
implicit downstream LU configuration 94 independent LU 6.2 configuration 88 information resources 107 installation details of existing packages 31 maintenance tasks after 37 manual 34, 35 preparation for 30 Remote API Client on AIX 56, 57 Remote API Client on Linux 45 Remote API Client on Linux for System z 50 using Easy-Install 33 installation requirements 20 installing a Remote API Client on AIX 56, 57 installing a Remote API Client on Linux 45 installing a Remote API Client on Linux for System z 50 interface choices 13 intermediate session routing (ISR) 13 International Organization for Standards (ISO) 26 IP address formats 23 IP port dialog 83 IPv4 address 23 IPv6 address 23 ISO (International Organization for Standards) 26 ISR (intermediate session routing) 13
F
features 30 fixed disk storage 22 focal point 14 forums, online 107 functional requirements functions 4
17
G
gateway definition 6 SNA gateway 6 GSKIT Remote API Client Remote API Client Remote API Client System z 49, 52 Remote API Client
M
MAC (medium access control) 82 main memory 22 manager application 15 manual installation 34 manual pages 30 master server 5 Max. broadcast attempts parameter 64 mbufs (memory buffers) 22 MDS-NMVT (Multiple Domain Support-Network Management Vector Transport) 14 medium access control (MAC) 82 memory buffers (mbufs) 22 memory requirements 22 advanced configurations 22 types of storage 22 migrating from previous levels of CS/AIX 32 modifying the configuration 77 Motif administration program description 12 help 12 management capabilities 15 using 71
on AIX 55, 57 on Linux 44, 46 on Linux for on Windows 66
H
hardware link 20 requirements 19 hardware requirements Remote API Client on AIX 55 Remote API Client on Linux 43 Remote API Client on Linux for System z 49 Remote API Client on Windows 59
J
Java Remote API Remote API Remote API System z Client on AIX 55 Client on Linux 44 Client on Linux for 49
118
MPQP (Multiprotocol Quad Port) 20 Multiple Domain Support-Network Management Vector Transport (MDS-NMVT) 14 multiple servers in a domain 5 Multiprotocol Quad Port (MPQP) 20
N
naming conventions 25 network alerts 15 information available through 107 management 14 naming conventions 25 peer-to-peer 1 planning 17, 18, 25 subarea 1 support 1 Network Installation Management 35 NIM (Network Installation Management) 35 node configuration 79 downstream 97 host communication 79 in APPN configuration 80 local 96 remote 88, 89 upstream 95 Node window 75 nodelock licenses 27 NOF API 13
preinstallation tasks 30 Primary RUI 3 primary storage 22 problem data 15 diagnosis tools 15 procedures installing Remote API Client on Windows 61, 64 program temporary fixes (PTFs) 31 PTFs (program temporary fixes) 31 PU (physical unit) 6 PU concentration 92 PU concentrator 6
S
SAA (Systems Application Architecture) 4 SAP (service access point) 20, 82 SDK software Remote API Client on Windows 60 SDLC configuration 81 for dependent traffic 81 Secure Sockets Layer (SSL) client authentication 101, 102 data encryption 38, 101, 102 server authentication 38, 101, 102 security options 14 server 5 adding 78 removing 78 Server Name 62 server, Telnet 9 service access point (SAP) 20, 82 session pacing 14 routing 13 support 3 U-shaped 3 Simple Network Management Protocol-Management Information Base (SNMP-MIB) 14 skill requirements 19 SMIT DLC configuration 27 Easy-Install 33 manual installation 34 SMIT (System Management Interface Tool) 13, 19 SNA library 107 SNA Channel Data Link 30 SNA gateway configuration 92 overview 6 snaadmin program 13 SNMP agent 14 SNMP-MIB (Simple Network Management Protocol-Management Information Base) 14 software features 6 software requirements 21 Remote API Client on AIX 55 Remote API Client on Linux 44 Remote API Client on Linux for System z 49 Remote API Client on Windows 59 start command 74 starting a resource 76 starting CS/AIX automatically at system startup 74 status commands 15 stop command 105 stopping a resource 76 storage requirements 22 subroutines 4 suggested reading 108 synchronous data link control (SDLC) 81 System Management Interface Tool (SMIT) 13, 19, 27 Index
Q
query commands 15
R
RAM (random access memory) 22 random access memory (RAM) 22 rc.sna file 74 Reconnect time-out parameter 64 release information 38 Remote API Client AIX hardware requirements 55 AIX software requirements 55 Linux for System z hardware requirements 49 Linux for System z software requirements 49 Linux hardware requirements 43 Linux software requirements 44 Remote API Client on Linux details of existing packages 44 Remote API Client on Linux for System z details of existing packages 50 Remote API Client on Windows installing 60 installing from the command line 64 installing with the setup program 61 remote node configuration 88, 89 partner LU configuration 89 requirements hardware 19 HTTPS 21 installation 20 memory and storage 22 personnel and skill 19 software 21 WebSphere Application Server 21 resource defining 76 deleting 76 information 107 items 77 management 75 requirements 18 starting 76 stopping 76 response time 23 RISC System/6000 workstations 19
O
online APPC 108 discussion groups 107 documentation 107 forums 107 help 12 Open Systems Interconnection (OSI) 25 OSI (Open Systems Interconnection) 25
P
pacing, session-level 14 paging storage 22 partner applications 5 partner LU alias 89 configuration 88, 89 defining with wildcards 90 on remote node 89 path for CS/AIX executable programs 73 PDF, viewing books 38 peer network 1 peer server 5 personnel requirements 19 physical unit (PU) 6 planning worksheets 72 port configuration 81, 82, 83 post-installation procedures 37
119
Systems Application Architecture (SAA) 4
X
xsnaadmin program 12, 71
T
task sheets 73 TN Redirector access record configuration 102 configuration 102 defaults configuration 102 overview 11 TN server access record configuration 101 association record configuration 101 configuration 97 defaults configuration 101 multiple session support 99 overview 9 user 98 TN3270 programs 9 server 9 TN3270 programs 97 TN3270 user 10, 98 tool bar buttons 77 TP (transaction program) 4 transaction program (TP) 4 transparency, local/remote 3 transport media 20 troubleshooting tools 15
U
U-shaped sessions 3 UDP broadcasts parameter 63 uninstalling a Remote API Client on AIX 58 uninstalling a Remote API Client on Linux 47 uninstalling a Remote API Client on Linux for System z 53 upstream node 95
V
verbs 4 version, IP address 23 viewing the configuration 77
W
WAN (wide area network) 2 Web administration program description 12 help 12 WebSphere Application Server configuring 36 requirements 21 wide area network (WAN) 2 wildcards 90 window 74 worksheets, planning 72 workstation requirements 19
120
Program Number: 5765-E51
Printed in USA
GC31-8583-04

Quick Beggin Ers

Uploaded by

Document Informationclick to expand document information

Copyright:

Available Formats

Quick Beggin Ers

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Quick Beggin Ers

Uploaded by

Copyright:

Available Formats

IBM Communications Server for AIX

IBM Communications Server for AIX

Chapter 1. About IBM Communications Server for AIX . . . . . . . . . . . . 1

Chapter 4. Installing IBM Remote API Clients on Linux . . . . . . . . . . 43

Chapter 5. Installing IBM Remote API Clients on Linux for System z . . . . . 49

Chapter 3. Installing CS/AIX on AIX Servers . . . . . . . . . . . . . . 27

Chapter 6. Installing IBM Remote API Clients on AIX Systems . . . . . . . 55

. 97 . 97 . 99 . 100 . 101 . 102 . 102 . 103 . 103 . 105

Chapter 9. Information Resources for CS/AIX and SNA . . . . . . . . . . 107

Appendix. Notices . . . . . . . . . 109

Chapter 8. Configuring and Using CS/AIX . . . . . . . . . . . . . . . 71

IBM Communications Server for AIX Quick Beginnings

Copyright IBM Corp. 2000, 2009

IBM Communications Server for AIX Quick Beginnings

Copyright IBM Corp. 2000, 2009

IBM Communications Server for AIX Quick Beginnings

Welcome to IBM Communications Server for AIX

How to Use This Book

Plan how to use CS/AIX in your network

Install Remote API Clients on AIX

Copyright IBM Corp. 2000, 2009

How to Use This Book

Abbreviations Used in This Book

IBM Communications Server for AIX Quick Beginnings

How to Use This Book

Functions That Have Been Retired

IBM Communications Server for AIX Quick Beginnings

Where to Find More Information

Where to Find More Information

Welcome to IBM Communications Server for AIX

IBM Communications Server for AIX Quick Beginnings

Chapter 1. About IBM Communications Server for AIX

IBM Communications Server for AIX Features and Packaging

IBM Communications Server for AIX V6.4

Copyright IBM Corp. 2000, 2009

IBM Communications Server for AIX Features and Packaging

IBM Communications Server for AIX Quick Beginnings

IBM Communications Server for AIX Features and Packaging

IBM Communications Server for AIX Features and Packaging

IBM Communications Server for AIX Quick Beginnings

IBM Communications Server for AIX Features and Packaging

IBM Communications Server for AIX Features and Packaging

Advanced Networking Features

IBM Communications Server for AIX Quick Beginnings

IBM Communications Server for AIX Features and Packaging

Chapter 1. About IBM Communications Server for AIX

IBM Communications Server for AIX Features and Packaging

APPN Backbone Network

Branch Network Node

Figure 2. Branch Extender

APPC Application Suite

IBM Communications Server for AIX Quick Beginnings

IBM Communications Server for AIX Features and Packaging

Chapter 1. About IBM Communications Server for AIX

IBM Communications Server for AIX Features and Packaging

TN Server Configuration Host

Host View of the Configuration Host

TN3270 Program View of the Configuration

SNA Node Running TN Server