txseries for multiplatforms using hp-ux snaplus2 with cics version 6.2

8/9/2019 TXSeries for Multiplatforms Using HP-UX SNAplus2 With CICS Version 6.2

1/77

TXSeries for Multiplatforms

Using HP-UX SNAplus2 with CICS

Version 6.2

SC34-6750-01


2/77


3/77

TXSeries for Multiplatforms

Using HP-UX SNAplus2 with CICS

Version 6.2

SC34-6750-01


4/77

Note

Before using this information and the product it supports, be sure to read the general information under “Notices” on page55.

Second Edition (January 2008)

This edition replaces SC34-6750-00.

Order publications through your IBM representative or through the IBM branch office serving your locality.

© Copyright International Business Machines Corporation 2002, 2008. All rights reserved.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.


5/77

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

About this book . . . . . . . . . . . . . . . . . . . . . . . . ixWho should read this book . . . . . . . . . . . . . . . . . . . . . ixDocument organization . . . . . . . . . . . . . . . . . . . . . . ixConventions used in this book. . . . . . . . . . . . . . . . . . . . xHow to send your comments . . . . . . . . . . . . . . . . . . . . xi

Chapter 1. Introduction to SNA. . . . . . . . . . . . . . . . . . . 1Basic SNA definitions . . . . . . . . . . . . . . . . . . . . . . . 1A sample network . . . . . . . . . . . . . . . . . . . . . . . . 1SNA connections . . . . . . . . . . . . . . . . . . . . . . . . 2Connections at the logical level . . . . . . . . . . . . . . . . . . 2Connections at the physical level. . . . . . . . . . . . . . . . . . 3Communicating across SNA connections . . . . . . . . . . . . . . . 4

Chapter 2. Collecting information for a HP-UX SNAplus2 configuration . . . 7Collecting information about the local HP-UX machine (node) . . . . . . . . 7Collecting information about remote machines . . . . . . . . . . . . . . 7Collecting information about a local CICS region . . . . . . . . . . . . . 9Collecting information about remote CICS regions . . . . . . . . . . . . 10Collecting information about modegroups . . . . . . . . . . . . . . . 11System-defined SNASVCMG and CPSVCMG modegroups . . . . . . . 12

Chapter 3. Choosing a communication configuration . . . . . . . . . 13Using the PPC Gateway server . . . . . . . . . . . . . . . . . . . 13Using local SNA . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 4. Installing HP-UX SNAplus2 . . . . . . . . . . . . . . . 17Initial installation of HP-UX SNAplus2 . . . . . . . . . . . . . . . . 17Kernel configuration for use of HP-UX SNAplus2 . . . . . . . . . . . . 17Migration from HP-UX SNAplus. . . . . . . . . . . . . . . . . . . 17

Chapter 5. System management for HP-UX SNAplus2 . . . . . . . . . 19Starting the HP-UX SNAplus2 GUI administration utility . . . . . . . . . . 19Defining a token ring port . . . . . . . . . . . . . . . . . . . . . 21Defining a local LU name for CICS local SNA support . . . . . . . . . . 22Defining a local LU name for PPC Gateway support . . . . . . . . . . . 23Defining a partner LU on a remote node . . . . . . . . . . . . . . . 25Defining a link station . . . . . . . . . . . . . . . . . . . . . . 27

Defining a modename . . . . . . . . . . . . . . . . . . . . . . 29Defining a default modename . . . . . . . . . . . . . . . . . . . 31Defining the bind password . . . . . . . . . . . . . . . . . . . . 32Defining conversation level security . . . . . . . . . . . . . . . . . 33Activating a token ring and link station . . . . . . . . . . . . . . . . 33Using the command-line HP-UX SNAplus2 utility . . . . . . . . . . . . 34

Chapter 6. Configuring VTAM with details of your CICS region . . . . . . 35Defining your machine and CICS regions to VTAM. . . . . . . . . . . . 35Defining modegroups to VTAM . . . . . . . . . . . . . . . . . . . 36

© Copyright IBM Corp. 2002, 2008 iii


6/77

Chapter 7. Problem determination for HP-UX SNAplus2 . . . . . . . . 39HP-UX SNAplus2 common configuration problems. . . . . . . . . . . . 39All SNA communications fail . . . . . . . . . . . . . . . . . . . 39

HP-UX SNAplus2 problem determination procedures . . . . . . . . . . . 40Getting help from the Hewlett-Packard Response Center . . . . . . . . . 40

Appendix A. Sample configuration for HP-UX SNAplus2 . . . . . . . . 41

The sna_node.cfg file . . . . . . . . . . . . . . . . . . . . . . 41The sna_domn.cfg file . . . . . . . . . . . . . . . . . . . . . . 47The sna.ini file . . . . . . . . . . . . . . . . . . . . . . . . . 48

Appendix B. Sample configuration of CICS for HP-UX . . . . . . . . . 49

Appendix C. Sample definitions for CICS/ESA . . . . . . . . . . . . 51

Appendix D. Bibliography . . . . . . . . . . . . . . . . . . . . 53SNA books . . . . . . . . . . . . . . . . . . . . . . . . . . 53HP-UX SNAplus books . . . . . . . . . . . . . . . . . . . . . . 53CICS books . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Trademarks and service marks . . . . . . . . . . . . . . . . . . . 56

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

iv TXSeries for Multiplatforms: Using HP-UX SNAplus2 with CICS


7/77

Figures

1. An example heterogeneous network . . . . . . . . . . . . . . . . . . . . . . . . 22. A simplified example heterogeneous network . . . . . . . . . . . . . . . . . . . . . 83. Obtaining the address of a remote machine using the ping and arp -a commands . . . . . . . 94. Matching HP-UX SNAplus2 and PPC Gateway server names with CICS definitions . . . . . . 145. Matching HP-UX SNAplus2 names with CICS definitions (local SNA) . . . . . . . . . . . 156. SNAplus2 node screen display. . . . . . . . . . . . . . . . . . . . . . . . . . 207. Add token ring display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218. Token ring SAP display . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229. Local LU screen display . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2310. Local LU for the PPC Gateway . . . . . . . . . . . . . . . . . . . . . . . . . 2411. PPC Gateway advanced settings display . . . . . . . . . . . . . . . . . . . . . . 2412. Remote node screen display . . . . . . . . . . . . . . . . . . . . . . . . . . 2513. Automatically defined remote LU display . . . . . . . . . . . . . . . . . . . . . . 2614. Partner LU screen display . . . . . . . . . . . . . . . . . . . . . . . . . . . 2715. Token ring link station screen display . . . . . . . . . . . . . . . . . . . . . . . 2816. Token ring parameters screen display . . . . . . . . . . . . . . . . . . . . . . . 29

17. The Modes screen display . . . . . . . . . . . . . . . . . . . . . . . . . . . 3018. Mode screen attributes display . . . . . . . . . . . . . . . . . . . . . . . . . . 3119. Session security- node_name screen display . . . . . . . . . . . . . . . . . . . . 3220. Session security screen attributes display. . . . . . . . . . . . . . . . . . . . . . 3321. define_node_config_file . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4122. define_node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4223. define_tr_dlc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4224. define_tr_port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4325. define_tr_ls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4426. define_local_lu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4527. define_partner_lu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4528. define_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4629. define_directory_entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

30. define_lu_lu_password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4731. define_defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4732. define_rcf_access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4733. set_log_file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4734. define_domain_config_file . . . . . . . . . . . . . . . . . . . . . . . . . . . 4835. set_global_log_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4836. set_central_logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4837. Sample sna.ini file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4838. Sample region definition (RD) . . . . . . . . . . . . . . . . . . . . . . . . . . 4939. Sample gateway definition (GD) . . . . . . . . . . . . . . . . . . . . . . . . . 4940. Sample communications definition (CD) . . . . . . . . . . . . . . . . . . . . . . 4941. CEDA output for connection definitions (CICS/ESA) . . . . . . . . . . . . . . . . . . 5142. CEDA output for session definition (CICS/ESA). . . . . . . . . . . . . . . . . . . . 52

© Copyright IBM Corp. 2002, 2008 v


8/77

vi TXSeries for Multiplatforms: Using HP-UX SNAplus2 with CICS


9/77

Tables

1. Getting started road map . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix2. Conventions that are used in this book . . . . . . . . . . . . . . . . . . . . . . . x3. Information required to describe an example local HP-UX machine . . . . . . . . . . . . . 74. Information required to define example links . . . . . . . . . . . . . . . . . . . . . 95. Information required to define a local LU . . . . . . . . . . . . . . . . . . . . . . 106. Information required to define example remote CICS regions . . . . . . . . . . . . . . 107. Information required to define example modegroups . . . . . . . . . . . . . . . . . . 11

© Copyright IBM Corp. 2002, 2008 vii


10/77

viii TXSeries for Multiplatforms: Using HP-UX SNAplus2 with CICS


