HP-UX SNAplus2 R7 Administration Guide HP-UX 11i v1, 11i v2 and 11i v3 Edition: 3 Manufacturing Part Number: 5991–1190 April 2007 © 2007 Hewlett-Packard Development Company, L.P. All rights reserved.
Contents Legal Notices...............................................................................................................................................8 Warranty..............................................................................................................................................8 U.S. Government License.. ................................................................................................................ 8 Copyright Notices.. ................................
1.3.4 1.3.5 Session Routing.. ........................................................................................................ 31 Branch Extender..........................................................................................................36 1.4 Accessing Subarea Networks from APPN Networks.. ........................................................... 38 Chapter 2 Introduction to SNAplus2................................................................................................
Chapter 5 Defining Connectivity Components...................................................................................85 5.1 Defining DLCs, Ports, and Connection Networks...................................................................86 5.1.1 DLC, Connection Network, and Port Configuration Parameters.................................86 5.1.2 Additional Configuration.. ............................................................................................ 90 5.2 Defining Link Stations.. ..
7.7.3 Configuring a Security Access List.. ......................................................................... 122 Chapter 8 Configuring User Applications.........................................................................................123 8.1 Configuring 3270 Users and Sessions.. ............................................................................... 124 8.1.1 Configuring 3270 Emulator Users.............................................................................124 8.1.
11.2.2 11.2.3 11.2.4 Viewing Status of a Win32 Client............................................................................146 Disabling a Win32 Client.........................................................................................146 Win32 Client Configuration......................................................................................146 11.3 Managing Win16 Clients.....................................................................................................158 11.3.
C.1 Appendix D D.1 File Format for an Invokable TP Definition...........................................................................200 Using SNAplus2 in a High Availability Environment..................................................205 What is High Availability?.....................................................................................................205 D.2 SNAplus2 High Availability Features....................................................................................206 D.2.
Legal Notices Trademark Notices Legal Notices The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Publishing History New and Changed Information in This Edition Publishing History The manual publishing date and part number indicate its current edition. The publishing date will change when a new edition is printed. Minor changes may be made without changing the publishing date. The manual part number will change when extensive changes are made. Manual updates may be issued between editions to correct errors or document product changes.
Before You Begin About This Book Before You Begin This book is a guide for enabling, configuring, and managing SNAplus2. This book applies to Release 7 of SNAplus2. Token Ring and FDDI adapters are not supported on HP-UX 11i v3. Prerequisite Knowledge Before reading this manual, you should have a knowledge of SNA and APPN concepts. For a list of books that provide this information, see Related Publications. About This Book This guide explains how to enable, configure, and manage SNAplus2.
Before You Begin About This Book • Appendix B, APPN Network Management Using the Simple Network Management Protocol, provides information about the support provided by SNAplus2 for the Simple Network Management Protocol (SNMP). This appendix also provides a list of the APPN Management Information Base (MIB) databases that SNAplus2 supports.
Before You Begin SNAplus2 Publications Graphic Conventions UNIX This symbol is used to indicate the start of a section of text that applies only to the HP-UX operating system. WINDOWS This symbol is used to indicate the start of a section of text that applies to the Win32 client, which runs on Microsoft Windows 2000, Windows XP, or Windows Server 2003. SNAplus2 also provides a Win16 client that runs on Microsoft Windows 3.1 and Windows for Workgroups 3.11.
Before You Begin SNAplus2 Publications Explains how to use the set of six utility applications supplied with SNAplus2 that can be run over an SNA network using SNAplus2. These applications use independent LU 6.2 protocols to communicate with similar applications running on other nodes in an SNA network. SNAplus2 Glossary Provides a comprehensive list of terms and their definitions used in the SNAplus2 library.
Before You Begin Related Publications Contains the information you need to write application programs using the Common Service Verbs (CSV) API. HP-UX SNAplus2 MS Programmer’s Guide Contains the information you need to write applications using the Management Services (MS) API. HP-UX SNAplus2 NOF Programmer’s Guide Contains the information you need to write applications using the Node Operator Facility (NOF) API. Related Publications For information about SNA, APPN, or LU 6.
SNA Terms and Concepts Basic SNA Concepts 1 SNA Terms and Concepts This chapter defines Systems Network Architecture (SNA) terms and concepts that are important to understanding and using SNAplus2. For information about SNAplus2, its capabilities, and how it implements the different SNA concepts described, see Chapter 2, Introduction to SNAplus2. If you are already familiar with SNA and SNAplus2, you can begin with Chapter 3, Administering SNAplus2.
SNA Terms and Concepts Basic SNA Concepts SNA functions are divided into a hierarchical structure of separate layers, each performing a specific set of functions. This division of network functions into layers enables network devices to share information and processing resources without having detailed information about each device on the network.
SNA Terms and Concepts Basic SNA Concepts Note HP-UX computers running SNAplus2 can function as type 2.1 or type 2.0 nodes. A type 4 or 5 subarea node to which a peripheral node is attached acts as a boundary node. It performs a boundary function by translating between the network addresses used by a subarea node and the local addresses used by a peripheral node. A simple subarea network includes the following components: Host A host is a mainframe computer compatible with the original IBM System/370.
SNA Terms and Concepts Basic SNA Concepts The root of the tree (at the top of the diagram) is the computer controlling the network. The branches are the communications links from the host to the other computers in the network (terminal controllers); the leaves (at the bottom of the diagram) are the terminals or printers attached to these computers, which are accessed by users. The traditional subarea SNA set-up described here enables the users to use the resources of a single host system.
SNA Terms and Concepts Basic SNA Concepts • File transfer • Database transaction processing • Network management • Centralized data services The TP accesses the network through a logical unit (LU) that establishes and maintains a session with a partner LU on another node. For more information about logical units, see Section 1.2.6, Network Accessible Units. Note SNAplus2 includes sample TPs for most supported APIs. For more information on sample TPs, refer to the programmer’s guide for the API.
SNA Terms and Concepts Basic SNA Concepts Physical Units Each SNA node contains a physical unit (PU). The PU manages resources (such as link resources) and supports communication with a host. Note On type 2.1 nodes (which can be APPN nodes), the control point provides PU services in addition to providing other services (see Section 1.2.6, Network Accessible Units). Two type 2.1 nodes (such as SNAplus2 nodes) can communicate directly, without requiring the services of a host to establish communications.
SNA Terms and Concepts Basic SNA Concepts For example, LU type 1 can support an application program running under Information Management System/ Virtual Storage (IMS/VS) and communicating with an IBM 8100 Information System. This enables an operator to correct a database that the application program maintains. Applications that use LU 1 are often described as remote job entry (RJE) applications. LU 0 (for LUA) LU 0, an early LU definition, supports primitive program-to-program communication.
SNA Terms and Concepts Basic SNA Concepts Session Types SNAplus2 is primarily concerned with the following types of sessions: LU-LU sessions In order for two TPs to communicate, the LUs that support the TPs must first establish an LU-LU session. In general, a session is established when a TP in one SNA node tries to communicate with a TP in another node and no existing session between the LUs on the two nodes is available. SSCP-LU sessions A dependent LU (see Section 1.2.
SNA Terms and Concepts Basic SNA Concepts An independent LU can act as a primary or as a secondary LU when establishing a session. Multiple and Parallel Sessions An independent LU can participate in sessions with more than one remote LU at the same time (multiple sessions). An independent LU can also participate in parallel sessions, or multiple concurrent sessions with the same remote LU. Dependent LUs (including dependent LU 6.2) cannot have multiple sessions.
SNA Terms and Concepts Basic SNA Concepts Figure 1–3 Communication between Transaction Programs and Logical Units Conversation TP Request TP Request Response LU Response Session LU Link Node A Node B SNA defines two types of conversations: basic and mapped. These two types of conversations use different methods to indicate the length of transmitted or received data packages to be passed between SNAplus2 and the TP.
SNA Terms and Concepts Basic APPN Concepts • For peer networks that do not support APPN, type 2.1 nodes can support sessions only with adjacent nodes; their sessions cannot be routed through intermediate nodes. • For APPN networks, SNA can compute routes dynamically at the time of session initiation, using a class of service specified for the mode used by the session (see Section 1.2.11, Class of Service).
SNA Terms and Concepts Basic APPN Concepts 1.3.1 APPN Node Types The following types of nodes can be part of an APPN network: • Network nodes (see Figure 1–4, Portion of a Sample APPN Network) • End nodes (see Figure 1–4, Portion of a Sample APPN Network) In addition, low-entry networking (LEN) nodes can be connected to an APPN network, but they do not use APPN features (see Figure 1–4, Portion of a Sample APPN Network). A sample APPN network is shown in Figure 1–4, Portion of a Sample APPN Network.
SNA Terms and Concepts Basic APPN Concepts the network node provides services. Because an APPN network node acts as the network entry point for end and LEN nodes in its domain, the network node is also referred to as the network node server for those nodes.
SNA Terms and Concepts Basic APPN Concepts • Two parallel CP-CP sessions are established between an APPN end node and the adjacent network node acting as the server for the end node. These CP-CP sessions are used to exchange directory, topology, and management services data. • LEN nodes do not support CP-CP sessions. The functions provided in CP-CP sessions vary based on the types of nodes involved, as follows: • All CP-CP sessions conduct directory searches.
SNA Terms and Concepts Basic APPN Concepts • An APPN end node maintains a directory that includes its own LUs. It can also be configured to store directory entries for partner LUs in adjacent nodes. This enables local LUs to establish peer-to-peer sessions with those LUs without using APPN functions.
SNA Terms and Concepts Basic APPN Concepts Figure 1–6 End Node Directory Node LEN1 LUX Node EN1 Node EN3 Node NNA LU1 LU2 LU3 LUA Node EN2 LU4 Node EN3 Directory: LU1 - Node EN3 LUX - Node LEN1 Potential partner LUs in the APPN network do not need to be defined to the end node. However, in order for Node EN3 to establish a session with LUX on Node LEN1, the LU on the LEN node must be configured as a partner LU on Node EN3.
SNA Terms and Concepts Basic APPN Concepts 2. If the destination LU is not located in the network node—but appears in its directory—the network node sends a directed search request to the destination network node server to verify the location of the LU. If the LU is not in the network node directory, the node initiates a search of the network by sending a broadcast search to every adjacent network node. 3. Each node in turn propagates the broadcast and returns replies indicating success or failure.
SNA Terms and Concepts Basic APPN Concepts Notes 1. APPN network nodes and end nodes also maintain topology information about links to a connection network (see Figure 1–10, Definitions Needed for Direct Links from Node EN1 to Every Node in an APPN Network). 2. LEN nodes maintain local topology information. They do not forward this information to a network node server.
SNA Terms and Concepts Basic APPN Concepts The shared network topology database is duplicated at Nodes NNA, NNB, NNC, and NND. In addition, each of those nodes includes local topology information (except Node NNC, which does not have any local topology information because it does not have any links to end nodes). For example, Node NNB includes information for Link f to Node EN2 and Link g to Node EN3, but it does not include information for Link i, which connects Nodes EN2 and EN3.
SNA Terms and Concepts Basic APPN Concepts Resource characteristics maintained by the topology database can include congestion status. If a network node becomes heavily congested, the network node can relay this information to other network nodes in the network, making the congested network node less likely to be included in session routes calculated for new sessions.
SNA Terms and Concepts Basic APPN Concepts • EN1 to NNA • EN1 to EN2 • EN1 to EN3 • EN1 to EN4 • EN1 to EN5 Figure 1–10 Definitions Needed for Direct Links from Node EN1 to Every Node in an APPN Network Network Node A (NNA) End Node 2 (EN2) End Node 1 (EN1) End Node 3 (EN3) End Node 4 (EN4) Link Definitions Needed for Node 1 EN1: EN1 to NNA EN1 ro EN2 EN1 to EN3 EN1 to EN4 EN1 to EN5 End Node 5 (EN5) If all of the nodes in the network are to support direct links to every other node, a total
SNA Terms and Concepts Basic APPN Concepts Figure 1–11 Definitions Needed for Direct Links Using a Virtual Node Network Node A (NNA) End Node 2 (EN2) End Node 1 (EN1) End Node 3 (EN3) Virtual Node 1 (VN) Link Definitions Needed for Node 1 EN1: End Node 4 (EN4) EN1 to NNA EN1 to VN End Node 5 (EN5) To support direct links between any two end nodes in the APPN network, a total of ten link definitions is required.
SNA Terms and Concepts Basic APPN Concepts Figure 1–12 Branch Extender Network Node Server APPN Backbone Network Branch Network Node End Nodes 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 organization’s headquarters).
SNA Terms and Concepts Accessing Subarea Networks from APPN Networks 1.4 Accessing Subarea Networks from APPN Networks Although APPN networks do not require a host to control resources in the network, hosts often participate in APPN networks. APPN has been implemented on many host platforms, and allows the hosts to perform as network nodes in the APPN network while still providing an SSCP to control any old subarea SNA function. Many SNA networks contain elements of both subarea SNA and APPN.
Introduction to SNAplus2 What Is SNAplus2? 2 Introduction to SNAplus2 This chapter provides an overview of SNAplus2 features and shows some of the basic configurations in which SNAplus2 can be used. It describes the major components of SNAplus2 and the SNA resources that are configured for and used by SNAplus2, and provides an overview of SNAplus2 administration responsibilities and tools. 2.
Introduction to SNAplus2 Example Configurations development of custom applications. These APIs implement the WOSA standards and are compatible with the APIs provided with Microsoft’s Host Integration Server. Administration facilities SNAplus2 includes several methods and tools you can use to configure and manage SNAplus2 servers and clients. For more information about SNAplus2 administration, see Section 3.1, Overview of SNAplus2 Administration. 2.
Introduction to SNAplus2 Example Configurations Figure 2–2 SNAplus2 Nodes in an APPN Network End Node Network Node LEN Node End Node End Node In Figure 2–3, SNAplus2 Node Providing PU Concentration and DLUR, a server with SNAplus2 is configured as an APPN network node that implements PU concentration to provide connectivity between a host computer and the computers in an APPN network.
Introduction to SNAplus2 Example Configurations In Figure 2–4, SNAplus2 Node Configured for TN Server, a computer running SNAplus2 provides TN server support for TN3270 and TN3270E clients. The TN server node and the clients communicate through the TCP/IP network.
Introduction to SNAplus2 SNAplus2 Components Figure 2–5 SNAplus2 Client/Server Configuration Host Controller SNA Node Server TCP/IP Network Windows 3.1 Client UNIX Client Windows NT Client Windows 95 Client These examples show the most basic ways in which you can configure SNAplus2 nodes. By combining nodes using these basic configuration types, you can use SNAplus2 to support different types of communication within more complex networks. 2.
Introduction to SNAplus2 SNAplus2 Components Figure 2–6 Components of SNAplus2 Emulation Programs User Applications Transaction Programs APIs Administration Facilities User Space Kernel Local Node LU Services LU 0 LU 1, 2, 3 LU 6.2 Link Protocols Communication with Host and Peer Computers The local node—including its associated connectivity resources (DLCs, ports, and link stations)—is implemented as a set of STREAMS components in the kernel of the HP-UX system.
Introduction to SNAplus2 SNAplus2 Components Passthrough Services Passthrough services enable downstream computers on a LAN to access host resources through a server running SNAplus2, or enable computers to access SNA resources across mixed SNA and IP networks. SNAplus2 provides the following passthrough services: • PU concentration (see Section 2.3.1, Node Components). • Dependent LU requester (see Figure 2–7, PU Concentration). • TN server (see Figure 2–7, PU Concentration).
Introduction to SNAplus2 SNAplus2 Components Dependent LU Requester This section does not apply to LEN nodes. In addition to providing direct access to a host computer, SNAplus2 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. DLUR on the SNAplus2 node works in conjunction with dependent LU server (DLUS) at the host.
Introduction to SNAplus2 SNAplus2 Components Figure 2–8 TN Server TN Server Configuration Host View of the Configuration Host TN3270 Program View of the Configuration Host SNA Node Running TN Server SNA Node Host TCP/IP Network TCP/IP Network SNA Nodes Running 3270 Emulators Clients Running TN3270 and TN3270E Programs Clients Running TN3270 and TN3270E Programs The SNAplus2 TN server feature provides an association between a TN3270 user and SNAplus2 3270 LU.
Introduction to SNAplus2 SNAplus2 Components • 3270 emulation programs (see Section 2.3.2, User Applications). • 5250 emulation programs (see Section 2.3.2, User Applications). • RJE workstation daemon (see Section 2.3.2, User Applications). • APPC Application Suite (see Section 2.3.
Introduction to SNAplus2 SNAplus2 Components Refer to HP-UX SNAplus2 RJE User’s Guide for information about using RJE to submit jobs to a host and about setting up the workstation style file. APPC Application Suite SNAplus2 includes the IBM APPC Application Suite, which provides the following set of APPC applications using independent LU 6.2: ACOPY, AFTP, ANAME, APING, APPC Remote EXECution (AREXEC), and APPC Tell (ATELL). For more information, refer to HP-UX SNAplus2 APPC Application Suite User’s Guide.
Introduction to SNAplus2 SNAplus2 Components In the Motif administration program, directory entries and partner LUs are not shown explicitly, but are included under the “Remote Systems” heading in the Node window for the local node.
Introduction to SNAplus2 SNAplus2 Components MS API The Management Services (MS) API enables an application to communicate with other MS products in an APPN network. An application can be either NMVT-level or MDS-level, depending on the type of MS data it sends and receives. SNAplus2 performs any data conversion that is required. For more information, refer to HP-UX SNAplus2 MS Programmer’s Guide.
Introduction to SNAplus2 SNAplus2 Components Each server maintains information about its own node configuration in a node configuration file. You can use the SNAplus2 administration tools, described in Section 3.1.2, Administration Tools, to examine and modify the node’s configuration. You can configure a node from any other computer in the domain, as long as the SNA software is running on the node where the configuration is performed (whether or not the node being configured is started).
Introduction to SNAplus2 SNAplus2 Components Note If the LAN is split by a network failure into two noncommunicating domains, each containing one or more backup servers, SNAplus2 cannot maintain a consistent configuration of domain resources across the LAN. In this situation, each domain has an acting master server, each tracking changes made to the domain configuration file in its own domain but unaware of any changes made in the other domain.
Introduction to SNAplus2 SNAplus2 Resources • The 32-bit version can be installed on machines running Microsoft Windows 2000, Windows XP, or Windows Server 2003. Configuration information required by Win32 clients is managed through the Windows Registry. For more information about the sna.ini file and the Windows Registry, and about managing Windows clients, refer to the HP-UX SNAplus2 Administration Guide. For information about Windows SNA APIs, see Section 2.3.
Introduction to SNAplus2 SNAplus2 Resources • DLCs (see Section 2.4.1, Connectivity Resources). If you use the Motif administration program to configure a port, the corresponding DLC definition is created automatically. For command-line administration, the DLC is configured separately. • Ports (see Section 2.4.1, Connectivity Resources). • Link stations (see Section 2.4.1, Connectivity Resources). • Connection networks (see Section 2.4.
Introduction to SNAplus2 SNAplus2 Resources • A peer computer, with SNAplus2 and the remote computer communicating as equal partners (the typical arrangement in an APPN network) • A downstream computer, which uses the SNAplus2 PU concentration feature or DLUR feature as a gateway to access a host. A link station is associated with a specific port. One or more link stations can be defined on the same port. Connection Networks Connection networks cannot be used by LEN nodes.
Introduction to SNAplus2 SNAplus2 Resources Dependent LUs Type 0–3 LUs are referred to as dependent LUs; they can support only one user session at a time, and a session is controlled by the host program. Type 6.2 LUs can also be dependent LUs if they are used to communicate with host computers running older versions of SNA host software. LU types 0–3 are sometimes referred to as “old LUs,” and are used to communicate with hosts using 3270 emulation, RJE or LUA.
Introduction to SNAplus2 SNAplus2 Resources • Balancing the traffic from user sessions across multiple servers or multiple host links, by defining a pool containing LUs on more than one node or on more than one host link. • Permitting access to more than one host system from the same configuration, so that if one host system becomes unavailable, sessions can still be established to another system without requiring reconfiguration. Default LUs If you are configuring type 6.
Administering SNAplus2 Overview of SNAplus2 Administration 3 Administering SNAplus2 For an overview of SNAplus2 administration and the different administration tools provided, see Section 3.1, Overview of SNAplus2 Administration. The first step in administering SNAplus2 is configuring the node and its resources. configuration as described in Section 3.2, Planning for SNAplus2 Configuration.
Administering SNAplus2 Overview of SNAplus2 Administration Notes 1. This document provides general information about SNAplus2 administration, which you can perform using any of the tools described in this section. For most purposes, the Motif administration program is recommended, because it provides context-sensitive guidance for node configuration and management. 2.
Administering SNAplus2 Overview of SNAplus2 Administration Before starting the Motif administration program, make sure the SNAplus2 software is enabled (for more information, see Chapter 3, Administering SNAplus2). As with any X/Motif application, 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: xsnapadmin & All started SNAplus2 servers are shown on the main screen.
Administering SNAplus2 Overview of SNAplus2 Administration administration commands from a client if you specify -n with a server name. A command issued from a client using -n has the same effect as if it were issued at the named server. You can get help for command-line administration by using any of the following commands: • snapadmin -h provides basic help for command-line administration and usage information for command-line help.
Administering SNAplus2 Overview of SNAplus2 Administration Note SNAplus2 configuration is a dynamic process; it is not necessary to define the entire configuration before starting the SNAplus2 software. The configuration file provides an initial definition of the available resources, but you can add, delete, or modify resources as necessary while the SNAplus2 software is running. SNAplus2 stores the current definition so that you can use it again when you need to restart the system.
Administering SNAplus2 Overview of SNAplus2 Administration server network configuration, you can specify global settings for the types of events to record on all servers, and then override these on individual servers if necessary. • SNAplus2 also maintains a usage log file, which is used to record information about the current and peak usage of SNAplus2 resources.
Administering SNAplus2 Planning for SNAplus2 Configuration Administration Tool Executable File(s) Motif administration program /opt/sna/bin/X11/xsnapadmin Command-line administration program /opt/sna/bin/snapadmin Any user can then run the appropriate administration tool and view information, but SNAplus2 will still prevent users not in the sna group from modifying, starting, or stopping resources. 3.
Administering SNAplus2 Enabling and Disabling SNAplus2 on the Local System 3.3 Enabling and Disabling SNAplus2 on the Local System This section explains how to enable and disable the SNAplus2 software on the HP-UX server. You must enable the SNAplus2 software before you can use any SNAplus2 tools (including the Motif administration program). Normally, the software is enabled automatically after you install SNAplus2, but if necessary you can enable it manually. 3.3.
Administering SNAplus2 Enabling and Disabling SNAplus2 on the Local System that would cause the total amount of memory currently allocated to SNAplus2 components to exceed this limit, the allocation attempt fails. If you do not use this option, kernel memory usage is not limited. -t Activates tracing on all interfaces between kernel components, and also client/server and back-level client/ server tracing. (This option does not turn on DLC tracing.
Administering SNAplus2 Using the Motif Administration Program If a 3270 emulation program is using LUs on the node when you disable the SNAplus2 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. If the RJE workstation program is running, it automatically exits.
Administering SNAplus2 Using the Motif Administration Program 3.4.2 Resource Windows The Domain window and the Node window show most of the information you need and provide easy access to additional information. From those windows, you can easily display information about resources in your local network. The Domain window shows all defined nodes, and enables you to add, delete, start, and stop nodes. Double-clicking on any node brings up the Node window for that node.
Administering SNAplus2 Using the Motif Administration Program Figure 3–1 SNAplus2 Domain Window If any active nodes in the domain (nodes on which SNAplus2 is running) are not configured, SNAplus2 prompts you to configure the node. Note The Domain window does not list SNAplus2 clients. Clients use the resources of SNAplus2 servers (SNA nodes) to access SNA resources.
Administering SNAplus2 Using the Motif Administration Program Select Logging from the Diagnostics menu. Turn tracing for a specific node on or off Click on the line for the node and select Tracing on selected node from the Diagnostics menu. Get information about domain resources Choose any of the options on the Windows menu. In addition to shared domain resources, the Windows menu also lists each Node window in the domain.
Administering SNAplus2 Using the Motif Administration Program Figure 3–2 Node Window From the Node window, you can add, delete, modify, and manage all of the resources and components for the SNAplus2 node. The layout of the resources in the window shows the relationships among resources and enables you to control which resources are displayed.
Administering SNAplus2 Using the Motif Administration Program The Node box in the top-right corner of the Node window indicates whether the node is Active or Inactive. Any ports, local LUs, and remote nodes that are defined on the node 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.
Administering SNAplus2 Using the Motif Administration Program 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 button or Contract button appears next to it. An Expand button indicates that the associated child items are hidden. You can click on the Expand button to show them. A Contract button indicates that the child items are shown. You can click on the Contract button to hide them.
Administering SNAplus2 Using the Motif Administration Program Copies the selected item. Pressing this button opens a dialog whose fields duplicate the configuration of the selected item. Complete the dialog’s fields (filling in the new item’s name) to add the new resource. Displays the current status of the selected item. Many resources, such as ports and link stations, cannot be modified while they are active.
Administering SNAplus2 Using the Motif Administration Program Figure 3–4 Sample Dialog Resource dialogs guide you through the configuration process and supply default values whenever possible. For example, when you add a dependent LU, the Motif administration program automatically fills in the LU number field with an available LU number on the link station you specify. If you do not supply a required value, the program presents a message pop-up that indicates the information you need to provide.
Administering SNAplus2 Using the Motif Administration Program If you are permitted to change the information in a resource dialog (when you are adding a new item or modifying an existing one), the dialog includes OK and Cancel buttons. Press the OK button when you are finished, or the Cancel button to exit without changing the configuration for the resource.
Administering SNAplus2 Using the Motif Administration Program Figure 3–5 Sample Status Dialog Status dialogs show information about the current state of the resource. The information is updated dynamically as you view it. 3.4.5 Help Windows The online help for the Motif administration program provides detailed guidance for each configuration task you need to perform. In particular, task sheets can take you through each step you need to perform in configuring a particular resource.
Administering SNAplus2 Using the Motif Administration Program Figure 3–6 Sample Help Window Additional help windows are included for each window and dialog, for error messages, and for SNA concepts.
Administering SNAplus2 Using the Command-Line Administration Program 3.5 Using the Command-Line Administration Program Command-line configuration enables you to change all SNAplus2 configuration parameters. You can use it to configure any of the resources that are available through the Motif administration program, and can set or change configuration parameters that are not exposed in the Motif program.
Basic Configuration Tasks Configuring Client/Server Functions 4 Basic Configuration Tasks This chapter provides an overview of configuration tasks and explains how to configure the SNAplus2 node. It also explains how to configure master and backup servers when SNAplus2 is used in a client/server environment. 4.1 Configuring Client/Server Functions This section is relevant only if you installed SNAplus2 to run in a client/server environment (with multiple SNAplus2 nodes in the same network).
Basic Configuration Tasks Configuring the Node Removes a server from the list. You can use the delete_backup command to delete either the master server (so that the second server listed takes over as master) or a backup server (so that it can no longer act as the master). Note You cannot delete a server if it is the only server listed on which the SNAplus2 software is running, because in this case there is no other server that can take over as the master server.
Basic Configuration Tasks Configuring Logging When you define the control point, SNAplus2 automatically defines a local LU with the same name. That LU can act as a default local LU for the node. Control point alias Local alias for the default local LU. Supply this value if the default local LU is used by independent LU 6.2 LUs. Node ID Identifier for the PU on the local node. Supply a value only if the node will be used for dependent traffic using the default (control point) LU. 4.2.
Basic Configuration Tasks Configuring Logging /var/opt/sna/sna.err /var/opt/sna/bak.err (backup) Audit log file /var/opt/sna/sna.aud /var/opt/sna/bak.aud (backup) Usage log file /var/opt/sna/sna.usage /var/opt/sna/bak.usage (backup) You can view the log files using a text editor or other HP-UX system utilities: vi View the file in a text editor. This allows you to move through the file forwards or backwards, and to search for particular entries. pg View a file one page at a time.
Defining Connectivity Components 5 Defining Connectivity Components In order for the SNAplus2 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.
Defining Connectivity Components Defining DLCs, Ports, and Connection Networks For information about configuring PU concentration, see Section 9.2, Configuring PU Concentration. 5.1 Defining DLCs, Ports, and Connection Networks A port represents the local end of a communications link as a unique access point in the network. Each port is associated with a specific link protocol, which can be any of the following: • SDLC • Token ring • Ethernet • FDDI • X.
Defining Connectivity Components Defining DLCs, Ports, and Connection Networks SNA port name The locally known name of the port. Adapter card number This field is not used for Enterprise Extender ports. A number that identifies the adapter card to use, if you have more than one card of the same type in this computer. For SDLC or QLLC, the card of this type in the lowest numbered slot is Card 0, the second card of this type is Card 1, the third is Card 2, and so on for any subsequent cards of the same type.
Defining Connectivity Components Defining DLCs, Ports, and Connection Networks Select a value that describes the role of the local node for link stations defined on this port. In SDLC communication, one end manages the link and is called the primary link station. The other end is the secondary link station. Use one of the following values for this field: Secondary The other end of the link is to be the controller and the remote system is configured to be primary.
Defining Connectivity Components Defining DLCs, Ports, and Connection Networks • 1 (300 baud) • 2 (600 baud) • 3 (1200 baud) • 4 (2400 baud) • 5 (4800 baud) • 6 (9600 baud) • 7 (19200 baud) For example, you can specify a 9600 baud rate dial string by entering (6), as follows: (6)AT &&D3 &&Q1 DT7,012345678 For an explanation of the rest of the dial string, refer to your modem’s documentation. For switched outgoing ports, the dial string is configured on each link station.
Defining Connectivity Components Defining DLCs, Ports, and Connection Networks Note The underlying stack is also configured with an address and accepts only calls that specify an address starting with the configured address. Any address configured on the port must start with the address configured on the stack; otherwise, calls accepted by the stack are subsequently rejected by the port.
Defining Connectivity Components Defining Link Stations 5.2 Defining Link Stations To communicate with other nodes in an SNA network, you must configure the characteristics of a link station (LS) to an adjacent node in the SNA network. Before you can define a link station, you must define a port for the adapter (and link protocol) you are using. Most of the information needed to configure a link station is the same, whatever protocol is being used.
Defining Connectivity Components Defining Link Stations Link station Use this area of the dialog to provide information that is required for all link stations, whether they support LU traffic for dependent LUs, independent LUs, or both. For descriptions of the parameters in this section, see Section 5.2.1, Link Station Configuration Parameters. Independent LU traffic Provide this information only if you are using the link station for independent traffic.
Defining Connectivity Components Defining Link Stations The link station can be used for both independent and dependent LU traffic. For this option, you must supply values for the fields described in Section 5.2.1, Link Station Configuration Parameters and Section 5.2.1, Link Station Configuration Parameters, in addition to those described in this section. Independent only The link station can be used only for independent LU traffic.
Defining Connectivity Components Defining Link Stations For switched incoming ports, the dial string is configured on the port. For leased ports, this field does not apply. By default, the dial string is sent to the modem at the rate of 1200 bits per second (the default baud rate) using asynchronous communications.
Defining Connectivity Components Defining Link Stations The DTE address of the remote DTE as a series of hexadecimal digits (only applicable if the circuit is a switched virtual circuit). Adapter/Port Number The card number (if your card has only one port). If you have only a single card, use a value of 0. If your card has more than one port, use the value npx, where n is the card number and x is the port number. Cards are numbered starting at 0; ports are numbered starting at 1.
Defining Connectivity Components Defining Link Stations The type of link to the remote node that is accessed through this link station (only applicable if the local node is a branch network node). If the remote node is a network node within the main APPN backbone, choose Uplink (to backbone). If the remote node is an end node within the branch, choose Downlink (within branch).
Defining Connectivity Components Defining DLUR PUs The link station is to a downstream node that will communicate with a host using the DLUR capabilities of the local node. (To the host, the LUs on the downstream node appear to reside on the local node.) Such links can be used only if the local node is an APPN network node. Downstream PU name The PU name associated with the downstream node. This value must match the PU name that is configured for the downstream node on the host computer.
Defining Connectivity Components Defining DLUR PUs To provide passthrough DLUR services to a downstream node, you must first configure (on the local node) the PU name associated with the downstream node. This value must match the PU name that is configured for the downstream node on the host computer. To configure a DLUR PU, use one of the following methods: Motif administration program Select Connectivity and New DLUR PU from the Services menu on the Node window.
Defining Connectivity Components Defining DLUR PUs Whether SNAplus2 retries the attempt to contact the DLUS if it fails on the first attempt. If you set this option, SNAplus2 will retry indefinitely if the first attempt fails. If you do not set this option, it will only retry once. 5.3.
Configuring Dependent LUs Defining LU Types 0–3 6 Configuring Dependent LUs This chapter provides instructions for configuring LUs and LU pools to support user applications that use 3270, TN3270, RJEand LUA communications. To use these, you must configure dependent LUs. Before you can configure the resources described in this chapter, you must perform the following configuration: • Configure the node as described in Section 4.2, Configuring the Node.
Configuring Dependent LUs Defining LU Types 0–3 6.1.1 LU Types 0–3 Configuration Parameters The following parameters are required for LU types 0–3 configuration: LU name An LU name of 1–8 characters (for a single LU) or a base name of 1–5 characters (for a range of LUs, a prefix is added to the base name to form all of the names for the LUs that are defined). The LU name is used only locally; it does not need to correspond to a name defined on the host.
Configuring Dependent LUs Defining LU Pools Pool name The name of the LU pool. 6.1.2 Additional Configuration After performing the LU type 0–3 configuration, continue with the following configuration tasks: • To use a pool of dependent LUs for a 3270 display, for TN3270 or for LUA, define the LU pool as described in Section 6.2, Defining LU Pools. • For 3270, define emulator users as described in Section 8.1.1, Configuring 3270 Emulator Users.
Configuring Dependent LUs Defining LU Pools Motif administration program Select LU Pools from the Windows menu on the Node window, then choose New to add a pool. Command-line administration program Issue the following command: define_lu_pool 6.2.1 LU Pool Configuration Parameters The following parameters are required for LU pool configuration: Name A name to identify the LU pool. This field applies only when you are adding a new LU pool. You cannot change the name of an existing pool.
Configuring APPC Communication Defining Local LUs 7 Configuring APPC Communication APPC applications, 5250 emulation programs, and CPI-C applications all require that you configure APPC first. An APPC application uses the node’s LU type 6.2 resources to communicate with another APPC or CPI-C application on a host or peer computer, using a specified mode. If the applications use CPI-C, you may need to do additional CPI-C configuration after configuring APPC. A CPI-C application uses the node’s LU type 6.
Configuring APPC Communication Defining Local LUs 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. 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.
Configuring APPC Communication Defining Remote Nodes Whether to make the LU a member of the default dependent APPC LU pool. An application that does not specify a particular local LU to use is assigned an available LU from the default pool. This field applies only if the LU is a dependent LU. 7.1.2 Additional Configuration After performing the local LU configuration, continue with the following configuration tasks: • To define a remote node, see Section 7.2, Defining Remote Nodes.
Configuring APPC Communication Defining Partner LUs To define a remote node, issue the following command: define_directory_entry To define a partner LU, issue the following command: define_partner_lu 7.2.1 Remote Node Configuration Parameters The following parameter is required for remote node configuration: Node’s SNA network name The fully qualified CP name of the remote node. The value entered on this dialog must match the CP name configured at that remote node. 7.2.
Configuring APPC Communication Defining Partner LUs • Wildcard partner LU on remote node Command-line administration program To define a partner LU, issue the following command: define_partner_lu To define a LEN node as a partner LU, issue the following commands: define_adjacent_len_node define_directory_entry 7.3.1 Partner LU Configuration Parameters The following parameters are required for partner LU configuration: Partner LU name The fully qualified LU name of the partner LU.
Configuring APPC Communication Defining Partner LUs Supports parallel sessions Whether the partner LU can support more than one session at a time. In most cases, the partner LU supports many sessions at one time, but some LEN nodes do not support parallel sessions. This field applies when you define partner LU on a specific remote node or when you define a partner LU alias.
Configuring APPC Communication Defining TPs • The first string can be a complete SNA network name that matches the first part of the fully qualified partner LU names exactly, or a wildcard prefix that matches the beginning of the network name for the partner LUs. If you supply a wildcard prefix as the value for the first string, leave the second string blank. For example, a wildcard entry of A would match all LUs in the SNA networks named A, ANT, or APPN (but not BUFFALO or ZEBRA).
Configuring APPC Communication Defining TPs Note In this manual, the phrase “Receive_Allocate” is used to indicate any of these three API calls. You can also define an invokable TP to route incoming allocation requests to a running TP. For an invokable TP, you can also specify a timeout value, to limit the wait for an allocation request. (You can only configure this option using command-line administration.
Configuring APPC Communication Defining TPs For information about using the snaptpinstall or tpinst32 command, see Appendix C, Configuring an Invokable TP from the Command Line. 7.4.1 TP Invocation Parameters on a Server This section describes the parameters required by the Motif administration program or the command-line administration program when configuring an invokable TP on a server.
Configuring APPC Communication Defining TPs Multiple instances supported If you do not select this option, the TP is a queued TP. Any incoming Allocate requests arriving while the TP is running are queued until the TP issues another Receive_Allocate, or until it finishes running and can be restarted.
Configuring APPC Communication Defining TPs Group ID The group ID that SNAplus2 uses to start the TP. This must be a valid HP-UX group ID on the SNAplus2 computer. This parameter is optional. If it is not included, the default is sna. Standard input Specify the full path name of the standard input file or device used by the TP. This parameter is optional. If it is not included, the default is /dev/null. Standard output Specify the full path name of the standard output file or device used by the TP.
Configuring APPC Communication Defining Modes and Classes of Service Security access list Name of a security access list that contains user IDs permitted to access this TP. If the Restrict access option is selected, you must provide this value. Conversation type Specify whether the TP accepts only basic conversations, only mapped conversations, or either type of conversation. Sync level Specify the levels of confirm synchronization that the TP accepts.
Configuring APPC Communication Defining Modes and Classes of Service Table 7–1 Standard Mode and COS Names Mode Name Associated COS Name Purpose (blank) #CONNECT Sessions that do not specify a mode name (basic default COS parameters) #BATCH #BATCH Sessions used by batch-processing applications #BATCHSC #BATCHSC Sessions used by batch-processing applications, with a minimal level of routing security #BATCHC #BATCH Sessions using compression in batch-processing applications #BATCHCS #BATCH
Configuring APPC Communication Defining Modes and Classes of Service Name The name of the mode you are defining. The mode name is a string of 1–8 characters. APPC applications that use this mode, including both local and remote applications, may also use this name, so check the name with your application developer (or refer to your product documentation for a third-party application). COS name The name of the class of service for this mode. The name is a string of 1–8 characters.
Configuring APPC Communication Defining Modes and Classes of Service Initial window size The initial setting for the number of request units (RUs) that the local LU can receive before it must send a pacing response to the remote LU. This can be safely set to 4. Setting it higher can improve performance in some circumstances, but doing so also increases memory usage.
Configuring APPC Communication Defining CPI-C Side Information 7.6 Defining CPI-C Side Information 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.
Configuring APPC Communication Defining CPI-C Side Information • #INTERSC • QPCSUPP Partner TP The name of the transaction program with which the CPI-C application communicates: • If the TP is a user application, specify the name as normal characters (up to 64 characters in length). • If the TP is a service TP, specify the name in hexadecimal (up to 8 hexadecimal digits, representing 4 bytes).
Configuring APPC Communication Configuring APPC Security • To define APPC security, see Section 7.7, Configuring APPC Security. • To configure 5250 communication, see Chapter 8, Configuring User Applications. 7.7 Configuring APPC Security You can perform the following configuration tasks for APPC security: • Configuring session security as described in Section 7.7.1, Configuring Session Security • Configuring conversation security as described in Section 7.7.
Configuring APPC Communication Configuring APPC Security To configure conversation security, use one of the following methods: Motif administration program Select APPC, Security, and Conversation-level security from the Services menu on the Node window.
Configuring User Applications 8 Configuring User Applications This chapter provides instructions for configuring SNA resources to support user applications that use any of the following communication: 3270, RJE, 5250, and LUA. The SNA resources required by such applications include LUs, session definitions, and user definitions. For 3270, RJE, LUA, and dependent APPC communication, you must configure dependent LUs.
Configuring User Applications Configuring 3270 Users and Sessions You can prepare jobs for submission to the host and add them to the queue for an RJE workstation at any time, regardless of whether the RJE workstation is running. When the workstation runs, it submits any outstanding jobs to the host (in the order in which they were submitted). It also routes any output received from the host to the appropriate destination, as determined by the configuration.
Configuring User Applications Configuring 3270 Users and Sessions Command-line administration program Issue the following command: define_emulator_user Emulation User and Group Configuration Parameters The following parameters are required for each 3270 emulator user definition: User Name The name of the emulator user. For users running the emulation program on HP-UX systems, thisis the name used to log in on that computer. The name is set up by the administrator of the HP-UX system. For Windows 3.
Configuring User Applications Configuring 3270 Users and Sessions The user can specify a style file at the command line, but cannot modify its settings. Sessions How many sessions to define for the user and which LU or pool to use for each session. 3270 permissions The user permissions for SNAplus2 3270 emulator users: Session limit If you select this option, also specify the maximum number of 3270 sessions a user can use from a single 3270 emulator. By default, the maximum number of sessions is set to 10.
Configuring User Applications Configuring 5250 Users Note The SNAplus2 HP-UX 3270 emulation program uses sessions with names in the range SESS0001–SESS0010. To define a session that is initially available to the user, choose a name in this range. If the user has remap permission, you can define a session to which the user can remap, choosing a name that is not in that range (for example, SESS0011). Display or Printer Specify whether the session is a display or printer session.
Configuring User Applications Configuring RJE Workstations Adding an individual user gives access to only that user. You can also add a group of users in a single operation. Adding a group of users gives access to all members of the group. This means that you do not have to define each user individually, reducing the time needed to configure users. Emulator user information can be accessed by a Windows client running an emulation program that is compatible with Microsoft’s Host Integration Server product.
Configuring User Applications Configuring RJE Workstations Note You must configure at least one RJE LU before defining an RJE workstation. To configure an RJE workstation, use one of the following methods: Motif administration program Select RJE Workstations on the Windows menu on the Node window. Command-line administration program Issue the following command: define_rje_wkstn 8.3.
Configuring Passthrough Services Configuring TN Server 9 Configuring Passthrough Services Passthrough services on a server running SNAplus2 enable communication between an SNA host and local systems that are not directly connected to the host. SNAplus2 includes TN server support for TN3270, TN3287, and TN3270E clients, collectively referred to as “TN3270 clients.” To configure this function, see Section 9.1, Configuring TN Server. PU concentration provides connectivity between the host and local systems.
Configuring Passthrough Services Configuring TN Server TN3270 clients can use the TN server only when the node, port, and link station are active. To configure a TN server access record, use one of the following methods: Motif administration program Select TN server from the Services menu on the Node window, and TN server from the submenu. On the resulting window, select the TN Server Client Access Permissions pane and choose New.
Configuring Passthrough Services Configuring TN Server If you choose a different port number that is not in use on the TN server, you also need to configure that port number on the TN3270 clients (or start the TN3270 clients using an option to specify the port number). Port numbers above 2000 are likely to be available. Port numbers in the range 256–1023 may give slightly better security, but are more likely to be in use.
Configuring Passthrough Services Configuring PU Concentration 9.2 Configuring PU Concentration Normally, a dependent LU session requires a direct communications link to the host computer. However, a node running SNAplus2 that has a direct communications link to the host can also provide PU concentration facilities to LUs on downstream computers, enabling them to access the host over the communications link from the SNAplus2 node. The downstream computer must contain an SNA PU type 2.0 or 2.
Configuring Passthrough Services Configuring DLUR If you are defining a range of LUs, specify a base name of 1–5 characters. SNAplus2 adds a three-digit decimal string to the base name to create an LU name for each LU number you specify. Downstream PU name The name of the link station to the downstream node. LU number The LU number must match the LU number defined on the downstream node. Contact your SNA network planner if you do not know what LU number to use.
Configuring Passthrough Services Configuring DLUR Note You cannot configure passthrough DLUR on an end 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. To configure DLUR support on the local node, you must perform the following configuration tasks: 1. Define the local node as described in Section 4.2, Configuring the Node.
Managing SNAplus2 from NetView Using the Host NetView Program 10 Managing SNAplus2 from NetView SNAplus2 includes a remote command facility (RCF) that operates in conjunction with the NetView program at a host computer, enabling a NetView operator to issue commands from the host NetView program to the SNAplus2 computer. (For a brief overview of NetView and RCF commands, see Section 10.1, Using the Host NetView Program.
Managing SNAplus2 from NetView Using the Host NetView Program 10.1.1 NetView Screen Display The layout of the NetView screen varies with different versions of NetView at different hosts. A typical layout is shown in Figure 10–1, Example of a NetView Screen. The display includes an input area at the bottom of the screen; this is the area into which you can type commands. The line ??? divides the main screen area (where NetView displays responses to your commands) from the input area.
Managing SNAplus2 from NetView Using SPCF The UCF daemon program running on the SNAplus2 computer associated with the service point name spname (for UCF commands) commandtext Supplies the text of the command being issued. For SPCF, this is a command issued to the SNAplus2 command-line administration program. For UCF, it is a command for the HP-UX operating system. For more information about the commands that can be used, see Section 10.2.
Managing SNAplus2 from NetView Using UCF administration program, in the same format as you would specify it to the snapadmin program on the HP-UX command line. Refer to HP-UX SNAplus2 Administration Command Reference for information about the syntax of administration commands and the parameters for individual commands. 10.2.
Managing SNAplus2 from NetView Using UCF to commands related to SNAplus2; subject to the restrictions in Section 10.3.2, Permitted Commands, any type of command can be issued. By using UCF, a remote operator can monitor activity on the SNAplus2 computer, diagnose problems, and in some cases take corrective action. You can specify whether SNAplus2 supports UCF by using the define_rcf_access command (refer to HPUX SNAplus2 Administration Command Reference).
Managing SNAplus2 from NetView Using UCF of the background command, but does not receive any subsequent output that is generated. Similarly, you can use UCF to start a daemon process, but you cannot see any output generated by the process.
Managing SNAplus2 from NetView Using UCF For each outstanding command (the one currently executing and any queued commands), the following message is displayed: = = = UNIX COMMAND CANCELLED = = = This message indicates that the HP-UX shell in which the command was running has been stopped. Further HP-UX commands can be issued as necessary. If a command starts a daemon process on the HP-UX computer, this process may not be stopped by ux-cancel.
Managing SNAplus2 Client/Server Systems IP Networking Requirements 11 Managing SNAplus2 Client/Server Systems SNAplus2 can operate as a standalone system with all SNA components and applications on a single HP-UX system, or can operate as part of a client/server domain. A client/server domain includes both servers (SNA nodes) and clients (which can access SNA connectivity through a server).
Managing SNAplus2 Client/Server Systems IP Networking Requirements 11.1.1 Setting Up IP Port Numbers SNAplus2 uses both TCP/IP and UDP/IP communications to send client/server data across the LAN. By default, it uses the port number 1553 for both types of communications. For most installations, this port number should be suitable; you do not need to change it.
Managing SNAplus2 Client/Server Systems Managing Win32 clients • The administration commands query_central_logger or query_node_all (these return the information that was available before the TCP/IP connection was dropped, and so may not match the current status of the LAN) • The NOF verbs query_central_logger or query_node_all (as for the equivalent administration commands) In particular, the TCP/IP connection is dropped if you enable the SNA software but do not start any SNAplus2 applications on the
Managing SNAplus2 Client/Server Systems Managing Win32 clients • Invokable TPs (APPC or CPI-C) that can run on the client The most commonly used parameters can also be modified using the Client Configuration Utility, which is the preferred method for modifying them. For more information, see Section 11.2.4, Win32 Client Configuration. 11.2.1 Enabling a Win32 Client The Win32 Client runs as a Windows service. The installation program configures it to start automatically when the computer starts.
Managing SNAplus2 Client/Server Systems Managing Win32 clients The Client Configuration Utility provides a simple way of modifying the most commonly used client configuration parameters, and is the preferred method for modifying these parameters. To use this program, run the Configuration Utility program, located in the SNAplus2 program group. The program displays the same Configuration window that was displayed in the initial install process.
Managing SNAplus2 Client/Server Systems Managing Win32 clients MSG_tracing file1 = msg_trace_filename_1 file2 = msg_trace_filename_2 flip_size = filesize truncation_length = length fmi = YES | NO CS_tracing file1 = cs_trace_filename_1 file2 = cs_trace_filename_2 flip_size = filesize admin_msg = YES | NO datagram = YES | NO data = YES | NO send = YES | NO receive = YES | NO Internal_tracing file1 = internal_trace_filename_1 file2 = internal_trace_filename_2 flip_size = filesize trace_level = nn trace_flushi
Managing SNAplus2 Client/Server Systems Managing Win32 clients • If you have not set up emulator user records for groups of users, this line of the file is optional. If the user name cannot be matched and no group name is specified, 3270 or 5250 users on the client can use the user record, if any, in the domain configuration file. • If the client will not be running 3270 or 5250 emulation, this line of the file is not required. invoked_tps The Registry data type of this value is REG_SZ.
Managing SNAplus2 Client/Server Systems Managing Win32 clients The Registry data type of this value is REG_DWORD. Specify the time in seconds that an application waits while the client starts and tries to contact a server. Values between 0 and 300 are valid; values outside this range are forced into the range. The default value is 10 seconds.
Managing SNAplus2 Client/Server Systems Managing Win32 clients Logging The Logging subkey specifies logging options for the client. These options can be used to specify client logging settings that override the logging options specified for the domain as a whole. For more information about specifying domain logging options, see Section 4.3, Configuring Logging. If central logging is enabled, all log messages are written to a central file on a server.
Managing SNAplus2 Client/Server Systems Managing Win32 clients Name of the backup error log file. When the error log file reaches the size specified in error_file_wrap_size, SNAplus2 copies its contents to the backup file (overwriting any existing file), then clears the error log file. This parameter is optional. If it is not specified, the default is bak.err. To log error and audit messages to a single file, specify the same file name for both this parameter and the backup_audit_file parameter.
Managing SNAplus2 Client/Server Systems Managing Win32 clients NO Use verbose logging: each message in the log file includes a full listing of the message header information, the message text string and parameters, and additional information on the cause of the log and any action required. This parameter is optional. If it is not specified, the default is taken from the previous set_global_log_type command issued to the master server (or set using the Motif administration program).
Managing SNAplus2 Client/Server Systems Managing Win32 clients truncation_length. This enables you to record the most important information for each message but avoid filling up the file with long messages. This parameter is optional. If it is not specified, SNAplus2 does not truncate messages (all the data from each message is written to the file). all_api The Registry data type of this value is REG_SZ. To trace messages for all APIs, set this parameter to YES.
Managing SNAplus2 Client/Server Systems Managing Win32 clients This parameter is optional. If it is not specified, the default is NO. If the all_api parameter is set to YES, this parameter is ignored, and MS messages are traced. MSG_tracing The MSG_tracing subkey specifies options for tracing on 3270 emulation programs. For more information about tracing, refer to HP-UX SNAplus2 Diagnostics Guide. The tracing options are specified as follows: file1 The Registry data type of this value is REG_SZ.
Managing SNAplus2 Client/Server Systems Managing Win32 clients The full path name of the trace file, or of the first trace file if tracing is to two files (see the description of the file2 parameter). This parameter is required if you want to enable client/server tracing; you also need to set the trace_flags parameter. file2 The Registry data type of this value is REG_SZ. The full path name of the second trace file.
Managing SNAplus2 Client/Server Systems Managing Win32 clients Internal_tracing The Internal_tracing subkey specifies options for tracing the internal operation of the client. For more information about tracing, refer to HP-UX SNAplus2 Diagnostics Guide. The tracing options are specified as follows: file1 The Registry data type of this value is REG_SZ. The full path name of the trace file, or of the first trace file if tracing is to two files (see the description of the file2 parameter).
Managing SNAplus2 Client/Server Systems Managing Win16 Clients To set these options in the registry for one or more applications, include a section in this format for each application, and replace the Appl_Name variable with the application program’s executable name (not including the .exe file name extension). For more information about CPI-C, refer to HP-UX SNAplus2 CPI-C Programmer’s Guide.
Managing SNAplus2 Client/Server Systems Managing Win16 Clients • 3270 Emulator Interface Specification For more information about Windows SNA APIs, see the documentation provided with Microsoft Host Integration Server. SNA network information, and other information required by Win16 clients, is held in the sna.ini file. On a Win16 client, the component that handles access to SNAplus2 servers is the network access process (NAP).
Managing SNAplus2 Client/Server Systems Managing Win16 Clients that is specific to Win16 clients. This file is stored in the directory where the Windows software was installed (typically c:\windows); it is set up during the client installation process, and is an ASCII text file that can be modified later as required using a standard text editor.
Managing SNAplus2 Client/Server Systems Managing Win16 Clients data = YES | NO send = YES | NO receive = YES | NO [Appl_Name] APPCTPN = tp_name APPCLLU = lu_name [CSV_data] CSVTBLG = table_G_filename Note The domain = domain_name line is the only required line in this file. The following sections explain the contents of the file. Where a parameter in the file takes the values YES or NO, any string beginning with Y or y is interpreted as YES, and any string beginning with N or n is interpreted as NO.
Managing SNAplus2 Client/Server Systems Managing Win16 Clients This client is used to run invoked TPs (APPC TPs that issue RECEIVE_ALLOCATE, or CPI-C applications that issue Accept_Conversation or Accept_Incoming). In this case, you may also need to define the TP on this client. For more information, see Section 7.4, Defining TPs or Appendix C, Configuring an Invokable TP from the Command Line. NO This client is not used to run invoked TPs. This line is optional. If it is not specified, the default is NO.
Managing SNAplus2 Client/Server Systems Managing Win16 Clients • In situations where the client cannot reach any servers using UDP broadcasts, and must use directed messages, specify the name of the first server it should try to contact. This applies in the following cases: • When the SNAplus2 LAN spans multiple TCP/IP subnets, and there are no SNAplus2 servers in any TCP/IP subnet that the client can access using UDP • When UDP support is not installed on the client.
Managing SNAplus2 Client/Server Systems Managing Win16 Clients log_directory The full path of the directory where log files are stored on this client. All the log files and backup log files (specified in the following parameters) are stored in this directory. This parameter is optional. If it is not specified, the files are stored in the Windows installation directory (typically c:\windows). error_file Name of the file to which error messages are written. This parameter is optional.
Managing SNAplus2 Client/Server Systems Managing Win16 Clients Specifies whether to use succinct logging or verbose logging in the error log file. This setting applies to both exception logs and problem logs. You can specify either of the following values: YES Use succinct logging: each message in the log file contains a summary of the message header information (such as the message number and log type) and the message text string and parameters.
Managing SNAplus2 Client/Server Systems Managing Win16 Clients truncation_length. This enables you to record the most important information for each message but avoid filling up the file with long messages. This parameter is optional. If it is not specified, SNAplus2 does not truncate messages (all the data from each message is written to the file). all_api To trace messages for all APIs, set this parameter to YES. In this case, SNAplus2 ignores the parameters from appc through nof.
Managing SNAplus2 Client/Server Systems Managing Win16 Clients The full path name of the trace file, or of the first trace file if tracing is to two files (see the description of the file2 parameter). This parameter is required if you want to enable message tracing; you also need to set the fmi parameter. file2 The full path name of the second trace file. This parameter is optional. To indicate that tracing is to one file instead of two files, do not include this line.
Managing SNAplus2 Client/Server Systems Managing Win16 Clients The maximum size of the trace file. If two file names are specified, tracing switches between the two files when the current file reaches this size. If only one file name is specified, this parameter is ignored; the file size is not limited. This parameter is optional. If it is not specified, the default is 100000 (bytes).
Managing SNAplus2 Client/Server Systems Managing HP-UX Clients If no applications on the client use this function, you do not need to include this section. The only option in this section is as follows: CSVTBLG The full path name of the file containing the user-defined Table G conversion table. This parameter is required if CSV applications need to perform Table G character conversion (there is no default); otherwise it is optional. 11.
Managing SNAplus2 Client/Server Systems Managing HP-UX Clients only if SNAplus2 logs error messages indicating that there is a port number clash with another program on the same computer. A client computer does not hold a copy of the domain configuration file or the SNA network data file; it holds only the information it needs to access servers on the SNAplus2 LAN, and relies on a server to provide the necessary configuration information.
Managing SNAplus2 Client/Server Systems Managing HP-UX Clients If the client uses the broadcast method to contact a server (specified by the * entry), this parameter specifies the maximum number of broadcasts to be made in one attempt to contact a server. The minimum value is 1; if a higher value is specified, the client retries every 10 seconds until it contacts a server or until this count is reached. If the count is reached without contacting a server, the client then attempts to contact a named server.
Managing SNAplus2 Client/Server Systems Defining Client TPs 11.5 Defining Client TPs For information about defining TPs on a SNAplus2 client system, see Section 7.4, Defining TPs or Appendix C, Configuring an Invokable TP from the Command Line.
Appendix AConfiguration Planning Worksheets AppendixA Configuration Planning Worksheets This appendix provides worksheets for configuring specific functions of SNAplus2. The worksheets summarize the basic configuration parameters needed to enable each function; for information about advanced configuration parameters, see the appropriate section in the body of this book, or refer to HP-UX SNAplus2 Administration Command Reference.
Appendix AConfiguration Planning Worksheets Motif Field Valid Entry/Notes Control point alias Up to 8 characters Node ID 8 hexadecimal digits Your Implementation Value Connectivity Configuration: See Section A.2, Connectivity Worksheets. Client/Server Configuration: Not required for a standalone node. Configuration server? Should the node act as a configuration server, to store information about domain resources in the SNAplus2 LAN? Application Configuration: See Section A.
Appendix AConfiguration Planning Worksheets Motif Field Valid Entry/Notes Control point name NETNAME.CPNAME (each 1–8 type A EBCDIC characters) Your Implementation Value To connect to a VTAM host, this name must match the NETID= and CPNAME= entries in the VTAM PU statement. Control point alias Up to 8 characters Node ID 8 hexadecimal digits Connectivity Configuration: See Section A.2, Connectivity Worksheets. Client/Server Configuration: Not required for a standalone node.
Appendix AConfiguration Planning Worksheets • Section A.2.1, SDLC • Section A.2.2, Token Ring • Section A.2.3, Ethernet • Section A.2.4, FDDI • Section A.2.5, QLLC (X.25) • Section A.2.6, Enterprise Extender (HPR/IP) A.2.1 SDLC Complete this worksheet to support connectivity using the SDLC link protocol.
Appendix AConfiguration Planning Worksheets Motif Field Valid Entry/Notes Physical link type Select modem type Dial string String for modem initialization (only for Smart Modem or V.25 switched incoming ports) Your Implementation Value SDLC Link Station Dialog Link station fields Name Up to 8 characters SNA port name Up to 8 characters Activation By administrator On node startup On demand LU traffic Any Independent only Dependent only Independent LU traffic Remote node NETNAME.
Appendix AConfiguration Planning Worksheets Motif Field Valid Entry/Notes Remote node ID 8 hexadecimal digits (optional) Downstream PU name 1–8 type A EBCDIC characters Upstream DLUS name NETNAME.LUNAME (each 1–8 type A EBCDIC characters) Your Implementation Value Contact information Poll address For switched incoming ports, only configured on the port.
Appendix AConfiguration Planning Worksheets Motif Field Valid Entry/Notes Your Implementation Value Token Ring Link Station Dialog Link station fields Name Up to 8 characters SNA port name Up to 8 characters Activation By administrator On node startup On demand LU traffic Any Independent only Dependent only Independent LU traffic Remote node NETNAME.
Appendix AConfiguration Planning Worksheets Motif Field Valid Entry/Notes Your Implementation Value Contact information MAC address Hexadecimal digits If the remote end of this link is a VTAM host, you can find its MAC address in the MACADDR= parameter of the VTAM Port definition. If you are configuring a link to an AS/400 system, the MAC address is the ADPTADR parameter in the Line Description.
Appendix AConfiguration Planning Worksheets Motif Field Valid Entry/Notes LU traffic Any Your Implementation Value Independent only Dependent only Independent LU traffic Remote node NETNAME.CPNAME (each 1–8 type A EBCDIC characters; optional) If the remote system is a VTAM host, you can find the network name (the first eight characters of the fully qualified name) in the NETID parameter of the VTAM start list. The last eight characters are in the SSCPNAME parameter of the VTAM start list.
Appendix AConfiguration Planning Worksheets Motif Field Valid Entry/Notes MAC address Hexadecimal digits Your Implementation Value If the remote end of this link is a VTAM host, you can find its MAC address in the MACADDR= parameter of the VTAM Port definition. If you are configuring a link to an AS/400 system, the MAC address is the ADPTADR parameter in the Line Description.
Appendix AConfiguration Planning Worksheets Motif Field Valid Entry/Notes Your Implementation Value Independent LU traffic Remote node NETNAME.CPNAME (each 1–8 type A EBCDIC characters; optional) If the remote system is a VTAM host, you can find the network name (the first eight characters of the fully qualified name) in the NETID parameter of the VTAM start list. The last eight characters are in the SSCPNAME parameter of the VTAM start list.
Appendix AConfiguration Planning Worksheets Motif Field Valid Entry/Notes MAC address Hexadecimal digits Your Implementation Value If the remote end of this link is a VTAM host, you can find its MAC address in the MACADDR= parameter of the VTAM Port definition. If you are configuring a link to an AS/400 system, the MAC address is the ADPTADR parameter in the Line Description.
Appendix AConfiguration Planning Worksheets Motif Field Valid Entry/Notes Remote node NETNAME.CPNAME (each 1–8 type A EBCDIC characters; optional) Your Implementation Value If the remote system is a VTAM host, you can find the network name (the first eight characters of the fully qualified name) in the NETID parameter of the VTAM start list. The last eight characters are in the SSCPNAME parameter of the VTAM start list.
Appendix AConfiguration Planning Worksheets Motif Field Valid Entry/Notes Enterprise Extender Port Dialog SNA port name Up to 8 characters Initially active Select if needed Local IP interface The identifier for the local network adapter card to be used for the IP link. Define on connection network Select if needed CN name NETNAME.
Appendix AConfiguration Planning Worksheets A.3 Passthrough Services Worksheets Complete worksheets for any of the passthrough services described in the following sections, if the service is to be supported by the local node: • Section A.3.1, DLUR on the Local Node • Section A.3.2, Passthrough DLUR for Downstream Nodes • Section A.3.3, PU Concentration • Section A.3.4, TN Server A.3.1 DLUR on the Local Node Complete this worksheet to support DLUR on the local node.
Appendix AConfiguration Planning Worksheets Motif Field Valid Entry/Notes Your Implementation Value Node Configuration: Configure the node as a network node (see Section A.1.1, APPN Network Node). Connectivity Configuration: See Section A.2, Connectivity Worksheets. Configure connectivity to the APPN network and also connectivity for dependent traffic to the downstream nodes. A.3.3 PU Concentration Complete this worksheet if the local node is to support PU concentration.
Appendix AConfiguration Planning Worksheets Motif Field Valid Entry/Notes TN3270 client address Specify one of the following: Support TN3270E • Default record (any TN3270 client) • TCP/IP address (dotted decimal address of client) • TCP/IP name or alias Your Implementation Value Select to support TN3270E (in addition to TN3270 and TN3287) TN3270 port and LUs TCP/IP port number Usually 23.
Appendix AConfiguration Planning Worksheets Motif Field Valid Entry/Notes Your Implementation Value Dependent LU parameters Host LS/DLUR PU Name of dependent link station to host or DLUR PU (must be defined before defining an LU) LU number 1–255 This value must match the LOCADDR parameter in the VTAM/NCP LU resource definition statement.
Appendix AConfiguration Planning Worksheets Motif Field Valid Entry/Notes COS name 1–8 type A EBCDIC characters Your Implementation Value Session limits Initial session limit Up to maximum session limit; recommended value is 8 Maximum session limit Up to 32767 Minimum contention winner sessions Up to maximum session limit; recommended value is 0. Minimum contention loser sessions Recommended value is 0.
Appendix AConfiguration Planning Worksheets Motif Field Valid Entry/Notes TP name User application: up to 64 ASCII characters Your Implementation Value Service TP: up to 8 hexadecimal digits Conversation level security required Select to require a valid user name and password on allocation requests Restrict access Select to require that user names be included on a security access list Security access list Name of security access list Conversation type Basic Mapped Either Sync level None Confi
Appendix AConfiguration Planning Worksheets Motif Field Valid Entry/Notes Mode Type A EBCDIC string Partner TP name User application: up to 64 characters Your Implementation Value Service TP: up to 8 hexadecimal digits Security None Same Program User ID Only for security level of Same or Program (not related to user login ID) Password Only for security level of Program (not related to user login password) A.4.3 5250 Complete this worksheet if the local node is to support 5250 communications.
Appendix AConfiguration Planning Worksheets Motif Field Valid Entry/Notes LU type 3270 model 2 (80x24) display 3270 model 3 (80x32) display 3270 model 4 (80x43) display 3270 model 5 (132x27) display 3270 Printer SCS Printer LU in pool Select desired option (only for display and unrestricted LUs).
Appendix AConfiguration Planning Worksheets Motif Field Valid Entry/Notes Number of sessions For multiple sessions only LU name For a single session LU/Pool name 1–8 type AE EBCDIC characters (for single or multiple display sessions) Your Implementation Value A.4.5 RJE Complete this worksheet if the local node is to support RJE communications with a host. Motif Field Valid Entry/Notes Your Implementation Value Node Configuration: See Section A.1, Node Worksheets.
Appendix AConfiguration Planning Worksheets Motif Field Valid Entry/Notes Your Implementation Value Node Configuration: See Section A.1, Node Worksheets. Connectivity Configuration: See Section A.2, Connectivity Worksheets (configure for dependent traffic).
Appendix BAPPN Network Management Using the Simple Network Management Protocol AppendixB APPN Network Management Using the Simple Network Management Protocol This appendix briefly introduces the Simple Network Management Protocol (SNMP), the SNMP components (manager, agent, subagent), the APPN Management Information Base (MIB), and the APPN SNMP subagent component of SNAplus2. B.
Appendix BAPPN Network Management Using the Simple Network Management Protocol B.2 SNAplus2 APPN SNMP Subagent SNAplus2 implements an SNMP subagent to provide support for the APPN MIB defined in RFC 1593. The subagent uses the services of the SNMPD daemon, which communicates with a management application using TCP/IP. The subagent supports receiving SNMP Get requests for a subset of the objects contained in the APPN MIB. The subagent does not support every object in the APPN MIB.
Appendix CConfiguring an Invokable TP from the Command Line AppendixC Configuring an Invokable TP from the Command Line SNAplus2 includes a command-line utility that enables a user or the writer of a TP installation program to define an invokable TP. You can run this utility on a server or client.
Appendix CConfiguring an Invokable TP from the Command Line C.1 File Format for an Invokable TP Definition The file that supplies configuration information for an invokable TP is an ASCII text file that can be modified using any standard text editor.
Appendix CConfiguring an Invokable TP from the Command Line combination of the two (for example, [<3f>"TP1"]). In this example, the first character is the unprintable character 0x3f, and the following characters are "TP1". SNAplus2 converts a supplied ASCII string to EBCDIC, but does not perform any conversion on a hexadecimal string (which is assumed to be in EBCDIC already). It then pads the name with EBCDIC spaces on the right (to a total of 64 characters) before matching against the specified TP name.
Appendix CConfiguring an Invokable TP from the Command Line • Ensure that the TP appends data to an existing file instead of creating the file (so that all copies of the TP append data to the same file) • Design the TP to generate file names at run-time, based on the process ID with which the TP is running (so that each copy of the TP writes to a different file). This line is optional. If it is not included, or if an invalid value is specified, the default is QUEUED.
Appendix CConfiguring an Invokable TP from the Command Line To indicate that the TP accepts incoming Attaches from any local LU, set this parameter to two double quotation mark characters, "", indicating a blank LU alias. If the invokable TP data file contains more than one entry for the same TP name, only one of these entries can specify a blank LU alias; each of the others must specify a different explicit LU alias.
Appendix CConfiguring an Invokable TP from the Command Line APPLICATION The TP executable is started as an application using the CreateProcess system call. SERVICE The TP executable is started as a service using the StartService system call. In this case, the service must have been previously installed with the Service Control Manager using the name specified by the SERVICE_NAME parameter.
Appendix DUsing SNAplus2 in a High Availability Environment AppendixD Using SNAplus2 in a High Availability Environment This appendix describes the high availability features of SNAplus2 and how it works with the HP MC/ServiceGuard product. D.1 What is High Availability? High availability is a term used to describe an environment in which mission critical applications are protected from severe impact of various failures.
Appendix DUsing SNAplus2 in a High Availability Environment program. Many software and hardware components deliver SNA network connectivity to the end user in this picture. Since the HP 9000 server plays such a critical role in maintaining the network connectivity for multiple end users, it is important to minimize the impact of component failures in and around the server.
Appendix DUsing SNAplus2 in a High Availability Environment Figure D–2 LU Pools Client Client Client Client LAN LU Pool A S800 Server S800 Server 3xxx Communications Controller IBM Host The LU pool gives you the ability to add a logical layer on top of the two servers. Clients access the SNA network by referring to the LU pool name, not to a specific LU in the pool. Within the SNAplus2 configuration above, the LU pool contains LUs associated with two LSs — one for each S800 server.
Appendix DUsing SNAplus2 in a High Availability Environment Figure D–3 Applications using multiple servers Client LAN S800 Server S800 Server 3xxx Communications Controller IBM Host The second way an application can use multiple servers is to have one SNAplus2 configuration that is used by multiple HP 9000 systems. For example, suppose two server systems are connected to an SNA network through Token Ring ports.
Appendix DUsing SNAplus2 in a High Availability Environment In this example, nine LUs are used by APPC production applications that run on the client systems. These LUs are configured to use an SNAplus2 LS called HALS. This LS is configured to use the SNAplus2 LAN port HAPORT and can be run under the SNAplus2 node HANODE. Normally, this configuration is run on the primary server hp_pr as shown below. In addition, five LUs are used by APPC transaction programs for development purposes.
Appendix DUsing SNAplus2 in a High Availability Environment Figure D–5 SNAplus2 on Primary and Backup Servers Client Client Client Client LAN Primary HP-UX Server hp_pri Backup HP-UX Server hp_back Development Configuration Temporarily Out of Service Node................DEVNODE LS....................DEVLS Port..................DEVPORT LUs..................DEVUO1...
Appendix DUsing SNAplus2 in a High Availability Environment Figure D–6 SNAplus2 environment with ServiceGuard Client Client Client Client LAN Standby client/server network links Active client/server network links Primary server S800 Server S800 Server Backup server Dual SNA network DLCs 3xxx Communications Controller IBM Host Some of the reasons that ServiceGuard works well with SNAplus2 in a high availability environment are as follows: 1.
Appendix DUsing SNAplus2 in a High Availability Environment make highly available. Identify at least two SNAplus2 servers that can provide SNA network connectivity in your ServiceGuard cluster. Consequently, if one server experiences a failure that prevents it from providing SNA network connectivity, another server can take over that role. Follow these steps to help you build your SNAplus2 package: 1. List all of the mission critical applications that use SNAplus2 for SNA network connectivity. 2.
Appendix DUsing SNAplus2 in a High Availability Environment Table D–2 Suggestions for Defining the SNAplus2 Package Item Suggestion Package Name Use a name that identifies how the SNAplus2 package is being used. For example, sna. Service Name Use the name of the SNAplus2 LS that you are making highly available. For example, HALS. Service Command This command will be used to monitor the SNAplus2 LS. Use the snapmon command which has been designed for this purpose.
Appendix DUsing SNAplus2 in a High Availability Environment Identifies which SNAplus2 LS is being monitored. interval Specifies the number of seconds that snapmon waits between attempts to obtain the status of the LS. If this parameter is not specified, snapmon will pause 5 seconds between queries. Any number between 1 and 3600 (inclusive) can be specified. retry_count Specifies how many times snapmon will allow the LS to be reported in a state other than active when snapmon is starting.
Appendix DUsing SNAplus2 in a High Availability Environment Figure D–7 SNAplus2 in Client/Server Configuration Client LAN client/server LAN connection Standby LAN adapter S800 Server 3xxx Communications Controller IBM Host SNAplus2 uses an internal mechanism to inform applications running on client systems about the IP addresses they should use to access each particular server.
Appendix DUsing SNAplus2 in a High Availability Environment Figure D–8 SNAplus2 Server connected to remote system via LAN HP 9000 Server Token Ring LAN 3xxx Communications Controller IBM Host For this type of communication, SNAplus2 communicates with the LAN driver using a Streams DLPI interface. Since ServiceGuard only supports local LAN failover for IP network traffic, SNAplus2 will not be able to take advantage of local LAN failover or floating IP addresses in this case.
Appendix DUsing SNAplus2 in a High Availability Environment Figure D–9 SNAplus2 Server Running TNServer TN3270 Client LAN TN Server LAN connection S800 Server 3xxx Communications Controller IBM Host Since TN3270 and TN Server communicate over a telnet (TCP/IP) connection, this connection can be maintained during a local LAN failover or can be quickly reestablished when the package is migrated to another server.
Appendix DUsing SNAplus2 in a High Availability Environment Figure D–10 Accessing SNAplus2 Server via LAN User Workstation LAN rlogin connection S800 Server 3xxx Communications Controller IBM Host D.3.6 Customizing the SNAplus2 Package Control Script The last step in defining an SNAplus2 package is customizing the Package Control Script to instruct ServiceGuard how to start and stop the SNAplus2 software associated with the package.
Appendix DUsing SNAplus2 in a High Availability Environment The run and halt commands must be designed to allow ServiceGuard to migrate the SNAplus2 package from the primary server to the backup server. If the SNAplus2 package fails on the primary server (which is indicated by the termination of the snapmon process), ServiceGuard will invoke the halt commands on the primary server. Most often the command, snap stop, is sufficient because that command will halt all of the SNAplus2 software.
Appendix DUsing SNAplus2 in a High Availability Environment D.3.7 I/O Compatibility Constraints The previous section described how to customize your Package Control Script for the best level of application transparency. To allow the same SNAplus2 node, port, and LS to run on multiple systems, it is important that they have compatible networking hardware.
Appendix DUsing SNAplus2 in a High Availability Environment Interface card. . . . . . . . . . [card0.......] The backup server should also be configured so that its X.25 card uses the name card0. That way, when ServiceGuard attempts to start the same configuration on the backup server, the card can be accessed by the expected name. Figure D–12 Client/Server Configuration Using X.
Appendix DUsing SNAplus2 in a High Availability Environment Figure D–13 Client/Server Configuration Using SDLC DLC Client Client Client Client LAN Primary HP-UX Server hp_pri Backup HP-UX Server hp_back PSI Adapter PSI Adapter Card 0 Card 0 Multi-drop Modem 3xxx Communications Controller IBM Host SNA connection over an IP-based network SNAplus2 can be configured over an IP-based network using the Enterprise Extender feature.
Appendix DUsing SNAplus2 in a High Availability Environment Figure D–14 ServiceGuard handling LAN card failure HP-UX Server Card 0 Card 1 IP Network IBM Host Node failure As shown in Figure D–15, ServiceGuard handling LAN card failure, ServiceGuard can migrate the floating IP address from the current node to the backup node in the cluster in the event of node failure. The Host will have to re-establish the connection to the floating IP address in this scenario.
Appendix DUsing SNAplus2 in a High Availability Environment D.4 Advanced Configuration Techniques The following advanced configuration techniques are useful in networks where there are multiple DLC (Data Link Control) types connecting one or more HP 9000 servers to the remote SNA system. For example, a standalone server might use a Token Ring LAN to communicate with the remote system, but have an SDLC DLC ready to use if the token ring is unavailable.
Appendix DUsing SNAplus2 in a High Availability Environment Note Some networking packages, like TCP/IP, support Continuous Availability during local failover; that is, applications do not experience outages while the system is switching from one network adapter to another. SNAplus2 does not support Continuous Availability during local failovers. Applications will experience session outages, and must re-establish LU-LU sessions with the remote SNA system after the switch has occurred.
Appendix DUsing SNAplus2 in a High Availability Environment while (( $exitcode == 0 )) do # # Attempt to start the node. If it is already active, # the command will have no effect. # snapadmin init_node # # Attempt to start the port. If it is already active, # the command will have no effect. # snapadmin start_port, port_name=TRPORT # # Attempt to start the LS. If the LS is configured to # be initially active, the command will have no effect.
Appendix DUsing SNAplus2 in a High Availability Environment Notice that this shell script uses the return code of snapmon to determine what action to take. If snapmon returns 0, the TRLS link station was active at some point while snapmon was running. If that is the case, it makes sense to simply attempt to restart the LS. If snapmon returns with a non-zero value, however, the LS failed to start for the entire initialization period (about 30 seconds).
Index 3270 emulation group additional configuration needs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 5250 emulation group parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 A Activation parameter . . . . . . . . . . . . . . Adapter card number parameter . . . . . . . . . Adapter/Port Number parameter . . . . . . . . . adjacent node . . . . . . . . . . . . . . . . administration responsibilities . . . . . . . . . . . . . . . tools . . . . . . . . . . . . . . . . .
branch network node . . . . . . . . worksheet . . . . . . . . . . . . connection network . . . . . . . . . control point . . . . . . . . . . . . description . . . . . . . . . . . . end node . . . . . . . . . . . . . worksheet . . . . . . . . . . . . example configuration . . . . . . . . functions . . . . . . . . . . . . . MIB . . . . . . . . . . . . . . . network . . . . . . . . . . . . . . on a token ring . . . . . . . . . route selection . . . . . . . . . .
managing . . . . . . . . . . . . . . . . . . . . network data file . . . . . . . . . . . . . . . . . networking requirements . . . . . . . . . . . . . . PATH parameter . . . . . . . . . . . . . . . . . SECURITY_TYPE parameter . . . . . . . . . . . . SERVICE_NAME parameter . . . . . . . . . . . . SHOW parameter . . . . . . . . . . . . . . . . . TIMEOUT parameter . . . . . . . . . . . . . . . TPname parameter . . . . . . . . . . . . . . . . TYPE parameter . . . . . . . . . . . . . . . . .
PU concentration . . . . . . . . . . . . . . . . . RJE workstations . . . . . . . . . . . . . . . . . security access list . . . . . . . . . . . . . . . . tasks . . . . . . . . . . . . . . . . . . . . . . TN server access records . . . . . . . . . . . . . . TN server association records . . . . . . . . . . . . TP . . . . . . . . . . . . . . . . . . . . . . . configuration server . . . . . . . . . . . . . . . . . adding . . . . . . . . . . . . . . . . . . . . . removing . . . . . . . . . . . . . . . . . . .
parameters Local LU . . . . . . . . . Local LU alias . . . . . . . Mode . . . . . . . . . . Name . . . . . . . . . . Partner LU . . . . . . . . Partner TP . . . . . . . . Password . . . . . . . . . Security . . . . . . . . . Use default LU . . . . . . User ID . . . . . . . . . CSV (Common Service Verb) API . CSVTBLG Win16 client . . . . . . . . . Win32 client . . . . . . . . . Customer Information Control System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Display LU assigned parameter . . . . . . Display LU parameter . . . . . . . . . . Display parameter . . . . . . . . . . . . DLC additional configuration needs . . . . . . configuration . . . . . . . . . . . . . parameters . . . . . . . . . . . . configuration methods . . . . . . . . . description . . . . . . . . . . . . . types supported . . . . . . . . . . . . DLUR additional configuration needs . . . . . . configuration . . . . . . . . . . . . . description . . . . . . . . . . . . .
E EN (end node) ( See end node ) enabling the SNA software HP-UXclient . . . . . . . . . . . . . . . . . enabling the SNAplus2 software on a server . . . . . . . . . . . . . . . . . problems during initialization . . . . . . . . . . Win16 client . . . . . . . . . . . . . . . . . Win32 Client . . . . . . . . . . . . . . . . end node APPN . . . . . . . . . . . . . . . . . . . description . . . . . . . . . . . . . . . . . directory . . . . . . . . . . . . . . . . . . in sample APPN network . . . . . . . . . .
H help command-line administration program . . Motif administration program . . . . . high availability failures . . . . . . . . . . . . . . features . . . . . . . . . . . . . . in client/server configuration . . . . . what is . . . . . . . . . . . . . . high-level language application programming ( See HLLAPI ) High-Performance Routing (HPR) ( See HPR ) HLLAPI . . . . . . . . . . . . . . host . . . . . . . . . . . . . . . . host communication example configuration . . . . . . . .
K kernel components, tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . kernel memory limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L LAN access timeout . . . . . . . . . . . . . LAN tracing on a client . . . . . . . . . . . . . . . . LEN node description . . . . . . . . . . . . . . . directory . . . . . . . . . . . . . . . . features . . . . . . . . . . . . . . . . . worksheet . . . . . . . . . . . . . . . . Line details parameter . . . . . . . . . . . .
parameters Host LS/DLUR PU . . . . LU alias . . . . . . . . LU name . . . . . . . . LU number . . . . . . . Member of default pool . . Local LU alias parameter . . . . Local LU name parameter . . . Local LU parameter . . . . . . local node LU . . . . . . . . . . . Local node ID parameter . . . . Local SAP number parameter . . local topology database . . . . . locating resources . . . . . . . Location parameter . . . . . . log files configuring . . . . . . . . types . . . . . . . . . . . log messages . . . .
viewing . . . . . . . . . LU traffic parameter . . . . . LU type 0-3 . . . . . . . . . . 6.2 . . . . . . . . . . . LU type parameter . . . . . LU types 0–3 additional configuration needs configuration methods . . . parameters Host LS/DLUR PU . . . LU in pool . . . . . . LU name . . . . . . . LU number . . . . . . LU type . . . . . . . Pool name . . . . . . LU-LU session . . . . . . . LU/Pool name parameter . . . LUA API . . . . . . . . . . configuration . . . . . . . pool configuration . . . . . worksheet .
additional configuration needs . . . . configuration parameters . . . . . . . . . . using Motif . . . . . . . . . . using the command line . . . . . description . . . . . . . . . . . parameters Auto-activated sessions . . . . . COS name . . . . . . . . . . Initial session limit . . . . . . . Initial window size . . . . . . . Maximum RU size . . . . . . . Maximum session limit . . . . . Maximum window size . . . . . Minimum contention loser sessions . Minimum contention winner sessions Name . . . . . . . . .
version numbers . . . . . . . network management . . . . . . . . . mixed . . . . . . . . . . . topology database . . . . . . . types . . . . . . . . . . . . network access process (NAP) . . . network accessible unit (NAU) . . . network addressable unit . . . . . network data file . . . . . . . . client . . . . . . . . . . . . description . . . . . . . . . HP-UXclient . . . . . . . . . network management data . . . . network node directory . . . . . . . . . . sample configuration . . . . .
configuration methods . . . . . . multiple, defining with wildcards . . parameters Alias . . . . . . . . . . . . Location . . . . . . . . . . Partner LU name . . . . . . . Supports parallel sessions . . . Uninterpreted Name . . . . . . Wildcard partner LU name . . . remote node, defining . . . . . . Partner LU name parameter . . . . . Partner LU parameter . . . . . . . Partner TP parameter . . . . . . . passthrough DLUR . . . . . . . . passthrough services configuring . . . . . . . . . . description . . . .
parameters Adapter card number . . . . . . . . . . . . CN name . . . . . . . . . . . . . . . . . Configure downstream LUs for implicit PU access Define on connection network . . . . . . . . . Ethernet type . . . . . . . . . . . . . . . HPR supported on implicit links . . . . . . . . Initially active . . . . . . . . . . . . . . . Line details . . . . . . . . . . . . . . . . Link level error recovery on implicit links . . . . Local IP interface . . . . . . . . . . . . . Local SAP number . . . . . . . . . . .
( See RCF ) remote computer . . . . . . . . . . . . . remote job entry (RJE) . . . . . . . . . . . remote node additional configuration needs . . . . . . . configuration methods . . . . . . . . . . defining . . . . . . . . . . . . . . . . LU . . . . . . . . . . . . . . . . . Node’s SNA network name parameter . . . . partner LU . . . . . . . . . . . . . . Remote node ID parameter . . . . . . . . . Remote node name parameter . . . . . . . . Remote node role parameter . . . . . . . . .
SDLC DLC . . . . . . . . . . . . . . . . port configuration . . . . . . . . . . . worksheet . . . . . . . . . . . . . . secondary LU . . . . . . . . . . . . . security APPC . . . . . . . . . . . . . . . conversation . . . . . . . . . . . . . session . . . . . . . . . . . . . . . UCF . . . . . . . . . . . . . . . . security access list additional configuration needs . . . . . . configuration methods . . . . . . . . . parameters Name . . . . . . . . . . . . . . Users in access list . . . . . . . . . purpose .
layers . . . . . . . . network . . . . . . . . network data file . . . . description . . . . . HP-UX client . . . . HP-UXclient . . . . Win16 client . . . . network information Win32 client . . . . network types . . . . . subarea . . . . . . . . SNA port name parameter . sna.ini file . . . . . . . . sna_clnt.net file . . . . . . snap2adm program . . . . snapadmin program . . . . SNAplus High Availability . SNMP agent . . . . . . . . . Get request . . . . . . manager . . . . . . . overview . . . . . . .
Support TN3270E parameter . . . Supports parallel sessions parameter Sync level parameter . . . . . . . synchronous data link control (SDLC) ( See SDLC ) system services control point (SSCP) T target TP . . . . . . . . . . . task sheets . . . . . . . . . . . TCP/IP port number parameter . . . TDU (topology database update) . . telnet (TN) ( See TN server ) terminal . . . . . . . . . . . . terminal controller . . . . . . . .
APPC definition parameters Conversation level security required . . . Conversation type . . . . . . . . . . PIP allowed . . . . . . . . . . . . . Restrict access . . . . . . . . . . . . Security access list . . . . . . . . . . Sync level . . . . . . . . . . . . . TP name . . . . . . . . . . . . . . client . . . . . . . . . . . . . . . . . configuration purpose . . . . . . . . . . . . . . . configuration methods . . . . . . . . . . description . . . . . . . . . . . . . . invocation parameters . . . . . . . .
U UCF access to files . . . . . . . canceling a command . . . . command syntax . . . . . . daemon program . . . . . . description . . . . . . . . output . . . . . . . . . . permissions . . . . . . . . permitted commands . . . . sample command . . . . . . security . . . . . . . . . . user . . . . . . . . . . . user name . . . . . . . . . using . . . . . . . . . . . valid commands . . . . . . UDP/IP communications . . . . Uninterpreted Name parameter . .
audit_file . . . . . . . . . . audit_file_wrap_size . . . . . . audit_logging_enabled . . . . . backup_audit_file . . . . . . . backup_error_file . . . . . . . broadcast_attempt_count . . . . client/server tracing information . configuration information . . . . CPI-C application data . . . . . cpic . . . . . . . . . . . . csv . . . . . . . . . . . . CSV application data . . . . . CSVTBLG . . . . . . . . . data . . . . . . . . . . . . datagram . . . . . . . . . . disabling . . . . . . . . . . domain . . . .
APPCTPN . . . . . . . . audit_file . . . . . . . . . audit_file_wrap_size . . . . . audit_logging_enabled . . . . backup_audit_file . . . . . . backup_error_file . . . . . . broadcast_attempt_count . . . client/server tracing information client_start_timeout . . . . . configuration information . . . CPI-C application data . . . . cpic . . . . . . . . . . . csv . . . . . . . . . . . CSV application data . . . . CSVTBLG . . . . . . . . data . . . . . . . . . . . datagram . . . . . . . . . disabling . . . . .
Emulator Users and Sessions . . . . . . LU Pools . . . . . . . . . . . . . . menus . . . . . . . . . . . . . . . Node . . . . . . . . . . . . . . . . resource . . . . . . . . . . . . . . resource items . . . . . . . . . . . . RJE Workstations . . . . . . . . . . . tool bar buttons . . . . . . . . . . . Windows APIs . . . . . . . . . . . . . . . . clients . . . . . . . . . . . . . . . Windows Open Systems Architecture (WOSA) worksheets . . . . . . . . . . . . . . . Workstation name parameter . . . . . . . .
