txseries for multiplatforms using ibm communications server for windows systems with cics version...

7/26/2019 TXSeries for Multiplatforms Using IBM Communications Server for Windows Systems With CICS Version 6.2

1/101

TXSeries for Multiplatforms

UsingIBM Communications Server forWindows Systems with CICS

Version 6.2

SC34-6748-01


2/101


3/101

TXSeries for Multiplatforms

UsingIBM Communications Server forWindows Systems with CICS

Version 6.2

SC34-6748-01


4/101

Note

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

Second Edition (January 2008)

This edition replaces SC34-6748-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/101

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 IBM Communications Server for Windows 2003 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 . . . . . . . . . . . . . . . . 5

Chapter 3. Collecting information for a new SNA configuration . . . . . . 7Collecting information about the local Windows machine . . . . . . . . . . 7Collecting information about remote machines . . . . . . . . . . . . . . 8Collecting information about remote systems . . . . . . . . . . . . . . 10Collecting information about local CICS regions . . . . . . . . . . . . . 10Collecting information about modegroups . . . . . . . . . . . . . . . 11System-defined SNASVCMG and CPSVCMG modegroups . . . . . . . 12

Chapter 4. Creating a Communications Server configuration . . . . . . 13Choosing a configuration scenario . . . . . . . . . . . . . . . . . . 13

Configuring the local Windows machine (node) . . . . . . . . . . . . . 16Configuring links . . . . . . . . . . . . . . . . . . . . . . . . 18Configuring devices . . . . . . . . . . . . . . . . . . . . . . 19Configuring peer connections . . . . . . . . . . . . . . . . . . 21

Configuring remote systems . . . . . . . . . . . . . . . . . . . . 24Configuring your CICS region . . . . . . . . . . . . . . . . . . . 27Configuring modenames . . . . . . . . . . . . . . . . . . . . . 29Completing the Communications Server configuration . . . . . . . . . . 31

Chapter 5. Example Communications Server configuration profiles . . . . 33Example SNA definitions for IBM Communications Server for Windows . . . . 34Example CICS for Windows systems configurations . . . . . . . . . . . 47Example CICS for VSE/ESA SNA profiles . . . . . . . . . . . . . . . 49

Example CICS for MVS/ESA SNA profiles . . . . . . . . . . . . . . . 51Example Communications Server for AIX profiles . . . . . . . . . . . . 53Example CICS on Open Systems SNA profiles . . . . . . . . . . . . . 56

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

Chapter 7. Operating Communications Server . . . . . . . . . . . . 63Introduction to the SNA Node Operations application . . . . . . . . . . . 63Starting the node and connections. . . . . . . . . . . . . . . . . . 65

Copyright IBM Corp. 1999, 2008 iii


6/101

Starting the node and connections that activate at startup . . . . . . . . 65Starting connections that do not activate at startup. . . . . . . . . . . 66

Stopping the node and connections . . . . . . . . . . . . . . . . . 68Stopping the node and connections simultaneously . . . . . . . . . . 68Stopping connections without stopping the node . . . . . . . . . . . 69

Starting, viewing, and stopping sessions . . . . . . . . . . . . . . . 69Starting sessions . . . . . . . . . . . . . . . . . . . . . . . 69

Viewing sessions . . . . . . . . . . . . . . . . . . . . . . . 71Stopping sessions. . . . . . . . . . . . . . . . . . . . . . . 71

Chapter 8. Problem determination for Communications Server . . . . . . 73The Log Viewer application . . . . . . . . . . . . . . . . . . . . 73The Display SNA Sense Data application . . . . . . . . . . . . . . . 74The Trace Facility application . . . . . . . . . . . . . . . . . . . 74

Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . 77SNA books . . . . . . . . . . . . . . . . . . . . . . . . . . 77IBM Communications Server for Windows books . . . . . . . . . . . . 77CICS books . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Trademarks and service marks . . . . . . . . . . . . . . . . . . . 80

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

iv TXSeries for Multiplatforms: Using IBM Communications Server for Windows Systems with CICS


7/101

Figures

1. An example heterogeneous network . . . . . . . . . . . . . . . . . . . . . . . . 32. An example schematic diagram of a heterogeneous network . . . . . . . . . . . . . . . 83. Using the ping and arp -a commands to obtain the address of a remote machine . . . . . . . 94. Choose a Configuration Scenario panel . . . . . . . . . . . . . . . . . . . . . . 145. SNA Node Configuration panel. . . . . . . . . . . . . . . . . . . . . . . . . . 156. Define the Node panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177. SNA Node Configuration panel with added node . . . . . . . . . . . . . . . . . . . 188. Device Type panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199. Define a LAN Device panel . . . . . . . . . . . . . . . . . . . . . . . . . . . 2010. SNA Node Configuration panel with added LAN device . . . . . . . . . . . . . . . . . 2111. Define a LAN Connection panel Basic options . . . . . . . . . . . . . . . . . . . . 2212. Define a LAN Connection panelAdvanced options . . . . . . . . . . . . . . . . . . 2313. SNA Node Configuration panel with added LINKVTAM and LINKAIX connections . . . . . . . 2414. Define a Partner LU 6.2 panel . . . . . . . . . . . . . . . . . . . . . . . . . . 2515. SNA Node Configuration panel with added partner LUs. . . . . . . . . . . . . . . . . 2716. Define a Local LU 6.2 panelBasic options . . . . . . . . . . . . . . . . . . . . . 28

17. SNA Node Configuration panel with added Local LU 6.2s . . . . . . . . . . . . . . . . 2918. Define a Mode panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3019. SNA Node Configuration panel with added modes . . . . . . . . . . . . . . . . . . 3120. Network used to show example SNA profiles . . . . . . . . . . . . . . . . . . . . 3321. The local machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3422. LINKVTAM connectionBasic options . . . . . . . . . . . . . . . . . . . . . . . 3523. LINKVTAM connectionAdvanced options . . . . . . . . . . . . . . . . . . . . . 3624. LINKAIX connectionBasic options . . . . . . . . . . . . . . . . . . . . . . . . 3725. LINKAIX connectionAdvanced options . . . . . . . . . . . . . . . . . . . . . . 3826. CICSESA partner LUBasic options . . . . . . . . . . . . . . . . . . . . . . . 3927. CICSMVS partner LUBasic options . . . . . . . . . . . . . . . . . . . . . . . 4028. CICSAIX partner LUBasic options . . . . . . . . . . . . . . . . . . . . . . . . 4129. CICSNT02 local LU definitionBasic options . . . . . . . . . . . . . . . . . . . . 42

30. CICSNT02 local LU definitionAdvanced options. . . . . . . . . . . . . . . . . . . 4331. CICSWINT local LU definitionBasic options . . . . . . . . . . . . . . . . . . . . 4432. CICSWINT local LU definitionAdvanced options . . . . . . . . . . . . . . . . . . 4533. CICSISC0Basic options . . . . . . . . . . . . . . . . . . . . . . . . . . . 4634. CICSISC0Advanced options . . . . . . . . . . . . . . . . . . . . . . . . . . 4735. CICS and Communications Server definitions when using a PPC Gateway server . . . . . . . 4836. CICS and Communications Server definitions when using local SNA support . . . . . . . . . 4937. Output of CEDA EXPAND GROUP command . . . . . . . . . . . . . . . . . . . . 5038. CEDA showing connection definition (CICSESA) . . . . . . . . . . . . . . . . . . . 5039. CEDA showing session definition (CICSESA) . . . . . . . . . . . . . . . . . . . . 5140. Output of CEDA EXPAND GROUP command . . . . . . . . . . . . . . . . . . . . 5241. CEDA showing connection definition (CICSMVS) . . . . . . . . . . . . . . . . . . . 5242. CEDA showing session definition (CICSMVS) . . . . . . . . . . . . . . . . . . . . 53