11/77

About this book

The Customer Information Control System (CICS ® ) requires a Systems NetworkArchitecture (SNA) product to connect to an SNA network. This book describes howto set up and use the HP-UX SNAplus2 product with HP-UX CICS.

Topics include how to: configure HP-UX SNAplus2; coordinate the configuration ofHP-UX SNAplus2 with the configuration of CICS and its partner systems; operateHP-UX SNAplus2; and investigate communication errors. A review of some of thebasic SNA terminology is also included.

Who should read this book

This book is designed for system administrators who configure, operate, andmanage SNA networks.

You should be familiar with CICS products and have an understanding of theconcepts of SNA. The TXSeries for Multiplatforms Intercommunication Guide is the

primary source of information about the communication features of CICS. It givesalso examples of configurations and advice about systems design.

Document organization

Table 1. Getting started road map

If you want to... Refer to...

Review SNA concepts and terminology Chapter 1, “Introduction to SNA,” on page 1

Plan information-gathering strategies Chapter 2, “Collecting information for a HP-UX SNAplus2configuration,” on page 7

Consider configuration options Chapter 3, “Choosing a communication configuration,” onpage 13

Read about installation, kernel configuration, andmigration

Chapter 4, “Installing HP-UX SNAplus2,” on page 17

Use system administration tools Chapter 5, “System management for HP-UX SNAplus2,”on page 19

Communicate with EBCDIC mainframes Chapter 6, “Configuring VTAM with details of your CICSregion,” on page 35

Solve communication problems Chapter 7, “Problem determination for HP-UX SNAplus2,”on page 39

See sample configurations Appendix A, “Sample configuration for HP-UX SNAplus2,”on page 41 and Appendix B, “Sample configuration ofCICS for HP-UX,” on page 49

See the sample definitions for CICS / ESA Appendix C, “Sample definitions for CICS/ESA,” on page51

Read through the Bibliography Appendix D, “Bibliography,” on page 53

© Copyright IBM Corp. 2002, 2008 ix


12/77

Conventions used in this book

TXSeries ® for Multiplatforms documentation uses the following typographical andkeying conventions.

Table 2. Conventions that are used in this book

Convention Meaning

Bold Indicates values that you must use literally, such as commands,functions, and resource definition attributes and their values. Whenreferring to graphical user interfaces (GUIs), bold also indicatesmenus, menu items, labels, buttons, icons, and folders.

Monospace Indicates text that you must enter at a command prompt. Monospacealso indicates screen text and code examples.

Italics Indicates variable values that you must provide (for example, yousupply the name of a file for file_name ). Italics also indicatesemphasis and the titles of books.

< > Encloses the names of keys on the keyboard.

Where x is the name of a key, indicates a control-charactersequence. For example, means hold down the Ctrl key

while you press the c key.

Refers to the key labeled with the word Return, the word Enter, orthe left arrow.

% Represents the UNIX ® command-shell prompt for a command thatdoes not require root privileges.

# Represents the UNIX command-shell prompt for a command thatrequires root privileges.

C:\> Represents the Windows ® command prompt.

> When used to describe a menu, shows a series of menu selections.For example, ″Select File > New″ means ″From the File menu,select the New command.″

Entering commands When instructed to “enter” or “issue” a command, type the commandand then press . For example, the instruction “Enter the lscommand” means type ls at a command prompt and then press.

[ ] Encloses optional items in syntax descriptions.

{ } Encloses lists from which you must choose an item in syntaxdescriptions.

| Separates items in a list of choices enclosed in { } (braces) in syntaxdescriptions.

... Ellipses in syntax descriptions indicate that you can repeat thepreceding item one or more times. Ellipses in examples indicate thatinformation was omitted from the example for the sake of brevity.

IN In function descriptions, indicates parameters whose values are usedto pass data to the function. These parameters are not used toreturn modified data to the calling routine. (Do not include the INdeclaration in your code.)

OUT In function descriptions, indicates parameters whose values are usedto return modified data to the calling routine. These parameters arenot used to pass data to the function. (Do not include the OUTdeclaration in your code.)

x TXSeries for Multiplatforms: Using HP-UX SNAplus2 with CICS


13/77

Table 2. Conventions that are used in this book (continued)

Convention Meaning

INOUT In function descriptions, indicates parameters whose values arepassed to the function, modified by the function, and returned to thecalling routine. These parameters serve as both IN and OUTparameters. (Do not include the INOUT declaration in your code.)

$CICS Indicates the full path name of the location in which the CICSproduct is installed; for example, /usr/lpp/cics on AIX ® . If the CICSenvironment variable is set to the product path name, you can usethe examples exactly as shown in this book; otherwise, you mustreplace all instances of $CICS with the CICS product path name.

CICS on OpenSystems

Refers collectively to the CICS product for all supported UNIXplatforms.

TXSeries forMultiplatforms

Refers collectively to the CICS for AIX, CICS for HP-UX, CICS forSolaris, and CICS for Windows products.

CICS Refers generically to the CICS for AIX, CICS for HP-UX (HP-UXPA-RISC and HP-UX IPF), CICS for Solaris, and CICS for Windowsproducts. Other CICS products in the CICS Family are distinguishedby their operating system (for example, IBM ® mainframe-based CICS

for the z/OS platform).

How to send your comments

Your feedback is important in helping to provide the most accurate and highestquality information. If you have any comments about this book or any otherTXSeries documentation, send your comments by e-mail to [email protected] sure to include the name of the book, the document number of the book, theversion of TXSeries, and, if applicable, the specific location of the information youare commenting on (for example, a page number or table number).

About this book xi


14/77

xii TXSeries for Multiplatforms: Using HP-UX SNAplus2 with CICS


15/77

Chapter 1. Introduction to SNA

This section introduces Systems Network Architecture (SNA) concepts andterminology that you must understand when using CICS in an SNA environment.The discussion in this chapter includes:

v “Basic SNA definitions”

v “A sample network”

v “SNA connections” on page 2

v “Connections at the logical level” on page 2

v “Connections at the physical level” on page 3

v “Communicating across SNA connections” on page 4

Basic SNA definitions

IBM SNA defines a set of rules that systems use to communicate. These rulesdefine the format , which is the layout of the data that flows between the systems,and the protocol , which is the action that the systems take when they receive the

data. Together, the format and protocol make the architecture .

SNA does not specify how a system implements the rules. A fundamental objectiveof SNA is to allow communication between systems that have very different internalhardware and software designs. The only requirement is that the externals meet therules of the architecture.

A sample network

Figure 1 on page 2 shows a heterogeneous network; it shows a HP-UX SNAplus2system intercommunicating with several different types of CICS regions.

© Copyright IBM Corp. 2002, 2008 1


16/77

Each CICS system uses its own platform-specific SNA product. CICS OS/2 usesCommunications Manager/2. CICS/400 uses OS/400 ® Intercommunication Facility(ICF). IBM mainframe-based CICS works very closely with VirtualTelecommunications Access Method (VTAM ® ) to support SNA.

When you are configuring your CICS region to communicate with another CICSsystem, you must understand the SNA product that the other system uses. Althoughthe two systems must agree on common parameters, the terminology that is used

for these parameters can differ.

SNA connections

You can connect CICS systems in a network in many ways. If the data issuccessfully transferred in the correct format, the CICS systems are unaware of thenetwork makeup. SNA configuration is performed at two levels:

v The logical level , which incorporates the characteristics of the systems that wantto communicate.

v The physical level , which incorporates the linking of actual machines in thenetwork.

The next two sections, “Connections at the logical level” and “Connections at thephysical level” on page 3, describe these connection levels in detail, and introduceyou to the common SNA terminology that is associated with them. “Communicatingacross SNA connections” on page 4 discusses communication across theseconnections.

Connections at the logical levelA Logical Unit (LU) is an SNA term that describes a logical collection of servicesthat can be accessed from a network. SNA defines many different types of LUs. ACICS region can be an LU, and devices like terminals and printers can also be LUs.The type of LU that is used for CICS intersystem communication is LU type 6.2 .

Figure 1. An example heterogeneous network

2 TXSeries for Multiplatforms: Using HP-UX SNAplus2 with CICS


17/77

Each LU is identified by a name of up to eight characters that is referred to as theLU name . The LU name that describes the local region is called the local LU . LUsthat describe remote systems are called partner LUs . The LU name that identifiesan IBM mainframe-based CICS system is the APPLID, which is defined in the CICSsystem initialization table. (The APPLID is also referred to as a NETNAME ). The LUname for a CICS OS/2 system is specified in the Communications Manager/2 LocalLU definition, and the LU name for a CICS/400 system is defined in the APPL

parameter of the ADDCICSSIT command.

