txseries for multiplatforms using snap-ix for solaris with cics version 6.2

8/9/2019 TXSeries for Multiplatforms Using SNAP-IX for Solaris With CICS Version 6.2

1/83

TXSeries for Multiplatforms

Using SNAP-IX for Solaris with CICS

Version 6.2

SC34-6751-01


2/83


3/83

TXSeries for Multiplatforms

Using SNAP-IX for Solaris with CICS

Version 6.2

SC34-6751-01


4/83

Note

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

Second Edition (January 2008)

This edition replaces SC34-6751-00.

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

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


5/83

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 SNAP-IX for Solaris . . . . . . . . . . . . 1

Chapter 2. Introduction to SNA. . . . . . . . . . . . . . . . . . . 3A sample network . . . . . . . . . . . . . . . . . . . . . . . . 3SNA configuration . . . . . . . . . . . . . . . . . . . . . . . . 4Connection at the logical level . . . . . . . . . . . . . . . . . . . 4Connection at the physical level . . . . . . . . . . . . . . . . . . 5

Communicating across SNA connections . . . . . . . . . . . . . . . 6

Chapter 3. Collecting information for a SNAP-IX configuration . . . . . . 7Collecting information about the local Solaris machine (node) . . . . . . . . 7Collecting information about remote machines . . . . . . . . . . . . . . 8Collecting information about a local CICS region . . . . . . . . . . . . 10Collecting information about remote CICS regions . . . . . . . . . . . . 10Collecting information about modegroups . . . . . . . . . . . . . . . 11System-defined SNASVCMG and CPSVCMG modegroups . . . . . . . 12

Chapter 4. Configuring SNAP-IX . . . . . . . . . . . . . . . . . . 13Configuring a node . . . . . . . . . . . . . . . . . . . . . . . 13

Configuring links . . . . . . . . . . . . . . . . . . . . . . . . 16Configuring a port . . . . . . . . . . . . . . . . . . . . . . . 17Configuring a link station . . . . . . . . . . . . . . . . . . . . 19

Configuring a local LU for CICS local SNA support. . . . . . . . . . . . 22Configuring a partner LU on a remote node . . . . . . . . . . . . . . 24Configuring modegroups . . . . . . . . . . . . . . . . . . . . . 27Configuring conversation level security . . . . . . . . . . . . . . . . 29

Chapter 5. Matching SNAP-IX parameters with CICS parameters . . . . . 31Sample configuration for SNAP-IX . . . . . . . . . . . . . . . . . . 34The sna_node.cfg file . . . . . . . . . . . . . . . . . . . . . 34The sna_domn.cfg file . . . . . . . . . . . . . . . . . . . . . 40

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

Chapter 7. Operating SNAP-IX . . . . . . . . . . . . . . . . . . 47Introduction to SNAP-IX operation . . . . . . . . . . . . . . . . . . 47Starting the node and connections. . . . . . . . . . . . . . . . . . 49Starting the node and connections that activate automatically at startup . . . 49Starting connections that do not activate at startup. . . . . . . . . . . 50

Stopping the node and connections . . . . . . . . . . . . . . . . . 51Stopping the node and connections simultaneously . . . . . . . . . . 51

© Copyright IBM Corp. 1999, 2008 iii


6/83

Stopping connections without stopping the node . . . . . . . . . . . 51Starting, viewing, and stopping sessions . . . . . . . . . . . . . . . 52Starting sessions . . . . . . . . . . . . . . . . . . . . . . . 52Viewing sessions . . . . . . . . . . . . . . . . . . . . . . . 52Stopping sessions. . . . . . . . . . . . . . . . . . . . . . . 53

Chapter 8. Problem determination for SNAP-IX . . . . . . . . . . . . 55

Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Viewing trace data . . . . . . . . . . . . . . . . . . . . . . 57

Appendix. Bibliography . . . . . . . . . . . . . . . . . . . . . 59SNA books . . . . . . . . . . . . . . . . . . . . . . . . . . 59SNAP-IX books. . . . . . . . . . . . . . . . . . . . . . . . . 59CICS books . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Trademarks and service marks . . . . . . . . . . . . . . . . . . . 62

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

iv TXSeries for Multiplatforms: Using SNAP-IX for Solaris with CICS


7/83

Figures

1. SNAP-IX node main screen . . . . . . . . . . . . . . . . . . . . . . . . . . . 12. An example heterogeneous network . . . . . . . . . . . . . . . . . . . . . . . . 33. A simplified example heterogeneous network . . . . . . . . . . . . . . . . . . . . . 84. Obtaining the address of a remote machine by using the ping and arp -a commands . . . . . . 95. SNAP-IX node main screen with unconfigured node . . . . . . . . . . . . . . . . . . 146. Node parameters screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157. SNAP-IX node main screen with configured node . . . . . . . . . . . . . . . . . . . 168. Add to screen with indicated port . . . . . . . . . . . . . . . . . . . . . . . . . 179. Token ring SAP screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1810. SNAP-IX node main screen with added Token Ring port . . . . . . . . . . . . . . . . 1911. Token ring link station screen for LINKAIX . . . . . . . . . . . . . . . . . . . . . 2012. SNAP-IX node main screen with added link stations . . . . . . . . . . . . . . . . . . 2113. Local LU screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2214. Local LU Advanced screen . . . . . . . . . . . . . . . . . . . . . . . . . . . 2315. SNAP-IX node main screen with added local LU . . . . . . . . . . . . . . . . . . . 2416. Partner LU screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

17. SNAP-IX node main screen with added partner LUs . . . . . . . . . . . . . . . . . . 2718. Mode screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2819. Modes screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2920. define_node_config_file stanza. . . . . . . . . . . . . . . . . . . . . . . . . . 3421. define_node stanza . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3522. define_tr_dlc stanza. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3523. define_tr_port stanza . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3624. define_tr_ls stanzas (only selected fields are shown for each) . . . . . . . . . . . . . . 3725. define_local_lu stanza . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3826. define_partner_lu stanzas . . . . . . . . . . . . . . . . . . . . . . . . . . . 3827. define_mode stanzas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3928. define_directory_entry stanzas . . . . . . . . . . . . . . . . . . . . . . . . . . 4029. define_defaults stanza . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

30. define_domain_config_file stanza . . . . . . . . . . . . . . . . . . . . . . . . . 4131. VTAM physical unit (PU) macro definition . . . . . . . . . . . . . . . . . . . . . . 4332. VTAM PATH macro definition . . . . . . . . . . . . . . . . . . . . . . . . . . 4433. VTAM logical unit (LU) definition . . . . . . . . . . . . . . . . . . . . . . . . . 4434. VTAM mode table macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4535. Typical system configuration before the node, connections, and sessions are activated . . . . . 4836. Starting the node and connections . . . . . . . . . . . . . . . . . . . . . . . . 5037. Example sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5338. Logging screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5539. Tracing screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

© Copyright IBM Corp. 1999, 2008 v


8/83

vi TXSeries for Multiplatforms: Using SNAP-IX for Solaris with CICS


9/83

Tables

