txseries for multiplatforms using ibm communications server for aix with cics version 6.2

8/9/2019 TXSeries for Multiplatforms Using IBM Communications Server for AIX With CICS Version 6.2

1/75

TXSeries for Multiplatforms

Using IBM Communications Server for AIX with CICS

Version 6.2

SC34-6642-02


2/75


3/75

TXSeries for Multiplatforms

Using IBM Communications Server for AIX with CICS

Version 6.2

SC34-6642-02


4/75

Note

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

Third Edition (January 2008)

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

Contents

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

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

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

Chapter 1. Introduction to SNA. . . . . . . . . . . . . . . . . . . 1Communicating across SNA connections . . . . . . . . . . . . . . . . 3

Chapter 2. Configuring Communications Server for AIX for CICS

intercommunication . . . . . . . . . . . . . . . . . . . . . . 5Collecting information for a new Communications Server for AIX configuration 5The local machine (control point). . . . . . . . . . . . . . . . . . 5

Remote machines (nodes) . . . . . . . . . . . . . . . . . . . . 6Modegroups . . . . . . . . . . . . . . . . . . . . . . . . . 7Local CICS regions. . . . . . . . . . . . . . . . . . . . . . . 8Remote systems (Partner LUs) . . . . . . . . . . . . . . . . . . 8

Creating a Communications Server for AIX configuration . . . . . . . . . 10Node setup . . . . . . . . . . . . . . . . . . . . . . . . . 10Defining a profile for your CICS transactions . . . . . . . . . . . . . 11Defining modenames . . . . . . . . . . . . . . . . . . . . . 12Enabling CICS user IDs . . . . . . . . . . . . . . . . . . . . 13Defining a local CICS region . . . . . . . . . . . . . . . . . . . 13Defining your SNA partner LUs . . . . . . . . . . . . . . . . . . 15Backing up configuration profiles . . . . . . . . . . . . . . . . . 17

Matching Communications Server for AIX names with CICS definitions . . . . 17Example Communications Server for AIX configuration profiles . . . . . . . 19Example Communications Server for AIX profiles . . . . . . . . . . . 20Example CICS SNA profiles . . . . . . . . . . . . . . . . . . . 26Example CICS/ESA SNA profiles . . . . . . . . . . . . . . . . . 28Example CICS/MVS SNA profiles . . . . . . . . . . . . . . . . . 30Example Communications Manager/2 SNA profiles . . . . . . . . . . 32Example CICS OS/2 SNA profiles . . . . . . . . . . . . . . . . . 35

Chapter 3. Configuring VTAM with details of your CICS region . . . . . . 37Defining your machine and CICS regions to VTAM. . . . . . . . . . . . 37Defining modegroups to VTAM . . . . . . . . . . . . . . . . . . . 38

Chapter 4. System management in an SNA intersystem environment . . . 41Starting AIX SNA . . . . . . . . . . . . . . . . . . . . . . . . 41Displaying the status of Communications Server for AIX. . . . . . . . . . 42Stopping AIX SNA. . . . . . . . . . . . . . . . . . . . . . . . 44

Chapter 5. Problem Determination for Communications Server for AIX . . 45Common error symptom list . . . . . . . . . . . . . . . . . . . . 45AIX SNA does not bind sessions for a connection . . . . . . . . . . . 45AIX SNA does not bind at synchronization level 2 . . . . . . . . . . . 45AIX SNA does not have the RESYNCTP TPN . . . . . . . . . . . . 46

Tracing an SNA link in AIX SNA . . . . . . . . . . . . . . . . . . 46

© Copyright IBM Corp. 1999, 2008 iii


6/75

Appendix. Bibliography . . . . . . . . . . . . . . . . . . . . . 49SNA books . . . . . . . . . . . . . . . . . . . . . . . . . . 49Communications Server for AIX books . . . . . . . . . . . . . . . . 49CICS books . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Trademarks and service marks . . . . . . . . . . . . . . . . . . . 52

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

iv TXSeries for Multiplatforms: Using IBM Communications Server for AIX with CICS


7/75

Figures

1. An example heterogeneous network . . . . . . . . . . . . . . . . . . . . . . . . 12. Result of netstat -v command . . . . . . . . . . . . . . . . . . . . . . . . . . 63. Node Definition Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114. Transaction Program Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 125. Mode Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136. Local LU Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147. Side Information Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158. Partner LU Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169. Partner LU 6.2 Location Profile . . . . . . . . . . . . . . . . . . . . . . . . . 1610. CICS and Communications Server for AIX definitions when using a PPC Gateway server . . . . 1811. CICS and Communications Server for AIX definitions when using local SNA support . . . . . . 1912. Overview of example configuration . . . . . . . . . . . . . . . . . . . . . . . . 2013. Example of a node profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 2114. Example of an SNA define_trusted_groups profile. . . . . . . . . . . . . . . . . . . 2115. Example of a local LU definition profile for LU OPENCICS . . . . . . . . . . . . . . . 2216. Example of a local LU definition profile for LU CICS6000 . . . . . . . . . . . . . . . . 22

17. Example of a side information profile for region OPENCICS . . . . . . . . . . . . . . . 2218. Example of a side information profile for region cics6000 . . . . . . . . . . . . . . . . 2319. Example remote system profile for system CICSESA . . . . . . . . . . . . . . . . . 2320. Example remote system profile for CICSMVS system . . . . . . . . . . . . . . . . . 2321. Example remote system profile for region CICSOS2 . . . . . . . . . . . . . . . . . . 2322. Example remote system location profile for CICSESA system . . . . . . . . . . . . . . 2423. Example remote system location profile for CICSMVS system . . . . . . . . . . . . . . 2424. Example of a local transaction program profile for a region . . . . . . . . . . . . . . . 2425. Example of selected information from a link station profile. . . . . . . . . . . . . . . . 2426. Example of selected information from a token ring port profile . . . . . . . . . . . . . . 2527. Example of a modegroup profile for CICSISC0 . . . . . . . . . . . . . . . . . . . . 2528. Example of a modegroup profile for CICSISC1 . . . . . . . . . . . . . . . . . . . . 2529. Region Definitions (RD) attributes used for intercommunication for region CICS6000 . . . . . . 26

30. Gateway Definitions (GD) attributes . . . . . . . . . . . . . . . . . . . . . . . . 2631. Communications Definitions (CD) attributes for connection CESA . . . . . . . . . . . . . 2732. Communications Definitions (CD) attributes for connection CMVS . . . . . . . . . . . . . 2733. Communications Definitions (CD) attributes for connection COS2 . . . . . . . . . . . . . 2834. Result of CEDA EXPAND GROUP command . . . . . . . . . . . . . . . . . . . . 2835. CEDA showing connection definition (CICS/ESA) . . . . . . . . . . . . . . . . . . . 2936. CEDA showing session definition (CICS/ESA) . . . . . . . . . . . . . . . . . . . . 3037. CEDA showing connection definition (CICS/MVS) . . . . . . . . . . . . . . . . . . . 3138. CEDA showing session definition (CICS/MVS) . . . . . . . . . . . . . . . . . . . . 3139. CEDA showing session definition for OPEN0 . . . . . . . . . . . . . . . . . . . . 3240. Example of Communications Manager/2 SNA definition. . . . . . . . . . . . . . . . . 3241. Example of Communications Manager/2 link definition . . . . . . . . . . . . . . . . . 3342. Example of Communications Manager/2 definition for CICSOS2 . . . . . . . . . . . . . 33

