Configuration parameters for an LU 6.2 connection

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

This chapter shows how to use the values on the worksheet for:

• Defining local node characteristics
• Connecting to a peer system
• Connecting to a host system
• Verifying the configuration

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 15. Configuration worksheet for Communications Manager/2

Explanation of terms

(1) Configuration name

This is the name of the OS/2 file that will hold the configuration.

If you are adding to or modifying an existing configuration it will be the name previously specified.

If you are creating a new configuration then you can specify any 8-character name that obeys the normal rules for file naming.

(2) Network ID

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 ID works with the local node name to uniquely identify a system. Your network administrator will tell you the value.

(3) Local node name

This is the unique Control Point name for this workstation. Your network administrator will assign this to you.

(4) Local node ID (hex)

This is a unique identifier for this workstation. On other platforms it is often referred to as the exchange ID (XID). Your network administrator will assign this to you.

(5) Local node alias name

This is the name by which your local node will be known within this workstation. This value is not used elsewhere, but it is recommended that it be the same as (3), the local node name.

(6) LU name (local)

An 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.

(7) Alias (for local LU name)

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. This value is used during WebSphere MQ configuration, when entries are added to the qm.ini file.

(8) Local transaction program (TP) 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. The TP name is also used during WebSphere MQ configuration, when entries are added to the qm.ini file. 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.

(9) OS/2 program path and file name

This is the path and name of the actual program to be run when a conversation has been initiated with this 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 (8).

(10) LAN adapter address

This is the address of your token-ring card. When using the default address, the exact value can be found in the LANTRAN.LOG file found in the \IBMCOM directory.

For example:

Adapter 0 is using node address 10005AFC5D83

(11) Link name

This is a meaningful symbolic name by which the connection to a partner node is known. It is used only inside Communications Manager/2 setup and is specified by you. It can be 1-8 characters in length.

(16) Alias (for remote LU name)

This is a value known only on this workstation 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. This name must be defined at each point in the network between the local and partner LUs. Your network administrator will assign this to you.