HP -UX SNAplus2 Administration Manual

Hewlett-packard owner's manual

page of 398

/ 398
Contents
Table of Contents
Bookmarks

Table of Contents

Quick Links

Download this manual

HP-UX SNAplus2

Administration Guide

Edition 2

J2740-90013

HP 9000 Networking

E1098

Printed in: United States

Table of Contents

Summary of Contents for HP HP-UX SNAplus2

Page 2: Legal Notices
Legal Notices The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and ﬁtness 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.
Page 3 ©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. ©copyright 1990, 1991, 1992 Cornell University ©copyright 1989-1991 The University of Maryland ©copyright 1988 Carnegie Mellon University ©copyright 1989-1997 Data Connection Limited...
Page 5: Table Of Contents
Contents Preface ..........15 Prerequisite Knowledge .
Page 6 Contents APPN Control Point ........47 Locating Resources .
Page 7 Contents Specifying the Path to SNAplus2 Programs ....111 Enabling SNAplus2 Servers ....... .112 Disabling SNAplus2 Servers .
Page 8 Contents Deﬁning DLUR PUs ........164 DLUR PU Conﬁguration Parameters .
Page 9 Contents Mode Conﬁguration Parameters ......196 Additional Conﬁguration ........199 Deﬁning CPI-C Side Information .
Page 10 Example of a UCF Command ....... 245 Output from HP-UX System Commands..... . 245 Canceling a Command .
Page 11 Win16 Client Initialization File (sna.ini) ..... .278 Managing HP-UX Clients ........295 Enabling SNAplus2 on HP-UX Clients .
Page 12 Contents CPI-C ..........330 5250 .
Page 13 Contents Specifying a Package IP Address......371 Customizing the SNAplus2 Package Control Script ... . .376 I/O Compatibility Constraints .
Page 14 Contents...
Page 15: Preface
Preface The HP-UX SNAplus2 Administration Guide provides information on enabling, conﬁguring, 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”.
Page 16 Provides information about the snappinstall utility and how it can be used to deﬁne an invokable TP. Appendix D, “Using SNAplus2 in a High Availability Environment.” Describes the high availability features of SNAplus2 and how it works with the HP MC/ServiceGuard product.
Page 17: Typographic Conventions
Option or ﬂag Variable representing a supplied value Return value 3270 key Keyboard keys Sample of Typography back up ﬁles before deleting HP-UX SNAplus2 Administration Guide /usr/spool/uucp/myfile.bkp /usr/spool/uucp/ snapadmin opcode; LU name 255; On node startup Status Services...
Page 18: 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.51 or...
Page 19: Publications For Administrators
HP-UX SNAplus2 General Information Provides an introduction to SNAplus2 and explains key product concepts and features. HP-UX SNAplus2 3270/3179G Users Guide Explains how to perform the following functions when you use 3270 emulation: • Starting and stopping 3270 emulation • Transferring ﬁles •...
Page 20: Publications For Programmers
Contains the information you need to write application programs using Common Programming Interface for Communications (CPI-C). HP-UX SNAplus2 3270 & TN3270 HLLAPI Programmers Guide Contains the information you need to write application programs using High-Level Language Application Program Interface (HLLAPI).
Page 21: Related Publications
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...
Page 23: Sna Terms And Concepts
SNA Terms and Concepts...
Page 24: Overview
SNA Terms and Concepts Overview Overview This chapter deﬁnes 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.”...
Page 25: Systems Network Architecture
SNA Terms and Concepts Systems Network Architecture Systems Network Architecture Systems Network Architecture (SNA) is an IBM data communication architecture that speciﬁes common conventions for communicating among a wide variety of hardware and software data communication products. This architecture consists of two kinds of deﬁnitions: formats that deﬁne the layout of messages exchanged by network components, and protocols that deﬁne the actions that network components take in response to messages.
Page 26: Basic Sna Concepts
• A mixed network is a network that supports both host-controlled communications and peer communications. NOTE HP-UX workstations running SNAplus2 can be part of a subarea network, a peer network, or both. SNA Nodes In SNA networks, a node is a system, workstation, or other device—with associated software components—that implements SNA protocols and...
Page 27 4 or 5 node. Type 2.0 nodes are referred to as dependent nodes. • Type 2.1 nodes can act as dependent nodes, but they can also communicate directly with other type 2.1 nodes. HP-UX workstations running SNAplus2 can function as type 2.1 or type NOTE 2.0 nodes. Chapter 1...
Page 28 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.
Page 29 In addition, SNAplus2 runs on HP-UX computers that can also be used for other tasks not related to SNA (unlike the terminal controller, which is used solely for communications with the host).
Page 30: Connectivity
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.
Page 31: Transaction Programs
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 ﬂow to a speciﬁc adjacent node. To establish communication between two adjacent nodes, one of the link stations must ﬁrst activate the link between the nodes.
Page 32: Network Accessible Units
SNAplus2 3270 emulation program • LUA API In addition, SNAplus2 includes the following proprietary programming interfaces (only for HP-UX systems): • MS (Management Services) API • NOF (Node Operator Facility) API For an overview of the APIs provided with SNAplus2, see “Application Programming Interfaces”.
Page 33 For example, a TP running on a workstation that uses the HP-UX operating system can communicate with a TP on an AS/400 computer as easily as it can with a TP on another HP-UX workstation, as long as both TPs use the same LU type.
Page 34 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.
Page 35: Control Points
For information about the data streams used by SNA logical units, refer NOTE 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.
Page 36: Sessions
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.
Page 37 CP-CP sessions Logical Unit Attributes for Sessions Logical units have attributes that determine how they interact during LU-LU sessions. These attributes are determined by the architecture of SNA. LUs can be primary or secondary, and dependent or independent. Primary and Secondary LUs. requests session activation by sending a BIND request to another LU: •...
Page 38 SNA Terms and Concepts Basic SNA Concepts dependent LU requester (DLUR) function enables session trafﬁc from dependent LUs to ﬂow 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. •...
Page 39: Conversations
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.
Page 40 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.
Page 41: Modes
A logical record consists of a two- or four-byte header starting with a two-byte length ﬁeld, 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.
Page 42: Class Of Service
SNA Terms and Concepts Basic SNA Concepts Class of Service Class of service (COS) is a deﬁnition 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.
Page 43: Basic Appn Concepts
Application System/400 (AS/400), the Enterprise System/9221 (ES/9221) running under Distributed Processing Program Executive/370 (DPPX/370), systems using Virtual Terminal Access Method (VTAM), and HP-UX servers running SNAplus2. APPN provides the following functions: • Support for APPN network nodes and end nodes as well as non-APPN peer nodes (see “APPN Node Types”)
Page 44 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.”...
Page 45 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.
Page 46 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.
Page 47: Appn Control Point
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.
Page 48: Locating Resources
SNA Terms and Concepts Basic APPN Concepts When setting up a workstation, you must deﬁne the CP name. The CP is also an LU that can support user sessions, and it can be the only LU deﬁned in your workstation, if you so choose. Locating Resources To support communication between TPs, SNAplus2 ﬁrst establishes a session between the logical units that control those TPs.
Page 49 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 speciﬁc link.
Page 50 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.
Page 51 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 deﬁned 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 conﬁgured as a partner LU on Node EN3.
Page 52 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: •...
Page 53: Session Routing
An APPN end node can also receive (and respond to) LOCATE search requests from its network node server to search for, or conﬁrm the continued presence of, speciﬁc 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.
Page 54 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.
Page 55 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. In addition, each of those nodes includes local topology information (except Node NNC, which does not have any local Chapter 1...
Page 56 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.
Page 57 • 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. •...
Page 58 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 trafﬁc if part of the route fails.
Page 59 SNA Terms and Concepts Basic APPN Concepts Figure 1-9 APPN Network Using a Shared-Access Transport Facility If Node EN1 has a link deﬁnition for each of the links in the network, it can establish a direct link to any node. The link deﬁnitions needed to support direct links between Node EN1 and every other node in the APPN network are shown in Figure 1-10, “Deﬁnitions Needed for Direct Links from Node EN1 to Every Node in an APPN Network.”...
Page 60 SNA Terms and Concepts Basic APPN Concepts Figure 1-10 Deﬁnitions 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 deﬁnitions are needed on the six nodes in this example.
Page 61 only a single link to an adjacent network node server and a link to the connection network, instead of conﬁguring every possible link to every node. To use the connection network feature, an APPN network must meet the following conditions: •...
Page 62 SNA Terms and Concepts Basic APPN Concepts Figure 1-11 Deﬁnitions 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 deﬁnitions is required. (Each end node needs two link deﬁnitions: one to a network node server and one to the virtual node.) Compared to the direct connectivity requirements for an APPN network that does not use a connection network (see Figure 1-10), you can have a...
Page 63 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.
Page 64: Accessing Subarea Networks From Appn Networks
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.
Page 65: Introduction To Snaplus2
Introduction to SNAplus2...
Page 66: Overview
Introduction to SNAplus2 Overview Overview This chapter provides an overview of SNAplus2 features and shows some of the basic conﬁgurations in which SNAplus2 can be used. It describes the major components of SNAplus2 and the SNA resources that are conﬁgured for and used by SNAplus2, and provides an overview of SNAplus2 administration responsibilities and tools.
Page 67: 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.
Page 68 Administration facilities 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”. SNAplus2 provides support for Windows clients (running Windows 3.11, Windows for Workgroups,...
Page 69: Example Conﬁgurations
Introduction to SNAplus2 Example Conﬁgurations Example Conﬁgurations 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.
Page 70 Introduction to SNAplus2 Example Conﬁgurations 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.
Page 71 Introduction to SNAplus2 Example Conﬁgurations Figure 2-3 SNAplus2 Node Providing PU Concentration and DLUR In Figure 2-4, “SNAplus2 Node Conﬁgured 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.
Page 72 Introduction to SNAplus2 Example Conﬁgurations Figure 2-4 SNAplus2 Node Conﬁgured 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 Conﬁguration.” The clients can access SNA resources through the servers.
Page 73 Introduction to SNAplus2 Example Conﬁgurations Figure 2-5 SNAplus2 Client/Server Conﬁguration These examples show the most basic ways in which you can conﬁgure SNAplus2 nodes. By combining nodes using these basic conﬁguration types, you can use SNAplus2 to support different types of communication within more complex networks.
Page 74: Snaplus2 Components
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. The 3270 emulation program, RJE workstation, APPC transaction programs, CPI-C applications, LUA applications, and the remote command facility (RCF) are user-space programs.
Page 75: Node Components
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;...
Page 76 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.
Page 77 Introduction to SNAplus2 SNAplus2 Components at the downstream computers are conﬁgured 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.
Page 78 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.
Page 79: User Applications
Introduction to SNAplus2 SNAplus2 Components SNAplus2 TN server supports all TN3270 client emulation programs that correctly implement the protocols deﬁned in RFCs 1123, 1576, 1646, and 1647. When a TN3270 program communicates with TN server, SNAplus2 identiﬁes the program by the TCP/IP address of the computer where the TN3270 program is running.
Page 80 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 conﬁguring support for 3270 emulation, see Chapter 8, “Conﬁguring User Applications.”...
Page 81: Application Programming Interfaces
The users of an RJE workstation can deﬁne workstation style ﬁles to supplement the SNAplus2 conﬁguration 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 ﬁle.
Page 82 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 speciﬁed 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.
Page 83 TP wherever it is running). For more information about TP conﬁguration, see “Deﬁning TPs”. For more information about the APPC API, refer to the HP-UX SNAplus2 APPC Programmers Guide. CPI-C API A CPI-C application uses the node's LU type 6.2 and mode resources to...
Page 84 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.
Page 85: Client/Server Support
A client can access one or more servers at the same time, and can run concurrent applications as needed. Servers must be HP-UX computers; clients can be running HP-UX or Windows. Servers and clients communicate across the SNAplus2 domain using TCP/IP.
Page 86 Introduction to SNAplus2 SNAplus2 Components conﬁguration. You can conﬁgure a node from any other computer in the domain, as long as the SNA software is running on the node where the conﬁguration is performed (whether or not the node being conﬁgured is started).
Page 87 Introduction to SNAplus2 SNAplus2 Components In a domain with multiple SNAplus2 servers, one server holds the master copy of the SNAplus2 domain conﬁguration ﬁle. This server is known as the master server. You can deﬁne other servers on the LAN to be backup servers.
Page 88 SNAplus2 LAN. The client relies on a server to provide the necessary conﬁguration information. Most of the details of using HP-UX client computers are the same as those for a server, except that the client has no node resources to deﬁne and manage.
Page 89: Windows Clients
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”): •...
Page 90: Snaplus2 Resources
Introduction to SNAplus2 SNAplus2 Resources SNAplus2 Resources The resources of the SNAplus2 system can be divided into the following types: • Node resources deﬁne the communications capabilities of a particular APPN node. The following are node resources: • Connectivity resources including the following: •...
Page 91: Connectivity 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: •...
Page 92 Introduction to SNAplus2 SNAplus2 Resources NOTE In the Motif administration program, DLCs are not shown directly. The information required for conﬁguring a DLC is displayed as part of the conﬁguration 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.
Page 93 Introduction to SNAplus2 SNAplus2 Resources The local node can have an explicit link station deﬁned 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 deﬁnitions, and results in a large volume of network topology information ﬂowing on the network.
Page 94: Session Resources
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...
Page 95 With DDDLU, LUs do not have to be conﬁgured statically at the host. (You must still deﬁne dependent LUs on the SNAplus2 node.) This reduces the initial conﬁguration 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 conﬁguration required.
Page 96: Directory Information
Introduction to SNAplus2 SNAplus2 Resources Default LUs. If you are conﬁguring type 6.2 dependent LUs for use with APPC or CPI-C applications, you may wish to deﬁne them as members of the default pool. The default pool can include LUs from more than one node.
Page 97: Domain Resources
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 deﬁnition is required for each such resource . Chapter 2...
Page 98: Snaplus2 Administration
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.
Page 99: Administration Tools
SNAplus2 includes the following administration tools: • Motif administration program (see “Motif Administration Program”). • Command-line administration program (see “Command-Line Administration Program”, or refer to the HP-UX SNAplus2 Administration Command Reference). • Service-point command facility (see “Remote Command Facility”). • Conﬁguration ﬁles (see “Conﬁguration Files”).
Page 100 Introduction to SNAplus2 SNAplus2 Administration • Querying the conﬁguration of deﬁned 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.
Page 101 The command-line administration program, snapadmin, enables you to issue commands to manage individual SNAplus2 resources. You can use snapadmin either directly from the HP-UX command prompt or from within a shell script. Commands can be issued to a speciﬁc SNAplus2 node to manage the node's resources, to the SNA network data ﬁle to manage master and...
Page 102 • snapadmin -h -d commandprovides detailed help for the named command, including a list of the conﬁguration parameters that can be speciﬁed with the command. Refer to the HP-UX SNAplus2 Administration Command Reference for more information. Remote Command Facility The remote command facility (RCF) provides the following facilities to...
Page 103 ﬁle directly using a standard ASCII text editor such as vi, or by means of a shell script using HP-UX utilities such as awk or sed. Any changes to conﬁguration ﬁles using a text editor must be made before starting SNAplus2.
Page 104 ﬁle can be modiﬁed using the menu interface of the 3270 emulation program. For more information about 3270 style ﬁles, refer to the HP-UX SNAplus2 3270/3179G Users Guide. RJE workstation style ﬁle Information about the customization of the RJE workstation is held in a style ﬁle, which can be set up...
Page 105: Diagnostic Tools
• For some error conditions, SNAplus2 sends a message to the HP-UX console to warn the operator, in addition to writing a problem message to the error log ﬁle.
Page 106 Refer to the HP-UX SNAplus2 Diagnostics Guide for information about SNAplus2 log messages, using SNAplus2 trace facilities, and interpreting trace ﬁles. For information about using the MS API, refer to the HP-UX SNAplus2 MS Programmers Guide. Simple Network Management Protocol Support The Simple Network Management Protocol (SNMP) is an industry-standard management protocol.
Page 107: Administering Snaplus2
Administering SNAplus2...
Page 108: Overview
Administering SNAplus2 Overview Overview The ﬁrst step in administering SNAplus2 is conﬁguring the node and its resources. Begin by planning for conﬁguration as described in “Planning for SNAplus2 Conﬁguration”. Before you can conﬁgure SNAplus2, you must enable the SNAplus2 software as described in “Enabling and Disabling SNAplus2 on the Local System”.
Page 109: Planning For Snaplus2 Conﬁguration
Administering SNAplus2 Planning for SNAplus2 Conﬁguration Planning for SNAplus2 Conﬁguration Before you make any conﬁguration 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 ﬁnd it useful to draw a diagram of any changes that you are making to the topology of the network.
Page 110: Task Sheets
Administering SNAplus2 Planning for SNAplus2 Conﬁguration Task Sheets The online help screens in the Motif administration program contain task sheets that provide guidance for speciﬁc conﬁguration tasks. The task sheets contain pointers to all of the help screens for the dialogs that you will use to enter the conﬁguration information.
Page 111: Enabling And Disabling Snaplus2 On The Local System
For UNIX This section explains how to enable and disable the SNAplus2 software on a HP-UX server or client. For information about enabling SNAplus2 on a Windows client, see For Windows Chapter 11, “Managing SNAplus2 Clients.”...
Page 112: Enabling Snaplus2 Servers
(either locally or from a remote SNAplus2 node). To enable the SNAplus2 software, enter the following command at the HP-UX command prompt: snap start [ -s ] [ -m kernel_memory_limit] [ -t ] You can also enable SNAplus2 automatically at system startup by inserting the snap start command into the startup ﬁle on your system.
Page 113: Disabling Snaplus2 Servers
ﬁle. The snap start command then ends with a nonzero exit code that indicates the nature of the error. For more information about exit code values, refer to the HP-UX SNAplus2 Diagnostics Guide. Disabling SNAplus2 Servers Disabling the SNAplus2 software on a server automatically stops the SNAplus2 node and its associated connectivity components.
Page 114 If SNAplus2 is disabled successfully, snap stop returns an exit code of 0. Any other exit code indicates that an error occurred and that the SNAplus2 software was not disabled. Refer to the HP-UX SNAplus2 Diagnostics Guide for more information about exit code values.
Page 115: Using The Motif Administration Program
Administering SNAplus2 Using the Motif Administration Program Using the Motif Administration Program The Motif administration program provides a user-friendly interface for conﬁguring SNAplus2. This program is the recommended tool for administering SNAplus2, because it guides you through the conﬁguration process and minimizes the information you need to provide to create a workable conﬁguration.
Page 116: Resource Windows
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. This guide uses the term window to describe Motif windows that display NOTE information about SNAplus2 resources. A window can contain one or more sections, or panes.
Page 117 Depending on the resources you select and the options you choose, the administration program can present additional resource windows, conﬁguration dialogs, or status logs. You will also see context dialogs that enable you to select a speciﬁc resource to conﬁgure, conﬁrmation dialogs that ask you to conﬁrm a choice, and message pop-ups that provide feedback or error information.
Page 118 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 conﬁgured, SNAplus2 prompts you to conﬁgure the node. The Domain window does not list SNAplus2 clients. Clients use the NOTE resources of SNAplus2 servers (SNA nodes) to access SNA resources.
Page 119 Add a node to the list of servers for the domain Remove the node from the list of servers for the domain Conﬁgure logging for all nodes in the domain Turn tracing for a speciﬁc node on or off Get information about domain resources If any servers in the local domain are running a back-level version of NOTE SNAplus2, those servers are listed in the Domain window, but they...
Page 120 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.
Page 121 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 speciﬁc link station or PU.
Page 122 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).
Page 123 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 conﬁgured before its child resources, and deleting the parent resource causes all its child resources to be deleted too.
Page 124: Resource Dialogs
Administering SNAplus2 Using the Motif Administration Program Many resources, such as ports and link stations, cannot be modiﬁed 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.
Page 125 Administering SNAplus2 Using the Motif Administration Program Figure 3-4 Sample Dialog Resource dialogs guide you through the conﬁguration process and supply default values whenever possible. For example, when you add a dependent LU, the Motif administration program automatically ﬁlls in the LU number ﬁeld with an available LU number on the link station you specify.
Page 126: Status Dialogs
Administering SNAplus2 Using the Motif Administration Program Most dialogs provide a Description ﬁeld; the information you enter there is displayed on the window where the resource is displayed. Press the Done button when you are ﬁnished, or the Cancel button to exit without changing the conﬁguration for the resource.
Page 127: Help Windows
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 conﬁguration task you need to perform.
Page 128 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. Chapter 3...
Page 129: Ascii Administration Program
The ASCII interface provides a subset of all functions availailable through the Motif Administration Program and can be used for conﬁguration and management of SNAplus2. The ASCII program is used through the HP ObAM environment. To start the program, enter: snap2adm Refer to the online help provided for more information on how to use the program.
Page 130: Using The Command-Line Administration Program
Administering SNAplus2 Using the Command-Line Administration Program Using the Command-Line Administration Program Command-line conﬁguration enables you to change all SNAplus2 conﬁguration parameters. You can use it to conﬁgure any of the resources that are available through the Motif administration program, and can set or change conﬁguration parameters that are not exposed in the Motif program.
Page 131 Returns information from the conﬁguration ﬁle on the query_* appropriate component, but does not modify the ﬁle. For complete information about command-line conﬁguration, refer to the HP-UX SNAplus2 Administration Command Reference. Chapter 3 Administering SNAplus2 Using the Command-Line Administration Program...
Page 132 Administering SNAplus2 Using the Command-Line Administration Program Chapter 3...
Page 133: Basic Conﬁguration Tasks
Basic Conﬁguration Tasks...
Page 134: Overview
Basic Conﬁguration Tasks Overview Overview This chapter provides an overview of conﬁguration tasks and explains how to conﬁgure the SNAplus2 node. It also explains how to conﬁgure master and backup servers when SNAplus2 is used in a client/server environment. Chapter 4...
Page 135: Conﬁguring Client/Server Functions
Basic Conﬁguration Tasks Conﬁguring Client/Server Functions Conﬁguring 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 conﬁgured on an individual node.
Page 136 Basic Conﬁguration Tasks Conﬁguring 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 conﬁguration 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.
Page 137: Conﬁguring The Node
Conﬁguring the Node The ﬁrst step in conﬁguring SNAplus2 on a system is to conﬁgure the local node. Node conﬁguration provides the basic information that the node needs in order to participate in an APPN network. You must conﬁgure the node before you can deﬁne connectivity or other resources for the node.
Page 138: Additional Conﬁguration
Basic Conﬁguration Tasks Conﬁguring the Node When you deﬁne the control point, SNAplus2 automatically deﬁnes 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.
Page 139: Conﬁguring Logging
Conﬁguring Logging SNAplus2 writes log messages describing abnormal events (and, optionally, normal events) to log ﬁles. When you try to diagnose a problem, the ﬁrst place to look is in the log ﬁles, because the log messages provide information about the cause of the problem and the action you should take.
Page 140 If your favorite editor is installed on the server, you can use it to view the log ﬁles. If not, you can use the standard HP-UX system utilities: View a ﬁle one page at a time. This utility is simple and easy to use but useful only if the log ﬁle is small.
Page 141 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. For more information about logging and tracing, refer to HP-UX SNAplus2 Diagnostics Guide. Chapter 4...
Page 142 Basic Conﬁguration Tasks Conﬁguring Logging Chapter 4...
Page 143: Deﬁning Connectivity Components
Deﬁning Connectivity Components...
Page 144: Overview
Deﬁning Connectivity Components Overview Overview In order for the SNAplus2 node to communicate with other nodes, you must conﬁgure connectivity with at least one adjacent node. A connecting link can be conﬁgured to carry dependent trafﬁc, independent trafﬁc, or both.You can have adapter cards for one or more link protocols installed in your computer.
Page 145 and they must be conﬁgured 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 conﬁgure can be greatly reduced.
Page 146 Deﬁning Connectivity Components Overview For information about conﬁguring PU concentration, see “Conﬁguring PU Concentration”. Chapter 5...
Page 147: Deﬁning Ports, Dlcs, And Connection Networks
Deﬁning Connectivity Components Deﬁning Ports, DLCs, and Connection Networks Deﬁning 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 speciﬁc link protocol, which can be any of the following: •...
Page 148: Port, Connection Network, And Dlc Conﬁguration Parameters
Deﬁning Connectivity Components Deﬁning Ports, DLCs, and Connection Networks Select Connectivity and New port from the Services menu on the Node window. Command-line administration program To conﬁgure a port: define_type_port To conﬁgure a DLC: define_type_dlc In these commands, type indicates the link protocol type (sdlc, tr, ethernet, fddi, qllc).
Page 149 This ﬁeld applies only if the adapter card can support more than one port. This ﬁeld 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.
Page 150 Deﬁning Connectivity Components Deﬁning Ports, DLCs, and Connection Networks Select a value that describes the role of the local node for link stations deﬁned 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.
Page 151 Deﬁning Connectivity Components Deﬁning 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 ﬁeld incorrectly, you will ﬁnd that the frames being received are all discarded and do not appear in any trace.
Page 152 Deﬁning Connectivity Components Deﬁning Ports, DLCs, and Connection Networks Consult your SNA network planner if you do not know how to conﬁgure 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.
Page 153: Additional Conﬁguration
NOTE The underlying stack is also conﬁgured with an address and accepts only calls that specify an address starting with the conﬁgured address. Any address conﬁgured on the port must start with the address conﬁgured on the stack; otherwise, calls accepted by the stack are subsequently rejected by the port.
Page 154: Deﬁning Link Stations
Deﬁning Connectivity Components Deﬁning Link Stations Deﬁning Link Stations To communicate with other nodes in an SNA network, you must conﬁgure the characteristics of a link station (LS) to an adjacent node in the SNA network. Before you can deﬁne a link station, you must deﬁne a port for the adapter (and link protocol) you are using.
Page 155: Link Station Conﬁguration Parameters
the local node. This dynamically created link station appears in the connectivity section of the Node window for the duration of the connection. To conﬁgure 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.
Page 156 The following parameters are required for all link stations, whether they support dependent trafﬁc, independent trafﬁc, 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.
Page 157 The type of LU trafﬁc to ﬂow over the link. This choice determines what other parameters are needed for link deﬁnition. The link station can be used for both independent and dependent LU trafﬁc. For this option, you must supply values for the ﬁelds described in “Parameters for Independent LU Trafﬁc”...
Page 158 Deﬁning Connectivity Components Deﬁning Link Stations • If you are conﬁguring 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.
Page 159 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. You can match the baud rate to the modem's baud rate by placing one of the following numbers (enclosed by parentheses) in front of the dial string: •...
Page 160 Deﬁning Connectivity Components Deﬁning 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 deﬁnition.
Page 161 Parameters for Independent LU Trafﬁc You need the following information to conﬁgure 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 qualiﬁed CP name of the remote node. If the remote system is a VTAM host, you can ﬁnd the network name (the ﬁrst eight characters of the fully qualiﬁed name) in the NETID parameter of the VTAM...
Page 162 Deﬁning Connectivity Components Deﬁning Link Stations slightly, so if you do know the type it is better to specify it. This also helps to ensure network conﬁguration consistency. You cannot choose Discover if the link station is activated on demand. If the local node is a LEN node, this ﬁeld does not apply.
Page 163: Additional Conﬁguration
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.
Page 164: Deﬁning Dlur Pus
Deﬁning Connectivity Components Deﬁning DLUR PUs Deﬁning 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.
Page 165 For each DLUR PU on the local node, specify a PU name. The name does not need to match the PU name conﬁgured on the host. DLUS Name The fully qualiﬁed 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.
Page 166: Additional Conﬁguration
Deﬁning Connectivity Components Deﬁning DLUR PUs Whether the DLUR PU is to be activated automatically after a failure (once the cause of the failure has been remedied). Additional Conﬁguration After conﬁguring DLUR, continue with the following conﬁguration tasks: • To conﬁgure LUs for DLUR, see “Deﬁning DLUR PUs”. •...
Page 167: Conﬁguring Dependent Lus
Conﬁguring Dependent LUs...
Page 168: Overview
Conﬁguring Dependent LUs Overview Overview This chapter provides instructions for conﬁguring LUs and LU pools to support user applications that use 3270, TN3270, RJE and LUA communications. To use these, you must conﬁgure dependent LUs. Before you can conﬁgure the resources described in this chapter, you must perform the following conﬁguration: •...
Page 169: Deﬁning Lu Types 0-3
Deﬁning LU Types 0–3 You must conﬁgure dependent LUs of types 0–3 to support communication with a host system. You can use the information in this section to deﬁne an LU to support 3270, RJE, or LUA. You can also deﬁne a range of LUs, to conﬁgure multiple LUs of the same type in a single operation.
Page 170 Conﬁguring Dependent LUs Deﬁning LU Types 0–3 The link station that provides the link to the host. The LU deﬁnition belongs to the link station you select. (If the dependent LU resides on a node that supports DLUR, this ﬁeld identiﬁes the DLUR PU that provides connectivity to the host.) LU numbers An LU number or range of LU numbers.
Page 171: Additional Conﬁguration
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 Conﬁguration After performing the LU type 0–3 conﬁguration, continue with the following conﬁguration tasks: •...
Page 172: Deﬁning Lu Pools
Conﬁguring Dependent LUs Deﬁning LU Pools Deﬁning LU Pools For 3270, TN3270, RJE,and LUA, you can deﬁne LU pools to simplify user conﬁguration and provide greater ﬂexibility in establishing host sessions. For example, you can deﬁne several 3270 LUs in a single LU pool, then conﬁgure multiple 3270 sessions using this LU pool.
Page 173: Lu Pool Conﬁguration Parameters
LU Pool Conﬁguration Parameters The following parameters are required for LU pool conﬁguration: Name A name to identify the LU pool. This ﬁeld 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.
Page 174 Conﬁguring Dependent LUs Deﬁning LU Pools Chapter 6...
Page 175: Conﬁguring Appc Communication
Conﬁguring APPC Communication...
Page 176: Overview
Conﬁguring APPC Communication Overview Overview APPC applications, 5250 emulation programs, and CPI-C applications all require that you conﬁgure APPC ﬁrst. 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 speciﬁed mode. If the applications use CPI-C, you may need to do additional CPI-C conﬁguration after conﬁguring APPC.
Page 177 Step 1. Deﬁne a local LU as described in “Deﬁning Local LUs”. Step 2. Deﬁne a remote node as described in “Deﬁning Remote Nodes”. Step 3. Deﬁne a partner LU as described in “Deﬁning Partner LUs”. Step 4. Deﬁne an invokable TP as described in “Deﬁning TPs”. Step 5.
Page 178: Deﬁning Local Lus
Conﬁguring APPC Communication Deﬁning Local LUs Deﬁning Local LUs In many cases, applications can use the local node's control point LU, which is automatically deﬁned when you conﬁgure the node. This is the default LU—if your application does not specify a particular LU, it can use this one.
Page 179: Local Lu Conﬁguration Parameters
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 Conﬁguration Parameters The following parameters are required for local LU conﬁguration: LU name The LU name of the local LU.
Page 180 Conﬁguring APPC Communication Deﬁning Local LUs • To deﬁne a remote node, see “Deﬁning Remote Nodes”. • To deﬁne a partner LU, see “Deﬁning Partner LUs”. • To deﬁne an invokable TP, see “Deﬁning TPs”. • To deﬁne a mode, see “Deﬁning Modes and Classes of Service”. •...
Page 181: Deﬁning Remote Nodes
Deﬁning Remote Nodes You must deﬁne a remote node (and the partner LUs on the node) in the following situations: • If the local node is a LEN node, you must deﬁne all of the remote nodes and any partner LUs on the remote node with which it communicates using APPC.
Page 182: Remote Node Conﬁguration Parameters
Conﬁguring APPC Communication Deﬁning Remote Nodes deﬁned 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 deﬁnition when the node is inactive.
Page 183: Deﬁning Partner Lus
Deﬁning 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 deﬁne the partner LU, because it can be dynamically located using APPN.
Page 184: Partner Lu Conﬁguration Parameters
Conﬁguring APPC Communication Deﬁning Partner LUs Partner LU Conﬁguration Parameters The following parameters are required for partner LU conﬁguration: Partner LU name The fully qualiﬁed LU name of the partner LU. This name must match the name that is conﬁgured at the remote node for this LU.
Page 185 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 ﬁeld applies when you deﬁne partner LU on a speciﬁc remote node or when you deﬁne a partner LU alias.
Page 186: Additional Conﬁguration
Conﬁguring APPC Communication Deﬁning Partner LUs Additional Conﬁguration After performing the partner LU conﬁguration, continue with the following conﬁguration tasks: • To deﬁne an invokable TP, see “Deﬁning TPs”. • To deﬁne a mode, see “Deﬁning Modes and Classes of Service”. •...
Page 187: Deﬁning Tps
Deﬁning TPs This section explains how to deﬁne an APPC TP. In most cases, you do not need to deﬁne TPs that run on the SNAplus2 system; but you do need to conﬁgure a TP deﬁnition in the following cases: APPC Characteristics Invokable TPs In this section, the phrase “Receive_Allocate”...
Page 188 Conﬁguring APPC Communication Deﬁning TPs For an invokable TP, you can also specify a timeout value, to limit the wait for an allocation request. (You can only conﬁgure this option using command-line administration.) SNAplus2 uses the invokable TP deﬁnition for the following purposes: •...
Page 189: Tp Invocation Parameters
The conﬁguration 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 deﬁnition and click on the Zoom button.
Page 190 Conﬁguring APPC Communication Deﬁning 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.
Page 191 ﬁle name is the same as the TP name parameter. If no path is speciﬁed, the default path for HP-UX systems is /etc/TPname, where TPname is the TP name parameter. For a Windows system, the system uses the usual Windows mechanism to locate the executable ﬁle.
Page 192: Tp Deﬁnition Parameters
SNAplus2. Group ID The group ID that SNAplus2 uses to start the TP. This must be a valid HP-UX group ID on the SNAplus2 computer. This line is optional. If it is not included, the default is sna.
Page 193 Select this option if an allocation request must include a valid user name and password (or an indicator that the password has already been veriﬁed). If you do not select this option, no veriﬁcation is required. Restrict access Select this option if the user name must be included on a security access list.
Page 194: Deﬁning Modes And Classes Of Service
Conﬁguring APPC Communication Deﬁning Modes and Classes of Service Deﬁning Modes and Classes of Service A mode speciﬁes 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.
Page 195 Table 7-1 Standard Mode and COS Names Mode Name (blank) #BATCH #INTER #BATCHSC #INTERSC SNASVCMG CPSVCMG CPSVRMGR QPCSUPP Once a mode has been conﬁgured, it can be used by any APPC or CPI-C application to activate a session between a local LU and a partner LU. An APPC application must specify the mode to use, but a CPI-C application can use CPI-C side information (which includes the mode name).
Page 196: Mode Conﬁguration Parameters
Conﬁguring APPC Communication Deﬁning Modes and Classes of Service Command-line administration program To deﬁne a mode, issue the following command: define_mode To change the default mode, issue the following command: define_defaults To deﬁne a class of service, issue the following command: define_cos Mode Conﬁguration Parameters...
Page 197 This ﬁeld 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.
Page 198 Conﬁguring APPC Communication Deﬁning 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.
Page 199: Additional Conﬁguration
The lower limit can be 0 or a value from 256 through the upper limit you specify. If the value in this ﬁeld is different from the RU size deﬁned 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.
Page 200: Deﬁning Cpi-C Side Information
Conﬁguring APPC Communication Deﬁning CPI-C Side Information Deﬁning CPI-C Side Information If you are supporting a CPI-C application that uses CPI-C symbolic destination names, you need to deﬁne 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.
Page 201 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 deﬁned). If the APPCLLU environment variable is set, the local LU information you supply is ignored, and the LU speciﬁed for the environment variable is used instead.
Page 202 ID that the application is deﬁned to accept. This user ID is not related to HP-UX login user IDs on either the local or the remote node. If the remote node is running SNAplus2, the user ID must be conﬁgured on the remote node using the Conversation Security Conﬁguration dialog.
Page 203: Additional Conﬁguration
Conﬁguring APPC Communication Deﬁning CPI-C Side Information Additional Conﬁguration After performing the CPI-C conﬁguration, continue with the following conﬁguration tasks: • To deﬁne APPC security, see “Conﬁguring APPC Security”. • To conﬁgure 5250 communication, see Chapter 8, “Conﬁguring User Applications.” Chapter 7...
Page 204: Conﬁguring Appc Security
LU name, a partner LU name, and a password. SNAplus2 uses the password to validate sessions between the local LU and partner LU. (The passwords are not related to HP-UX logon passwords.) To conﬁgure session security, use one of the following methods:...
Page 205: Conﬁguring Conversation Security
Conversation security is used to validate incoming conversations. Each deﬁnition consists of a user ID and a password. The user IDs and passwords are not related to HP-UX logon user IDs and passwords. To conﬁgure conversation security, use one of the following methods:...
Page 206: Conﬁguring A Security Access List
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 Conﬁguration After conﬁguring conversation security, you can conﬁgure 5250...
Page 207 Conﬁguring APPC Communication Conﬁguring APPC Security Additional Conﬁguration After performing the security access list conﬁguration, continue with the following conﬁguration tasks: • Conﬁgure TP access as described in “Deﬁning TPs”. Chapter 7...
Page 208 Conﬁguring APPC Communication Conﬁguring APPC Security Chapter 7...
Page 209: Conﬁguring User Applications
Conﬁguring User Applications...
Page 210: Overview
Conﬁguring User Applications Overview Overview This chapter provides instructions for conﬁguring 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 deﬁnitions, and user deﬁnitions. For 3270, RJE, LUA, and dependent APPC communication, you must conﬁgure dependent LUs.
Page 211 SNAplus2 provides 3270 emulation software that enables you to log on to and use SNA host systems from your HP-UX computer. Using this software, you can transfer ﬁles between the local and host computers, and control display and printer emulation sessions. You can customize some of the 3270 emulation features, such as key mapping and display attributes.
Page 212 Conﬁguring 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.
Page 213: Conﬁguring 3270 Users And Sessions
Conﬁguring 3270 Users and Sessions To enable 3270 communications, you must deﬁne emulator users or groups of users as described in “Conﬁguring 3270 Emulator Users”, and 3270 emulator sessions as described in “Conﬁguring 3270 Sessions”. Conﬁguring 3270 Emulator Users You must add emulator user deﬁnitions for each user who requires access to a 3270 emulator.
Page 214 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.
Page 215 If the user has a style ﬁle, enter the ﬁle name. If there is no style ﬁle, the user runs the emulation program with a default style. The style ﬁle determines the appearance and behavior of the emulation screens and keyboard for the emulator user.
Page 216: Conﬁguring 3270 Sessions
• To conﬁgure a single session, supply the following information: Session name The SNAplus2 HP-UX 3270 emulation program uses sessions with NOTE names in the range SESS0001–SESS0010. To deﬁne a session that is initially available to the user, choose a name in this range. If the user has remap permission, you can deﬁne a session to which the user can remap,...
Page 217 Display or Printer LU/Pool name • To conﬁgure multiple sessions, supply the following information: Session base name NOTE If you want to add several 3270 sessions for use with the SNAplus2 3270 emulation program, you can specify a base name of SESS. The ﬁrst 10 sessions are automatically given the names SESS0001–SESS0010.
Page 218: Conﬁguring 5250 Users
Conﬁguring User Applications Conﬁguring 5250 Users Conﬁguring 5250 Users To enable 5250 communications, you must deﬁne emulator users or groups of users as described in “Conﬁguring 5250 Emulator Users”. Conﬁguring 5250 Emulator Users You must add emulator user deﬁnitions for each user who requires access to a 5250 emulator.
Page 219 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 ﬁeld in the...
Page 220: Conﬁguring Rje Workstations
The name of the HP-UX system on which the RJE workstation runs. If you do not supply this value, the workstation can run on any computer.
Page 221: Additional Conﬁguration
In addition to conﬁguring RJE using SNAplus2, you need to create RJE workstation style ﬁles. RJE workstation style ﬁles control the operation of RJE workstations. On each HP-UX computer used for remote job entry, there is a workstation style ﬁle for each RJE workstation. For more information about RJE workstation style ﬁles, refer to the HP-UX...
Page 222 Conﬁguring User Applications Conﬁguring RJE Workstations Chapter 8...
Page 223: Conﬁguring Passthrough Services
Conﬁguring Passthrough Services...
Page 224: Overview
Conﬁguring 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.”...
Page 225: Conﬁguring Tn Server
Conﬁguring 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 deﬁned on the TN server. The TN server LUs establish sessions with LUs at the host to support TN3270 sessions for the clients.
Page 226: Conﬁguring Tn Server Access Records
Conﬁguring Passthrough Services Conﬁguring TN Server Conﬁguring 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 identiﬁes 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.
Page 227 The well-known port number for the TN3270 service is 23, but use of this port number is likely to clash with the HP-UX system TELNET service. SNAplus2 includes a utility to enable this port to be shared between the telnet and TN3270 daemons; that utility must be installed for both to work.
Page 228: Conﬁguring Tn Server Association Records
Conﬁguring Passthrough Services Conﬁguring TN Server If you want a TN3270 client to be able to use more than one LU or LU pool, deﬁne 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.
Page 229 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. Command-line administration program Issue the following command: define_tn3270_association TN Server Association Record Conﬁguration Parameters The following parameters are required for TN server association record conﬁguration:...
Page 230: Conﬁguring Pu Concentration
Conﬁguring Passthrough Services Conﬁguring PU Concentration Conﬁguring 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.
Page 231: Downstream Lu Conﬁguration Parameters
• Deﬁne the LUs on the local node that are used for communication with the host (the upstream LUs). Upstream LUs must be deﬁned using the LU Type 0-3 Conﬁguration dialog, specifying an LU type of unrestricted (unknown). To add the LUs, see “Deﬁning LU Types 0–3”.
Page 232: Additional Conﬁguration
Conﬁguring Passthrough Services Conﬁguring PU Concentration The LU number must match the LU number deﬁned on the downstream node. Contact your SNA network planner if you do not know what LU number to use. You can conﬁgure several LUs with consecutive LU numbers by deﬁning a range of LUs.
Page 233: Conﬁguring Dlur
Conﬁguring 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.
Page 234 Conﬁguring Passthrough Services Conﬁguring DLUR printer, RJE, or LUA. Depending on the requirements of the user applications supported by the LUs, you may also need to perform further conﬁguration. Chapter 9...
Page 235: Managing Snaplus2 From Netview
Managing SNAplus2 from NetView...
Page 236: Overview
This facility is described in “Using SPCF”. • UNIX command facility (UCF) enables a NetView operator to issue HP-UX operating system commands from NetView. This facility is described in “Using UCF”. Both of these functions can be accessed from the NetView console in the same way, and the overall syntax for issuing the commands is the same.
Page 237: Using The Host Netview Program
Step 2. If you are accessing the NetView program using 3270 emulation, start the 3270 emulation program and activate the session to the host. (Refer to HP-UX SNAplus2 3270/3179G Users Guide if necessary.) Step 3. Follow the instructions given to you by the host administrator for starting NetView and logging on.
Page 238: Netview Screen Display
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 ﬁnished issuing commands. NetView Screen Display The layout of the NetView screen varies with different versions of NetView at different hosts.
Page 239: Uppercase Characters And Escape Characters
NetView program does not. Instead, it translates all characters into uppercase before sending them to the HP-UX computer. Also, the host character set may not support the square bracket characters [ and ], which are required in some commands.
Page 240 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. Also, when using SPCF to issue administration commands, be aware that constant names such as LIST_FROM_NEXT are not case-sensitive.
Page 241: Using Spcf
SNAplus2 command-line administration program, in the same format as you would specify it to the snapadmin program on the HP-UX command line. Refer to HP-UX SNAplus2 Administration Command Reference for information about the syntax of administration commands and the parameters for individual commands.
Page 242: Examples Of Spcf Commands
For more information about setting up security options for SPCF, refer to the description of the define_rcf_access command in HP-UX SNAplus2 Administration Command Reference. Examples of SPCF Commands The following example shows how you could issue the define_lu_0_to_3 command using SPCF.
Page 243: Using Ucf
UCF is supported, SNAplus2 starts the UCF daemon program when the node is started. The UCF daemon processes HP-UX commands from the UCF by starting a new HP-UX shell for each command and running the command in that shell. If UCF support is not included, SNAplus2 does not start this program.
Page 244: Permitted Commands
(as described in “Overview of RCF Command Syntax”). 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 UCF. 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.
Page 245: Example Of A Ucf Command
-f ﬁlename 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 conﬁgured UCF user, the valid commands are limited by the access rights of the UCF user's login. In particular, root or superuser commands are not permitted.
Page 246: Canceling A Command
In addition to canceling the command that is currently executing, SNAplus2 cancels any commands that are queued after it. The command syntax is the same as for the HP-UX command, with the string ux-cancel instead of the command text. For example:...
Page 247: Ucf Security
It is intended that you use the normal security features provided by HP-UX to restrict the commands the UCF user can access, in order to permit only those commands you consider reasonable for use from UCF.
Page 248 Managing SNAplus2 from NetView Using UCF Chapter 10...
Page 249: Managing Snaplus2 Clients
Managing SNAplus2 Clients...
Page 250: 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.
Page 251: Client Networking Requirements
Client Networking Requirements Before you can run SNAplus2 on a client computer, you must conﬁgure 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 conﬂicts as described in “Setting Up IP Port Numbers”. In addition, you may wish to set clients up so that the TCP/IP connection is dropped automatically when the client is ﬁnished using SNAplus2, as described in “LAN Access Timeout”.
Page 252: Lan Access Timeout
Step 4. If your SNAplus2 domain includes Windows clients, add the same two lines to the services ﬁle on each Windows computer. The services ﬁle is in the same format as the HP-UX ﬁle, 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.
Page 253: Deﬁning Client Tps
When one of these events occurs while the TCP/IP connection is down, the client re-starts the attempt to contact a server, as described for the * and servername parameters in “HP-UX Client Network Data File (sna_clnt.net)”, “Servers”, or “[Servers]”. Incoming Attaches for invoked TPs on this client cannot be accepted while the TCP/IP connection is down;...
Page 254: Managing Win32 Clients
Managing SNAplus2 Clients Managing Win32 Clients Managing Win32 Clients SNAplus2 enables machines running Microsoft Windows 95 and For Windows 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.
Page 255: Enabling A 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 Conﬁguration”.
Page 256: Win32 Client Security
Win32 client security is enabled, the client software displays a pop-up message requesting a password. This password from the Registry is checked against the user names deﬁned to the HP-UX system on the server. If the Win32 client user does not specify a 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.
Page 257: Win32 Client Conﬁguration
Windows Program Registry. The Windows Program Registry contains SNA network information (similar to the information held in the client network data ﬁle on HP-UX clients). It also contains some additional conﬁguration information that is speciﬁc to Win32 clients.
Page 258 Managing SNAplus2 Clients Managing Win32 Clients rui = YES | NO nof = YES | NO ms = YES | NO MSG_tracing file1 = msg_trace_ﬁlename_1 file2 = msg_trace_ﬁlename_2 flip_size = ﬁlesize truncation_length = length fmi = YES | NO CS_tracing file1 = cs_trace_ﬁlename_1 file2 = cs_trace_ﬁlename_2 flip_size = ﬁlesize...
Page 259 The group_name value indicates the group name of the SNAplus2 user on this client. This name must match the SNAplus2 conﬁguration on servers, as follows: • If the client will be running 3270 or 5250 emulation, and you have set up the SNAplus2 conﬁguration 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...
Page 260 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”.
Page 261 This parameter is optional. The valid range is 5–65535. If it is not speciﬁed, 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.
Page 262 Managing SNAplus2 Clients Managing Win32 Clients server has been contacted, the client then tries using directed messages to one or more named servers (speciﬁed by the following lines of the ﬁle). • In situations where the client cannot reach any servers using UDP broadcasts, and must use directed messages, specify the name of the ﬁrst server it should try to contact.
Page 263 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 ﬁle. Logging The Logging subkey speciﬁes logging options for the client. These options can be used to specify client logging settings that override the logging options speciﬁed for the domain as a whole.
Page 264 Managing SNAplus2 Clients Managing Win32 Clients This parameter is optional. If it is not speciﬁed, 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.
Page 265 amount of disk space taken up by error log ﬁles is approximately twice the value of the error_ﬁle_wrap_size parameter. This parameter is optional. If it is not speciﬁed, the default is 1000000 (bytes). If you are logging error and audit messages to the same ﬁle, this parameter must be set to the same value as the audit_ﬁle_wrap_size parameter.
Page 266 To obtain more details of the cause of the log and any action required, you can use the snaphelp utility on a computer running HP-UX. Use verbose logging: each message in the log ﬁle includes a full listing of the message header...
Page 267 API_tracing The API_tracing subkey speciﬁes API tracing options for applications running on the client. For more information about tracing, refer to HP-UX SNAplus2 Diagnostics Guide. The tracing options are speciﬁed as follows: ﬁle1 The Registry data type of this value is REG_SZ.
Page 268 Managing SNAplus2 Clients Managing Win32 Clients The maximum size of the trace ﬁle. If two ﬁle names are speciﬁed, tracing switches between the two ﬁles when the current ﬁle reaches this size. If only one ﬁle name is speciﬁed, this parameter is ignored; the ﬁle size is not limited.
Page 269 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 speciﬁed, the default is NO. If the all_api parameter is set to YES, this parameter is ignored, and CPI-C messages are traced.
Page 270 MSG_tracing The MSG_tracing subkey speciﬁes 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 speciﬁed as follows: ﬁle1 The Registry data type of this value is REG_SZ.
Page 271 CS_tracing The CS_tracing subkey speciﬁes 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. The tracing options are speciﬁed as follows: ﬁle1 The Registry data type of this value is REG_SZ.
Page 272 Managing SNAplus2 Clients Managing Win32 Clients The Registry data type of this value is REG_SZ. The full path name of the second trace ﬁle. This parameter is optional; to indicate that tracing is to one ﬁle instead of two ﬁles, do not include this line. If both ﬁle1 and ﬁle2 are speciﬁed, tracing is to two ﬁles.
Page 273 Appl_Name variable with the application program's executable name (not including the .exe ﬁle name extension). For more information about CPI-C, refer to HP-UX SNAplus2 CPI-C Programmers Guide. The options are speciﬁed as follows: APPCLLU The Registry data type of this value is REG_SZ.
Page 274 It applies only to applications that use the CONVERT verb to perform character conversion with a user-deﬁned conversion table (Table G). For more information about the CONVERT verb, refer to HP-UX SNAplus2 CSV Programmers Guide. If no applications on the client use this function, you do not need to include this section.
Page 275: 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.
Page 276: Enabling A Win16 Client
TPs (APPC or CPI-C) that can run on the client; it is equivalent to the sna_tps ﬁle on a computer running the HP-UX operating system, as described in “Deﬁning TPs”. For more information about this ﬁle, see Appendix C, “Conﬁguring an Invokable TP Using snaptpinstall.”...
Page 277: Win16 Client Security
This password and the user name from the sna.ini ﬁle are checked against the user names deﬁned to the HP-UX system on the server. If the Win16 client user does not specify a Chapter 11 Managing SNAplus2 Clients...
Page 278: Win16 Client Initialization File (Sna.ini)
The Win16 client initialization ﬁle, sna.ini, contains SNA network information (similar to the information held in the client network data ﬁle on HP-UX clients). This ﬁle also contains some additional conﬁguration information that is speciﬁc to Win16 clients. This ﬁle is stored in the directory where the Windows software was installed (typically c:\windows);...
Page 279 Managing SNAplus2 Clients Managing Win16 Clients backup_error_file = backup_error_ﬁlename error_file_wrap_size = error_ﬁle_size audit_file = audit_ﬁlename backup_audit_file = backup_audit_ﬁlename audit_file_wrap_size = audit_ﬁle_size succinct_errors = YES | NO succinct_audits = YES | NO [API_tracing] file1 = trace_ﬁlename_1 file2 = trace_ﬁlename_2 flip_size = ﬁlesize truncation_length = length all_api = YES | NO appc = YES | NO...
Page 280 The user_name argument indicates the user name of the SNAplus2 user on this client. This name was speciﬁed during the client installation. It must match the SNAplus2 conﬁguration and the HP-UX conﬁguration on servers, as follows: • If the SNAplus2 system is set up to validate user names for Win16 clients (as described in “Win16...
Page 281 The group_name argument indicates the group name of the SNAplus2 user on this client. This name must match the SNAplus2 conﬁguration on servers, as follows: • If the client will be running 3270 or 5250 emulation, and you have set up the SNAplus2 conﬁguration 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...
Page 282 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”.
Page 283 [Servers] The [Servers] section of the ﬁle 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 ﬁnd 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...
Page 284 Managing SNAplus2 Clients Managing Win16 Clients attempts to contact the server speciﬁed in Server2 using a directed message. If this fails, it tries the server speciﬁed 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 speciﬁed by Server1 is unavailable.
Page 285 This parameter is optional. If it is not speciﬁed, 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: Record audit messages.
Page 286 Managing SNAplus2 Clients Managing Win16 Clients To log error and audit messages to a single ﬁle, specify the same ﬁle name for both this parameter and the backup_audit_ﬁle parameter. error_ﬁle_wrap_size The maximum size of the log ﬁle speciﬁed by error_ﬁle. When a message written to the ﬁle causes the ﬁle size to exceed this limit, SNAplus2 copies the current contents of the log ﬁle to the backup log ﬁle, then clears the log ﬁle.
Page 287 To obtain more details of the cause of the log and any action required, you can use the snaphelp utility on a computer running HP-UX. Use verbose logging: each message in the log ﬁle includes a full listing of the message header...
Page 288 [API_tracing] The [API_tracing] section of the ﬁle speciﬁes API tracing options for applications running on the client. For more information about tracing, refer to HP-UX SNAplus2 Diagnostics Guide. The tracing options are speciﬁed as follows: ﬁle1 The full path name of the trace ﬁle, or of the ﬁrst trace ﬁle if tracing is to two ﬁles (see the description of the...
Page 289 This parameter is optional. If it is not speciﬁed, the default is 100000 (bytes). truncation_length The maximum length, in bytes, of the information written to the trace ﬁle for each message. If a message is longer than this, SNAplus2 writes only the start of the message to the trace ﬁle, and discards the data beyond truncation_length.
Page 290 MS messages are traced. [MSG_tracing] The [MSG_tracing] section of the ﬁle speciﬁes options for tracing on Win16 client 3270 emulation programs. For more information about tracing, refer to HP-UX SNAplus2 Diagnostics Guide. The tracing options are speciﬁed as follows: ﬁle1 Chapter 11...
Page 291 The full path name of the trace ﬁle, or of the ﬁrst trace ﬁle if tracing is to two ﬁles (see the description of the ﬁle2 parameter). This parameter is required if you want to enable message tracing; you also need to set the fmi parameter.
Page 292 [CS_tracing] The [CS_tracing] section of the ﬁle speciﬁes 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. The tracing options are speciﬁed as follows: ﬁle1 The full path name of the trace ﬁle, or of the ﬁrst trace...
Page 293 Appl_Name variable with the application program's executable name (not including the .exe ﬁle name extension). For more information about CPI-C, refer to HP-UX SNAplus2 CPI-C Programmers Guide. The options are speciﬁed as follows:...
Page 294 CONVERT verb to perform character conversion with a user-deﬁned conversion table (Table G). For more information about the CONVERT verb, refer to HP-UX SNAplus2 CSV Programmers Guide. If no applications on the client use this function, you do not need to include this section.
Page 295: Managing Hp-Ux Clients
Managing HP-UX Clients Client information for a client running on a HP-UX system is stored in For UNIX the sna_clnt.net ﬁle, which is created when you install the SNAplus2 software on the client. That ﬁle must be present before you can enable SNAplus2 on the client.
Page 296: Hp-Ux Client Network Data File (Sna_Clnt.net)
(sna_clnt.net) The sna_clnt.net ﬁle deﬁnes 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 ﬁle on a Windows client, see Chapter 11, “Managing SNAplus2 Clients.”...
Page 297 If the client loses contact with a server and needs to reconnect, or if it has failed to contact a server using either broadcasts or named servers, this parameter speciﬁes the time in seconds for which the client waits Chapter 11 Managing SNAplus2 Clients Managing HP-UX Clients...
Page 298 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 speciﬁed timeout;...
Page 299 Managing SNAplus2 Clients Managing HP-UX Clients received no response, the client attempts to contact the ﬁrst 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 speciﬁed;...
Page 300 Managing SNAplus2 Clients Managing HP-UX Clients Chapter 11...
Page 301: Conﬁguration Planning Worksheets
Conﬁguration Planning Worksheets...
Page 302: Overview
HP-UX SNAplus2 Administration Command Reference. To gather all of the information needed to conﬁgure a node, you must complete worksheets in the following categories: Node conﬁguration...
Page 303: 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).
Page 304: Len Node
Conﬁguration Planning Worksheets Node Worksheets Motif Field Client/Server Conﬁguration: Not required for a standalone node. Conﬁguration server? Application Conﬁguration: See “User Application Support Worksheets”. LEN Node Complete this worksheet if the local node is a LEN node (a node that does not support APPN functions or a standalone system that communicates only with a host computer).
Page 305 Motif Field Client/Server Conﬁguration: Not required for a standalone node. Conﬁguration server? Application Conﬁguration: See “User Application Support Worksheets”. Appendix A Valid Entry/Notes Should the node act as a conﬁguration server, to store information about domain resources in the SNAplus2 LAN? Conﬁguration Planning Worksheets Node Worksheets Your...
Page 306: Connectivity Worksheets
Conﬁguration 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 conﬁgure more than one link station on a port. • “SDLC” • “Token Ring” •...
Page 307 Motif Field Link role 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 conﬁgured as the ADDR= parameter in the VTAM PU deﬁnition. On an AS/400 system, the poll address is the STNADR parameter of the Line Description.
Page 308 Conﬁguration Planning Worksheets Connectivity Worksheets Motif Field Activation By administrator On node startup On demand LU trafﬁc Independent only Dependent only Independent LU trafﬁc Remote node NETNAME.CPNAME (each 1–8 type A EBCDIC characters; optional) If the remote system is a VTAM host, you can ﬁnd the network name (the ﬁrst eight characters of the fully qualiﬁed name) in the NETID parameter of the VTAM Start...
Page 309 Motif Field Downstream PU 1–8 type A EBCDIC characters name Upstream DLUS NETNAME.LUNAME (each 1–8 type A name EBCDIC characters) Contact information Poll address For switched incoming ports, only conﬁgured on the port. 2 hexadecimal digits: • C1 for point-to-point •...
Page 310: Token Ring
Conﬁguration Planning Worksheets Connectivity Worksheets Token Ring Complete this worksheet to support connectivity using the token ring link protocol. Motif Field Token Ring SAP Dialog SNA port name Up to 8 characters Token ring card 0 to number_of_cards_minus_1 number Local SAP number Hexadecimal (multiple of 4) Initially active Select if needed...
Page 311 Motif Field Remote node NETNAME.CPNAME (each 1–8 type A EBCDIC characters; optional) If the remote system is a VTAM host, you can ﬁnd the network name (the ﬁrst eight characters of the fully qualiﬁed name) in the NETID parameter of the VTAM Start command.
Page 312: Ethernet
Conﬁguration Planning Worksheets Connectivity Worksheets Motif Field Contact information MAC address Hexadecimal digits If the remote end of this link is a VTAM host, you can ﬁnd its MAC address in the MACADDR= parameter of the VTAM Port deﬁnition. If you are conﬁguring a link to an AS/400 system, the MAC address is the ADPTADR parameter in the Line Description.
Page 313 Motif Field Ethernet SAP Dialog SNA port name Ethernet card number Local SAP number Initially active Deﬁne on connection network CN name Ethernet Link Station Dialog Link station ﬁelds Name SNA port name Activation LU trafﬁc Independent LU trafﬁc Appendix A Valid Entry/Notes Up to 8 characters 0 to number_of_cards_minus_1...
Page 314 Conﬁguration Planning Worksheets Connectivity Worksheets Motif Field Remote node Remote node type Dependent LU trafﬁc Remote node role Local node ID Remote node ID Downstream PU name Upstream DLUS name Valid Entry/Notes NETNAME.CPNAME (each 1–8 type A EBCDIC characters; optional) If the remote system is a VTAM host, you can ﬁnd the network name (the ﬁrst eight characters of the fully...
Page 315: Fddi
Motif Field Contact information MAC address SAP number FDDI Complete this worksheet to support connectivity using the FDDI link protocol. Appendix A Valid Entry/Notes Hexadecimal digits If the remote end of this link is a VTAM host, you can ﬁnd its MAC address in the MACADDR= parameter of the VTAM Port deﬁnition.
Page 316 Conﬁguration Planning Worksheets Connectivity Worksheets Motif Field FDDI SAP Dialog SNA port name FDDI card number Local SAP number Initially active Deﬁne on connection network CN name FDDI Link Station Dialog Link station ﬁelds Name SNA port name Activation LU trafﬁc Independent LU trafﬁc Valid Entry/Notes Up to 8 characters...
Page 317 Motif Field Remote node Remote node type Dependent LU trafﬁc Remote node role Local node ID Remote node ID Downstream PU name Upstream DLUS name Appendix A Valid Entry/Notes NETNAME.CPNAME (each 1–8 type A EBCDIC characters; optional) If the remote system is a VTAM host, you can ﬁnd the network name (the ﬁrst eight characters of the fully qualiﬁed name) in the NETID...
Page 318: Qllc (X.25)
Conﬁguration Planning Worksheets Connectivity Worksheets Motif Field Contact information MAC address SAP number QLLC (X.25) Complete this worksheet to support connectivity using the QLLC (X.25) link protocol. Valid Entry/Notes Hexadecimal digits If the remote end of this link is a VTAM host, you can ﬁnd its MAC address in the MACADDR= parameter of the VTAM Port...
Page 319 Motif Field QLLC Port Dialog SNA port name X.25 card number Port number Initially active Match incoming X.25 address Local X.25 sub-address QLLC Link Station Dialog Link station ﬁelds Name SNA port name Activation LU trafﬁc Independent LU trafﬁc Appendix A Valid Entry/Notes Up to 8 characters 0 to number_of_cards_minus_1...
Page 320 Conﬁguration Planning Worksheets Connectivity Worksheets Motif Field Remote node Remote node type Dependent LU trafﬁc Remote node role Local node ID Remote node ID Downstream PU name Upstream DLUS name Contact information Valid Entry/Notes NETNAME.CPNAME (each 1–8 type A EBCDIC characters; optional) If the remote system is a VTAM host, you can ﬁnd the network name (the ﬁrst eight characters of the fully...
Page 321 Motif Field Circuit type Channel ID Remote X.25 address Adapter/port number Subnet ID Appendix A Valid Entry/Notes Permanent virtual circuit Switched virtual circuit 1–4096 (only for PVC) Hexadecimal digits (only for SVC) [mp]n, where m is an optional adapter number and n is the port number Up to 4 characters Conﬁguration Planning Worksheets...
Page 322: Passthrough Services Worksheets
Conﬁguration 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 Node Conﬁguration: See “Node Worksheets”.
Page 323: Pu Concentration
Motif Field Initially active Reactivate PU after failure Local LU and Application Conﬁguration: See “User Application Support Worksheets”. You must conﬁgure local dependent LUs and any application support you require. PU Concentration Complete this worksheet if the local node is to support PU concentration. Motif Field Node Conﬁguration: See “Node Worksheets”.
Page 324: Tn Server
Conﬁguration Planning Worksheets Passthrough Services Worksheets Motif Field Downstream PU name LU numbers Upstream LU name TN Server Complete this worksheet if the local node is to support TN3270 clients. Motif Field Node Conﬁguration: See “Node Worksheets”. Connectivity Conﬁguration: See “Connectivity Worksheets” (conﬁgure for dependent LU trafﬁc to host).
Page 325 Motif Field TN3270 client address Support TN3270E TN3270 port and LUs TCP/IP port number Display LU Assigned Printer LU Assigned Allow access to speciﬁc TN Server Association Dialog Display LU Printer LU Appendix A Valid Entry/Notes Specify one of the following: •...
Page 326: User Application Support Worksheets
Conﬁguration 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.
Page 327 Motif Field LU number Member of default pool Local LU parameters Support syncpoint Disable password substitution Restrict to speciﬁc SSCP Remote Node Dialog: Only conﬁgure if the local node is a LEN node. Node's SNA network name Partner LU Dialog: Only required for communication with a LEN node, to deﬁne a partner LU alias, or if the local node is a LEN node.
Page 328 Conﬁguration Planning Worksheets User Application Support Worksheets Motif Field Location LS Routing Dialog: Only required if partner LU is located by link station. LU name LS name Partner LU name Use partner LU name as a wildcard Mode Dialog: Only required if you are using a nonstandard mode. Name COS name Session limits...
Page 329 Motif Field Maximum RU size Session Security Dialog: Only required if session security is required for sessions between a speciﬁc local and partner LU. Local LU Partner LU Password TP Invocation Dialog: Only required if local TP is to be started in response to requests from remote systems.
Page 330: Cpi-C
Conﬁguration Planning Worksheets User Application Support Worksheets Motif Field TP name Conversation level security required Restrict access Security access list Conversation type Sync level PIP allowed Conversation Security Dialog: Only required if conversation security is required for a local TP that is to be started in response to requests from remote systems. User ID Password CPI-C...
Page 331 Motif Field Node Conﬁguration: See “Node Worksheets”. Connectivity Conﬁguration: See “Connectivity Worksheets”. APPC Conﬁguration: See “APPC”. CPI-C Destination Dialog Symbolic destination name Local LU Partner LU Mode Partner TP name Security User ID Password 5250 Complete this worksheet if the local node is to support 5250 communications.
Page 332 Conﬁguration Planning Worksheets User Application Support Worksheets Motif Field Node Conﬁguration: See “Node Worksheets”. Connectivity Conﬁguration: See “Connectivity Worksheets” (conﬁgure for independent trafﬁc). APPC Conﬁguration: See “APPC”. Emulator User and Emulator Group Dialogs User name or group Valid user login or group name, or name <DEFAULT>...
Page 333 Motif Field LU numbers LU type LU in pool Pool name LU Pool Dialog Pool name LU lists Emulator User and Emulator Group Dialogs User name or group name Style ﬁle name Style ﬁle access Appendix A Valid Entry/Notes 1–255 (for a range, supply ﬁrst and last numbers) This value must match the LOCADDR parameter in the VTAM/NCP LU...
Page 334: Rje
Conﬁguration Planning Worksheets User Application Support Worksheets Motif Field 3270 permissions 3270 Session Dialog Single session or Multiple sessions Session name Session base name Session type Number of sessions LU name LU/Pool name Complete this worksheet if the local node is to support RJE communications with a host.
Page 335 Motif Field Node Conﬁguration: See “Node Worksheets”. Connectivity Conﬁguration: See “Connectivity Worksheets” (conﬁgure for dependent trafﬁc). LU Type 0–3 Dialog LU name Host LS/DLUR PU LU numbers LU type LU in pool Pool name RJE Workstation Dialog Workstation name Run on computer UNIX user name UNIX group name Assigned LUs...
Page 336: Lua
Conﬁguration Planning Worksheets User Application Support Worksheets Complete this worksheet if the local node is to support LUA applications. Motif Field Node Conﬁguration: See “Node Worksheets”. Connectivity Conﬁguration: See “Connectivity Worksheets” (conﬁgure for dependent trafﬁc). LU Type 0–3 Dialog LU name 1–8 type A EBCDIC characters (or 1–5 characters for a base name for a range of LUs)
Page 337: Appn Network Management Using The Simple Network Management Protocol
APPN Network Management Using the Simple Network Management Protocol...
Page 338: Overview
APPN Network Management Using the Simple Network Management Protocol Overview Overview This appendix brieﬂy 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. Appendix B...
Page 339: Introduction To Snmp
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 speciﬁes and structures the information that is exchanged between managing and managed systems.
Page 340 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).
Page 341: Snaplus2 Appn 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 deﬁned in RFC 1593. The subagent uses the services of the SNMPD daemon, which communicates with a management application using TCP/IP.
Page 342: Appn Management Information Base (Mib)
APPN Network Management Using the Simple Network Management Protocol APPN Management Information Base (MIB) APPN Management Information Base (MIB) The APPN MIB is deﬁned by informational RFC 1593. The ASN.1 representation of the APPN MIB is located in the ﬁle named /etc/opt/sna/mib/appn.my, which also provides a more detailed description of the APPN MIB objects.
Page 343: Conﬁguring An Invokable Tp Using Snaptpinstall
Conﬁguring an Invokable TP Using snaptpinstall...
Page 344: Overview
-r -t TP_name This command removes the entry that has both the same TP name and (on HP-UX machines) the same LU alias. The LU alias applies only on HP-UX machines; omit that parameter when removing a TP deﬁnition from a Windows client.
Page 345: File Format For Snaptpinstall
TP name, the TP type, and the timeout value; the other parameters apply only to automatically started TPs. For UNIX On HP-UX machines, SNAplus2 returns an error message if you enter an invalid parameter. For Windows On Window machines, SNAplus2 ignores invalid parameters.
Page 346 Conﬁguring 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 speciﬁed as an ASCII string, enclosed in double quotation marks (for example, ["TPNAME1"]).
Page 347 Conﬁguring 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 ﬁnishes running and can be restarted. An incoming Allocate request is routed to this TP only if it is received by an LU that is conﬁgured to route incoming Allocate requests to this computer.
Page 348 Conﬁguring an Invokable TP Using snaptpinstall File Format for snaptpinstall TIMEOUT USERID For UNIX If you use NON-QUEUED, more than one copy of the TP can be running at a time. If the TP writes to ﬁles on the Windows computer, you need to ensure that different copies of the TP do not overwrite each other's ﬁles.
Page 349 SNAplus2. GROUP Specify the group ID that SNAplus2 uses to start the TP. This must be a valid HP-UX group ID on the SNAplus2 computer; it can be up to 64 characters, unless your HP-UX conﬁguration restricts group names to fewer characters.
Page 350 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. If you need to permit the TP to determine the correct LU alias at run-time...
Page 351 SECURITY_TYPE SERVICE_NAME End of Section Note the following points about the format of these entries: • You can include a comment line by including # as the ﬁrst character of the line; SNAplus2 then ignores this line. SNAplus2 also ignores completely blank lines.
Page 352 Conﬁguring 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). •...
Page 353: Using Snaplus2 In A High Availability Environment
Using SNAplus2 in a High Availability Environment...
Page 354: Overview
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. Appendix D...
Page 355: What Is High Availability
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.
Page 356 APPC transaction program. Many software and hardware components deliver SNA network connectivity to the end user in this picture. Since the HP 9000 server plays such a critical role in maintaining the network connectivity for multiple end users, it is important to minimize the impact of component failures in and around the server.
Page 357 Other failures to consider include power failures, IBM mainframe outages, client system failures, etc. This appendix focus es on what can be done to reduce the impact of failures in and around the HP 9000 server system. Speciﬁcally, it discuss es the high availability features built into SNAplus2 and how those features can be enhanced and complemented with the use of HP’s MC/ServiceGuard product.
Page 358: Snaplus2 High Availability Features
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 conﬁgurations. LU Pools for 3270, 3179G, and LUA One of the most signiﬁcant fault-tolerant feature s of SNAplus2 is the LU Pool feature.
Page 359: Client/Server Conﬁguration
Figure D-2 LU Pools 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 speciﬁc LU in the pool. Within the SNAplus2 conﬁguration above, the LU pool contains LUs associated with two LSs —...
Page 360 SNAplus2 application running on a client system. First, the application can be conﬁgured to use multiple LUs, and those LUs can be spread across multiple HP 9000 servers. If the ﬁrst LU is unavailable, the application can request a different one. LU pools, if they contain LUs that use multiple SNAplus2 LSs , can be used in this fashion.
Page 361 Applications using multiple servers The second way an application can use multiple servers is to have one SNAplus2 conﬁguration that is used by multiple HP 9000 systems. For example, suppose two server systems are connected to an SNA network through Token Ring ports . The SNAplus2 conﬁguration contains information about the deﬁnition of SNAplus2 nodes, ports , and LSs .
Page 362 Using SNAplus2 in a High Availability Environment SNAplus2 High Availability Features Table D-1 Component System Name SNAplus2 Node SNAplus2 Port SNAplus2 LS SNAplus2 Local LU aliases The above example will be used throughout this appendix to explain NOTE many different aspects of high availability systems. In this example, nine LUs are used by APPC production applications that run on the client systems.
Page 363 Step 2. The SNAplus2 LS HALS is started on the backup server, if it is conﬁgured to be operator started, using the command snapadmin start_ls, ls_name=HALS. Appendix D Using SNAplus2 in a High Availability Environment Client Client Primary HP-UX Server hp_pri Production Configuration Node...HANODE LS...HALS Port...HAPORT LUs...HALUO1...HALU09 Token Ring...
Page 364 Later sections describe how the MC/ ServiceGuard product can automate the switch from a primary to a backup server even when unexpected failures occur. Client Client Primary HP-UX Server hp_pri Temporarily Out of Service Token Ring Communications Controller...
Page 365: Using Snaplus2 With Mc/Serviceguard
(like SNAplus2 ) into packages. (See Managing MC/ServiceGuard, HP Part No. B3936-90003). Using SNAplus2 in a ServiceGuard cluster protects against many of the unexpected failures that can interrupt SNA network access to end users. The strategy employed by ServiceGuard is to prevent a single failure from disrupting service by providing software and hardware redundancy.
Page 366: Creating The Ha Snaplus2 Package
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.
Page 367 SNA network connectivity. Step 3. List the SNAplus2 LSs that must be highly available. The SNAplus2 LSs are what will be monitored by ServiceGuard to determine if the HP 9000 server is providing SNA network connectivity. If all of the highly available SNAplus2 LSs are active, the server is providing SNA network connectivity.
Page 368: Snaplus2 Package
To integrate SNAplus2 into your ServiceGuard cluster, an SNAplus2 package must be deﬁned. Deﬁning an SNAplus2 package tells ServiceGuard that the SNAplus2 software on the HP 9000 server must be highly available, and access to the SNA network is mission critical.
Page 369: Specifying The Service Command
Script Location IP Address Specifying the Service Command The Service Command starts a Service, which is an HP-UX process that ServiceGuard monitors. The termination of the process indicates to ServiceGuard that the package has failed, and that the package needs to be migrated to another system.
Page 370 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.
Page 371: Specifying A Package Ip Address
and become active. If this parameter is not speciﬁed, 10 retries will be allowed. Any number between 0 and 600 (inclusive) can be speciﬁed. The return code of snapmon is 0 if the LS was active at some time while snapmon was running.
Page 372 As described above, SNAplus2 can use either a standalone or a client/server conﬁguration. In a client/server conﬁguration, you run applications on client systems (HP 9000s or PCs) that access an SNAplus2 server through the slim process running on the server system.
Page 373 If an SNA LAN adapter fails, SNA sessions will be disconnected and the normal package failure recovery will take place. Appendix D Using SNAplus2 in a High Availability Environment Using SNAplus2 with MC/ServiceGuard HP 9000 Server Token Ring LAN 3xxx...
Page 374 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 ﬂoating 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 speciﬁed can be the IP address of the SNAplus2 package.
Page 375 Using the LAN to Access Standalone Servers When SNAplus2 is used in a standalone conﬁguration, 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.
Page 376: Customizing The Snaplus2 Package Control Script
Using SNAplus2 in a High Availability Environment Using SNAplus2 with MC/ServiceGuard Customizing the SNAplus2 Package Control Script The last step in deﬁning 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 ﬁle that we used in our list of suggestions is /etc/cmcluster/sna/sna.cntl.
Page 377 In addition, you must make sure the following requirements are satisﬁed: • The remote SNA system does not restrict which HP 9000 server can activate the same PU conﬁguration. For example, the remote SNA system allows communication from any MAC address in a Token Ring LAN.
Page 378: I/O Compatibility Constraints
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.
Page 379 QLLC Port conﬁguration screen: Appendix D Using SNAplus2 in a High Availability Environment Client Client Primary HP-UX Server hp_pri Token Ring Adapter Card 0 Token Ring 3xxx Communications Controller Host...
Page 380 SDLC Allowing multiple servers to use the same SDLC conﬁguration is more difﬁcult than with the other link types because SDLC DLCs are often dedicated lines from one HP 9000 server to a remote SNA system. Client Client Primary HP-UX Server hp_pri...
Page 381 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 conﬁgured in the SDLC Port conﬁguration screen.
Page 382: Advanced Conﬁguration Techniques
The following advanced conﬁguration 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.
Page 383: Writing Your Own Snaplus2 Service Script
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: •...
Page 384 Using SNAplus2 in a High Availability Environment Advanced Conﬁguration 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 ﬁrst try to restart TRLS.
Page 385 # 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.
Page 386 Using SNAplus2 in a High Availability Environment Advanced Conﬁguration 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.
Page 387 Index Index Numerics 3270 emulation group additional conﬁguration needs emulation group parameters 3270 permissions Group Name Sessions Style File Style ﬁle access emulation program description style ﬁle emulation user additional conﬁguration needs emulation user parameters 3270 permissions Sessions Style File Style ﬁle access User Name emulator users...
Page 388 RCF commands CICS (Customer Information Control System) Circuit type parameter class of service (COS)See COS client ARGUMENTS parameter deﬁning TP on deﬁnition HP-UX management invokable TP conﬁguration managing network data ﬁle networking requirements PATH parameter SECURITY_TYPE parameter SERVICE_NAME parameter SHOW parameter...
Page 389 Index additional conﬁguration needs APPN conﬁguration parameters conﬁguration methods description topology information connectivity conﬁguration overview description direct resources worksheets control data control point (CP) Control point alias parameter Control point name parameter conversation description security Conversation level security required parameter conversation security conﬁguration methods parameters...
Page 390 Upstream LU name DPPX/370 (Distributed Processing Program Executive/370) dynamic deﬁnition of dependent LUs (DDDLU)See DDDLU EN (end node)See end node enabling the SNAplus2 software HP-UX client on a server problems during initialization Win16 client Win32 client end node APPN description...
Page 391 Index HLLAPI host host communication example conﬁguration Host LS/DLUR PU parameter host node description HP-UX client broadcast_attempt_count domain name lan_access_timeout server names server_lost_timeout HP-UX commands IMS/VS (Information Management System/ Virtual Storage) independent LU conﬁguration description Information Management System/Virtual Storage (IMS/VS)
Page 392 Index description independent pool types LU 0 description LU 1 LU 2 LU 3 LU 6.2 conﬁguration description LU alias parameter LU in pool parameter LU name parameter LU number parameter LU pool additional conﬁguration needs conﬁguration methods deﬁning for TN server users parameters Assigned LUs Name...
Page 393 (NAP) network accessible unit (NAU) network addressable unit network data ﬁle client description HP-UX client network management data network node directory sample conﬁguration network node server NN (network node)See network node node additional conﬁguration needs conﬁguration ﬁle...
Page 394 Index path for SNAplus2 executable programs peer network node types route selection peer server peer-to-peer communicationsSee APPN peripheral node physical unit (PU)See PU physical unit control point (PUCP) planning worksheets Poll address parameter Pool name parameter pool, LU port additional conﬁguration needs conﬁguration methods overview...
Page 395 Simple Network Management Protocol (SNMP)See SNMP APPN concepts basic concepts description hierarchical structure layers network network data ﬁle description HP-UX client Win16 client Win32 client network types subarea SNA port name parameter sna.ini ﬁle sna_clnt.net ﬁle snap2adm command snapadmin program...
Page 396 Index start command stop command STREAMS components style ﬁle 3270 emulation program RJE workstation Style ﬁle access parameter Style File parameter subarea network description example node types route selection subarea node subarea SNA succinct logging Support TN3270E parameter Supports parallel sessions parameter synchronous data link control (SDLC)See SDLC...
Page 397 Index transport network troubleshooting TRS (topology and routing services) type 2.0 node type 2.1 node type 4 node type 5 node access to ﬁles canceling a command command syntax daemon program description output permissions permitted commands sample command security user user name using valid commands...
Page 398 Index Win32 client 3270 message tracing information admin_msg all_api API tracing information appc APPCLLU APPCTPN audit_ﬁle audit_ﬁle_wrap_size audit_logging_enabled backup_audit_ﬁle backup_error_ﬁle broadcast_attempt_count client/server tracing information client_start_timeout conﬁguration information cpic CPI-C application data CSV application data CSVTBLG data datagram disabling domain enabling error_ﬁle error_ﬁle_wrap_size exception_logging_enabled...

HP -UX SNAplus2 Administration Manual

Preface

1 SNA Terms and Concepts

2 Introduction to Snaplus2

3 Administering Snaplus2

4 Basic Conﬁguration Tasks

5 Deﬁning Connectivity Components

6 Conﬁguring Dependent Lus

7 Conﬁguring APPC Communication

8 Conﬁguring User Applications

9 Conﬁguring Passthrough Services

10 Managing Snaplus2 from Netview

11 Managing Snaplus2 Clients

Conﬁguration Planning Worksheets

APPN Network Management Using the Simple Network Management Protocol

Conﬁguring an Invokable TP Using Snaptpinstall

Using Snaplus2 in a High Availability Environment

Quick Links

Related Manuals for HP HP-UX SNAplus2

Summary of Contents for HP HP-UX SNAplus2