TXSeries For Multiplatforms Using SNAP-IX For Solaris With CICS Version 6.2

TXSeries for Multiplatforms
Using SNAP-IX for Solaris with CICS

Version 6.2
SC34-6751-01

Version 6.2
SC34-6751-01
Note
Before using this information and the product it supports, be sure to read the general information under Notices on page
61.
Second Edition (January 2008)

This edition replaces SC34-6751-00.
Order publications through your IBM representative or through the IBM branch office serving your locality.
Copyright International Business Machines Corporation 1999, 2008. All rights reserved.
US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
About this book . . . . .
Who should read this book . .
Document organization . . .
Conventions used in this book .
How to send your comments .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
ix
ix
ix
x
xi
Chapter 1. Introduction to SNAP-IX for Solaris
. . . . . . . . . . . . 1
Chapter 2. Introduction to SNA . . . . .

A sample network . . . . . . . . . .
SNA configuration . . . . . . . . . .
Connection at the logical level . . . . .
Connection at the physical level . . . .
Communicating across SNA connections .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
3
4
4
5
6
Chapter 3. Collecting information for a SNAP-IX configuration

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

Configuring a node . . . . . . . . . . . .
Configuring links . . . . . . . . . . . . .
Configuring a port . . . . . . . . . . . .
Configuring a link station . . . . . . . . .
Configuring a local LU for CICS local SNA support .
Configuring a partner LU on a remote node . . .
Configuring modegroups . . . . . . . . . .
Configuring conversation level security . . . . .
.
.
.
.
.
.
.
.
.
Chapter 5. Matching SNAP-IX parameters

Sample configuration for SNAP-IX . . . .
The sna_node.cfg file . . . . . . .
The sna_domn.cfg file . . . . . . .
with
. .
. .
. .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
CICS parameters
. . . . . . .
. . . . . . .
. . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
13
13
16
17
19
22
24
27
29
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
31
34
34
40
Chapter 6. Configuring VTAM with details of your CICS region . . . . . . 43

Defining your machine and CICS regions to VTAM . . . . . . . . . . . . 43
Defining modegroups to VTAM . . . . . . . . . . . . . . . . . . . 44
Chapter 7. Operating SNAP-IX . . . . . . . . . . . . . . .
Introduction to SNAP-IX operation . . . . . . . . . . . . . . .
Starting the node and connections . . . . . . . . . . . . . . .
Starting the node and connections that activate automatically at startup
Starting connections that do not activate at startup . . . . . . . .
Stopping the node and connections . . . . . . . . . . . . . .
Stopping the node and connections simultaneously . . . . . . .
Copyright IBM Corp. 1999, 2008
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
47
47
49
49
50
51
51
iii
Stopping connections without stopping

Starting, viewing, and stopping sessions
Starting sessions . . . . . . . .
Viewing sessions . . . . . . . .
Stopping sessions . . . . . . . .
the node
. . . .
. . . .
. . . .
. . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
51
52
52
52
53
Chapter 8. Problem determination

Logging . . . . . . . . . .
Tracing . . . . . . . . . . .
Viewing trace data . . . . .
for SNAP-IX
. . . . .
. . . . .
. . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
55
55
56
57
Appendix. Bibliography
SNA books . . . . .
SNAP-IX books . . . .
CICS books . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
59
59
59
59
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Trademarks and service marks . . . . . . . . . . . . . . . . . . . 62
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
iv
TXSeries for Multiplatforms: Using SNAP-IX for Solaris with CICS
Figures
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
SNAP-IX node main screen . . . . . . . . . . . . . . . . . . . . . .

An example heterogeneous network . . . . . . . . . . . . . . . . . . .
A simplified example heterogeneous network . . . . . . . . . . . . . . . .
Obtaining the address of a remote machine by using the ping and arp -a commands .
SNAP-IX node main screen with unconfigured node . . . . . . . . . . . . .
Node parameters screen . . . . . . . . . . . . . . . . . . . . . . .
SNAP-IX node main screen with configured node . . . . . . . . . . . . . .
Add to screen with indicated port . . . . . . . . . . . . . . . . . . . .
Token ring SAP screen . . . . . . . . . . . . . . . . . . . . . . .
SNAP-IX node main screen with added Token Ring port . . . . . . . . . . .
Token ring link station screen for LINKAIX . . . . . . . . . . . . . . . .
SNAP-IX node main screen with added link stations . . . . . . . . . . . . .
Local LU screen . . . . . . . . . . . . . . . . . . . . . . . . . .
Local LU Advanced screen . . . . . . . . . . . . . . . . . . . . . .
SNAP-IX node main screen with added local LU . . . . . . . . . . . . . .
Partner LU screen . . . . . . . . . . . . . . . . . . . . . . . . .
SNAP-IX node main screen with added partner LUs . . . . . . . . . . . . .
Mode screen . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modes screen . . . . . . . . . . . . . . . . . . . . . . . . . . .
define_node_config_file stanza. . . . . . . . . . . . . . . . . . . . .
define_node stanza . . . . . . . . . . . . . . . . . . . . . . . . .
define_tr_dlc stanza . . . . . . . . . . . . . . . . . . . . . . . . .
define_tr_port stanza . . . . . . . . . . . . . . . . . . . . . . . .
define_tr_ls stanzas (only selected fields are shown for each) . . . . . . . . .
define_local_lu stanza . . . . . . . . . . . . . . . . . . . . . . . .
define_partner_lu stanzas . . . . . . . . . . . . . . . . . . . . . .
define_mode stanzas . . . . . . . . . . . . . . . . . . . . . . . .
define_directory_entry stanzas . . . . . . . . . . . . . . . . . . . . .
define_defaults stanza . . . . . . . . . . . . . . . . . . . . . . . .
define_domain_config_file stanza . . . . . . . . . . . . . . . . . . . .
VTAM physical unit (PU) macro definition . . . . . . . . . . . . . . . . .
VTAM PATH macro definition . . . . . . . . . . . . . . . . . . . . .
VTAM logical unit (LU) definition . . . . . . . . . . . . . . . . . . . .
VTAM mode table macro . . . . . . . . . . . . . . . . . . . . . . .
Typical system configuration before the node, connections, and sessions are activated
Starting the node and connections . . . . . . . . . . . . . . . . . . .
Example sessions . . . . . . . . . . . . . . . . . . . . . . . . .
Logging screen . . . . . . . . . . . . . . . . . . . . . . . . . .
Tracing screen. . . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 1
. 3
. 8
. 9
. 14
. 15
. 16
. 17
. 18
. 19
. 20
. 21
. 22
. 23
. 24
. 26
. 27
. 28
. 29
. 34
. 35
. 35
. 36
. 37
. 38
. 38
. 39
. 40
. 40
. 41
. 43
. 44
. 44
. 45
. 48
. 50
. 53
. 55
. 57
vi
Tables
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
Getting started road map . . . . . . . . . . . . . . . . . . . . . . . . . . .

Conventions that are used in this book . . . . . . . . . . . . . . . . . . . . . .
Information required to define an example node . . . . . . . . . . . . . . . . . . .
Information required to define example links . . . . . . . . . . . . . . . . . . . .
Information required to define an example local system . . . . . . . . . . . . . . .
Information required to define example remote systems . . . . . . . . . . . . . . .
Information required to define example modegroups . . . . . . . . . . . . . . . . .
Information required to configure an example local node . . . . . . . . . . . . . . .
Information required to configure example links. . . . . . . . . . . . . . . . . . .
Information required to configure an example local system . . . . . . . . . . . . . .
Information required to configure example remote systems . . . . . . . . . . . . . .
Information required to configure example modegroups . . . . . . . . . . . . . . . .
Matching the Local LU parameter values of SNAP-IX with selected parameter values of local
CICS region CICSSOL and partner CICS region CICSESA . . . . . . . . . . . . . .
Matching the Remote LU parameter values of SNAP-IX with selected parameter values of local
CICS region CICSSOL and partner CICS region CICSESA . . . . . . . . . . . . . .
Matching the Mode parameter values of SNAP-IX with selected parameter values of local CICS
region CICSSOL and partner CICS region CICSESA . . . . . . . . . . . . . . . .
Matching the Local LU parameter values of SNAP-IX with selected parameter values of local
CICS region CICSSOL and partner CICS region CICSAIX. . . . . . . . . . . . . . .
Matching the Remote LU parameter values of SNAP-IX with selected parameter values of local
CICS region CICSSOL and partner CICS region CICSAIX. . . . . . . . . . . . . . .
Matching the Mode parameter values of SNAP-IX with selected parameter values of local CICS
region CICSSOL and partner CICS region CICSAIX . . . . . . . . . . . . . . . . .
. ix
. x
. 7
. 9
. 10
. 11
. 11
. 13
. 16
. 22
. 25
. 27
. 31
. 32
. 32
. 33
. 33
. 34
vii
viii
About this book

The Customer Information Control System (CICS) requires a Systems Network
Architecture (SNA) product to connect to an SNA network. This document describes
how to set up and use the SNAP-IX for Solaris product (which is referred to as
SNAP-IX throughout this document) with CICS for Solaris.
Topics include how to configure SNAP-IX, coordinate the configuration of SNAP-IX
with the configuration of CICS and its partner systems, operate SNAP-IX, and
investigate communications errors. Basic information about SNAP-IX and a review
of basic SNA terminology are also included.
Who should read this book

This book is designed for system administrators who configure, operate, and
manage SNA networks. The user should be familiar with the CICS and SNAP-IX
products, and have an understanding of SNA concepts. The TXSeries for
Multiplatforms Intercommunication Guide, the primary source of information on the
communications features of CICS, gives examples of configurations and advice on
systems design.
Document organization
Table 1. Getting started road map
If you want to...
Refer to...
Review basic information about SNAP-IX
Chapter 1, Introduction to SNAP-IX for

Solaris, on page 1
Review common SNA terminology
Chapter 2, Introduction to SNA, on page 3
Collect information for a new SNA

configuration
Chapter 3, Collecting information for a

SNAP-IX configuration, on page 7
Configure SNAP-IX
Chapter 4, Configuring SNAP-IX, on page

13
Review example configuration profiles
Chapter 5, Matching SNAP-IX parameters

with CICS parameters, on page 31
Communicate with EBCDIC mainframes
Chapter 6, Configuring VTAM with details of

your CICS region, on page 43
Start and stop nodes, connections, and

sessions
Chapter 7, Operating SNAP-IX, on page 47
Solve communications problems
Chapter 8, Problem determination for

SNAP-IX, on page 55
ix
Conventions used in this book

TXSeries for Multiplatforms documentation uses the following typographical and
keying 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. When
referring to graphical user interfaces (GUIs), bold also indicates
menus, menu items, labels, buttons, icons, and folders.
Monospace
Indicates text that you must enter at a command prompt. Monospace

also indicates screen text and code examples.
Italics
Indicates variable values that you must provide (for example, you
supply the name of a file for file_name). Italics also indicates
emphasis and the titles of books.
<>
Encloses the names of keys on the keyboard.
<Ctrl-x>
Where x is the name of a key, indicates a control-character

sequence. For example, <Ctrl-c> means hold down the Ctrl key
while you press the c key.
<Return>
Refers to the key labeled with the word Return, the word Enter, or
the left arrow.
Represents the UNIX command-shell prompt for a command that