1. Getting started road map . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix2. Conventions that are used in this book . . . . . . . . . . . . . . . . . . . . . . . x3. Information required to define an example node . . . . . . . . . . . . . . . . . . . . 74. Information required to define example links . . . . . . . . . . . . . . . . . . . . . 95. Information required to define an example local system . . . . . . . . . . . . . . . . 106. Information required to define example remote systems . . . . . . . . . . . . . . . . 117. Information required to define example modegroups . . . . . . . . . . . . . . . . . . 118. Information required to configure an example local node . . . . . . . . . . . . . . . . 139. Information required to configure example links. . . . . . . . . . . . . . . . . . . . 1610. Information required to configure an example local system . . . . . . . . . . . . . . . 2211. Information required to configure example remote systems . . . . . . . . . . . . . . . 2512. Information required to configure example modegroups. . . . . . . . . . . . . . . . . 2713. Matching the Local LU parameter values of SNAP-IX with selected parameter values of local

CICS region CICSSOL and partner CICS region CICSESA . . . . . . . . . . . . . . . 3114. Matching the Remote LU parameter values of SNAP-IX with selected parameter values of local

CICS region CICSSOL and partner CICS region CICSESA . . . . . . . . . . . . . . . 32

15. Matching the Mode parameter values of SNAP-IX with selected parameter values of local CICSregion CICSSOL and partner CICS region CICSESA . . . . . . . . . . . . . . . . . 3216. Matching the Local LU parameter values of SNAP-IX with selected parameter values of local

CICS region CICSSOL and partner CICS region CICSAIX. . . . . . . . . . . . . . . . 3317. Matching the Remote LU parameter values of SNAP-IX with selected parameter values of local

CICS region CICSSOL and partner CICS region CICSAIX. . . . . . . . . . . . . . . . 3318. Matching the Mode parameter values of SNAP-IX with selected parameter values of local CICS

region CICSSOL and partner CICS region CICSAIX . . . . . . . . . . . . . . . . . . 34

© Copyright IBM Corp. 1999, 2008 vii


10/83

viii TXSeries for Multiplatforms: Using SNAP-IX for Solaris with CICS


11/83

About this book

The Customer Information Control System (CICS ® ) requires a Systems NetworkArchitecture (SNA) product to connect to an SNA network. This document describeshow to set up and use the SNAP-IX for Solaris product (which is referred to asSNAP-IX throughout this document) with CICS for Solaris.

Topics include how to configure SNAP-IX, coordinate the configuration of SNAP-IXwith the configuration of CICS and its partner systems, operate SNAP-IX, andinvestigate communications errors. Basic information about SNAP-IX and a reviewof basic SNA terminology are also included.

Who should read this book

This book is designed for system administrators who configure, operate, andmanage SNA networks. The user should be familiar with the CICS and SNAP-IXproducts, and have an understanding of SNA concepts. The TXSeries for Multiplatforms Intercommunication Guide , the primary source of information on the

communications features of CICS, gives examples of configurations and advice onsystems design.

Document organization

Table 1. Getting started road map

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

Review basic information about SNAP-IX Chapter 1, “Introduction to SNAP-IX forSolaris,” on page 1

Review common SNA terminology Chapter 2, “Introduction to SNA,” on page 3

Collect information for a new SNAconfiguration

Chapter 3, “Collecting information for aSNAP-IX configuration,” on page 7

Configure SNAP-IX Chapter 4, “Configuring SNAP-IX,” on page13

Review example configuration profiles Chapter 5, “Matching SNAP-IX parameterswith CICS parameters,” on page 31

Communicate with EBCDIC mainframes Chapter 6, “Configuring VTAM with details ofyour CICS region,” on page 43

Start and stop nodes, connections, andsessions

Chapter 7, “Operating SNAP-IX,” on page 47

Solve communications problems Chapter 8, “Problem determination forSNAP-IX,” on page 55

© Copyright IBM Corp. 1999, 2008 ix


12/83


