Configuration parameters for an LU 6.2 connection

Table 33 presents a worksheet listing all the parameters needed to set up communication from z/OS 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.

The steps required to set up an LU 6.2 connection are described in Establishing an LU 6.2 connection with numbered cross references to the parameters on the worksheet.

Configuration worksheet

Use this worksheet to record the values you use for your 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. The entries in the Parameter Name column are explained in Explanation of terms.

Table 33. Configuration worksheet for z/OS using LU 6.2

Explanation of terms

(1) Command prefix

This is the unique command prefix of your WebSphere MQ for z/OS queue-manager subsystem. The z/OS systems programmer defines this at installation time, in SYS1.PARMLIB(IEFSSNss), and will be able to tell you the value.

(2) Network ID

The VTAM startup procedure in your installation is partly customized by the ATCSTRxx member of the data set referenced by the DDNAME VTAMLST. The Network ID is the value specified for the NETID parameter in this member. For Network ID you must specify the name of the NETID that owns the WebSphere MQ communications subsystem (WebSphere MQ channel initiator or CICS for z/OS as the case may be). Your network administrator will tell you the value.

(3) Node name

VTAM, being a low-entry network node, does not have a Control Point name for Advanced Peer-to-Peer Networking (APPN) use. It does however have a system services control point name (SSCPNAME). For node name, you must specify the name of the SSCP that owns the WebSphere MQ communications subsystem (WebSphere MQ channel initiator or CICS for z/OS as the case may be). This is defined in the same ATCSTRxx member as the Network ID. Your network administrator will tell you the value.

(4) Local LU name

A logical unit (LU) is software that serves as an interface or translator between a transaction program and the network. It manages the exchange of data between transaction programs. The local LU name is the unique VTAM APPLID of this WebSphere MQ subsystem. Your network administrator will tell you this value.

(5) (13) Symbolic destination

This is the name you give to the CPI-C side information profile. You need a side information entry for each LU 6.2 listener.

(6) (14) Modename

This is the name given to the set of parameters that control the LU 6.2 conversation. An entry with this name and similar attributes must be defined at each end of the session. In VTAM, this corresponds to a mode table entry. You network administrator will assign this to you.

(7) (15) Transaction Program name

WebSphere MQ applications trying to converse with this queue manager will specify a symbolic name for the program to be run at the receiving end. This will have been specified in the TPNAME attribute on the channel definition at the sender. For simplicity, wherever possible 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 32 for more information. If the receiving end is z/OS using CICS, special values are required.

(8) LAN destination address

This is the LAN destination address that your partner nodes will use to communicate with this host. When you are using a 3745 network controller, it will be the value specified in the LOCADD parameter for the line definition to which your partner is physically connected. If your partner nodes use other devices such as 317X or 6611 devices, the address will have been set during the customization of those devices. Your network administrator will tell you this value.

(16) Partner LU name

This is the LU name of the WebSphere MQ queue manager on the system with which you are setting up communication. This value is specified in the side information entry for the remote partner.

(21)Remote node ID

For a connection to Windows, this is the ID of the local node on the Windows system with which you are setting up communication.