does not require root privileges.
Represents the UNIX command-shell prompt for a command that

requires 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 command

and then press <Return>. For example, the instruction Enter the ls
command means type ls at a command prompt and then press
<Return>.
[]
Encloses optional items in syntax descriptions.
{}
Encloses lists from which you must choose an item in syntax

descriptions.
Separates items in a list of choices enclosed in { } (braces) in syntax

descriptions.
...
Ellipses in syntax descriptions indicate that you can repeat the

preceding item one or more times. Ellipses in examples indicate that
information was omitted from the example for the sake of brevity.
IN
In function descriptions, indicates parameters whose values are used

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

to return modified data to the calling routine. These parameters are
not used to pass data to the function. (Do not include the OUT
declaration in your code.)
Table 2. Conventions that are used in this book (continued)

Convention
Meaning
INOUT
In function descriptions, indicates parameters whose values are

passed to the function, modified by the function, and returned to the
calling routine. These parameters serve as both IN and OUT
parameters. (Do not include the INOUT declaration in your code.)
$CICS
Indicates the full path name of the location in which the CICS
product is installed; for example, /usr/lpp/cics on AIX. If the CICS
environment variable is set to the product path name, you can use
the examples exactly as shown in this book; otherwise, you must
replace all instances of $CICS with the CICS product path name.
CICS on Open
Systems
Refers collectively to the CICS product for all supported UNIX

platforms.
TXSeries for
Multiplatforms
Refers collectively to the CICS for AIX, CICS for HP-UX, CICS for
Solaris, and CICS for Windows products.
CICS
Refers generically to the CICS for AIX, CICS for HP-UX, CICS for
Solaris, and CICS for Windows products. Other CICS products in the
CICS Family are distinguished by their operating system (for
example, IBM mainframe-based CICS for the z/OS platform).
How to send your comments

Your feedback is important in helping to provide the most accurate and highest
quality information. If you have any comments about this book or any other
TXSeries documentation, send your comments by e-mail to idrcf@hursley.ibm.com.
Be sure to include the name of the book, the document number of the book, the
version of TXSeries, and, if applicable, the specific location of the information you
are commenting on (for example, a page number or table number).
About this book
xi
xii
Chapter 1. Introduction to SNAP-IX for Solaris

SNAP-IX for Solaris, which is referred to as SNAP-IX throughout this document, is a
comprehensive networking product that enables communications among many
types of devices across several 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. The product must be installed
on the same Solaris machine as is your CICS region.
The SNAP-IX product is administered by using either of two utilities:
v The command-line utility snaadmin
v The X Window Graphical User Interface (GUI) utility xsnaadmin
This document focuses on the use of the xsnaadmin utility. A typical system that is
configured by using this utility is shown in Figure 1.
Figure 1. SNAP-IX node main screen
From this node main screen, you can add, delete, modify, and manage all the
resources and components for the SNAP-IX node. The menu bar at the top of the
SNAP-IX node main screen contains five menus:
v Selection: Lets you control, modify, or delete an item that is currently selected in
the node main screen. You can start or stop the node, or zoom on it to display its
properties. You can also add a new item in the currently selected pane.
v Services: Provides the functions that are necessary for configuring the node for
common tasks. You can add or modify resources or get help for configuration or
management tasks.
v Diagnostics: Controls logging and tracing to help diagnose SNA network
problems.
v Windows: Controls the number of windows that display SNAP-IX information.
v Help: Provides information about using SNAP-IX.
The toolbar that is below the menus contains buttons that duplicate the most
popular options that the menus provide. When you point the mouse over a button, a
label displays its function. A one-line description of the function is also displayed in
the status bar that is at the bottom of the main window. The node button that is in
the upper right corner indicates the node state.
The SNAP-IX node main screen is divided into three panes:
v Connectivity and dependent LUs: Lists connectivity resources for the node,
including ports and link stations on each port.
v Independent local LUs: Lists independent Logical Units (LUs) for the node. For
each LU, it shows the sessions that are using the LU.
v Remote systems: Lists information about remote nodes and partner LUs. It also
shows session information for each remote node or partner LU.
Select a pane by clicking anywhere within it, or select specific resources within a
pane by clicking the line for the resource. The layout of the resources in the screen
shows the relationships among them.
After you have installed SNAP-IX, you must configure the product. If you are
familiar with SNA terminology, go to Chapter 3, Collecting information for a
SNAP-IX configuration, on page 7. Otherwise, review Chapter 2, Introduction to
SNA, on page 3, which explains the common SNA concepts that you encounter
during product configuration.
Chapter 2. Introduction to SNA

This section introduces the concepts and terminology that are related to Systems
Network Architecture (SNA). You must be familiar with these when you are using
CICS in an SNA environment.
SNA defines a set of rules that systems use to communicate. These rules define
the layout of the data that flows between the systems and the action that the
systems take when they receive the data. SNA does not specify how a system
implements the rules. A fundamental objective of SNA is to allow systems that have
very different internal hardware and software designs to communicate. The only
requirement is that the externals meet the rules of the architecture.
A sample network
Figure 2 shows a heterogeneous network that has CICS for Solaris system
intercommunicating with several different types of CICS regions.
Figure 2. An example heterogeneous network
Each CICS system uses its own platform-specific SNA product. CICS OS/2 uses
Communications Manager/2. CICS/400 uses OS/400 Intercommunication Facility
(ICF). IBM mainframe-based CICS works very closely with Virtual
Telecommunications Access Method (VTAM) to support SNA.
When you are configuring your CICS region to communicate with another CICS
system, you must understand the SNA product that the other system uses. Although
the two systems must agree on common parameters, the terminology that is used
for these parameters can differ.
SNA configuration
You can connect CICS systems in a network in many ways. If the data is
successfully transferred in the correct format, the CICS systems are unaware of the
network composition. SNA configuration is performed at two levels:
v The logical level, which incorporates the characteristics of the systems that are to
communicate.
v The physical level, which incorporates the linking of actual machines in the
network.
The next two sections, Connection at the logical level and Connection at the
physical level on page 5, describe these connection levels in detail, and introduce
you to the common SNA terminology that is associated with them. Communicating
across SNA connections on page 6 discusses communications across these
connections.
Connection at the logical level

Logical Unit (LU) is an SNA term that is used to describe a logical collection of
services that can be accessed from a network. SNA defines many different types of
LUs. A CICS region can be an LU, and devices like terminals and printers can also
be LUs. The type of LU that is used for CICS intersystem communications is LU
type 6.2.
Each LU is identified by a name of up to eight characters that is referred to as the
LU name. The LU name that describes the local region is called the local LU. LUs
that describes remote systems are called partner LUs. The local LU name for a
CICS on Open Systems or CICS for Windows NT system is configured in the
LocalLUName parameter of the Region Definitions (RD) for the region. An IBM
mainframe-based CICS system uses as its LU name (also referred to as a
NETNAME), the APPLID that is defined in the CICS system initialization table. The
LU name for a CICS OS/2 system is specified in the Communications Manager/2
Local LU definition, and the LU name for a CICS/400 system is defined in the APPL
parameter of the ADDCICSSIT command.
An SNA network also has a name of up to eight characters, called the network
name. The network name is sometimes referred to as the network id or the netid.
An LU can be uniquely identified by combining its LU name with the network name
of the network that owns it. The name is then referred to as the network-qualified
LU name or the fully qualified LU name. For example, if an LU that is named
CICSA belongs to a network that is named NETWORK1, its network-qualified LU
name is NETWORK1.CICSA.
For an LU to communicate with another LU, at least one session must be
established 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 though the network. The receiving
LU then sends a description of its capabilities to the initiating LU in the BIND
response. After the session is established, it can be used for several intersystem
requests. It remains active for as long as the two LUs and the network between
them are available.
When you configure your network, you can set up individual characteristics for the
different sessions that are established between a pair of LUs, such as the route that
is taken through the network. The set of characteristics for a session is referred to
as a modegroup or mode. A modegroup is identified by a modename of up to eight
characters.
All the sessions that are associated with a modegroup have the same
characteristics. The most important of these is contention. For each session
between two systems, one system is the contention winner, and the other system is
the contention loser. If both systems attempt to use the session at the same time,
the contention winner system is given priority. The contention loser must wait until
the contention winner is finished using the session. When you configure your
modegroups, ensure that your systems have a suitable balance of
contention-winner and -loser sessions. (Each system must have at least one
contention-winner session defined.)
Modegroups also define the number of sessions that are allowed on a connection
between two systems. Each session allows only one CICS intersystem request to
run at a time. Therefore, the number of sessions between the two systems affects
the number of concurrent intersystem requests that they can process. By controlling
the number of sessions between the two systems, you control the network traffic
that is generated by the two systems and prevent one system from flooding the
other with requests.
In addition to the intersystem requests that your applications make, CICS regions
send management requests among themselves. For this reason, define more than
one session between two CICS regions. A single session is not enough to handle
this traffic.
When defining a CICS region, you must also identify the required SNA
synchronization level. CICS used with SNAP-IX supports synchronization levels 0
and 1:
v Synchronization level 0 (NONE): SNA provides no synchronization support. The
application must code its own.
v Synchronization level 1 (CONFIRM): SNA provides the ability to send simple
acknowledgment requests.
Connection at the physical level

Each actual machine in a network is referred to as an SNA node. You must assign
to each a unique Control Point (CP) name, which is the name that the network uses
to communicate with it. This CP name can have one through eight characters that
consist of uppercase letters (A through Z) and numbers (0 through 9). It must be
unique within the SNA network. It must be different from all other CP and LU names
in the network.
Some large SNA networks use naming conventions that prevent name clashes.
Alternatively, you can often use the host name of your Solaris machine as the CP
name. Consult your network administrator for help when choosing names.
Associated with the CP name is the node identifier, which is also referred to as the
exchange identifier or XID. This eight-digit number identifies the Physical Unit (PU)
that is associated with the control point. A PU is a combination of hardware and
software that controls the links to other nodes. Several PU types with different
capabilities and responsibilities exist, such as:
v PU type 5: The best known example is an IBM mainframe processor that is
running VTAM. VTAM provides the support for the Systems Services Control
Point (SSCP) function that is defined in SNA.
Chapter 2. Introduction to SNA
v PU type 4: This is a communications controller, such as an Advanced

Communications Function for the Network Control Program (ACF/NCP), which
resides in the center of a network, routing and controlling the data flow between
machines.
v PU type 2: This is a small machine, such as an Advanced Program-to-Program
Communications (APPC) workstation. It can communicate directly only with a PU
type 4 or a PU type 5, and relies on these PUs to route the data to the correct
system.
v PU type 2.1: This is a more advanced PU type 2 that can also communicate with
other PU type 2.1 nodes directly. This node can support an independent LU. An
independent LU can establish a session with another LU without using VTAM.
SNAP-IX is a PU type 2.1 node.
PU type 2.1 nodes can support Advanced Peer-to-Peer Networking (APPN). This
support enables a node to search for an LU in the network, rather than requiring
you to preconfigure the remote LUs location locally. Two types of APPN nodes
exist: end nodes and network nodes. An end node can receive a search request for
an LU and respond, indicating whether the LU is local to the node or not. A network
node can issue search requests and respond to them. It maintains a dynamic
database that contains the results of the search requests. Support for APPN can
greatly reduce the maintenance work in an SNA network, especially if the network is
large or dynamic. SNAP-IX supports APPN. Alternatively, a low-entry networking
(LEN) node also can be connected to an APPN network or end node, but it does
not support APPN functions.
Each node has physical links, or connections, to other nodes so that every node is
connected to at least one other node. Data must sometimes travel along several
links to get from one system to another. These links can be of different types. For
example, IBM Token Ring, Synchronous Data Link Control (SDLC), and Ethernet
are all physical links. These types of links are collectively referred to as data link
control (DLC) protocols.
Communicating across SNA connections

