Configuration parameters for an LU 6.2 connection

Table 50 presents a worksheet listing all the parameters needed to set up communication from VSE/ESA 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 50. Configuration worksheet for VSE/ESA using APPC

ID Parameter Name Reference Example Used User Value
Definition for local node
(1) Network ID
NETID
(2) Node name
VSEPU
(3) Local LU name
VSELU
(4) Local Transaction Program name
MQ01 MQ01
(5) LAN destination address
400074511092
Connection to an OS/2 system

The values in this section of the table must match those used in the table for OS/2, as indicated.

(6) Connection name
OS2
(7) Group name
EXAMPLE
(8) Session name
OS2SESS
(9) Netname (6) OS2LU
Connection to a Windows system

The values in this section of the table must match those used in the table for Windows NT, as indicated.

(6) Connection name
WNT
(7) Group name
EXAMPLE
(8) Session name
WNTSESS
(9) Netname (5) WINNTLU
Connection to an AIX system

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

(6) Connection name
AIX
(7) Group name
EXAMPLE
(8) Session name
AIXSESS
(9) Netname (4) AIXLU
Connection to an HP-UX system

The values in this section of the table must match those used in the table for HP-UX, as indicated.

(6) Connection name
HPUX
(7) Group name
EXAMPLE
(8) Session name
HPUXSESS
(9) Netname (5) HPUXLU
Connection to an AT&T GIS UNIX system

The values in this section of the table must match those used in the table for GIS UNIX, as indicated.

(6) Connection name
GIS
(7) Group name
EXAMPLE
(8) Session name
GISSESS
(9) Netname (4) GISLU
Connection to a Solaris system

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

(6) Connection name
SOL
(7) Group name
EXAMPLE
(8) Session name
SOLSESS
(9) Netname (7) SOLARLU
Connection to an iSeries system

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

(6) Connection name
AS4
(7) Group name
EXAMPLE
(8) Session name
AS4SESS
(9) Netname (3) AS400LU
Connection to a z/OS system without CICS

The values in this section of the table must match those used in the table for z/OS, as indicated.

(6) Connection name
MVS
(7) Group name
EXAMPLE
(8) Session name
MVSSESS
(9) Netname (4) MVSLU

Explanation of terms

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

(2) Node name
This is the name of the SSCP which owns the CICS/VSE region.

(3) Local LU name
This is the unique VTAM APPLID of this CICS/VSE region.

(4) Transaction Program name
WebSphere MQ applications trying to converse with this queue manager will specify a transaction name for the program to be run at the receiving end. This will have been defined on the channel definition at the sender. MQSeries for VSE/ESA uses a name of MQ01.

(5) LAN destination address
This is the LAN destination address that your partner nodes will use to communicate with this host. It is usually the address of the 3745 on the same LAN as the partner node.

(6) Connection name
This is a 4-character name by which each connection will be individually known in CICS RDO.

(7) Group name
You choose your own 8-character name for this value. Your system may already have a group defined for connections to partner nodes. Your system administrator will give you a value to use.

(8) Session name
This is an 8-character name by which each session will be individually known. For clarity we use the connection name, concatenated with 'SESS'.

(9) Netname
This is the LU name of the WebSphere MQ queue manager on the system with which you are setting up communication.



© IBM Corporation 2002. All Rights Reserved