An SNA network also has a name of up to eight characters, which is called thenetwork name . The network name is sometimes referred to as the network id or thenetid . An LU can be uniquely identified by combining its LU name with the networkname of the network that owns it. The name is then referred to as thenetwork-qualified LU name or the fully-qualified LU name . For example, if an LUthat is named CICSA belongs to a network that is named NETWORK1, itsnetwork-qualified LU name is NETWORK1.CICSA.

Connections at the physical levelYour physical machine is referred to as an SNA node . You must assign to it a

Control Point (CP) name (the name that the network uses to communicate with it).This CP name can have one to eight characters that consist of uppercase letters (Athrough Z) and numbers (0 through 9). It must be unique within the SNA network. Itmust be different from:v All other CP names in the network.v All other Logical Unit (LU) names in the network.

Some large SNA networks use naming conventions that prevent name clashes.Alternatively, you can often use the host name of your HP-UX machine as the CPname. Consult your network administrator for help when choosing names.

Associated with the CP name is the node identifier (also referred to as theexchange identifier or XID ). This eight-digit number, which usually begins with 05F

on HP-UX systems, identifies the Physical Unit (PU) that is associated with thecontrol point.

Each node has a physical unit (PU) . This is a combination of hardware andsoftware that controls the links to other nodes. Several PU types that have differentcapabilities and responsibilities exist, such as:

PU type 5The best known example is an IBM mainframe processor that is runningVirtual Telecommunications Access Method (VTAM). VTAM provides thesupport for the Systems Services Control Point (SSCP) function that isdefined in SNA.

PU type 4

This is a communications controller, such as an Advanced CommunicationsFunction for the Network Control Program (ACF/NCP), which resides in thecenter of a network, routing and controlling the data flow betweenmachines.

PU type 2

This is a small machine, such as an Advanced Peer-to-PeerCommunications (APPC) workstation. It can communicate directly only witha PU type 4 or a PU type 5, and relies on these PUs to route the data tothe correct system.

Chapter 1. Introduction to SNA 3


18/77

PU type 2.1This is a more advanced PU type 2 that can also communicate with otherPU type 2.1 nodes directly. This node can support an independent LU . Anindependent LU can establish a session with another LU without usingVTAM. HP-UX SNAplus2 is a PU type 2.1 node.

Each node has physical links, or connections , to other nodes so that every node is

connected to at least one other node. Data must sometimes travel along severallinks to get from one system to another. These links can be of different types. Forexample, IBM Token Ring, Synchronous Data Link Control (SDLC), and Ethernetare all physical links. These types of links are collectively referred to as data link control (DLC) protocols .

Communicating across SNA connectionsFor an LU to communicate with another LU, at least one session must beestablished between them. The request to activate a session is referred to as aBIND request . It is used to pass details of the capabilities of the initiating LU to thereceiving system, and also to determine a route though the network. The receivingLU then sends a description of its capabilities to the initiating LU in the BIND

response . When the session is established, it can be used for several intersystemrequests and remains active for as long as the two LUs and the network betweenthem are available.

Different session characteristics, such as the route that is taken through thenetwork, can be set up for the sessions that are established between a pair of LUs.Session characteristics are referred to as modegroups or modes . All the sessionsthat are associated with a modegroup have the same characteristics. Modegroupsare identified by a modename of up to eight characters.

PU type 2.1 nodes can have support for Advanced Peer-to-Peer Networking ®

(APPN) . This enables a node to search for an LU in the network , rather thanrequiring a remote LU’s location to be pre-configured locally. Two types of APPN

nodes exist: end nodes and network nodes . An end node can receive a searchrequest for an LU, respond, and indicate whether the LU is local to the node or not.A network node can both issue and respond search requests, and maintain adynamic database that contains the results of the search requests that the nodehas made. Support for APPN can greatly reduce the maintenance work in an SNAnetwork, especially if the network is large or dynamic.

CICS regions can communicate across SNA with any system that supports APPC.HP-UX SNAplus2 supports local SNA, which gives your CICS regions support forsynchronization levels 0 and 1, and provides the fastest SNA connectivity that CICSoffers. It enables CICS applications to communicate with every other member of theCICS family, and enables IBM CICS Universal Clients to use SNA to communicatewith CICS. To use local SNA support, HP-UX SNAplus2 or SNA Client must be

installed and configured on the same machine as is the CICS region.

When defining a CICS region, you must also identify the required SNAsynchronization level. CICS supports all three synchronization levels that aredefined by SNA. HP-UX SNAplus2 supports only synchronization levels 0 and 1:

v Synchronization level 0 (NONE) : SNA provides no synchronization support. Theapplication must code its own.

v Synchronization level 1 (CONFIRM) : SNA provides the ability to send simpleacknowledgment requests.



19/77

v Synchronization level 2 (SYNCPOINT) : SNA provides the ability for two or moresystems to handle as one logical unit of work (LUW), the updates that anapplication makes on these systems.

Chapter 1. Introduction to SNA 5


20/77



21/77

Chapter 2. Collecting information for a HP-UX SNAplus2configuration

This following sections describe the information that you need in order to configureHP-UX SNAplus2 for use with CICS. You will find Systems Network Architecture

(SNA) configuration much easier if you collect this information before you start tocreate the SNA definitions.

The steps are:1. “Collecting information about the local HP-UX machine (node)”2. “Collecting information about remote machines”3. “Collecting information about a local CICS region” on page 94. “Collecting information about remote CICS regions” on page 105. “Collecting information about modegroups” on page 11

Collecting information about the local HP-UX machine (node)

The following list describes the information that you need in order to register theHP-UX machine that is running HP-UX SNAplus2 with the SNA network. You needto know:

v The Control Point (CP) name

v The node identifier (XID) name

v The SNA network name

Table 3 shows the information that is required in order to describe an example localHP-UX machine.

Table 3. Information required to describe an example local HP-UX machine

CP Name Node Identifier Local Network Name

HP000001 05F01234 MYSNANET

If you plan to communicate with remote systems through the VirtualTelecommunications Access Method (VTAM), your CP name, node identifier, andthe LU name of your CICS region must be defined to VTAM. Chapter 6,“Configuring VTAM with details of your CICS region,” on page 35 shows someexample VTAM definitions.

Collecting information about remote machines

This section describes the information that you need in order to connect your local

HP-UX machine to other machines (referred to as SNA nodes) in the SNA network.

It is often helpful to draw a schematic diagram of the network, such as that which isshown in Figure 2 on page 8.



22/77

Note: When you define your connections to HP-UX SNAplus2, you need to includeonly those machines that can be contacted directly . Connections tomachines that are indirectly accessed are identified through definitions thatare set up in the intermediate machines. As a result, you need to consult theowners of those intermediate machines to arrange the appropriateconfigurations.

You must complete the following steps:

v

Identify the machines to which you want to be connected and assign aconnection name to each connection. Choose meaningful names of up to eightcharacters that consist of uppercase letters (A through Z) and numbers (0through 9), to help you identify the machines that are at the remote end of theconnections. The more meaningful the names, the easier will be your networkmanagement.

v Determine the type of network that is to be used to connect the machinestogether. Typical network types are:

– IBM Token Ring LAN

– Ethernet LAN

– SDLC line

v Collect information about each remote node, such as its:– Control Point (CP) name– Node identifier (XID)

v Determine the hardware (MAC) address of each remote machine. Methods fordetermining these addresses differ depending on the type of machine:

– View the hardware address of a remote NT machine under the Transportssection of the Network applet of its NT Diagnostics tool application.

– View the address of a remote AIX machine by running the netstat -vcommand on the AIX machine.

Figure 2. A simplified example heterogeneous network



23/77

– Obtain the address of a remote mainframe by contacting that system’s SNANetwork Administrator. (The address that you need is probably that of anetwork controller that is handling the network traffic on behalf of themainframe.)

– Obtain the address of a remote machine that is connected by way of TCP/IP.To do this, use the ping command at your local HP-UX machine to contactthe remote machine. Then use the command arp -a to list the addresses

about which the address resolution protocol (arp) knows. For example,Figure 3 shows how 10-00-5a-4b-3c-2d, the hardware address of aix5, isobtained.

Table 4 shows an example of such an information-gathering process.

Table 4. Information required to define example links

Connection

NameLink Type

Network

Name

Remote CP

Name

Remote

Node

Identifier

Remote

Hardware

Address

LINKVTAMIBM Token

Ring MYSNANET MYVTAM 04354321 400012345678

LINKAIXIBM Token

RingMYSNANET AIX00005 07101234 10005A4B3C2D

Collecting information about a local CICS region

This section describes the information that is required in order to configure a localCICS region. For your region, you need to know:

v The Logical Unit (LU) name for the region. An LU name can have one to eightcharacters that consist of uppercase letters (A through Z) and numbers (0through 9). All LU names must be unique within your network. Ensure that any

LU name that you choose for your CICS region is different from:– All other CP names in the network– All other LU names in the network

Many networks have naming conventions that help prevent name clashes.Consult your network administrator for advice when choosing LU names.