CICS regions can communicate across SNA with any system that supports APPC.
SNAP-IX supports local SNA, which gives your CICS regions support for
synchronization levels 0 and 1, and provides the fastest SNA connectivity that CICS
offers. It enables CICS applications to communicate with every other member of the
CICS family, and enables IBM CICS Clients to use SNA to communicate with CICS.
To use local SNA support, SNAP-IX must be installed and configured on the same
machine as is the CICS region.

This following sections describe the information that you need to configure SNAP-IX
for use with CICS. You will find Systems Network Architecture (SNA) configuration
much easier if you collect this information before you start to create the SNA
definitions.
The steps that follow include:
1. Collecting information about
the local Solaris machine (node)

remote machines on page 8
a local CICS region on page 10
remote CICS regions on page 10
modegroups on page 11
Collecting information about the local Solaris machine (node)

This section describes the information that you need in order to register the Solaris
machine that is running SNAP-IX with the SNA network.
Your physical machine is referred to as an SNA node. You must assign to it a
Control Point (CP) name, which is the name that the network uses to communicate
with it. This CP name can have one through eight characters that consist of
uppercase letters (A through Z) and numbers (0 through 9). It must be unique within
the SNA network. It must be different from all other CP names and Logical Unit (LU)
names that are in the network.
Some large SNA networks use naming conventions that prevent name clashes. You
can often use the host name of your machine as the CP name. Consult your
network administrator for help when choosing names.
Associated with the CP name is the node identifier, which is also referred to as the
exchange identifier or XID. This eight-digit number identifies the Physical Unit (PU)
that is associated with the control point. Your network administrator can provide this
number.
You also need to know the name of the SNA network to which your SNA machine
and all the CICS regions that use your SNA machine belong. The SNA network
name can have one through eight characters that consist of uppercase letters (A
thjrough Z) and numbers (0 through 9).
Table 3 shows the information that you need in order to define an example local
node.
Table 3. Information required to define an example node
CP name
Node identifier
Local network name
SL000001
05F01234
MYSNANET
If you plan to communicate with remote systems through the Virtual

Telecommunications Access Method (VTAM), your CP name, node identifier, and
the LU name of your CICS region need to be defined to VTAM. Chapter 6,
Configuring VTAM with details of your CICS region, on page 43 shows some
example VTAM definitions.
Collecting information about remote machines

This section describes the information that you need in order to connect your local
Solaris machine to other machines (referred to as SNA nodes) in the SNA network.
You need to know the location of the remote CICS regions and systems with which
your local CICS for Solaris region is to communicate. You also need to know on
which machines these systems are running, and how those machines are
connected. It is often helpful to draw a schematic diagram of the network, such as
that shown in Figure 3.
Figure 3. A simplified example heterogeneous network
In this example, the CICS region called CICSSOL communicates with another
region, CICSAIX, that is running on a machine that is connected to the same local
area network (LAN). Region CICSSOL also communicates with two mainframe
CICS regions, CICSESA and CICSMVS. The CICSESA region is on a machine that
is connected to the same LAN as is CICSSOL. However, CICSMVS can be
contacted only through another machine. This distinction is important.
Note: When you define your connections to SNAP-IX, you need to include only
those machines that can be contacted directly (in this example, the machines
that are running CICSAIX and CICSESA). Connections to machines that are
indirectly accessed (in this example, the machine that are running
CICSMVS) are set up in definitions in the intermediate machines. As a result,
you need to consult the owners of those intermediate machines to arrange
the appropriate configurations.
To connect your local Solaris machine physically to other machines in the SNA
network, complete the following steps:
v Identify the machines to which you want to be connected and assign a
connection name to each connection. Choose meaningful names of up to eight
characters that consist of uppercase letters (A through Z) and numbers (0

through 9), to help you identify the machines that are at the remote end of the
connections. (These connection names will appear on the SNAP-IX node main
screen, and you will use them to stop and start connections. Meaningful names
make your network management easier.)
v Determine the type of network that is to be used to connect the machines.
Typical network types include:
IBM Token Ring LAN
Ethernet LAN
SDLC line
v Collect information about each remote node, for example:
Its Control Point (CP) name
Its Node identifier (XID)
v Determine the hardware (MAC) address of each remote machine. Methods for
determining these addresses depend on the type of machine:
View the hardware address of a remote NT machine under the Transports
section of the Network applet of its NT Diagnostics tool application.
View the address of a remote AIX machine by running the netstat -v
command on the AIX machine.
Obtain the address of a remote mainframe by contacting that systems SNA
network administrator. (The address that you need is probably that of a
network controller that is handling the network traffic on behalf of the
mainframe.)
Obtain the address of a remote machine that is connected by way of TCP/IP,
by using the ping command on your local Solaris machine to contact it. Then
use the command arp -a to list the addresses about which the address
resolution protocol (arp) knows. For example, Figure 4 shows how
10-00-5a-4b-3c-2d, the hardware address of aix5, is obtained.
C:\>ping aix5
Pinging aix5.cicsland.com [1.23.45.67] with 32 bytes of data:
Reply
Reply
Reply
Reply
from
from
from
from
1.23.45.67:
1.23.45.67:
1.23.45.67:
1.23.45.67:
bytes=32
bytes=32
bytes=32
bytes=32
time<10ms
time<10ms
time<10ms
time<10ms
TTL=255
TTL=255
TTL=255
TTL=255
C:\>arp -a
Interface: 1.23.45.987
Internet Address
Physical Address
1.23.4.6
08-00-70-81-92-03
1.23.45.67
10-00-5a-4b-3c-2d
Type
dynamic
dynamic
Figure 4. Obtaining the address of a remote machine by using the ping and arp -a commands
Table 4 shows the information that is collected for the example that is shown in
Figure 3 on page 8.
Table 4. Information required to define example links
Connection
name
Link type
Network name
Remote CP
name
Remote hardware
address
LINKVTAM
IBM Token Ring
MYSNANET
MYVTAM
400012345678
LINKAIX
IBM Token Ring
MYSNANET
AIX00005
10005A4B3C2D
Collecting information about a local CICS region

This section describes the information that you need in order to configure a local
CICS region. For the local CICS region, you need to know the following:
v The local Logical Unit (LU) name for the region. A local LU name can have one
to eight characters that consist of uppercase letters (A through Z) and numbers
(0 through 9). The local LU name that you choose must be unique within your
network. Many networks have naming conventions that help to prevent name
clashes. Consult your network administrator for advice when choosing local LU
names.
v The default modename to use when the region does not explicitly specify a
modename on an intersystem request. You can specify a modename explicitly on
an intersystem request by using the SNAModeName attribute of the CICS
Transaction Definitions (TD), or by using the PROFILE option of the EXEC CICS
ALLOCATE command. Alternatively, you can specify a modename in the
DefaultSNAModeName attribute of the CICS Communications Definitions (CD)
entry. This modename is used if you do not specify a modename explicitly in the
TD entry or in the EXEC CICS command. Identification of this parameter is
described further in the TXSeries for Multiplatforms Intercommunication Guide.
v Whether synchronization level 2 is supported. CICS local SNA does not support
synchronization level 2.
Table 5 shows the information that is required to define a CICS region called
CICSSOL. The default modename for this LU name is CICSISC0.
Table 5. Information required to define an example local system
Local LU name
Local LU alias
Synchronization
level 2?
CICS CD DefaultSNA
ModeName
CICSSOL
CICSSOL
No
CICSISC0
Collecting information about remote CICS regions

This section describes the information that you need to know about the remote
systems with which your CICS region is going to communicate. These remote
systems are commonly referred to as partner LUs.
For each partner LU, you need to know the following:
v Its LU name. An IBM mainframe-based CICS region uses as its LU name (also
referred to as a NETNAME), its APPLID that is defined in the CICS system
initialization table. The LU name for a CICS for OS/2 or CICS on Open Systems
region is specified in its local SNA products local LU definition. The LU name for
a CICS/400 region is in the APPL parameter of the ADDCICSSIT command.
v The name of the SNA network to which it belongs. A SNA network name can
have one to eight characters that consist of uppercase letters (A through Z) and
numbers (0 through 9).
If the partner LU is not on a machine that is defined as an Advanced
Peer-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 not
specify the CP name, your local machine cannot bind sessions to the partner LU.
10
v The level of security, if any, that is used for the communications. You can use
conversation-level security, which involves receiving a user ID from the remote
system. Refer to the TXSeries for Multiplatforms Intercommunication Guide for
more information.
Table 6 shows examples of data that is collected for remote CICS systems.
Table 6. Information required to define example remote systems
Partner LU name
Partner LU alias
Partner CP name
CICSESA
CICSESA
MYSNANET.MYVTAM
CICSMVS
CICSMVS
MYSNANET.MYVTAM
CICSAIX
CICSAIX
MYSNANET.AIX00005
Collecting information about modegroups

This section describes the information that you need in order to define the
modegroups (or modes) that are used on the SNA connections between your CICS
system and remote SNA systems.
When you configure your network, you can set up individual characteristics for the
different sessions that are established between a pair of LUs, such as the route that
is taken through the network. The set of characteristics for a session is referred to
as a modegroup or mode. All the sessions that are associated with a modegroup
have the same characteristics. A modegroup is identified by a modename of one to
eight characters that consist of uppercase letters (A through Z) and numbers (0
through 9).
You must define at least one modegroup to SNAP-IX. SNA connections can share
modegroup definitions. The session limits that are defined in a modegroup apply
independently to each connection that uses that modegroup. A connection can use
more than one modegroup. For example, suppose you have a connection that
handles fast intersystem requests for interactive users and slower intersystem
requests that send or receive large amounts of data. Simply define two
modegroups: one for the interactive requests (called modename CICSISC0), and
the other, for the slower data transfer requests (called modename CICSISC1).
In addition to the intersystem requests that your applications make, CICS regions
send management requests among themselves. For this reason, define more than
one session between two CICS regions. A single session is not enough to handle
this traffic.
Table 7 shows the information that you need in order to define two modegroups.
Remember that the modegroups that are used on a connection must be defined
with consistent session limits on both systems. If SNAP-IX uses VTAM to
communicate with the remote system, you must include a MODEENT definition for
the modename in the VTAM tables. Refer to Chapter 6, Configuring VTAM with
details of your CICS region, on page 43 for an example of a MODEENT definition.
Table 7. Information required to define example modegroups
Modename
Max sessions
Min winners
CICSISC0
10
CICSISC1
11
System-defined SNASVCMG and CPSVCMG modegroups

SNA network connections that use parallel sessions have a standard modegroup
called SNASVCMG. This is a system-defined modegroup reserved for use by SNA
management programs. Do not attempt to define this modegroup in SNAP-IX or use
it for your CICS intersystem requests.
APPN systems also use a modegroup called CPSVCMG. This is reserved for APPN
management programs. Again, do not attempt to define this modegroup or use it for
your CICS intersystem requests.
12
Chapter 4. Configuring SNAP-IX

