Preparing for SNA configuration

To establish a SNA connection, each system must:

  1. Define itself to the network
  2. Define the connection to its partner
  3. Ensure that the remote system has a definition of the local system

You could regard the first step as the system registering its name and address with the network; the second step as a system specifying its intended partner’s name and address so that the network can establish a link to it; and the third step as your partner registering your system’s name so that it will recognize your system’s requests when it receives them.

Matching parameters

The names that are used to define system resources include the network name, LU name, PU name, CP name and XID.

Some of these names are used as parameters when configuring the CICS® product, and others are used as parameters when configuring the SNA product. Some are used in both products. Some are used in one product on the local system and in another product on the remote system. When a parameter is used in more than one place, it is important that the same name is used. That is, the parameters must match.

Mode name

The partners must use matching mode names. Any mode may be used, but a convenient one is the #INTER architected mode.

Alias names

Some resources (typically the LU) may have an alias or local name as well as a real name. The alias is only used internally within a local system. The partner system recognizes only the real name, and it is that name that must match across the systems.

Platform specific implementation

Depending upon the particular network configurations and SNA products being used, you may find that not all the parameters are needed. For example, the XID may be used rather than the CP name to identify the partner. In other circumstances when, for example, there is only one LU in the PU, the CP may have to have the same name as the LU. You should refer to the product-specific manuals for clarification of these points when you are ready to proceed beyond this first basic configuration.

The scenario

In the scenario chosen for this discussion, we assume that there is an established SNA network of interconnected CICS on System/390® systems into which we are adding a CICS for AIX® system. This chapter is written from the perspective of the AIX systems’ administrator who connects the workstations to the mainframe host.

To avoid the potential problem of duplicate names being used, and to assist management of the network, the VTAM® system administrator may act as coordinator for the network resource names. You therefore need to agree the network names of your workstations with the VTAM systems administrator.

Related concepts
Introduction to SNA terminology
Related tasks
Configuring CICS for SNA--next steps
Related reference
Configuration details
[[ Contents Previous Page | Next Page Index ]]