v Which of the modenames to use as a default when the region does not explicitlyspecify a modename on an intersystem request. You can specify a modenameexplicitly on an intersystem request by using the SNAModeName attribute of theCICS Transaction Definitions (TD), or by using the PROFILE option of the EXECCICS ALLOCATE command. Alternatively, you can specify a modename in the

C:\>ping aix5

Pinging aix5.cicsland.com [1.23.45.67] with 32 bytes of data:

Reply from 1.23.45.67: bytes=32 time


24/77

DefaultSNAModeName attribute of the CICS Communications Definitions (CD)entry. This modename is used if you do not specify a modename explicitly in theTD entry or in the EXEC CICS command. Identification of this parameter isdescribed further in the TXSeries for Multiplatforms Intercommunication Guide .

v Whether synchronization level 2 is supported. CICS local SNA does not supportsynchronization level 2.

Table 5 shows the information that is required in order to to define a CICS regioncalled CICS9000. The default modename for this LU name is CICSISC0.

Table 5. Information required to define a local LU

Network Name Local LU Name Local LU Alias Syncpoint

Support?

CICS CD DefaultSNA

ModeName

MYSNANET CICS9000 CICS9000 No CICSISC0

Collecting information about remote CICS regions

This section describes the information that you need to know about the remote

systems with which your CICS region is going to communicate. These remotesystems are commonly referred to as partner LUs.

For each partner LU you need to know:

v Its LU name. An IBM mainframe-based CICS region uses as its LU name (alsoreferred to as a NETNAME), its APPLID that is defined in the CICS systeminitialization table. The LU name for a CICS for OS/2 ® or CICS on Open Systemsregion is specified in its local SNA product’s local LU definition. The LU name fora CICS/400 ® region is found in the APPL parameter of the ADDCICSSITcommand.

v The name of the SNA network to which it belongs. A SNA network name canhave one to eight characters that consist of uppercase letters (A through Z) andnumbers (0 through 9).

If the partner LU is not on a machine that is defined as an AdvancedPeer-to-Peer Networking (APPN) network node, you need the control point (CP)name of the machine on which the partner LU resides, or of the machine that isconfigured with the information about where the partner LU resides. If you do notspecify the CP name, your local machine cannot bind sessions to the partner LU.When you have defined and activated a link to a particular remote machine,HP-UX SNAplus2 displays the CP name of this machine.

Note: For discussions about configuring conversation-level security, which includesthe receiving of a user ID from the remote system, see “Definingconversation level security” on page 33. Also, see the TXSeries for Multiplatforms Intercommunication Guide .

Table 6 shows examples of data that is collected for remote CICS systems.

Table 6. Information required to define example remote CICS regions

Partner LU Name Partner LU Alias Network Name Partner CP Name

CICSESA CICSESA MYSNANET MYSNANET.MYVTAM

CICSMVS CICSMVS MYSNANET MYSNANET.MYVTAM

CICSAIX CICSAIX MYSNANET MYSNANET.AIX00005



25/77

Collecting information about modegroups

This section describes the information that is required in order to define themodegroups (or modes) that are used on the SNA connections between your CICSsystem and remote SNA systems.

Modegroups define the number of sessions that are allowed on a connection

between two systems. Each session allows only one CICS intersystem request torun at a time, so the number of sessions between the two systems affects thenumber of concurrent intersystem requests that they can process. By controlling thenumber of sessions between the two systems, you control the network traffic that isgenerated by the two systems, and prevent one system from flooding the other withrequests. Identify each modegroup by assigning to it a modename, one to eightcharacters long, that consists of uppercase letters (A through Z) and numbers (0through 9).

You must define at least one modegroup to the HP-UX SNAplus2. SNA connectionscan share modegroup definitions. The session limits that are defined in amodegroup apply independently to each connection that uses that modegroup. Aconnection can use more than one modegroup. For example, suppose you have aconnection that handles fast intersystem requests for interactive users and slowerintersystem requests that send or receive large amounts of data. Define twomodegroups: one for the interactive requests (called modename CICSISC0), andthe other for the slower data transfer requests (called modename CICSISC1).

The modegroup also defines the characteristics of the sessions that belong to theconnection. The most important of these is contention . For each session betweentwo systems, one system is the contention winner , and the other system is thecontention loser . If both systems attempt to use the session at the same time, thecontention winner system is given priority. The contention loser must wait until thecontention winner is finished using the session. When you configure yourmodegroups, ensure that your systems have a suitable balance of

contention-winner and -loser sessions. (Each system must have at least onecontention-winner session defined.)

In addition to the intersystem requests that your applications make, CICS regionssend management requests among themselves. For this reason, define more thanone session between two CICS regions. A single session is not enough to handlethis traffic.

Table 7 shows the information that is needed in order to define two modegroups.Remember that the modegroups that are used on a connection must be definedwith consistent session limits on both systems. If HP-UX SNAplus2 uses VTAM tocommunicate with the remote system, you must include a MODEENT definition forthe modename in its tables. Refer to Chapter 6, “Configuring VTAM with details of

your CICS region,” on page 35 for an example of a MODEENT definition.Table 7. Information required to define example modegroups

Modename Max Sessions Min Winners

CICSISC0 10 5

CICSISC1 4 2

Chapter 2. Collecting information for a HP-UX SNAplus2 configuration 11


26/77

System-defined SNASVCMG and CPSVCMG modegroupsSNA network connections that use parallel sessions have a standard modegroupcalled SNASVCMG . This is a system-defined modegroup that is reserved for use bySNA management programs. Do not attempt to define this modegroup in HP-UXSNAplus2 or use it for your CICS intersystem requests.

APPN systems also use a modegroup called CPSVCMG . This is reserved for APPNmanagement programs. Again, do not attempt to define this modegroup or use it foryour CICS intersystem requests.



27/77

Chapter 3. Choosing a communication configuration

HP-UX SNAplus2 enables communication by CICS local SNA support and the PPCGateway server through SNA. You can configure CICS to use local SNA, or thePPC Gateway server, or both, subject to the following rules:

v

To use CICS local SNA support, you must install HP-UX SNAplus2 on the samemachine as is CICS.

v To use the PPC Gateway server, you must install HP-UX SNAplus2 on the samemachine as is the PPC Gateway server. CICS can be on the same machine as isthe PPC Gateway server, or on a different machine.

v To use both local SNA and the PPC Gateway server, either of the followingconfigurations is possible:

– CICS, HP-UX SNAplus2, and the PPC Gateway server on the same machine

– CICS and HP-UX SNAplus2 on one machine, and HP-UX SNAplus2 and PPCGateway server on another machine

This section presents a sample configuration that uses HP-UX SNAplus2 to

communicate between CICS for HP-UX and IBM mainframe-based CICS. Figure 4on page 14 and Figure 5 on page 15 give an overview of the definitions that arerequired for these cases. In addition, these figures also show how the attributes thatare defined in HP-UX SNAplus2 relate to resource definitions in CICS.

The system administration scenarios that are depicted in Chapter 5, “Systemmanagement for HP-UX SNAplus2,” on page 19 use the sample configuration;Appendix A, “Sample configuration for HP-UX SNAplus2,” on page 41 containsdetailed samples for the PPC Gateway server case.

This section does not cover every aspect of configuring HP-UX SNAplus2. For moreinformation about configuring, controlling, and monitoring HP-UX SNAplus2, refer tothe HP-UX SNAplus2 Administration Guide .

Using the PPC Gateway server

Figure 4 on page 14 is an overview of the definitions that you need in order to usethe PPC Gateway server. It shows CICS for HP-UX definitions, HP-UX SNAplus2definitions for the PPC Gateway server, and CICS/ESA ® definitions. VTAMdefinitions are not shown in this overview.



28/77


29/77

The CICS for HP-UX definitions are on the left of the figure, the HP-UX SNAplus2definitions are on the right, and the CICS/ESA definitions are at the top right.

Note: SNAConnectName is not required in the CICS for HP-UX communicationdefinition with local SNA. However you must match the values ofRemoteLUName and RemoteNetworkName in CICS for HP-UX with thevalue of fqplu_name in HP-UX SNAplus2.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. Region Definition (RD) . . CICS/ESA region: CICSESA .

. LocalNetworkName=MYSNANET . . CONNECTION: OPEN .

. LocalLUName=CICS9000 . . NETNAME=CICS9000 .

. LocalSysId=9000 . . SESSION: OPEN0 .

. . . . . . . . . . . . . . . . . MODENAME=CICSISC0 .

. . . . . . . . . . . . . . . . SESSION: OPEN1 .

. Listener Definition (LD) . . MODENAME=CICSISC1 .

.

SNA: . . . . . . . . . . . . . . . .

. Protocol=SNA . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . HP-UX SNAplus2 .. [define_local_lu] .

. lu_name = CICS9000 .. syncpt_support = NO .. lu_alias = CICS9000 .