The following sections describe how to configure SNAP-IX:
v Configuring a node
v
v
v
v
v
v
Configuring
Configuring
Configuring
Configuring
Configuring
Configuring
a port on page 17
a link station on page 19
a local LU for CICS local SNA support on page 22
a partner LU on a remote node on page 24
modegroups on page 27
conversation level security on page 29
Ensure that you have read Chapter 3, Collecting information for a SNAP-IX
configuration, on page 7 and have all the information that you need about the
systems that you want to connect across a Systems Network Architecture (SNA)
network.
In the configuration example that is presented in this section, it is assumed that
SNAP-IX is installed and has been enabled by using the sna start command.
Note: Normally, the sna start command needs to be run only once after
installation. SNAP-IX updates the startup file to include the sna start
command. This ensures that SNAP-IX activates automatically at system
startup. See the SNAP-IX Installation Guide and SNAP-IX Administration
Guide for more information about SNAP-IX installation.
The examples that follow are not designed to cover every aspect of configuring
SNAP-IX. Only those fields that are particularly relevant to CICS are discussed.
Using default values works well for many other fields. If you require more
information, you can see a description of each field by selecting the Help button on
the configuration window in which the field appears.
Configuring a node
This section describes how to define your local machine. It uses the values that are
shown in Table 8 in an example local machine configuration.
Table 8. Information required to configure an example local node
CP name
Node identifier
Local network name
SL000001
05F01234
MYSNANET
To configure the node, follow these steps:

1. Ensure that SNAP-IX is active, and start the administration utility xsnaadmin by
issuing the following command:
/opt/sna/bin/X11/xsnaadmin
The SNAP-IX node main screen is displayed, along with the XSnaadmin
message box, which asks you to configure the local node.
2. Click Cancel in the XSnaadmin message box.
Note: Clicking OK in the XSnaadmin message box brings up a SNAP-IX node
configuration Task Sheet that can lead you through node configuration.
13
For the purposes of this example, however, click Cancel instead.

The SNAP-IX node main screen is displayed, as shown in Figure 5.
Figure 5. SNAP-IX node main screen with unconfigured node
3. From the Services menu, click the Configure node parameters option. The
Node parameters screen appears.
4. Select the node type for the node that you are defining, by clicking the APPN
support selection box (in this example, select the LEN node option).
5. In the Control point name field, enter the SNA network name in the first box
and the CP name in the second (in this example, MYSNANET and SL000001).
6. In the Control point alias field, enter the CP name (in this example, SL000001).
7. In the Node ID field, enter the first three characters of the node identifier (XID)
in the first box, and the next five characters of the XID in the second box (in this
example, 05F and 01234).
14
8. Enter a description if desired. Your screen now appears as shown in Figure 6.
Figure 6. Node parameters screen
9. Click OK. SNAP-IX creates a default local LU that is based on this node, which
appears in the Independent local LUs pane on the SNAP-IX node main
screen, as shown in Figure 7 on page 16.
15
Figure 7. SNAP-IX node main screen with configured node
Configuring links
This section describes how to define links to other machines in the SNA network. It
uses the values that are given in Table 9 in an example configuration.
Table 9. Information required to configure example links
16
Connection
name
Link type
LINKVTAM
LINKAIX
Network name
Remote CP
name
Remote
hardware
address
IBM Token Ring MYSNANET
MYVTAM
400012345678
IBM Token Ring MYSNANET
AIX00005
10005A4B3C2D
Before you can connect to other machines, you must configure a port. The
xsnaadmin utility automatically configures the associated data link control (DLC)
device driver when the port is configured. The DLC device driver controls the use of
the network connection to your machine. The port and DLC are configured
separately when you use the command-line administration program.
Configuring a port
To configure a port, use the following procedure:
1. From the SNAP-IX node main screen that is shown in Figure 7 on page 16,
click anywhere within the Connectivity and dependent LUs pane to highlight
it.
2. Click the Add button. The Add to screen is displayed.
3. Click the Port using button to display a list of options. For this example, select
the SunLink TRI/S Adapter option, as shown in Figure 8.
Figure 8. Add to screen with indicated port
4. Click OK on the Add to screen. The Token ring SAP screen is displayed.
5. For this example, clear the Use HPR on implicit links option and ensure that
the Initially active option is selected.
6. Enter a description if desired. Accept the default values for all other attributes.
Your screen now appears as shown in Figure 9 on page 18.
17
Figure 9. Token ring SAP screen
7. Click OK to return to the SNAP-IX node main screen, which now appears as
shown in Figure 10 on page 19.
18
Figure 10. SNAP-IX node main screen with added Token Ring port
Configuring a link station

At this point, you have configured a port and DLC device driver. (In this example,
the xsnaadmin utility configured the DLC automatically when you configured the
port.) You can now connect your machine to other machines by using link station
definitions. Use the following procedure to configure a link station called LINKAIX,
which connects a machine that is running CICS for Solaris to a machine that is
running CICS for AIX:
1. From the SNAP-IX node main screen that is shown in Figure 10, click the
TRSAPO entry in the Connectivity and dependent LUs pane.
3. Ensure that the Link station to port TRSAPO option is selected and click OK.
The Token ring link station screen is displayed.
19
4. In the Name field, enter the link name (in this example, LINKAIX).
5. Accept the default value of TRSAPO in the SNA port name field.
6. Click the Activation option button. Select the On node startup option from
the list that is displayed.
7. In the LU traffic section, select the Independent only option.
8. In the Independent LU traffic sections Remote node field, enter the network
name (in this example, MYSNANET) in the first box and the control point name of
the remote node (in this example, AIX00005) in the second box.
9. In the Contact information section, do the following:
a. Enter the remote machines MAC address (in this example, 10005A4B3C2D)
in the MAC address field.
b. Accept the default value in the SAP number field.
10. Enter a description, if desired. Your screen now appears as shown in
Figure 11.
Figure 11. Token ring link station screen for LINKAIX
11. Click OK.
20
12. A message box is displayed that asks whether you want to add the remote
node definition to your configuration automatically. Click OK.
13. A message box is displayed that informs you that the remote node has been
defined. Click OK to return to the SNAP-IX node main screen.
14. Follow similar steps to configure the LINKVTAM link station, which connects a
machine that is running CICS for Solaris to a machine that is running CICS for
VSE/ESA. Your screen now appears as shown in Figure 12.
Figure 12. SNAP-IX node main screen with added link stations
21
Configuring a local LU for CICS local SNA support

You need to define a unique local LU to configure a CICS system. This section
uses the values that are given in Table 10 in an example configuration.
Table 10. Information required to configure an example local system
Local LU name
Local LU alias
Synchronization level 2?
CICSSOL
CICSSOL
No
To define a local LU name for CICS local SNA support, use the following procedure:
1. From the SNAP-IX node main screen that is shown in Figure 12 on page 21,
click anywhere within the Independent local LUs pane to highlight it.
2. Click the Add button. The Local LU screen is displayed.
3. Enter the LU name (for this example, CICSSOL) in the LU name field.
4. Click the box that is beside the LU alias field. Because the LU alias must match
the LU name, the xsnaadmin utility automatically inserts the entry from the LU
name field into the LU alias field.
5. Enter a description if desired. Your screen now appears as shown in Figure 13.
Figure 13. Local LU screen
6. Click the Advanced button.

7. Ensure that the Support Syncpoint option is unselected, as shown in Figure 14
on page 23. (The default value is unselected.)
22
Figure 14. Local LU Advanced screen
8. Click OK.
9. Click OK to return to the SNAP-IX node main screen, which now appears as
shown in Figure 15 on page 24.
23
Figure 15. SNAP-IX node main screen with added local LU
Configuring a partner LU on a remote node

This section describes how to define the remote systems with which your CICS
region communicates across the SNA network. It uses the values that are given in
Table 11 on page 25 in an example configuration.
Note: SNAP-IX permits you to configure conversation-level security, which involves
receiving a user ID from the remote system, on a separate screen. You can
access this screen by selecting the APPC option from the Services menu on
the SNAP-IX node main screen, then selecting the Security option and the
Conversation level security option from the displayed submenus. For more
information about how to configure conversation-level security, see the
SNAP-IX Administration Guide and the TXSeries for Multiplatforms
24
Intercommunication Guide.
Table 11. Information required to configure example remote systems
Partner LU name
Partner LU alias
Partner CP name
CICSESA
CICSESA
MYSNANET.MYVTAM
CICSMVS
CICSMVS
MYSNANET.MYVTAM
CICSAIX
CICSAIX
MYSNANET.AIX00005
To configure a partner LU, use the following procedure:

1. From the SNAP-IX node main screen that is shown in Figure 15 on page 24, in
the Remote systems pane, click the remote node that will contain the partner
LU (in this example, MYSNANET.MYVTAM).
3. Ensure that the Define partner LU on node MYSNANET.MYVTAM option is
selected and click OK. The Partner LU screen is displayed.
4. Enter the partner LU name (in this example, CICSESA) in the second box to the
right of the Partner LU name field.
5. Click the boxes that are beside the Alias and Uninterpreted name fields. They
fill in automatically.
6. Ensure that the Supports parallel sessions option is selected.
7. Add a description if desired, and accept any other default values. Your screen
now appears as shown in Figure 16 on page 26.
25
Figure 16. Partner LU screen
8. Click OK to return to the SNAP-IX node main screen.

9. Follow similar steps to define the CICSMVS and CICSAIX partner LUs. Your
screen now appears as shown in Figure 17 on page 27.
26
Figure 17. SNAP-IX node main screen with added partner LUs
Configuring modegroups
This section describes how to configure modegroups. It uses the values that are
given in Table 12 in an example configuration.
Table 12. Information required to configure example modegroups
Modename
Max sessions
Min winners
CICSISC0
10
CICSISC1
To define a modegroup, use the following procedure:

1. From the SNAP-IX node main screen that is shown in Figure 17, select APPC
from the Services menu.
2. Select the Modes option from the menu that is associated with the APPC
option. The Modes screen is displayed.
27
3. Click the New button on the Modes screen. The Mode screen is displayed.
4. Enter the modename (in this example, CICSISC0) in the Name field.
5. In the Session limits section, enter 10 in the Initial field and 5 in the Min.
con. winner sessions and Auto-activated sessions fields.
6. Enter a description if desired, and accept the default values in the other fields.
Your screen now appears as shown in Figure 18.
Figure 18. Mode screen
7. Click OK.
8. Make CICSISC0 the default modename by clicking the CICSISC0 modename
on the Modes screen to highlight it, then clicking the Make default button.
28
9. Follow similar steps to configure mode CICSISC1. The modes CICSISC0 and
CICSISC1 now appear on the listing in the Modes screen, as shown in
Figure 19.
Note: Do not make CICSISC1 the default modename.
Figure 19. Modes screen
10. Click Done in the Modes screen to return to the SNAP-IX node main screen.
Configuring conversation level security

SNAP-IX permits you to configure conversation-level security, which involves
receiving a user ID from the remote system, on a separate screen. You can access
this screen by selecting the APPC option from the Services menu on the SNAP-IX
node main screen, then selecting the Security option and the Conversation level
security option from the displayed submenus. For more information about how to
configure conversation-level security, see the SNAP-IX Administration Guide and
the TXSeries for Multiplatforms Intercommunication Guide.
29
30
Chapter 5. Matching SNAP-IX parameters with CICS