43. Example of a node profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 5444. Example of an SNA define_trusted_groups profile. . . . . . . . . . . . . . . . . . . 5445. Example of a local LU definition profile for LU CICSAIX . . . . . . . . . . . . . . . . 5546. Example of a side information profile for CICSAIX . . . . . . . . . . . . . . . . . . 5547. Example remote system profile for CICSWINT . . . . . . . . . . . . . . . . . . . . 5548. Example of a local transaction program profile for a region . . . . . . . . . . . . . . . 5649. Example of a modegroup profile for CICSISC0 . . . . . . . . . . . . . . . . . . . . 5650. Region Definitions (RD) attributes used for intercommunication for CICSAIX . . . . . . . . . 5651. Listener Definitions (LD) attributes . . . . . . . . . . . . . . . . . . . . . . . . 5752. Communications Definitions (CD) attributes for connection LINKAIX . . . . . . . . . . . . 5753. VTAM physical unit (PU) macro definition . . . . . . . . . . . . . . . . . . . . . . 59

Copyright IBM Corp. 1999, 2008 v

||


8/101

54. VTAM PATH definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6055. VTAM logical unit (LU) definition . . . . . . . . . . . . . . . . . . . . . . . . . 6056. VTAM mode table macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6157. SNA Node Operations application. . . . . . . . . . . . . . . . . . . . . . . . . 6458. The node is running. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6659. Starting a connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6760. LINKVTAM in Pending Active state . . . . . . . . . . . . . . . . . . . . . . . . 68

61. Setting the number of sessions . . . . . . . . . . . . . . . . . . . . . . . . . 7062. The Log Viewer application . . . . . . . . . . . . . . . . . . . . . . . . . . . 7363. Display SNA Sense Data panel . . . . . . . . . . . . . . . . . . . . . . . . . 7464. The Trace Facility application . . . . . . . . . . . . . . . . . . . . . . . . . . 7565. Selecting APPC tracetrace inactive . . . . . . . . . . . . . . . . . . . . . . . 7566. Selecting connectivity tracetrace active . . . . . . . . . . . . . . . . . . . . . . 76

vi TXSeries for Multiplatforms: Using IBM Communications Server for Windows Systems with CICS


9/101

Tables

1. Getting started road map . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix2. Conventions that are used in this book . . . . . . . . . . . . . . . . . . . . . . . x3. Information required to describe an example local Windows machine . . . . . . . . . . . . 74. Information required to define example links . . . . . . . . . . . . . . . . . . . . . 95. Information required to define example remote CICS regions . . . . . . . . . . . . . . 106. Information required to define example local systems . . . . . . . . . . . . . . . . . 117. Information required to define example modegroups . . . . . . . . . . . . . . . . . . 128. Information required to configure an example local Windows machine . . . . . . . . . . . 169. Information required to configure example links. . . . . . . . . . . . . . . . . . . . 1810. Information required to configure example remote systems . . . . . . . . . . . . . . . 2411. Relationship between conversation security support and RemoteSysSecurity. . . . . . . . . 2612. Information required to configure an example local system . . . . . . . . . . . . . . . 2713. Information required to configure example modenames. . . . . . . . . . . . . . . . . 30

Copyright IBM Corp. 1999, 2008 vii


10/101

viii TXSeries for Multiplatforms: Using IBM Communications Server for Windows Systems with CICS


11/101


12/101

Conventions used in this book

TXSeries for Multiplatforms documentation uses the following typographical andkeying conventions.

Table2. Conventions thatare 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 IBM Communications Server for Windows Systems with CICS


13/101