43. Example of Communications Manager/2 definition for region cics6000 . . . . . . . . . . . 3344. Example of Communications Manager/2 definition for modegroup CICSISC0 . . . . . . . . . 3345. Example of Communications Manager/2 SNA defaults . . . . . . . . . . . . . . . . . 3446. Example of Communications Manager/2 SNA transaction program definition for CPMI . . . . . 3447. Example of Communications Manager/2 SNA transaction program definition for CVMI . . . . . 3448. Example of Communications Manager/2 SNA transaction program definition for CECI . . . . . 3449. Example of Communications Manager/2 SNA transaction program definition for CRSR . . . . . 3550. Example of Communications Manager/2 SNA transaction program definition for CRTE . . . . . 3551. Example of Communications Manager/2 SNA transaction program definition for CEDA . . . . . 3552. CEDA connection and session table (TCS) . . . . . . . . . . . . . . . . . . . . . 3653. Starting an SNA Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

© Copyright IBM Corp. 1999, 2008 v


8/75

54. RESYNCTP TPN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

vi TXSeries for Multiplatforms: Using IBM Communications Server for AIX with CICS


9/75

Tables

1. Getting started road map . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix2. Conventions that are used in this book . . . . . . . . . . . . . . . . . . . . . . . x

© Copyright IBM Corp. 1999, 2008 vii


10/75

viii TXSeries for Multiplatforms: Using IBM Communications Server for AIX with CICS


11/75

About this book

The Customer Information Control System (CICS ® ) requires a Systems NetworkArchitecture (SNA) product in order to connect to an SNA network. The IBM ®

Communications Server for AIX product provides:

v

Local SNA support for a CICS for AIX

®

regionv Gateway SNA support when used with the CICS PPC Gateway server

This book describes how to:

v Configure Communications Server for AIX

v Coordinate the configuration of Communications Server for AIX with theconfiguration of CICS and its partner systems

v Start and shut down Communications Server for AIX; and investigatecommunications errors

A review of some common SNA terminology is also included.

Who should read this book This book is for system administrators who are responsible for the configuration,operation, and management of CICS machines in an SNA LU 6.2 network.

The administrator should be familiar with Communications Server for AIX and CICSproducts and understand SNA concepts. The TXSeries for Multiplatforms Intercommunication Guide , the primary source of information about thecommunications features of CICS, gives examples of configurations and adviceabout systems design.

Document organization

Table 1. Getting started road map

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

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

Configure Communications Server for AIX Chapter 2, “Configuring CommunicationsServer for AIX for CICS intercommunication,”on page 5

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

Start and stop sessions and displayinformation about links to other machines

Chapter 4, “System management in an SNAintersystem environment,” on page 41

Solve communications problems Chapter 5, “Problem Determination for

Communications Server for AIX,” on page 45

© Copyright IBM Corp. 1999, 2008 ix


12/75

Conventions used in this book

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

Table 2. Conventions that are used in this book

Convention Meaning

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

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

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

< > Encloses the names of keys on the keyboard.

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

while you press the c key.

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

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

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

C:\> Represents the Windows ® command prompt.

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

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

[ ] Encloses optional items in syntax descriptions.

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

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

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

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

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

x TXSeries for Multiplatforms: Using IBM Communications Server for AIX with CICS


13/75

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 for Multiplatforms 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 for Multiplatforms, and, if applicable,the specific location of the information you are commenting on (for example, a pagenumber or table number).

About this book xi


14/75

xii TXSeries for Multiplatforms: Using IBM Communications Server for AIX with CICS


15/75

Chapter 1. Introduction to SNA