parameters
After configuring SNAP-IX, configure the CICS communications resources. This
process is described in detail in the TXSeries for Multiplatforms Intercommunication
Guide. Some of the parameter values that you specify when configuring CICS must
match those that you have used to configure SNAP-IX. This section describes the
parameter values that must match.
Table 13, Table 14 on page 32, and Table 15 on page 32 show examples of the
parameter values that are defined in SNAP-IX. These values must match those of a
local CICS region, CICSSOL, that is connected to a remote CICS region,
CICSESA. Table 13 shows the Local LU parameter values that are defined in
SNAP-IX. These values must also match. Table 14 on page 32 shows the Remote
LU parameter values that must match. Table 15 on page 32 shows the Mode
parameter values that must match.
Similar matches must also be created among parameter values that are defined in
SNAP-IX, the local CICS region CICSSOL, and the remote CICS region CICSMVS.
SNAP-IX and the two CICS regions are represented in the columns; read across
the rows to see the matching parameter values. For example, in Table 13, the value
CICSSOL must be used in the LU Name parameter in SNAP-IX, the LocalLUName
parameter in the Region Definitions (RD) of region CICSSOL, and the NETNAME
parameter of region CICSESA.
Note: Some parameter values need to match only between two of the columns.
For example, in Table 13, the value SOL must match only in the LocalSysId
parameter in the Region Definitions (RD) of region CICSSOL and in the
CONNECTION parameter of region CICSESA. No match is required in any
Local LU parameters in SNAP-IX. In cases such as this, the term Not
applicable appears on the line in the column where no match is needed.
Table 13. Matching the Local LU parameter values of SNAP-IX with selected parameter
values of local CICS region CICSSOL and partner CICS region CICSESA
SNAP-IX
Region CICSSOL
Region CICSESA
Local LU parameters
Region Definitions (RD)
Network Name=MYSNANET
LocalNetworkName=
MYSNANET
Not applicable
LU Name=CICSSOL
LocalLUName=CICSSOL
NETNAME=CICSSOL
LocalSysId=SOL
CONNECTION=SOL
LU Alias=CICSSOL
Not applicable
Communications Definitions
(CD)
CESA:
31
values of local CICS region CICSSOL and partner CICS region CICSESA (continued)
SNAP-IX
Region CICSSOL
Region CICSESA
Support Syncpoint=No
ConnectionType=local_sna
Not applicable
GatewayName=
Not applicable
Listener Definitions (LD)

LOCALSNA:
Protocol=SNA
Not applicable
Table 14. Matching the Remote LU parameter values of SNAP-IX with selected parameter
values of local CICS region CICSSOL and partner CICS region CICSESA
SNAP-IX
Region CICSSOL
Remote LU parameters
(CD)
Region CICSESA
CESA:
RemoteNetwork
Name=MYSNANET
Not applicable
LU Name=CICSESA
RemoteLUName=CICSESA
Not applicable
LU Alias=CICSESA
Table 15. Matching the Mode parameter values of SNAP-IX with selected parameter values
of local CICS region CICSSOL and partner CICS region CICSESA
SNAP-IX
Region CICSSOL
Mode parameters
(CD)
Region CICSESA
CESA:
Modename=CICSISC0
DefaultSNAModeName=
CICSISC0
SESSION:OPEN0
MODENAME=CICSISC0
Transaction Definitions (TD)

BULK:
Modename=CICSISC1
SNAModeName=CICSISC1
SESSION:OPEN1
MODENAME=CICSISC1
Table 16 on page 33, Table 17 on page 33, and Table 18 on page 34 show
examples of how the parameter values that are defined in SNAP-IX must match
those of a local CICS region, CICSSOL, that is connected to a remote CICS on
Open Systems region, CICSAIX. Much of the configuration has not changed from
the examples that are shown in Table 13 on page 31, Table 14, and Table 15. The
required changes follow:
v A new remote LU definition for CICSAIX in SNAP-IX.
v A new Communications Definitions (CD) entry, CAIX, in the CICSSOL region.
v New Communications Definitions (CD) and Region Definitions (RD) in the remote
region CICSAIX. (The CICSISC1 mode is not used by intersystem requests that
are sent to CICSAIX.)
32
SNAP-IX and the two CICS regions are represented in the columns; read across
the rows to see the matching parameter values. For example, in Table 16, the value
CICSSOL must be used in the LU Name parameter in SNAP-IX, the LocalLUName
parameter in the Region Definitions (RD) of region CICSSOL, and the
RemoteLUName parameter of region CICSAIX.
Note: Some parameter values need to match only between two of the columns.
For example, in Table 18 on page 34, the value CICSISC0 must match only in
the Modename parameter in SNAP-IX, and in the DefaultSNAModeName
parameter in the Communications Definitions (CD) of region CICSSOL. No
match is required in any parameters in region CICSAIX. In cases such as
this, the term Not applicable appears on the line in the column in which no
match is needed.
values of local CICS region CICSSOL and partner CICS region CICSAIX
SNAP-IX
Region CICSSOL
Region CICSAIX
Local LU parameters
Communications
Definitions (CD)
COSSOL:
LocalNetworkName=
MYSNANET
RemoteNetworkName=
MYSNANET
LU Name=CICSSOL
LocalLUName=CICSSOL
RemoteLUName=CICSSOL
LU Alias=CICSSOL
Communications
Definitions (CD)
CAIX:
Support Syncpoint=no
ConnectionType=local_sna
Not applicable
GatewayName=
Not applicable

LOCALSNA:
Protocol=SNA
Not applicable
Table 17. Matching the Remote LU parameter values of SNAP-IX with selected parameter
values of local CICS region CICSSOL and partner CICS region CICSAIX
SNAP-IX
Region CICSSOL
Region CICSAIX
Remote LU parameters
Communications
Definitions (CD)
CAIX:
Network Name= MYSNANET RemoteNetworkName=
MYSNANET
LocalNetworkName=
MYSNANET
LU Name=CICSAIX
LocalLUName=CICSAIX
RemoteLUName=CICSAIX
LU Alias=CICSAIX
Chapter 5. Matching SNAP-IX parameters with CICS parameters
33
Table 18. Matching the Mode parameter values of SNAP-IX with selected parameter values
of local CICS region CICSSOL and partner CICS region CICSAIX
SNAP-IX
Region CICSSOL
Mode parameters
Communications
Definitions (CD)
Region CICSAIX
CAIX:
Modename=CICSISC0
DefaultSNAModeName=
CICSISC0
Not applicable
Sample configuration for SNAP-IX

The following figures provide the resulting files that were produced from the
SNAP-IX configuration that was performed in Chapter 4, Configuring SNAP-IX, on
page 13.
The sna_node.cfg file

The following stanzas are defined:
v define_node_config_file stanza in Figure 20
v define_node stanza in Figure 21 on page 35
v define_tr_dlc stanza in Figure 22 on page 35
v define_tr_port stanza in Figure 23 on page 36
v define_tr_ls stanzas in Figure 24 on page 37
v define_local_lu stanza in Figure 25 on page 38
v define_partner_lu stanzas in Figure 26 on page 38
v define_mode stanzas in Figure 27 on page 39
v define_directory_entry stanzas in Figure 28 on page 40
v define_defaults stanza in Figure 29 on page 40
Note: In this document, the stanza groups are displayed in separate figures. In the
actual sna_node.cfg file, each stanza is separated from the next by a blank
line.
[define_node_config_file]
major_version = 5
minor_version = 1
update_release = 1
revision_level = 188
Figure 20. define_node_config_file stanza
34
[define_node]
node_name = SL000001
description = Control point
fqcp_name = MYSNANET.SL000001
node_type = LEN_NODE
mode_to_cos_map_supp = NO
mds_supported = YES
node_id = <05f01234>
max_locates = 1500
dir_cache_size = 255
max_dir_entries = 0
locate_timeout = 0
reg_with_nn = YES
reg_with_cds = YES
mds_send_alert_q_size = 100
cos_cache_size = 24
tree_cache_size = 40
tree_cache_use_limit = 40
max_tdm_nodes = 0
max_tdm_tgs = 0
max_isr_sessions = 1000
isr_sessions_upper_threshold = 900
isr_sessions_lower_threshold = 800
isr_max_ru_size = 16384
isr_rcv_pac_window = 8
store_endpt_rscvs = NO
store_isr_rscvs = NO
store_dlur_rscvs = NO
dlur_support = NO
pu_conc_support = YES
nn_rar = 128
max_ls_exception_events = 0
ms_support = NORMAL
queue_nmvts = YES
ptf_flags = NONE
Figure 21. define_node stanza
[define_tr_dlc]
dlc_name = TOKEN0
description = ""
neg_ls_supp = YES
card_type = SPARC_TRI_S
initially_active = NO
adapter_number = 0
Figure 22. define_tr_dlc stanza
35
[define_tr_port]
port_name = TRSAP0
description = Token Ring port
dlc_name = TOKEN0
port_type = PORT_SATF
port_number = 0
max_rcv_btu_size = 4105
tot_link_act_lim = 64
inb_link_act_lim = 0
out_link_act_lim = 0
ls_role = LS_NEG
implicit_dspu_services = NONE
implicit_dspu_template = ""
implicit_ls_limit = 0
act_xid_exchange_limit = 9
nonact_xid_exchange_limit = 5
ls_xmit_rcv_cap = LS_TWS
max_ifrm_rcvd = 7
target_pacing_count = 7
max_send_btu_size = 4105
mac_address = <000000000000>
lsap_address = 0x04
implicit_cp_cp_sess_support = NO
implicit_limited_resource = NO
implicit_deact_timer = 30
implicit_hpr_support = NO
implicit_link_lvl_error = NO
effect_cap = 3993600
connect_cost = 0
byte_cost = 0
security = SEC_NONSECURE
prop_delay = PROP_DELAY_LAN
user_def_parm_1 = 128
initially_active = YES
window_inc_threshold = 1
test_timeout = 10
test_timer_retry = 5
xid_timer = 10
xid_timer_retry = 5
ack_timeout = 5000
p_bit_timeout = 5000
t2_timeout = 100
rej_timeout = 10
busy_state_timeout = 30
idle_timeout = 30
max_retry = 3
Figure 23. define_tr_port stanza
36
[define_tr_ls]
ls_name = LINKAIX
description = Link to AIX
port_name = TRSAP0
adj_cp_name = MYSNANET.AIX00005
adj_cp_type = END_NODE
mac_address = <10005a4b3c2d>
lsap_address = 0x04
auto_act_supp = NO
tg_number = 0
limited_resource = NO
solicit_sscp_sessions = NO
pu_name = <0000000000000000>
disable_remote_act = NO
default_nn_server = NO
dspu_services = NONE
dspu_name = <0000000000000000>
dlus_name = <0000000000000000000000000000000000>
bkup_dlus_name = <0000000000000000000000000000000000>
hpr_supported = NO
hpr_link_lvl_error = NO
link_deact_timer = 30
use_default_tg_chars = YES
ls_attributes = SNA
adj_node_id = <00000000>
local_node_id = <00000000>
cp_cp_sess_support = NO
effect_cap = 3993600
connect_cost = 0
byte_cost = 0
security = SEC_NONSECURE
:
:
:
:
initially_active = YES
react_timer = 30
react_timer_retry = 65535
test_timeout = 10
test_timer_retry = 5
xid_timer = 10
xid_timer_retry = 5
ack_timeout = 5000
p_bit_timeout = 5000
t2_timeout = 100
rej_timeout = 10
busy_state_timeout = 30
idle_timeout = 30
max_retry = 3
[define_tr_ls]
ls_name = LINKVTAM
description = Link to VTAM
port_name = TRSAP0
adj_cp_name = MYSNANET.MYVTAM
adj_cp_type = END_NODE
mac_address = <400012345678>
lsap_address = 0x04
auto_act_supp = NO
tg_number = 0
limited_resource = NO
solicit_sscp_sessions = NO
pu_name = <0000000000000000>
disable_remote_act = NO
default_nn_server = NO
dspu_services = NONE
dspu_name = <0000000000000000>
dlus_name = <0000000000000000000000000000000000>
bkup_dlus_name = <0000000000000000000000000000000000>
hpr_supported = NO
hpr_link_lvl_error = NO
link_deact_timer = 30
use_default_tg_chars = YES
ls_attributes = SNA
adj_node_id = <00000000>
37
[define_local_lu]
lu_alias = CICSSOL
list_name = ""
description = CICS Region CICSSOL
lu_name = CICSSOL
lu_session_limit = 0
pu_name = <0000000000000000>
nau_address = 0
default_pool = NO
syncpt_support = NO
lu_attributes = NONE
sscp_id = 0
disable = NO
sys_name = ""
timeout = 60
back_level = NO
Figure 25. define_local_lu stanza
[define_partner_lu]
plu_alias = CICSAIX
description = CICS for AIX region
fqplu_name = MYSNANET.CICSAIX
plu_un_name = CICSAIX
parallel_sess_supp = YES
max_mc_ll_send_size = 0
conv_security_ver = NO
[define_partner_lu]
plu_alias = CICSESA
description = CICS for VSE/ESA region
fqplu_name = MYSNANET.CICSESA
plu_un_name = CICSESA
[define_partner_lu]
plu_alias = CICSMVS
description = CICS for MVS/ESA region
fqplu_name = MYSNANET.CICSMVS
plu_un_name = CICSMVS
Figure 26. define_partner_lu stanzas
38
[define_mode]
mode_name = CICSISC0
description = Mode CICSISC0
max_neg_sess_lim = 32767
plu_mode_session_limit = 10
min_conwin_src = 5
min_conloser_src = 0
auto_act = 5
receive_pacing_win = 4
max_receive_pacing_win = 0
default_ru_size = YES
max_ru_size_upp = 1024
max_ru_size_low = 0
cos_name = #CONNECT
[define_mode]
description = ""
max_neg_sess_lim = 4
plu_mode_session_limit = 4
min_conwin_src = 2
mIn_conloser_src = 0
auto_act = 2
receive_pacing_win = 4
max_receive_pacing_win = 0
default_ru_size = YES
max_ru_size_upp = 1024
max_ru_size_low = 0
cos_name = #CONNECT
Figure 27. define_mode stanzas
39
[define_directory_entry]
resource_name = MYSNANET.MYVTAM
resource_type = ENCP_RESOURCE
description = (Auto defined - remote node)
parent_name = <0000000000000000000000000000000000>
parent_type = ENCP_RESOURCE
resource_name = MYSNANET.MYVTAM
resource_type = LU_RESOURCE
description = (Auto defined - default LU)
parent_name = MYSNANET.MYVTAM
resource_name = MYSNANET.CICSESA
description = CICS for VSE/ESA region
resource_name = MYSNANET.CICSMVS
description = CICS for MVS/ESA region
resource_name = MYSNANET.AIX00005
resource_type = ENCP_RESOURCE
description = (Auto defined - remote node)
parent_name = <0000000000000000000000000000000000>
resource_name = MYSNANET.CICSAIX
description = CICS for AIX region
parent_name = MYSNANET.AIX00005
resource_name = MYSNANET.AIX00005
description = (Auto defined - default LU)
parent_name = MYSNANET.AIX00005
Figure 28. define_directory_entry stanzas
[define_defaults]
description = ""
implicit_plu_forbidden = NO
specific_security_codes = NO
limited_timeout = 20
Figure 29. define_defaults stanza
The sna_domn.cfg file