. . . . . . . . . . . . . . . . . . . .

. .Communications Definitions (CD) . .. CESA: . . [define_partner_lu] .

. ConnectionType=local_sna . . plu_un_name = CICSESA .

. RemoteLUName=CICSESA . . fqplu_name = MYSNANET.CICSESA .

. RemoteNetworkName=MYSNANET . . parallel_sess_supp = YES .

. RemoteSysSecurity=trusted . . conv_security_ver = YES .

. DefaultSNAModeName=CICSISC0 . . .

. RemoteCodePageTR=american_e . . [define_mode] .

. . . mode_name = CICSISC0 .

. . . min_conwin_src = 5 .

. Transaction Definitions (TD) . . plu_mode_session_limit = 10 .

. REMT: . . max_neg_sess_lim = 10 .. RemoteSysId=CESA . . .

. RemoteName=CEMT . . [define_mode] .

. SNAModeName=CICSISC1 . . mode_name = CICSISC1 .

. SEMT: . . min_conwin_src = 2 .. RemoteSysId=CESA . . plu_mode_session_limit = 4 .

. RemoteName=CEMT . . max_neg_sess_lim = 2 .

. SNAModeName="" . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

Figure 5. Matching HP-UX SNAplus2 names with CICS definitions (local SNA)

Chapter 3. Choosing a communication configuration 15


30/77



31/77

Chapter 4. Installing HP-UX SNAplus2

This section discusses the following topics:

v “Initial installation of HP-UX SNAplus2” discusses code installation for a newimplementation of HP-UX SNAplus2.

v“Kernel configuration for use of HP-UX SNAplus2” discusses kernel configurationthat is required for use of HP-UX SNAplus2.

v “Migration from HP-UX SNAplus” discusses migration from HP-UX SNAplus toHP-UX SNAplus2.

Initial installation of HP-UX SNAplus2

Use the HP-UX administration utility swinstall to install HP-UX SNAplus2. Theswinstall utility guides you through the necessary steps to complete the installationof the HP-UX SNAplus2.

Note: If you intend to migrate from an existing HP-UX SNAplus system to HP-UXSNAplus2, do not remove HP-UX SNAplus. If HP-UX SNAplus is removed,you do not get the migration tools. Do not remove HP-UX SNAplus afterinstalling HP-UX SNAplus2. See HP-UX SNAplus2 Release 7.11 Release Notes for more details. See “Migration from HP-UX SNAplus” for adiscussion about migration.

Kernel configuration for use of HP-UX SNAplus2

To configure the kernel, use the sam administration tool, select Networking andcommunication, then select SNAplus2 Installation.

Check with the HP-UX SNAplus2 Release 7.11 Release Notes for the latestpatches before you configure the kernel of your HP-UX SNAplus2 server as a

server, a client, or a stand-alone implementation. The HP-UX SNAplus2 Release 7.11 Release Notes are in /opt/sna/samples/rel_notes.SNAplus2.

Migration from HP-UX SNAplus

If you intend to migrate from an existing HP-UX SNAplus system to HP-UXSNAplus2, do NOT remove HP-UX SNAplus. If HP-UX SNAplus is removed, you donot get the migration tools. Do not remove HP-UX SNAplus after installing HP-UXSNAplus2. See HP-UX SNAplus2 Release 7.11 Release Notes for more details.See “Migration from HP-UX SNAplus” for a discussion about migration.

The migration tool snapmigrate allows you to migrate your HP-UX SNAplus

configuration files to HP-UX SNAplus2.

For example, if you have a file com.cfg that was used to configure HP-UXSNAplus2, proceed as follows:

1. Copy or move the file into the directory /etc/opt/sna.

2. Make directory /etc/opt/sna your working directory by using the followingcommand:

cd /etc/opt/sna

3. If the files sna_node.cfg and sna_domn.cfg already exist in the directory, renamethem as backup copies.



32/77

4. Enter the following command:

snapmigrate com.cfg new

This command creates various files, including: new. machineName and new.dom.

5. Rename files new. machineName and new.dom as follows:

mv new. machineName sna_node.cfgmv new.dom sna_domn.cfg

In this example, machineName is the name of your machine.

6. If the snapmigrate command produced other files (new.*), and you want to usethese files in your HP-UX SNAplus2 configuration, consult the HP-UX SNAplus2 Migration Guide for information about how to rename these files.

The file /etc/opt/sna/sna_node.cfg contains the APPC local and remote LUdefinitions. Refer to the HP-UX SNAplus2 Migration Guide for full migrationinstructions. It is useful to have a copy of the HP-UX SNAplus configuration filecom.cfg in readable format while migrating.



33/77

Chapter 5. System management for HP-UX SNAplus2

The HP-UX SNAplus2 product is administered by using either of two utilities:snapadmin is a command-line utility; xsnapadmin is the same tool implementedwith a Graphical User Interface (GUI). These tools are fully described in the HP-UX SNAplus2 Administration Guide .

This document focuses on the use of the GUI-based HP-UX SNAplus2administration utility. The command-line HP-UX SNAplus2 administration utility isbriefly discussed in “Defining conversation level security” on page 33 and “Using thecommand-line HP-UX SNAplus2 utility” on page 34.

Administration tasks are discussed in the following sections:

v “Starting the HP-UX SNAplus2 GUI administration utility”

v “Defining a token ring port” on page 21

v “Defining a local LU name for CICS local SNA support” on page 22

v “Defining a local LU name for PPC Gateway support” on page 23

v“Defining a partner LU on a remote node” on page 25

v “Defining a link station” on page 27

v “Defining a modename” on page 29

v “Defining a default modename” on page 31

v “Defining conversation level security” on page 33

v “Activating a token ring and link station” on page 33

v “Defining conversation level security” on page 33

v “Using the command-line HP-UX SNAplus2 utility” on page 34

Starting the HP-UX SNAplus2 GUI administration utility

The HP-UX SNAplus2 GUI administration utility allows you to see the status of theSNA logical units, and to activate ports and link stations.

1. You must start HP-UX SNAplus2 before you use the administration utility. Tostart HP-UX SNAplus2, issue the command snap start. (You can stop HP-UXSNAplus2 with the command snap stop.)

2. When HP-UX SNAplus2 is active, start the administration utility by issuing thefollowing command:

/opt/sna/bin/X11/xsnapadmin

The SNAplus2 node screen is displayed. This screen contains three panes:

v Connectivity and dependent LUs: Use this pane to define a token ring port.

v Independent local LUs: Use this pane to define a local LU name for CICSlocal SNA and PPC Gateway support.

v Remote systems: Use this pane to define a partner LU name.

Figure 6 on page 20 shows the SNAplus2 node screen. The SNAplus2 nodescreen is the main screen for the HP-UX SNAplus2 administration utility. Itreoccurs throughout the scenarios that detail administrative procedures, but it isnot displayed with each occurrence. When this document mentions theSNAplus2 node screen, it is referring to the screen that is displayed in Figure 6on page 20.



34/77

Figure 6. SNAplus2 node screen display



35/77

Defining a token ring port

To define a token ring port, use the following procedure:

1. Highlight the Connectivity and dependent LUs pane on the SNAplus2 nodescreen. Figure 6 on page 20 shows this highlighted pane.

2. Select the Add button.

3. The Add screen is displayed.

Note: The Add screen reoccurs throughout the scenarios that detailadministrative procedures. The screen selections that are available onthe Add screen can vary, based on where the call to the screen isinitiated. When this document mentions the Add screen, it is referring toone of the call-initiated variations of the Add screen such as that which isdisplayed in Figure 7.

4. You can display a choice list by clicking the box that is beside the Port usingbutton on the Add screen. Click the token ring card selection; an example isshown in Figure 7.

5. Press the OK button on the Add screen.

6. The Token ring SAP screen is displayed. Enter the required attributes, and

ensure that the Initially active toggle is on. An example is shown in Figure 8 onpage 22.

Figure 7. Add token ring display

Chapter 5. System management for HP-UX SNAplus2 21


36/77

7. Press the OK button to return to the SNAplus2 node screen.

Defining a local LU name for CICS local SNA support

To define a local LU name for CICS local SNA support, use the following procedure:

1. Highlight the Independent local LUs pane on the SNAplus2 node screen.

2. Select the Add button. The Local LU screen is displayed.

3. Enter the required attributes; an example is shown in Figure 9 on page 23.

Figure 8. Token ring SAP display



37/77

The LU alias must match the LU name. The GUI tool automatically inserts theentry from the LU name field into the LU alias field.

4. Click the OK button to return to the SNAplus2 node screen.

Defining a local LU name for PPC Gateway support

To define a local LU name for PPC Gateway support, use the following procedure:

1. Highlight the Independent local LUs pane on the SNAplus2 node screen.

2. Click the Add button. The Local LU screen is displayed.

3. Enter the required attributes; an example is shown in Figure 10 on page 24.