Table2. Conventions thatare used in thisbook (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, IBMmainframe-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 [email protected]. Be sure to include the name of the book, the documentnumber of the book, the version of TXSeries, and, if applicable, the specific locationof the information you are commenting on (for example, a page number or tablenumber).

About this book xi


14/101


15/101

Chapter 1. Introduction to IBM Communications Server forWindows 2003

The Communications Server is a comprehensive networking product that enablescommunications among many types of devices across a number of network

protocols. CICS uses the Advanced Program-to-Program Communications (APPC)part of this product to connect to a Systems Network Architecture (SNA) network.Connections can exist with or without Advanced Peer-to-Peer Networking (APPN)support.

IBMCommunicationsServer forWindows2003:QuickBeginningsexplains how toinstall Communications Server. The product must be installed on the sameWindows machine as is your CICS region or regions if you are using local SNA, oron the same Windows machine as is your Peer-to-Peer Communications (PPC)Gateway server if you are using a PPC gateway. If your machine will becommunicating over a Local Area Network (LAN), you must select the IEEE 802.2IBM LLC2 protocol interface during installation.

The installation adds several applications to your Windows system. The applicationsthat are useful when you are using Communications Server with CICS are:

SNA Node Configuration

This application creates the SNA configuration that describes how CICSconnects to the SNA network and to the systems with which itcommunicates. The applications graphical user interface (GUI) andsupplied defaults let you easily configure while using a minimum number ofparameters. An automatic verification program examines your configuration,alerts you to any errors and, if no conflicts exist, creates the requiredconfiguration files.

SNA Node Operations

This application allows you to view graphically the status of your SNA

network to determine with which systems the Communications Server iscommunicating. It also lets you connect to, and disconnect from, othersystems in the network. You can also perform system administrationthrough the supplied Tivoli Management Environment (TME) Module andWeb administration interface; see the IBMCommunicationsServer forWindows2003:NetworkAdministrationGuide for more information.

Log Viewer

This application lets you view the messages and return codes thatCommunications Server produces.

Display SNA Sense Data

This application lets you quickly look up and display SNA sense codedescriptions.

Trace Facility

This application gathers additional information to help diagnose SNAnetwork problems.

When you have installed Communications Server and rebooted your machine, youmust configure the product. If you are familiar with SNA terminology, go toChapter 3, Collecting information for a new SNA configuration, on page 7.Otherwise, review Chapter 2, Introduction to SNA, on page 3, which explains thecommon SNA concepts that you will encounter during product configuration.

Copyright IBM Corp. 1999, 2008 1


16/101

2 TXSeries for Multiplatforms: Using IBM Communications Server for Windows Systems with CICS


17/101

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 concepts andterminology when you use the CICS 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 1 shows a heterogeneous network with a CICS for Windows NT 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 configuring your CICS region to communicate with another CICS system, youmust understand the SNA product that the other system uses. Although the twosystems must agree on common parameters, the terminology for these parameterscan differ.

Figure1. Anexampleheterogeneousnetwork



18/101

SNA configuration

CICS systems can be connected 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 are tocommunicate.

v The physical level, which incorporates the linking of actual machines that are inthe network.

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.

Connection at the logical levelLogicalUnit (LU) is an SNA term that describes a logical collection of services thatcan be accessed from a network. SNA defines many different types of LUs,including devices such as terminals and printers. A CICS region can be an LU. Thetype of LU that is used for CICS intersystem communication is LU type6.2.

Each LU is identified by a name of up to eight characters, which is referred to asthe LUname. The LU name that describes the local region is called the local LU.LUs that describe remote systems are called partnerLUs. An IBM mainframe-basedCICS system uses as its LU name (also referred to as a NETNAME), the APPLIDthat is defined in the CICS system initialization table. The LU name for a CICSOS/2 system is specified in the Communications Manager/2 local LU definition, andthe LU name for a CICS/400 system is defined in the APPL parameter of theADDCICSSIT command.

An SNA network also has a name of up to eight characters, which is called thenetworkname. The network name is sometimes referred to as the network IDor the

netid. An LU can be uniquely identified by combining its LU name with the networkname of the network that owns it. The LUs name is then referred to as thenetwork-qualifiedLUnameor the fully qualifiedLUname. For example, if an LUnamed CICSA belongs to a network named NETWORK1, its network-qualified LUname is NETWORK1.CICSA.

For an LU to communicate with another LU, it must establish at least one sessionbetween them. The request to activate a session is referred to as a BIND request. Itis used to pass details of the capabilities of the initiating LU to the receiving system,and also to determine a route through the network. The receiving LU then sends adescription of its capabilities to the initiating LU in the BINDresponse. After thesession is established, it can be used for several intersystem requests and remainsactive for as long as the two LUs and the network between them are available.

When you configure your network, you can set up different characteristics for thesessions that are established between a pair of LUs, such as for the routes thatthey take through the network. The set of characteristics for a session is referred toas a modegroupor mode. All the sessions that are associated with a modegrouphave the same characteristics. A modegroup is identified by a modenameof up toeight characters.

When defining a CICS region, you must also identify the SNA synchronization levelthat is required. CICS supports all three synchronization levels that are defined bySNA:



19/101

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.

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 are made

by an application on these systems.

Connection at the physical levelEach actual machine in a network is described as a node. Assigned to it is a uniqueControlPoint (CP)name (the name that the network uses to communicate with it).Associated with the CP name is the node identifier (also referred to as theexchange identifieror XID), which identifies the physical unit (PU) that is associatedwith the CP. Each node has physical links, or connections, to other nodes so thatevery node is connected to at least one other node. Data must sometimes travelalong several links to get from one system to another. These links can be ofdifferent types. For example, IBM Token Ring, Synchronous Data Link Control(SDLC), Ethernet, and X.25 are all physical links. These types of links arecollectively referred to as data link control (DLC)protocols.

Each node has a PhysicalUnit (PU). This 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 type5: 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.

v PU type4: This is a communications controller, such as an AdvancedCommunications Function for the Network Control Program (ACF/NCP), thatresides in the center of a network, and routes and controls the data flow betweenmachines.

v PU type2: This is a small machine, such as an Advanced Program-to-Program

Communications (APPC) workstation. It can communicate directly only with a PUtype 4 or PU type 5, and relies on these PUs to route the data to the correctsystem.

v PU type2.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 independentLU. Anindependent LU can establish a session with another LU without using VTAM.Communications Server 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 LUs location locally. APPN nodes are of two types:endnodesand networknodes. An end node can receive a search request for an

LU, respond, and indicate whether the LU is local to the node or not. A networknode can issue search requests, and respond to them. Also, it maintains a dynamicdatabase that contains the results of the search requests. Support for APPN cangreatly reduce the maintenance work in an SNA network, especially if the network islarge or dynamic. Communications Server supports APPN.

Communicating across SNA connections

CICS regions can communicate across SNA with any system that supports APPC.Two methods of communication exist:

Chapter 2. Introduction to SNA 5


20/101

v Local SNA support gives your CICS regions support for synchronization levels 0and 1, and provides the fastest SNA connectivity that CICS offers. It enablesCICS applications to communicate with every other member of the CICS family,and enables IBM CICS Universal Clients to use SNA to communicate with CICS.For you to use local SNA support, SNA must be installed and configured on thesame machine as is the CICS region.

v Communication through a Peer-to-Peer Communications (PPC) Gateway server

provides synchronization level 2 support. This enables applications to ship oraccept transactions from other systems that use LU 6.2, such as IBMmainframe-based CICS, CICS OS/2, and CICS/400. SNA must be on the samemachine as is the gateway.



21/101

Chapter 3. Collecting information for a new SNA configuration

This following sections describe the information that you need in order to configureCommunications Server. It is practical to collect this information before starting tocreate the Systems Network Architecture (SNA) definitions.

The steps that follow include:1. Collecting information about the local Windows machine2. Collecting information about remote machines on page 83. Collecting information about remote systems on page 104. Collecting information about local CICS regions on page 105. Collecting information about modegroups on page 11

Collecting information about the local Windows machine

This section describes the information that you need in order to register theWindows machine that is running Communications Server with the SNA network.

Your physical machine is referred to as an SNA node. You must assign to it aControl Point (CP) name (the name that the network uses to communicate with it).This CP name can have one through eight characters that consist of uppercaseletters (A through Z) and numbers (0 through 9). It must be unique within the SNAnetwork. It must be different from:v All other CP names in the networkv All other Logical Unit (LU) names in the network

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

Associated with the CP name is the node identifier (also referred to as the

exchange identifier or XID). This eight-digit number, usually beginning with 05D onWindows systems, identifies the Physical Unit (PU) that is associated with thecontrol point.

You also need to know the name of the SNA network to which your SNA machineand all the CICS regions that use it belongs. The SNA network name can have onethrough eight characters that consist of uppercase letters (A through Z) andnumbers (0 through 9).

Table 3 shows the information that is required to describe an example localWindows machine.

Table3. Informationrequired todescribean example localWindowsmachine

CP name Node identifier Local networkname

NT000127 05D98765 MYSNANET

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



22/101

Collecting information about remote machines

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

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

your local CICS region is to communicate. You also need to know on whichmachines these systems are running, and how those machines are connectedtogether. It is often helpful to draw a schematic diagram of the network, such asthat which is shown in Figure 2.

In this example, the CICS region called CICSWINT communicates with anotherregion, CICSAIX, that is running on a machine that is connected to the same localarea network (LAN). Region CICSWINT also communicates with two mainframeCICS regions, CICSESA and CICSMVS. The CICSESA region is on a machine thatis connected to the same LAN as is CICSWINT. However, CICSMVS can becontacted only through another machine. This distinction is important. When youdefine your connections to Communications Server, you need to include only thosemachines that can be contacted directly (in this example, the machines that arerunning CICSAIX and CICSESA). Connections to other machines (in this example,

the machine that is running CICSMVS) are set up in definitions in the intermediatemachines. As a result, you need to consult the owners of those intermediatemachines to arrange the appropriate configurations.

When you have determined to which machines you want to connect, assign a nameto each connection. Choose meaningful names of up to eight characters, thatconsist of uppercase letters (A through Z) and numbers (0 through 9), to help youidentify the machines that are at the remote end of the connections. (Theseconnection names appear on the SNA Node Operations application window, andyou use them to start and stop connections. The more meaningful the names, theeasier is your network management.)

Figure2. Anexampleschematicdiagramof aheterogeneousnetwork



23/101


24/101

Collecting information about remote systems

This section describes the information that you need in order to know about theremote systems with which your CICS regions are going to communicate. Theseremote systems 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/2or CICS on OpenSystems region is specified in its local SNA products local LU definition. The LUname for a CICS for OS/400 region is in the APPL parameter of theADDCICSSIT command.

v The name of the SNA network to which it belongs. A SNA network name canhave one through eight characters that consist of uppercase letters (A through Z)and numbers (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 is

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

Note: When you have defined and activated a link to a particular remotemachine, Communications Server displays the CP name of this machine.

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

Table 5 shows data collected for three remote CICS systems. Conversation-levelsecurity is expressed in terms of the CICS Communications Definitions (CD)

RemoteSysSecurity attribute.Table5. Informationrequired todefineexample remoteCICS regions

Partner LU name Networkname Partner CP nameCICS CD

RemoteSysSecurity

CICSESA MYSNANET MYSNANET.MYVTAM trusted

CICSMVS MYSNANET MYSNANET.MYVTAM trusted

CICSAIX MYSNANET MYSNANET.AIX00005 trusted

Collecting information about local CICS regions

This section describes the information that you need in order to configure a localCICS region to communicate with a remote region or regions. For each local CICSregion, you need to:

v Know the local LU names for the region. Each region needs:

A local LU name for local SNA, if local SNA support is being used.

A local LU name for each PPC Gateway server, if PPC gateways are beingused.

For example, if your region uses only local SNA, it requires only one local LUname. If your region uses PPC Gateway servers, it requires one local LU name



25/101

for each PPC Gateway server. If you are using local SNA and two PPC Gatewayservers, you need three local LU names: one for local SNA and one for eachPPC Gateway server.

An LU name can have one through eight characters that consist of uppercaseletters (A through Z) and numbers (0 through 9). All the LU names that youchoose must be unique within your network. Many networks have namingconventions that help to prevent name clashes. Consult your network

administrator for advice when choosing LU names.

v Identify which of the modenames to use as a default when the region does notexplicitly specify a modename on an intersystem request. You can specify amodename explicitly on an intersystem request by using the SNAModeNameattribute of the CICS Transaction Definitions (TD), or by using the PROFILEoption of the EXEC CICS ALLOCATE command. Alternatively, you can specify amodename in the DefaultSNAModeName attribute of the CICS CommunicationsDefinitions (CD) entry. This modename is used if you do not specify a modenameexplicitly in the TD entry or in the EXEC CICS command. Identification of thisparameter is described further in the TXSeries forMultiplatformsIntercommunicationGuide.

v Decide, for each LU name, whether synchronization level 2 is required. You can

use synchronization level 2 only if the LU name is for a PPC Gateway server thatis used to communicate with systems that support synchronization level 2, suchas CICS Transaction Server for z/OS and CICS for VSE/ESA. Furtherinformation about synchronization level 2 and about using a PPC Gateway servercan be found in the TXSeries forMultiplatformsIntercommunicationGuide.

Table 6 shows LU names for the CICS region CICSWINT. Region CICSWINT isusing LU name CICSWINT for a local SNA connection, and LU name CICSNT02 fora PPC Gateway server connection. The default modename for these LU names isCICSISC0.

Table6. Informationrequired todefineexample local systems

Region name Local LU name Synchronization level 2?

CICSWINT CICSWINT No

CICSWINT CICSNT02 Yes

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 CICSsystems and remote SNA systems.

A modegroup defines the number of sessions that are allowed on a connectionbetween two systems. Each session allows only one CICS intersystem request to

run 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 througheight characters long that consist of uppercase letters (A through Z) and numbers (0through 9).

You must define at least one modegroup to the Communications Server. SNAconnections can share modegroup definitions. The session limits that are defined ina modegroup apply independently to each connection that uses that modegroup. A

Chapter 3. Collecting information for a new SNA configuration 11


26/101

connection 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. Simply define twomodegroups: one for the interactive requests (called modename CICSISC0), andthe other for the slower data transfer requests (called modename CICSISC1).

A modegroup also defines the characteristics of the sessions that belong to a

connection. The most important of these is contention. For each session betweentwo systems, one system is the contentionwinner, 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 ofcontention-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 Communications Server usesVTAM to communicate with the remote system, you must include a MODEENTdefinition for the modename in its tables. (Chapter 6, Configuring VTAM with detailsof your CICS region, on page 59 has an example of a MODEENT definition.)

Table7. Informationrequired todefineexamplemodegroups

Modename Max sessions Min winners

CICSISC0 10 5

CICSISC1 4 2

System-defined SNASVCMG and CPSVCMG modegroupsSNA network connections that are using parallel sessions have a standardmodegroup called SNASVCMG. This is a system-defined modegroup that isreserved for use by SNA management programs. Do not attempt to define thismodegroup in Communications Server 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/101

Chapter 4. Creating a Communications Server configuration

The following sections describe how to configure Communications Server. Ensurethat you have read Chapter 3, Collecting information for a new SNA configuration,on page 7 and have all the information that you need about the systems that youwant to connect across a Systems Network Architecture (SNA) network.

Communications Server is configured by using the SNA Node Configurationapplication, which you can start by selecting

Start Programs

IBM Communications Server SNA Node Configuration

How to use this application is described in the following sections:

v Choosing a configuration scenario describes how to choose a configurationscenario.

v

Configuring the local Windows machine (node) on page 16 describes how todefine your machine to the SNA network.

v Configuring links on page 18 describes how to set up links to other machines inthe SNA network.

v Configuring remote systems on page 24 describes how to define the remotesystems with which your CICS region is to communicate.

v Configuring your CICS region on page 27 describes how to define your localCICS region to the SNA network.

v Configuring modenames on page 29 describes how to set up modegroups.

v Completing the Communications Server configuration on page 31 describes thefinal steps that are needed to complete your Communications Serverconfiguration.

The examples that follow are not designed to cover every aspect of configuringCommunications Server. Only those fields that are particularly relevant to CICS arediscussed. Using default values works well for many other fields. If you requiremore information, you can see a description of each field by selecting the Helpbutton on the configuration window where the field appears.

Choosing a configuration scenario

The first step in creating a Communications Server configuration is to choose aconfiguration scenario. To do this:

1. Start the SNA Node Configuration application.

2. On the first panel that appears, click New.3. Click Next.

The panel that is shown in Figure 4 on page 14 is displayed.



28/101

Communications Server simplifies configuration of SNA nodes and associatedresources by offering you several scenarios. Choose a configuration scenariofrom the list that best describes how you will use Communications Server. Bychoosing a scenario, you reduce the number of SNA configuration options thatyou see on the SNA Node Configuration main panel. (That is, only the tasksand definitions that must be completed for your scenario are displayed in theresulting panel.) Alternatively, you can view and set all SNA configurationoptions by checking the Advanced check box.

This example configures an Advanced Peer-to-Peer Networking (APPN) networknode.

4. Click APPN NetworkNode on the list in the Choose a Configuration Scenariopanel.

5. Click Finish.

The panel shown in Figure 5 on page 15 is displayed.

Figure4. ChooseaConfigurationScenariopanel



29/101

The Follow these steps pane on the left (which will be referred to as the Stepspane throughout this document) shows the required and optional steps that youperform to create an APPN network node. Required steps are marked with anasterisk. A step is accessed by clicking the running-person icon beside it. Clickingthe question mark beside a step brings up an online tutorial with useful informationabout it. As you complete each step, a check mark appears beside it, and an arrowpoints to the next configuration step.

The Definition Hierarchy by Function pane on the right (which will be referred toas the Definition Hierarchy pane throughout this document) shows, through a

logical tree-view, the SNA definitions that are particular to your scenario and therelationships between them. To expand a parent definition and show all its childdefinitions, click the plus sign (+); to hide an expanded definition, click the minussign (-). When you create definitions by following the configuration steps on theSteps pane, check marks appear in the boxes beside entries in the DefinitionHierarchy pane, to give you the state of your configuration at a glance. Theexisting check mark beside the CPI-C and APPC entry reflects that someconfiguration information for this definition has been automatically generated fromthe local control point, possibly eliminating the need for manual configuration ofthose parameters.

Figure5. SNA NodeConfigurationpanel

Chapter 4. Creating a Communications Server configuration 15


30/101

Configuring the local Windows machine (node)

This section describes how to use the SNA Node Configuration application todefine your local machine to SNA. It uses the values that are shown in Table 8 inan example local machine configuration.

Table8. Informationrequired to configurean example localWindowsmachine

CP name Node identifier Local networkname

NT000127 05D98765 MYSNANET

To configure the node:

1. Click the running-person icon that is beside Networknode setup in the Stepspane of the SNA Node Configuration main panel, which is shown in Figure 5 onpage 15. The Define the Node panel appears.

2. Under Fully qualified CP name, enter the SNA network name in the first boxand the CP name in the second.

3. Enter the CP name under CP alias.

4. Enter the first three characters of the node identifier (XID) under Block ID, andthe remaining characters under Physical Unit ID.

5. Select the node type for the node that you are defining. In addition to End Nodeand NetworkNode choices, Communications Server offers a Branch ExtenderNode option. This option divides large networks into smaller, more manageablesubnetworks by letting you define a network node in such a way that the APPNbackbone network views it and its connected end nodes or subordinate branchextender nodes as a single end node. For this example, select the NetworkNode option. Your screen now appears as shown in Figure 6 on page 17.



31/101


32/101

Completion check marks appear beside Networknode setup in the Steps paneand Node in the Definition Hierarchy pane. An arrow points to the next requiredconfiguration step, Device configuration, in the Steps pane.

Configuring links

This section describes how to define links to other machines in the SNA network. Ituses the values in Table 9 in an example configuration.

Table9. Informationrequired to configureexample links

Connectionname

Link type Remote hardwareaddress

Remote CPname

Networkname

Remotenode

identifier

LINKVTAM IBM TokenRing

400012345678 MYVTAM MYSNANET 04300007

LINKAIX IBM TokenRing

10005A4B3C2D AIX00005 MYSNANET 07101234

Figure7. SNA NodeConfigurationpanelwithaddednode



33/101


34/101

Note: If the value for Adapter number is blank (not 0), either you have notinstalled a DLC device driver, or you have not rebooted your machinesince the installation. To install the LLC2 Protocol DLC device driver thatcan be used for the LAN, switch to the directory where CommunicationsServer is installed and run one of the following:v INLLC35.HLP (for Windows NT3.51 systems)v INLLC40.HLP (for Windows NT 4.0 systems)v INLLC50.HLP (for Windows 2000 systems)

A window appears that explains how to add the device.

4. Click OK and the device is added. To view it, in the Definition Hierarchy pane,click the plus sign (+) that is beside the Devices entry, then click the plus signthat is beside LAN. Your screen now appears as shown in Figure 10 on page21.

Figure9. Definea LANDevicepanel



35/101

Completion check marks appear beside Device configuration in the Steps paneand Devices in the Definition Hierarchy pane. Because the remainder of theconfiguration steps are optional, no arrow appears beside Peer connectionconfiguration in the Steps pane.

Configuring peer connections

After you have a DLC device driver, you can connect your machine to othermachines by using peer connection definitions. To configure a peer connection toanother machine:

1. Click the running-person icon that is beside Peer connection configuration inthe Steps pane of the SNA Node Configuration main panel, which is shown inFigure 10. The Define a LAN Connection panel appears.

2. Enter a value for Linkstation name (for example, LINKVTAM).

3. Enter the remote machine address for Destination address. Your screen nowappears as shown in Figure 11 on page 22.

Figure10. SNA NodeConfigurationpanelwithaddedLANdevice



36/101

4. If the remote machine does not support APPN, select the Advanced tab.Deselect APPN support by clearing the check box that is beside it. (APPNsupport is selected by default). Your screen now appears as shown in Figure 12on page 23.

Figure11. Definea LANConnectionpanelBasicoptions



37/101

You can also configure information about the remote system node and linkreactivation parameters on the Adjacent Node and Reactivation tabs. If you donot define these parameters, the default values are used.

5. When you have completed entering information, click OK, and the linkLINKVTAM is added.

6. Follow similar steps to configure the link LINKAIX. (However, because LINKAIXdoes support APPN, leave the APPN support check box checked on the Definea LAN ConnectionAdvanced options panel.)

7. To view the new links, in the Definition Hierarchy pane, click the plus sign (+)

that is beside the Peer Connections entry, then click the plus sign that isbeside LAN. Your screen now appears as shown in Figure 13 on page 24.

Figure12. Definea LANConnectionpanelAdvancedoptions



38/101

Completion check marks appear beside Peer connection configuration in theSteps pane and Peer Connections in the Definition Hierarchy pane. Notice thatthe CPI-C and APPC definition automatically expanded to show the check markbeside Peer Connections. Check marks also appear beside Modes andTransaction Programs to reflect that application-generated entries exist for thesedefinitions.

Configuring remote systems

This section describes how to define the remote systems with which your CICSregion communicates across the SNA network. It uses the values that are given inTable 10 in an example configuration.

Table10. Informationrequired to configureexample remotesystems

Partner LU

name

Networkname Partner CP name CICS CD

RemoteSysSecurity

CICSESA MYSNANET MYSNANET.MYVTAM trusted

CICSMVS MYSNANET MYSNANET.MYVTAM trusted

CICSAIX MYSNANET MYSNANET.AIX00005 trusted

Figure13. SNA NodeConfigurationpanelwithaddedLINKVTAMandLINKAIXconnections



39/101

To configure a partner LU:

1. Click the running-person icon that is beside Partner LU 6.2 configuration inthe Steps pane of the SNA Node Configuration main panel, which is shown inFigure 13 on page 24. The Define a Partner LU 6.2 panel appears.

2. Enter the fully qualified partner LU name (for example, MYSNANET.CICSESA)under Partner LU name. For this example, verify that the Wildcard check boxis cleared. When checked, this option appends an asterisk to the partner LUname, and lets you easily locate all partner LUs that have names that match thewildcard.

3. Enter the partner LU alias (CICSESA) under Partner LU alias.

4. Click the New radio button to indicate that this is a new fully qualified controlpoint (CP) name.

5. Enter the fully qualified CP name of the remote machine(MYSNANET.MYVTAM) under Fully qualified CP name. Your screen nowappears as shown in Figure 14.

Figure14. DefineaPartnerLU6.2panel



40/101

6. Click the Advanced tab. The value for Conversation security support mustbe consistent with the value of the CICS Communications Definitions (CD)RemoteSysSecurity attribute, as shown in Table 11.

Table11. Relationshipbetweenconversationsecurity supportandRemoteSysSecurity

Conversation security support CICS CD RemoteSysSecurity

Not selected local or verify

Selected trusted

For more information about security parameters, refer to the TXSeries forMultiplatformsIntercommunicationGuide.

For this example, both Conversation security support and Parallel sessionsupport must be selected (show a check mark beside them). (Selected is thedefault value for both.) Accept the default value of 32767 for Maximum LLrecord size, which is the maximum size of the logical record in the data streamfor basic conversations.

7. Click OK, and the partner LU is added.

8. Follow similar steps to configure the CICSMVS and CICSAIX partner LUs.

9. To view the new partner LUs, in the Definition Hierarchy pane, click the plussign (+) that is beside the Partner LU 6.2 LUs entry. Your screen now appearsas shown in Figure 15 on page 27.



41/101

Completion check marks appear beside Partner LU 6.2 configuration in the Stepspane and Partner LU 6.2 LUs in the Definition Hierarchy pane.

Note: Because you generally do not need to configure a connection network for aCICS system, skip the Connection networkconfiguration step that is listedin the Steps pane.

Configuring your CICS region

Although you are not prompted by this scenario to define unique local LU 6.2 LUs,you do need to define them to configure a CICS system. This section uses thevalues in Table 12 in an example configuration.

Table12. Informationrequired to configurean example local system

Region name Local LU name Synchronization level 2?

CICSWINT CICSWINT No

CICSWINT CICSNT02 Yes

Figure15. SNA NodeConfigurationpanelwithaddedpartnerLUs



42/101


43/101

which means no limit. Because you are defining a PPC Gateway serverconnection, check the Synchronization support check box.

10. Click OK, and the local LU is added to the configuration.

11. To view the CICSWINT and CICSNT02 local LU entries, in the DefinitionHierarchy pane, click the plus sign (+) beside the Local LU 6.2 LUs entry.Your screen now appears as shown in Figure 17. A completion check mark

appears beside Local LU 6.2 LUs in the Definition Hierarchy pane.

Configuring modenames

Communications Server provides several SNA mode definitions for use both bysystem and by user Advanced Program-to-Program Communications (APPC)sessions. However, you usually need to define modes with specific modenames orcharacteristics for use with CICS. Because this example uses the modenamesCICSISC0 and CICSISC1, those modenames must be defined.

Figure17. SNA NodeConfigurationpanelwithaddedLocalLU6.2s



44/101

This section uses the values that are given in Table 13 in an example configuration.

Table13. Informationrequired to configureexamplemodenames

Modename Max sessions Min winners

CICSISC0 10 5

CICSISC1 4 2

To create a new mode:

1. From the SNA Node Configuration main panel that is shown in Figure 17 onpage 29, scroll down the Definition Hierarchy pane until the entry Modesappears. Double-click Modes. The Define a Mode screen appears.

2. Enter CICSISC0 in the Modename box.

3. Enter 10 in the PLU mode session limit box.

4. Enter 5 in the Minimum contention winner sessions box. (This value must beat least 1, and is recommended to be about half of the value that is in PLUmode session limit.) Your screen now appears as shown in Figure 18.

Figure18. DefineaMode panel



45/101

5. You can use the fields under the Advanced tab to change the performancecharacteristics of the sessions that belong to the mode. For example, to activatesome of your sessions on startup automatically, you can enter the number thatare to be activated in the Auto activate sessions field. The default values aregenerally enough for an initial configuration. However, you can achieve betterperformance by matching these values to those that are defined in the remoteLU. For this example, accept the default values for the fields on the Advanced

tab. Click OK, and mode CICSISC0 is added to the configuration.6. Follow similar steps to configure mode CICSISC1.

7. The new modes appear under Modes in the Definition Hierarchy pane. TheSNA Node Configuration panel now appears as shown in Figure 19.

Completing the Communications Server configuration

When you have completed making changes to your configuration, follow thesesteps to complete it:

1. In the SNA Node Configuration main panel shown in Figure 19, click Finish.

Figure19. SNA NodeConfigurationpanelwithaddedmodes



46/101

2. A message box is displayed, informing you that you are to be prompted for afilename. Click OK.

3. In the dialog box that appears, indicate your chosen name for the configurationfile and the directory in which you want to store it. Click Save.

4. In the dialog box that appears, indicate whether you want the new configurationto be used as the default by clicking Yes or No.

5. In the dialog box that appears, indicate whether you want to start the node. Ifyou choose:

v Yes, see Chapter 7, Operating Communications Server, on page 63 forinformation about how to use the SNA Node Operations application.

v No, click Exit on the File menu.

After configuring Communications Server, you must configure the CICScommunications resources. Some of the arguments that you use when configuringCICS must match those that you have used to configure Communications Server.See Example CICS for Windows systems configurations on page 47 for examplesof the parameters that must match. More detailed information is given in theTXSeries forMultiplatformsIntercommunicationGuide.



47/101

Chapter 5. Example Communications Server configurationprofiles

The following sections provide examples of Systems Network Architecture (SNA)profiles that connect a CICS region named CICSWINT on Windows to a CICS for

VSE/ESA region named CICSESA, a CICS for MVS/ESA

region namedCICSMVS, and a CICS on Open Systems region named CICSAIX. The partner LUname for the CICS for VSE/ESA region CICSESA is CICSESA. The partner LUname for the CICS for MVS/ESA region named CICSMVS is CICSMVS. Thepartner LU name for the CICS on Open Systems region named CICSAIX isCICSAIX. This configuration is represented in Figure 20.

The connections to regions CICSESA and CICSMVS are through a Peer-to-PeerCommunications (PPC) Gateway server. They use synchronization level 2 and alocal LU of CICSNT02. The connection to region CICSAIX uses local SNA support,a synchronization level of 1, and a local LU of CICSWINT.

The profiles are shown as follows:

v Example SNA definitions for IBM Communications Server for Windows on page34

v Example CICS for Windows systems configurations on page 47

v Example CICS for VSE/ESA SNA profiles on page 49

Figure20. Networkused to showexampleSNA profiles



48/101

v Example CICS for MVS/ESA SNA profiles on page 51

v Example Communications Server for AIX profiles on page 53

v Example CICS on Open Systems SNA profiles on page 56

Example SNA definitions for IBM Communications Server for Windows

This section describes the example definitions that are required for CommunicationsServer for this example. Figure 21 shows the definition of the local machine.

This example has two connections to remote machines: LINKVTAM and LINKAIX.(Connections are defined only for machines that are directly connected. For moreinformation about which machines must be connected, refer to Collectinginformation about remote machines on page 8.)

Figure 22 on page 35 and Figure 23 on page 36 show the two configurationscreens that define the LINKVTAM connection.

Figure21. The localmachine



49/101

Figure22. LINKVTAMconnectionBasicoptions

Chapter 5. Example Communications Server configuration profiles 35


50/101

Figure 24 on page 37 and Figure 25 on page 38 show the two configurationscreens that define the LINKAIX connection.

Figure23. LINKVTAMconnectionAdvancedoptions



51/101


52/101

This example has three remote systems, so three partner LU definitions arerequired. Figure 26 on page 39, Figure 27 on page 40, and Figure 28 on page 41show the Basic options screens that define the CICSESA, CICSMVS, andCICSAIX remote systems, respectively. The Advanced options screen for eachshows the Conversation security support and Parallel session support checkboxes checked, and has the default value of 32767 for Maximum LL record size.

Figure25. LINKAIX connectionAdvancedoptions



53/101

Figure26. CICSESA partnerLUBasicoptions



54/101

Figure27. CICSMVS partnerLUBasicoptions



55/101

Local LU names are the SNA names for the local CICS region. Two LU names aredefined for CICS region CICSWINT:

v CICSNT02 for the PPC Gateway server connection to LINKVTAM, which isshown in Figure 29 on page 42 and Figure 30 on page 43. Notice that inFigure 30 on page 43, the check box that is beside Synchronization support ischecked, which indicates that this connection supports synchronization level 2.

v CICSWINT for the local SNA connection to LINKAIX, which is shown in Figure 31on page 44 and Figure 32 on page 45. Notice that in Figure 32 on page 45, thecheck box that is beside Synchronization support is not checked, which

indicates that this connection supports only synchronization levels 0 and 1.

Figure28. CICSAIX partnerLUBasicoptions



56/101

Figure29. CICSNT02 localLUdefinitionBasicoptions



57/101

Figure30. CICSNT02 localLUdefinitionAdvancedoptions



58/101

Figure31. CICSWINT localLUdefinitionBasicoptions



59/101

The modenames define the number and characteristics of the sessions betweentwo systems. Figure 33 on page 46 and Figure 34 on page 47 show theconfiguration screens that define the CICSISC0 modename.

Figure32. CICSWINTlocalLUdefinitionAdvancedoptions



60/101

Figure33. CICSISC0Basicoptions



61/101

Similar definitions exist for the CICSISC1 modegroup.

Example CICS for Windows systems configurations

After configuring Communications Server, you must configure the CICScommunications resources. This process is described in detail in the TXSeries forMultiplatformsIntercommunicationGuide. Some of the values that you specify whenconfiguring CICS must match those that you have used to configureCommunications Server. This section describes the values that must match.

The following diagrams show how Communications Server profiles relate to CICSdefinitions.

Note: CICS attribute names in these diagrams reflect CICS command namingconventions, rather than IBM TXSeries Administration Console namingconventions.

Figure 35 on page 48 shows a configuration that has CICS for Windows NT regionCICSWINT, which is using a local LU of CICSNT02, and a PPC Gateway server.The remote region is CICSESA. (For this example, similar definitions would have to

Figure34. CICSISC0Advancedoptions



62/101

be set up for region CICSMVS.)

Figure 36 on page 49 shows a configuration with CICS for Windows NT regionCICSWINT using a local LU of CICSWINT and local SNA support. The remoteregion is CICSAIX.

Figure35. CICSandCommunicationsServerdefinitionswhenusingaPPCGatewayserver



63/101

Example CICS for VSE/ESA SNA profiles

You can craete and view CICS for VSE/ESA definitions by using the CEDAtransaction. Figure 37 on page 50 shows the results of a CEDA EXPANDGROUP(WINT) command that was issued on the CICSESA system. It shows thedefinitions of a connection called WINT that have been set up in a CICS ResourceDefinition Online (RDO) group, which is also called WINT.

Figure36. CICSandCommunicationsServerdefinitionswhenusing localSNA support



64/101

Defining a connection from CICSESA to a remote system requires a CONNECTIONdefinition to describe the name and characteristics of the remote system and atleast one SESSIONS definition to define the modegroup (modename) that theconnection will use. This example has two SESSIONS definitions because thisparticular connection is using two modegroups.

Figure 38 shows the contents of the WINT CONNECTION definition. The name ofthe connection (WINT) is the SYSID that transactions use to communicate with theCICSNT02 LU.

Figure 39 on page 51 shows one of the SESSIONS definitions, WINT0, whichdescribes modegroup CICSISC0. The name that is defined in the Connection

EXPAND GROUP(WINT)ENTER COMMANDSNAME TYPE GROUP DATE TIMEWINT CONNECTION WINT 92.324 11.21.53WINT0 SESSIONS WINT 93.026 14.33.53WINT1 SESSIONS WINT 93.026 14.36.43

APPLID=CICSESARESULTS: 1 TO 3 OF 3 TIME: 11.46.31 DATE: 94.108

PF 1 HELP 3 END 6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL

Figure37. OutputofCEDA EXPANDGROUPcommand

OBJECT CHARACTERISTICS CICS RELEASE = 0330CEDA ViewConnection : WINTGroup : WINTDEscription : Connection to system CICSNT02CONNECTION IDENTIFIERSNetname : CICSNT02INDsys :REMOTE ATTRIBUTESREMOTESystem :REMOTEName :CONNECTION PROPERTIESACcessmethod : Vtam Vtam | IRc | INdirect | XmProtocol : Appc Appc | Lu61SInglesess : No No | YesDAtastream : User User | 3270 | SCs | STrfield | LmsRECordformat : U U | VbOPERATIONAL PROPERTIESAUtoconnect : Yes No | Yes | AllINService : Yes Yes | NoSECURITYSEcurityname :ATtachsec : Identify Local | Identify | Verify | Persistent

| MixidpeBINDPassword : PASSWORD SPECIFIEDBINDSecurity : Yes No | Yes

APPLID=CICSESA

PF 1 HELP 2 COM 3 END 6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL

Figure38. CEDA showingconnectiondefinition(CICSESA)



65/101

attribute is the name of the CONNECTION to which this SESSIONS definitionbelongs. The two values that are specified under MAximum (010 , 005) are themaximum number of sessions and maximum number of contention winners,respectively. These must be consistent with the values that are specified in theCommunications Server mode definition for this modegroup.

Example CICS for MVS/ESA SNA profilesYou can create and view CICS for MVS/ESA definitions by using the CEDAtransaction. Figure 40 on page 52 shows the results of a CEDA EXPANDGROUP(WINT) ALL(*) command that is issued on the CICSMVS system. It showsthe definitions of a connection called WINT that have been set up in a CICSResource Definition Online (RDO) group, which is also called WINT.

OBJECT CHARACTERISTICS CICS RELEASE = 0330CEDA ViewSessions : WINT0Group : WINTDEscription : Modegroup CICSISC0 for connection to CICSNT02

SESSION IDENTIFIERSConnection : WINTSESSName :NETnameq :MOdename : CICSISC0

SESSION PROPERTIESProtocol : Appc Appc | Lu61MAximum : 010 , 005 0-999RECEIVEPfx :RECEIVECount : 1-999SENDPfx :SENDCount : 1-999SENDSize : 04096 1-30720RECEIVESize : 01024 1-30720SESSPriority : 000 0-255Transaction :

OPERATOR DEFAULTSOPERId :OPERPriority : 000 0-255OPERRsl : 0 0-24,...OPERSecurity : 1 1-64,...

PRESET SECURITYUSERId :

OPERATIONAL PROPERTIESAutoconnect : Yes No | Yes | AllINservice : No | YesBuildchain : Yes Yes | NoUSERArealen : 000 0-255IOarealen : 00000 , 00000 0-32767RELreq : Yes No | YesDIscreq : Yes No | YesNEPclass : 000 0-255

RECOVERYRECOVOption : Sysdefault Sysdefault | Clearconv | Releasesess

| Uncondrel | NoneRECOVNotify : None None | Message | Transaction

APPLID=CICSESA

PF 1 HELP 2 COM 3 END 6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL

Figure39. CEDA showingsessiondefinition(CICSESA)



66/101

Defining a connection from CICSMVS to a remote system requires aCONNECTION definition to describe the name and characteristics of the remotesystem, and at least one SESSIONS definition to define the modegroup(modename) that the connection will use.

Figure 41 shows the contents of the WINT CONNECTION definition. The name ofthe connection (WINT) is the SYSID that transactions use to communicate with theCICSNT02 LU.

Figure 42 on page 53 shows the SESSIONS definition WINT0 that describesmodegroup CICSISC0. The name that is defined in the Connection attribute is thename of the CONNECTION to which this SESSIONS definition belongs. The twovalues that are specified under MAximum (00010 , 00005) are the maximumnumber of sessions and maximum number of contention winners, respectively.These must be consistent with the values that are specified in the CommunicationsServer mode definition for this modegroup.

EXPAND GROUP(WINT) ALL(*)ENTER COMMANDSNAME TYPE GROUP DATE TIMEWINT CONNECTION WINT 92.324 11.21.52WINT0 SESSIONS WINT 94.046 11.06.48

RESULTS: 1 TO 2 OF 2 TIME: 12.19.28 DATE: 94.108PF 1 HELP 3 END 6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL

Figure40. OutputofCEDA EXPANDGROUPcommand

OBJECT CHARACTERISTICSCEDA ViewConnection : WINTGroup : WINTCONNECTION IDENTIFIERSNetname : CICSNT02INDsys :CONNECTION PROPERTIES

ACcessmethod : Vtam Vtam | IRc | INdirect | XmProtocol : Appc Appc | Lu61SInglesess : No No | YesDatastream : User User | 3270 | SCs | STrfield | LmsRecordformat : U U | VbOPERATIONAL PROPERTIESAUtoconnect : Yes No | Yes | AllINService : Yes Yes | NoSECURITYSEcurityname :ATtachsec : Identify Local | Identify | VerifyBINDPassword : PASSWORD SPECIFIED


Figure41. CEDA showingconnectiondefinition(CICSMVS)



67/101

Example Communications Server for AIX profiles

The examples below show the profiles that are required for the CICS regionCICSAIX, which is using the local LU name CICSAIX, to communicate with CICSregion CICSWINT, which is using the LU name CICSWINT. These example profilesare always available in ASCII format in the sna_node.cfg, sna_domn.cfg, and

sna_tps files that are in the /etc/sna directory of the host machine.

Figure 43 on page 54 shows an example of a node profile. It describes theRS/6000 that is running Communications Server for AIX.

OBJECT CHARACTERISTICSCEDA ViewSessions : WINT0Group : WINT

SESSION IDENTIFIERSConnection : WINTSESSName :

NETnameq :MOdename : CICSISC0SESSION PROPERTIESProtocol : Appc Appc | Lu61MAximum : 00010 , 00005 0-32767RECEIVEPfx :RECEIVECount : No No | 1-999SENDPfx :SENDCount : No No | 1-999SENDSize : 04096 1-30720RECEIVESize : 01024 1-30720

OPERATOR DEFAULTSOPERId :OPERPriority : 000 0-255OPERRsl : 0 0-24,...OPERSecurity : 1 1-64,...USERId :

SESSION USAGESTransaction :SESSPriority : 000 0-255

OPERATIONAL PROPERTIESAutoconnect : Yes No | Yes | AllINservice : No | YesBuildchain : Yes Yes | NoUSERArealen : 000 0-255IOarealen : 00000 , 00000 0-32767RELreq : Yes No | YesDiscreq : Yes No | YesNEPclass : 000 0-255

RECOVERYRECOVOption : Sysdefault Sysdefault | Clearconv | Releasesess |

Uncondrel | NoneRECOVNotify : None None | Message | Transaction


Figure42. CEDA showingsessiondefinition(CICSMVS)



68/101

Figure 44 shows an example of the SNA define_trusted_groups profile. The cics

group identification number is in /etc/group.

Figure 45 on page 55 shows an example of the local LU definition CICSAIX for theCICS region CICSAIX.

[define_node]cp_alias = AIX00005description = ""fqcp_name = MYSNANET.AIX00005node_type = NETWORK_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 = YESpu_conc_support = YESnn_rar = 128max_ls_exception_events = 0ms_support = NORMALqueue_nmvts = NOptf_flags = NONE

Figure43. Exampleofa nodeprofile

[define_trusted_groups]group_id = 79

Figure44. ExampleofanSNA define_trusted_groupsprofile



69/101

The field synctpt_support = no indicates that the CICSAIX local LU is to be usedby local SNA. (This field instructs Communications Server for AIX to bind sessionsat synchronization level 1.)

Figure 46 shows an example of the side information profile that defines the defaultmodename for the LU.

Figure 47 defines the partner LU CICSWINT.

Figure 48 on page 56 shows an example of the local transaction program profilethat is created for all local CICS regions that are using this particular instance ofCommunications Server for AIX. The name of this profile (CICSTPN) is configuredin the TPNSNAProfile attribute of the regions Transaction Definitions (TD) entries.

[define_local_lu]lu_alias = CICSAIXlist_name = ""description = ""lu_name = CICSAIXlu_session_limit = 0pu_name = nau_address = 0

default_pool = NOsyncpt_support = NOlu_attributes = NONEsscp_id = 0disable = NOsys_name = ""timeout = 60back_level = YES

Figure45. Exampleof a localLUdefinitionprofile forLUCICSAIX

[define_cpic_side_info]sym_dest_name = CICSAIXdescription = ""lu_alias = CICSAIXpartner_lu_name = ""mode_name = CICSISC0tp_name_type = APPLICATION_TPtp_name = conversation_security_type = NONEsecurity_user_id = ""security_password = ""

Figure46. Exampleof a side informationprofile forCICSAIX

[define_partner_lu]plu_alias = CICSWINTdescription = ""fqplu_name = MYSNANET.CICSWINTplu_un_name = CICSWINTparallel_session_supp = YESappcip_routing_preference = USE_DEFAULT_PREFERENCEmax_mc_11_send_size = 0conv_security_ver = NO

Figure47. Exampleremotesystemprofile forCICSWINT



70/101

Figure 49 shows an example of a profile that describes the modegroup CICSISC0.

Example CICS on Open Systems SNA profiles

The examples that follow show the relevant parts of the files that contain theresource definitions for the CICS region CICSAIX. Figure 50 shows part of theRegion Definitions (RD) file that is named:

/var/cics_regions/cicsaix/database/RD/RD.stanza

In files that are similar to this one, you can see the values that are defined for theLocalSysId, LocalLUName, and LocalNetworkName at

txseries for multiplatforms using ibm communications server for windows systems with cics version...

Documents