Configuration parameters for an LU 6.2 connection

Table 26 presents a worksheet listing all the parameters needed to set up communication from AT&T GIS UNIX5 to one of the other WebSphere MQ platforms. The worksheet shows examples of the parameters, which have been tested in a working environment, and leaves space for you to fill in your own values. An explanation of the parameter names follows the worksheet. Use the worksheet in this chapter in conjunction with the worksheet in the chapter for the platform to which you are connecting.

Configuration worksheet

Use the following worksheet to record the values you will use for this configuration. Where numbers appear in the Reference column they indicate that the value must match that in the appropriate worksheet elsewhere in this book. The examples that follow in this chapter refer back to the values in the ID column of this table. The entries in the Parameter Name column are explained in Explanation of terms.

Table 26. Configuration worksheet for AT&T GIS SNA Services

ID Parameter Name Reference Example User Value
Parameters for local node
(1) Configuration
010
(2) Network name
NETID
(3) Control Point name
GISPU
(4) Local LU name
GISLU
(5) LU 6.2 Transaction Program name
MQSERIES
(6) Local PU name
GISPU
(7) Mode name
#INTER
(8) Token-Ring adapter address
10007038E86B
(9) Local XID
03E 00018
Connection to an OS/2 system

The values in this section of the table must match those used in Table 15, as indicated.

(10) Remote Node name (3) OS2PU
(11) Network name (2) NETID
(12) Remote LU name (6) OS2LU
(13) Remote Transaction Program name (8) MQSERIES
(14) LU 6.2 CPI-C side information symbolic destination
OS2CPIC
(15) Mode name (17) #INTER
(16) LAN destination address (10) 10005AFC5D83
Connection to a Windows system

The values in this section of the table must match those used in Table 17, as indicated.

(10) Remote Node name (3) WINNTCP
(11) Network name (2) NETID
(12) Remote LU name (5) WINNTLU
(13) Remote Transaction Program name (7) MQSERIES
(14) LU 6.2 CPI-C side information symbolic destination
NTCPIC
(15) Mode name (17) #INTER
(16) LAN destination address (9) 08005AA5FAB9
Connection to an AIX system

The values in this section of the table must match those used in Table 21, as indicated.

(10) Remote Node name (2) AIXPU
(11) Network name (1) NETID
(12) Remote LU name (4) AIXLU
(13) Remote Transaction Program name (6) MQSERIES
(14) LU 6.2 CPI-C side information symbolic destination
AIXCPIC
(15) Mode name (14) #INTER
(16) LAN destination address (8) 123456789012
Connection to an HP-UX system

The values in this section of the table must match those used in Table 24, as indicated.

(10) Remote Node name (2) HPUXPU
(11) Network name (4) NETID
(12) Remote LU name (5) HPUXLU
(13) Remote Transaction Program name (7) MQSERIES
(14) LU 6.2 CPI-C side information symbolic destination
HPUXCPIC
(15) Mode name (6) #INTER
(16) LAN destination address (8) 100090DC2C7C
Connection to a Solaris system

The values in this section of the table must match those used in Table 28, as indicated.

(10) Remote Node name (3) SOLARPU
(11) Network name (2) NETID
(12) Remote LU name (7) SOLARLU
(13) Remote Transaction Program name (8) MQSERIES
(14) LU 6.2 CPI-C side information symbolic destination
SOLCPIC
(15) Mode name (17) #INTER
(16) LAN destination address (5) 08002071CC8A
Connection to an iSeries system

The values in this section of the table must match those used in Table 48, as indicated.

(10) Remote Node name (2) AS400PU
(11) Network name (1) NETID
(12) Remote LU name (3) AS400LU
(13) Remote Transaction Program name (8) MQSERIES
(14) LU 6.2 CPI-C side information symbolic destination
AS4CPIC
(15) Mode name (17) #INTER
(16) LAN destination address (4) 10005A5962EF
Connection to a z/OS system without CICS

The values in this section of the table must match those used in Table 33, as indicated.

(10) Remote Node name (3) MVSPU
(11) Network name (2) NETID
(12) Remote LU name (4) MVSLU
(13) Remote Transaction Program name (7) MQSERIES
(14) LU 6.2 CPI-C side information symbolic destination
MVSCPIC
(15) Mode name (10) #INTER
(16) LAN destination address (8) 400074511092
Connection to a VSE/ESA system

The values in this section of the table must match those used in Table 50, as indicated.

(10) Remote Node name (2) VSEPU
(11) Network name (1) NETID
(12) Remote LU name (3) VSELU
(13) Remote Transaction Program name (4) MQ01
(14) LU 6.2 CPI-C side information symbolic destination
VSECPIC
(15) Mode name
#INTER
(16) LAN destination address (5) 400074511092

Explanation of terms

(1) Configuration
This is the unique ID of the SNA Server configuration you are creating or modifying. Valid values are between 0 and 255.

(2) Network name
This is the unique ID of the network to which you are connected. Your network administrator will tell you this value.

(3) Control Point name
This is a unique Control Point name for this workstation. Your network administrator will assign this to you.

(4) Local LU name
A logical unit (LU) manages the exchange of data between systems. The local LU name is the name of the LU on your system. Your network administrator will assign this to you.

(5) LU 6.2 Transaction Program name
WebSphere MQ applications trying to converse with this workstation will specify a symbolic name for the program to be run at the receiving end. This will have been defined on the channel definition at the sender. Wherever possible we use a transaction program name of MQSERIES, or in the case of a connection to VSE/ESA, where the length is limited to 4 bytes, use MQTP.

See Table 20 for more information.

(6) Local PU name
This is a unique PU name for this workstation. Your network administrator will assign this to you.

(7) Mode name
This is the name given to the set of parameters that control the APPC conversation. This name must be defined at each partner system. Your network administrator will assign this to you.

(8) Token-ring adapter address
The is the 12-character hex address of the token-ring card.

(10) Remote Node name
This is a meaningful symbolic name by which the connection to a partner node is known. It is used only inside SNA Server setup and is specified by you.

(14) LU 6.2 CPI-C Side Information Symbolic Destination
This is a name given to the definition of a partner node. You supply the name. It need be unique only on this machine. You will later use the name in the WebSphere MQ sender channel definition.


Footnotes:

5
This platform has become NCR UNIX SVR4 MP-RAS, R3.0


© IBM Corporation 2002. All Rights Reserved