The following stanza is defined:
40
[define_domain_config_file]
major_version = 5
minor_version = 1
update_release = 1
revision_level = 4
comment = ""
updating = N
Figure 30. define_domain_config_file stanza
41
42
Chapter 6. Configuring VTAM with details of your CICS region

The Virtual Telecommunications Access Method (VTAM) is an IBM product that runs
on a mainframe and controls access to CICS products such as CICS Transaction
Server for z/OS and CICS for VSE/ESA. VTAM uses the services of the Network
Control Program (NCP) product to connect the mainframe to the network.
Therefore, the NCP possibly needs to be updated to enable it will pass requests
from your Systems Network Architecture (SNA) machine to VTAM and to the remote
system beyond.
Code VTAM and NCP definitions by using macros. The following sections show a
few example definitions. Use these examples for guidance only; they cannot cover
the extensive range of network configurations that are possible. Refer to VTAM and
NCP documentation for more information and examples of VTAM and NCP
definitions.
Defining your machine and CICS regions to VTAM

The VTAM Physical Unit (PU) macro defines the machine on which your SNA
product is running. Figure 31 provides an example of a PU macro for a PC that is
running CICS for Solaris and is connected to the network with an IBM Token Ring:
***********************************************************************
*
SL000001 PU
ADDR=C1,
STATION ADDRESS (CAN BE ANY VALUE) X
IDBLK=05F,
071 = RS/6000, 05D = OS/2 or NT
X
IDNUM=01234,
PART OF XID.
X
DISCNT=NO,
HANG-UP ON LU LOGOFF
X
MAXDATA=265,
MAX I-FIELD SIZE
X
MAXOUT=7,
RECEIVE PACING WINDOW
X
MAXPATH=1,
NO OF DIAL-OUT PATHS
X
MODETAB=MTDFLT,
MODETAB IF LU DOES NOT SPECIFY ONE X
SSCPFM=FSS,
LUs NOT SUPPORTING CHAR-CODED MSGS X
PACING=0,
X
VPACING=0,
X
PUTYPE=2,
X
ISTATUS=ACTIVE
*
***********************************************************************
Figure 31. VTAM physical unit (PU) macro definition
Values that are coded in the PU definition for your machine must match the
definitions that you create in your SNA product. For example, VTAM can use either
an Exchange Identifier (also known as an XID or node identifier) or a control point
(CP) name to match a request from your machine to its PU definition. The PU
definition that is shown in Figure 31 has an XID defined. This consists of the IDBLK
and IDNUM values. Therefore, the SNA product is configured with an XID of
05F01234.
You can code the CP name on a PU definition by using the CPNAME parameter.
This coding is not required in the example in Figure 31 because the XID is coded. If
your SNA product allows you to configure both an XID and a CP name, but you
specify only an XID in the VTAM PU definition, specify the same PU name
(SL000001 in this example) as the CP name. This makes it easier for you to
associate the VTAM PU definition with your machine. However, if you use the
CPNAME parameter in the PU definition, that CP name must be different from the
PU name.
43
When you are setting up a link between your machine and VTAM, you must decide
which machine is to issue the command that establishes the link. One machine
must call, and the other must listen. It is usual for VTAM to listen and for your
machine to call. However, if you want to set up VTAM so that it calls your machine,
VTAM needs to know the address of your machine. This address is specified in a
PATH definition. The PATH definition is coded just after the PU definition.
***********************************************************************
*
SU01
PATH GRPNM=SUN,
ECLTYPE=LOGICAL group in NCP X
DIALNO=01044000012345678,
X
GID=1,
X
PID=1,
X
USE=YES
*
***********************************************************************
Figure 32. VTAM PATH macro definition
Following the PU and, if defined, the PATH macro definitions, are the logical unit
(LU) definitions. The LUs are in the machines that are defined in the PU definition,
and are configured in the SNA product in those machines.
***********************************************************************
*
CICSSOL LU
LOCADDR=0,ISTATUS=ACTIVE,MODETAB=MTCICS
*
***********************************************************************
Figure 33. VTAM logical unit (LU) definition
The LOCADDR=0 parameter in the LU definition indicates that the regions LU is

independent. This enables it to communicate with other independent LUs without
using VTAM. The MODETAB parameter specifies the name of the VTAM mode table
that defines all the modegroups (modenames) that the CICS region uses. Examples
of mode table entries are shown in Figure 34 on page 45.
Defining modegroups to VTAM

The example macro that is in Figure 34 on page 45 shows part of a VTAM mode
table MTCICS. This defines a number of modegroups, including modename CICSISC0.
The mode table that a CICS region uses must have a definition for all the
modegroups (modenames) that it uses and a definition for the SNASVCMG modegroup.
This modegroup is used by your SNA product for network management requests.
44
MTCICS
MODETAB
***********************************************************************
* MODE TABLE FOR CICS
*
***********************************************************************
:
:
:
:
:
*
* Modename CICSISC0 - Parallel_Sessions=yes
*
CICSISC0 MODEENT LOGMODE=CICSISC0,
X
TYPE=0,
ONLY TYPE RECOGNISED
X
FMPROF=X13,
SNA
X
TSPROF=X07,
SNA
X
PRIPROT=XB0,
PRIMARY PROTOCOL
X
SECPROT=XB0,
SECONDARY PROTOCOL
X
COMPROT=X79A5,
COMMON PROTOCOL
X
SSNDPAC=X00,
X
SRCVPAC=X00,
X
RUSIZES=X8989,
RUSIZES IN-4096 OUT-4096
X
PSNDPAC=X00,
X
PSERVIC=X060200000000000000122F00
*
* Modename SNASVCMG - required for parallel sessions
*
SNASVCMG MODEENT LOGMODE=SNASVCMG
:
:
:
:
:
MODEEND
***********************************************************************
* END OF MODE TABLE FOR CICS
*
***********************************************************************
Figure 34. VTAM mode table macro
Chapter 6. Configuring VTAM with details of your CICS region
45
46
Chapter 7. Operating SNAP-IX

The sections that follow describe how to control Systems Network Architecture
(SNA) SNAP-IX resources:
v Introduction to SNAP-IX operation
v Starting the node and connections on page 49
v Stopping the node and connections on page 51
v Starting, viewing, and stopping sessions on page 52
For more detailed information about these topics, see the SNAP-IX Administration
Guide.
Introduction to SNAP-IX operation

Figure 35 on page 48 shows a typical system configuration before the node,
connections, and sessions are activated.
47
Figure 35. Typical system configuration before the node, connections, and sessions are activated
Node status appears in the node box that is in the upper right corner of the
SNAP-IX node main screen. One of the following states always appears:
v Active: The node is active.
v Inactive: The node is inactive. (If you start a link station or port when the node is
inactive, the node starts automatically.)
v Unconfigured: The node is not configured.
v Starting: The node is starting. This status appears for a short time when the
node is being started.
v Stopping: The node is stopping. This status appears for a short time when the
node is being stopped.
The status state of an individual port or link station is displayed beside it in the
Connectivity and dependent LUs pane. Possible port states are as follows:
v Active: The port is active.
v Inactive: The port is inactive. (If you start a link station when the port is inactive,
the port starts automatically.)
48
v Starting: The port is starting.