13/83

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, CICS forSolaris, and CICS for Windows products. Other CICS products in theCICS Family are distinguished by their operating system (forexample, 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/83

xii TXSeries for Multiplatforms: Using SNAP-IX for Solaris with CICS


15/83

Chapter 1. Introduction to SNAP-IX for Solaris

SNAP-IX for Solaris, which is referred to as SNAP-IX throughout this document, is acomprehensive networking product that enables communications among manytypes of devices across several network protocols. CICS uses the AdvancedProgram-to-Program Communications (APPC) part of this product to connect to aSystems Network Architecture (SNA) network. Connections can exist with or withoutAdvanced Peer-to-Peer Networking ® (APPN) support. The product must be installedon the same Solaris machine as is your CICS region.

The SNAP-IX product is administered by using either of two utilities:

v The command-line utility snaadmin

v The X Window Graphical User Interface (GUI) utility xsnaadmin

This document focuses on the use of the xsnaadmin utility. A typical system that isconfigured by using this utility is shown in Figure 1.

Figure 1. SNAP-IX node main screen

© Copyright IBM Corp. 1999, 2008 1


16/83

From this node main screen, you can add, delete, modify, and manage all theresources and components for the SNAP-IX node. The menu bar at the top of theSNAP-IX node main screen contains five menus:

v Selection: Lets you control, modify, or delete an item that is currently selected inthe node main screen. You can start or stop the node, or zoom on it to display itsproperties. You can also add a new item in the currently selected pane.

v

Services: Provides the functions that are necessary for configuring the node forcommon tasks. You can add or modify resources or get help for configuration ormanagement tasks.

v Diagnostics: Controls logging and tracing to help diagnose SNA networkproblems.

v Windows: Controls the number of windows that display SNAP-IX information.

v Help: Provides information about using SNAP-IX.

The toolbar that is below the menus contains buttons that duplicate the mostpopular options that the menus provide. When you point the mouse over a button, alabel displays its function. A one-line description of the function is also displayed inthe status bar that is at the bottom of the main window. The node button that is in

the upper right corner indicates the node state.

The SNAP-IX node main screen is divided into three panes:

v Connectivity and dependent LUs: Lists connectivity resources for the node,including ports and link stations on each port.

v Independent local LUs: Lists independent Logical Units (LUs) for the node. Foreach LU, it shows the sessions that are using the LU.

v Remote systems: Lists information about remote nodes and partner LUs. It alsoshows session information for each remote node or partner LU.

Select a pane by clicking anywhere within it, or select specific resources within apane by clicking the line for the resource. The layout of the resources in the screenshows the relationships among them.

After you have installed SNAP-IX, you must configure the product. If you arefamiliar with SNA terminology, go to Chapter 3, “Collecting information for aSNAP-IX configuration,” on page 7. Otherwise, review Chapter 2, “Introduction toSNA,” on page 3, which explains the common SNA concepts that you encounterduring product configuration.

2 TXSeries for Multiplatforms: Using SNAP-IX for Solaris with CICS


17/83

Chapter 2. Introduction to SNA

This section introduces the concepts and terminology that are related to SystemsNetwork Architecture (SNA). You must be familiar with these when you are usingCICS in an SNA environment.

SNA defines a set of rules that systems use to communicate. These rules definethe layout of the data that flows between the systems and the action that thesystems take when they receive the data. SNA does not specify how a systemimplements the rules. A fundamental objective of SNA is to allow systems that havevery different internal hardware and software designs to communicate. The onlyrequirement is that the externals meet the rules of the architecture.

A sample network

Figure 2 shows a heterogeneous network that has CICS for Solaris systemintercommunicating with several different types of CICS regions.

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 usedfor these parameters can differ.

Figure 2. An example heterogeneous network



18/83

SNA configuration

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 composition. SNA configuration is performed at two levels:

v The logical level , which incorporates the characteristics of the systems that are tocommunicate.

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

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

Connection at the logical levelLogical Unit (LU) is an SNA term that is used to describe a logical collection ofservices that can be accessed from a network. SNA defines many different types ofLUs. A CICS region can be an LU, and devices like terminals and printers can alsobe LUs. The type of LU that is used for CICS intersystem communications is LU type 6.2 .

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 describes remote systems are called partner LUs . The local LU name for aCICS on Open Systems or CICS for Windows NT system is configured in theLocalLUName parameter of the Region Definitions (RD) for the region. An IBMmainframe-based CICS system uses as its LU name (also referred to as aNETNAME ), the APPLID that is defined in the CICS system initialization table. TheLU name for a CICS OS/2 system is specified in the Communications Manager/2

Local LU definition, and the LU name for a CICS/400 system is defined in the APPLparameter of the ADDCICSSIT command.

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

For 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 a

BIND 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 . After the session is established, it can be used for several intersystemrequests. It remains active for as long as the two LUs and the network betweenthem are available.

When you configure your network, you can set up individual characteristics for thedifferent sessions that are established between a pair of LUs, such as the route that



19/83

is taken through the network. The set of characteristics for a session is referred toas a modegroup or mode . A modegroup is identified by a modename of up to eightcharacters.

All the sessions that are associated with a modegroup have the samecharacteristics. The most important of these is contention . For each sessionbetween two systems, one system is the contention winner , and the other system is

the contention loser . If both systems attempt to use the session at the same time,the contention winner system is given priority. The contention loser must wait untilthe contention winner is finished using the session. When you configure yourmodegroups, ensure that your systems have a suitable balance ofcontention-winner and -loser sessions. (Each system must have at least onecontention-winner session defined.)

Modegroups also define the number of sessions that are allowed on a connectionbetween two systems. Each session allows only one CICS intersystem request torun at a time. Therefore, the number of sessions between the two systems affectsthe number of concurrent intersystem requests that they can process. By controllingthe number of sessions between the two systems, you control the network trafficthat is generated by the two systems and prevent one system from flooding the

other with requests.

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.

When defining a CICS region, you must also identify the required SNAsynchronization level. CICS used with SNAP-IX supports synchronization levels 0and 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.

Connection at the physical levelEach actual machine in a network is referred to as an SNA node . You must assignto each a unique Control Point (CP) name , which is the name that the network usesto communicate with it. This CP name can have one through eight characters thatconsist of uppercase letters (A through Z) and numbers (0 through 9). It must beunique within the SNA network. It must be different from all other CP and LU namesin the network.

Some large SNA networks use naming conventions that prevent name clashes.

Alternatively, you can often use the host name of your Solaris machine as the CPname. Consult your network administrator for help when choosing names.

Associated with the CP name is the node identifier , which is also referred to as theexchange identifier or XID . This eight-digit number identifies the Physical Unit (PU) that is associated with the control point. A PU is a combination of hardware andsoftware that controls the links to other nodes. Several PU types with differentcapabilities and responsibilities exist, such as:v PU type 5: The best known example is an IBM mainframe processor that isrunning VTAM. VTAM provides the support for the Systems Services ControlPoint (SSCP) function that is defined in SNA.

Chapter 2. Introduction to SNA 5


20/83

v PU type 4: This is a communications controller, such as an AdvancedCommunications Function for the Network Control Program (ACF/NCP), whichresides in the center of a network, routing and controlling the data flow betweenmachines.

v PU type 2: This is a small machine, such as an Advanced Program-to-ProgramCommunications (APPC) workstation. It can communicate directly only with a PUtype 4 or a PU type 5, and relies on these PUs to route the data to the correct

system.v PU type 2.1: This is a more advanced PU type 2 that can also communicate withother PU type 2.1 nodes directly. This node can support an independent LU . Anindependent LU can establish a session with another LU without using VTAM.SNAP-IX is a PU type 2.1 node.

PU type 2.1 nodes can support Advanced Peer-to-Peer Networking (APPN). Thissupport enables a node to search for an LU in the network, rather than requiringyou to preconfigure the remote LU’s location locally. Two types of APPN nodesexist: end nodes and network nodes . An end node can receive a search request foran LU and respond, indicating whether the LU is local to the node or not. A networknode can issue search requests and respond to them. It maintains a dynamicdatabase that contains the results of the search requests. Support for APPN can

greatly reduce the maintenance work in an SNA network, especially if the network islarge or dynamic. SNAP-IX supports APPN. Alternatively, a low-entry networking (LEN) node also can be connected to an APPN network or end node, but it doesnot support APPN functions.

Each node has physical links, or connections , to other nodes so that every node isconnected 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 connectionsCICS regions can communicate across SNA with any system that supports APPC.SNAP-IX 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 Clients to use SNA to communicate with CICS.To use local SNA support, SNAP-IX must be installed and configured on the samemachine as is the CICS region.



21/83

Chapter 3. Collecting information for a SNAP-IX configuration

This following sections describe the information that you need to configure SNAP-IXfor use with CICS. You will find Systems Network Architecture (SNA) configurationmuch easier if you collect this information before you start to create the SNAdefinitions.

The steps that follow include:1. “Collecting information about the local Solaris machine (node)”2. “Collecting information about remote machines” on page 83. “Collecting information about a local CICS region” on page 104. “Collecting information about remote CICS regions” on page 105. “Collecting information about modegroups” on page 11

Collecting information about the local Solaris machine (node)

This section describes the information that you need in order to register the Solarismachine that is running SNAP-IX with the SNA network.

Your physical machine is referred to as an SNA node. You must assign to it aControl Point (CP) name, which is the name that the network uses to communicatewith it. This CP name can have one through eight characters that consist ofuppercase letters (A through Z) and numbers (0 through 9). It must be unique withinthe SNA network. It must be different from all other CP names and Logical Unit (LU)names that are in the network.

Some large SNA networks use naming conventions that prevent name clashes. Youcan often use the host name of your machine as the CP name. Consult yournetwork administrator for help when choosing names.

Associated with the CP name is the node identifier, which is also referred to as theexchange identifier or XID. This eight-digit number identifies the Physical Unit (PU)that is associated with the control point. Your network administrator can provide thisnumber.

You also need to know the name of the SNA network to which your SNA machineand all the CICS regions that use your SNA machine belong. The SNA networkname can have one through eight characters that consist of uppercase letters (Athjrough Z) and numbers (0 through 9).

Table 3 shows the information that you need in order to define an example localnode.

Table 3. Information required to define an example node

CP name Node identifier Local network name

SL000001 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 need to be defined to VTAM. Chapter 6,“Configuring VTAM with details of your CICS region,” on page 43 shows someexample VTAM definitions.



22/83

Collecting information about remote machines

This section describes the information that you need in order to connect your localSolaris machine to other machines (referred to as SNA nodes) in the SNA network.

You need to know the location of the remote CICS regions and systems with which

your local CICS for Solaris region is to communicate. You also need to know onwhich machines these systems are running, and how those machines areconnected. It is often helpful to draw a schematic diagram of the network, such asthat shown in Figure 3.

In this example, the CICS region called CICSSOL communicates with anotherregion, CICSAIX, that is running on a machine that is connected to the same localarea network (LAN). Region CICSSOL also communicates with two mainframeCICS regions, CICSESA and CICSMVS. The CICSESA region is on a machine thatis connected to the same LAN as is CICSSOL. However, CICSMVS can becontacted only through another machine. This distinction is important.

Note: When you define your connections to SNAP-IX, you need to include onlythose machines that can be contacted directly (in this example, the machinesthat are running CICSAIX and CICSESA). Connections to machines that areindirectly accessed (in this example, the machine that are runningCICSMVS) are set up in definitions in the intermediate machines. As a result,you need to consult the owners of those intermediate machines to arrangethe appropriate configurations.

To connect your local Solaris machine physically to other machines in the SNAnetwork, 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 eight

Figure 3. A simplified example heterogeneous network



23/83

characters 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. (These connection names will appear on the SNAP-IX node mainscreen, and you will use them to stop and start connections. Meaningful namesmake your network management easier.)

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

– IBM Token Ring LAN– Ethernet LAN– SDLC line

v Collect information about each remote node, for example:– Its Control Point (CP) name– Its Node identifier (XID)

v Determine the hardware (MAC) address of each remote machine. Methods fordetermining these addresses depend 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 -v

command on the AIX machine.– 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,by using the ping command on your local Solaris machine to contact it. Thenuse the command arp -a to list the addresses about which the addressresolution protocol (arp) knows. For example, Figure 4 shows how10-00-5a-4b-3c-2d, the hardware address of aix5, is obtained.

Table 4 shows the information that is collected for the example that is shown inFigure 3 on page 8.

Table 4. Information required to define example links

Connection

name

Link type Network name Remote CP

name

Remote hardware

address

LINKVTAM IBM Token Ring MYSNANET MYVTAM 400012345678

LINKAIX IBM Token Ring MYSNANET AIX00005 10005A4B3C2D

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/83

Collecting information about a local CICS region

This section describes the information that you need in order to configure a localCICS region. For the local CICS region, you need to know the following:

v The local Logical Unit (LU) name for the region. A local LU name can have oneto eight characters that consist of uppercase letters (A through Z) and numbers(0 through 9). The local LU name that you choose must be unique within yournetwork. Many networks have naming conventions that help to prevent nameclashes. Consult your network administrator for advice when choosing local LUnames.

v The default modename to use when the region does not explicitly specify amodename on an intersystem request. You can specify a modename explicitly onan intersystem request by using the SNAModeName attribute of the CICSTransaction Definitions (TD), or by using the PROFILE option of the EXEC CICSALLOCATE command. Alternatively, you can specify a modename in theDefaultSNAModeName 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 to define a CICS region calledCICSSOL. The default modename for this LU name is CICSISC0.

Table 5. Information required to define an example local system

Local LU name Local LU alias Synchronization

level 2?

CICS CD DefaultSNA

ModeName

CICSSOL CICSSOL No CICSISC0

Collecting information about remote CICS regionsThis section describes the information that you need to know about the remotesystems 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 the following:

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 in the APPL parameter of the ADDCICSSIT command.

v The name of the SNA network to which it belongs. A SNA network name can

have 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.



25/83

v The level of security, if any, that is used for the communications. You can useconversation-level security, which involves receiving a user ID from the remotesystem. Refer to the TXSeries for Multiplatforms Intercommunication Guide formore information.

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

Table 6. Information required to define example remote systems Partner LU name Partner LU alias Partner CP name

CICSESA CICSESA MYSNANET.MYVTAM

CICSMVS CICSMVS MYSNANET.MYVTAM

CICSAIX CICSAIX MYSNANET.AIX00005

Collecting information about modegroups

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

When you configure your network, you can set up individual characteristics for thedifferent sessions that are established between a pair of LUs, such as the route thatis taken through the network. The set of characteristics for a session is referred toas a modegroup or mode . All the sessions that are associated with a modegrouphave the same characteristics. A modegroup is identified by a modename of one toeight characters that consist of uppercase letters (A through Z) and numbers (0through 9).

You must define at least one modegroup to SNAP-IX. SNA connections can sharemodegroup definitions. The session limits that are defined in a modegroup applyindependently to each connection that uses that modegroup. A connection can usemore than one modegroup. For example, suppose you have a connection thathandles fast intersystem requests for interactive users and slower intersystemrequests that send or receive large amounts of data. Simply define twomodegroups: one for the interactive requests (called modename CICSISC0), andthe other, for the slower data transfer requests (called modename CICSISC1).

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 you need in order to define two modegroups.Remember that the modegroups that are used on a connection must be defined

with consistent session limits on both systems. If SNAP-IX uses VTAM tocommunicate with the remote system, you must include a MODEENT definition forthe modename in the VTAM tables. Refer to Chapter 6, “Configuring VTAM withdetails of your CICS region,” on page 43 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 3. Collecting information for a SNAP-IX configuration 11


26/83

System-defined SNASVCMG and CPSVCMG modegroupsSNA network connections that use parallel sessions have a standard modegroupcalled SNASVCMG . This is a system-defined modegroup reserved for use by SNAmanagement programs. Do not attempt to define this modegroup in SNAP-IX or useit 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/83

Chapter 4. Configuring SNAP-IX

The following sections describe how to configure SNAP-IX:

v “Configuring a node”

v “Configuring a port” on page 17

v “Configuring a link station” on page 19v “Configuring a local LU for CICS local SNA support” on page 22

v “Configuring a partner LU on a remote node” on page 24

v “Configuring modegroups” on page 27

v “Configuring conversation level security” on page 29

Ensure that you have read Chapter 3, “Collecting information for a SNAP-IXconfiguration,” on page 7 and have all the information that you need about thesystems that you want to connect across a Systems Network Architecture (SNA)network.

In the configuration example that is presented in this section, it is assumed that

SNAP-IX is installed and has been enabled by using the sna start command.

Note: Normally, the sna start command needs to be run only once afterinstallation. SNAP-IX updates the startup file to include the sna startcommand. This ensures that SNAP-IX activates automatically at systemstartup. See the SNAP-IX Installation Guide and SNAP-IX Administration Guide for more information about SNAP-IX installation.

The examples that follow are not designed to cover every aspect of configuringSNAP-IX. Only those fields that are particularly relevant to CICS are discussed.Using default values works well for many other fields. If you require moreinformation, you can see a description of each field by selecting the Help button onthe configuration window in which the field appears.

Configuring a node

This section describes how to define your local machine. It uses the values that areshown in Table 8 in an example local machine configuration.

Table 8. Information required to configure an example local node

CP name Node identifier Local network name

SL000001 05F01234 MYSNANET

To configure the node, follow these steps:

1. Ensure that SNAP-IX is active, and start the administration utility xsnaadmin byissuing the following command:

/opt/sna/bin/X11/xsnaadmin

The SNAP-IX node main screen is displayed, along with the XSnaadminmessage box, which asks you to configure the local node.

2. Click Cancel in the XSnaadmin message box.

Note: Clicking OK in the XSnaadmin message box brings up a SNAP-IX nodeconfiguration Task Sheet that can lead you through node configuration.



28/83

For the purposes of this example, however, click Cancel instead.The SNAP-IX node main screen is displayed, as shown in Figure 5.

3. From the Services menu, click the Configure node parameters option. TheNode parameters screen appears.

4. Select the node type for the node that you are defining, by clicking the APPNsupport selection box (in this example, select the LEN node option).

5. In the Control point name field, enter the SNA network name in the first boxand the CP name in the second (in this example, MYSNANET and SL000001).

6. In the Control point alias field, enter the CP name (in this example, SL000001).

7. In the Node ID field, enter the first three characters of the node identifier (XID)in the first box, and the next five characters of the XID in the second box (in thisexample, 05F and 01234).

Figure 5. SNAP-IX node main screen with unconfigured node



29/83

8. Enter a description if desired. Your screen now appears as shown in Figure 6.

9. Click OK. SNAP-IX creates a default local LU that is based on this node, whichappears in the Independent local LUs pane on the SNAP-IX node mainscreen, as shown in Figure 7 on page 16.

Figure 6. Node parameters screen

Chapter 4. Configuring SNAP-IX 15


30/83

Configuring links

This section describes how to define links to other machines in the SNA network. It

uses the values that are given in Table 9 in an example configuration.Table 9. Information required to configure example links

Connection

name

Link type Network name Remote CP

name

Remote

hardware

address

LINKVTAM IBM Token Ring MYSNANET MYVTAM 400012345678

LINKAIX IBM Token Ring MYSNANET AIX00005 10005A4B3C2D

Figure 7. SNAP-IX node main screen with configured node



31/83

Before you can connect to other machines, you must configure a port. Thexsnaadmin utility automatically configures the associated data link control (DLC)device driver when the port is configured. The DLC device driver controls the use ofthe network connection to your machine. The port and DLC are configuredseparately when you use the command-line administration program.

Configuring a port

To configure a port, use the following procedure:

1. From the SNAP-IX node main screen that is shown in Figure 7 on page 16,click anywhere within the Connectivity and dependent LUs pane to highlightit.

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

3. Click the Port using button to display a list of options. For this example, selectthe SunLink TRI/S Adapter option, as shown in Figure 8.

4. Click OK on the Add to screen. The Token ring SAP screen is displayed.

5. For this example, clear the Use HPR on implicit links option and ensure thatthe Initially active option is selected.

6. Enter a description if desired. Accept the default values for all other attributes.Your screen now appears as shown in Figure 9 on page 18.

Figure 8. Add to screen with indicated port



32/83

7. Click OK to return to the SNAP-IX node main screen, which now appears asshown in Figure 10 on page 19.

Figure 9. Token ring SAP screen



33/83

Configuring a link station

At this point, you have configured a port and DLC device driver. (In this example,

the xsnaadmin utility configured the DLC automatically when you configured theport.) You can now connect your machine to other machines by using link stationdefinitions. Use the following procedure to configure a link station called LINKAIX,which connects a machine that is running CICS for Solaris to a machine that isrunning CICS for AIX:

1. From the SNAP-IX node main screen that is shown in Figure 10, click theTRSAPO entry in the Connectivity and dependent LUs pane.


3. Ensure that the Link station to port TRSAPO option is selected and click OK.The Token ring link station screen is displayed.

Figure 10. SNAP-IX node main screen with added Token Ring port



34/83

4. In the Name field, enter the link name (in this example, LINKAIX).

5. Accept the default value of TRSAPO in the SNA port name field.

6. Click the Activation option button. Select the On node startup option fromthe list that is displayed.

7. In the LU traffic section, select the Independent only option.

8. In the Independent LU traffic section’s Remote node field, enter the network

name (in this example, MYSNANET) in the first box and the control point name ofthe remote node (in this example, AIX00005) in the second box.

9. In the Contact information section, do the following:

a. Enter the remote machine’s MAC address (in this example, 10005A4B3C2D)in the MAC address field.

b. Accept the default value in the SAP number field.

10. Enter a description, if desired. Your screen now appears as shown inFigure 11.

11. Click OK.

Figure 11. Token ring link station screen for LINKAIX



35/83

12. A message box is displayed that asks whether you want to add the remotenode definition to your configuration automatically. Click OK.

13. A message box is displayed that informs you that the remote node has beendefined. Click OK to return to the SNAP-IX node main screen.

14. Follow similar steps to configure the LINKVTAM link station, which connects amachine that is running CICS for Solaris to a machine that is running CICS for

VSE/ESA

™

. Your screen now appears as shown in Figure 12.

Figure 12. SNAP-IX node main screen with added link stations



36/83

Configuring a local LU for CICS local SNA support

You need to define a unique local LU to configure a CICS system. This sectionuses the values that are given in Table 10 in an example configuration.

Table 10. Information required to configure an example local system

Local LU name Local LU alias Synchronization level 2?CICSSOL CICSSOL No

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

1. From the SNAP-IX node main screen that is shown in Figure 12 on page 21,click anywhere within the Independent local LUs pane to highlight it.

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

3. Enter the LU name (for this example, CICSSOL) in the LU name field.

4. Click the box that is beside the LU alias field. Because the LU alias must matchthe LU name, the xsnaadmin utility automatically inserts the entry from the LUname field into the LU alias field.

5. Enter a description if desired. Your screen now appears as shown in Figure 13.

6. Click the Advanced button.

7. Ensure that the Support Syncpoint option is unselected, as shown in Figure 14on page 23. (The default value is unselected.)

Figure 13. Local LU screen



37/83

8. Click OK.

9. Click OK to return to the SNAP-IX node main screen, which now appears asshown in Figure 15 on page 24.

Figure 14. Local LU Advanced screen



38/83


39/83

Intercommunication Guide .

Table 11. Information required to configure example remote systems

Partner LU name Partner LU alias Partner CP name

CICSESA CICSESA MYSNANET.MYVTAM

CICSMVS CICSMVS MYSNANET.MYVTAM

CICSAIX CICSAIX MYSNANET.AIX00005

To configure a partner LU, use the following procedure:

1. From the SNAP-IX node main screen that is shown in Figure 15 on page 24, inthe Remote systems pane, click the remote node that will contain the partnerLU (in this example, MYSNANET.MYVTAM).


3. Ensure that the Define partner LU on node MYSNANET.MYVTAM option isselected and click OK. The Partner LU screen is displayed.

4. Enter the partner LU name (in this example, CICSESA) in the second box to theright of the Partner LU name field.

5. Click the boxes that are beside the Alias and Uninterpreted name fields. Theyfill in automatically.

6. Ensure that the Supports parallel sessions option is selected.

7. Add a description if desired, and accept any other default values. Your screennow appears as shown in Figure 16 on page 26.



40/83

8. Click OK to return to the SNAP-IX node main screen.

9. Follow similar steps to define the CICSMVS and CICSAIX partner LUs. Yourscreen now appears as shown in Figure 17 on page 27.

Figure 16. Partner LU screen



41/83

Configuring modegroups

This section describes how to configure modegroups. It uses the values that aregiven in Table 12 in an example configuration.

Table 12. Information required to configure example modegroups

Modename Max sessions Min winners

CICSISC0 10 5

CICSISC1 4 2

To define a modegroup, use the following procedure:

1. From the SNAP-IX node main screen that is shown in Figure 17, select APPCfrom the Services menu.

2. Select the Modes option from the menu that is associated with the APPCoption. The Modes screen is displayed.

Figure 17. SNAP-IX node main screen with added partner LUs



42/83

3. Click the New button on the Modes screen. The Mode screen is displayed.

4. Enter the modename (in this example, CICSISC0) in the Name field.

5. In the Session limits section, enter 10 in the Initial field and 5 in the Min.con. winner sessions and Auto-activated sessions fields.

6. Enter a description if desired, and accept the default values in the other fields.Your screen now appears as shown in Figure 18.

7. Click OK.

8. Make CICSISC0 the default modename by clicking the CICSISC0 modenameon the Modes screen to highlight it, then clicking the Make default button.

Figure 18. Mode screen



43/83

9. Follow similar steps to configure mode CICSISC1. The modes CICSISC0 andCICSISC1 now appear on the listing in the Modes screen, as shown inFigure 19.

Note: Do not make CICSISC1 the default modename.

10. Click Done in the Modes screen to return to the SNAP-IX node main screen.

Configuring conversation level security

SNAP-IX permits you to configure conversation-level security, which involvesreceiving a user ID from the remote system, on a separate screen. You can accessthis screen by selecting the APPC option from the Services menu on the SNAP-IXnode main screen, then selecting the Security option and the Conversation levelsecurity option from the displayed submenus. For more information about how toconfigure conversation-level security, see the SNAP-IX Administration Guide andthe TXSeries for Multiplatforms Intercommunication Guide .

Figure 19. Modes screen



44/83



45/83

Chapter 5. Matching SNAP-IX parameters with CICSparameters

After configuring SNAP-IX, configure the CICS communications resources. Thisprocess is described in detail in the TXSeries for Multiplatforms Intercommunication

Guide . Some of the parameter values that you specify when configuring CICS mustmatch those that you have used to configure SNAP-IX. This section describes theparameter values that must match.

Table 13, Table 14 on page 32, and Table 15 on page 32 show examples of theparameter values that are defined in SNAP-IX. These values must match those of alocal CICS region, CICSSOL, that is connected to a remote CICS region,CICSESA. Table 13 shows the Local LU parameter values that are defined inSNAP-IX. These values must also match. Table 14 on page 32 shows the RemoteLU parameter values that must match. Table 15 on page 32 shows the Modeparameter values that must match.

Similar matches must also be created among parameter values that are defined in

SNAP-IX, the local CICS region CICSSOL, and the remote CICS region CICSMVS.

SNAP-IX and the two CICS regions are represented in the columns; read acrossthe rows to see the matching parameter values. For example, in Table 13, the valueCICSSOL must be used in the LU Name parameter in SNAP-IX, the LocalLUNameparameter in the Region Definitions (RD) of region CICSSOL, and the NETNAMEparameter of region CICSESA.

Note: Some parameter values need to match only between two of the columns.For example, in Table 13, the value SOL must match only in the LocalSysIdparameter in the Region Definitions (RD) of region CICSSOL and in theCONNECTION parameter of region CICSESA. No match is required in anyLocal LU parameters in SNAP-IX. In cases such as this, the term Not

applicable appears on the line in the column where no match is needed.

Table 13. Matching the Local LU parameter values of SNAP-IX with selected parameter

values of local CICS region CICSSOL and partner CICS region CICSESA

SNAP-IX Region CICSSOL Region CICSESA

Local LU parameters Region Definitions (RD)

Network Name=MYSNANET LocalNetworkName=MYSNANET

Not applicable

LU Name=CICSSOL

LU Alias=CICSSOL

LocalLUName=CICSSOL NETNAME=CICSSOL

Not applicable LocalSysId=SOL CONNECTION=SOL

Communications Definitions

(CD)

CESA:



46/83


47/83

SNAP-IX and the two CICS regions are represented in the columns; read acrossthe rows to see the matching parameter values. For example, in Table 16, the valueCICSSOL must be used in the LU Name parameter in SNAP-IX, the LocalLUNameparameter in the Region Definitions (RD) of region CICSSOL, and theRemoteLUName parameter of region CICSAIX.

Note: Some parameter values need to match only between two of the columns.

For example, in Table 18 on page 34, the value CICSISC0 must match only inthe Modename parameter in SNAP-IX, and in the DefaultSNAModeNameparameter in the Communications Definitions (CD) of region CICSSOL. Nomatch is required in any parameters in region CICSAIX. In cases such asthis, the term Not applicable appears on the line in the column in which nomatch is needed.

Table 16. Matching the Local LU parameter values of SNAP-IX with selected parameter

values of local CICS region CICSSOL and partner CICS region CICSAIX

SNAP-IX Region CICSSOL Region CICSAIX

Local LU parameters Region Definitions (RD) Communications

Definitions (CD)

COSSOL:

Network Name=MYSNANET LocalNetworkName=MYSNANET

RemoteNetworkName=MYSNANET

LU Name=CICSSOL

LU Alias=CICSSOL

LocalLUName=CICSSOL RemoteLUName=CICSSOL

Communications

Definitions (CD)

CAIX:

Support Syncpoint=no ConnectionType=local_sna Not applicable

GatewayName=″″ Not applicable

Listener Definitions (LD)

LOCALSNA:

Protocol=SNA Not applicable

Table 17. Matching the Remote LU parameter values of SNAP-IX with selected parameter

values of local CICS region CICSSOL and partner CICS region CICSAIX

SNAP-IX Region CICSSOL Region CICSAIX

Remote LU parameters Communications

Definitions (CD)

CAIX:

Region Definitions (RD)

Network Name= MYSNANET RemoteNetworkName=MYSNANET

LocalNetworkName=MYSNANET

LU Name=CICSAIX

LU Alias=CICSAIX

RemoteLUName=CICSAIX LocalLUName=CICSAIX

Chapter 5. Matching SNAP-IX parameters with CICS parameters 33


48/83


49/83

[define_node]node_name = SL000001description = Control pointfqcp_name = MYSNANET.SL000001node_type = LEN_NODEmode_to_cos_map_supp = NOmds_supported = YESnode_id =

max_locates = 1500dir_cache_size = 255max_dir_entries = 0locate_timeout = 0reg_with_nn = YESreg_with_cds = YESmds_send_alert_q_size = 100cos_cache_size = 24tree_cache_size = 40tree_cache_use_limit = 40max_tdm_nodes = 0max_tdm_tgs = 0max_isr_sessions = 1000isr_sessions_upper_threshold = 900isr_sessions_lower_threshold = 800isr_max_ru_size = 16384isr_rcv_pac_window = 8store_endpt_rscvs = NOstore_isr_rscvs = NOstore_dlur_rscvs = NOdlur_support = NOpu_conc_support = YESnn_rar = 128max_ls_exception_events = 0ms_support = NORMALqueue_nmvts = YESptf_flags = NONE

Figure 21. define_node stanza

[define_tr_dlc]dlc_name = TOKEN0description = ""neg_ls_supp = YEScard_type = SPARC_TRI_Sinitially_active = NOadapter_number = 0

Figure 22. define_tr_dlc stanza



50/83

[define_tr_port]port_name = TRSAP0description = Token Ring portdlc_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_NEGimplicit_dspu_services = NONEimplicit_dspu_template = ""implicit_ls_limit = 0act_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 = 30implicit_hpr_support = NOimplicit_link_lvl_error = NOeffect_cap = 3993600connect_cost = 0byte_cost = 0security = SEC_NONSECUREprop_delay = PROP_DELAY_LANuser_def_parm_1 = 128user_def_parm_2 = 128user_def_parm_3 = 128initially_active = YESwindow_inc_threshold = 1test_timeout = 10test_timer_retry = 5

xid_timer = 10xid_timer_retry = 5ack_timeout = 5000p_bit_timeout = 5000t2_timeout = 100rej_timeout = 10busy_state_timeout = 30idle_timeout = 30max_retry = 3

Figure 23. define_tr_port stanza



51/83

[define_tr_ls]ls_name = LINKAIXdescription = Link to AIXport_name = TRSAP0adj_cp_name = MYSNANET.AIX00005adj_cp_type = END_NODEmac_address = lsap_address = 0x04

auto_act_supp = NOtg_number = 0limited_resource = NOsolicit_sscp_sessions = NOpu_name = disable_remote_act = NOdefault_nn_server = NOdspu_services = NONEdspu_name = dlus_name = bkup_dlus_name = hpr_supported = NOhpr_link_lvl_error = NOlink_deact_timer = 30use_default_tg_chars = YESls_attributes = SNAadj_node_id = local_node_id = cp_cp_sess_support = NOeffect_cap = 3993600connect_cost = 0byte_cost = 0security = SEC_NONSECURE: :: :initially_active = YESreact_timer = 30react_timer_retry = 65535test_timeout = 10test_timer_retry = 5xid_timer = 10

xid_timer_retry = 5ack_timeout = 5000p_bit_timeout = 5000t2_timeout = 100rej_timeout = 10busy_state_timeout = 30idle_timeout = 30max_retry = 3

[define_tr_ls]ls_name = LINKVTAMdescription = Link to VTAMport_name = TRSAP0adj_cp_name = MYSNANET.MYVTAMadj_cp_type = END_NODEmac_address =

lsap_address = 0x04auto_act_supp = NOtg_number = 0limited_resource = NOsolicit_sscp_sessions = NOpu_name = disable_remote_act = NOdefault_nn_server = NOdspu_services = NONEdspu_name = dlus_name = bkup_dlus_name = hpr_supported = NOhpr_link_lvl_error = NOlink_deact_timer = 30

use_default_tg_chars = YESls_attributes = SNAadj_node_id =



52/83


53/83

[define_mode]mode_name = CICSISC0description = Mode CICSISC0max_neg_sess_lim = 32767plu_mode_session_limit = 10min_conwin_src = 5min_conloser_src = 0auto_act = 5

receive_pacing_win = 4max_receive_pacing_win = 0default_ru_size = YESmax_ru_size_upp = 1024max_ru_size_low = 0cos_name = #CONNECT

[define_mode]mode_name = CICSISC1description = ""max_neg_sess_lim = 4plu_mode_session_limit = 4min_conwin_src = 2mIn_conloser_src = 0auto_act = 2receive_pacing_win = 4

max_receive_pacing_win = 0default_ru_size = YESmax_ru_size_upp = 1024max_ru_size_low = 0cos_name = #CONNECT

Figure 27. define_mode stanzas



54/83

The sna_domn.cfg fileThe following stanza is defined:

[define_directory_entry]resource_name = MYSNANET.MYVTAMresource_type = ENCP_RESOURCEdescription = (Auto defined - remote node)parent_name = parent_type = ENCP_RESOURCE

[define_directory_entry]resource_name = MYSNANET.MYVTAM

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

[define_directory_entry]resource_name = MYSNANET.CICSESAresource_type = LU_RESOURCEdescription = CICS for VSE/ESA regionparent_name = MYSNANET.MYVTAMparent_type = ENCP_RESOURCE

[define_directory_entry]resource_name = MYSNANET.CICSMVSresource_type = LU_RESOURCEdescription = CICS for MVS/ESA region

parent_name = MYSNANET.MYVTAMparent_type = ENCP_RESOURCE

[define_directory_entry]resource_name = MYSNANET.AIX00005resource_type = ENCP_RESOURCEdescription = (Auto defined - remote node)parent_name = parent_type = ENCP_RESOURCE

[define_directory_entry]resource_name = MYSNANET.CICSAIXresource_type = LU_RESOURCEdescription = CICS for AIX regionparent_name = MYSNANET.AIX00005parent_type = ENCP_RESOURCE

[define_directory_entry]resource_name = MYSNANET.AIX00005resource_type = LU_RESOURCEdescription = (Auto defined - default LU)parent_name = MYSNANET.AIX00005parent_type = ENCP_RESOURCE

Figure 28. define_directory_entry stanzas

[define_defaults]description = ""mode_name = CICSISC0implicit_plu_forbidden = NOspecific_security_codes = NOlimited_timeout = 20

Figure 29. define_defaults stanza



55/83

[define_domain_config_file]major_version = 5minor_version = 1update_release = 1revision_level = 4comment = ""updating = N

Figure 30. define_domain_config_file stanza



56/83



57/83

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 CICS products such as CICS TransactionServer for z/OS and CICS for VSE/ESA. VTAM uses the services of the NetworkControl Program (NCP) product to connect the mainframe to the network.Therefore, the NCP possibly needs to be updated to enable it will pass requestsfrom your Systems Network Architecture (SNA) machine to VTAM and to the remotesystem beyond.

Code VTAM and NCP definitions by using macros. The following sections show afew example definitions. Use these examples for guidance only; they cannot coverthe extensive range of network configurations that are possible. Refer to VTAM andNCP documentation for more information and examples of VTAM and NCPdefinitions.

Defining your machine and CICS regions to VTAM

The VTAM Physical Unit (PU) macro defines the machine on which your SNAproduct is running. Figure 31 provides an example of a PU macro for a PC that isrunning CICS for Solaris and is connected to the network with an IBM Token Ring:

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 (also known as an XID or node identifier) or a control point(CP) name to match a request from your machine to its PU definition. The PUdefinition that is shown in Figure 31 has an XID defined. This consists of the IDBLK

and IDNUM values. Therefore, the SNA product is configured with an XID of05F01234.

You can code the CP name on a PU definition by using the CPNAME parameter.This coding is not required in the example in Figure 31 because the XID is coded. Ifyour SNA product allows you to configure both an XID and a CP name, but youspecify only an XID in the VTAM PU definition, specify the same PU name(SL000001 in this example) as the CP name. This makes it easier for you toassociate the VTAM PU definition with your machine. However, if you use theCPNAME parameter in the PU definition, that CP name must be different from thePU name.

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

IDBLK=05F, 071 = RS/6000, 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 X

PACING=0, XVPACING=0, XPUTYPE=2, XISTATUS=ACTIVE

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

Figure 31. VTAM physical unit (PU) macro definition



58/83

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 for yourmachine to call. However, if you want to set up VTAM so that it calls your machine,VTAM needs to know the address of your machine. This address is specified in aPATH definition. The PATH definition is coded just after the PU definition.

Following 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,and are configured in the SNA product in those machines.

The LOCADDR=0 parameter in the LU definition indicates that the region’s LU isindependent. This enables it to communicate with other independent LUs withoutusing VTAM. The MODETAB parameter specifies the name of the VTAM mode tablethat defines all the modegroups (modenames) that the CICS region uses. Examplesof mode table entries are shown in Figure 34 on page 45.

Defining modegroups to VTAM

The example macro that is in Figure 34 on page 45 shows part of a VTAM modetable MTCICS. This defines a number of modegroups, including modename CICSISC0.The mode table that a CICS region uses must have a definition for all themodegroups (modenames) that it uses and a definition for the SNASVCMG modegroup.This modegroup is used by your SNA product for network management requests.

************************************************************************SU01 PATH GRPNM=SUN, ECLTYPE=LOGICAL group in NCP X

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

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

Figure 32. VTAM PATH macro definition

************************************************************************CICSSOL LU LOCADDR=0,ISTATUS=ACTIVE,MODETAB=MTCICS************************************************************************

Figure 33. VTAM logical unit (LU) definition



59/83

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

: : : : :** Modename CICSISC0 - Parallel_Sessions=yes*

CICSISC0 MODEENT LOGMODE=CICSISC0, XTYPE=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*SNASVCMG MODEENT LOGMODE=SNASVCMG

: : : : :MODEEND

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

Figure 34. VTAM mode table macro

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


60/83



61/83

Chapter 7. Operating SNAP-IX

The sections that follow describe how to control Systems Network Architecture(SNA) SNAP-IX resources:

v “Introduction to SNAP-IX operation”

v“Starting the node and connections” on page 49

v “Stopping the node and connections” on page 51

v “Starting, viewing, and stopping sessions” on page 52

For more detailed information about these topics, see the SNAP-IX Administration Guide .

Introduction to SNAP-IX operation

Figure 35 on page 48 shows a typical system configuration before the node,connections, and sessions are activated.



62/83

Node status appears in the node box that is in the upper right corner of theSNAP-IX node main screen. One of the following states always appears:

v Active: The node is active.

v Inactive: The node is inactive. (If you start a link station or port when the node isinactive, the node starts automatically.)

v Unconfigured: The node is not configured.

vStarting: The node is starting. This status appears for a short time when thenode is being started.

v Stopping: The node is stopping. This status appears for a short time when thenode is being stopped.

The status state of an individual port or link station is displayed beside it in theConnectivity and dependent LUs pane. Possible port states are as follows:

v Active: The port is active.

v Inactive: The port is inactive. (If you start a link station when the port is inactive,the port starts automatically.)

Figure 35. Typical system configuration before the node, connections, and sessions are activated



63/83

v Starting: The port is starting.

v Stopping: The port is stopping.

Possible link station states are as follows:

v Active: The link station is active and session traffic can use it.

v Listening: The link station is currently stopped. It can be activated by a remote

system that needs to start a session with a local node.v On demand: The link station is currently stopped. It can be activated by a localapplication if that application needs to start a session, or by a remote system thatneeds to start a session with a local node.

v Inactive: The link station’s parent port is inactive. The link station can beactivated by a local application or by a remote system.

v Disabled: The link station is currently stopped. It cannot be activated by a localapplication or by a remote system.

v Starting: The link station is starting.

v Stopping: The link station is stopping.

v Pending Retry: The link station failed to start or was deactivated because of a

failure. SNAP-IX is continuing to attempt to reactivate it and will retry the linkstation soon.

You can get the status of a port or link station by clicking it in the Connectivity anddependent LUs pane of the SNAP-IX node main screen, then clicking the Statusbutton in the toolbar.

Starting the node and connections

SNAP-IX lets you simultaneously start your node and any connections that youhave indicated to activate at startup. (You use the screens that are shown inFigure 9 on page 18 and Figure 11 on page 20 to configure connections to activateat startup.) Alternatively, you can start connections separately from their associatednodes.

Starting the node and connections that activate automatically atstartup

To start the node and any connections that you have indicated to activate at startup:

1. From the SNA node main screen that is shown in Figure 35 on page 48, clickthe node button in the upper right corner of the screen.

2. Click the Start button on the toolbar. The word Active appears under the nodename on the node button. The associated ports and link stations that you haveindicated to start automatically are also activated, as shown in Figure 36 onpage 50.

Chapter 7. Operating SNAP-IX 49


64/83

If the node or connections or both are not activated successfully, SNAP-IX writeserror messages to its log file. You can view the error log file (sna.err) or the auditlog file (sna.aud) in the directory /var/opt/sna by using a text editor. (Refer toChapter 8, “Problem determination for SNAP-IX,” on page 55 for more details onlogging.)

Starting connections that do not activate at startup

To start a port that is not activated automatically at startup:

1. Ensure that the associated node is active (the term Active appears on the nodebutton that is in the upper right corner of the SNAP-IX node main screen).

2. Click the port in the Connectivity and dependent LUs pane of the SNAP-IXnode main screen.

3. Click the Start button.

To start a link station that is not activated automatically at startup:

Figure 36. Starting the node and connections



65/83

1. Ensure that the associated node is active (the term Active appears on the nodebutton that is in the upper right corner of the SNAP-IX node main screen).

2. If the parent port is active:

a. Click the link station in the Connectivity and dependent LUs pane of theSNAP-IX node main screen.

v If the Listening state is displayed for the link station, click the Start

button in the toolbar.v If the Disabled state is displayed for the link station:

1) Click the Start button in the toolbar.

