HP-UX SNAplus2 Administration Guide Edition 2 J2740-90013 HP 9000 Networking E1098 Printed in: United States © Copyright 1998 © Hewlett-Packard Company, 1998.
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. Warranty.
©copyright 1980, 1984, 1986 Novell, Inc. ©copyright 1986-1992 Sun Microsystems, Inc. ©copyright 1985-86, 1988 Massachusetts Institute of Technology. ©copyright 1989-93 The Open Software Foundation, Inc. ©copyright 1986 Digital Equipment Corporation. ©copyright 1990 Motorola, Inc.
Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Prerequisite Knowledge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 About This Book. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 Organization of This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 Typographic Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents APPN Control Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Locating Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Session Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Accessing Subarea Networks from APPN Networks . . . . . . . . . . . . . . . 64 2. Introduction to SNAplus2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Specifying the Path to SNAplus2 Programs . . . . . . . . . . . . . . . . . . . .111 Enabling SNAplus2 Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112 Disabling SNAplus2 Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113 Using the Motif Administration Program . . . . . . . . . . . . . . . . . . . . . . .115 Invoking the Motif Administration Program . . . . . . . . . . . . . . . . . . .115 Resource Windows . . . . . . . . . . . . . . . . . . . . . .
Contents Defining DLUR PUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 DLUR PU Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . 164 Additional Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 6. Configuring Dependent LUs Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Defining LU Types 0–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Mode Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196 Additional Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199 Defining CPI-C Side Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200 CPI-C Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . .200 Additional Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203 Configuring APPC Security. . .
Contents Additional Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Configuring DLUR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 10. Managing SNAplus2 from NetView Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Using the Host NetView Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . NetView Screen Display . . . . . . . . . . . . . . . . . . . . . . .
Contents Disabling SNAplus2 for a Win32 Client . . . . . . . . . . . . . . . . . . . . . . .255 Win32 Client Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256 Win32 Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257 Managing Win16 Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275 Enabling a Win16 Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents CPI-C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5250 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3270 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LUA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Specifying a Package IP Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . .371 Customizing the SNAplus2 Package Control Script . . . . . . . . . . . . .376 I/O Compatibility Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .378 Advanced Configuration Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . .382 Writing Your Own SNAplus2 Service Script . . . . . . . . . . . . . . . . . . .
Contents 14
Preface The HP-UX SNAplus2 Administration Guide provides information on enabling, configuring, and managing SNAplus2. 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. Organization of This Book This book is organized as follows: Chapter 1, “SNA Terms and Concepts.
Explains how to configure connectivity for the SNAplus2 node. Chapter 6, “Configuring Dependent LUs.” Explains how to configure dependent LUs (logical units) for LU types 0–3 and LU pools. Chapter 7, “Configuring APPC Communication.” Explains how to configure APPC (advanced program-to-program communications). Chapter 8, “Configuring User Applications.” Explains how to configure user applications. Chapter 9, “Configuring Passthrough Services.
Typographic Conventions The typographic styles used in this document are shown in Table 1. Table 1 Typographic Conventions Special Element Sample of Typography Emphasized words back up files before deleting Document title HP-UX SNAplus2 Administration Guide File or path name /usr/spool/uucp/myfile.
Special Element Sample of Typography Hexadecimal value 0x20 Environment variable PATH Function, call, or entry point ioctl Programming verb GET_LU_STATUS Operating System Conventions For UNIX This heading is used to indicate the start of a section of text that applies only to the HP-UX operating system. For Windows This heading is used to indicate the start of a section of text that applies to the Win32 client, which runs on the Microsoft NT (Version 3.
HP-UX SNAplus2 General Information Provides an introduction to SNAplus2 and explains key product concepts and features.
Explains how to enable, configure, and manage SNAplus2. This guide provides information about SNA concepts, and an overview of the features provided by SNAplus2. It describes how to configure and manage SNAplus2 using the Motif administration program and provides guidance for users of the SNAplus2 command-line administration program.
Contains the information you need to write application programs using the Common Service Verbs (CSV) application program interface (API). HP-UX SNAplus2 MS Programmers Guide Contains the information you need to write applications using the Management Services (MS) API. HP-UX SNAplus2 NOF Programmers 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.
1 SNA Terms and Concepts 23
SNA Terms and Concepts Overview Overview This chapter defines Systems Network Architecture (SNA) terms and concepts that are important to understanding and using SNAplus2. For information about SNAplus2 and its capabilities, see Chapter 2, “Introduction to SNAplus2.” If you are already familiar with SNA and SNAplus2, you can begin with Chapter 3, “Administering SNAplus2.” This chapter is divided into the following parts: • “Systems Network Architecture” provides a definition of SNA.
SNA Terms and Concepts Systems Network Architecture Systems Network Architecture Systems Network Architecture (SNA) is an IBM data communication architecture that specifies common conventions for communicating among a wide variety of hardware and software data communication products. This architecture consists of two kinds of definitions: formats that define the layout of messages exchanged by network components, and protocols that define the actions that network components take in response to messages.
SNA Terms and Concepts Basic SNA Concepts Basic SNA Concepts SNA defines the standards, protocols, and functions used by devices—from mainframes to terminals—to enable them to communicate with each other in SNA networks. SNA functions are divided into a hierarchical structure of separate layers, each performing a specific set of functions.
SNA Terms and Concepts Basic SNA Concepts Each node manages its end of the network communication paths, and uses SNA protocols to communicate with the node at the other end of each path. Because subarea networks and peer networks define the relationships among nodes differently, they also use different terms for node types (to describe the roles that nodes play in the network).
SNA Terms and Concepts Basic SNA Concepts 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. A host is a type 5 node.
SNA Terms and Concepts Basic SNA Concepts Figure 1-1 SNA Subarea Network 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.
SNA Terms and Concepts Basic SNA Concepts Node Types in a Peer Network Peer networks do not classify nodes hierarchically, as is done in a subarea network. Exchanges with other nodes are not controlled by a host or other centralized processor. Instead, any node can establish communication with any other node. A peer network is composed of type 2.1 nodes.
SNA Terms and Concepts Basic SNA Concepts Each node connected to a network has one or more link stations, which are the hardware and software in a node that control data flow to a specific adjacent node. To establish communication between two adjacent nodes, one of the link stations must first activate the link between the nodes. Transaction Programs Programs that exchange information across the SNA network are called transaction programs (TPs).
SNA Terms and Concepts Basic SNA Concepts • CPI-C (Common Programming Interface for Communications)—LU type 6.
SNA Terms and Concepts Basic SNA Concepts NOTE On type 2.1 nodes (which can be APPN nodes), the control point provides PU services in addition to providing other services (see “Control Points”). Two type 2.1 nodes (such as SNAplus2 nodes) can communicate directly, without requiring the services of a host to establish communications. Logical Units Each SNA node contains one or more logical units (LUs). An LU provides a set of functions that are used by TPs and end users to provide access to the network.
SNA Terms and Concepts Basic SNA Concepts For example, LU 3 can support an application program running under Customer Information Control System (CICS) and sending data to an IBM 3262 printer attached to an IBM 3174 Establishment Controller. LU 2 (for 3270 displays) LU 2 supports application programs and display workstations communicating in an interactive environment using the SNA 3270 data stream. Type 2 LUs also use the SNA 3270 data stream for file transfer.
SNA Terms and Concepts Basic SNA Concepts Operating System) use LU 0. Current releases of these products also support LU 6.2 communication, which is the preferred protocol for new applications. NOTE For information about the data streams used by SNA logical units, refer to Systems Network Architecture Technical Reference. Control Points A control point (CP) is an NAU that manages network resources within its domain, controlling resource activation, deactivation, and status monitoring.
SNA Terms and Concepts Basic SNA Concepts In a subarea network, the CP on an SNA node acts as a type 2.0 PU. It communicates with an SSCP on a host and does not communicate with other CPs in the subarea network. When participating in an APPN network, the CP exchanges network control information with the CPs in adjacent nodes. The CP can also function as an independent LU of type 6.2. The CP acts as the default LU for TPs on the local node.
SNA Terms and Concepts Basic SNA Concepts Before an SSCP-LU session can be established, the PU controlling the LU must have an active SSCP-PU session with an SSCP on a type 5 node. The SSCP-PU session is used to pass control data and network management data between the PU and SSCP. CP-CP sessions In an APPN network, adjacent nodes establish CP-CP sessions. These sessions are used to search for a resource in the APPN network and to maintain topology information (see “APPN Control Point”).
SNA Terms and Concepts Basic SNA Concepts dependent LU requester (DLUR) function enables session traffic from dependent LUs to flow over APPN networks. For more information about DLUR, see “Accessing Subarea Networks from APPN Networks”. A dependent LU on a peripheral node is always the secondary LU. • An independent LU can establish sessions with other independent LUs without the aid of an SNA host. LU 6.2 is the only LU type that can be independent.
SNA Terms and Concepts Basic SNA Concepts Figure 1-2 Multiple and Parallel Sessions Conversations This section applies to LU 6.2 only. Once a session is established between two LUs, the LU-LU session supports the exchange of information between two TPs, which have the exclusive use of the session to execute a transaction. This exchange of information is called a conversation.
SNA Terms and Concepts Basic SNA Concepts As shown in Figure 1-3, “Communication between Transaction Programs and Logical Units,” information is exchanged between TPs and LUs to enable one node to communicate with another. Although the TPs appear to be communicating directly, the LUs on each node are the intermediaries in every exchange. Figure 1-3 Communication between Transaction Programs and Logical Units SNA defines two types of conversations: basic and mapped.
SNA Terms and Concepts Basic SNA Concepts A logical record consists of a two- or four-byte header starting with a two-byte length field, often represented as “LL,” followed by up to 32,765 bytes of data. Logical records can be grouped together and sent as a block, transmitting more than one logical record with a single call to the SEND function.
SNA Terms and Concepts Basic SNA Concepts Class of Service Class of service (COS) is a definition of the transport network (data link control and path control) characteristics—such as route security, transmission priority, and bandwidth—that the local node can use to establish a particular session. The COS definition assigns relative values to factors such as acceptable levels of security, cost per byte, cost per connect-time, propagation delay, and effective capacity.
SNA Terms and Concepts Basic APPN Concepts Basic APPN Concepts Advanced Peer-to-Peer Networking (APPN) is a network architecture that supports distributed network control. It makes networks easy to configure and use, provides centralized network management, and supports flexible connectivity. An APPN network is composed of type 2.1 nodes. Each node in the network is connected by a link to at least one other node in the APPN network.
SNA Terms and Concepts Basic APPN Concepts • Network nodes (see “APPN Network Nodes”) • End nodes (see “APPN End Nodes”) In addition, low-entry networking (LEN) nodes can be connected to an APPN network, but they do not use APPN features (see “LEN Nodes”). A sample APPN network that includes all of these node types is shown in Figure 1-4, “Portion of a Sample APPN Network.
SNA Terms and Concepts Basic APPN Concepts One of the APPN network nodes (NNA) also participates in a subarea network, connecting to a host through a communication controller. This node functions as an APPN node when communicating with nodes in the APPN network, and as a peripheral node when communicating with nodes in the subarea network. Through this network node, LU type 6.2 LUs on other nodes in the APPN network can establish LU-LU sessions with LU type 6.2 LUs on the host.
SNA Terms and Concepts Basic APPN Concepts An APPN end node can be attached to multiple network nodes (see EN3 in Figure 1-4, “Portion of a Sample APPN Network,”) but it can have CP-CP sessions active with only one network node at a time—its network node server. The other network nodes can be used only to provide intermediate routing for the end node or as substitute network node servers if the main network node server becomes unavailable.
SNA Terms and Concepts Basic APPN Concepts APPN Control Point An APPN control point is a set of functions that manages node resources and supports both physical unit and logical unit functions on a type 2.1 node. An APPN CP directs local node functions (such as activating and deactivating adapters and links), provides directory and topology information, and assists LUs in session initiation and termination.
SNA Terms and Concepts Basic APPN Concepts When setting up a workstation, you must define the CP name. The CP is also an LU that can support user sessions, and it can be the only LU defined in your workstation, if you so choose. Locating Resources To support communication between TPs, SNAplus2 first establishes a session between the logical units that control those TPs.
SNA Terms and Concepts Basic APPN Concepts reside on the LEN node's network node server. The LEN node establishes sessions with LUs on its network node server. The network node routes the session through the APPN network to the proper node in the network. A LEN node can also use wildcards in a directory entry to specify multiple partner LUs that can be accessed over a specific link. • An APPN end node maintains a directory that includes its own LUs.
SNA Terms and Concepts Basic APPN Concepts Figure 1-5 LEN Node Directory To establish a session with an LU on a node that is not directly attached, Node LEN1 sends an LU-LU session activation (BIND) request to its network node server (Node NNA). The server automatically locates the destination LU and forwards the BIND. NOTE In this example, Node LEN1 can establish a session with LU1 on Node EN1 through its network node server, NNA.
SNA Terms and Concepts Basic APPN Concepts Figure 1-6 End Node Directory 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. Network Node Directories. A network node provides distributed directory services to the end nodes it serves. An example of a network node directory is shown in Figure 1-7, “Network Node Directory.
SNA Terms and Concepts Basic APPN Concepts Figure 1-7 Network Node Directory A network node locates a remote LU as follows: 1. The network node receives a request to locate an LU. The request can be any of the following: • The name of a destination LU sent by an end node or a LEN node to its network node server • An LU name specified in a LOCATE search request from an end node • An LU name specified in a BIND request from a LEN node • An LU name specified by a TP on the network node 2.
SNA Terms and Concepts Basic APPN Concepts An APPN end node can also receive (and respond to) LOCATE search requests from its network node server to search for, or confirm the continued presence of, specific LUs in the end node. Each APPN end node registers its LUs with its network node server by sending the network node a registration message. In this way, the network node maintains current directory information for the end nodes in its domain. A LEN node cannot register LUs with its network node server.
SNA Terms and Concepts Basic APPN Concepts network backbone topology—the nodes and transmission groups that can be used for routing sessions between any pair of nodes in the network. In addition, the topology database on each network node contains local information about transmission groups from that network node to adjacent end nodes or LEN nodes.
SNA Terms and Concepts Basic APPN Concepts Figure 1-8 Network Topology Database in Network Nodes The shared network topology database is duplicated at Nodes NNA, NNB, NNC, and NND.
SNA Terms and Concepts Basic APPN Concepts 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. End nodes include information only for links to adjacent nodes. For example, Node EN2 includes information about Link f to Node NNB and Link i to Node EN3. Topology Database Updates.
SNA Terms and Concepts Basic APPN Concepts • If the session partner is not on an adjacent node, the network node server for the LU requesting the session uses the network topology database to identify network nodes and intermediate transmission groups in the route to the session partner.
SNA Terms and Concepts Basic APPN Concepts data. In ISR, once a session route has been established, all data on that session uses the same route. If part of the route fails, the session ends. • In automatic network routing (ANR), available in network nodes that support APPN's High-Performance Routing (HPR) function, intermediate network nodes can dynamically reroute session traffic if part of the route fails. ANR does not provide intermediate session pacing or segmentation and reassembly.
SNA Terms and Concepts Basic APPN Concepts Figure 1-9 APPN Network Using a Shared-Access Transport Facility If Node EN1 has a link definition for each of the links in the network, it can establish a direct link to any node. The link definitions needed to support direct links between Node EN1 and every other node in the APPN network are shown in Figure 1-10, “Definitions Needed for Direct Links from Node EN1 to Every Node in an APPN Network.
SNA Terms and Concepts Basic APPN Concepts Figure 1-10 Definitions Needed for Direct Links from Node EN1 to Every Node in an APPN Network If all of the nodes in the network are to support direct links to every other node, a total of 30 link definitions are needed on the six nodes in this example. In general, the number of link definitions can be calculated as n × (n−1), where n is the number of nodes in the network. In a larger network, the number of link definitions quickly becomes unwieldy.
SNA Terms and Concepts Basic APPN Concepts only a single link to an adjacent network node server and a link to the connection network, instead of configuring every possible link to every node. To use the connection network feature, an APPN network must meet the following conditions: • The nodes in the APPN network must be linked using switched media such as token ring or Ethernet (see “DLCs”). • All of the links in the APPN network must use the same media.
SNA Terms and Concepts Basic APPN Concepts Figure 1-11 Definitions Needed for Direct Links Using a Virtual Node To support direct links between any two end nodes in the APPN network, a total of ten link definitions is required. (Each end node needs two link definitions: one to a network node server and one to the virtual node.
SNA Terms and Concepts Basic APPN Concepts 3. The server normally selects the direct link between two end nodes as the optimal route for the LU-LU session. It provides the node with the primary LU the information it needs to establish a dynamic link to the node with the partner LU. 4. The end nodes can then establish an LU-LU session without the need for intermediate session routing.
SNA Terms and Concepts Accessing Subarea Networks from APPN Networks 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.
2 Introduction to SNAplus2 65
Introduction to SNAplus2 Overview Overview 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.
Introduction to SNAplus2 What Is SNAplus2? What Is SNAplus2? SNAplus2 is a software product that enables HP-UX computers to participate in an SNA network that includes mainframes, PCs, and other HP-UX computers. With SNAplus2, you can access data and programs that reside on other computer systems, thereby increasing your computing power.
Introduction to SNAplus2 What Is SNAplus2? Within a TCP/IP local area network (LAN), SNAplus2 supports communication between servers (SNA nodes) and clients (HP-UX or Windows computers). For more information about client/server facilities on a LAN, see “Client/Server Support”. Windows clients SNAplus2 provides support for Windows clients (running Windows 3.11, Windows for Workgroups, Windows 95, and Windows NT), enabling them to access SNA resources through SNAplus2 servers.
Introduction to SNAplus2 Example Configurations Example Configurations SNAplus2 can be used as a standalone system to support direct communication with a host or another SNA node, within a LAN to support SNA communications across the LAN, or as a gateway to support communication between a host and systems in a LAN.
Introduction to SNAplus2 Example Configurations Figure 2-2 SNAplus2 Nodes in an APPN Network In Figure 2-3, “SNAplus2 Node Providing PU Concentration and DLUR,” 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 Example Configurations Figure 2-3 SNAplus2 Node Providing PU Concentration and DLUR 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 Example Configurations Figure 2-4 SNAplus2 Node Configured for TN Server A network that includes SNA nodes (SNAplus2 servers) and non-SNA computers (SNAplus2 clients) is shown in Figure 2-5, “SNAplus2 Client/Server Configuration.” The clients can access SNA resources through the servers.
Introduction to SNAplus2 Example Configurations Figure 2-5 SNAplus2 Client/Server Configuration 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.
Introduction to SNAplus2 SNAplus2 Components SNAplus2 Components The components of SNAplus2 and their relationships are shown in Figure 2-6, “Components of SNAplus2.” Figure 2-6 Components of SNAplus2 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 Node Components A server running SNAplus2 implements an SNA node. It can also provide passthrough services between an SNA host and computers in an APPN or TCP/IP network. SNA Support SNAplus2 provides SNA node type 2.0 and 2.1 (LEN node) support for communicating with host and peer computers; it also implements an APPN node, providing end node function. SNAplus2 implements an APPN node to communicate with other nodes on the SNA network.
Introduction to SNAplus2 SNAplus2 Components Figure 2-7 PU Concentration The downstream computer must contain an SNA PU type 2.0 or 2.1 to support dependent LUs. For example, the downstream computer could be a PC running Microsoft SNA Server for Windows NT, or another SNAplus2 computer. When the local SNAplus2 node uses the PU concentration feature, all the data transferred between the host and the downstream computer is routed through the local node.
Introduction to SNAplus2 SNAplus2 Components at the downstream computers are configured as part of the resources of the SNAplus2 computer. The host computer is not aware that PU concentration is being used. 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.
Introduction to SNAplus2 SNAplus2 Components NOTE This guide uses the term TN3270 for information that applies equally to the TN3270, TN3287, and TN3270E protocols. SNAplus2 TN server provides access to 3270 host computers for TN3270 users on other computers. TN server enables TN3270 users to share a host connection with SNAplus2 or with other TN3270 users, instead of requiring a direct link. TN server also enables TN3270 users to access hosts that are not running TCP/IP.
Introduction to SNAplus2 SNAplus2 Components SNAplus2 TN server supports all TN3270 client emulation programs that correctly implement the protocols defined in RFCs 1123, 1576, 1646, and 1647. When a TN3270 program communicates with TN server, SNAplus2 identifies the program by the TCP/IP address of the computer where the TN3270 program is running. SNAplus2 cannot distinguish between two different TN3270 programs being used by different users on the same computer.
Introduction to SNAplus2 SNAplus2 Components Refer to the HP-UX SNAplus2 3270/3179G Users Guide for information about using the 3270 emulation software to communicate with a host. For more information about configuring support for 3270 emulation, see Chapter 8, “Configuring User Applications.” 5250 Emulation Using 5250 emulation software, you can log on to and use AS/400 systems from your computer.
Introduction to SNAplus2 SNAplus2 Components The users of an RJE workstation can define workstation style files to supplement the SNAplus2 configuration and to control the operation of the workstation. Refer to the HP-UX SNAplus2 RJE Users Guide for information about using RJE to submit jobs to a host and about setting up the workstation style file.
Introduction to SNAplus2 SNAplus2 Components APPC API 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. The APPC API includes TP server support, enabling applications to have greater control over starting transaction programs (TPs) and distributing conversations to those TPs.
Introduction to SNAplus2 SNAplus2 Components • If the TP is operator-started (not started automatically by SNAplus2), and the use of the TP does not need to be restricted, you do not need to define any additional resources. The only exceptions are when you want to do the following: • Change the default timeout for a RECEIVE_ALLOCATE issued by the TP. • Specify that the TP is a broadcast queued TP (which means that incoming conversation requests can be routed dynamically to the TP wherever it is running).
Introduction to SNAplus2 SNAplus2 Components For more information, refer to the HP-UX SNAplus2 3270 & TN3270 HLLAPI Programmers Guide or HP-UX SNAplus2 3270/3179G Users Guide. LUA API The LUA API enables application programmers to write applications that communicate with host applications at the request unit and response unit (RU) level, and to send and receive data on both the SSCP-LU session and the PLU-SLU session. This API can be used to support LU 0, 1, 2, or 3 communication with the host.
Introduction to SNAplus2 SNAplus2 Components • Windows CPI-C • Windows LUA • Windows CSV • 3270 Emulator Interface Specification For more information about Windows SNA APIs, see the documentation provided with Microsoft SNA Server. End of Section Client/Server Support Computers running SNAplus2 can be configured to communicate using client/server protocols.
Introduction to SNAplus2 SNAplus2 Components 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). Information about the configuration of domain resources for the complete SNAplus2 LAN is held in a domain configuration file.
Introduction to SNAplus2 SNAplus2 Components In a domain with multiple SNAplus2 servers, one server holds the master copy of the SNAplus2 domain configuration file. This server is known as the master server. You can define other servers on the LAN to be backup servers. The domain configuration file is copied to backup servers—either when they are started, or when the master copy is changed—so that all backup servers hold a copy of the latest information.
Introduction to SNAplus2 SNAplus2 Components preserved when the connection is re-established, do not make any changes to the file in either domain while the LAN connection is broken. Changes can still be made to the configuration of individual nodes. SNAplus2 stores information about the master server and backup servers in the file sna.net, known as the SNA network data file.
Introduction to SNAplus2 SNAplus2 Components End of Section Windows Clients For Windows SNAplus2 enables machines running Microsoft Windows 3.1, Windows for Workgroups 3.11, Windows 95, Windows NT, and OS/2 to act as clients in the SNAplus2 domain. You can run either a 16-bit version of the SNAplus2 client software (referred to in this guide as “Win16”) or a 32-bit version (referred to in this guide as “Win32”): • The 16-bit version can be installed on machines running Windows 3.
Introduction to SNAplus2 SNAplus2 Resources SNAplus2 Resources The resources of the SNAplus2 system can be divided into the following types: • Node resources define the communications capabilities of a particular APPN node. The following are node resources: • Connectivity resources including the following: • DLCs • Ports • Link stations • Connection networks • Session resources including the following: • LUs (types 0–3 for 3270, RJE, and LUA communications, and type 6.
Introduction to SNAplus2 SNAplus2 Resources NOTE Some of the resources listed here do not appear in the Motif administration program, or are presented differently. These differences are indicated in the following sections where they apply. Connectivity Resources Connectivity to remote systems is supported by the following resources: • DLCs (see “DLCs”). If you use the Motif administration program to configure a port, the corresponding DLC definition is created automatically.
Introduction to SNAplus2 SNAplus2 Resources NOTE In the Motif administration program, DLCs are not shown directly. The information required for configuring a DLC is displayed as part of the configuration of a port owned by the DLC. Ports A port represents the local end of a communications link as a unique access point in the network. In general, this corresponds to a single physical access point such as an adapter card.
Introduction to SNAplus2 SNAplus2 Resources The local node can have an explicit link station defined for its communication path to another node on the SATF, but enabling communications between every pair of nodes on the SATF requires a large number of link station definitions, and results in a large volume of network topology information flowing on the network.
Introduction to SNAplus2 SNAplus2 Resources Session Resources The following session resources are used by SNAplus2: • Logical units (see “Logical Units”) • Modes and their associated classes of service (see “Modes and Classes of Service”) • Directory information (see “Directory Information”) Logical Units An LU is the node's point of contact with a user program (3270 emulation program, RJE workstation, APPC TP, CPI-C application, or LUA application).
Introduction to SNAplus2 SNAplus2 Resources With DDDLU, LUs do not have to be configured statically at the host. (You must still define dependent LUs on the SNAplus2 node.) This reduces the initial configuration required at the host, and makes later expansion easier. SNAplus2 can communicate with both DDDLU-capable and non-DDDLU-capable hosts, with no difference in the configuration required.
Introduction to SNAplus2 SNAplus2 Resources Default LUs. If you are configuring type 6.2 dependent LUs for use with APPC or CPI-C applications, you may wish to define them as members of the default pool. The default pool can include LUs from more than one node. An application that does not specify a particular local LU is assigned an unused LU from the pool of default LUs.
Introduction to SNAplus2 SNAplus2 Resources Domain Resources Information about domain resources such as 3270 users, RJE workstations, access to the remote command facility, CPI-C side information, and logging levels may be needed anywhere in the network. For this reason, only one definition is required for each such resource .
Introduction to SNAplus2 SNAplus2 Administration SNAplus2 Administration As the SNAplus2 administrator, you are responsible for installing the SNAplus2 software and for managing its resources. Before beginning SNAplus2 administration, you must understand the main features of the SNAplus2 product. This section describes the administration tasks you must perform and the tools you can use to perform them. Administration Responsibilities To administer the SNAplus2 system, you need to do the following: Step 1.
Introduction to SNAplus2 SNAplus2 Administration Administration Tools SNAplus2 provides a range of tools for administering the system. Depending on your requirements, you may not need to use all of them. This section summarizes the functions provided by each of these tools. NOTE This document provides general information about SNAplus2 administration, which you can perform using any of the tools described in this section.
Introduction to SNAplus2 SNAplus2 Administration • Querying the configuration of defined resources and their current status if they are active • Deleting resources The Motif administration program can be used to manage both node resources (for any server on the LAN, as long as the SNAplus2 software is running on that server) and domain resources. For each type of communications (such as 3270 or APPC), the program guides you in setting up the configuration of the required resources.
Introduction to SNAplus2 SNAplus2 Administration The other SNAplus2 administration tools, including command-line configuration, and NOF application programs, provide access to a wider range of configuration parameters and options than those shown in the Motif administration program. In most cases, however, you can perform all needed configuration from the Motif administration program, because it exposes the key fields you need to configure and hides the fields that most users should not modify.
Introduction to SNAplus2 SNAplus2 Administration • snapadmin -h -d commandprovides detailed help for the named command, including a list of the configuration parameters that can be specified with the command. Refer to the HP-UX SNAplus2 Administration Command Reference for more information.
Introduction to SNAplus2 SNAplus2 Administration The sna_domn.cfg file contains information about SNAplus2 domain resources (resources not associated with a particular local node). The master copy of this file resides on the master server. Invokable TP data file The sna_tps file contains information that SNAplus2 needs to start invokable (target) TPs, and can also provide other information (such as the level of security required to access the TP). This file resides on the computer where the TPs run.
Introduction to SNAplus2 SNAplus2 Administration For more information about this file, refer to the HP-UX SNAplus2 Administration Command Reference. Client network data file The sna_clnt.net file contains information about how to access SNAplus2 servers, required by a client computer. This text file resides on the client computer. You can modify the contents of this file using a standard ASCII text editor. For more information about this file, refer to the HP-UX SNAplus2 Administration Command Reference.
Introduction to SNAplus2 SNAplus2 Administration Refer to the HP-UX SNAplus2 NOF Programmers Guide for more information. Diagnostic Tools SNAplus2 provides several diagnostics tools to help you diagnose and correct problems encountered during SNAplus2 operation: • Any component detecting a problem or an exception (an abnormal condition that may indicate the cause of a problem) writes an entry to an error log file. In addition, all significant system events can be recorded in an audit log file.
Introduction to SNAplus2 SNAplus2 Administration • Using command-line utilities, you can filter trace files to extract or interpret specific information or to produce a summary of message flows. The resulting output files can be viewed using a standard ASCII text editor such as vi. • SNAplus2 can generate alerts and send them to the NetView program at a host computer.
3 Administering SNAplus2 107
Administering SNAplus2 Overview Overview The first step in administering SNAplus2 is configuring the node and its resources. Begin by planning for configuration as described in “Planning for SNAplus2 Configuration”. Before you can configure SNAplus2, you must enable the SNAplus2 software as described in “Enabling and Disabling SNAplus2 on the Local System”. When SNAplus2 is enabled, you can run the Motif administration program (see “Using the Motif Administration Program”).
Administering SNAplus2 Planning for SNAplus2 Configuration Planning for SNAplus2 Configuration Before you make any configuration changes it is very important to plan thoroughly. Changes that you make can cause disruption, not only to the users of your local node but possibly to users all around the network. You may find it useful to draw a diagram of any changes that you are making to the topology of the network.
Administering SNAplus2 Planning for SNAplus2 Configuration Task Sheets The online help screens in the Motif administration program contain task sheets that provide guidance for specific configuration tasks. The task sheets contain pointers to all of the help screens for the dialogs that you will use to enter the configuration information. You can use these to browse the help and see exactly what data you must collect.
Administering SNAplus2 Enabling and Disabling SNAplus2 on the Local System Enabling and Disabling SNAplus2 on the Local System 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. For UNIX This section explains how to enable and disable the SNAplus2 software on a HP-UX server or client.
Administering SNAplus2 Enabling and Disabling SNAplus2 on the Local System Enabling SNAplus2 Servers This section describes how to enable SNAplus2 on a computer that was installed as a server (that is, with the SNA node components installed). If you are enabling SNAplus2 on a client, see “Enabling SNAplus2 on HP-UX Clients”. You must enable SNAplus2 on the local system before you can configure or manage the local node (either locally or from a remote SNAplus2 node).
Administering SNAplus2 Enabling and Disabling SNAplus2 on the Local System tracing.) Tracing enables you to diagnose problems that occur during startup. If you do not use this option, tracing is inactive at all interfaces; you can then activate it on specific interfaces as required, using the command-line administration program snapadmin. Tracing on all interfaces degrades the performance of SNAplus2 components.
Administering SNAplus2 Enabling and Disabling SNAplus2 on the Local System 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 Using the Motif Administration Program The Motif administration program provides a user-friendly interface for configuring SNAplus2. This program is the recommended tool for administering SNAplus2, because it guides you through the configuration process and minimizes the information you need to provide to create a workable configuration. You can also use the Motif administration program to manage the SNAplus2 system while it is active.
Administering SNAplus2 Using the Motif Administration Program In a client/server environment, SNAplus2 displays the Domain window. For a standalone system, SNAplus2 displays the Node window. NOTE This guide uses the term window to describe Motif windows that display information about SNAplus2 resources. A window can contain one or more sections, or panes. A dialog is a Motif window on which you can enter information.
Administering SNAplus2 Using the Motif Administration Program You can easily access other windows from this menu. These windows include the following: • Emulator Users and Sessionswindow • RJE Workstations window • LU Pools window • CPI-C Destination Names window Depending on the resources you select and the options you choose, the administration program can present additional resource windows, configuration dialogs, or status logs.
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 When you select a node to be administered, SNAplus2 displays the Node window as shown in Figure 3-2, “Node Window.” (For a standalone system, SNAplus2 does not display the Domain window, because the domain has only one node. Instead, SNAplus2 immediately displays the Node window when you start the administration program.
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. The Node box in the top-right corner of the Node window indicates whether the node is Active or Inactive.
Administering SNAplus2 Using the Motif Administration Program The body of the Node window is split into the following panes for the different types of resources for the node: Connectivity pane The top pane of the Node window lists connectivity resources for the node, including ports, link stations or PUs on each port, and dependent LUs on a specific link station or PU. For each resource, this window shows current status information.
Administering SNAplus2 Using the Motif Administration Program Select the resource and click on the Start or Stop button. (Alternatively, you can select Start item or Stop item from the Selection menu.) Add a resource for an item Select the item and click on the New button (or select New from the Selection menu). For example, to add a link station for a port, select the port and click on the New button.
Administering SNAplus2 Using the Motif Administration Program list of associated link stations is shown or hidden. Similarly, link stations with a list of associated LUs can be expanded to show the LUs, or contracted to hide them. A parent resource must always be configured before its child resources, and deleting the parent resource causes all its child resources to be deleted too. Tool Bar Buttons Resource windows include tool bar buttons to make it easy to perform common functions.
Administering SNAplus2 Using the Motif Administration Program Many resources, such as ports and link stations, cannot be modified while they are active. You can, however, view an active resource's parameters by selecting the resource and clicking on the Zoom button to open its dialog, or click on the Status button to view detailed status information for the resource. Resource Dialogs Resource dialogs show the current configuration information for the resource.
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 Most dialogs provide a Description field; the information you enter there is displayed on the window where the resource is displayed. Press the Done button when you are finished, or the Cancel button to exit without changing the configuration for the resource. For context-sensitive help on the dialog, click on the Help button.
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. 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 ASCII Administration Program ASCII Administration Program A menu-based ASCII administration program is available for character-based terminals. The ASCII interface provides a subset of all functions availailable through the Motif Administration Program and can be used for configuration and management of SNAplus2. The ASCII program is used through the HP ObAM environment.
Administering SNAplus2 Using the Command-Line Administration Program 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.
Administering SNAplus2 Using the Command-Line Administration Program The remainder of this section summarizes administration commands for different types of resources. Some of the types of commands listed are as follows: status_* Provides summary information for types of resources. define_* Creates a new define_* record in the configuration file, or replaces an record for the same resource with the new definition. delete_* Removes the corresponding define_* record from the file.
Administering SNAplus2 Using the Command-Line Administration Program 132 Chapter 3
4 Basic Configuration Tasks 133
Basic Configuration Tasks Overview Overview 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.
Basic Configuration Tasks Configuring Client/Server Functions 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). Many resources, such as ports and LUs, are configured on an individual node. These are known as “node resources.” Other resources, such as emulator user definitions, are common to all nodes; only one definition for the resource is maintained for the entire domain.
Basic Configuration Tasks Configuring Client/Server Functions NOTE You cannot directly indicate which node acts as the master server; the master server is selected based on the order in which nodes are added to the configuration server list. If you wish to move a server to the top of the list, remove all other nodes from the list and then add them again. In the Motif administration program Domain window, you can add a configuration server by selecting Make configuration server from the Selection menu.
Basic Configuration Tasks Configuring the Node Configuring the Node The first step in configuring SNAplus2 on a system is to configure the local node. Node configuration provides the basic information that the node needs in order to participate in an APPN network. You must configure the node before you can define connectivity or other resources for the node. If the node has already been configured, you must stop the node before changing the node configuration.
Basic Configuration Tasks Configuring the Node 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.
Basic Configuration Tasks Configuring Logging Configuring Logging SNAplus2 writes log messages describing abnormal events (and, optionally, normal events) to log files. When you try to diagnose a problem, the first place to look is in the log files, because the log messages provide information about the cause of the problem and the action you should take.
Basic Configuration Tasks Configuring Logging If your favorite editor is installed on the server, you can use it to view the log files. If not, you can use the standard HP-UX system utilities: pg View a file one page at a time. This utility is simple and easy to use but useful only if the log file is small. tail View the tail (end) of a file. The end of the file is where the most recent log messages are. Use this utility with the -f option to monitor the log file while the system is running.
Basic Configuration Tasks Configuring Logging The Logging dialog in the Motif administration program affects log settings throughout the domain. Using the command line, you can override the domain settings by configuring local log settings on a particular machine. In addition to providing control over logging, the Motif administration program provides node-level control over tracing. The command-line interface provides greater control over both logging and tracing functions.
Basic Configuration Tasks Configuring Logging 142 Chapter 4
5 Defining Connectivity Components 143
Defining Connectivity Components Overview Overview 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 Overview and they must be configured on the adjacent nodes as well as on the SNAplus2 node, so you may need to consult your SNA network planner. Operating as an APPN Node If the SNAplus2 node is an end node in an APPN network, the number of links that you need to configure can be greatly reduced. You can configure links to one or more adjacent network nodes and access all nodes in the APPN network using these links.
Defining Connectivity Components Overview For information about configuring PU concentration, see “Configuring PU Concentration”.
Defining Connectivity Components Defining Ports, DLCs, and Connection Networks Defining Ports, DLCs, 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.25 or QLLC (qualified logical link control) You can configure more than one port that uses a particular link protocol.
Defining Connectivity Components Defining Ports, DLCs, and Connection Networks Select Connectivity and New port from the Services menu on the Node window. Command-line administration program To configure a port: define_type_port To configure a DLC: define_type_dlc In these commands, type indicates the link protocol type (sdlc, tr, ethernet, fddi, qllc).
Defining Connectivity Components Defining Ports, DLCs, and Connection Networks This field applies only if the adapter card can support more than one port. This field is not used for SDLC or QLLC ports. Initially active Whether to activate the port automatically when the node is started. This setting enables link stations that use the port to be activated in response to requests from adjacent nodes or on demand by the local node.
Defining Connectivity Components Defining Ports, DLCs, 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 Ports, DLCs, and Connection Networks Select NRZ (typically used in the U.S.) or NRZI (typically used in Europe) for the encoding used on your SDLC line. This value must match the encoding scheme used by the modem at the remote end of the link. If you set this field incorrectly, you will find that the frames being received are all discarded and do not appear in any trace. On a VTAM host, this is the NRZI= setting in the LINE/GROUP definition.
Defining Connectivity Components Defining Ports, DLCs, and Connection Networks Consult your SNA network planner if you do not know how to configure any of these parameters. Additional Port Parameters for Token Ring, FDDI and Ethernet Local SAP number The address of the SAP, usually 04. Use a different value only if you need to use more than one SAP on the card. The SAP number must be a multiple of 4. If you do not know what value to enter for this field, contact your SNA network planner.
Defining Connectivity Components Defining Ports, DLCs, 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 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 the local node. This dynamically created link station appears in the connectivity section of the Node window for the duration of the connection. To configure a link station, use one of the following methods: Motif administration program Select Connectivity and New link station from the Services menu on the Node window.
Defining Connectivity Components Defining Link Stations Common Link Station Parameters The following parameters are required for all link stations, whether they support dependent traffic, independent traffic, or both. For more information about the parameters on this dialog, refer to the online help or to HP-UX SNAplus2 Administration Command Reference. Name A name to identify the link station locally. SNA port name The port that is to be used to access the adjacent node.
Defining Connectivity Components Defining Link Stations The type of LU traffic to flow over the link. This choice determines what other parameters are needed for link definition. Any 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 “Parameters for Independent LU Traffic” and “Parameters for Dependent LU Traffic”, in addition to those described in this section.
Defining Connectivity Components Defining Link Stations • If you are configuring a primary switched outgoing link station, and you do not know the poll address of the remote secondary with which you wish to communicate, you can specify a poll address of 0xFF on the primary. This value enables the node to accept responses from a secondary, regardless of the poll address it has configured. 0xFF is not a valid address for a nonprimary link or a link that is not switched outgoing.
Defining Connectivity Components Defining Link Stations 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 If you do not know what value to use, consult your SNA network planner. If the remote end of this link is a VTAM host, the SAP number is the SAPADDR= parameter of the VTAM PU definition. If you are configuring a link to an AS/400 system, the MAC address is the ADPTADR parameter in the Line Description. Additional Link Station Parameters for X.25 (QLLC).
Defining Connectivity Components Defining Link Stations Parameters for Independent LU Traffic You need the following information to configure this link station for use by independent LUs (LUs of type 6.2 for use by APPC, 5250, or CPI-C applications): Remote node name The fully qualified CP name of the remote node. 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 command.
Defining Connectivity Components Defining Link Stations slightly, so if you do know the type it is better to specify it. This also helps to ensure network configuration consistency. You cannot choose Discover if the link station is activated on demand. If the local node is a LEN node, this field does not apply. Parameters for Dependent LU Traffic Configuring a link station for dependent LU traffic automatically creates an appropriate PU with the same name as the link station.
Defining Connectivity Components Defining Link Stations CP name of the remote node, but for remote nodes that do not send their CP name when activating a link, the remote node ID must be used instead. If you do not specify the remote node ID, the node ID of the remote node is not checked when the link is activated. Remote node role The role of the remote (adjacent) node: Host The link station supports dependent LUs (such as 3270 LUs) that are used for sessions with a host computer (the most common case).
Defining Connectivity Components Defining DLUR PUs Defining DLUR PUs Normally, a dependent LU session requires a direct communications link to the host computer. If many nodes (including a host node) are connected together in an APPN network, some of them may not have a direct connection to the host, but only an indirect connection through another node. It is not possible to establish dependent LU sessions to the host from LUs in these indirectly connected nodes.
Defining Connectivity Components Defining DLUR PUs For each DLUR PU on the local node, specify a PU name. The name does not need to match the PU name configured on the host. DLUS Name The fully qualified LU name of the host LU that supports DLUS. In order to use DLUR, the DLUR component of SNAplus2 has to establish an LU-LU session with the DLUS on the host. Contact your SNA network planner to determine the name of the host LU.
Defining Connectivity Components Defining DLUR PUs Whether the DLUR PU is to be activated automatically after a failure (once the cause of the failure has been remedied). Additional Configuration After configuring DLUR, continue with the following configuration tasks: • To configure LUs for DLUR, see “Defining DLUR PUs”. • To configure other passthrough services, see Chapter 9, “Configuring Passthrough Services.” • To support specific user applications, see Chapter 8, “Configuring User Applications.
6 Configuring Dependent LUs 167
Configuring Dependent LUs Overview Overview This chapter provides instructions for configuring LUs and LU pools to support user applications that use 3270, TN3270, RJE and 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 “Configuring the Node”. • Configure connectivity as described in Chapter 5, “Defining Connectivity Components.
Configuring Dependent LUs Defining LU Types 0–3 Defining LU Types 0–3 You must configure dependent LUs of types 0–3 to support communication with a host system. You can use the information in this section to define an LU to support 3270, RJE, or LUA. You can also define a range of LUs, to configure multiple LUs of the same type in a single operation.
Configuring Dependent LUs Defining LU Types 0–3 The link station that provides the link to the host. The LU definition belongs to the link station you select. (If the dependent LU resides on a node that supports DLUR, this field identifies the DLUR PU that provides connectivity to the host.) LU numbers An LU number or range of LU numbers. LU numbers can be from 1–255. The LU numbers must correspond to those in the host VTAM configuration.
Configuring Dependent LUs Defining LU Types 0–3 Whether the LU is assigned to an LU pool. Only printer, display, and unrestricted (unknown) LUs can be members of a pool. Pool name The name of the LU pool. 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, for RJE, or for LUA, define the LU pool as described in “Defining LU Pools”.
Configuring Dependent LUs Defining LU Pools Defining LU Pools For 3270, TN3270, RJE,and LUA, you can define LU pools to simplify user configuration and provide greater flexibility in establishing host sessions. For example, you can define several 3270 LUs in a single LU pool, then configure multiple 3270 sessions using this LU pool. This makes configuring the 3270 sessions easier and enables any 3270 session to use any LU in the pool.
Configuring Dependent LUs Defining LU Pools 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. Assigned LUs LUs to be assigned to the pool. An LU can only be a member of one pool. RJE LUs cannot be used as members of a pool.
Configuring Dependent LUs Defining LU Pools 174 Chapter 6
7 Configuring APPC Communication 175
Configuring APPC Communication Overview Overview 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 Overview Step 1. Define a local LU as described in “Defining Local LUs”. Step 2. Define a remote node as described in “Defining Remote Nodes”. Step 3. Define a partner LU as described in “Defining Partner LUs”. Step 4. Define an invokable TP as described in “Defining TPs”. Step 5. Define a mode as described in “Defining Modes and Classes of Service”. Step 6. Define CPI-C side information as described in “Defining CPI-C Side Information”. Step 7.
Configuring APPC Communication Defining Local LUs Defining Local LUs In many cases, applications can use the local node's control point LU, which is automatically defined when you configure the node. This is the default LU—if your application does not specify a particular LU, it can use this one. If the application uses the default LU, you do not need to define a local LU. Check the documentation for your APPC application, or contact the application programmer.
Configuring APPC Communication Defining Local LUs Command-line administration program Issue the following command: define_local_lu You can use the advanced dialog to specify sync point support, attach routing characteristics, restrictions on SSCP access, and security. Local LU Configuration Parameters The following parameters are required for local LU configuration: LU name The LU name of the local LU. If you do not know what name to use, consult your SNA network planner.
Configuring APPC Communication Defining Local LUs • To define a remote node, see “Defining Remote Nodes”. • To define a partner LU, see “Defining Partner LUs”. • To define an invokable TP, see “Defining TPs”. • To define a mode, see “Defining Modes and Classes of Service”. • To define CPI-C side information, see “Defining CPI-C Side Information”. • To define APPC security, see “Configuring APPC Security”. • To configure 5250 communication, see “Configuring User Applications”.
Configuring APPC Communication Defining Remote Nodes Defining Remote Nodes You must define a remote node (and the partner LUs on the node) in the following situations: • If the local node is a LEN node, you must define all of the remote nodes and any partner LUs on the remote node with which it communicates using APPC. A LEN node is not able to dynamically locate partner LUs; the remote node definition enables it to do so.
Configuring APPC Communication Defining Remote Nodes defined a remote node and SNAplus2 establishes CP-CP sessions with it, the entry is temporarily converted into a dynamic one. You should correct the fault by deleting the remote node definition when the node is inactive. To configure a remote node, use one of the following methods: Motif administration program Select APPC and New remote node from the Services menu on the Node window.
Configuring APPC Communication Defining Partner LUs Defining Partner LUs If both the local node and the remote node are end nodes or network nodes and your application uses an LU name to refer to the partner LU, there is no need to define the partner LU, because it can be dynamically located using APPN. If both nodes are end nodes or network nodes, but your application uses an LU alias to refer to its partner LU, you should add a partner LU alias definition.
Configuring APPC Communication Defining Partner LUs 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. This name must match the name that is configured at the remote node for this LU. If you do not know what that name is, consult your SNA network planner. 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 Partner LUs A locally displayable alias for the partner LU. You do not have to specify an LU alias if there is no local application that refers to the partner LU using an LU alias. This field applies when you define partner LU on a specific remote node or when you define a partner LU alias. Uninterpreted Name The uninterpreted name used by dependent local LUs when requesting the host to start an LU-LU session between the partner LU and the local LU.
Configuring APPC Communication Defining Partner LUs Additional Configuration After performing the partner LU configuration, continue with the following configuration tasks: • To define an invokable TP, see “Defining TPs”. • To define a mode, see “Defining Modes and Classes of Service”. • To define CPI-C side information, see “Defining CPI-C Side Information”. • To define APPC security, see “Configuring APPC Security”. • To configure 5250 communication, see “Configuring User Applications”.
Configuring APPC Communication Defining TPs Defining TPs This section explains how to define an APPC TP. In most cases, you do not need to define TPs that run on the SNAplus2 system; but you do need to configure a TP definition in the following cases: APPC Characteristics If the TP on the SNAplus2 computer is the invoking TP (or source TP—the TP that starts the APPC conversation) and you do not need to restrict access to the TP, you do not need to define the TP.
Configuring APPC Communication Defining TPs 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.) SNAplus2 uses the invokable TP definition for the following purposes: • When a TP issues Receive_Allocate, SNAplus2 searches for an invokable TP definition with the appropriate TP name.
Configuring APPC Communication Defining TPs The configuration methods for servers and clients are different: • On a server, use either of the following methods: Motif administration program Select APPC and Transaction Programs from the Services menu on the Node window. When SNAplus2 displays the TP window, select the top pane and click on the Add button, or select an existing invokable TP definition and click on the Zoom button. Command-line administration program Issue the snaptpinstall command.
Configuring APPC Communication Defining TPs The local LU alias from which the TP is to accept incoming Attaches. This name must match the name of a local APPC LU on the SNAplus2 node. If you do not specify an LU alias, the TP accepts incoming Attaches from any local LU. This field applies only if you specify that the parameters for this TP definition are for invocation on any LU. You can define multiple TPs that have the same TP name, provided each TP definition specifies a different LU alias.
Configuring APPC Communication Defining TPs about the TP is broadcast to all servers on the LAN; if an LU on another computer receives an incoming Allocate request and has no routing information configured, it can dynamically locate the TP and route the Allocate request to it. Using this option avoids having to configure explicit routing information on LUs, and enables load-balancing by running more than one copy of the same TP on different computers.
Configuring APPC Communication Defining TPs The TP is started in the home directory associated with this user ID. This home directory is also the default path for trace files and any other files accessed by the TP (unless the application overrides it by specifying a full path).
Configuring APPC Communication Defining TPs Select this option if an allocation request must include a valid user name and password (or an indicator that the password has already been verified). If you do not select this option, no verification is required. Restrict access Select this option if the user name must be included on a security access list. This field applies only if the Conversation level security required option is selected.
Configuring APPC Communication Defining Modes and Classes of Service Defining Modes and Classes of Service A mode specifies a set of characteristics that a local LU (LU type 6.2) uses to communicate with its partner LU. These characteristics include information about the way data is transmitted between the two LUs (such as maximum RU lengths and pacing window sizes), and about whether the LUs can establish parallel sessions.
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 #INTER #INTER Sessions used by interactive applications #BATCHSC #BATCHSC Sessions used by batch-processing applications, with a minimal level of routing security #INTERSC #INTERSC Sessions used by i
Configuring APPC Communication Defining Modes and Classes of Service Command-line administration program To define a mode, issue the following command: define_mode To change the default mode, issue the following command: define_defaults To define a class of service, issue the following command: define_cos Mode Configuration Parameters The following parameters are required for mode configuration: Name The name of the mode you are defining. The mode name is a string of 1–8 characters.
Configuring APPC Communication Defining Modes and Classes of Service This field is usually set to the same value as the initial session limit. If you are in doubt, consult your SNA network planner or APPC application developer (or for a third-party application, the product documentation). Minimum contention winner sessions The number of sessions (up to the session limit) that SNAplus2 must reserve for use by the local LU as the contention winner.
Configuring APPC Communication Defining Modes and Classes of Service 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. Maximum window size The maximum number of request units (RUs) that the local LU can receive before it must send a pacing response to the remote LU.
Configuring APPC Communication Defining Modes and Classes of Service The lower limit can be 0 or a value from 256 through the upper limit you specify. If the value in this field is different from the RU size defined for the remote node, the size used for a session with that node can be negotiated to establish an appropriate RU size for the session. The actual value cannot be lower than the lower limit field.
Configuring APPC Communication Defining CPI-C Side Information 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 Specify this option to use a member of the default pool (if one exists) or the node control point LU (if no default pool is defined). If the APPCLLU environment variable is set, the local LU information you supply is ignored, and the LU specified for the environment variable is used instead. Partner LU Either an alias or the fully qualified partner LU name for conversations initiated by local TPs using this side information.
Configuring APPC Communication Defining CPI-C Side Information Same The partner TP uses security, but accepts verification by the local TP of the user ID and password provided by the initiating TP. If you choose a security level of Same, you also need to specify a valid user ID that is accepted by the partner TP. Program The partner TP requires a User ID and password. If you choose a security level of Program, you need to specify a valid user ID and password that are accepted by the partner TP.
Configuring APPC Communication Defining CPI-C Side Information Additional Configuration After performing the CPI-C configuration, continue with the following configuration tasks: • To define APPC security, see “Configuring APPC Security”. • To configure 5250 communication, see Chapter 8, “Configuring User Applications.
Configuring APPC Communication Configuring APPC Security Configuring APPC Security You can perform the following configuration tasks for APPC security: • Configuring session security as described in “Configuring Session Security” • Configuring conversation security as described in “Configuring Conversation Security” Configuring Session Security Session-level security is used to validate LU-LU sessions. Each definition consists of a local LU name, a partner LU name, and a password.
Configuring APPC Communication Configuring APPC Security used to create a key, which is exchanged when the session is established. This password is not related to HP-UX login passwords on either the local or the remote node. Additional Configuration After performing the session security configuration, continue with the following configuration tasks: • To configure conversation security, see “Configuring Conversation Security”.
Configuring APPC Communication Configuring APPC Security The password to be accepted in an incoming conversation from a remote node. The password can be up to 10 characters long. This password is not related to HP-UX login passwords on either the local or the remote node. Additional Configuration After configuring conversation security, you can configure 5250 communication as described in Chapter 8, “Configuring User Applications.
Configuring APPC Communication Configuring APPC Security Additional Configuration After performing the security access list configuration, continue with the following configuration tasks: • Configure TP access as described in “Defining TPs”.
Configuring APPC Communication Configuring APPC Security 208 Chapter 7
8 Configuring User Applications 209
Configuring User Applications Overview Overview 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 Overview Step 1. For a 3270 display or printer, define a dependent LU as described in “Defining LU Types 0–3”. Step 2. To enable 3270 displays to select from a pool of LUs, define an LU pool as described in “Defining LU Pools”. If a display uses a dedicated LU, you can skip this step. Step 3. Define emulator users (or groups of users) and 3270 emulator sessions as described in “Configuring 3270 Users and Sessions”.
Configuring User Applications Overview RJE applications SNAplus2 provides support for remote job entry (RJE), enabling you to submit jobs to a host computer for processing. The RJE workstation daemon handles transfer of jobs to the host, and also handles the output returned from the host. 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.
Configuring User Applications Configuring 3270 Users and Sessions Configuring 3270 Users and Sessions To enable 3270 communications, you must define emulator users or groups of users as described in “Configuring 3270 Emulator Users”, and 3270 emulator sessions as described in “Configuring 3270 Sessions”. Configuring 3270 Emulator Users You must add emulator user definitions for each user who requires access to a 3270 emulator. Adding an individual user gives access to only that user.
Configuring User Applications Configuring 3270 Users and Sessions 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, this is 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.1 or Windows for Workgroups 3.
Configuring User Applications Configuring 3270 Users and Sessions If the user has a style file, enter the file name. If there is no style file, the user runs the emulation program with a default style. The style file determines the appearance and behavior of the emulation screens and keyboard for the emulator user. These may be different for different users. When entering the style file name, you should omit the .stu extension.
Configuring User Applications Configuring 3270 Users and Sessions The user can view RTM data. Send alerts The user can send alerts to NetView. Additional Configuration After performing the emulation user configuration, you can define 3270 sessions for users or groups as described in “Configuring 3270 Sessions”. Configuring 3270 Sessions A 3270 session definition must be added as the child of an emulator user or group definition.
Configuring User Applications Configuring 3270 Users and Sessions Display or Printer Specify whether the session is a display or printer session. LU/Pool name The name of the LU or pool to be used by the session. Assign printer LUs for printer sessions, and display LUs or pools of display LUs for display sessions. The LU should be defined on a host link station, and an LU pool should be defined in the LU Pools window.
Configuring User Applications Configuring 5250 Users Configuring 5250 Users To enable 5250 communications, you must define emulator users or groups of users as described in “Configuring 5250 Emulator Users”. Configuring 5250 Emulator Users You must add emulator user definitions for each user who requires access to a 5250 emulator. Adding an individual user gives access to only that user. You can also add a group of users in a single operation.
Configuring User Applications Configuring 5250 Users For users running the emulation program on HP-UX systems, this is 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.1 or Windows for Workgroups 3.11, or on Win16 subsystems on Windows NT, Windows 95, or OS/2, this name is the snauser field in the Configuration section of the sna.ini file (which usually resides in the c:\windows directory).
Configuring User Applications Configuring RJE Workstations Configuring RJE Workstations You can define an RJE workstation to submit jobs to a host computer for processing. The RJE workstation also handles the output returned by the host. 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.
Configuring User Applications Configuring RJE Workstations The RJE workstation runs using this user name, and all files created by the RJE workstation are owned by this user. UNIX group name The HP-UX system group name for the users who use the RJE workstation. The name must be a valid group name on the HP-UX system on which the RJE workstation runs, and the primary user of the RJE workstation must be a member of the group.
Configuring User Applications Configuring RJE Workstations 222 Chapter 8
9 Configuring Passthrough Services 223
Configuring Passthrough Services Overview Overview 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 “Configuring TN Server”. PU concentration provides connectivity between the host and local systems.
Configuring Passthrough Services Configuring TN Server Configuring TN Server TN server enables TN3270 clients to communicate with a host through an intermediate SNAplus2 node that implements the TN server. The TN3270 clients connect to the TN server using TCP/IP, and use LUs defined on the TN server. The TN server LUs establish sessions with LUs at the host to support TN3270 sessions for the clients.
Configuring Passthrough Services Configuring TN Server Configuring TN Server Access Records TN server access records indicate which TN3270 clients can access the TN server and which LUs they should use. Each access record identifies a TN3270 client that is permitted to access the TN server, the TCP/IP port that the client connects to, and the LU or LU pool that the client uses. You can also define default records that enable access by any TN3270 client.
Configuring Passthrough Services Configuring TN Server Permit access from a specific TCP/IP address. If you know the TCP/IP address of the TN3270 client, select this option and enter the address in the standard TCP/IP dotted decimal address format. Support TN3270E The level of TN3270 support provided by the node: TN3270 Support only the TN3270 protocol. Selecting this option disables server support for TN3270E protocols, even if they are supported on the client.
Configuring Passthrough Services Configuring TN Server If you want a TN3270 client to be able to use more than one LU or LU pool, define multiple access records, each with a different TCP/IP port number, so that you can identify the different LUs or LU pools by specifying different port numbers. Display LU assigned The name of the LU that the TN3270 client accesses when it is active. The LU must be a dependent LU on the local node.
Configuring Passthrough Services Configuring TN Server Motif administration program Select TN Server from the Services menu on the Node window, then select the Association Records pane on the TN Server window and choose New.
Configuring Passthrough Services Configuring PU Concentration 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 PU Concentration • Define the LUs on the local node that are used for communication with the host (the upstream LUs). Upstream LUs must be defined using the LU Type 0-3 Configuration dialog, specifying an LU type of unrestricted (unknown). To add the LUs, see “Defining LU Types 0–3”. • If you are going use any LU pools, define them as described in “Defining LU Pools”.
Configuring Passthrough Services Configuring PU Concentration 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. You can configure several LUs with consecutive LU numbers by defining a range of LUs. Upstream LU name The name of the host LU or a pool of LUs with which the downstream LUs will communicate.
Configuring Passthrough Services Configuring DLUR Configuring DLUR Normally, a dependent LU session requires a direct communications link to the host computer. If many nodes (including a host node) are connected together in an APPN network, some of them may have an indirect connection through another node instead of a direct connection to the host. Without a direct connection, it is not possible to establish dependent LU sessions to the host from LUs in these indirectly connected nodes.
Configuring Passthrough Services Configuring DLUR printer, RJE, or LUA. Depending on the requirements of the user applications supported by the LUs, you may also need to perform further configuration.
10 Managing SNAplus2 from NetView 235
Managing SNAplus2 from NetView Overview Overview 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 “Using the Host NetView Program”.
Managing SNAplus2 from NetView Using the Host NetView Program Using the Host NetView Program The SNAplus2 RCF operates in conjunction with the NetView program at a host computer. The host must be running NetView Version 1 Release 2, or a later version; SNAplus2 does not support NetView Version 1 Release 1.
Managing SNAplus2 from NetView Using the Host NetView Program Step 5. If you are using 3270 emulation to access NetView, follow the instructions in HP-UX SNAplus2 3270/3179G Users Guide for ending 3270 emulation when you have finished issuing commands. NetView Screen Display The layout of the NetView screen varies with different versions of NetView at different hosts. The display includes an input area at the bottom of the screen; this is the area into which you can type commands.
Managing SNAplus2 from NetView Using the Host NetView Program node The SNAplus2 node associated with the service point name spname (for SPCF commands) unix 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.
Managing SNAplus2 from NetView Using the Host NetView Program Table 10-1 Using Escape Characters in RCF Commands Characters to Produce Input ABcd \a\bcd [] \( \) \a \\a \[ \\\( The escape characters you would normally use on the HP-UX command line, to prevent the HP-UX shell from interpreting special characters, are not required with RCF. For example, do not use escape characters with strings containing the characters * or $, as you would when entering them on the HP-UX command line.
Managing SNAplus2 from NetView Using SPCF Using SPCF SPCF enables you to issue commands from the NetView console to manage the running SNAplus2 system. These commands are the same as those you can issue using the SNAplus2 command-line management program snapadmin (as described in HP-UX SNAplus2 Administration Command Reference). For information about the syntax of an SPCF command, see “Overview of RCF Command Syntax”.
Managing SNAplus2 from NetView Using SPCF To provide security, you can set up the SNAplus2 configuration so that only certain types of commands are permitted from SPCF. For example, you can permit remote users to issue query_* commands, but not to activate or deactivate SNAplus2 components.
Managing SNAplus2 from NetView Using UCF Using UCF UCF enables a NetView operator to issue HP-UX commands on a computer running SNAplus2 by typing the command text at the NetView console, and to view output from these commands. The facility is not restricted to commands related to SNAplus2; subject to the restrictions in “Permitted Commands”, any type of command can be issued.
Managing SNAplus2 from NetView Using UCF Specify spname, which is the name of your service point as defined at NetView. The host NetView personnel can give you this information. appl=unix Instruct NetView to send the command to the UCF daemon program on the SNAplus2 computer associated with the service point name spname. HP-UX_command Supply the HP-UX operating system command.
Managing SNAplus2 from NetView Using UCF • The UCF cannot be used with a command that requires further input from the user before it completes (for example, a command such as vi filename that starts an interactive process, or a command such as tail -f filename that does not complete until it is stopped by the user). Because all HP-UX commands run with the login ID and permissions of the configured UCF user, the valid commands are limited by the access rights of the UCF user's login.
Managing SNAplus2 from NetView Using UCF If you issue a command when a previous command is still in progress (that is, before the UNIX COMMAND COMPLETED message is received), the following message is displayed: = = = COMMAND QUEUED = = = The second command is queued, and is executed when the previous command has completed. Canceling a Command UCF provides a method of canceling a command that is still in progress.
Managing SNAplus2 from NetView Using UCF In this case, the ux-cancel command is ignored. No action is necessary. This message can be displayed when the ux-cancel command is issued after the previous command finishes but before the UNIX COMMAND COMPLETED message is received. UCF Security Because the UCF enables a remote operator to issue commands on the HP-UX computer and to receive output from these commands, it is important to consider the security implications.
Managing SNAplus2 from NetView Using UCF 248 Chapter 10
11 Managing SNAplus2 Clients 249
Managing SNAplus2 Clients Overview Overview A domain for SNAplus2 can include both servers (SNA nodes) and clients (which can access SNA connectivity through a server). Clients can be computers running the HP-UX operating system or the Windows 3.1, Windows for Workgroups 3.11, Windows 95, or Windows NT operating systems. Servers and clients communicate across the SNAplus2 domain using TCP/IP. A client can access one or more servers at the same time, and can run concurrent applications as needed.
Managing SNAplus2 Clients Client Networking Requirements Client Networking Requirements Before you can run SNAplus2 on a client computer, you must configure TCP/IP port addresses on both the clients and servers in your network. If you encounter problems with the default port assignments, you may need to resolve conflicts as described in “Setting Up IP Port Numbers”.
Managing SNAplus2 Clients Client Networking Requirements For Windows Step 4. If your SNAplus2 domain includes Windows clients, add the same two lines to the services file on each Windows computer. The services file is in the same format as the HP-UX file, and is generally stored in the home directory of the Windows TCP/IP software; see your Windows TCP/IP documentation for more information if necessary. End of Section Step 5. Re-enable the SNAplus2 software.
Managing SNAplus2 Clients Client Networking Requirements • 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).
Managing SNAplus2 Clients Managing Win32 Clients Managing Win32 Clients For Windows SNAplus2 enables machines running Microsoft Windows 95 and Windows NT to act as clients in the SNAplus2 domain. The SNAplus2 client software includes API libraries that are fully compatible with Microsoft SNA Server and the Windows Open Systems Architecture (WOSA), enabling applications written for SNA Server to run unchanged on the SNAplus2 Win32 client.
Managing SNAplus2 Clients Managing Win32 Clients • Logging and tracing options for applications running on the client • Additional options for CPI-C and CSV applications running on the client • Invokable TPs (APPC or CPI-C) that can run on the client For more information, see “Win32 Client Configuration”. Enabling a Win32 Client To enable the SNAplus2 software on a Windows 95 computer, either double-click on the Win32 Client icon, or use the normal Windows “File Run” mechanisms to run sxclappl.exe.
Managing SNAplus2 Clients Managing Win32 Clients Win32 Client Security SNAplus2 provides a facility for validating the user name and password of any Win32 client running on Windows 95 and attempting to contact a server running SNAplus2. This enables you to ensure that only authorized Windows users are able to access the SNAplus2 system. On Windows NT no validation is performed (the fact that the user had to enter a password to access the desktop is considered to provide sufficient security).
Managing SNAplus2 Clients Managing Win32 Clients Win32 Client Configuration On both Windows NT and Windows 95, configuration information is managed through the Windows Program Registry. The Windows Program Registry contains SNA network information (similar to the information held in the client network data file on HP-UX clients). It also contains some additional configuration information that is specific to Win32 clients.
Managing SNAplus2 Clients Managing Win32 Clients rui = YES | NO nof = YES | NO ms = YES | NO 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 Appl_Name APPCTPN = tp_name APPCLLU = lu_name CSV_data CSVTBLG = table_G_filename NOTE The domain = doma
Managing SNAplus2 Clients Managing Win32 Clients The group_name value indicates the group name of the SNAplus2 user on this client. This name must match the SNAplus2 configuration on servers, as follows: • If the client will be running 3270 or 5250 emulation, and you have set up the SNAplus2 configuration to include emulator records for groups of users rather than an individual record for each user, this name must match the name of an emulator user record that is defined for use by a group of users.
Managing SNAplus2 Clients Managing Win32 Clients Specify the time in seconds for which the TCP/IP connection from the client to a server should be kept active while no applications on the client are using SNAplus2 resources. For more information, see “LAN Access Timeout”. The valid range is 0–65535. The minimum timeout is 60 seconds (lower values are rounded up to 60 seconds). To deactivate the TCP/IP connection more quickly, disable the client. This parameter is optional.
Managing SNAplus2 Clients Managing Win32 Clients This parameter is optional. The valid range is 5–65535. If it is not specified, the default is 200 (seconds). client_start_timeout The Registry data type of this value is REG_DWORD. Specify the time in seconds that an application waits while the Win32 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 Clients Managing Win32 Clients server has been contacted, the client then tries using directed messages to one or more named servers (specified by the following lines of the file). • 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.
Managing SNAplus2 Clients Managing Win32 Clients The parameters Server2–Server10 cannot be set to * to indicate the use of UDP broadcasts. Only the Server1 parameter can be used to indicate this, because the * value must precede any server names in the file. 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.
Managing SNAplus2 Clients Managing Win32 Clients This parameter is optional. If it is not specified, the Win32 client uses the global domain settings to determine whether audit messages are recorded. (The initial default is that audit messages are recorded.) log_directory The Registry data type of this value is REG_SZ. 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.
Managing SNAplus2 Clients Managing Win32 Clients amount of disk space taken up by error log files is approximately twice the value of the error_file_wrap_size parameter. This parameter is optional. If it is not specified, the default is 1000000 (bytes). If you are logging error and audit messages to the same file, this parameter must be set to the same value as the audit_file_wrap_size parameter. audit_file The Registry data type of this value is REG_SZ. Name of the file to which audit messages are written.
Managing SNAplus2 Clients Managing Win32 Clients This parameter is optional. If it is not specified, the default is 1000000 (bytes). If you are logging error and audit messages to the same file, this parameter must be set to the same value as the error_file_wrap_size parameter. succinct_errors The Registry data type of this value is REG_SZ. Specifies whether to use succinct logging or verbose logging in the error log file. This setting applies to both exception logs and problem logs.
Managing SNAplus2 Clients Managing Win32 Clients The Registry data type of this value is REG_SZ. Specifies whether to use succinct logging or verbose logging in the audit log file. The permitted values and their meanings are the same as for the succinct_errors parameter. API_tracing The API_tracing subkey specifies API tracing options for applications running on the client. For more information about tracing, refer to HP-UX SNAplus2 Diagnostics Guide.
Managing SNAplus2 Clients Managing Win32 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 1000000 (bytes). truncation_length The Registry data type of this value is REG_DWORD.
Managing SNAplus2 Clients Managing Win32 Clients The Registry data type of this value is REG_SZ. To trace CPI-C API messages, set this parameter to YES; otherwise, set it to NO. 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 CPI-C messages are traced. csv The Registry data type of this value is REG_SZ. To trace CSV API messages, set this parameter to YES; otherwise, set it to NO. This parameter is optional.
Managing SNAplus2 Clients 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 Win32 client 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 Clients Managing Win32 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 1000000 (bytes). truncation_length The Registry data type of this value is REG_DWORD.
Managing SNAplus2 Clients Managing Win32 Clients The Registry data type of this value is REG_SZ. 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. If both file1 and file2 are specified, tracing is to two files. When the first file reaches the size specified by the flip_size parameter, the second file is cleared, and tracing continues to the second file.
Managing SNAplus2 Clients Managing Win32 Clients To trace data messages, set this parameter to YES; otherwise, set it to NO. This parameter is optional. If it is not specified, the default is NO. send The Registry data type of this value is REG_SZ. To trace all data messages sent from the client to the server, set this parameter to YES; otherwise, set it to NO. This parameter is optional. If it is not specified, the default is NO. receive The Registry data type of this value is REG_SZ.
Managing SNAplus2 Clients Managing Win32 Clients The TP name of the application. This name is used in log and trace files to identify the application. For an invoked application (one that issues Accept_Conversation), it is also used to match the TP name on an incoming Allocate request with the correct application; the invoked application can also use the Specify_Local_TP_Name call to specify additional names to be matched with incoming Allocate requests. This parameter is optional.
Managing SNAplus2 Clients Managing Win16 Clients Managing Win16 Clients SNAplus2 enables machines running Microsoft Windows 3.1 and Windows for Workgroups 3.11 to act as clients in the SNAplus2 domain. The SNAplus2 client software includes API libraries that are fully compatible with Microsoft SNA Server and the Windows Open Systems Architecture (WOSA), enabling applications written for SNA Server to run unchanged on the SNAplus2 Win16 client.
Managing SNAplus2 Clients Managing Win16 Clients • Servers that the client can access • Logging and tracing options for applications running on the client • Additional options for CPI-C and CSV applications running on the client For more information about this file, see “Win16 Client Initialization File (sna.ini)”. sna_tps.ini Win16 client invokable TP data file.
Managing SNAplus2 Clients Managing Win16 Clients To disable the NAP, click on the Windows NAP icon and choose Close. If any SNAplus2 applications are running, the Close option is not selectable; if you are sure you want to disable the NAP, stop the relevant applications before retrying. Win16 Client Security SNAplus2 provides a facility for validating the user name and password of any Win16 client attempting to contact a server running SNAplus2.
Managing SNAplus2 Clients Managing Win16 Clients password, or if the user name and password cannot be matched with a user name and password on the server, the server rejects the client's access attempt. To stop using Win16 client security, so that any Win16 client user can access SNAplus2 servers without having to specify a password, use the following command: snapwinsec off This command removes Win16 client security on all servers in the SNAplus2 domain.
Managing SNAplus2 Clients Managing Win16 Clients backup_error_file = backup_error_filename error_file_wrap_size = error_file_size audit_file = audit_filename backup_audit_file = backup_audit_filename audit_file_wrap_size = audit_file_size succinct_errors = YES | NO succinct_audits = YES | NO [API_tracing] file1 = trace_filename_1 file2 = trace_filename_2 flip_size = filesize truncation_length = length all_api = YES | NO appc = YES | NO cpic = YES | NO csv = YES | NO rui = YES | NO nof = YES | NO ms = YES |
Managing SNAplus2 Clients Managing Win16 Clients [Configuration] The [Configuration] section of the file contains configuration information for the client, as follows: domain The domain_name argument indicates the domain name of the SNAplus2 LAN, as specified during the client installation. This line is required. snauser The user_name argument indicates the user name of the SNAplus2 user on this client. This name was specified during the client installation.
Managing SNAplus2 Clients Managing Win16 Clients The group_name argument indicates the group name of the SNAplus2 user on this client. This name must match the SNAplus2 configuration on servers, as follows: • If the client will be running 3270 or 5250 emulation, and you have set up the SNAplus2 configuration to include emulator records for groups of users rather than an individual record for each user, this name must match the name of an emulator user record that is defined for use by a group of users.
Managing SNAplus2 Clients Managing Win16 Clients Specify the time in seconds for which the TCP/IP connection from the client to a server should be kept active while no applications on the client are using SNAplus2 resources. For more information, see “LAN Access Timeout”. The valid range is 0–65535. The minimum timeout is 60 seconds (lower values are rounded up to 60 seconds). To deactivate the TCP/IP connection more quickly, disable the NAP on the client. This parameter is optional.
Managing SNAplus2 Clients Managing Win16 Clients [Servers] The [Servers] section of the file contains information about SNAplus2 servers that the client can access, as follows: Server1 Enter an asterisk (*) or a server name: • To indicate that the client should attempt to find a server running SNAplus2 by using a UDP broadcast message to all computers on its TCP/IP subnet (or on all subnets that it can access, if the client computer contains more than one LAN adapter card), specify *.
Managing SNAplus2 Clients Managing Win16 Clients attempts to contact the server specified in Server2 using a directed message. If this fails, it tries the server specified in Server3, and so on. These server names are optional, but provide a backup mechanism if the broadcast method of locating a server fails or if the server specified by Server1 is unavailable.
Managing SNAplus2 Clients Managing Win16 Clients This parameter is optional. If it is not specified, the Win16 client uses the global domain settings to determine whether exception messages are recorded. (The initial default is that exception messages are recorded.) audit_logging_enabled Set this parameter to one of the following values: YES Record audit messages. NO Do not record audit messages. This parameter is optional.
Managing SNAplus2 Clients Managing Win16 Clients 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. error_file_wrap_size The maximum size of the log file specified by error_file. When a message written to the file causes the file size to exceed this limit, SNAplus2 copies the current contents of the log file to the backup log file, then clears the log file.
Managing SNAplus2 Clients Managing Win16 Clients clears the log file. This means that the maximum amount of disk space taken up by audit log files is approximately twice the value of the audit_file_wrap_size parameter. This parameter is optional. If it is not specified, the default is 10000 (bytes). If you are logging error and audit messages to the same file, this parameter must be set to the same value as the error_file_wrap_size parameter.
Managing SNAplus2 Clients Managing Win16 Clients either be from the set_global_log_type command, or from a set_log_type command issued to that server to override the default. succinct_audits Specifies whether to use succinct logging or verbose logging in the audit log file. The permitted values and their meanings are the same as for the succinct_errors parameter. [API_tracing] The [API_tracing] section of the file specifies API tracing options for applications running on the client.
Managing SNAplus2 Clients Managing Win16 Clients This parameter is optional. If it is not specified, the default is 100000 (bytes). truncation_length The maximum length, in bytes, of the information written to the trace file for each message. If a message is longer than this, SNAplus2 writes only the start of the message to the trace file, and discards the data beyond truncation_length.
Managing SNAplus2 Clients Managing Win16 Clients To trace CSV API messages, set this parameter to YES; otherwise, set it to NO. 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 CSV messages are traced. rui To trace LUA RUI messages, set this parameter to YES; otherwise, set it to NO. This parameter is optional. If it is not specified, the default is NO.
Managing SNAplus2 Clients 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 Clients Managing Win16 Clients To trace 3270 messages, set this parameter to YES; otherwise, set it to NO. This parameter is optional. If it is not specified, the default is NO. [CS_tracing] The [CS_tracing] section of the file specifies options for client/server tracing (tracing on messages between the client and SNAplus2 servers). For more information about tracing, refer to HP-UX SNAplus2 Diagnostics Guide.
Managing SNAplus2 Clients Managing Win16 Clients To trace internal messages relating to client/server topology, set this parameter to YES; otherwise, set it to NO. This parameter is optional. If it is not specified, the default is NO. datagram To trace datagram messages, set this parameter to YES; otherwise, set it to NO. This parameter is optional. If it is not specified, the default is NO. data To trace data messages, set this parameter to YES; otherwise, set it to NO. This parameter is optional.
Managing SNAplus2 Clients Managing Win16 Clients The name of the local LU that this application uses. This parameter is optional. If it is not specified, the application attempts to use the default LU (the LU associated with a local node's control point). APPCTPN The TP name of the application. This name is used in log and trace files to identify the application.
Managing SNAplus2 Clients Managing HP-UX Clients Managing HP-UX Clients For UNIX Client information for a client running on a HP-UX system is stored in the sna_clnt.net file, which is created when you install the SNAplus2 software on the client. That file must be present before you can enable SNAplus2 on the client.
Managing SNAplus2 Clients Managing HP-UX Clients HP-UX Client Network Data File (sna_clnt.net) The sna_clnt.net file defines the SNAplus2 facilities available on a client computer running on a HP-UX system, and the servers the client can access. For information about the equivalent file on a Windows client, see Chapter 11, “Managing SNAplus2 Clients.” It also includes information about setting up the IP port numbers that SNAplus2 uses for client/server communications.
Managing SNAplus2 Clients Managing HP-UX Clients that issue the Accept_Conversation or Accept_Incoming verbs). In this case, you may also need to define the TP on this client. For more information, see “Defining TPs”. Specify invoked_tps = NO if this client is not used to run invoked TPs. This line is optional; if it is not included, the default is NO.
Managing SNAplus2 Clients Managing HP-UX Clients before beginning or restarting the attempt to contact a server. If the client has lost contact with the server, SNAplus2 does not wait for the full timeout period, but retries after a random period between 5 seconds and the specified timeout; this is to avoid bursts of network traffic caused by large numbers of clients attempting to contact a server at the same time. This parameter is optional; if it is not specified, the default is 200 seconds.
Managing SNAplus2 Clients Managing HP-UX Clients received no response, the client attempts to contact the first server listed using a directed message. If this fails, the client tries the second server listed, and so on. If the * line (to indicate the use of UDP broadcasts) is not included, at least one server name must be specified; otherwise, server names are optional.
Managing SNAplus2 Clients Managing HP-UX Clients 300 Chapter 11
A Configuration Planning Worksheets 301
Configuration Planning Worksheets Overview Overview 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.
Configuration Planning Worksheets Node Worksheets Node Worksheets Complete only one of the following worksheets: • “APPN End Node” • “LEN Node” APPN End Node Complete this worksheet if the local node is an APPN end node (a node that can use dynamic routing information but does not provide routing services for other nodes). Motif Field Valid Entry/Notes Your Implementation Value Node Parameters Dialog APPN support End node Control point name NETNAME.
Configuration Planning Worksheets Node Worksheets Motif Field Valid Entry/Notes Your Implementation Value 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 “User Application Support Worksheets”.
Configuration Planning Worksheets Node Worksheets Motif Field Valid Entry/Notes Your Implementation Value 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 “User Application Support Worksheets”.
Configuration Planning Worksheets Connectivity Worksheets Connectivity Worksheets For each link protocol used to communicate with another node, complete one of the following worksheets. If necessary, you can configure more than one link station on a port. • “SDLC” • “Token Ring” • “Ethernet” • “FDDI” • “QLLC (X.25)” SDLC Complete this worksheet to support connectivity using the SDLC link protocol.
Configuration Planning Worksheets Connectivity Worksheets Motif Field Valid Entry/Notes Link role Your Implementation Value Negotiable Primary Primary multi-drop Secondary For switched incoming or leased line: Poll address Only for nonprimary, switched incoming ports On a VTAM host, the poll address is configured as the ADDR= parameter in the VTAM PU definition. On an AS/400 system, the poll address is the STNADR parameter of the Line Description.
Configuration Planning Worksheets Connectivity Worksheets Motif Field Valid Entry/Notes Activation By administrator On node startup On demand LU traffic Any Independent only Dependent only 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 command.
Configuration Planning Worksheets Connectivity Worksheets Motif Field Valid Entry/Notes 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.
Configuration Planning Worksheets Connectivity Worksheets Token Ring Complete this worksheet to support connectivity using the token ring link protocol. Motif Field Valid Entry/Notes Your Implementation Value Token Ring SAP Dialog SNA port name Up to 8 characters Token ring card number 0 to number_of_cards_minus_1 Local SAP number Hexadecimal (multiple of 4) Initially active Select if needed Define on connection network Select if needed CN name NETNAME.
Configuration Planning Worksheets Connectivity Worksheets Motif Field Remote node Valid Entry/Notes Your Implementation Value 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 command. The last eight characters are in the SSCPNAME parameter of the VTAM Start command.
Configuration Planning Worksheets Connectivity 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.
Configuration Planning Worksheets Connectivity Worksheets Motif Field Valid Entry/Notes Your Implementation Value Ethernet SAP Dialog SNA port name Up to 8 characters Ethernet card number 0 to number_of_cards_minus_1 Local SAP number Hexadecimal (multiple of 4) Initially active Select if needed Define on connection network Select if needed CN name NETNAME.
Configuration Planning Worksheets Connectivity Worksheets Motif Field Remote node Valid Entry/Notes Your Implementation Value 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 command. The last eight characters are in the SSCPNAME parameter of the VTAM Start command.
Configuration Planning Worksheets Connectivity 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.
Configuration Planning Worksheets Connectivity Worksheets Motif Field Valid Entry/Notes Your Implementation Value FDDI SAP Dialog SNA port name Up to 8 characters FDDI card number 0 to number_of_cards_minus_1 Local SAP number Hexadecimal (multiple of 4) Initially active Select if needed Define on connection network Select if needed CN name NETNAME.
Configuration Planning Worksheets Connectivity Worksheets Motif Field Remote node Valid Entry/Notes Your Implementation Value 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 command. The last eight characters are in the SSCPNAME parameter of the VTAM Start command.
Configuration Planning Worksheets Connectivity 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.
Configuration Planning Worksheets Connectivity Worksheets Motif Field Valid Entry/Notes Your Implementation Value QLLC Port Dialog SNA port name Up to 8 characters X.25 card number 0 to number_of_cards_minus_1 Port number 0 to number_of_ports_on_card_minus_1 Initially active Select if needed Match incoming X.25 address Local X.
Configuration Planning Worksheets Connectivity Worksheets Motif Field Remote node Valid Entry/Notes Your Implementation Value 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 command. The last eight characters are in the SSCPNAME parameter of the VTAM Start command.
Configuration Planning Worksheets Connectivity Worksheets Motif Field Valid Entry/Notes Circuit type Permanent virtual circuit Switched virtual circuit Channel ID 1–4096 (only for PVC) Remote X.
Configuration Planning Worksheets Passthrough Services Worksheets 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: • “DLUR” • “TN Server” DLUR Complete this worksheet to support DLUR on the local node. Motif Field Valid Entry/Notes Your Implementation Value Node Configuration: See “Node Worksheets”. Connectivity Configuration: See “Connectivity Worksheets”.
Configuration Planning Worksheets Passthrough Services Worksheets Motif Field Valid Entry/Notes Initially active Select if needed Reactivate PU after failure Select if needed Your Implementation Value Local LU and Application Configuration: See “User Application Support Worksheets”. You must configure local dependent LUs and any application support you require. PU Concentration Complete this worksheet if the local node is to support PU concentration.
Configuration Planning Worksheets Passthrough Services Worksheets Motif Field Valid Entry/Notes Downstream PU name Type A EBCDIC string LU numbers 1-255 (for a range, supply first and last numbers) Upstream LU name Type A EBCDIC string (for LU name) or type AE EBCDIC string (for LU pool name) Your Implementation Value TN Server Complete this worksheet if the local node is to support TN3270 clients.
Configuration Planning Worksheets Passthrough Services Worksheets Motif Field TN3270 client address Valid Entry/Notes Your Implementation Value Specify one of the following: • Default record (any TN3270 client) • TCP/IP address (dotted decimal address of client) • TCP/IP name or alias Support TN3270E Select to support TN3270E (in addition to TN3270 and TN3287) TN3270 port and LUs TCP/IP port number Usually 23.
Configuration Planning Worksheets User Application Support Worksheets User Application Support Worksheets Complete the following worksheets if the corresponding user-level applications are to be supported by the local node: • “APPC” • “CPI-C” • “5250” • “3270” • “RJE” • “LUA” APPC Complete this worksheet if the local node is to support APPC applications. Motif Field Valid Entry/Notes Your Implementation Value Node Configuration: See “Node Worksheets”.
Configuration Planning Worksheets User Application Support Worksheets Motif Field LU number Valid Entry/Notes Your Implementation Value 1–255 This value must match the LOCADDR parameter in the VTAM/NCP LU resource definition statement. Member of default pool Select if needed (only for dependent LU) Local LU parameters Support syncpoint Select if needed Disable password substitution Select if needed Restrict to specific SSCP Select if needed (only for dependent LU).
Configuration Planning Worksheets User Application Support Worksheets Motif Field Location Valid Entry/Notes Your Implementation Value NETNAME.CPNAME (each 1–8 type A EBCDIC characters) LS Routing Dialog: Only required if partner LU is located by link station. LU name 1–8 type A EBCDIC characters LS name Up to 8 characters Partner LU name (NETNAME.
Configuration Planning Worksheets User Application Support Worksheets Motif Field Maximum RU size Valid Entry/Notes Your Implementation Value Recommended upper limit is 1024. Session Security Dialog: Only required if session security is required for sessions between a specific local and partner LU.
Configuration Planning Worksheets User Application Support Worksheets Motif Field TP name Valid Entry/Notes Your Implementation Value User application: up to 64 ASCII characters 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 Eithe
Configuration Planning Worksheets User Application Support Worksheets Motif Field Valid Entry/Notes Your Implementation Value Node Configuration: See “Node Worksheets”. Connectivity Configuration: See “Connectivity Worksheets”. APPC Configuration: See “APPC”. CPI-C Destination Dialog Symbolic destination name 1–8 characters Local LU Alias (up to 8 characters) or fully qualified name (NETNAME.
Configuration Planning Worksheets User Application Support Worksheets Motif Field Valid Entry/Notes Your Implementation Value Node Configuration: See “Node Worksheets”. Connectivity Configuration: See “Connectivity Worksheets” (configure for independent traffic). APPC Configuration: See “APPC”. Emulator User and Emulator Group Dialogs User name or group name Valid user login or group name, or 3270 Complete this worksheet if the local node is to support 3270 communications.
Configuration Planning Worksheets User Application Support Worksheets Motif Field LU numbers Valid Entry/Notes Your Implementation Value 1–255 (for a range, supply first and last numbers) This value must match the LOCADDR parameter in the VTAM/NCP LU resource definition statement.
Configuration Planning Worksheets User Application Support Worksheets Motif Field 3270 permissions Valid Entry/Notes Your Implementation Value Select any of the following: • Session Limit (indicate number of sessions) • View RTM data • Change LU • Send alerts 3270 Session Dialog Single session or Multiple sessions Select desired option Session name SESS0001–SESS0010 (for single sessions only) Session base name Up to 5 characters (for multiple sessions only) Session type For single sessions only,
Configuration Planning Worksheets User Application Support Worksheets Motif Field Valid Entry/Notes Your Implementation Value Node Configuration: See “Node Worksheets”. Connectivity Configuration: See “Connectivity Worksheets” (configure for dependent traffic).
Configuration Planning Worksheets User Application Support Worksheets LUA Complete this worksheet if the local node is to support LUA applications. Motif Field Valid Entry/Notes Your Implementation Value Node Configuration: See “Node Worksheets”. Connectivity Configuration: See “Connectivity Worksheets” (configure for dependent traffic).
B APPN Network Management Using the Simple Network Management Protocol 337
APPN Network Management Using the Simple Network Management Protocol Overview Overview 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.
APPN Network Management Using the Simple Network Management Protocol Introduction to SNMP Introduction to SNMP The Simple Network Management Protocol (SNMP) is an industry-standard management protocol, originally designed for managing TCP/IP networks. SNMP is described by a series of Request for Comments (RFCs) that specifies and structures the information that is exchanged between managing and managed systems.
APPN Network Management Using the Simple Network Management Protocol Introduction to SNMP Figure B-1 Overview of SNMP The SNMP agent talks to both subagents and managers. The SNMP manager (which resides on one node in the network) sends requests to the agent (which resides on another). The agent sends responses and traps to the manager. For SNAplus2, the APPN MIB is implemented by the SNAplus2 SNMP subagent.
APPN Network Management Using the Simple Network Management Protocol SNAplus2 APPN SNMP Subagent 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.
APPN Network Management Using the Simple Network Management Protocol APPN Management Information Base (MIB) APPN Management Information Base (MIB) The APPN MIB is defined by informational RFC 1593. The ASN.1 representation of the APPN MIB is located in the file named /etc/opt/sna/mib/appn.my, which also provides a more detailed description of the APPN MIB objects. This MIB definition should be used with your management application.
C Configuring an Invokable TP Using snaptpinstall 343
Configuring an Invokable TP Using snaptpinstall Overview Overview The snaptpinstall utility is a command-line application that enables a user or the writer of a TP installation program to define an invokable TP. You can run snaptpinstall on a server or client. The syntax of the command is different depending on whether you are defining, removing, or querying TP definitions: Define an invokable TP: snaptpinstall -a file_name This command adds one or more TP definitions from the specified file_name.
Configuring an Invokable TP Using snaptpinstall File Format for snaptpinstall File Format for snaptpinstall The file that supplies configuration information for an invokable TP is an ASCII text file that can be modified using any standard text editor.
Configuring an Invokable TP Using snaptpinstall File Format for snaptpinstall on the RECEIVE_ALLOCATE verb when it starts up, to enable SNAplus2 to route the incoming Attach to the correct TP. This name must be enclosed within square brackets. The name can be specified as an ASCII string, enclosed in double quotation marks (for example, ["TPNAME1"]).
Configuring an Invokable TP Using snaptpinstall File Format for snaptpinstall 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. An incoming Allocate request is routed to this TP only if it is received by an LU that is configured to route incoming Allocate requests to this computer. QUEUED-BROADCAST The TP is a broadcast queued TP.
Configuring an Invokable TP Using snaptpinstall File Format for snaptpinstall If you use NON-QUEUED, more than one copy of the TP can be running at a time. If the TP writes to files on the Windows computer, you need to ensure that different copies of the TP do not overwrite each other's files.
Configuring an Invokable TP Using snaptpinstall File Format for snaptpinstall TP (unless the application overrides it by specifying a full path). If the application specifies a file name without a path, SNAplus2 searches for the file in this home directory; if the application specifies a file name with a relative path, SNAplus2 searches for the file in the specified directory relative to this home directory. This line is required, and must be specified.
Configuring an Invokable TP Using snaptpinstall File Format for snaptpinstall If the LU alias is specified for an automatically started TP, the TP must use the extended form of the RECEIVE_ALLOCATE verb and specify this LU alias as a parameter to the verb. This enables SNAplus2 to route the incoming Attach to the correct TP. For more information about the different forms of RECEIVE_ALLOCATE, refer to HP-UX SNAplus2 APPC Programmers Guide.
Configuring an Invokable TP Using snaptpinstall File Format for snaptpinstall The application is displayed at its normal size and position. NOACTIVATE The application is displayed at its normal size and position, and the focus remains on the previously active window. This application's window does not become the active window. MINNOACTIVATE The application is minimized, and the focus remains on the previously active window. This parameter is optional. If it is not included, the default is NORMAL.
Configuring an Invokable TP Using snaptpinstall File Format for snaptpinstall • White space (space characters and tab characters) at the start or end of a line, or before or after the = character, is ignored (except in the string environment_variable=value for the ENV parameter). • Each TP definition begins with the line identifying the TP name, and ends with the end of the file or the next TP name.
D Using SNAplus2 in a High Availability Environment 353
Using SNAplus2 in a High Availability Environment Overview Overview This appendix describes the high availability features of SNAplus2 and how it works with the HP MC/ServiceGuard product.
Using SNAplus2 in a High Availability Environment What is High Availability? 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 . These failures might include entire computer system failures, network failures, software failures, power failures, disk drive failures, and I/O interface failures.
Using SNAplus2 in a High Availability Environment What is High Availability? Figure D-1 SNAplus2 client/server network Client Client Client Client LAN Client/server network link S800 Server SNAplus2 Link software Disk Drives SNA network link 3xxx Communications Controller IBM Host In this environment, applications run on client systems (HP9000s or PCs) and access the IBM mainframe through an HP9000 S800 server.
Using SNAplus2 in a High Availability Environment What is High Availability? • The LAN networking software on the server system • The SNAplus2 Link software on the server system • The operating system on the server system • Disk drives attached to the server system • The SNA network adapter card on the server system • The SNA network between the HP 9000 and the IBM Front End Processor Other failures to consider include power failures, IBM mainframe outages, client system failures, etc.
Using SNAplus2 in a High Availability Environment SNAplus2 High Availability Features SNAplus2 High Availability Features SNAplus2 already has high availability features built in, namely, LU pools, and client/server configurations. LU Pools for 3270, 3179G, and LUA One of the most significant fault-tolerant feature s of SNAplus2 is the LU Pool feature. This feature allows users of 3270, 3179G, and LUA to access a pool of LUs rather than a specific LU.
Using SNAplus2 in a High Availability Environment SNAplus2 High Availability Features 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.
Using SNAplus2 in a High Availability Environment SNAplus2 High Availability Features for high availability environments in that applications running on client systems can access ports on multiple servers. By providing applications with multiple paths to the remote SNA system, the client/server configuration greatly reduces the number of single points of failure. When an SNAplus2 application starts in a client/server configuration, it tries to locate a suitable LU that is available.
Using SNAplus2 in a High Availability Environment SNAplus2 High Availability Features 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 .
Using SNAplus2 in a High Availability Environment SNAplus2 High Availability Features Table D-1 Component NOTE Primary Server Backup Server System Name hp_pri hp_back SNAplus2 Node HANODE DEVNODE SNAplus2 Port HAPORT DEVPORT SNAplus2 LS HALS DEVLS SNAplus2 Local LU aliases HALU01...HALU09 DEVLU01...DEVLU05 The above example will be used throughout this appendix to explain many different aspects of high availability systems.
Using SNAplus2 in a High Availability Environment SNAplus2 High Availability Features Figure D-4 SNAplus2 on Primary and Backup Servers Client Client Client Client LAN Primary HP-UX Server hp_pri Backup HP-UX Server hp_back Production Configuration Development Configuration Node.................HANODE LS.....................HALS Port...................HAPORT LUs...................HALUO1...HALU09 Node................DEVNODE LS....................DEVLS Port..................DEVPORT LUs............
Using SNAplus2 in a High Availability Environment SNAplus2 High Availability Features At this point, the backup server has completely taken over the primary server and is providing the HALU01...HALU09 LUs for the production applications. The less important development LUs are no longer available. The key point is that the production applications do not need to change when this switch takes place. The location of where the software components are started changes, not the underlying SNAplus2 configuration.
Using SNAplus2 in a High Availability Environment Using SNAplus2 with MC/ServiceGuard Using SNAplus2 with MC/ServiceGuard MC/ServiceGuard (product number B3935AA) is a specialized facility for protecting mission critical applications from hardware and software failures by allowing you to organize groups of servers into clusters and applications (like SNAplus2 ) into packages. (See Managing MC/ServiceGuard, HP Part No. B3936-90003).
Using SNAplus2 in a High Availability Environment Using SNAplus2 with MC/ServiceGuard Some of the reasons that ServiceGuard works well with SNAplus2 in a high availability environment are as follows: 1. ServiceGuard is designed for general software resiliency. This means that ServiceGuard packages can easily be built for SNAplus2 . 2. The automatic recovery capabilities of ServiceGuard complement the built-in high availability features of SNAplus2 . 3.
Using SNAplus2 in a High Availability Environment Using SNAplus2 with MC/ServiceGuard Step 1. List all of the mission critical applications that use SNAplus2 for SNA network connectivity. Step 2. Diagram your network topology so that you know the location of the servers that are part of the ServiceGuard cluster and any other systems needed for SNA network connectivity. Step 3. List the SNAplus2 LSs that must be highly available.
Using SNAplus2 in a High Availability Environment Using SNAplus2 with MC/ServiceGuard Assuming the applications attempt to activate a new LU-LU session when they lose the LU-LU session they were using, you simply need to wait for the migration to occur. The applications require no restart ing because they run on client systems. The set of commands needed to start HALS on the backup server are listed. Once the backup server reactivates HALS, the applications will again be able to obtain LU-LU sessions.
Using SNAplus2 in a High Availability Environment Using SNAplus2 with MC/ServiceGuard 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.
Using SNAplus2 in a High Availability Environment Using SNAplus2 with MC/ServiceGuard snapadmin start_ls, ls_name=HALS LS details are: Activation state = active Port name = HAPORT In this example, the state of the LS is active, which means the server is currently providing SNA network connectivity to a remote SNA system. The snapadmin start_ls command is not useful as a Service Command, however, because the command returns after displaying the state information.
Using SNAplus2 in a High Availability Environment Using SNAplus2 with MC/ServiceGuard and become active. If this parameter is not specified, 10 retries will be allowed. Any number between 0 and 600 (inclusive) can be specified. The return code of snapmon is 0 if the LS was active at some time while snapmon was running. Otherwise, a non-zero value is returned. One snapmon Service Command will be listed in the Package Control Script for each SNAplus2 LS that should be monitored.
Using SNAplus2 in a High Availability Environment Using SNAplus2 with MC/ServiceGuard capability. Following are four different ways in which applications can gain SNA network connectivity through an SNAplus2 server using a LAN. SNAplus2 Client/Server LAN Connections As described above, SNAplus2 can use either a standalone or a client/server configuration.
Using SNAplus2 in a High Availability Environment Using SNAplus2 with MC/ServiceGuard To protect against a failure of a server’s LAN adapter, you can configure a standby LAN adapter for the server. You can configure ServiceGuard to assign the primary LAN adapter’s IP address to the standby LAN adapter in the event of a failure. This way, TCP/IP connections from the client system to the server system would be maintained during the switch.
Using SNAplus2 in a High Availability Environment Using SNAplus2 with MC/ServiceGuard TN Server LAN Connections One application that can take advantage of both local LAN failover and floating IP addresses in an SNAplus2 network is TN3270. When you run TN3270, you specify a particular IP address to contact. When an SNAplus2 server is running the TN Server component, the IP address you specified can be the IP address of the SNAplus2 package.
Using SNAplus2 in a High Availability Environment Using SNAplus2 with MC/ServiceGuard Using the LAN to Access Standalone Servers When SNAplus2 is used in a standalone configuration, the LAN can still be used to access the server system. Although you do not run applications on SNAplus2 client systems, you access the applications running on the server from another computer system via the LAN.
Using SNAplus2 in a High Availability Environment Using SNAplus2 with MC/ServiceGuard 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. The example file that we used in our list of suggestions is /etc/cmcluster/sna/sna.cntl. See Table D-2, “Suggestions for Defining the SNAplus2 Package.
Using SNAplus2 in a High Availability Environment Using SNAplus2 with MC/ServiceGuard the SNAplus2 software. Insert this command in the customer_defined_halt_cmds section of the Package Control Script as follows: function customer_defined_halt_cmds { snap stop } After ServiceGuard stops the SNAplus2 package on the primary server, it will attempt to start the package on the backup server.
Using SNAplus2 in a High Availability Environment Using SNAplus2 with MC/ServiceGuard start the node on the backup server until SNAplus2 recognizes that the primary server is down. This time period can be lengthy (up to 30 minutes). Therefore, if the backup server is running SNAplus2, it is safest to completely stop the SNAplus2 software on the backup server before issuing the activation commands.
Using SNAplus2 in a High Availability Environment Using SNAplus2 with MC/ServiceGuard Figure D-11 Client/Server configuration using Token Ring LAN DLC Client Client Client Client LAN Primary HP-UX Server hp_pri Backup HP-UX Server hp_back Token Ring Adapter Token Ring Adapter Card 0 Card 0 Token Ring 3xxx Communications Controller IBM Host D12 QLLC If you are using QLLC links, both servers must have the same name configured in the X.25 interface card configuration file.
Using SNAplus2 in a High Availability Environment Using SNAplus2 with MC/ServiceGuard 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.
Using SNAplus2 in a High Availability Environment Using SNAplus2 with MC/ServiceGuard To create a network where multiple HP systems can share the same SDLC line, use a multidrop modem to connect the HP servers to the single SDLC line. The PSI adapter cards that support the SDLC protocol must have the same card numbers, as configured in the SDLC Port configuration screen.
Using SNAplus2 in a High Availability Environment Advanced Configuration Techniques 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 server s 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.
Using SNAplus2 in a High Availability Environment Advanced Configuration Techniques to add more intelligence to the Service in the Package Control Script that will allow you to attempt local recovery before informing ServiceGuard that a remote failover is necessary. Writing Your Own SNAplus2 Service Script By customizing the Service used in the Package Control Script, you can do the following: • Automatically attempt local restart of an SNAplus2 package that has failed.
Using SNAplus2 in a High Availability Environment Advanced Configuration Techniques commands in the script. The ability to add other SNAplus2 commands gives you a way to specify local recovery actions before allowing the script to end. For example, suppose you want to monitor a Token Ring LS called TRLS. If it fails, you first try to restart TRLS. If TRLS does not restart, you try to start an SDLC LS called SDLCLS.
Using SNAplus2 in a High Availability Environment Advanced Configuration Techniques # # Attempt to start the LS. If the LS is configured to # be initially active, the command will have no effect. # snapadmin start_ls, ls_name=TRLS # # Monitor the primary LS again to see if local restart # was successful. Only allow 30 seconds for the LS to # become active. # snapmon -i1 -r30 TRLS # # Since snapmon returned, the LS is no longer active. # Save the exit code.
Using SNAplus2 in a High Availability Environment Advanced Configuration Techniques quits trying to perform a local restart of the Token Ring LS, and attempts to start the SDLC LS. When that LS fails, the script exits, to allow ServiceGuard to perform a remote failover. Notice also that this solution does not provide the best level of application transparency. Since two different SNAplus2 LSs are being used on this server, each application must have the ability to access LUs that are configured for each LS.
Index Numerics 3270 emulation group additional configuration needs, 216 emulation group parameters 3270 permissions, 215 Group Name, 214 Sessions, 215 Style File, 214 Style file access, 215 emulation program description, 79 style file, 104 emulation user additional configuration needs, 216 emulation user parameters 3270 permissions, 215 Sessions, 215 Style File, 214 Style file access, 215 User Name, 214 emulator users configuration methods, 213 LU for TN server, 78 LU configuration, 169 message tracing Win
Index port facility, 58 network example, 44 network node, 30, 45 node, 75 node types, 43 route selection, 56 SNMP subagent, 341 APPN support parameter, 137 Arguments parameter, 191 AS/400 (Application System/ 400), 43 ASCII Administration Program, 129 Assigned LUs parameter, 173, 221 audit log file, 105 Auto-activated sessions parameter, 197 automatic network routing (ANR)See ANR, 53 B backup master server, 135 backup server, 87 basic conversation, 40 BIND request, 37 boundary node, 28 broadcast search, 52
Index additional configuration needs, 153 APPN, 60 configuration, 147 parameters, 148 configuration methods, 147 description, 43, 92, 93 topology information, 54 connectivity configuration overview, 143 description, 30 direct, 58 resources, 91 worksheets, 302, 306 control data, 37 control point (CP), 35 Control point alias parameter, 138 Control point name parameter, 137 conversation description, 39 security, 205 Conversation level security required parameter, 193 conversation security configuration method
Index additional configuration needs, 166 configuration, 233 description, 64, 77 worksheet, 322 DLUR PU configuration methods, 164 parameters DLUS Name, 165 Initially active, 165 PU ID, 165 PU Name, 165 Reactivate PU after failure, 166 DLUS description, 64 with DLUR, 77 DLUS Name parameter, 165 Document Content Architecture (DCA), 34 documentation set, 18 domain configuration file, 86, 103 description, 27, 85 name, 85 resources, 90, 97 domain resources, 135 Domain window, 117 downstream computer, 76 downst
Index HLLAPI, 32, 83 host, 28 host communication example configuration, 69 Host LS/DLUR PU parameter, 170, 179 host node, 27 HPR description, 53 HP-UX client *, 298 broadcast_attempt_count, 297 domain name, 296 lan_access_timeout, 297 server names, 299 server_lost_timeout, 298 HP-UX commands, 236 I IMS/VS (Information Management System/ Virtual Storage), 34 independent LU configuration, 176 description, 38, 94 Information Management System/Virtual Storage (IMS/VS), 34 Initial session limit parameter, 196 I
Index description, 16, 33 independent, 94 pool, 95 types, 33, 94 LU 0 description, 34 LU 1, 34 LU 2, 34 LU 3, 33 LU 6.2 configuration, 176 description, 33 LU alias parameter, 179, 190 LU in pool parameter, 171 LU name parameter, 169, 179 LU number parameter, 170, 179, 232 LU pool additional configuration needs, 173 configuration methods, 172 defining, 172 for TN server users, 79 parameters Assigned LUs, 173 Name, 173 viewing, 172 LU traffic parameter, 157 LU type 0-3, 94 6.
Index Domain window, 117 help, 127 invoking, 115 Node window, 119 resource items, 122 resource windows, 116 tool bar buttons, 123 using, 115 MS (Management Services), 45, 84 Multiple instances supported parameter, 190 multiple servers on a LAN, 87 multiple sessions, 38 multiple sessions parameter, 217 N Name parameter CPI-C symbolic destination, 200 link station, 156 LU pool, 173 mode, 196 security access list, 206 NAP (network access process), 254, 275 NAU (network accessible unit), 32 NetView changing si
Index path for SNAplus2 executable programs, 111 peer network, 26 node types, 30 route selection, 41 peer server, 87 peer-to-peer communicationsSee APPN, 25 peripheral node, 27 physical unit (PU)See PU, 32 physical unit control point (PUCP), 35 planning worksheets, 109 Poll address parameter, 157 Pool name parameter, 171, 217 pool, LU, 95 port additional configuration needs, 153 configuration methods, 147 overview, 147 parameters, 148 description, 92 parameters Adapter card number, 148 CN name, 152 Configu
Index configuration methods, 220 parameters Assigned LUs, 221 Run on computer, 220 UNIX group name, 221 UNIX user name, 221 Workstation name, 220 style file, 104 route, 41 Route incoming Allocates to running TP parameter, 190 route selection, 41, 53, 56 RTP description, 53 endpoints, 58 RU (request unit), 198 Run on computer parameter, 220 S SAP (service access point), 62 SAP number parameter, 159 SATF description, 92 direct connectivity, 58 in APPN network, 60 SDLC DLC, 91 port configuration, 147 workshee
Index start command, 112 stop command, 114 STREAMS components, 74 style file 3270 emulation program, 104 RJE workstation, 104 Style file access parameter, 215 Style File parameter, 214 subarea network description, 26 example, 28 node types, 27 route selection, 41 subarea node, 27 subarea SNA, 25 succinct logging, 105 Support TN3270E parameter, 227 Supports parallel sessions parameter, 185 synchronous data link control (SDLC)See SDLC, 91 system services control point (SSCP), 35 T target TP, 39, 187 task she
Index transport network, 42 troubleshooting, 105 TRS (topology and routing services), 53 type 2.0 node, 27 type 2.
Index Win32 client 3270 message tracing information, 270 admin_msg, 272 all_api, 268 API tracing information, 267 appc, 268 APPCLLU, 273 APPCTPN, 273 audit_file, 265 audit_file_wrap_size, 265 audit_logging_enabled, 263 backup_audit_file, 265 backup_error_file, 264 broadcast_attempt_count, 260 client/server tracing information, 271 client_start_timeout, 261 configuration information, 258 cpic, 269 CPI-C application data, 273 csv, 269 CSV application data, 274 CSVTBLG, 274 data, 272 datagram, 272 disabling,