v Stopping: The port is stopping.
Possible link station states are as follows:
v Active: The link station is active and session traffic can use it.
v Listening: The link station is currently stopped. It can be activated by a remote
system that needs to start a session with a local node.
v On demand: The link station is currently stopped. It can be activated by a local
application if that application needs to start a session, or by a remote system that
needs to start a session with a local node.
v Inactive: The link stations parent port is inactive. The link station can be
activated by a local application or by a remote system.
v Disabled: The link station is currently stopped. It cannot be activated by a local
application or by a remote system.
v Starting: The link station is starting.
v Stopping: The link station is stopping.
v Pending Retry: The link station failed to start or was deactivated because of a
failure. SNAP-IX is continuing to attempt to reactivate it and will retry the link
station soon.
You can get the status of a port or link station by clicking it in the Connectivity and
dependent LUs pane of the SNAP-IX node main screen, then clicking the Status
button in the toolbar.
Starting the node and connections

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

startup
To start the node and any connections that you have indicated to activate at startup:
1. From the SNA node main screen that is shown in Figure 35 on page 48, click
the node button in the upper right corner of the screen.
2. Click the Start button on the toolbar. The word Active appears under the node
name on the node button. The associated ports and link stations that you have
indicated to start automatically are also activated, as shown in Figure 36 on
page 50.
49
Figure 36. Starting the node and connections
If the node or connections or both are not activated successfully, SNAP-IX writes
error messages to its log file. You can view the error log file (sna.err) or the audit
log file (sna.aud) in the directory /var/opt/sna by using a text editor. (Refer to
Chapter 8, Problem determination for SNAP-IX, on page 55 for more details on
logging.)
Starting connections that do not activate at startup

To start a port that is not activated automatically at startup:
1. Ensure that the associated node is active (the term Active appears on the node
button that is in the upper right corner of the SNAP-IX node main screen).
2. Click the port in the Connectivity and dependent LUs pane of the SNAP-IX
node main screen.
3. Click the Start button.
To start a link station that is not activated automatically at startup:
50
1. Ensure that the associated node is active (the term Active appears on the node
button that is in the upper right corner of the SNAP-IX node main screen).
2. If the parent port is active:
a. Click the link station in the Connectivity and dependent LUs pane of the
SNAP-IX node main screen.
v If the Listening state is displayed for the link station, click the Start
button in the toolbar.
v If the Disabled state is displayed for the link station:
1) Click the Start button in the toolbar.
2) A message asks if you want to start the link station or simply enable it
for autoactivation without starting it. Select the appropriate option and
click OK.
3. If the parent port is inactive:
a. Click the link station in the Connectivity and dependent LUs pane of the
v If the Inactive state is displayed for the link station, click the Start button
in the toolbar. The parent node is activated with the link station.
v If the Disabled state is displayed for the link station:
1) Click the Start button in the toolbar.
2) A message asks if you want to start the link station or simply enable it
for autoactivation without starting it. Select the appropriate option and
click OK. The parent node is activated with the link station in either
case.
Stopping the node and connections

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

To stop the node and any associated connections simultaneously:
1. From the SNA node main screen that is shown in Figure 36 on page 50, click
the node button that is in the upper right corner of the screen.
2. Click the Stop button on the toolbar.
3. A message asks you to confirm your request to stop the node. Click OK. The
word Inactive appears under the node name on the node button. The ports
and link stations that are associated with the node also stop.
Stopping connections without stopping the node

To stop a port without stopping the node:
1. From the Connectivity and dependent LUs pane of the SNAP-IX node main
screen, click the port that you want to stop.
3. A message asks you to confirm your decision to stop the node. Click OK. All
associated link stations are stopped also.
To stop a link station without stopping the node:
1. From the Connectivity and dependent LUs pane of the SNAP-IX node main
screen, click the link station that you want to stop.
51

3. A message asks you to confirm your request to stop the link station, and gives
you the option of leaving the link station available for autoactivation. Select the
appropriate option and click OK. If you stopped the link station, leaving it
available for autoactivation, Inactive or Listening appears beside the link
station name in the Connectivity and dependent LUs pane of the SNAP-IX
node main screen. If you disabled the link station, Disabled appears beside the
link station name in the Connectivity and dependent LUs pane of the
Starting, viewing, and stopping sessions

CICS intersystem requests flow across a SNA network by way of sessions. CICS
applications must use sessions with a modename that you have defined. These
types of sessions can be started in several ways:
v By issuing a CICS intersystem request
v By using the administration application in the remote system
v By using SNAP-IX, which is described in Starting sessions
Starting sessions
To use SNAP-IX to start a session:
1. Ensure that the associated node and connection are active. (The term Active
appears on the node button that is in the upper right corner of the SNAP-IX
node main screen; one of the terms Active, Listening, or On demand, appears
beside the link connection name in the Connectivity and dependent LUs
pane.)
2. In the Independent local LUs pane of the SNAP-IX node main screen, click the
independent local LU that is to initiate the session.
3. Click the Start button in the toolbar.
4. A message asks you to supply either the Partner LU alias or the fully qualified
Partner LU name, the modename for the session, and the polarity that is
required. Enter appropriate values for your system and click OK.
If the links have just been started, it is possible that the only sessions that exist are
CPSVCMG sessions to other machines that support APPN. These sessions are
used to locate remote systems in APPN networks. Do not use them for CICS
intersystem requests.
In addition to sessions for your modename, some sessions for the SNASVCMG
modename have possibly been activated. These sessions are used by the SNA
products to manage the SNA network. Do not attempt to start or stop these
sessions or to use the SNASVCMG modename for your CICS intersystem requests.
Network interference can result.
Viewing sessions
When a node is active, the Independent local LUs pane shows the number of
sessions for each of its independent LUs. By clicking the plus sign (+) that is beside
the local LU name, you expand the entry to show its partner LUs, together with the
number of sessions for each partner LU and mode. The Remote systems pane
shows the number of sessions for each remote node. By clicking the plus sign (+)
that is beside the remote node name, you expand the entry to show the partner
LUs on that node, together with the number of sessions for each local LU and
mode. Figure 37 on page 53 shows an example networked system with active and
52
inactive sessions.
Figure 37. Example sessions
Stopping sessions
To use SNAP-IX to stop a session:
1. In the Independent local LUs pane of the SNAP-IX node main screen, click the
session that you want to stop.
2. Click the Stop button in the toolbar.
3. A message asks you to confirm that you want to stop all sessions from the
selected local LU to the partner LU that use the mode of the selected session.
Click OK.
53
54
Chapter 8. Problem determination for SNAP-IX

SNAP-IX provides two ways of diagnosing communications problems, which are
discussed in the following sections:
v Logging
v Tracing on page 56
A complete guide to problem determination for SNAP-IX is given in the SNAP-IX
Diagnostics Guide. In addition, your CICS region can log explanatory messages
when intersystem requests fail. For an overview of intersystem problem
determination, refer to the TXSeries for Multiplatforms Intercommunication Guide.
Logging
SNAP-IX writes, to log files, log messages that describe abnormal events and,
optionally, normal events. Log messages provide information about the causes of
problems and suggest actions that you can take to solve them.
To activate logging, complete the following procedure:
1. From the SNAP-IX node main screen, select the Logging option from the
Diagnostics menu. The Logging screen is displayed, as shown in Figure 38.
Figure 38. Logging screen
2. You must accept the default selection of Log exceptions. This selection
enables SNAP-IX to log abnormal events that degrade the system, but are
possibly not noticeable to a user. Problem and exception messages are logged
to the error log file /var/opt/sna/sna.err.
Note: When the sna.err log file reaches the maximum allowed size, SNAP-IX
copies its current contents to a backup file, then clears the log file. By
default, the file /var/opt/sna/bak.err is used as the name of the backup
error log file.
3. If desired, click the Log audit messages option. This selection enables
SNAP-IX to log normal events also. Audit messages are logged to the file
/var/opt/sna/sna.aud.
55
Note: When the sna.aud log file reaches the maximum allowed size, SNAP-IX
copies its current contents to a backup file, then clears the log file. By
default, the file /var/opt/sna/bak.aud is used as the name of the backup
audit log file.
4. Click either the verbose or the succinct option to control the level of detail that
is recorded in the log messages. Verbose messages list full details, including
logging number, originating component, type of message, text of the message,
additional information that indicates the cause of the condition that produced the
message, and any action that is recommended. Succinct messages contain only
an abbreviated version of the header information (message number, originating
component, and message type) and the text of the message.
5. Click OK.
You can view these messages by using a text editor, or by using standard Solaris
commands, such as pg or tail.
Tracing
When you are trying to diagnose a problem, you can turn on tracing to obtain
detailed information about the messages and data that SNAP-IX is sending and
receiving. Normally, leave all tracing turned off (the default) because tracing
degrades system performance.
To activate, use, and deactivate tracing, complete the following procedure:
1. In the SNAP-IX node main screen, select Node tracing from the Diagnostics
menu. The Tracing screen is displayed.
2. Choose the type of tracing you want by clicking the appropriate options.
SNAP-IX provides the following types of tracing:
v Line trace: Diagnoses network problems or tracks the progress of SNA
communications with the remote system. It traces the SNA messages that are
sent to, and received from, the remote system.
v Server message trace: Traces internal message flows and other message
types.
By clicking the Set all tracing on button, you select all parameters for tracing.
In this example, the Token Ring connection and the node and APPC messages
are traced.
3. Accept the default of 1024 for the Truncate messages to xxx bytes field. Your
screen now appears as shown in Figure 39 on page 57.
56
Figure 39. Tracing screen
4. Click OK.
5. When you have completed tracing, in the SNAP-IX node main screen, select
Node tracing from the Diagnostics menu.
6. Click the Set all tracing off option button.
7. Click OK.
Viewing trace data

The default trace output file is /var/opt/sna/sna1.trc. When the trace file reaches the
maximum allowed size, SNAP-IX copies its current contents to a backup file, then
clears the trace file to prevent it from becoming too large. By default,
/var/opt/sna/sna2.trc is used as the name for the backup trace file.
These files are binary files, so they cannot be viewed directly. Instead, the SNAP-IX
trace formatting utility, snatrcfmt, which converts the binary data into text files,
must be used to format the files. To convert the files to readable form, follow this
procedure:
1. Change to the directory /var/opt/sna.
2. Enter the following commands:
/opt/sna/bin/snatrcfmt -f sna1.trc -o sna1
/opt/sna/bin/snatrcfmt -f sna2.trc -o sna2
Chapter 8. Problem determination for SNAP-IX
57
This action generates two message dump files in the /var/opt/sna directory that are
called sna1.dmp and sna2.dmp. These are text files that contain all the trace
messages. You can view the formatted trace output by using a standard text editor;
for example the Solaris text editor vi.
Reading SNAP-IX traces requires some knowledge of SNA architecture. See the
Bibliography, on page 59 for books that provide information about SNA.
58
Appendix. Bibliography
For access to SNA and CICS books, visit the IBM Web sites for these products.
SNAP-IX books are provided by Data Connection Limited and can be found on that
companys Web site.
SNA books
v Systems Network Architecture Technical Overview, GC30-3073
v Systems Network Architecture Transaction Programmers Reference Manual for
LU Type 6.2, GC30-3084
v Systems Network Architecture--Sessions Between Logical Units, GC20-1868
v Systems Network Architecture Format and Protocol Reference Manual:
Architecture Logic for LU Type 6.2, SC30-3269
v Systems Network Architecture LU 6.2 Reference--Peer Protocols, SC31-6808
SNAP-IX books
v SNAP-IX Administration Guide
v
v
v
v
SNAP-IX Administration Command Reference