This section introduces the concepts and terminology that are related to IBM’sSystems Network Architecture (SNA) with which you must be familiar when usingthe Customer Information Control System (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 actions 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.

Figure 1 shows a heterogeneous network in which a CICS system isintercommunicating 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 that is used for theseparameters can differ. Some of the important common parameters are discussed inthis chapter.

Logical Unit (LU) is an SNA term that is used to describe a logical collection ofservices that can be accessed from a network. In this environment, you can think ofa CICS region as an LU. SNA defines many different types of LUs, including

Figure 1. An example heterogeneous network

© Copyright IBM Corp. 1999, 2008 1


16/75

devices such as terminals and printers. The type of LU that is used for CICSintersystem communication is LU type 6.2 .

Each LU is identified by a name of up to eight characters, which is referred to asthe LU name . An IBM mainframe-based CICS system uses, as its LU name, theAPPLID that is defined in the CICS system initialization table. (This LU name is alsoreferred to as a NETNAME .) The LU name for a CICS OS/2 system is specified in

the Communications Manager/2 Local LU definition, and the LU name for aCICS/400 system is defined in the APPL parameter of the ADDCICSSIT command.

An SNA network also has a name of up to eight characters, which is called thenetwork name . The network name is sometimes referred to as the network ID or thenetid . An LU can be uniquely identified by combining its LU name with the networkname of the network that owns it. The LU’s name is then referred to as thenetwork-qualified LU name or the fully-qualified LU name . 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 session 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 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 BIND response . When 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 in the route that theytake through the network. Session characteristics are referred to as modegroups . Allthe sessions that are associated with a modegroup have the same characteristics.A modegroup is identified by a modename of up to eight characters.

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

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 madeby an application on these systems.

CICS systems can be connected in a network in many ways. If the data issuccessfully transferred in the correct format, these CICS systems are unaware ofthe network makeup. SNA configuration is performed at two levels:

v The logical level , which is described in the preceding paragraphs, incorporatesthe characteristics of the systems that want to communicate.

v The physical level incorporates the linking of actual machines, or nodes , in thenetwork. 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. Also, 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 .

2 TXSeries for Multiplatforms: Using IBM Communications Server for AIX with CICS


17/75

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

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.

v

PU type 4 : This is a communications controller, such as an AdvancedCommunications Function for the Network Control Program (ACF/NCP), thatresides in the center of a network. It routes and controls 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 PU type 5 and relies on these PUs to route the data to the correctsystem.

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.Communications Server for AIX is a PU type 2.1 node.

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

(APPN) . This support enables a node to search for an LU in the network, ratherthan requiring a remote LU’s location to be preconfigured locally. Two types ofAPPN nodes exist: end nodes and network nodes . An end node can receive asearch request for an LU, respond, and indicate whether the LU is local to thenode. A network node can issue search requests, and respond to them. It maintainsa dynamic database that contains the results of the search requests. Support forAPPN can greatly reduce the maintenance work in an SNA network, especially ifthe network is large or dynamic. Communications Server for AIX supports APPN.

Communicating across SNA connections

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

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.To use local SNA support, SNA must be installed and configured on the samemachine as is the CICS region.

v Communication through a PPC Gateway server provides synchronization level 2support. This enables applications to ship or accept transactions from othersystems that use LU 6.2, such as IBM mainframe-based CICS, CICS OS/2, andCICS/400. SNA must be on the same machine as is the gateway.

Chapter 1. Introduction to SNA 3


18/75



19/75

Chapter 2. Configuring Communications Server for AIX forCICS intercommunication

Communications Server for AIX is an advanced Systems Network Architecture(SNA) product for the RS/6000 ® that supports Advanced Peer-To-Peer Networking

(APPN). APPN reduces the configuration that is required in order to enable systemsto communicate with each other across an SNA network.

Collecting information for a new Communications Server for AIX

configuration

To configure Communications Server for AIX, you need information about:

v The local AIX machine (control point)

v Remote machines (nodes)

v Modegroups

v Local regions

v

The system with which you want to communicate (generally known as the partnerLU)

The sections that follow describe how to collect this information. SNA configurationis much easier if you collect this information before configuring the profiles.

The local machine (control point)This section describes the information that you need in order to register your localRS/6000 that is running Communications Server for AIX in the SNA network.

You must give your SNA machine (referred to as an SNA node ) a control point (CP) name . The CP name can have one through eight characters made up of uppercaseletters (A through Z) and numbers (0 through 9). Because it is the name that thenetwork uses to communicate with your SNA machine, it must be unique within theSNA network. It must be different from:

v All other CP names in the network.

v All other logical unit (LU) names in the network. LU names are the SNA namesfor systems, such as CICS regions.

Many systems have naming conventions that help prevent name clashes. Consultyour network administrator for help when choosing names for your network.

Associated with the CP name is the Node Identifier (also referred to as theExchange Identifier or XID ). This eight-digit number, beginning with 071, identifiesthe physical unit (PU) that is associated with the control point.

You also need the name of the SNA network to which your SNA machine (and allthe CICS regions that use it) belongs. The SNA Network Name can have onethrough eight characters made up of uppercase letters (A through Z) and numbers(0 through 9).

The following example shows the information that is required in order to describethe local AIX machine.

CP Name AIX00005

© Copyright IBM Corp. 1999, 2008 5


20/75

Node Identifier 07101234

Local Network Name MYSNANET

If you are communicating with systems that use Virtual Telecommunications AccessMethod (VTAM), such as CICS MVS/ESA™, your CP name and node identifier

possibly need to be defined to VTAM. Chapter 3, “Configuring VTAM with details ofyour CICS region,” on page 37 shows some example VTAM definitions.

Remote machines (nodes)This section describes the information that is needed in order to define links fromyour local AIX machine to remote machines (referred to as SNA nodes).

For each link, you must decide whether your local machine is to make a call to theremote machine to establish the link, or is to listen for a call from the remotemachine. For a link to work, one machine must call and the other listen, so youmust coordinate with the owner of the remote machine to ensure compatible setupson each machine. The machine that is servicing more links or that is available forthe most amount of time normally listens. For example, your AIX or RS/6000

machine would most likely call on a link to VTAM and listen for a link to aworkstation.

If your machine is to call, it requires the address of the remote machine. If yourmachine is to listen, the owner of the remote machine requires your machineaddress. You can determine the address of your RS/6000 machine by using thenetstat -v command. Figure 2 shows an example from a machine that is usingToken Ring. Its address is 10005A4B3C2D, which is shown in the TOKEN-RINGSTATISTICS section, under Hardware Address.

In Communications Server for AIX, you have to set up the links only where your

local machine is calling the remote machine. For each of these links, you mustinvent a link name and record the address of the remote machine.

Note: Link names must be one through eight printable characters long. Do not useslashes (/), double quotes (″), single quotes (’), or asterisks (*) in them.These link names should be reasonably meaningful, because they are usedin the commands to start and stop a link. They also appear in the output ofseveral commands that display SNA status.

The following example shows the information for a link that calls a mainframe that isrunning VTAM.

% netstat -v: :: :

TOKEN-RING STATISTICS (tok0) :Device Type: Token-Ring High-Performance Adapter (8fc8)Hardware Address: 10:00:5a:4b:3c:2dElapsed Time: 2 days 2 hours 15 minutes 56 seconds

Transmit Statistics: Receive Statistics:-------------------- -------------------Packets: 4340087 Packets: 5790367Bytes: 1010998896 Bytes: 2220225655: :: :

Figure 2. Result of netstat -v command



21/75

Link Name LINKVTAM

Link Address 400012345678

ModegroupsThis section describes the information that you need in order to define the

modegroups (or modes ) that are used on the SNA connections between your CICSsystems and remote SNA systems.

Modegroups define the number of sessions that are allowed on a connectionbetween two systems. Each session allows one intersystem request to run at atime, so the number of sessions between two systems affects the number ofconcurrent intersystem requests that they can process. By controlling the number ofsessions between two systems, you control the network traffic that the two systemsgenerate, and prevent one system from flooding the other with requests. Identifyeach modegroup by assigning it a modename , one to eight characters long, madeup of uppercase letters (A through Z) and numbers (0 through 9).

You must define at least one modegroup to Communications Server for AIX. SNA

connections can share modegroup definitions. The session limits that are defined ina modegroup apply independently to each connection that uses that modegroup. Aconnection can use more than one modegroup. For example, suppose you have aconnection that handles fast intersystem requests for interactive users and slowerintersystem requests that send or receive large amounts of data. Simply define twomodegroups: one for the interactive requests (such as CICSISC0), and the other,for the slower data transfer requests (such as CICSISC1).

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

The following examples show the information that you need in order to definemodegroups. Remember that the modegroups that are used on a connection mustbe defined with consistent session limits on both systems. If your connection usesVTAM to communicate with the remote system, you must include a MODEENTdefinition for the modename in its tables. (Chapter 3, “Configuring VTAM with detailsof your CICS region,” on page 37 has an example of a MODEENT definition.)

Modename CICSISC0 CICSISC1

Max Sessions 10 4Min Winners 5 2

A note on the SNASVCMG and CPSVCMG modegroups

Experienced users of SNA networks know that all connections that use parallelsessions have a modegroup called SNASVCMG. SNASVCMG is a system-definedmodegroup that is reserved for use by SNA management programs. Do not attemptto define this modegroup in Communications Server for AIX or use it for your CICSintersystem requests.

Chapter 2. Configuring Communications Server for AIX for CICS intercommunication 7


22/75

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.

Local CICS regionsFor each local CICS region, you need to know:

v

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 namefor 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 made up 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 naming

conventions that help to prevent name clashes. Consult your networkadministrator for advice when choosing names for the network.

v Which of the modenames, which are defined in “Modegroups” on page 7, to useas a default when the region does not explicitly specify a modename on anintersystem request. You can specify a modename explicitly on an intersystemrequest by using the SNAModeName attribute of the Transaction Definitions (TD)or by using the PROFILE option of the EXEC CICS ALLOCATE command.Alternatively, you can specify a modename in the DefaultSNAModeNameattribute of the Communications Definitions (CD) entry. This modename is used ifyou do not specify a modename explicitly in the TD entry or in the EXEC CICScommand. This is described further in the TXSeries for Multiplatforms Intercommunication Guide .

v

For each LU name, whether synchronization level 2 is required. You can usesynchronization level 2 only if the LU name is for a PPC Gateway server that isused to communicate with systems that support synchronization level 2, such asCICS Transaction Server for z/OS, CICS/ESA, CICS/MVS and CICS/VSE.Further information about synchronization level 2 and about using a PPCGateway server can be found in the TXSeries for Multiplatforms Intercommunication Guide .

The following example shows LU names for two CICS regions: opencics andcics6000. The LU names OPENCICS and CICS6000 are used by PPC Gatewayservers and use synchronization level 2. The default modename for these LUnames is CICSISC0.

Local Region LU Name OPENCICS CICS6000Default Modename CICSISC0 CICSISC0

Synchronization Level 2? yes yes

Remote systems (Partner LUs)For each remote system (Partner LU ) with which your CICS regions are going tocommunicate across SNA, you need to know:

v Its LU name. Each CICS region in an SNA network is referred to, in SNA, as anLU. An IBM mainframe-based CICS system uses its APPLID as its LU name



23/75

(also referred to as a NETNAME ). The LU name for a CICS OS/2 system isspecified in the Communications Manager/2 Local LU definition, and the LUname for a CICS/400 region is in the APPL parameter of the ADDCICSSITcommand.

v The name of the SNA network to which it belongs. An SNA network name can beup to eight characters long, made up of uppercase letters (A through Z) andnumbers (0 through 9). If both the local node and the remote node are end

nodes or network nodes, and are part of an APPN network, you do not have todefine the remote node where the partner LU is located.

If the partner LU is not on a machine that is defined as an APPN network node,you need the control point (CP) name of the machine on which the partner LUresides, or of the machine that is configured with the information about where thepartner LU resides. If you do not specify the control point name, your localmachine cannot bind sessions to the partner LU.

Note: When you have defined and activated a link to a particular remotemachine, Communications Server for AIX displays the CP name of thismachine. If you cannot identify the CP name of a remote machine now,remember that you need this information.

v Whether you want to receive a user ID from it.Refer to the TXSeries for Multiplatforms Intercommunication Guide for moreinformation about these topics.

The following example shows data that is collected for three partner LUs. CICSESAand CICSMVS are connected to an RS/6000 machine through VTAM. VTAM’scontrol point is called MYSNANET.MYVTAM. CICSOS2 is using CommunicationsManager/2, which is set up as an APPN network node. In this case,Communications Server for AIX does not require the name of the OS/2 ® controlpoint.

Partner LUName

CICSESA CICSMVS CICSOS2

Partner NetworkName

MYSNANET MYSNANET MYSNANET

Partner CPName

MYSNANET.MYVTAM MYSNANET.MYVTAM Not Applicable

ConversationSecurity

same same none

The next step

When you have collected the information that you need about the systems that youwant to connect across an SNA network, you are ready to configure

Communications Server for AIX. This is described in “Creating a CommunicationsServer for AIX configuration” on page 10.

Related Informationv “Creating a Communications Server for AIX configuration” on page 10v “Matching Communications Server for AIX names with CICS definitions” on page17

v “Example Communications Server for AIX configuration profiles” on page 19



24/75

Creating a Communications Server for AIX configuration

This section describes how to configure Communications Server for AIX. It assumesthat you have read “Collecting information for a new Communications Server for AIXconfiguration” on page 5 and have all the information that you need about thesystems that you want to connect across an SNA network. You can use either the

System Management Interface Tool (SMIT), or the supplied Motif AdministrationProgram, to configure Communications Server for AIX. This manual describes howto use SMIT.

1. “Node setup” describes how to identify your local RS/6000 to SNA. How toconfigure links from your machine to other machines in the SNA network is alsodiscussed.

2. “Defining a profile for your CICS transactions” on page 11 describes how to setup a profile for your CICS transactions. You must set up at least one of theseprofiles to enable your CICS region to receive intersystem requests from remoteSNA systems.

3. “Defining modenames” on page 12 describes how to set up modenames.

4. “Enabling CICS user IDs” on page 13 describes how to set up Communications

Server for AIX so that your CICS region can send and receive user IDs acrossSNA.

5. “Defining a local CICS region” on page 13 describes how to set up profiles thatdescribe your local CICS regions.

6. “Defining your SNA partner LUs” on page 15 describes how to set up profilesthat describe a remote system that will communicate with your CICS regionacross SNA.

7. “Backing up configuration profiles” on page 17 describes how to back up yourconfigurations.

Note: To configure Communications Server for AIX, you need to be logged on toAIX with a user ID that is a member of the AIX system group, such as root.

Node setup

To allow you to configure the node, SMIT uses the following data for the localmachine:

Control Point (CP) Alias AIX00005

Node Identifier 07101234

Local Network Name MYSNANET

1. Enter smitty sna and select these options:

→ Configure SNA Resources

→ Local Node Resources→ Node Definition

2. The Node Definition panel displays as shown in Figure 3 on page 11. Thevalues that you must enter are shown highlighted in the panel. Note that theFully-qualified Control Point name field combines the Local Network Nameand Control Point (CP) Name information. Press the Enter key to create theprofile.



25/75

3. At this point, you must also configure a link station for each remote node withwhich your local node communicates. Enter smitty sna and select theseoptions:

→ Configure SNA Resources→ Local Node Resources

→ Connectivity

The Connectivity menu guides you through setting up DLCs, ports, and linkstations based on your connection type. More information about connections isavailable in the Communications Server for AIX documentation. For theRS/6000 setup configuration example in this chapter, assume that the RS/6000calls on a token-ring link station with the name LINKVTAM and address400012345678.

4. After you have defined the node and all the links to remote machines, test theconfiguration before continuing. At this point, you must acquire the CP names ofany remote machines. (A remote machine’s CP name is displayed byCommunications Server for AIX when the link to the remote machine is active.)

v Refer to “Starting AIX SNA” on page 41 for information about starting SNA andthe links to remote machines.

v Refer to “Displaying the status of Communications Server for AIX” on page 42 forinformation about displaying the CP name of a remote machine.

Note: If your region is to communicate with a remote system that uses VTAM,VTAM must be configured with information about your local machine.Chapter 3, “Configuring VTAM with details of your CICS region,” on page 37

shows some examples of VTAM definitions.

Defining a profile for your CICS transactions

CICS regions need an LU 6.2 Transaction Program Name (TPN) Profile if they areto receive intersystem requests from SNA partner LUs.

1. To create this profile, enter smitty sna, and select the following options todisplay the Add Transaction Program panel:

Node Definition

Type or select values in entry fields.Press Enter AFTER making all desired changes.

[Entry Fields]* Control Point alias [AIX00005]Description []

* Fully-qualified Control Point name [MYSNANET.AIX00005]Node type NETWORK_NODE +Node identifier [07101234] XManagement Services support NORMAL +

If BACK_LEVEL,

Queue NMVTs? NO +

F1=Help F2=Refresh F3=Cancel F4=ListF5=Reset F6=Command F7=Edit F8=ImageF9=Shell F10=Exit Enter=Do

Figure 3. Node Definition Profile



26/75


→ LU 6.2 Configuration→ LU 6.2 Transaction Program

→ LU 6.2 transaction Programe Definitions→ Add Transaction Program

2. Fill in the entry fields as shown in Figure 4. Press the Enter key to create theprofile. This example defines a transaction program called CICSTPN.

3. After you have created this profile, you need to add its name (CICSTPN) to theTPNSNAProfile attribute in the following CICS Transaction Definitions (TD)entries of your CICS regions:

v The CICS intercommunication transactions: CRTE, CRSR, CPMI, CVMI,CSMI, CSM1, CSM2, CSM3, and CSM5

v All CICS transactions that an SNA partner LU can possibly access by using

transaction routingv All back-end DTP transactions that are called by DTP front-end transactionsthat are running on an SNA partner LU

4. Use the cicsupdateclass command to update TPNSNAProfile in all TD entries.The following example sets TPNSNAProfile=″CICSTPN″ in all TD entries:

Defining modenames

For each modename that your CICS region uses, you must create a Mode Profileas follows:

1. Enter smitty sna, and select the following options to display the Add Modepanel:


→ LU 6.2 Configuration→ LU 6.2 Mode

→ Add Mode

Add Transaction Program


[Entry Fields]* Name [CICSTPN]Description []List name [] +Conversation type(s) supported MAPPED +Conversation security is required? NO +Synchronization level supported? SYNCPT_NEGOTIABLE +Program Initialization Parameters (PIP) allowed? YES +


Figure 4. Transaction Program Profile

% cicsupdateclass -r regionName \-c td \-w \-a TPNSNAProfile \-n "CICSTPN"



27/75

2. Fill in the entry fields as shown in Figure 5. Press the Enter key to create theprofile.

The example that is shown in Figure 5 creates a profile for a modegroup that hasthe following attributes:

Modename CICSISC0

Max Sessions 10

Min Winners 5

The example also sets Auto-activate sessions to the same value as Min con.winner sessions. This means that Communications Server for AIX will bind fivecontention winner sessions between the two systems when the first intersystemrequest uses this modegroup on a connection. This makes five sessionsimmediately available for subsequent intersystem requests. You can specify theAuto-activate sessions to be zero through the maximum number of sessions limit.

Enabling CICS user IDsTo set up Communications Server for AIX so that a CICS region can send andreceive user IDs to and from remote SNA systems, use the following command.

The group identification number for the cics group can be found in /etc/group.% snaadmin define_trusted_groups,group_id= group_identification_number

Defining a local CICS region

Two Communications Server for AIX profiles are required for each of your CICSregion’s LU names: the Local LU Profile and the Side Information Profile. Thissection describes how to create them. The two profiles use the following example:

Local Region’s LU Name OPENCICS

Add Mode

Type or select values in entry fields.

Press Enter AFTER making all desired changes.

[TOP] [Entry Fields]* Name [CICSISC0]Description []

Session limits

Maximum number of sessions [10] #Initial session limit [10] #Min con. winner sessions [5] #Min con. loser sessions [0] #Auto-activate sessions [5] #

Receive pacing window

[MORE. . .10]


Figure 5. Mode Profile



28/75

Default Modename CICSISC0

Synchronization Level 2 yes

Conversation Security same

1. To create a Local LU Profile for your CICS region, enter smitty sna, and selectthe following options to display the Add Independent LU Type 6.2 panel:


→ LU 6.2 Configuration→ LU 6.2

→ Add Independent LU Type 6.2

2. Fill in the entry fields as shown in Figure 6. Press the Enter key to create theprofile. Here, you are creating the profile for the OPENCICS LU name. Alwaysensure that your LU name and LU alias are the same. The attribute SupportSyncpoint 2 must be set to yes if this LU name is to be used with a PPCGateway server and to no if it is to be used with local SNA.

3. To create a Side Information Profile for your CICS region, enter smitty sna andselect the following options to display the Add Side Information panel:


→ LU 6.2 Configuration→ LU 6.2 Side Information

→ Add Side Information

4. Fill in the entry fields as shown in Figure 7 on page 15. Press the Enter key tocreate the profile. Here, you are creating the profile for the OPENCICS LUname. The modename (CICSISC0) that is entered is the default modename forthe LU name. The modename that you use must be defined as described in“Defining modenames” on page 12. The Symbolic destination name mustalways be the same as your local LU name and local LU alias.

The value that is entered in the Conversation security field depends on thevalue of RemoteSysSecurity that is specified in the SNA CommunicationsDefinitions (CD) that is defined for this partner LU in your CICS region. Whenthe Conversation security field is set to none, use the corresponding value oflocal for RemoteSysSecurity. When the Conversation security field is set tosame or program, use the corresponding value of trusted forRemoteSysSecurity. For more information about security parameters, refer tothe TXSeries for Multiplatforms Intercommunication Guide .

Add Independent LU Type 6.2


[Entry Fields]* LU alias [OPENCICS]List name [] +Description []

* LU name [OPENCICS]Support Syncpoint 2 YES +Additional LU properties NONE +


Figure 6. Local LU Profile



29/75

Defining your SNA partner LUs

The way to define a partner LU depends on the capabilities of the particular partnerLU. All partner LUs require a Partner LU Profile. If the partner LU is not on anAPPN network node (such as CICS Transaction Server for z/OS, CICS/ESA,CICS/MVS and CICS/VSE), you also need to create a Partner LU 6.2 LocationProfile.

This section describes how to create profiles for partner LUs. The profiles use the

following example:Partner LU Name CICSESA

Partner Network Name MYSNANET

Partner CP Name MYSNANET.MYVTAM

1. To create a Partner LU Profile, enter smitty sna, and select the followingoptions to display the Add Partner LU panel:


→ LU 6.2 Configuration→ LU 6.2 Partner LU

→ Add Partner LU

2. Fill in the entry fields as shown in Figure 8 on page 16. Press the Enter key tocreate the profile. Here, you are creating the profile for a CICS TransactionServer for z/OS partner LU called CICSESA that belongs to the SNA networkMYSNANET.

3. If you are using a PPC Gateway server, you must always define a partner LUalias. If the partner LU alias is different from the partner LU name, you must setSNAConnectName= in the CICS CommunicationsDefinitions (CD) entry.

Add Side Information


[Entry Fields]* Symbolic destination name [OPENCICS]Description []

Local LU alias [OPENCICS] +Partner LU name [] +Mode [CICSISC0] +TP name type APPLICATION_TP +TP name [] +Conversation security SAME +User ID []Password []


Figure 7. Side Information Profile



30/75

4. If the partner LU is not on an APPN network node (such as CICS TransactionServer for z/OS, CICS/ESA, CICS/MVS and CICS/VSE), you also need to

create a Partner LU 6.2 Location Profile. To create this profile, enter smitty sna,and select the following options to display the Add Partner LU 6.2 Locationpanel:


→ LU 6.2 Configuration→ Partner LU 6.2 Location

→ Location on Remote Node→ Add Partner LU

Here, you are creating the profile for a CICS Transaction Server for z/OS partnerLU, called CICSESA, that belongs to the SNA network MYSNANET. The Parentname is the name of the nearest SNA control point that knows how to contact the

partner LU. For example, this can be the local VTAM machine. Although thisexample defines a location that is on a remote node, you can also specify locationby a link station if needed. Fill in the entry fields as shown in Figure 9. Press theEnter key to create the profile. In some cases, a Partner LU 6.2 Location Profile forthe Parent might have to be created first.

Add Partner LU


[Entry Fields]* Alias [CICSESA]Description []

* Fully-qualified LU name [MYSNANET.CICSESA]Uninterpreted LU name []Parallel sessions supported? YES +AnyNet routing USE_DEFAULT_PREFERENCE +


Figure 8. Partner LU Profile

Add Partner LU


[Entry Fields]* Resource name [MYSNANET.CICSESA]Resource type LU_RESOURCE +Description []

Parent name [MYSNANET.MYVTAM]Parent type ENCP_RESOURCE +


Figure 9. Partner LU 6.2 Location Profile



31/75

Backing up configuration profilesWhenever you add or change an SNA configuration, back up your SNA databases.ASCII versions of the current Communications Server for AIX configuration profilesexist in /etc/sna. To back up these profiles, copy the sna_domn.cfg,sna_node.cfg, and sna_tps files that are there. Store these backup files in a safeplace away from the SNA machine.

Where to next

Some parameters that you use when configuring CICS must match those that youhave used when configuring Communications Server for AIX. This requirement isexplained in:

v “Matching Communications Server for AIX names with CICS definitions”

Many example configurations to different types of remote systems are given in:

v “Example Communications Server for AIX configuration profiles” on page 19

The remote systems with which your local CICS region communicates must beconfigured in compatible ways to your CICS system. Remote systems that use

VTAM are discussed in:

v Chapter 3, “Configuring VTAM with details of your CICS region,” on page 37

After you have configured Communications Server for AIX, you can configure yourCICS region. Information can be found in the TXSeries for Multiplatforms Intercommunication Guide .

Matching Communications Server for AIX names with CICS definitions

After configuring Communications Server for AIX, you must configure the CICScommunications resources. This is described in the TXSeries for Multiplatforms Intercommunication Guide . Some of the arguments that you use when configuring

CICS must match those that you have used to configure Communications Serverfor AIX. This section describes the parameters that must match.

These diagrams show how Communications Server for AIX profiles relate to CICSdefinitions. Figure 10 on page 18 shows a configuration that has a local LUOPENCICS and a PPC Gateway server. Figure 11 on page 19 shows aconfiguration that has a local LU CICS6000 that does not include a PPC Gatewayserver, but instead, uses local SNA support. Refer to “Example CommunicationsServer for AIX configuration profiles” on page 19 for examples of the complete SNAprofiles that are given here.



32/75

Figure 10. CICS and Communications Server for AIX definitions when using a PPC Gateway server



33/75

Related Informationv “Collecting information for a new Communications Server for AIX configuration”on page 5

v “Creating a Communications Server for AIX configuration” on page 10v “Example Communications Server for AIX configuration profiles”

Example Communications Server for AIX configuration profiles

The following sections provide examples of SNA profiles that connect a CICS onOpen Systems region named cics6000 to a CICS Transaction Server for z/OSsystem named CICSESA, a CICS/MVS system named CICSMVS, and a CICSOS/2 system named CICSOS2. This configuration is represented in Figure 12 onpage 20.

The connections to CICSESA and CICSMVS are through a PPC Gateway server.They use synchronization level 2 and a local LU of OPENCICS. The connection toCICSOS2 uses local SNA support and a local LU of CICS6000.

Figure 11. CICS and Communications Server for AIX definitions when using local SNA support



34/75

The profiles are shown in the following sections:v “Example Communications Server for AIX profiles”v “Example CICS SNA profiles” on page 26v “Example CICS/ESA SNA profiles” on page 28v “Example CICS/MVS SNA profiles” on page 30v “Example Communications Manager/2 SNA profiles” on page 32v “Example CICS OS/2 SNA profiles” on page 35

Example VTAM definitions for the OPENCICS and CICS6000 LUs are described inChapter 3, “Configuring VTAM with details of your CICS region,” on page 37.

Example Communications Server for AIX profilesThe example profiles that follow reflect similar profiles that exist for your current

system configuration. These profiles are always available in ASCII format in thesna_node.cfg, sna_domn.cfg, and sna_tps files that are in /etc/sna. Theexamples that are given here show the profiles that are required for the CICSregion named cics6000, using local LU names OPENCICS and CICS6000, tocommunicate with three systems: CICSESA, CICSMVS, and CICSOS2. For moreinformation about how to create these profiles, go to “Creating a CommunicationsServer for AIX configuration” on page 10.

Figure 13 on page 21 shows an example of a node profile. It describes the RS/6000that is running Communications Server for AIX.

VTAMCommunicationsManager/2

CICS/ESA

CICSapplication

CICSapplication

OS /2 ESA

SNA Network

TCP/IP

VTAM

CICS/MVS

CICSapplication

MV S

CICS forOS/2

L Una me =CICS60 00 L Un ame =OPENCICSSNA Product

CICS on OpenSystems

PPCExecutive

PPC GatewayServer

Figure 12. Overview of example configuration



35/75

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

group identification number is in /etc/group.

Figure 15 on page 22 and Figure 16 on page 22 show examples of the local LUdefinitions for the CICS region. Two definitions exist, one for each of its local LUs.

[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 = NOmds_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

Figure 13. Example of a node profile

[define_trusted_groups]group_id = 79

Figure 14. Example of an SNA define_trusted_groups profile



36/75

The synctpt_support = yes indicates that a PPC Gateway server is going to usethe OPENCICS local LU. (This field instructs Communications Server for AIX tobind sessions at synchronization level 2.)

The synctpt_support = no indicates that the CICS6000 local LU is to be used bylocal SNA. (This field instructs Communications Server for AIX to bind sessions atsynchronization level 1.)

Figure 17 and Figure 18 on page 23 show examples of the side information profilesthat define the default modename for each of the local region’s LUs:

[define_local_lu]lu_alias = OPENCICSlist_name = ""description = ""lu_name = OPENCICSlu_session_limit = 0pu_name = nau_address = 0

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

Figure 15. Example of a local LU definition profile for LU OPENCICS

[define_local_lu]lu_alias = CICS6000list_name = ""description = ""lu_name = CICS6000lu_session_limit = 0pu_name = nau_address = 0default_pool = NOsyncpt_support = NOlu_attributes = NONEsscp_id = 0disable = NOsys_name = ""timeout = 60

back_level = YESFigure 16. Example of a local LU definition profile for LU CICS6000

[define_cpic_side_info]sym_dest_name = OPENCICSdescription = ""

lu_alias = OPENCICSpartner_lu_name = ""mode_name = CICSISC0tp_name_type = APPLICATION_TPtp_name = conversation_security_type = SAMEsecurity_user_id = ""security_password = ""

Figure 17. Example of a side information profile for region OPENCICS



37/75

Figure 19, Figure 20, and Figure 21 show examples of standard partner LU profilesfor the remote systems CICSESA, CICSMVS, and CICSOS2.

CICSESA and CICSMVS are running on a machine that is not an APPN networknode, so they require partner LU location profiles, as well as the standard partnerLU profiles. Figure 22 on page 24 and Figure 23 on page 24 show example partnerLU location profiles.

[define_cpic_side_info]sym_dest_name = CICS6000description = ""lu_alias = CICS6000partner_lu_name = ""mode_name = CICSISC0tp_name_type = APPLICATION_TPtp_name =

conversation_security_type = NONEsecurity_user_id = ""security_password = ""

Figure 18. Example of a side information profile for region cics6000

[define_partner_lu]plu_alias = CICSESAdescription = ""fqplu_name = MYSNANET.CICSESAplu_un_name = CICSESAparallel_session_supp = YES

appcip_routing_preference = USE_DEFAULT_PREFERENCEmax_mc_11_send_size = 0conv_security_ver = YES

Figure 19. Example remote system profile for system CICSESA

[define_partner_lu]plu_alias = CICSMVSdescription = ""fqplu_name = MYSNANET.CICSMVSplu_un_name = CICSMVSparallel_session_supp = YESappcip_routing_preference = USE_DEFAULT_PREFERENCEmax_mc_11_send_size = 0conv_security_ver = YES

Figure 20. Example remote system profile for CICSMVS system

[define_partner_lu]plu_alias = CICSOS2description = ""fqplu_name = MYSNANET.CICSOS2plu_un_name = CICSOS2parallel_session_supp = YESappcip_routing_preference = USE_DEFAULT_PREFERENCEmax_mc_11_send_size = 0conv_security_ver = NO

Figure 21. Example remote system profile for region CICSOS2



38/75

Figure 24 shows an example of the local transaction program profile that is createdfor all local CICS regions that are using this particular instance of CommunicationsServer for AIX. The name of this profile (CICSTPN) is configured in theTPNSNAProfile attribute of the region’s Transaction Definitions (TD) entries.

Figure 25 shows selected information from the profile example that defines the linkfrom the RS/6000 to VTAM. This link is used on the connections from local LUOPENCICS to CICSESA and CICSMVS.

Figure 26 on page 25 shows selected information from the profile example thatdescribes the token ring port that Communications Server for AIX uses.

[define_directory_entry]resource_name = MYSNANET.CICSESAresource_type = LU_RESOURCEdescription = ""parent_name = MYSNANET.MYVTAMparent_type = ENCP_RESOURCE

Figure 22. Example remote system location profile for CICSESA system

[define_directory_entry]resource_name = MYSNANET.CICSMVSresource_type = LU_RESOURCEdescription = ""parent_name = MYSNANET.MYVTAMparent_type = ENCP_RESOURCE

Figure 23. Example remote system location profile for CICSMVS system

[define_tp]tp_name = CICSTPNdescription = ""list_name = ""conv_type = MAPPEDsecurity_rqd = NOsync_level = SYNCPT_NEGOTIABLEenabled = YESpip_allowed = YEStp_instance_limit = 0incoming_alloc_timeout = 0

Figure 24. Example of a local transaction program profile for a region

[define_token_ring_ls]ls_name = LINKVTAMdescription = ""port_name = tok0.001: :: :local_node_id = adj_node_id = mac_address = 0x400012345678: :

: :Figure 25. Example of selected information from a link station profile



39/75

Figure 27 and Figure 28 show examples of two profiles that describe themodegroups CICSISC0 and CICSISC1. CICSISC0 is used on all the connections.

CICSISC1 is used only on the connection from OPENCICS to CICSESA.Communications Server for AIX does not require you to specify which connectionsuse each modegroup. It allows any connection to use any modegroup that isdefined. However, the modegroup must be defined in both systems before it can beused successfully.

[define_tr_port]port_name = tok0.001description = "": :: :max_rcv_btu_size = 00000tot_link_act_lim = 100inb_link_acc_lim = 0

out_link_acc_lim = 0: :: :max_ifrm_rcvd = 8: :: :max_send_btu_size = 00000: :: :force_time = 120

Figure 26. Example of selected information from a token ring port profile

[define_mode]mode_name = CICSISC0description = ""max_neg_sess_lim = 10plu_mode_session_limit = 10min_conwin_src = 5min_conloser_src = 0auto_act = 5

receive_pacing_win = 7max_receive_pacing_win = 16default_ru_size = YESmax_ru_size_upp = 1024max_ru_size_low = 256cos_name = #CONNECT

Figure 27. Example of a modegroup profile for CICSISC0

[define_mode]mode_name = CICSISC1description = ""max_neg_sess_lim = 4plu_mode_session_limit = 4min_conwin_src = 2min_conloser_src = 0auto_act = 2receive_pacing_win = 7max_receive_pacing_win = 16default_ru_size = YESmax_ru_size_upp = 1024max_ru_size_low = 256cos_name = #CONNECT

Figure 28. Example of a modegroup profile for CICSISC1



40/75

Example CICS SNA profilesThe examples that follow show the relevant parts of the files that contain theresource definitions for the CICS region cics6000. Figure 29 shows part of theRegion Definitions (RD) file named:

/var/cics_regions/cics6000/database/RD/RD.stanza

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

Figure 30 shows the Gateway Definitions (GD) file named:/var/cics_regions/cics6000/database/GD/GD.stanza

This is the definition of the PPC Gateway server that will be used to contactCICSESA and CICSMVS. (More information about defining GD entries is given inthe TXSeries for Multiplatforms Intercommunication Guide .)

Figure 31 on page 27, Figure 32 on page 27, and Figure 33 on page 28 showCommunications Definitions (CD) from a file named:

/var/cics_regions/cics6000/database/CD/CD.stanza

These three CD entries define connections to the three remote systems. CESA isthe CD entry for the connection to CICSESA, CMVS is the CD entry for theconnection to CICS/MVS, and COS2 is the CD entry for the connection toCICSOS2. The connections CESA and CMVS are through the PPC Gateway serverthat is defined in the GD entry GWY. This is specified in the CD attributeGatewayName. (More information about defining CD entries is given in the

TXSeries for Multiplatforms Intercommunication Guide .)

ResourceDescription = "Region Definition for cics6000": : :: : :

LocalSysId = "6000"LocalNetworkName = "MYSNANET"

: : :: : :

LocalLUName = "CICS6000"

Figure 29. Region Definitions (RD) attributes used for intercommunication for region CICS6000

GWY:: : :: : :

ResourceDescription="Gateway for LU OPENCICS": : :: : :GatewayLUName="OPENCICS"

Figure 30. Gateway Definitions (GD) attributes



41/75

CESA:GroupName=""ActivateOnStartup=yesResourceDescription="Connection to CICSESA"AmendCounter=0Permanent=noAllocateTimeout=60TSLKeyMask=none

RSLKeyMask=noneConnectionType=ppc_gatewayRemoteLUName="CICSESA"GatewayName="GWY"RemoteNetworkName="MYSNANET"SNAConnectName=""RemoteCodePageTR="IBM-037"RemoteSysSecurity=trustedLinkUserId="LINKCESA"RemoteSysEncrypt=noneOutboundUserIds=sentInService=yesListenerName=""RemoteTCPAddress=""RemoteTCPPort="1435"DefaultSNAModeName=""

Figure 31. Communications Definitions (CD) attributes for connection CESA

CMVS:GroupName=""ActivateOnStartup=yesResourceDescription="Connection to CICS/MVS"AmendCounter=0Permanent=noAllocateTimeout=0TSLKeyMask=noneRSLKeyMask=noneConnectionType=ppc_gatewayRemoteLUName="CICSMVS"

GatewayName="GWY"RemoteNetworkName="MYSNANET"SNAConnectName=""RemoteCodePageTR="IBM-037"RemoteSysSecurity=trustedLinkUserId="LINKCMVS"RemoteSysEncrypt=noneOutboundUserIds=sentInService=yesListenerName=""RemoteTCPAddress=""RemoteTCPPort="1435"DefaultSNAModeName=""

Figure 32. Communications Definitions (CD) attributes for connection CMVS



42/75

Example CICS/ESA SNA profilesYou can create and view CICS Transaction Server for z/OS definitions by using theCICS Transaction Server for z/OS CEDA transaction. Figure 34 shows the results ofa CEDA EXPAND GROUP(OPEN) command that is issued on the CICSESAsystem. It shows the definitions of a connection named OPEN that have been setup in a CICS group that is also named OPEN.

Defining a connection from CICS/ESA ® 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. This example contains two SESSIONSdefinitions, because this particular connection is using two modegroups.

Figure 35 on page 29 shows the contents of the OPEN CONNECTION definition.The name of connection OPEN is the SYSID that transactions use to communicate

COS2:GroupName=""ActivateOnStartup=yesResourceDescription="Connection to CICSOS2"AmendCounter=0Permanent=noAllocateTimeout=0TSLKeyMask=none

RSLKeyMask=noneConnectionType=local_snaRemoteLUName="CICSOS2"GatewayName=""RemoteNetworkName="MYSNANET"SNAConnectName=""RemoteCodePageTR="IBM-037"RemoteSysSecurity=localLinkUserId="LINKCOS2"RemoteSysEncrypt=noneOutboundUserIds=not_sentInService=yesListenerName=""RemoteTCPAddress=""RemoteTCPPort="1435"DefaultSNAModeName=""

Figure 33. Communications Definitions (CD) attributes for connection COS2

EXPAND GROUP(OPEN)ENTER COMMANDSNAME TYPE GROUP DATE TIMEOPEN CONNECTION OPEN 92.324 11.21.53OPEN0 SESSIONS OPEN 93.026 14.33.53OPEN1 SESSIONS OPEN 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

Figure 34. Result of CEDA EXPAND GROUP command



43/75

with the OPENCICS LU.

Figure 36 on page 30 shows one of the SESSIONS definitions, OPEN0, thatdescribes modegroup CICSISC0. The name that is defined in the CONNECTIONattribute is the name of the CONNECTION to which this SESSIONS definition

belongs. The two values that are specified under MAximum (010 , 005) are themaximum number of sessions and the maximum number of contention winners,respectively. These must be consistent with the values that are specified in themode profile for this modegroup.

OBJECT CHARACTERISTICS CICS RELEASE = 0330CEDA ViewConnection : OPENGroup : OPENDEscription : Connection to system OPENCICS

CONNECTION IDENTIFIERSNetname : OPENCICSINDsys :

REMOTE ATTRIBUTESREMOTESystem :REMOTEName :

CONNECTION PROPERTIESACcessmethod : Vtam Vtam | IRc | INdirect | XmProtocol : Appc Appc | Lu61SInglesess : No No | YesDAtastream : User User | 3270 | SCs | STrfield | LmsRECordformat : U U | Vb

OPERATIONAL PROPERTIESAUtoconnect : Yes No | Yes | AllINService : Yes Yes | No

SECURITYSEcurityname :

ATtachsec : Identify Local | Identify | Verify | Persistent| Mixidpe

BINDPassword : 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

Figure 35. CEDA showing connection definition (CICS/ESA)



44/75

Example CICS/MVS SNA profilesYou can create and view CICS/MVS definitions by using the CICS/MVS CEDAtransaction. Figure 37 on page 31 shows the results of a CEDA EXPANDGROUP(OPEN) ALL(*) command that is issued on the CICSMVS system. Alsoshown are the definitions of a connection named OPEN that have been set up in a

CICS group that is also named OPEN.

OBJECT CHARACTERISTICS CICS RELEASE = 0330CEDA ViewSessions : OPEN0Group : OPENDEscription : Modegroup CICSISC0 for connection to OPENCICSSESSION IDENTIFIERSConnection : OPENSESSName :

NETnameq :MOdename : CICSISC0SESSION 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-255RECOVERYRECOVOption : 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

Figure 36. CEDA showing session definition (CICS/ESA)



45/75

Defining a connection from CICS/MVS 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 38 shows the contents of the OPEN CONNECTION definition. The name ofthe connection OPEN is the SYSID that transactions use to communicate with theOPENCICS LU.

Figure 39 on page 32 shows the SESSIONS definition OPEN0 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 maximum numberof sessions and the maximum number of contention winners, respectively. Thesemust be consistent with the values that are specified in the mode profile for thismodegroup.

EXPAND GROUP(OPEN) ALL(*)ENTER COMMANDSNAME TYPE GROUP DATE TIME6000 CONNECTION OPEN 92.324 11.21.526000 SESSIONS OPEN 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

Figure 37. CEDA showing connection definition (CICS/MVS)

OBJECT CHARACTERISTICSCEDA ViewConnection : OPENGroup : OPEN

CONNECTION IDENTIFIERSNetname : OPENCICSINDsys :

CONNECTION PROPERTIESACcessmethod : Vtam Vtam | IRc | INdirect | Xm

Protocol : Appc Appc | Lu61SInglesess : No No | YesDatastream : User User | 3270 | SCs | STrfield | LmsRecordformat : U U | Vb

OPERATIONAL PROPERTIESAUtoconnect : Yes No | Yes | AllINService : Yes Yes | No

SECURITYSEcurityname :ATtachsec : Identify Local | Identify | VerifyBindpassword : PASSWORD NOT SPECIFIED


Figure 38. CEDA showing session definition (CICS/MVS)



46/75

Example Communications Manager/2 SNA profilesThe example profiles that follow are Communications Manager/2 NDF profiles foran OS/2 machine that is running a CICS OS/2 system that is communicating withthe CICS region named cics6000. The cics6000 region is using the LU nameCICS6000 and the CICS OS/2 system is using the LU name CICSOS2. Figure 40shows the SNA definition of the OS/2 machine.

OBJECT CHARACTERISTICSCEDA ViewSessions : OPEN0Group : OPENSESSION IDENTIFIERSConnection : OPENSESSName :

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-30720OPERATOR DEFAULTSOPERId :OPERPriority : 000 0-255OPERRsl : 0 0-24,...OPERSecurity : 1 1-64,...USERId :

SESSION USAGESTransaction :SESSPriority : 000 0-255OPERATIONAL 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-255RECOVERYRECOVOption : Sysdefault Sysdefault | Clearconv | Releasesess |

Uncondrel | NoneRECOVNotify : None None | Message | Transaction


Figure 39. CEDA showing session definition for OPEN0

DEFINE_LOCAL_CP FQ_CP_NAME(MYSNANET.OS200003)DESCRIPTION(Local control point)CP_ALIAS(OS200003)NAU_ADDRESS(INDEPENDENT_LU)NODE_TYPE(NN)NODE_ID(X’05D54321’)HOST_FP_SUPPORT(NO);

Figure 40. Example of Communications Manager/2 SNA definition



47/75

The example in Figure 41 defines a link that calls an RS/6000 that is runningCommunications Server for AIX and an AIX PPC Gateway Server. The OPENCICSregion is on this RS/6000.

Figure 42 shows the definition for the CICS OS/2 system CICSOS2.

Figure 43 shows the definition of the cics6000 region’s local LU CICS6000.

Figure 44 shows the definition for the modegroup CICSISC0 that is used on theconnection between CICSOS2 and cics6000.

Figure 45 on page 34 shows the Communications Manager/2 SNA defaults:

DEFINE_LOGICAL_LINK LINK_NAME(LINKAIX5)DESCRIPTION(LU6.2 Link to AIX SNA Server)FQ_ADJACENT_CP_NAME(MYSNANET.AIX00005)ADJACENT_NODE_TYPE(NN)DLC_NAME(IBMTRNET)ADAPTER_NUMBER(0)DESTINATION_ADDRESS(X’10005A4B3C2D’)CP_CP_SESSION_SUPPORT(YES)ACTIVATE_AT_STARTUP(YES)LIMITED_RESOURCE(NO)LINK_STATION_ROLE(USE_ADAPTER_DEFINITION)SOLICIT_SSCP_SESSION(NO)EFFECTIVE_CAPACITY(USE_ADAPTER_DEFINITION)COST_PER_CONNECT_TIME(USE_ADAPTER_DEFINITION)COST_PER_BYTE(USE_ADAPTER_DEFINITION)SECURITY(USE_ADAPTER_DEFINITION)PROPAGATION_DELAY(USE_ADAPTER_DEFINITION)USER_DEFINED_1(USE_ADAPTER_DEFINITION)USER_DEFINED_2(USE_ADAPTER_DEFINITION)

USER_DEFINED_3(USE_ADAPTER_DEFINITION);

Figure 41. Example of Communications Manager/2 link definition

DEFINE_LOCAL_LU LU_NAME(CICSOS2 )DESCRIPTION(CICS OS/2 System)LU_ALIAS(CICSOS2 )NAU_ADDRESS(INDEPENDENT_LU);

Figure 42. Example of Communications Manager/2 definition for CICSOS2

DEFINE_PARTNER_LU FQ_PARTNER_LU_NAME(MYSNANET.CICS6000)DESCRIPTION(OPEN Based CICS Region)PARTNER_LU_ALIAS(cics6000)PARTNER_LU_UNINTERPRETED_NAME(CICS6000)MAX_MC_LL_SEND_SIZE(32767)CONV_SECURITY_VERIFICATION(NO)PARALLEL_SESSION_SUPPORT(YES);

Figure 43. Example of Communications Manager/2 definition for region cics6000

DEFINE_MODE MODE_NAME(CICSISC0)

DESCRIPTION(Parallel sessions to RS/6000)COS_NAME(#CONNECT)DEFAULT_RU_SIZE(NO)MAX_RU_SIZE_UPPER_BOUND(1920)RECEIVE_PACING_WINDOW(7)MAX_NEGOTIABLE_SESSION_LIMIT(10)PLU_MODE_SESSION_LIMIT(10)MIN_CONWINNERS_SOURCE(5);

Figure 44. Example of Communications Manager/2 definition for modegroup CICSISC0



48/75

Figures Figure 46 through Figure 51 on page 35 show the transaction programdefinitions for all of the CICSOS2 transactions that the cics6000 region accesses:

DEFINE_DEFAULTS IMPLICIT_INBOUND_PLU_SUPPORT(YES)DESCRIPTION(Created on 24-04-98 at 02:04p)DEFAULT_MODE_NAME(CICSISC0)MAX_MC_LL_SEND_SIZE(32767)DIRECTORY_FOR_INBOUND_ATTACHES(*)DEFAULT_TP_OPERATION(NONQUEUED_AM_STARTED)DEFAULT_TP_PROGRAM_TYPE(BACKGROUND)DEFAULT_TP_CONV_SECURITY_RQD(NO)

MAX_HELD_ALERTS(10);Figure 45. Example of Communications Manager/2 SNA defaults

DEFINE_TP TP_NAME(CPMI)PIP_ALLOWED(NO)FILESPEC(D:\CICS200\BIN\FAACLPIN.EXE)PARM_STRING(CPMI)CONVERSATION_TYPE(EITHER)CONV_SECURITY_RQD(NO)SYNC_LEVEL(EITHER)TP_OPERATION(NONQUEUED

txseries for multiplatforms using ibm communications server for aix with cics version 6.2

Documents