Configuration parameters for an LU 6.2 connection

Table 17 presents a worksheet listing all the parameters needed to set up communication from Windows 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, with numbered cross references to the parameters on the worksheet. These steps are:

• Configuring the local node
• Adding a connection
• Adding a partner
• Adding a CPI-C entry
• Configuring an invokable TP

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 17. Configuration worksheet for IBM Communications Server for Windows systems

Explanation of terms

(1) Configuration Name

This is the name of the file in which the Communications Server configuration is saved.

(2) Network Name

This is the unique ID of the network to which you are connected. It is an alphanumeric value and can be 1-8 characters long. The network name works with the Control Point Name to uniquely identify a system. Your network administrator will tell you the value.

(3) Control Point Name

In Advanced Peer-to-Peer Networking^(R) (APPN^(R)), a control point is responsible for managing a node and its resources. A control point is also a logical unit (LU). The Control Point Name is the name of the LU and is assigned to your system by the network administrator.

(4) Local Node ID (hex)

Some SNA products require partner systems to specify a node identifier that uniquely identifies their workstation. The two systems exchange this node identifier in a message unit called the exchange identifier (XID). Your network administrator will assign this ID for you.

(5) LU Name (local)

A logical unit (LU) is software that serves as an interface or translator between a transaction program and the network. An LU manages the exchange of data between transaction programs. The local LU Name is the name of the LU on your workstation. Your network administrator will assign this to you.

(6) LU Alias (local)

The name by which your local LU will be known to your applications. You choose this name yourself. It can be 1-8 characters long.

(7) TP Name

WebSphere MQ applications trying to converse with your workstation specify a symbolic name for the program that is to start running. This will have been defined 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 13 for more information.

(8) Command line

This is the path and name of the actual program to be run when a conversation has been initiated with your workstation. The example shown on the worksheet assumes that WebSphere MQ is installed in the default directory, c:\mqm. The configuration pairs this name with the symbolic name (7) when you use TPSETUP (which is part of the SNA Server software developers kit).

(9) LAN adapter address

This is the address of your token-ring card. To discover this type net config server at a command prompt. The address appears in the output. For example:

Server is active on 08005AA5FAB9

(10) Connection

This is a meaningful symbolic name by which the connection to a partner node is known. It is used only within SNA Server administration and is specified by you.

(15) LU Alias (remote)

This is a value known only in this server and is used to represent the fully qualified partner LU name. You supply the value.

(17) Mode

This is the name given to the set of parameters that control the APPC conversation. An entry with this name and a similar set of parameters must be defined at each partner system. Your network administrator will tell you this name.

(18) CPI-C Name

This is the name given to a locally held definition of a partner application. You supply the name and it must be unique within this server. The name is specified in the CONNAME attribute of the WebSphere MQ sender channel definition.