Figure 9. Local LU screen display



38/77

4. Click the Advanced ... button. The Local LU parameters screen is displayed.Figure 11 shows the Local LU parameters screen.

5. Select the Support Syncpoint toggle to enable syncpoint transaction security.

6. Click the OK button to return to the node display panel.

Figure 10. Local LU for the PPC Gateway

Figure 11. PPC Gateway advanced settings display



39/77

Defining a partner LU on a remote node

To define a partner LU name, use the following procedure:

1. Highlight the Remote systems pane on the SNAplus2 node screen.

2. Click the Add button. The Add screen is displayed.

3. Select Define remote node.

4. Click the OK button. The Remote node screen is displayed.

5. Enter the required attributes; an example is shown in Figure 12.

6. Click the OK button in this screen.

7. An Information panel pops up and shows the following message:

The default LU has automatically been defined for MYSNANET.CICSESA

Click the OK button in this Information panel to return to the SNAplus2 nodescreen. A default LU is automatically defined, as shown in the following figure:

Figure 12. Remote node screen display



40/77

8. Highlight the automatically defined default LU in the Remote Systems pane ofthe SNAplus2 node screen.

Figure 13. Automatically defined remote LU display



41/77


42/77

v In the Contact Information section, fill in the MAC address, and any otherattributes. An example is shown in Figure 15.

6. Click the Advanced ... button on the Token ring link station screen. The Tokenring parameters screen is displayed.

7. Fill in any required attributes on the Token ring parameters screen. An exampleis shown in Figure 16 on page 29.

Figure 15. Token ring link station screen display



43/77

8. Click the OK button in Token ring parameters screen; the display returns to theToken ring link station screen. Click the OK button in Token ring link stationscreen to return to the SNAplus2 node screen.

In the definition of a token ring link station, the default setting for thelimited_resource parameter is YES. To communicate with IBM mainframe-basedCICS, edit the sna_node.cfg file to change the setting to limited_resource=NO.Figure 25 on page 44 shows the define_tr_ls stanza after the limited_resource valuehas been changed to NO.

Defining a modenameTo define a modename, use the following procedure:

1. Select the Services drop-down menu on the SNAplus2 node screen.

2. Select APPC from the choices on the Services drop-down menu. Next, selectModes ... from the drop-down menu associated with APPC. The Modes screenis displayed. An example is shown in Figure 17 on page 30.

Figure 16. Token ring parameters screen display



44/77

3. Click the New button on the Modes screen. The Mode screen is displayed.Enter mode attributes; an example is shown in Figure 9 on page 23.

Figure 17. The Modes screen display



45/77

4. Click the OK button in the Mode screen to return to the Modes screen.

“Defining a default modename” continues with this screen display.

Defining a default modename

To define a default modename, use the following procedure:

1. In the Modes screen, highlight modename CICSIS0 (see Figure 17 on page 30).

2. Click the Make default button.

Figure 18. Mode screen attributes display



46/77

3. Click the Done button. The display returns to the SNAplus2 node screen.

Defining the bind password

To define the bind password, use the following procedure:

1. On the SNAplus2 node screen, select the Services drop-down menu.

2. Select APPC from the Services drop-down menu choices.

3. Select Security from the APPC drop-down menu choices.

4. Select Session level security from the Security drop-down menu choices. TheSessions security- node_name screen is displayed. An example is shown inFigure 19.

5. Click the New button. The Session security screen is displayed.

6. Enter appropriate attributes; an example is shown in Figure 20 on page 33.

Figure 19. Session security- node_name screen display



47/77

7. Click the OK button. The display returns to the Sessions security- hope screen.

8. Click the Done button on the Sessions security- node_name screen.

Defining conversation level security

You can restrict incoming attach requests to particular user ID and password pairs.To do so, you need to use both the GUI-based version and the command-lineversion of the HP-UX SNAplus2 administration utilities.

To restrict the incoming user IDs, use the GUI-based HP-UX SNAplus2administration utility. Select the Services drop-down menu from the SNAplus2 nodescreen. Select APPC from the choice list; select Security, and Conversation levelsecurity, then select on the Add button. This sets an attribute that is associatedwith the user ID to already-verified. User IDs that have this setting can accessremote systems where the RemoteSysSecurity attribute in the CICSCommunications Definitions is set to trusted.

For partner LUs to use the already-verified attribute, you must set CICS theRemoteSysSecurity attribute in the CICS Communications Definition to trusted.Also, issue the following command using the command-line HP-UX SNAplus2administration utility:

snapadmin define_partner_lu,fqplu_name=MYSNANET.CICSESA,plu_alias=CICSESA,description=\"conv sec enabled\",max_mc_ll_send_size=32767,parallel_sess_supp=YES,conv_security_ver=YES

It is not possible to modify the setting conv_security_ver=YES by using theGUI-based HP-UX SNAplus2 administration utility.

Activating a token ring and link station

The button that is on the upper right of the SNAplus2 node screen is labeled node name inactive; for example, hope inactive. Click this button to highlight it. Click theStart button. The port and link station are started. The button now says node name active.

Figure 20. Session security screen attributes display



48/77

Using the command-line HP-UX SNAplus2 utility

The command-line HP-UX SNAplus2 administration utility offers some helpfulcommands. This section shows some of those commands and their output.

Use the following command to list summary details that are associated with thelocal LU resources:

snapadmin query_local_lu,num_entries=0,list_options=SUMMARY+FIRST_IN_LIST

Here is an example of the output that this command produces:

------------------------------------------------------------------------list_options = SUMMARY + FIRST_IN_LIST

description = local_sna local LU namelu_name = CICS9000lu_alias = CICS9000

description = HP control pointlu_name = HP000001lu_alias = HP000001

description = ppc_gateway local LU namelu_name = OPENCICSlu_alias = OPENCICS

------------------------------------------------------------------------

To get a more detailed view of a single resource, use the following command:

snapadmin query_local_lu,num_entries=1,\list_options=DETAIL+LIST_INCLUSIVE,lu_name=CICS9000

Here is an example of the output that this command produces:

------------------------------------------------------------------------list_options = DETAIL + LIST_INCLUSIVE

lu_name = CICS9000description = local_sna local LU namelu_alias = CICS9000nau_address = 0syncpt_support = NOlu_session_limit = 0default_pool = NOpu_name = sys_name = ""timeout = 30back_level = NO

------------------------------------------------------------------------

The following snapadmin command defines resources in great detail:

snapadmin define_partner_lu,fqplu_name=MYSNANET.CICSESA,\plu_alias=CICSESA,conv_security_ver=YES,\parallel_sess_supp=YES

Note: The SNAplus2 node screen that is displayed by the GUI-based utilityprovides valuable details through the Status button on the menu bar.



49/77

Chapter 6. Configuring VTAM with details of your CICS region

The Virtual Telecommunications Access Method (VTAM) is an IBM product that runson a mainframe and controls access to systems such as CICS Transaction Serverfor z/OS, CICS/ESA, CICS/MVS and CICS/VSE. VTAM uses the services of theNetwork Control Program (NCP) product to connect the mainframe to the network.Therefore, the NCP might need updating so that it will pass requests from yourSNA machine to VTAM and the remote system beyond.

VTAM and NCP definitions are coded by use of macros. The sections below showexample definitions. Only a few examples are shown. Because these examplescould not cover the extensive range of network configurations, they are to be usedas guidance only. Please refer to the following manuals for more information andexamples of VTAM and NCP definitions:v VTAM Resource Definition Examples v IBM Network Products Implementation Guide

Defining your machine and CICS regions to VTAM

The VTAM Physical Unit (PU) macro defines the machine on which your SNAproduct is running. The example below is a PU macro for a PC that is runningHP-UX SNAplus2 that is connected to the network with an IBM Token Ring:

************************************************************************HP000001 PU ADDR=C1, STATION ADDRESS (CAN BE ANY VALUE) X

IDBLK=05F, 05F = HP, 05D = OS/2 or NT XIDNUM=01234, PART OF XID. XDISCNT=NO, HANG-UP ON LU LOGOFF XMAXDATA=265, MAX I-FIELD SIZE XMAXOUT=7, RECEIVE PACING WINDOW XMAXPATH=1, NO OF DIAL-OUT PATHS XMODETAB=MTDFLT, MODETAB IF LU DOES NOT SPECIFY ONE XSSCPFM=FSS, LUs NOT SUPPORTING CHAR-CODED MSGS XPACING=0, XVPACING=0, XPUTYPE=2, XISTATUS=ACTIVE

************************************************************************

Values that are coded in the PU definition for your machine must match thedefinitions that you create in your SNA product. For example, VTAM can use eitheran Exchange Identifier (XID) or a control point (CP) name to match to its PUdefinition a request from your machine. The PU definition above has an XIDdefined. This consists of the IDBLK and IDNUM values. Therefore your SNAproduct would be configured with an XID of 05F01234.

