Instruction/ maintenance manual of the product HP-UX SNAplus2 HP (Hewlett-Packard)
Go to page of 398
HP-UX SNAplus2 Administration Guide Edition 2 J2740-90013 HP 9000 Networking E1098 Printed in: United States © Copyright 1998 © Hewlett-P ackard Company , 1998.
2 Legal Notices The information in this document is subject to change without notice . Hewlett-P ac kard makes no warranty of any kind with regard to this manual, including , but not limited to , the implied warranties of merchantability and fitness f or a particular purpose .
3 ©copyright 1980, 1984, 1986 Novell, Inc. ©copyright 1986-1992 Sun Microsystems , Inc. ©copyright 1985-86, 1988 Massachusetts Institute of T echnology . ©copyright 1989-93 The Open Software F oundation, Inc. ©copyright 1986 Digital Equipment Corporation.
4.
Contents 5 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Prerequisite Knowledge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 About This Book. . . . . . .
6 Contents APPN Control P oint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Locating Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Session Routing . . . . . . . . . . .
Contents 7 Specifying the P ath to SNAplus2 Programs . . . . . . . . . . . . . . . . . . . . 111 Enabling SNAplus2 Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Disabling SNAplus2 Servers . . . . . . . . . . . . . . . . .
8 Contents Defining DLUR PUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 DLUR PU Configuration P arameters . . . . . . . . . . . . . . . . . . . . . . . . 164 Additional Configuration . . . . . . . . . . . . .
Contents 9 Mode Configuration P arameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Additional Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Defining CPI-C Side Information . . . . . . .
10 Contents Additional Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Configuring DLUR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 10. Managing SNAplus2 from NetView Overview .
Contents 11 Disabling SNAplus2 for a Win32 Client . . . . . . . . . . . . . . . . . . . . . . . 255 Win32 Client Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 Win32 Client Configuration . . . . . . . . . . . .
12 Contents CPI-C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 5250 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 3270 . . . . . . .
Contents 13 Specifying a P ackage IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371 Customizing the SNAplus2 P ackage Control Script . . . . . . . . . . . . . 376 I/O Compatibility Constraints . . . . . . . . . . . . . . . . . .
14 Contents.
15 Preface The HP-UX SNAplus2 Administration Guide provides information on enabling, configuring , and managing SNAplus2. Prerequisite Knowledge Before reading this manual, you should have a knowledge of SNA and APPN concepts . F or a list of books that provide this information, see “Related Publications”.
16 Explains how to configure connectivity for the SNAplus2 node. Chapter 6, “Configuring Dependent LUs . ” Explains how to configure dependent LUs (logical units) for LU types 0–3 and LU pools. Chapter 7, “Configuring APPC Communication. ” Explains how to configure APPC (advanced program-to-program communications).
17 Typographic Conventions The typographic styles used in this document are shown in T able 1. T able 1 Typographic Conventions Special Element Sample of Typography Emphasized words back up files bef ore deleting Document title HP-UX SNAplus2 Administration Guide File or path name /usr/spool/uucp/myfile.
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 c lient, which runs on the Microsoft NT (V ersion 3.
19 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 f.
20 Explains how to enable, configure , and manage SNAplus2. This guide provides information about SNA concepts , and an overview of the features provided by SNAplus2. It describes how to configure and manage SNAplus2 using the Motif administration program and provides guidance for users of the SNAplus2 command-line administration program.
21 Contains the information you need to write application programs using the Common Service V erbs (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.
22.
23 1 SNA T erms and Concepts.
24 Chapter 1 SNA T erms and Concepts Overview Overview This chapter defines Systems Network Architecture (SNA) terms and concepts that are important to understanding and using SNAplus2. F or information about SNAplus2 and its capabilities , see Chapter 2, “Introduction to SNAplus2.
Chapter 1 25 SNA T erms and Concepts Systems Network Ar chitecture Systems Network Architecture Systems Network Architecture (SNA) is an IBM data communication architecture that specifies common conventions for communicating among a wide variety of hardware and softw are data communication products .
26 Chapter 1 SNA T erms and Concepts Basic SNA Concepts Basic SNA Concepts SNA defines the standards , protocols, and functions used by devices—from mainframes to terminals—to enable them to communicate with each other in SNA networks .
Chapter 1 27 SNA T erms and Concepts Basic SNA Concepts Each node manages its end of the network communication paths , and uses SNA protocols to communicate with the node at the other end of each path.
28 Chapter 1 SNA T erms 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.
Chapter 1 29 SNA T erms and Concepts Basic SNA Concepts Figure 1-1 SNA Subarea Network The root of the tree (at the top of the diagram) is the computer controlling the network.
30 Chapter 1 SNA T erms and Concepts Basic SNA Concepts Node Types in a P eer Network P eer 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 .
Chapter 1 31 SNA T erms and Concepts Basic SNA Concepts Each node connected to a network has one or more link stations , which are the hardware and softw are in a node that control data flow to a specific adjacent node.
32 Chapter 1 SNA T erms and Concepts Basic SNA Concepts • CPI-C (Common Programming Interface for Communications)—LU type 6.2 only • CSV (Common Service V erb) API • HLLAPI (high-level languag.
Chapter 1 33 SNA T erms and Concepts Basic SNA Concepts NO TE On type 2.1 nodes (which can be APPN nodes), the control point provides PU services in addition to providing other services (see “Control P oints”).
34 Chapter 1 SNA T erms and Concepts Basic SNA Concepts F or 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 .
Chapter 1 35 SNA T erms and Concepts Basic SNA Concepts Operating System) use LU 0. Current releases of these products also support LU 6.2 communication, which is the preferred protocol for new applications. NO TE F or information about the data streams used by SNA logical units, refer to Systems Network Arc hitecture T echnical Reference .
36 Chapter 1 SNA T erms and Concepts Basic SNA Concepts In a subarea network, the CP on an SNA node acts as a type 2.0 PU . It communicates with an SSCP on a host and does not communicate with other CPs in the subarea network. When participating in an APPN network, the CP exchanges network control information with the CPs in adjacent nodes .
Chapter 1 37 SNA T erms and Concepts Basic SNA Concepts Before an SSCP-LU session can be established, the PU controlling the LU must have an active SSCP-PU session with an SSCP on a type 5 node. The SSCP-PU session is used to pass control data and network management data between the PU and SSCP .
38 Chapter 1 SNA T erms and Concepts Basic SNA Concepts dependent LU requester (DLUR) function enables session traffic from dependent LUs to flow over APPN networks. F or more information about DLUR, see “ Accessing Subarea Networks from APPN Networks”.
Chapter 1 39 SNA T erms and Concepts Basic SNA Concepts Figure 1-2 Multiple and P arallel 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.
40 Chapter 1 SNA T erms and Concepts Basic SNA Concepts As shown in Figure 1-3, “Communication between Transaction Programs and Logical Units ,” information is exc hanged between TPs and LUs to enable one node to communicate with another .
Chapter 1 41 SNA T erms and Concepts Basic SNA Concepts A logical record consists of a two- or four -byte header starting with a two-byte length field, often represented as “LL,” followed by up to 32,765 bytes of data.
42 Chapter 1 SNA T erms and Concepts Basic SNA Concepts Class of Service Class of service (COS) is a definition of the transport network (data link control and path control) characteristics—such as route security , transmission priority , and bandwidth—that the local node can use to establish a particular session.
Chapter 1 43 SNA T erms and Concepts Basic APPN Concepts Basic APPN Concepts Advanced P eer -to-P eer Networking (APPN) is a network architecture that supports distributed network control. It makes networks easy to configure and use, provides centralized network management, and supports flexible connectivity .
44 Chapter 1 SNA T erms 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”).
Chapter 1 45 SNA T erms 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 .
46 Chapter 1 SNA T erms and Concepts Basic APPN Concepts An APPN end node can be attached to multiple network nodes (see EN3 in Figure 1-4, “P ortion of a Sample APPN Network,”) but it can ha ve CP-CP sessions active with only one network node at a time—its network node server .
Chapter 1 47 SNA T erms and Concepts Basic APPN Concepts APPN Control P oint 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.
48 Chapter 1 SNA T erms and Concepts Basic APPN Concepts When setting up a workstation, you must define the CP name. The CP is also an LU that can support user sessions, and it can be the only LU defined in your workstation, if you so choose.
Chapter 1 49 SNA T erms and Concepts Basic APPN Concepts reside on the LEN node's network node server . The LEN node establishes sessions with LUs on its network node server . The network node routes the session through the APPN network to the proper node in the network.
50 Chapter 1 SNA T erms and Concepts Basic APPN Concepts Figure 1-5 LEN Node Directory T o 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).
Chapter 1 51 SNA T erms and Concepts Basic APPN Concepts Figure 1-6 End Node Directory P otential partner LUs in the APPN network do not need to be defined to the end node. However , in order for Node EN3 to establish a session with LUX on Node LEN1, the LU on the LEN node must be configured as a partner LU on Node EN3.
52 Chapter 1 SNA T erms 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 .
Chapter 1 53 SNA T erms and Concepts Basic APPN Concepts An APPN end node can also receive (and respond to) LOCATE search requests from its network node server to search for , or confirm the continued presence of , specific LUs in the end node.
54 Chapter 1 SNA T erms 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.
Chapter 1 55 SNA T erms and Concepts Basic APPN Concepts Figure 1-8 Network T opology Database in Network Nodes The shared network topology database is duplicated at Nodes NNA, NNB , NNC , and NND .
56 Chapter 1 SNA T erms and Concepts Basic APPN Concepts topology information because it does not have any links to end nodes). F or 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.
Chapter 1 57 SNA T erms and Concepts Basic APPN Concepts • If the session partner is not on an adjacent node, the network node server for the LU requesting the session uses the network topology database to identify network nodes and intermediate transmission groups in the route to the session partner .
58 Chapter 1 SNA T erms and Concepts Basic APPN Concepts data. In ISR, once a session route has been established, all data on that session uses the same route.
Chapter 1 59 SNA T erms and Concepts Basic APPN Concepts Figure 1-9 APPN Network Using a Shared-Access Transport F acility If Node EN1 has a link definition for each of the links in the network, it can establish a direct link to any node.
60 Chapter 1 SNA T erms and Concepts Basic APPN Concepts Figure 1-10 Definitions Needed for Direct Links from Node EN1 to Every Node in an APPN Network If all of the nodes in the network are to support direct links to every other node, a total of 30 link definitions are needed on the six nodes in this example.
Chapter 1 61 SNA T erms and Concepts Basic APPN Concepts only a single link to an adjacent network node server and a link to the connection network, instead of configuring every possible link to every node.
62 Chapter 1 SNA T erms and Concepts Basic APPN Concepts Figure 1-11 Definitions Needed for Direct Links Using a Virtual Node T o support direct links between any two end nodes in the APPN network, a total of ten link definitions is required. (Each end node needs two link definitions: one to a network node server and one to the virtual node.
Chapter 1 63 SNA T erms and Concepts Basic APPN Concepts 3. The server normally selects the direct link between two end nodes as the optimal route for the LU-LU session. It provides the node with the primary LU the information it needs to establish a dynamic link to the node with the partner LU .
64 Chapter 1 SNA T erms and Concepts Accessing Subarea Networks fr om 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 .
65 2 Introduction to SNAplus2.
66 Chapter 2 Introduction to SNAplus2 Overview Overview This chapter provides an overview of SNAplus2 features and shows some of the basic configurations in which SNAplus2 can be used.
Chapter 2 67 Introduction to SNAplus2 What Is SNAplus2? What Is SNAplus2? SNAplus2 is a software product that enables HP-UX computers to participate in an SNA network that includes mainframes , PCs, and other HP-UX computers .
68 Chapter 2 Introduction to SNAplus2 What Is SNAplus2? Within a TCP/IP local area network (LAN), SNAplus2 supports communication between servers (SNA nodes) and clients (HP-UX or Windows computers). F or more information about client/server facilities on a LAN , see “Client/Server Support”.
Chapter 2 69 Introduction to SNAplus2 Example Configurations Example Configurations SNAplus2 can be used as a standalone system to support direct communication with a host or another SNA node, within a LAN to support SNA communications across the LAN , or as a gatew ay to support communication between a host and systems in a LAN .
70 Chapter 2 Introduction to SNAplus2 Example Configurations Figure 2-2 SNAplus2 Nodes in an APPN Network In Figure 2-3, “SNAplus2 Node Providing PU Concentration and DLUR, ” a computer running SNAplus2 provides TN server support for TN3270 and TN3270E clients .
Chapter 2 71 Introduction to SNAplus2 Example Configurations Figure 2-3 SNAplus2 Node Providing PU Concentration and DLUR In Figure 2-4, “SNAplus2 Node Configured for TN Server ,” a computer running SNAplus2 provides TN server support for TN3270 and TN3270E clients .
72 Chapter 2 Introduction to SNAplus2 Example Configurations Figure 2-4 SNAplus2 Node Configured for TN Server A network that includes SNA nodes (SNAplus2 servers) and non-SNA computers (SNAplus2 clients) is shown in Figure 2-5, “SNAplus2 Client/Server Configuration.
Chapter 2 73 Introduction to SNAplus2 Example Configurations Figure 2-5 SNAplus2 Client/Server Configuration These examples show the most basic wa ys in which you can configure SNAplus2 nodes. By combining nodes using these basic configuration types , you can use SNAplus2 to support different types of communication within more complex networks.
74 Chapter 2 Introduction to SNAplus2 SNAplus2 Components SNAplus2 Components The components of SNAplus2 and their relationships are shown in Figure 2-6, “Components of SNAplus2.
Chapter 2 75 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.
76 Chapter 2 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. F or example, the downstream computer could be a PC running Microsoft SNA Server for Windows NT , or another SNAplus2 computer .
Chapter 2 77 Introduction to SNAplus2 SNAplus2 Components at the downstream computers are configured as part of the resources of the SNAplus2 computer . The host computer is not aw are that PU concentration is being used. Dependent LU Requester. This section does not apply to LEN nodes.
78 Chapter 2 Introduction to SNAplus2 SNAplus2 Components NO TE 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.
Chapter 2 79 Introduction to SNAplus2 SNAplus2 Components SNAplus2 TN server supports all TN3270 client emulation programs that correctly implement the protocols defined in RFCs 1123, 1576, 1646, and 1647.
80 Chapter 2 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. F or more information about configuring support for 3270 emulation, see Chapter 8, “Configuring User Applications .
Chapter 2 81 Introduction to SNAplus2 SNAplus2 Components The users of an RJE workstation can define workstation style files to supplement the SNAplus2 configuration and to control the operation of the workstation.
82 Chapter 2 Introduction to SNAplus2 SNAplus2 Components APPC API An APPC application uses the node's LU type 6.2 resources to communicate with another APPC or CPI-C application on a host or peer computer , using a specified mode .
Chapter 2 83 Introduction to SNAplus2 SNAplus2 Components • If the TP is operator -started (not started automatically by SNAplus2), and the use of the TP does not need to be restricted, you do not need to define any additional resources.
84 Chapter 2 Introduction to SNAplus2 SNAplus2 Components F or more information, refer to the HP-UX SNAplus2 3270 & TN3270 HLLAPI Programmers Guide or HP-UX SNAplus2 3270/3179G Users Guide .
Chapter 2 85 Introduction to SNAplus2 SNAplus2 Components • Windows CPI-C • Windows LU A • Windows CSV • 3270 Emulator Interface Specification F or more information about Windows SNA APIs , see the documentation provided with Microsoft SNA Server .
86 Chapter 2 Introduction to SNAplus2 SNAplus2 Components configuration. Y ou can configure a node from any other computer in the domain, as long as the SNA software is running on the node where the configuration is performed (whether or not the node being configured is started).
Chapter 2 87 Introduction to SNAplus2 SNAplus2 Components In a domain with multiple SNAplus2 servers , one server holds the master copy of the SNAplus2 domain configuration file. This server is known as the master server. Y ou can define other servers on the LAN to be backup servers.
88 Chapter 2 Introduction to SNAplus2 SNAplus2 Components preserved when the connection is re-established, do not make any changes to the file in either domain while the LAN connection is broken. Changes can still be made to the configuration of individual nodes.
Chapter 2 89 Introduction to SNAplus2 SNAplus2 Components End of Section Windows Clients For Windows SNAplus2 enables machines running Microsoft W indows 3.1, Windows for W orkgroups 3.11, Windows 95, W indows NT , and OS/2 to act as clients in the SNAplus2 domain.
90 Chapter 2 Introduction to SNAplus2 SNAplus2 Resources SNAplus2 Resources The resources of the SNAplus2 system can be divided into the following types: • Node resources define the communications capabilities of a particular APPN node.
Chapter 2 91 Introduction to SNAplus2 SNAplus2 Resources NO TE 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 .
92 Chapter 2 Introduction to SNAplus2 SNAplus2 Resources NO TE In the Motif administration program, DLCs are not shown directly . The information required for configuring a DLC is displayed as part of the configuration of a port owned by the DLC .
Chapter 2 93 Introduction to SNAplus2 SNAplus2 Resources The local node can have an explicit link station defined for its communication path to another node on the SATF , but enabling communications .
94 Chapter 2 Introduction to SNAplus2 SNAplus2 Resources Session Resources The following session resources are used by SNAplus2: • Logical units (see “Logical Units”) • Modes and their associa.
Chapter 2 95 Introduction to SNAplus2 SNAplus2 Resources With DDDLU , LUs do not have to be configured statically at the host. (Y ou must still define dependent LUs on the SNAplus2 node .) This reduces the initial configuration required at the host, and makes later expansion easier .
96 Chapter 2 Introduction to SNAplus2 SNAplus2 Resources Default LUs. If you are configuring type 6.2 dependent LUs for use with APPC or CPI-C applications, you ma y wish to define them as members of the default pool. The default pool can include LUs from more than one node.
Chapter 2 97 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.
98 Chapter 2 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.
Chapter 2 99 Introduction to SNAplus2 SNAplus2 Administration Administration T ools SNAplus2 provides a range of tools for administering the system. Depending on your requirements , you may not need to use all of them. This section summarizes the functions provided by each of these tools .
100 Chapter 2 Introduction to SNAplus2 SNAplus2 Administration • Querying the configuration of defined resources and their current status if they are active • Deleting resources The Motif admini.
Chapter 2 101 Introduction to SNAplus2 SNAplus2 Administration The other SNAplus2 administration tools, inc luding command-line configuration, and NOF application programs , provide access to a wider range of configuration parameters and options than those shown in the Motif administration program.
102 Chapter 2 Introduction to SNAplus2 SNAplus2 Administration • snapadmin -h -d command provides detailed help for the named command , including a list of the configuration parameters that can be specified with the command. Refer to the HP-UX SNAplus2 Administration Command Reference for more information.
Chapter 2 103 Introduction to SNAplus2 SNAplus2 Administration The sna_domn.cfg file contains information about SNAplus2 domain resources (resources not associated with a particular local node). The master copy of this file resides on the master server .
104 Chapter 2 Introduction to SNAplus2 SNAplus2 Administration F or more information about this file, refer to the HP-UX SNAplus2 Administration Command Reference . Client network data file The sna_clnt.net file contains information about how to access SNAplus2 servers , required by a client computer .
Chapter 2 105 Introduction to SNAplus2 SNAplus2 Administration Refer to the HP-UX SNAplus2 NOF Programmers Guide for more information. Diagnostic T ools SNAplus2 provides several diagnostics tools to .
106 Chapter 2 Introduction to SNAplus2 SNAplus2 Administration • Using command-line utilities, you can filter trace files to extract or interpret specific information or to produce a summary of message flows . The resulting output files can be viewed using a standard ASCII text editor such as vi .
107 3 Administering SNAplus2.
108 Chapter 3 Administering SNAplus2 Overview Overview The first step in administering SNAplus2 is configuring the node and its resources . Begin by planning for configuration as described in “Planning for SNAplus2 Configuration”.
Chapter 3 109 Administering SNAplus2 Planning for SNAplus2 Configuration Planning for SNAplus2 Configuration Before you make any configuration changes it is very important to plan thoroughly . Changes that you make can cause disruption, not only to the users of your local node but possibly to users all around the network.
110 Chapter 3 Administering SNAplus2 Planning for SNAplus2 Configuration T ask Sheets The online help screens in the Motif administration program contain task sheets that provide guidance for specific configuration tasks .
Chapter 3 111 Administering SNAplus2 Enabling and Disabling SNAplus2 on the Local System Enabling and Disabling SNAplus2 on the Local System Y ou must enable the SNAplus2 softw are before you can use any SNAplus2 tools (including the Motif administration program).
112 Chapter 3 Administering SNAplus2 Enabling and Disabling SNAplus2 on the Local System Enabling SNAplus2 Servers This section describes how to enable SNAplus2 on a computer that was installed as a server (that is , with the SNA node components installed).
Chapter 3 113 Administering SNAplus2 Enabling and Disabling SNAplus2 on the Local System tracing .) Tracing enables you to diagnose problems that occur during startup.
114 Chapter 3 Administering SNAplus2 Enabling and Disabling SNAplus2 on the Local System If a 3270 emulation program is using LUs on the node when you disable the SNAplus2 software , all 3270 emulation sessions using these LUs end. The program continues to run, but the user cannot use the sessions until the software is re-enabled.
Chapter 3 115 Administering SNAplus2 Using the Motif Administration Program Using the Motif Administration Program The Motif administration program provides a user -friendly interface for configuring SNAplus2.
116 Chapter 3 Administering SNAplus2 Using the Motif Administration Program In a client/server environment, SNAplus2 displays the Domain window . F or a standalone system, SNAplus2 displays the Node window . NO TE This guide uses the term window to describe Motif windows that display information about SNAplus2 resources .
Chapter 3 117 Administering SNAplus2 Using the Motif Administration Program Y ou can easily access other windows from this menu. These windows include the following: • Emulator Users and Sessionswin.
118 Chapter 3 Administering SNAplus2 Using the Motif Administration Program Figure 3-1 SNAplus2 Domain Window If any active nodes in the domain (nodes on which SNAplus2 is running) are not configured, SNAplus2 prompts you to configure the node. NO TE The Domain window does not list SNAplus2 clients .
Chapter 3 119 Administering SNAplus2 Using the Motif Administration Program When you select a node to be administered, SNAplus2 displays the Node window as shown in Figure 3-2, “Node Window . ” (F or a standalone system, SNAplus2 does not display the Domain window , because the domain has only one node.
120 Chapter 3 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.
Chapter 3 121 Administering SNAplus2 Using the Motif Administration Program The body of the Node window is split into the following panes for the different types of resources for the node: Connectivit.
122 Chapter 3 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).
Chapter 3 123 Administering SNAplus2 Using the Motif Administration Program list of associated link stations is shown or hidden. Similarly , link stations with a list of associated LUs can be expanded to show the LUs , or contracted to hide them.
124 Chapter 3 Administering SNAplus2 Using the Motif Administration Program Many resources , such as ports and link stations, cannot be modified while they are active.
Chapter 3 125 Administering SNAplus2 Using the Motif Administration Program Figure 3-4 Sample Dialog Resource dialogs guide you through the configuration process and supply default values whenever possible.
126 Chapter 3 Administering SNAplus2 Using the Motif Administration Program Most dialogs provide a Description field; the information you enter there is displayed on the window where the resource is displayed. Press the Done button when you are finished, or the Cancel button to exit without changing the configuration for the resource .
Chapter 3 127 Administering SNAplus2 Using the Motif Administration Program Figure 3-5 Sample Status Dialog Status dialogs show information about the current state of the resource.
128 Chapter 3 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 129 Administering SNAplus2 ASCII Administration Program ASCII Administration Program A menu-based ASCII administration program is available for character -based terminals.
130 Chapter 3 Administering SNAplus2 Using the Command-Line Administration Program Using the Command-Line Administration Program Command-line configuration enables you to change all SNAplus2 configuration parameters .
Chapter 3 131 Administering SNAplus2 Using the Command-Line Administration Program The remainder of this section summarizes administration commands for different types of resources. Some of the types of commands listed are as follows: status_ * Provides summary information for types of resources .
132 Chapter 3 Administering SNAplus2 Using the Command-Line Administration Program.
133 4 Basic Configuration T asks.
134 Chapter 4 Basic Configuration T asks Overview Overview This chapter provides an overview of configuration tasks and explains how to configure the SNAplus2 node. It also explains how to configure master and backup servers when SNAplus2 is used in a client/server environment.
Chapter 4 135 Basic Configuration T asks Configuring Client/Server Functions Configuring Client/Server Functions This section is relevant only if you installed SNAplus2 to run in a client/server environment (with multiple SNAplus2 nodes in the same network).
136 Chapter 4 Basic Configuration T asks Configuring Client/Server Functions NO TE Y ou cannot directly indicate which node acts as the master server; the master server is selected based on the order in which nodes are added to the configuration server list.
Chapter 4 137 Basic Configuration T asks Configuring the Node Configuring the Node The first step in configuring SNAplus2 on a system is to configure the local node. Node configuration provides the basic information that the node needs in order to participate in an APPN network.
138 Chapter 4 Basic Configuration T asks Configuring the Node When you define the control point, SNAplus2 automatically defines a local LU with the same name. That LU can act as a default local LU for the node. Control point alias Local alias for the default local LU .
Chapter 4 139 Basic Configuration T asks Configuring Logging Configuring Logging SNAplus2 writes log messages describing abnormal events (and, optionally , normal events) to log files.
140 Chapter 4 Basic Configuration T asks Configuring Logging If your favorite editor is installed on the server , you can use it to view the log files . If not, you can use the standard HP-UX system utilities: pg View a file one page at a time . This utility is simple and easy to use but useful only if the log file is small.
Chapter 4 141 Basic Configuration T asks Configuring Logging The Logging dialog in the Motif administration program affects log settings throughout the domain. Using the command line, you can override the domain settings by configuring local log settings on a particular machine .
142 Chapter 4 Basic Configuration T asks Configuring Logging.
143 5 Defining Connectivity Components.
144 Chapter 5 Defining Connectivity Components Overview Overview In order for the SNAplus2 node to communicate with other nodes, you must configure connectivity with at least one adjacent node. A connecting link can be configured to carry dependent traffic, independent traffic, or both.
Chapter 5 145 Defining Connectivity Components Overview and they must be configured on the adjacent nodes as well as on the SNAplus2 node, so you ma y need to consult your SNA network planner . Operating as an APPN Node If the SNAplus2 node is an end node in an APPN network, the number of links that you need to configure can be greatly reduced.
146 Chapter 5 Defining Connectivity Components Overview F or information about configuring PU concentration, see “Configuring PU Concentration”.
Chapter 5 147 Defining Connectivity Components Defining P orts, DLCs, and Connection Networks Defining P orts, DLCs, and Connection Networks A port represents the local end of a communications link as a unique access point in the network.
148 Chapter 5 Defining Connectivity Components Defining P orts, DLCs, and Connection Networks Select Connectivity and New port from the Services menu on the Node window .
Chapter 5 149 Defining Connectivity Components Defining P orts, DLCs, and Connection Networks This field applies only if the adapter card can support more than one port. This field is not used for SDLC or QLLC ports. Initially active Whether to activate the port automatically when the node is started.
150 Chapter 5 Defining Connectivity Components Defining P orts, DLCs, and Connection Networks Select a value that describes the role of the local node for link stations defined on this port. In SDLC communication, one end manages the link and is called the primary link station.
Chapter 5 151 Defining Connectivity Components Defining P orts, 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.
152 Chapter 5 Defining Connectivity Components Defining P orts, DLCs, and Connection Networks Consult your SNA network planner if you do not know how to configure any of these parameters . Additional P ort P arameters for T oken Ring, FDDI and Ethernet Local SAP number The address of the SAP , usually 04 .
Chapter 5 153 Defining Connectivity Components Defining P orts, DLCs, and Connection Networks NO TE The underlying stack is also configured with an address and accepts only calls that specify an address starting with the configured address.
154 Chapter 5 Defining Connectivity Components Defining Link Stations Defining Link Stations T o communicate with other nodes in an SNA network, you must configure the characteristics of a link station (LS) to an adjacent node in the SNA network.
Chapter 5 155 Defining Connectivity Components Defining Link Stations the local node. This dynamically created link station appears in the connectivity section of the Node window for the duration of the connection.
156 Chapter 5 Defining Connectivity Components Defining Link Stations Common Link Station P arameters The following parameters are required for all link stations, whether they support dependent traffic, independent traffic , or both.
Chapter 5 157 Defining Connectivity Components Defining Link Stations The type of LU traffic to flow over the link. This choice determines what other parameters are needed for link definition. Any The link station can be used for both independent and dependent LU traffic.
158 Chapter 5 Defining Connectivity Components Defining Link Stations • If you are configuring a primary switched outgoing link station, and you do not know the poll address of the remote secondary with which you wish to communicate, you can specify a poll address of 0xFF on the primary .
Chapter 5 159 Defining Connectivity Components Defining Link Stations By default, the dial string is sent to the modem at the rate of 1200 bits per second (the default baud rate) using asynchronous communications .
160 Chapter 5 Defining Connectivity Components Defining Link Stations If you do not know what value to use, consult your SNA network planner . If the remote end of this link is a VTAM host, the SAP number is the SAP ADDR= parameter of the VTAM PU definition.
Chapter 5 161 Defining Connectivity Components Defining Link Stations P arameters for Independent LU Traffic Y ou need the following information to configure this link station for use by independent LUs (LUs of type 6.2 for use by APPC , 5250, or CPI-C applications): Remote node name The fully qualified CP name of the remote node.
162 Chapter 5 Defining Connectivity Components Defining Link Stations slightly , so if you do know the type it is better to specify it. This also helps to ensure network configuration consistency . Y ou cannot choose Discover if the link station is activated on demand.
Chapter 5 163 Defining Connectivity Components Defining Link Stations CP name of the remote node, but for remote nodes that do not send their CP name when activating a link, the remote node ID must be used instead. If you do not specify the remote node ID , the node ID of the remote node is not checked when the link is activated.
164 Chapter 5 Defining Connectivity Components Defining DLUR PUs Defining DLUR PUs Normally , a dependent LU session requires a direct communications link to the host computer .
Chapter 5 165 Defining Connectivity Components Defining DLUR PUs F or each DLUR PU on the local node, specify a PU name. The name does not need to matc h the PU name configured on the host. DLUS Name The fully qualified LU name of the host LU that supports DLUS .
166 Chapter 5 Defining Connectivity Components Defining DLUR PUs Whether the DLUR PU is to be activated automatically after a failure (once the cause of the failure has been remedied). Additional Configuration After configuring DLUR, continue with the following configuration tasks: • T o configure LUs for DLUR, see “Defining DLUR PUs”.
167 6 Configuring Dependent LUs.
168 Chapter 6 Configuring Dependent LUs Overview Overview This chapter provides instructions for configuring LUs and LU pools to support user applications that use 3270, TN3270, RJE and LU A communications . T o use these, you must configure dependent LUs.
Chapter 6 169 Configuring Dependent LUs Defining LU T ypes 0–3 Defining LU Types 0–3 Y ou must configure dependent LUs of types 0–3 to support communication with a host system. Y ou can use the information in this section to define an LU to support 3270, RJE, or LU A.
170 Chapter 6 Configuring Dependent LUs Defining LU T ypes 0–3 The link station that provides the link to the host. The LU definition belongs to the link station you select. (If the dependent LU resides on a node that supports DLUR, this field identifies the DLUR PU that provides connectivity to the host.
Chapter 6 171 Configuring Dependent LUs Defining LU T ypes 0–3 Whether the LU is assigned to an LU pool. Only printer , display , and unrestricted (unknown) LUs can be members of a pool.
172 Chapter 6 Configuring Dependent LUs Defining LU P ools Defining LU P ools F or 3270, TN3270, RJE,and LUA, you can define LU pools to simplify user configuration and provide greater flexibility in establishing host sessions .
Chapter 6 173 Configuring Dependent LUs Defining LU P ools LU P ool Configuration P arameters The following parameters are required for LU pool configuration: Name A name to identify the LU pool. This field applies only when you are adding a new LU pool.
174 Chapter 6 Configuring Dependent LUs Defining LU P ools.
175 7 Configuring APPC Communication.
176 Chapter 7 Configuring APPC Communication Overview Overview APPC applications , 5250 emulation programs, and CPI-C applications all require that you configure APPC first. An APPC application uses the node's LU type 6.2 resources to communicate with another APPC or CPI-C application on a host or peer computer , using a specified mode .
Chapter 7 177 Configuring APPC Communication Overview Step 1. Define a local LU as described in “Defining Local LUs”. Step 2. Define a remote node as described in “Defining Remote Nodes”. Step 3. Define a partner LU as described in “Defining P artner LUs”.
178 Chapter 7 Configuring APPC Communication Defining Local LUs Defining Local LUs In many cases , applications can use the local node's control point LU , which is automatically defined when you configure the node . This is the default LU—if your application does not specify a particular LU , it can use this one.
Chapter 7 179 Configuring APPC Communication Defining Local LUs Command-line administration program Issue the following command: define_local_lu Y ou can use the advanced dialog to specify sync point support, attach routing characteristics , restrictions on SSCP access, and security .
180 Chapter 7 Configuring APPC Communication Defining Local LUs • T o define a remote node, see “Defining Remote Nodes”. • T o define a partner LU , see “Defining P artner LUs”. • T o define an invokable TP , see “Defining TPs”.
Chapter 7 181 Configuring APPC Communication Defining Remote Nodes Defining Remote Nodes Y ou must define a remote node (and the partner LUs on the node) in the following situations: • If the local node is a LEN node, you must define all of the remote nodes and any partner LUs on the remote node with which it communicates using APPC .
182 Chapter 7 Configuring APPC Communication Defining Remote Nodes defined a remote node and SNAplus2 establishes CP-CP sessions with it, the entry is temporarily converted into a dynamic one. Y ou should correct the fault by deleting the remote node definition when the node is inactive.
Chapter 7 183 Configuring APPC Communication Defining Partner LUs Defining P artner LUs If both the local node and the remote node are end nodes or network nodes and your application uses an LU name to refer to the partner LU , there is no need to define the partner LU , because it can be dynamically located using APPN .
184 Chapter 7 Configuring APPC Communication Defining Partner LUs P artner LU Configuration P arameters The following parameters are required for partner LU configuration: P artner LU name The fully qualified LU name of the partner LU . This name must match the name that is configured at the remote node for this LU .
Chapter 7 185 Configuring APPC Communication Defining Partner LUs A locally displayable alias for the partner LU . Y ou do not have to specify an LU alias if there is no local application that refers to the partner LU using an LU alias .
186 Chapter 7 Configuring APPC Communication Defining Partner LUs Additional Configuration After performing the partner LU configuration, continue with the following configuration tasks: • T o define an invokable TP , see “Defining TPs”. • T o define a mode, see “Defining Modes and Classes of Service”.
Chapter 7 187 Configuring APPC Communication Defining TPs Defining TPs This section explains how to define an APPC TP . In most cases, you do not need to define TPs that run on the SNAplus2 syste.
188 Chapter 7 Configuring APPC Communication Defining TPs F or an invokable TP , you can also specify a timeout value, to limit the w ait for an allocation request.
Chapter 7 189 Configuring APPC Communication Defining TPs The configuration methods for servers and clients are different: • On a server , use either of the following methods: Motif administration program Select APPC and Transaction Programs from the Services menu on the Node window .
190 Chapter 7 Configuring APPC Communication Defining TPs The local LU alias from which the TP is to accept incoming Attaches . This name must match the name of a local APPC LU on the SNAplus2 node. If you do not specify an LU alias, the TP accepts incoming Attac hes from any local LU .
Chapter 7 191 Configuring APPC Communication Defining TPs about the TP is broadcast to all servers on the LAN; if an LU on another computer receives an incoming Allocate request and has no routing information configured, it can dynamically locate the TP and route the Allocate request to it.
192 Chapter 7 Configuring APPC Communication Defining TPs The TP is started in the home directory associated with this user ID . This home directory is also the default path for trace files and any other files accessed by the TP (unless the application overrides it by specifying a full path).
Chapter 7 193 Configuring APPC Communication Defining TPs Select this option if an allocation request must include a valid user name and password (or an indicator that the password has already been verified). If you do not select this option, no verification is required.
194 Chapter 7 Configuring APPC Communication Defining Modes and Classes of Service Defining Modes and Classes of Service A mode specifies a set of characteristics that a local LU (LU type 6.
Chapter 7 195 Configuring APPC Communication Defining Modes and Classes of Service T able 7-1 Standard Mode and COS Names Once a mode has been configured, it can be used by any APPC or CPI-C application to activate a session between a local LU and a partner LU .
196 Chapter 7 Configuring APPC Communication Defining Modes and Classes of Service Command-line administration program T o define a mode, issue the following command: define_mode T o change the def.
Chapter 7 197 Configuring APPC Communication Defining Modes and Classes of Service This field is usually set to the same value as the initial session limit. If you are in doubt, consult your SNA network planner or APPC application developer (or for a third-party application, the product documentation).
198 Chapter 7 Configuring APPC Communication Defining Modes and Classes of Service The initial setting for the number of request units (RUs) that the local LU can receive before it must send a pacing response to the remote LU . This can be safely set to 4 .
Chapter 7 199 Configuring APPC Communication Defining Modes and Classes of Service The lower limit can be 0 or a value from 256 through the upper limit you specify .
200 Chapter 7 Configuring APPC Communication Defining CPI-C Side Information Defining CPI-C Side Information If you are supporting a CPI-C application that uses CPI-C symbolic destination names , you need to define the CPI-C side information.
Chapter 7 201 Configuring APPC Communication Defining CPI-C Side Information Specify this option to use a member of the default pool (if one exists) or the node control point LU (if no default pool is defined).
202 Chapter 7 Configuring APPC Communication Defining CPI-C Side Information Same The partner TP uses security , but accepts verification by the local TP of the user ID and password provided by the initiating TP . If you choose a security level of Same , you also need to specify a valid user ID that is accepted by the partner TP .
Chapter 7 203 Configuring APPC Communication Defining CPI-C Side Information Additional Configuration After performing the CPI-C configuration, continue with the following configuration tasks: • T o define APPC security , see “Configuring APPC Security”.
204 Chapter 7 Configuring APPC Communication Configuring APPC Security Configuring APPC Security Y ou can perform the following configuration tasks for APPC security: • Configuring session secu.
Chapter 7 205 Configuring APPC Communication Configuring APPC Security used to create a key , which is exchanged when the session is established. This password is not related to HP-UX login passwords on either the local or the remote node.
206 Chapter 7 Configuring APPC Communication Configuring APPC Security The password to be accepted in an incoming conversation from a remote node. The password can be up to 10 characters long . This password is not related to HP-UX login passwords on either the local or the remote node.
Chapter 7 207 Configuring APPC Communication Configuring APPC Security Additional Configuration After performing the security access list configuration, continue with the following configuration tasks: • Configure TP access as described in “Defining TPs”.
208 Chapter 7 Configuring APPC Communication Configuring APPC Security.
209 8 Configuring User Applications.
210 Chapter 8 Configuring User Applications Overview Overview This chapter provides instructions for configuring SNA resources to support user applications that use any of the following communication: 3270, RJE, 5250, and LU A. The SNA resources required by such applications include LUs , session definitions, and user definitions .
Chapter 8 211 Configuring User Applications Overview Step 1. F or a 3270 display or printer , define a dependent LU as described in “Defining LU Types 0–3”. Step 2. T o enable 3270 displa ys to select from a pool of LUs , define an LU pool as described in “Defining LU P ools”.
212 Chapter 8 Configuring User Applications Overview RJE applications SNAplus2 provides support for remote job entry (RJE), enabling you to submit jobs to a host computer for processing . The RJE workstation daemon handles transfer of jobs to the host, and also handles the output returned from the host.
Chapter 8 213 Configuring User Applications Configuring 3270 Users and Sessions Configuring 3270 Users and Sessions T o enable 3270 communications, you must define emulator users or groups of users as described in “Configuring 3270 Emulator Users”, and 3270 emulator sessions as described in “Configuring 3270 Sessions”.
214 Chapter 8 Configuring User Applications Configuring 3270 Users and Sessions Emulation User and Group Configuration P arameters The following parameters are required for each 3270 emulator user definition: User Name The name of the emulator user .
Chapter 8 215 Configuring User Applications Configuring 3270 Users and Sessions If the user has a style file, enter the file name . If there is no style file, the user runs the emulation program with a default style. The style file determines the appearance and behavior of the emulation screens and keyboard for the emulator user .
216 Chapter 8 Configuring User Applications Configuring 3270 Users and Sessions The user can view RTM data. Send alerts The user can send alerts to NetView . Additional Configuration After performing the emulation user configuration, you can define 3270 sessions for users or groups as described in “Configuring 3270 Sessions”.
Chapter 8 217 Configuring User Applications Configuring 3270 Users and Sessions Display or Printer Specify whether the session is a display or printer session. LU/P ool name The name of the LU or pool to be used by the session. Assign printer LUs for printer sessions, and display LUs or pools of display LUs for displa y sessions.
218 Chapter 8 Configuring User Applications Configuring 5250 Users Configuring 5250 Users T o enable 5250 communications, you must define emulator users or groups of users as described in “Configuring 5250 Emulator Users”.
Chapter 8 219 Configuring User Applications Configuring 5250 Users F or 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. F or Windows 3.
220 Chapter 8 Configuring User Applications Configuring RJE W orkstations Configuring RJE W orkstations Y ou can define an RJE workstation to submit jobs to a host computer for processing . The RJE workstation also handles the output returned by the host.
Chapter 8 221 Configuring User Applications Configuring RJE W orkstations The RJE workstation runs using this user name, and all files created by the RJE workstation are owned by this user . UNIX group name The HP-UX system group name for the users who use the RJE workstation.
222 Chapter 8 Configuring User Applications Configuring RJE W orkstations.
223 9 Configuring P assthrough Services.
224 Chapter 9 Configuring Passthrough Services Overview Overview P assthrough 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 .
Chapter 9 225 Configuring Passthrough Services Configuring TN Server Configuring TN Server TN server enables TN3270 clients to communicate with a host through an intermediate SNAplus2 node that implements the TN server . The TN3270 clients connect to the TN server using TCP/IP , and use LUs defined on the TN server .
226 Chapter 9 Configuring Passthrough Services Configuring TN Server Configuring TN Server Access Records TN server access records indicate which TN3270 clients can access the TN server and which LUs they should use .
Chapter 9 227 Configuring Passthrough Services Configuring TN Server P ermit access from a specific TCP/IP address . If you know the TCP/IP address of the TN3270 client, select this option and enter the address in the standard TCP/IP dotted decimal address format.
228 Chapter 9 Configuring Passthrough Services Configuring TN Server If you want a TN3270 c lient to be able to use more than one LU or LU pool, define multiple access records, eac h with a different TCP/IP port number , so that you can identify the different LUs or LU pools by specifying different port numbers.
Chapter 9 229 Configuring Passthrough Services Configuring TN Server Motif administration program Select TN Server from the Services menu on the Node window , then select the Association Records pane on the TN Server window and choose New .
230 Chapter 9 Configuring Passthrough Services Configuring PU Concentration Configuring PU Concentration Normally , a dependent LU session requires a direct communications link to the host computer .
Chapter 9 231 Configuring Passthrough Services Configuring PU Concentration • Define the LUs on the local node that are used for communication with the host (the upstream LUs). Upstream LUs must be defined using the LU Type 0-3 Configuration dialog, specifying an LU type of unrestricted (unknown).
232 Chapter 9 Configuring Passthrough Services Configuring PU Concentration The LU number must match the LU number defined on the downstream node. Contact your SNA network planner if you do not know what LU number to use. Y ou can configure several LUs with consecutive LU numbers by defining a range of LUs .
Chapter 9 233 Configuring Passthrough Services Configuring DLUR Configuring DLUR Normally , a dependent LU session requires a direct communications link to the host computer .
234 Chapter 9 Configuring Passthrough Services Configuring DLUR printer , RJE, or LU A. Depending on the requirements of the user applications supported by the LUs , you may also need to perform further configuration.
235 10 Managing SNAplus2 from NetV iew.
236 Chapter 10 Managing SNAplus2 from NetView Overview Overview SNAplus2 includes a remote command facility (RCF) that operates in conjunction with the NetView program at a host computer , enabling a NetView operator to issue commands from the host NetV iew program to the SNAplus2 computer .
Chapter 10 237 Managing SNAplus2 from NetView Using the Host NetView Pr ogram Using the Host NetV iew Program The SNAplus2 RCF operates in conjunction with the NetView program at a host computer . The host must be running NetV iew V ersion 1 Release 2, or a later version; SNAplus2 does not support NetView V ersion 1 Release 1.
238 Chapter 10 Managing SNAplus2 from NetView Using the Host NetView Pr ogram Step 5. If you are using 3270 emulation to access NetView , follow the instructions in HP-UX SNAplus2 3270/3179G Users Guide for ending 3270 emulation when you have finished issuing commands .
Chapter 10 239 Managing SNAplus2 from NetView Using the Host NetView Pr ogram node The SNAplus2 node associated with the service point name spname (for SPCF commands) unix The UCF daemon program runni.
240 Chapter 10 Managing SNAplus2 from NetView Using the Host NetView Pr ogram T able 10-1 Using Escape Characters in RCF Commands The escape characters you would normally use on the HP-UX command line, to prevent the HP-UX shell from interpreting special c haracters, are not required with RCF .
Chapter 10 241 Managing SNAplus2 from NetView Using SPCF Using SPCF SPCF enables you to issue commands from the NetView console to manage the running SNAplus2 system. These commands are the same as those you can issue using the SNAplus2 command-line management program snapadmin (as described in HP-UX SNAplus2 Administration Command Reference ).
242 Chapter 10 Managing SNAplus2 from NetView Using SPCF T o provide security , you can set up the SNAplus2 configuration so that only certain types of commands are permitted from SPCF . F or example, you can permit remote users to issue query_ * commands, but not to activate or deactivate SNAplus2 components.
Chapter 10 243 Managing SNAplus2 from NetView Using UCF Using UCF UCF enables a NetView operator to issue HP-UX commands on a computer running SNAplus2 by typing the command text at the NetView console, and to view output from these commands .
244 Chapter 10 Managing SNAplus2 from NetView Using UCF Specify spname , which is the name of your service point as defined at NetView . The host NetV iew personnel can give you this information. appl =unix Instruct NetView to send the command to the UCF daemon program on the SNAplus2 computer associated with the service point name spname .
Chapter 10 245 Managing SNAplus2 from NetView Using UCF • The UCF cannot be used with a command that requires further input from the user before it completes (for example, a command such as vi filename that starts an interactive process , or a command such as tail -f filename that does not complete until it is stopped by the user).
246 Chapter 10 Managing SNAplus2 from NetView Using UCF If you issue a command when a previous command is still in progress (that is , before the UNIX COMMAND COMPLETED message is received), the following message is displayed: = = = COMMAND QUEUED = = = The second command is queued, and is executed when the previous command has completed.
Chapter 10 247 Managing SNAplus2 from NetView Using UCF In this case, the ux-cancel command is ignored. No action is necessary . This message can be displayed when the ux-cancel command is issued after the previous command finishes but before the UNIX COMMAND COMPLETED message is received.
248 Chapter 10 Managing SNAplus2 from NetView Using UCF.
249 11 Managing SNAplus2 Clients.
250 Chapter 11 Managing SNAplus2 Clients Overview Overview A domain for SNAplus2 can include both servers (SNA nodes) and clients (which can access SNA connectivity through a server). Clients can be computers running the HP-UX operating system or the Windows 3.
Chapter 11 251 Managing SNAplus2 Clients Client Networking Requirements Client Networking Requirements Before you can run SNAplus2 on a client computer , you must configure TCP/IP port addresses on both the clients and servers in your network.
252 Chapter 11 Managing SNAplus2 Clients Client Networking Requirements For Windows Step 4. If your SNAplus2 domain includes W indows clients, add the same two lines to the services file on each Windows computer .
Chapter 11 253 Managing SNAplus2 Clients Client Networking Requirements • The administration commands query_central_logger or query_node_all (these return the information that was available before the TCP/IP connection w as dropped, and so may not match the current status of the LAN).
254 Chapter 11 Managing SNAplus2 Clients Managing Win32 Clients Managing W in32 Clients For Windows SNAplus2 enables machines running Microsoft W indows 95 and Windows NT to act as c lients in the SNAplus2 domain.
Chapter 11 255 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 F or more information, see “Win32 Client Configuration”.
256 Chapter 11 Managing SNAplus2 Clients Managing Win32 Clients W in32 Client Security SNAplus2 provides a facility for validating the user name and password of any Win32 c lient running on Windows 95 and attempting to contact a server running SNAplus2.
Chapter 11 257 Managing SNAplus2 Clients Managing Win32 Clients W in32 Client Configuration On both Windows NT and W indows 95, configuration information is managed through the Windows Program Registry .
258 Chapter 11 Managing SNAplus2 Clients Managing Win32 Clients rui = YES | NO nof = YES | NO ms = YES | NO MSG_tracing file1 = msg_trace_filename_1 file2 = msg_trace_filename_2 flip_size = filesiz.
Chapter 11 259 Managing SNAplus2 Clients Managing Win32 Clients The group_name value indicates the group name of the SNAplus2 user on this client. This name must match the SNAplus2 configuration on s.
260 Chapter 11 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 . F or more information, see “LAN Access Timeout”.
Chapter 11 261 Managing SNAplus2 Clients Managing Win32 Clients This parameter is optional. The valid range is 5 – 65535 . If it is not specified, the default is 200 (seconds). client_start_timeout The Registry data type of this value is REG_DWORD .
262 Chapter 11 Managing SNAplus2 Clients Managing Win32 Clients server has been contacted, the client then tries using directed messages to one or more named servers (specified by the following lines of the file).
Chapter 11 263 Managing SNAplus2 Clients Managing Win32 Clients The parameters Server2 – Server10 cannot be set to * to indicate the use of UDP broadcasts . Only the Server1 parameter can be used to indicate this , because the * value must precede any server names in the file.
264 Chapter 11 Managing SNAplus2 Clients Managing Win32 Clients This parameter is optional. If it is not specified, the Win32 c lient uses the global domain settings to determine whether audit messages are recorded. (The initial default is that audit messages are recorded.
Chapter 11 265 Managing SNAplus2 Clients Managing Win32 Clients amount of disk space taken up by error log files is approximately twice the value of the error_file_wrap_size parameter . This parameter is optional. If it is not specified, the default is 1000000 (bytes).
266 Chapter 11 Managing SNAplus2 Clients Managing Win32 Clients This parameter is optional. If it is not specified, the default is 1000000 (bytes). If you are logging error and audit messages to the same file, this parameter must be set to the same value as the error_file_wrap_size parameter .
Chapter 11 267 Managing SNAplus2 Clients Managing Win32 Clients The Registry data type of this value is REG_SZ . Specifies whether to use succinct logging or verbose logging in the audit log file. The permitted values and their meanings are the same as for the succinct_errors parameter .
268 Chapter 11 Managing SNAplus2 Clients Managing Win32 Clients The maximum size of the trace file. If two file names are specified, tracing switches between the two files when the current file reaches this size . If only one file name is specified, this parameter is ignored; the file size is not limited.
Chapter 11 269 Managing SNAplus2 Clients Managing Win32 Clients The Registry data type of this value is REG_SZ . T o trace CPI-C API messages, set this parameter to YES ; otherwise, set it to NO . This parameter is optional. If it is not specified, the default is NO .
270 Chapter 11 Managing SNAplus2 Clients Managing Win32 Clients This parameter is optional. If it is not specified, the default is NO . If the all_api parameter is set to YES , this parameter is ignored, and MS messages are traced. MSG_tracing The MSG_tracing subkey specifies options for tracing on Win32 client 3270 emulation programs .
Chapter 11 271 Managing SNAplus2 Clients Managing Win32 Clients The maximum size of the trace file. If two file names are specified, tracing switches between the two files when the current file reaches this size. If only one file name is specified, this parameter is ignored; the file size is not limited.
272 Chapter 11 Managing SNAplus2 Clients Managing Win32 Clients The Registry data type of this value is REG_SZ . The full path name of the second trace file. This parameter is optional; to indicate that tracing is to one file instead of two files , do not include this line.
Chapter 11 273 Managing SNAplus2 Clients Managing Win32 Clients T o trace data messages, set this parameter to YES ; otherwise, set it to NO . This parameter is optional. If it is not specified, the default is NO . send The Registry data type of this value is REG_SZ .
274 Chapter 11 Managing SNAplus2 Clients Managing Win32 Clients The TP name of the application. This name is used in log and trace files to identify the application.
Chapter 11 275 Managing SNAplus2 Clients Managing Win16 Clients Managing W in16 Clients SNAplus2 enables machines running Microsoft W indows 3.1 and Windows for W orkgroups 3.
276 Chapter 11 Managing SNAplus2 Clients Managing Win16 Clients • Servers that the client can access • Logging and tracing options for applications running on the client • Additional options for CPI-C and CSV applications running on the client F or more information about this file, see “W in16 Client Initialization File (sna.
Chapter 11 277 Managing SNAplus2 Clients Managing Win16 Clients T o disable the NAP , click on the Windows NAP icon and c hoose Close . If any SNAplus2 applications are running , the Close option is not selectable; if you are sure you want to disable the NAP , stop the relevant applications before retrying.
278 Chapter 11 Managing SNAplus2 Clients Managing Win16 Clients password, or if the user name and password cannot be matched with a user name and password on the server , the server rejects the client's access attempt.
Chapter 11 279 Managing SNAplus2 Clients Managing Win16 Clients backup_error_file = backup_error_filename error_file_wrap_size = error_file_size audit_file = audit_filename backup_audit_file = back.
280 Chapter 11 Managing SNAplus2 Clients Managing Win16 Clients [Configuration] The [Configuration] section of the file contains configuration information for the client, as follows: domain The domain_name argument indicates the domain name of the SNAplus2 LAN , as specified during the client installation.
Chapter 11 281 Managing SNAplus2 Clients Managing Win16 Clients The group_name argument indicates the group name of the SNAplus2 user on this client. This name must match the SNAplus2 configuration o.
282 Chapter 11 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 . F or more information, see “LAN Access Timeout”.
Chapter 11 283 Managing SNAplus2 Clients Managing Win16 Clients [Servers] The [Servers] section of the file contains information about SNAplus2 servers that the client can access , as follows: Server.
284 Chapter 11 Managing SNAplus2 Clients Managing Win16 Clients attempts to contact the server specified in Server2 using a directed message. If this fails , it tries the server specified in Server3 , and so on.
Chapter 11 285 Managing SNAplus2 Clients Managing Win16 Clients This parameter is optional. If it is not specified, the Win16 c lient uses the global domain settings to determine whether exception messages are recorded. (The initial default is that exception messages are recorded.
286 Chapter 11 Managing SNAplus2 Clients Managing Win16 Clients T o log error and audit messages to a single file, specify the same file name for both this parameter and the backup_audit_file parameter . error_file_wrap_size The maximum size of the log file specified by error_file .
Chapter 11 287 Managing SNAplus2 Clients Managing Win16 Clients clears the log file . This means that the maximum amount of disk space taken up by audit log files is approximately twice the value of the audit_file_wrap_size parameter . This parameter is optional.
288 Chapter 11 Managing SNAplus2 Clients Managing Win16 Clients either be from the set_global_log_type command, or from a set_log_type command issued to that server to override the default. succinct_audits Specifies whether to use succinct logging or verbose logging in the audit log file.
Chapter 11 289 Managing SNAplus2 Clients Managing Win16 Clients This parameter is optional. If it is not specified, the default is 100000 (bytes). truncation_length The maximum length, in bytes , of the information written to the trace file for each message.
290 Chapter 11 Managing SNAplus2 Clients Managing Win16 Clients T o trace CSV API messages, set this parameter to YES ; otherwise, set it to NO . This parameter is optional. If it is not specified, the default is NO . If the all_api parameter is set to YES , this parameter is ignored, and CSV messages are traced.
Chapter 11 291 Managing SNAplus2 Clients Managing Win16 Clients The full path name of the trace file, or of the first trace file if tracing is to two files (see the description of the file2 parameter). This parameter is required if you want to enable message tracing; you also need to set the fmi parameter .
292 Chapter 11 Managing SNAplus2 Clients Managing Win16 Clients T o trace 3270 messages, set this parameter to YES ; otherwise, set it to NO . This parameter is optional.
Chapter 11 293 Managing SNAplus2 Clients Managing Win16 Clients T o trace internal messages relating to client/server topology , set this parameter to YES ; otherwise, set it to NO . This parameter is optional. If it is not specified, the default is NO .
294 Chapter 11 Managing SNAplus2 Clients Managing Win16 Clients The name of the local LU that this application uses . This parameter is optional. If it is not specified, the application attempts to use the default LU (the LU associated with a local node's control point).
Chapter 11 295 Managing SNAplus2 Clients Managing HP-UX Clients Managing HP-UX Clients For UNIX Client information for a client running on a HP-UX system is stored in the sna_clnt.net file, whic h is created when you install the SNAplus2 software on the c lient.
296 Chapter 11 Managing SNAplus2 Clients Managing HP-UX Clients HP-UX Client Network Data F ile (sna_clnt.net) The sna_clnt.net file defines the SNAplus2 facilities available on a client computer running on a HP-UX system, and the servers the client can access .
Chapter 11 297 Managing SNAplus2 Clients Managing HP-UX Clients that issue the Accept_Conversation or Accept_Incoming verbs). In this case, you ma y also need to define the TP on this client. F or more information, see “Defining TPs”. Specify invoked_tps = NO if this client is not used to run invoked TPs .
298 Chapter 11 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.
Chapter 11 299 Managing SNAplus2 Clients Managing HP-UX Clients received no response, the c lient attempts to contact the first server listed using a directed message.
300 Chapter 11 Managing SNAplus2 Clients Managing HP-UX Clients.
301 A Configuration Planning W orksheets.
302 Appendix A Configuration Planning W orksheets Overview Overview This appendix provides worksheets for configuring specific functions of SNAplus2.
Appendix A 303 Configuration Planning W orksheets Node W orksheets Node W orksheets Complete only one of the following worksheets: • “ APPN End Node” • “LEN Node” APPN End Node Complete t.
304 Appendix A Configuration Planning W orksheets Node W orksheets 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). Client/Server Configuration: Not required for a standalone node.
Appendix A 305 Configuration Planning W orksheets Node W orksheets Client/Server Configuration: Not required for a standalone node. Configuration server? Should the node act as a configuration server , to store information about domain resources in the SNAplus2 LAN? Application Configuration: See “User Application Support W orksheets”.
306 Appendix A Configuration Planning W orksheets Connectivity W orksheets Connectivity W orksheets F or each link protocol used to communicate with another node, complete one of the following worksheets . If necessary , you can configure more than one link station on a port.
Appendix A 307 Configuration Planning W orksheets Connectivity W orksheets Link role Negotiable Primary Primary multi-drop Secondary F or switched incoming or leased line: P oll address Only for nonprimary , switc hed incoming ports On a VTAM host, the poll address is configured as the ADDR= parameter in the VTAM PU definition.
308 Appendix A Configuration Planning W orksheets Connectivity W orksheets Activation By administrator On node startup On demand LU traffic Any Independent only Dependent only Independent LU traffic Remote node NETNAME .
Appendix A 309 Configuration Planning W orksheets Connectivity W orksheets Downstream PU name 1–8 type A EBCDIC characters Upstream DLUS name NETNAME . LUNAME (each 1–8 type A EBCDIC characters) Contact information P oll address F or switched incoming ports , only configured on the port.
310 Appendix A Configuration Planning W orksheets Connectivity W orksheets T oken Ring Complete this worksheet to support connectivity using the token ring link protocol.
Appendix A 311 Configuration Planning W orksheets Connectivity W orksheets Remote node NETNAME . CPNAME (each 1–8 type A EBCDIC characters; optional) If the remote system is a VTAM host, you can find the network name (the first eight characters of the fully qualified name) in the NETID parameter of the VTAM Start command.
312 Appendix A Configuration Planning W orksheets Connectivity W orksheets Ethernet Complete this worksheet to support connectivity using the Ethernet link protocol.
Appendix A 313 Configuration Planning W orksheets Connectivity W orksheets Motif Field V alid Entry/Notes Y our Implementation V alue Ethernet SAP Dialog SNA port name Up to 8 characters Ethernet car.
314 Appendix A Configuration Planning W orksheets Connectivity W orksheets Remote node NETNAME . CPNAME (each 1–8 type A EBCDIC characters; optional) If the remote system is a VTAM host, you can find the network name (the first eight characters of the fully qualified name) in the NETID parameter of the VTAM Start command.
Appendix A 315 Configuration Planning W orksheets Connectivity W orksheets FDDI Complete this worksheet to support connectivity using the FDDI link protocol. Contact information MAC address Hexadecimal digits If the remote end of this link is a VTAM host, you can find its MAC address in the MACADDR= parameter of the VTAM P ort definition.
316 Appendix A Configuration Planning W orksheets Connectivity W orksheets Motif Field V alid Entry/Notes Y our Implementation V alue FDDI SAP Dialog SNA port name Up to 8 characters FDDI card number.
Appendix A 317 Configuration Planning W orksheets Connectivity W orksheets Remote node NETNAME . CPNAME (each 1–8 type A EBCDIC characters; optional) If the remote system is a VTAM host, you can find the network name (the first eight characters of the fully qualified name) in the NETID parameter of the VTAM Start command.
318 Appendix A Configuration Planning W orksheets Connectivity W orksheets QLLC (X.25) Complete this worksheet to support connectivity using the QLLC (X.
Appendix A 319 Configuration Planning W orksheets Connectivity W orksheets Motif Field V alid Entry/Notes Y our Implementation V alue QLLC P ort Dialog SNA port name Up to 8 characters X.25 card number 0 to number_of_cards_minus_1 P ort number 0 to number_of_ports_on_card_minus_1 Initially active Select if needed Match incoming X.
320 Appendix A Configuration Planning W orksheets Connectivity W orksheets Remote node NETNAME . CPNAME (each 1–8 type A EBCDIC characters; optional) If the remote system is a VTAM host, you can find the network name (the first eight characters of the fully qualified name) in the NETID parameter of the VTAM Start command.
Appendix A 321 Configuration Planning W orksheets Connectivity W orksheets Circuit type Permanent virtual circuit Switched virtual circuit Channel ID 1 – 4096 (only for PVC) Remote X.
322 Appendix A Configuration Planning W orksheets Passthr ough Ser vices W orksheets P assthrough Services W orksheets Complete worksheets for any of the passthrough services described in the followi.
Appendix A 323 Configuration Planning W orksheets Passthr ough Ser vices W orksheets PU Concentration Complete this worksheet if the local node is to support PU concentration. Initially active Select if needed Reactivate PU after failure Select if needed Local LU and Application Configuration: See “User Application Support W orksheets”.
324 Appendix A Configuration Planning W orksheets Passthr ough Ser vices W orksheets TN Server Complete this worksheet if the local node is to support TN3270 clients .
Appendix A 325 Configuration Planning W orksheets Passthr ough Ser vices W orksheets TN3270 client address Specify one of the following: • Default record (any TN3270 client) • TCP/IP address (dot.
326 Appendix A Configuration Planning W orksheets User Application Support W orksheets User Application Support W orksheets Complete the following worksheets if the corresponding user -level applicat.
Appendix A 327 Configuration Planning W orksheets User Application Support W orksheets LU number 1 – 255 This value must match the LOCADDR parameter in the VTAM/NCP LU resource definition statement.
328 Appendix A Configuration Planning W orksheets User Application Support W orksheets Location NETNAME . CPNAME (each 1–8 type A EBCDIC characters) LS Routing Dialog: Only required if partner LU is located by link station. LU name 1–8 type A EBCDIC characters LS name Up to 8 characters P artner LU name ( NETNAME .
Appendix A 329 Configuration Planning W orksheets User Application Support W orksheets Maximum RU size Recommended upper limit is 1024 . Session Security Dialog: Only required if session security is required for sessions between a specific local and partner LU .
330 Appendix A Configuration Planning W orksheets User Application Support W orksheets CPI-C Complete this worksheet if the local node is to support CPI-C applications .
Appendix A 331 Configuration Planning W orksheets User Application Support W orksheets 5250 Complete this worksheet if the local node is to support 5250 communications . Motif Field V alid Entry/Notes Y our Implementation V alue Node Configuration: See “Node W orksheets”.
332 Appendix A Configuration Planning W orksheets User Application Support W orksheets 3270 Complete this worksheet if the local node is to support 3270 communications . Motif Field V alid Entry/Notes Y our Implementation V alue Node Configuration: See “Node W orksheets”.
Appendix A 333 Configuration Planning W orksheets User Application Support W orksheets LU numbers 1 – 255 (for a range, supply first and last numbers) This value must match the LOCADDR parameter in the VTAM/NCP LU resource definition statement.
334 Appendix A Configuration Planning W orksheets User Application Support W orksheets RJE Complete this worksheet if the local node is to support RJE communications with a host.
Appendix A 335 Configuration Planning W orksheets User Application Support W orksheets Motif Field V alid Entry/Notes Y our Implementation V alue Node Configuration: See “Node W orksheets”. Connectivity Configuration: See “Connectivity W orksheets” (configure for dependent traffic).
336 Appendix A Configuration Planning W orksheets User Application Support W orksheets LU A Complete this worksheet if the local node is to support LU A applications . Motif Field V alid Entry/Notes Y our Implementation V alue Node Configuration: See “Node W orksheets”.
337 B APPN Network Management Using the Simple Network Management Protocol.
338 Appendix B APPN Network Management Using the Simple Network Management Protocol Overview Overview This appendix briefly introduces the Simple Network Management Protocol (SNMP), the SNMP components (manager , agent, subagent), the APPN Management Information Base (MIB), and the APPN SNMP subagent component of SNAplus2.
Appendix B 339 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 .
340 Appendix B 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).
Appendix B 341 APPN Network Management Using the Simple Network Management Protocol SNAplus2 APPN SNMP Subagent SNAplus2 APPN SNMP Subagent SNAplus2 implements an SNMP subagent to provide support for the APPN MIB defined in RFC 1593. The subagent uses the services of the SNMPD daemon, which communicates with a management application using TCP/IP .
342 Appendix B APPN Network Management Using the Simple Network Management Protocol APPN Management Information Base (MIB) APPN Management Information Base (MIB) The APPN MIB is defined by informational RFC 1593. The ASN .1 representation of the APPN MIB is located in the file named /etc/opt/sna/mib/appn.
343 C Configuring an Invokable TP Using snaptpinstall.
344 Appendix C Configuring an Invokab le TP Using snaptpinstall Overview Overview The snaptpinstall utility is a command-line application that enables a user or the writer of a TP installation program to define an invokable TP . Y ou can run snaptpinstall on a server or client.
Appendix C 345 Configuring an Invokab le TP Using snaptpinstall File Format for snaptpinstall F ile F ormat for snaptpinstall The file that supplies configuration information for an invokable TP is an ASCII text file that can be modified using any standard text editor .
346 Appendix C Configuring an Invokab le TP Using snaptpinstall File Format for snaptpinstall on the RECEIVE_ALLOCA TE 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 .
Appendix C 347 Configuring an Invokab le TP Using snaptpinstall File Format for snaptpinstall The TP is a queued TP . Any incoming Allocate requests arriving while the TP is running are queued until the TP issues another Receive_Allocate, or until it finishes running and can be restarted.
348 Appendix C Configuring an Invokab le TP Using snaptpinstall File Format for snaptpinstall If you use NON-QUEUED , more than one copy of the TP can be running at a time. If the TP writes to files on the Windows computer , you need to ensure that different copies of the TP do not overwrite each other's files .
Appendix C 349 Configuring an Invokab le TP Using snaptpinstall File Format for snaptpinstall TP (unless the application overrides it by specifying a full path).
350 Appendix C Configuring an Invokab le TP Using snaptpinstall File Format for snaptpinstall If the LU alias is specified for an automatically started TP , the TP must use the extended form of the RECEIVE_ALLOCA TE verb and specify this LU alias as a parameter to the verb.
Appendix C 351 Configuring an Invokab le TP Using snaptpinstall File Format for snaptpinstall The application is displayed at its normal size and position. NOACTIVATE The application is displayed at its normal size and position, and the focus remains on the previously active window .
352 Appendix C Configuring an Invokab le 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).
353 D Using SNAplus2 in a High A vailability Environment.
354 Appendix D Using SNAplus2 in a High A vailability En vironment Overview Overview This appendix describes the high availability features of SNAplus2 and how it works with the HP MC/ServiceGuard product.
Appendix D 355 Using SNAplus2 in a High A vailability En vironment What is High A vailability? What is High A vailability? High availability is a term used to describe an environment in which mission critical applications are protected from severe impact of various failures .
356 Appendix D Using SNAplus2 in a High A vailability En vironment What is High A vailability? Figure D-1 SNAplus2 client/server network In this environment, applications run on client systems (HP9000s or PCs) and access the IBM mainframe through an HP9000 S800 server .
Appendix D 357 Using SNAplus2 in a High A vailability En vironment What is High A vailability? • The LAN networking software on the server system • The SNAplus2 Link software on the server system .
358 Appendix D Using SNAplus2 in a High A vailability En vironment SNAplus2 High A vailability Features SNAplus2 High A vailability F eatures SNAplus2 already has high availability features built in, namely , LU pools , and client/server configurations.
Appendix D 359 Using SNAplus2 in a High A vailability En vironment SNAplus2 High A vailability Features Figure D-2 LU P ools The LU pool gives you the ability to add a logical layer on top of the two servers. Clients access the SNA network by referring to the LU pool name, not to a specific LU in the pool.
360 Appendix D Using SNAplus2 in a High A vailability En vironment SNAplus2 High A vailability Features for high availability environments in that applications running on client systems can access ports on multiple servers .
Appendix D 361 Using SNAplus2 in a High A vailability En vironment SNAplus2 High A vailability Features Figure D-3 Applications using multiple servers The second wa y an application can use multiple servers is to have one SNAplus2 configuration that is used by multiple HP 9000 systems.
362 Appendix D Using SNAplus2 in a High A vailability En vironment SNAplus2 High A vailability Features T able D-1 NO TE The above example will be used throughout this appendix to explain many different aspects of high availability systems . In this example, nine LUs are used by APPC production applications that run on the client systems .
Appendix D 363 Using SNAplus2 in a High A vailability En vironment SNAplus2 High A vailability Features Figure D-4 SNAplus2 on Primary and Backup Servers Whenever the primary server is about to become.
364 Appendix D Using SNAplus2 in a High A vailability En vironment SNAplus2 High A vailability Features At this point, the backup server has completely taken over the primary server and is providing the HALU01 ... HALU09 LUs for the production applications .
Appendix D 365 Using SNAplus2 in a High A vailability En vironment Using SNAplus2 with MC/ServiceGuard Using SNAplus2 with MC/ServiceGuard MC/ServiceGuard (product number B3935AA) is a specialized fac.
366 Appendix D Using SNAplus2 in a High A vailability En vironment 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 .
Appendix D 367 Using SNAplus2 in a High A vailability En vironment Using SNAplus2 with MC/ServiceGuard Step 1. List all of the mission critical applications that use SNAplus2 for SNA network connectivity .
368 Appendix D Using SNAplus2 in a High A vailability En vironment Using SNAplus2 with MC/ServiceGuard Assuming the applications attempt to activate a new LU-LU session when they lose the LU-LU session they were using , you simply need to wait for the migration to occur .
Appendix D 369 Using SNAplus2 in a High A vailability En vironment Using SNAplus2 with MC/ServiceGuard T able D-2 Suggestions for Defining the SNAplus2 P ackage Specifying the Service Command The Service Command starts a Service, whic h is an HP-UX process that ServiceGuard monitors.
370 Appendix D Using SNAplus2 in a High A vailability En vironment Using SNAplus2 with MC/ServiceGuard snapadmin start_ls, ls_name=HALS LS details are: Activation state = active P ort 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.
Appendix D 371 Using SNAplus2 in a High A vailability En vironment Using SNAplus2 with MC/ServiceGuard and become active. If this parameter is not specified, 10 retries will be allowed. Any number between 0 and 600 (inclusive) can be specified. The return code of snapmon is 0 if the LS was active at some time while snapmon was running .
372 Appendix D Using SNAplus2 in a High A vailability En vironment Using SNAplus2 with MC/ServiceGuard capability . F ollowing are four different ways in which applications can gain SNA network connectivity through an SNAplus2 server using a LAN .
Appendix D 373 Using SNAplus2 in a High A vailability En vironment Using SNAplus2 with MC/ServiceGuard T o protect against a failure of a server’s LAN adapter , you can configure a standby LAN adapter for the server .
374 Appendix D Using SNAplus2 in a High A vailability En vironment Using SNAplus2 with MC/ServiceGuard TN Server LAN Connections One application that can take advantage of both local LAN failover and floating IP addresses in an SNAplus2 network is TN3270.
Appendix D 375 Using SNAplus2 in a High A vailability En vironment Using SNAplus2 with MC/ServiceGuard Using the LAN to Access Standalone Servers When SNAplus2 is used in a standalone configuration, the LAN can still be used to access the server system.
376 Appendix D Using SNAplus2 in a High A vailability En vironment Using SNAplus2 with MC/ServiceGuard Customizing the SNAplus2 P ackage Control Script The last step in defining an SNAplus2 package is customizing the P ackage Control Script to instruct ServiceGuard how to start and stop the SNAplus2 software associated with the pac kage.
Appendix D 377 Using SNAplus2 in a High A vailability En vironment Using SNAplus2 with MC/ServiceGuard the SNAplus2 software . Insert this command in the customer_defined_halt_cmds section of the P ac.
378 Appendix D Using SNAplus2 in a High A vailability En vironment Using SNAplus2 with MC/ServiceGuard start the node on the backup server until SNAplus2 recognizes that the primary server is down.
Appendix D 379 Using SNAplus2 in a High A vailability En vironment Using SNAplus2 with MC/ServiceGuard Figure D-11 Client/Server configuration using T oken Ring LAN DLC QLLC If you are using QLLC links , both servers must have the same name configured in the X.
380 Appendix D Using SNAplus2 in a High A vailability En vironment Using SNAplus2 with MC/ServiceGuard Interface card. . . . . . . . . . [card0.......] The backup server should also be configured so that its X.
Appendix D 381 Using SNAplus2 in a High A vailability En vironment Using SNAplus2 with MC/ServiceGuard T o 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.
382 Appendix D Using SNAplus2 in a High A vailability En vironment Adv anced Configuration T echniques Advanced Configuration T echniques The following advanced configuration techniques are useful in networks where there are multiple DLC (Data Link Control) types connecting one or more HP 9000 server s to the remote SNA system.
Appendix D 383 Using SNAplus2 in a High A vailability En vironment Adv anced Configuration T echniques to add more intelligence to the Service in the P ackage Control Script that will allow you to attempt local recovery before informing ServiceGuard that a remote failover is necessary .
384 Appendix D Using SNAplus2 in a High A vailability En vironment Adv anced Configuration T echniques commands in the script. The ability to add other SNAplus2 commands gives you a wa y to specify local recovery actions before allowing the script to end.
Appendix D 385 Using SNAplus2 in a High A vailability En vironment Adv anced Configuration T echniques # # 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.
386 Appendix D Using SNAplus2 in a High A vailability En vironment Adv anced Configuration T echniques quits trying to perform a local restart of the T oken Ring LS , and attempts to start the SDLC LS . When that LS fails, the script exits , to allow ServiceGuard to perform a remote failover .
Index 387 Numerics 3270 emulation group additional configuration needs , 216 emulation group parameters 3270 permissions , 215 Group Name , 214 Sessions , 215 Style File , 214 Style file access , 21.
388 Index port facility , 58 network example , 44 network node , 30 , 45 node , 75 node types , 43 route selection , 56 SNMP subagent , 341 APPN support parameter , 137 Arguments parameter , 191 AS/40.
Index 389 additional configuration needs , 153 APPN , 60 configuration , 147 parameters , 148 configuration methods , 147 description , 43 , 92 , 93 topology information , 54 connectivity configur.
390 Index additional configuration needs , 166 configuration , 233 description , 64 , 77 worksheet , 322 DLUR PU configuration methods , 164 parameters DLUS Name , 165 Initially active , 165 PU ID .
Index 391 HLLAPI , 32 , 83 host , 28 host communication example configuration , 69 Host LS/DLUR PU parameter , 170 , 179 host node , 27 HPR description , 53 HP-UX client * , 298 broadcast_attempt_cou.
392 Index description , 16 , 33 independent , 94 pool , 95 types , 33 , 94 LU 0 description , 34 LU 1 , 34 LU 2 , 34 LU 3 , 33 LU 6.2 configuration , 176 description , 33 LU alias parameter , 179 , 1.
Index 393 Domain window , 117 help , 127 invoking , 115 Node window , 119 resource items , 122 resource windows , 116 tool bar buttons , 123 using , 115 MS (Management Services) , 45 , 84 Multiple ins.
394 Index path for SNAplus2 executable programs , 111 peer network , 26 node types , 30 route selection , 41 peer server , 87 peer -to-peer communications See APPN , 25 peripheral node , 27 physical u.
Index 395 configuration methods , 220 parameters Assigned LUs , 221 Run on computer , 220 UNIX group name , 221 UNIX user name , 221 W orkstation name , 220 style file , 104 route , 41 Route incomin.
396 Index start command , 112 stop command , 114 STREAMS components , 74 style file 3270 emulation program , 104 RJE workstation , 104 Style file access parameter , 215 Style File parameter , 214 su.
Index 397 transport network , 42 troubleshooting , 105 TRS (topology and routing services) , 53 type 2.0 node , 27 type 2.1 node , 27 type 4 node , 27 type 5 node , 27 U UCF access to files , 247 can.
398 Index Win32 client 3270 message tracing information , 270 admin_msg , 272 all_api , 268 API tracing information , 267 appc , 268 APPCLLU , 273 APPCTPN , 273 audit_file , 265 audit_file_wrap_size.
An important point after buying a device HP (Hewlett-Packard) HP-UX SNAplus2 (or even before the purchase) is to read its user manual. We should do this for several simple reasons:
If you have not bought HP (Hewlett-Packard) HP-UX SNAplus2 yet, this is a good time to familiarize yourself with the basic data on the product. First of all view first pages of the manual, you can find above. You should find there the most important technical data HP (Hewlett-Packard) HP-UX SNAplus2 - thus you can check whether the hardware meets your expectations. When delving into next pages of the user manual, HP (Hewlett-Packard) HP-UX SNAplus2 you will learn all the available features of the product, as well as information on its operation. The information that you get HP (Hewlett-Packard) HP-UX SNAplus2 will certainly help you make a decision on the purchase.
If you already are a holder of HP (Hewlett-Packard) HP-UX SNAplus2, but have not read the manual yet, you should do it for the reasons described above. You will learn then if you properly used the available features, and whether you have not made any mistakes, which can shorten the lifetime HP (Hewlett-Packard) HP-UX SNAplus2.
However, one of the most important roles played by the user manual is to help in solving problems with HP (Hewlett-Packard) HP-UX SNAplus2. Almost always you will find there Troubleshooting, which are the most frequently occurring failures and malfunctions of the device HP (Hewlett-Packard) HP-UX SNAplus2 along with tips on how to solve them. Even if you fail to solve the problem, the manual will show you a further procedure – contact to the customer service center or the nearest service center