2) A message asks if you want to start the link station or simply enable itfor autoactivation without starting it. Select the appropriate option andclick OK.

3. If the parent port is inactive:

a. Click the link station in the Connectivity and dependent LUs pane of theSNAP-IX node main screen.

v If the Inactive state is displayed for the link station, click the Start buttonin the toolbar. The parent node is activated with the link station.

v

If the Disabled state is displayed for the link station:1) Click the Start button in the toolbar.

2) A message asks if you want to start the link station or simply enable itfor autoactivation without starting it. Select the appropriate option andclick OK. The parent node is activated with the link station in eithercase.

Stopping the node and connections

SNAP-IX lets you stop the node and connections simultaneously or separately.

Stopping the node and connections simultaneously

To stop the node and any associated connections simultaneously:

1. From the SNA node main screen that is shown in Figure 36 on page 50, clickthe node button that is in the upper right corner of the screen.

2. Click the Stop button on the toolbar.

3. A message asks you to confirm your request to stop the node. Click OK. Theword Inactive appears under the node name on the node button. The portsand link stations that are associated with the node also stop.

Stopping connections without stopping the node

To stop a port without stopping the node:

1. From the Connectivity and dependent LUs pane of the SNAP-IX node mainscreen, click the port that you want to stop.


3. A message asks you to confirm your decision to stop the node. Click OK. Allassociated link stations are stopped also.

To stop a link station without stopping the node:

1. From the Connectivity and dependent LUs pane of the SNAP-IX node mainscreen, click the link station that you want to stop.

Chapter 7. Operating SNAP-IX 51


66/83


3. A message asks you to confirm your request to stop the link station, and givesyou the option of leaving the link station available for autoactivation. Select theappropriate option and click OK. If you stopped the link station, leaving itavailable for autoactivation, Inactive or Listening appears beside the linkstation name in the Connectivity and dependent LUs pane of the SNAP-IXnode main screen. If you disabled the link station, Disab

txseries for multiplatforms using snap-ix for solaris with cics version 6.2

Documents