The CP name can be coded on a PU definition by use of the CPNAME parameter.This is not required in the example above because the XID is coded. If your SNAproduct allows you to configure both an XID and a CP name, but in the VTAM PUdefinition you specify only an XID, it is suggested that you make the PU name(HP000001 in this example) the same as the CP name. This will make it easier foryou to associate the VTAM PU definition with your machine. However if you do usethe CPNAME parameter in the PU definition, that CP name must be different fromthe PU name.



50/77

When you are setting up a link between your machine and VTAM, you must decidewhich machine is to issue the command that establishes the link. One machinemust call and the other must listen . It is usual for VTAM to listen and your machineto call. However, if you want to set up VTAM so that it calls your machine, VTAMneeds to know the address of your machine. This is defined in a PATH definition.The PATH definition is coded just after the PU definition.

***********************************************************************

*HP01 PATH GRPNM=HPUX, ECLTYPE=LOGICAL group in NCP X

DIALNO=01044000012345678, XGID=1, XPID=1, XUSE=YES

************************************************************************

Under the PU and, if defined, the PATH macro definitions, are the logical unit (LU)definitions. The LUs are in the machines that are defined in the PU definition, andare configured in the SNA product in that machine.

************************************************************************

CICSHPUX LU LOCADDR=0,ISTATUS=ACTIVE,MODETAB=MTCICS

************************************************************************

The LOCADDR=0 option on the LU definition indicates that the region’s LU isindependent. This enables it to communicate with other independent LUs withoutusing VTAM. The MODETAB parameter specified the name of the VTAM modetable that defined all the modegroups (modenames) that the CICS region uses.Examples of mode table entries are shown in “Defining modegroups to VTAM.”

Defining modegroups to VTAM

The example macro below shows part of a VTAM mode table MTCICS. This definesseveral modegroups that include the entry for modename CICSISC0. The modetable that a CICS region uses must have a definition for all its modegroups(modenames) that it uses, and a definition for the SNASVCMG modegroup. Thismodegroup is used by your SNA product for network management requests.

MTCICS MODETAB************************************************************************ MODE TABLE FOR CICS ************************************************************************

: : : : :** Modename CICSISC0 - Parallel_Sessions=yes*CICSISC0 MODEENT LOGMODE=CICSISC0, X

TYPE=0, ONLY TYPE RECOGNISED XFMPROF=X’13’, SNA XTSPROF=X’07’, SNA XPRIPROT=X’B0’, PRIMARY PROTOCOL XSECPROT=X’B0’, SECONDARY PROTOCOL XCOMPROT=X’79A5’, COMMON PROTOCOL XSSNDPAC=X’00’, XSRCVPAC=X’00’, XRUSIZES=X’8989’, RUSIZES IN-4096 OUT-4096 XPSNDPAC=X’00’, XPSERVIC=X’060200000000000000122F00’

** Modename SNASVCMG - required for parallel sessions



51/77

*SNASVCMG MODEENT LOGMODE=SNASVCMG

: : : : :MODEEND

************************************************************************ END OF MODE TABLE FOR CICS ************************************************************************

Chapter 6. Configuring VTAM with details of your CICS region 37


52/77



53/77

Chapter 7. Problem determination for HP-UX SNAplus2

A complete guide to HP-UX SNAplus2 problem determination is given in HP-UX SNAplus2 Diagnostic Guide . This book describes the different types of trace thatare available, the commands that control the messages and trace, and commonconfiguration errors.

HP-UX SNAplus2 common configuration problems

This section lists symptoms of communication problems that are a result ofconfiguration errors. The descriptions suggest possible solutions and point you tofurther information as required.

All SNA communications failSNA communications can fail for several reasons. To discover why, do the followingtasks in the sequence that is given:

1. Verify that the SNA process is started before the PPC Gateway server isstarted. For example, the command /bin/ps -ef | grep sna shows that thesnaperrlog, snapcfgdae, and snapdaemon processes were running.

2. If you are using a gateway, ensure that it is running, then start CICS.

3. When CICS is running, check whether the gateway has been successfullyconfigured.

4. If the gateway has been successfully configured, enter the commandxsnapadmin on the machine that is running HP-UX SNAplus2. This shouldshow that the node, link, and connections that are defined for your region areactive.

5. If the node and link are not active, check whether the network is available. Forexample, if VTAM is being used, check whether the correct VTAM netlists havebeen activated.

6. If the network is active, it is likely that the link definition (and any definitions towhich it points) has values in it that are inconsistent with the values that aredefined elsewhere in the network. Check whether the values in these definitionsare accurate.

7. If the node and link are active, but the connection is not, it is likely that eitherthe remote system is not available, or the HP-UX SNAplus2 connectiondefinition contains errors.

8. If the remote system is available, compare the attributes that are in the HP-UXSNAplus2 configuration with those that are in the remote system. For example:

a. Ensure that if a BIND password has been set up for either the HP-UXSNAplus2 connection definition or in the remote system, the same BINDpassword has also been set up at the other end. (See the TXSeries for

Multiplatforms Intercommunication Guide .)b. Ensure that the network names and LU names of each system are defined

correctly in the other system’s definitions.

c. Ensure that both systems are defined to use parallel sessions, or that bothsystems are defined to use a single session.

d. Ensure that the modes that are listed in the connection’s mode-list definemode names that exactly match those that are configured in the remotesystem.

e. If the node, link, and connection are active, HP-UX SNAplus2 and theremote system have successfully contacted one another, and the problem is



54/77

due to an inconsistency between your CICS definitions, the PPC Gatewayserver, and the HP-UX SNAplus2 configuration.

HP-UX SNAplus2 problem determination procedures

To view the status of a connection, enter the xsnapadmin command. See Figure 17on page 30, which shows the status of dependent LUs, independent local LUs, and

remote systems.

Getting help from the Hewlett-Packard Response Center

If the list of symptoms and their descriptions did not help to solve your intersystemconfiguration problem, and if your symptom is not listed this book, call theHewlett-Packard Response Center with the following information:

1. An export file of your HP-UX SNAplus2 configuration.

2. The file /var/opt/cics/snalog.1 if it exists.

3. Any error messages that the gateway produced. These messages are in thefollowing file:

/var/cics_servers/GSD/cics/ppc/gateway/name/msg4. The console.msg, CSMT.out, and environment file from your region.

5. The Region Definitions (RD), Communications Definitions (CD), GatewayDefinitions (GD), and Transaction Definitions (TD) from your region database.



55/77

Appendix A. Sample configuration for HP-UX SNAplus2

The following figures provide examples of configuration files that let you use HP-UXSNAplus2 with the PPC Gateway server and with local SNA to communicate withCICS/ESA. They might be helpful if you are trying to debug problems.

The sna_node.cfg file

The following stanzas are defined:v define_node_config_file in Figure 21v define_node in Figure 22 on page 42v define_tr_dlc in Figure 23 on page 42v define_tr_port in Figure 24 on page 43v define_tr_ls in Figure 25 on page 44v define_local_lu in Figure 26 on page 45v define_partner_lu in Figure 27 on page 45v define_mode_lu in Figure 28 on page 46v define_directory_entry in Figure 29 on page 47v

define_lu_lu_password in Figure 30 on page 47v define_defaults in Figure 31 on page 47v define_rcf_access in Figure 32 on page 47v set_log_file in Figure 33 on page 47

In this document, the stanzas are displayed in separate figures. In the sna_node.cfgfile, each stanza is separated from the next by a blank line.

[define_node_config_file]major_version = 5minor_version = 1update_release = 1revision_level = 44

Figure 21. define_node_config_file



56/77

[define_node]node_name = HP000001description = Local Node for END_NODE HP001node_type = LEN_NODEfqcp_name = MYSNANET.HP000001cp_alias = HP000001mode_to_cos_map_supp = NOmds_supported = YES

node_id = max_locates = 256dir_cache_size = 256max_dir_entries = 0locate_timeout = 0reg_with_nn = YESreg_with_cds = YESmds_send_alert_q_size = 100cos_cache_size = 16tree_cache_size = 40tree_cache_use_limit = 40max_tdm_nodes = 0max_tdm_tgs = 0max_isr_sessions = 1024isr_sessions_upper_threshold = 896isr_sessions_lower_threshold = 768isr_max_ru_size = 4096isr_rcv_pac_window = 8store_endpt_rscvs = NOstore_isr_rscvs = NOstore_dlur_rscvs = NOdlur_support = NOpu_conc_support = NOnn_rar = 0ptf_flags = NONE

Figure 22. define_node

[define_tr_dlc]dlc_name = TOKEN0

description = ""neg_ls_supp = YESinitially_active = NOadapter_number = 0

Figure 23. define_tr_dlc



57/77

[define_tr_port]port_name = TRPORTdescription = ""dlc_name = TOKEN0port_type = PORT_SATFport_number = 0max_rcv_btu_size = 4105tot_link_act_lim = 64

