Configuration parameters for an LU 6.2 connection using SunLink Version 9.1

Table 28 presents a worksheet listing all the parameters needed to set up communication from Solaris to one of the other WebSphere MQ platforms, using SunLink Version 9.1. 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 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 28. Configuration worksheet for SunLink Version 9.1

Explanation of terms

(1) PU2.1 server name

This is the name of the PU2.1 server for the local control point.

(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) CP name

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

(4) Line name

This is the name that identifies the connection to the LAN.

(5) Local MAC address

This is the network address of the token-ring card. The address to be specified is found in the ether value displayed in response to the ifconfig tr0 command issued at a root level of authority. (Tr0 is the name of the machine's token-ring interface.) If you do not have the necessary level of authority, your Solaris system administrator can tell you the value.

(6) Local terminal ID

This is the unique ID of this workstation. On other platforms this is often referred to as the Exchange ID or XID. Your network administrator will assign this ID for you.

(7) Local LU name

An LU manages the exchange of data between transactions. The local LU name is the name of the LU on your system. Your network administrator will assign this to you.

(8) 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. 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 MQ01.

See Table 20 for more information.

(9) TP path

This is the path and name of the script file that invokes the WebSphere MQ program to run.

(10) Unique session name

This is the unique name of the Partner LU/Mode definition.

(12) DLC name

This is the name of the link to the remote system.

(13) Remote CP name

This is the name of the control point on the remote system.

(18) CPI-C file name

This is the full path and name of the file which holds CPI-C side information for a partner system. There must be a separate CPI-C file for each partner. For increased flexibility, include the full path and file name in the WebSphere MQ sender channel definition.