SNAP-IX APPC Programmers Guide
SNAP-IX Diagnostics Guide
SNAP-IX Installation Guide
CICS books
v TXSeries for Multiplatforms Administration Guide, SC34-6746
v TXSeries for Multiplatforms Administration Reference, SC34-6641
v TXSeries for Multiplatforms Intercommunication Guide, SC34-6644
v TXSeries for Multiplatforms Using IBM Communications Server for Windows
Systems with CICS, SC34-6748
v TXSeries for Multiplatforms Using IBM Communications Server for AIX with
CICS, SC34-6642
v CICS Family: Interproduct Communication, SC33-0824
v CICS for MVS/ESA V4R1 Intercommunication Guide, SC33-1181
v CICS Transaction Server for OS/390 V1R3 CICS Intercommunication Guide,
SC33-1695
v CICS Family: Communicating from CICS on System/390, SC33-1697
v CICS for VSE/ESA V2R3 Intercommunication Guide, SC33-0701
v CICS for OS/2 V3R1 Intercommunication, SC33-1583
v CICS/400 Intercommunication V3R1, SC33-1388
59
60
Notices
This information was developed for products and services offered in the U.S.A. IBM
may not offer the products, services, or features discussed in this document in other
countries. Consult your local IBM representative for information on the products and
services currently available in your area. Any reference to an IBM product, program,
or service is not intended to state or imply that only that IBM product, program, or
service may be used. Any functionally equivalent product, program, or service that
does not infringe any IBM intellectual property right may be used instead. However,
it is the users responsibility to evaluate and verify the operation of any non-IBM
product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you any
license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
DOCUMENT AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OR CONDITIONS OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express
or implied warranties in certain transactions, therefore, this statement may not apply
to you.
This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the document. IBM may make improvements and/or
changes in the product(s) and/or the program(s) described in this publication at any
time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those
Web sites. The materials at those Web sites are not part of the materials for this
IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes
appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of
enabling: (i) the exchange of information between independently created programs
61
and other programs (including this one) and (ii) the mutual use of the information
which has been exchanged, should contact:
IBM Corporation
ATTN: Software Licensing
11 Stanwix Street
Pittsburgh, PA 15222
U.S.A.
Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.
The licensed program described in this document and all licensed material available
for it are provided by IBM under terms of the IBM International Program License
Agreement or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those
products, their published announcements or other publicly available sources. IBM
has not tested those products and cannot confirm the accuracy of performance,
compatibility or any other claims related to non-IBM products. Questions on the
capabilities of non-IBM products should be addressed to the suppliers of those
products.
All statements regarding IBMs future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples may include
the names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
If you are viewing this information softcopy, the photographs and color illustrations
may not appear.
Trademarks and service marks

The following terms are trademarks or registered trademarks of the IBM Corporation
in the United States, other countries, or both:
Advanced Peer-to-Peer Networking
AS/400
62
AIX
CICS
CICS/400
CICS/6000
CICS/ESA
CICS/MVS
CICS/VSE
CICSPlex
C-ISAM
Database 2
DB2
DB2 Universal Database
GDDM
IBM Registry
IBM
IMS
Informix
Language Environment
MVS
MVS/ESA
OS/390
OS/2
OS/400
RACF
RETAIN
RISC System/6000
RS/6000
SOM
Systems Application Architecture
System/390
TXSeries
TCS
VisualAge
VSE/ESA
VTAM
WebSphere
z/OS
Domino, Lotus, and LotusScript are trademarks or registered trademarks of Lotus

Development Corporation in the United States, other countries, or both.
ActiveX, Microsoft, Visual Basic, Visual C++, Visual J++, Visual Studio, Windows,
Windows NT, and the Windows 95 logo are trademarks or registered trademarks
of Microsoft Corporation in the United States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Acucorp and ACUCOBOL-GT are registered trademarks of Acucorp, Inc. in the
United States, other countries, or both.
Pentium is a trademark of Intel Corporation in the United States, other countries,
or both.
This software contains RSA encryption code.
Other company, product, and service names may be trademarks or service marks
of others.
Notices
63
64
Index
A
ACF/NCP 5
ADDCICSSIT 4, 10
Advanced Peer-to-Peer Networking (APPN) 6, 55
Advanced Program-to-Program Communications
(APPC) 5, 6
ALLOCATE 10
APPC 5, 6
APPLID 4, 10
APPN 6, 55
LEN node 6
link address 9, 16
link definition 8, 16
link service 8
link station
defining 19
linking machines with SNA 8, 16
example 31
local LU 4, 10, 22
local SNA support 6, 10
logical level 4
Logical Unit (LU) name
fully qualified 4
network-qualified 4
low-entry network (LEN) node 6
LU definition (VTAM) 44
B
BIND
request 4
response 4
C
communication methods
local SNA 6, 10
Communications Definitions (CD)
DefaultSNAModeName 10
example 31
configuration profile examples
SNAP-IX 31
contention winner/loser 4
Control Point (CP) name 5, 7, 13, 43
CPSVCMG 12
D
data link control (DLC) protocols
default modename 10, 27
defining connections (links) 8
defining devices 17
defining links 8, 16
5, 8
M
MAC address 9
mode
definition 4, 11
MODEENT definition (VTAM) 44
modegroup 4, 11
modename
ALLOCATE command 10
configuring 27
default modename 10
definition 4, 11
SNAModeName 10
VTAM 44
end node 6
Ethernet 5, 9
exchange identifier (XID) 5, 7, 13, 43
EXEC CICS ALLOCATE 10
netid 4
NETNAME 4, 10
network ID 4
network name (SNA) 4, 7, 10, 13
network node 6
network-qualified LU name 4
node (SNA) 5, 7, 13
node identifier 5, 7, 13
fully qualified LU name
I
IBM Token Ring 5, 9
independent LUs 5, 43
partner LU 4
PATH definition (VTAM) 43
peer connections 19
physical level 4
Physical Unit (PU) 5, 7, 43
port
defining 17
problem determination 55
PROFILE 10
65
PU definition (VTAM)
43
R
example 31
region name 10, 22
S
session limits 11, 27
sessions, SNA 4
SNA
ADDCICSSIT 4, 10
Advanced Peer-to-Peer Networking (APPN) 5
Advanced Program-to-Program Communications
(APPC) 5, 6
APPLID 4, 10
BIND 4
configuration profiles 31
configuring 4, 13
connecting machines 8
contention winner/loser 4
Control Point (CP) name 5, 7, 13, 24, 43
conversation-level security 11, 24, 29
CPSVCMG 12
data link control (DLC) protocols 5, 8
default modename 10
defining connections (links) 8
devices 17
example profiles 31
exchange identifier (XID) 5, 7, 13, 43
fully qualified LU name 4
independent LUs 4, 43
link address 9, 16
link service 8
local LU 4, 10, 22
Logical Unit (LU) 4, 10, 22, 24
LU definition (VTAM) 44
LU name 4, 10, 22
MAC address 9
mode 4, 11
modegroup 4, 11
modename 4, 10, 11, 27, 44
netid 4
NETNAME 4, 10
network ID 4
network name 4, 7, 10, 13, 24
network-qualified LU name 4
node 5, 7, 13, 16
node identifier 5, 7, 13
partner LUs 4, 10, 24
PATH definition (VTAM) 43
peer connections 19
Physical Unit (PU) 5, 7, 43
PU definition (VTAM) 43
remote LUs 10, 24
session limits 11, 27
SNASVCMG 12, 44
synchronization level 4, 10
VTAM 5, 43
66
SNA (continued)
XID 5, 7, 13, 43
SNAModeName 10
SNAP-IX
configuring 13
example configurations 31
example profiles 31
problem determination 55
SNA 31
starting connections 49
starting nodes 49
starting sessions 52
stopping connections 51
stopping nodes 51
stopping sessions 52
viewing sessions 52
SNASVCMG 12, 44
synchronization level 4, 10
Synchronous Data Link Control (SDLC) 5, 9
Systems Services Control Point (SSCP) 5
T
Transaction Definitions (TD)
example 31
SNAModeName 10
V
VTAM 5, 43
X
XID
5, 7, 13, 43
SC34-6751-01

Spine information:
Version 6.2
SC34-6751-01

TXSeries For Multiplatforms Using SNAP-IX For Solaris With CICS Version 6.2

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

TXSeries For Multiplatforms Using SNAP-IX For Solaris With CICS Version 6.2

Загружено:

Авторское право:

Доступные форматы

TXSeries for Multiplatforms

Using SNAP-IX for Solaris with CICS

TXSeries for Multiplatforms

Using SNAP-IX for Solaris with CICS

Second Edition (January 2008)

Chapter 1. Introduction to SNAP-IX for Solaris

Chapter 2. Introduction to SNA . . . . .

Chapter 3. Collecting information for a SNAP-IX configuration

Chapter 4. Configuring SNAP-IX . . . . . . .

Chapter 5. Matching SNAP-IX parameters

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

Stopping connections without stopping

Chapter 8. Problem determination

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

SNAP-IX node main screen . . . . . . . . . . . . . . . . . . . . . .

Copyright IBM Corp. 1999, 2008

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

Getting started road map . . . . . . . . . . . . . . . . . . . . . . . . . . .

Copyright IBM Corp. 1999, 2008

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

About this book

Who should read this book

Review basic information about SNAP-IX

Chapter 1, Introduction to SNAP-IX for

Review common SNA terminology

Chapter 2, Introduction to SNA, on page 3

Collect information for a new SNA

Chapter 3, Collecting information for a

Chapter 4, Configuring SNAP-IX, on page

Review example configuration profiles

Chapter 5, Matching SNAP-IX parameters

Communicate with EBCDIC mainframes

Chapter 6, Configuring VTAM with details of

Start and stop nodes, connections, and

Chapter 7, Operating SNAP-IX, on page 47

Solve communications problems

Chapter 8, Problem determination for

Copyright IBM Corp. 1999, 2008

Conventions used in this book

Indicates values that you must use literally, such as commands,

Indicates text that you must enter at a command prompt. Monospace

Encloses the names of keys on the keyboard.

Where x is the name of a key, indicates a control-character

Represents the UNIX command-shell prompt for a command that

Represents the UNIX command-shell prompt for a command that

Represents the Windows command prompt.

When used to describe a menu, shows a series of menu selections.

When instructed to enter or issue a command, type the command

Encloses optional items in syntax descriptions.

Encloses lists from which you must choose an item in syntax

Separates items in a list of choices enclosed in { } (braces) in syntax

Ellipses in syntax descriptions indicate that you can repeat the

In function descriptions, indicates parameters whose values are used

In function descriptions, indicates parameters whose values are used

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

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

In function descriptions, indicates parameters whose values are

Refers collectively to the CICS product for all supported UNIX

How to send your comments

About this book

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

Chapter 1. Introduction to SNAP-IX for Solaris

Figure 1. SNAP-IX node main screen