inb_link_act_lim = 0out_link_act_lim = 0ls_role = LS_NEGact_xid_exchange_limit = 9nonact_xid_exchange_limit = 5ls_xmit_rcv_cap = LS_TWSmax_ifrm_rcvd = 7target_pacing_count = 7max_send_btu_size = 4105mac_address = lsap_address = 0x04implicit_cp_cp_sess_support = NOimplicit_limited_resource = NOimplicit_deact_timer = 0effect_cap = 3993600connect_cost = 0byte_cost = 0security = SEC_NONSECUREprop_delay = PROP_DELAY_LANuser_def_parm_1 = 0user_def_parm_2 = 0user_def_parm_3 = 0initially_active = YEStest_timeout = 5test_retry_limit = 2xid_timeout = 5xid_retry_limit = 2t1_timeout = 5t1_retry_limit = 5

Figure 24. define_tr_port

Appendix A. Sample configuration for HP-UX SNAplus2 43


58/77

[define_tr_ls]ls_name = VTAMLNKdescription = Host link stationport_name = TRPORTadj_cp_name = MYSNANET.MYVTAMadj_cp_type = BACK_LEVEL_LEN_NODEmac_address = lsap_address = 0x04

auto_act_supp = YEStg_number = 1limited_resource = NOsolicit_sscp_sessions = NOpu_name = disable_remote_act = NOdefault_nn_server = NOdspu_services = NONEdspu_name = dlus_name = bkup_dlus_name = link_deact_timer = 0use_default_tg_chars = YESls_attributes = SNAadj_node_id = local_node_id = cp_cp_sess_support = NOeffect_cap = 3993600connect_cost = 0byte_cost = 0security = SEC_NONSECUREprop_delay = PROP_DELAY_LANuser_def_parm_1 = 0user_def_parm_2 = 0user_def_parm_3 = 0target_pacing_count = 7max_send_btu_size = 4105ls_role = USE_PORT_DEFAULTSinitially_active = NOreact_timer = 30react_timer_retry = 65535

test_timeout = 5test_retry_limit = 2xid_timeout = 5xid_retry_limit = 2t1_timeout = 5t1_retry_limit = 5

Figure 25. define_tr_ls



59/77

[define_local_lu]lu_name = CICS9000description = Local_sna local LU namelu_alias = CICS9000nau_address = 0syncpt_support = NOlu_session_limit = 0default_pool = NO

pu_name = sys_name = ""timeout = 30back_level = NO

[define_local_lu]lu_name = OPENCICSdescription = ppc_gateway local lu definitionlu_alias = OPENCICSnau_address = 0syncpt_support = YESlu_session_limit = 0default_pool = NOpu_name = sys_name = ""timeout = 30back_level = NO

Figure 26. define_local_lu

[define_partner_lu]description = conv sec enabledfqplu_name = MYSNANET.CICSESAplu_alias = CICSESAplu_un_name = max_mc_ll_send_size = 32767conv_security_ver = YESparallel_sess_supp = YES

Figure 27. define_partner_lu



60/77

[define_mode]mode_name = ""description = (SNA defined mode)max_ru_size_upp = 1024receive_pacing_win = 3default_ru_size = YESmax_neg_sess_lim = 8plu_mode_session_limit = 8

min_conwin_src = 4cos_name = #CONNECTcryptography = NONEauto_act = 4

[define_mode]mode_name = CICSISC0description = Modename for CICSmax_ru_size_upp = 1024receive_pacing_win = 4default_ru_size = YESmax_neg_sess_lim = 10plu_mode_session_limit = 10min_conwin_src = 5cos_name = #CONNECTcryptography = NONE

auto_act = 5[define_mode]mode_name = CICSISC1description = modename for CICSmax_ru_size_upp = 1024receive_pacing_win = 4default_ru_size = YESmax_neg_sess_lim = 4plu_mode_session_limit = 4min_conwin_src = 2cos_name = #CONNECTcryptography = NONEauto_act = 2

[define_mode]mode_name = SNASVCMG

description = (SNA defined mode)max_ru_size_upp = 1024receive_pacing_win = 7default_ru_size = NOmax_neg_sess_lim = 2plu_mode_session_limit = 2min_conwin_src = 1cos_name = SNASVCMGcryptography = NONEauto_act = 1

Figure 28. define_mode



61/77

The sna_domn.cfg file

The following stanzas are defined:v define_domain_config_file in Figure 34 on page 48v set_global_log_type in Figure 35 on page 48v set_central_logging in Figure 36 on page 48

In this book, the stanzas are displayed in separate figures. In the sna_domn.cfg file,each stanza is separated from the next by a blank line.

[define_directory_entry]resource_name = MYSNANET.MYVTAMresource_type = ENCP_RESOURCEdescription = Remote node definitionparent_name = parent_type = ENCP_RESOURCE

[define_directory_entry]

resource_name = MYSNANET.CICSESAresource_type = LU_RESOURCEdescription = (Auto defined - default LU)parent_name = MYSNANET.MYVTAMparent_type = ENCP_RESOURCE

Figure 29. define_directory_entry

[define_lu_lu_password]lu_name = OPENCICSlu_alias = OPENCICSfqplu_name = MYSNANET.CICSESAdescription = ""password =

Figure 30. define_lu_lu_password

[define_defaults]description = ""mode_name = CICSISC0

Figure 31. define_defaults

[define_rcf_access]ucf_username = ""spcf_permissions = NONE

Figure 32. define_rcf_access

[set_log_file]

log_file_type = AUDITaction = NO_FILE_ACTIONfile_name = /var/opt/sna/sna.audbackup_file_name = ""file_size = 0

[set_log_file]log_file_type = ERRORaction = NO_FILE_ACTIONfile_name = /var/opt/sna/sna.errbackup_file_name = ""file_size = 0

Figure 33. set_log_file



62/77


63/77

Appendix B. Sample configuration of CICS for HP-UX

The following definitions are provided to configure CICS to use the PPC Gatewayserver.

v Region definition in Figure 38

vGateway definition in Figure 39

v Communications definition in Figure 40

The value of 60 for AllocateTimeout is recommended.

ResourceDescription = "Region Definition"LocalNetworkName = "MYSNANET"LocalLUName = ""

Figure 38. Sample region definition (RD)

GWY:GroupName=""ActivateOnStartup=yesResourceDescription="Gateway Definition"AmendCounter=0

Permanent=noGatewayCDSName="HPgwy"GatewayLUName="OPENCICS"

Figure 39. Sample gateway definition (GD)

CESA:GroupName = ""ActivateOnStartup = yesResourceDescription = "Communications Definition"AmendCounter = 0Permanent = noConnectionType = ppc_gatewayRemoteLUName = "CICSESA"RemoteNetworkName = "MYSNANET"

SNAConnectName = "CICSESA"DefaultSNAModeName = "CICSISC0"GatewayName = "GWY"ListenerName = ""RemoteTCPAddress = ""RemoteTCPPort = 1435AllocateTimeout = 60RemoteCodePageTR = "american_e"InService = yesOutboundUserIds = sentRemoteSysSecurity = trustedLinkUserId = ""TSLKeyMask = noneRSLKeyMask = noneRemoteSysEncrypt = none

Figure 40. Sample communications definition (CD)



64/77



65/77

Appendix C. Sample definitions for CICS/ESA

The following is an example of definitions for CICS/ESA:

In the preceding figure, the BINDPassword field is hidden, but its actual contentsmatch the value that is in the password field of the define_lu_lu_password stanza in /etc/opts/sna/sna_node.cfg.

OBJECT CHARACTERISTICS CICS RELEASE = 0330CEDA View

Connection : OPENGroup : OPENDEscription : CONNECTION TO HP-UXCONNECTION IDENTIFIERSNetname : OPENCICSINDsys :REMOTE ATTRIBUTESREMOTESystem :REMOTEName :CONNECTION PROPERTIESACcessmethod : Vtam Vtam | IRc | INdirect | XmProtocol : Appc Appc | Lu61SInglesess : No No | YesDAtastream : User User | 3270 | SCs | STrfield | LmsRECordformat : U U | Vb

OPERATIONAL PROPERTIESAUtoconnect : Yes No | Yes | AllINService : Yes Yes | NoSECURITYSEcurityname :ATtachsec : Identify Local | Identify | Verify | Persistent

| MixidpeBINDPassword : PASSWORD SPECIFIEDBINDSecurity : Yes No | Yes

Figure 41. CEDA output for connection definitions (CICS/ESA)



66/77

OBJECT CHARACTERISTICS CICS RELEASE = 0330CEDA ViewSessions : OPEN0Group : OPENDEscription : Modegroup CICSISC0 for connection to HP-UXSESSION IDENTIFIERSConnection : O

txseries for multiplatforms using hp-ux snaplus2 with cics version 6.2

Documents