Configuration parameters for an LU 6.2 connection

Table 24 presents a worksheet listing all the parameters needed to set up communication from HP-UX 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 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 24. Configuration worksheet for HP SNAplus2

Explanation of terms

(1) Configuration file name

This is the unique name of the SNAplus2 configuration file. The default for this name is sna_node.cfg.

Although it is possible to edit this file it is strongly recommended that configuration is done using xsnapadmin.

(2) Control point name

This is the unique Control point name for this workstation. In the SNA network, the Control point is an addressable location (PU type 2.1). Your network administrator will assign this to you.

(3) Node ID to send

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.

(4) 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.

(5) Local APPC LU

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

(6) APPC mode

This is the name given to the set of parameters that control the APPC conversation. This name must be defined at each partner system. Your network administrator will assign this to you.

(7) Invokable TP

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

See Table 20 for more information.

(8) Token-ring adapter address

Use the HP-UX System Administration Manager (SAM) to discover the adapter address for this workstation. You need root authority to use SAM. From the initial menu, select Networking and Communications, then select Network Interface cards followed by LAN 0 (or whichever LAN you are using). The adapter address is displayed under the heading Station Address (hex). The card name represents the appropriate card type. If you do not have root level authority, your HP-UX system administrator can tell you the value.

(9) Port name

This is a meaningful symbolic name that is used to associate the definitions with a network interface (in this case, a Token-Ring adapter). A separate Port must be defined for each physical device attached to the workstation.

(10) Full path to executable

On HP SNAplus2 Release 5, this is the path and name of a shell script file that invokes the actual program to be run when a conversation is initiated with this workstation. You can choose the path and name of the script file. The contents of the file are illustrated in WebSphere MQ for HP-UX invokable TP setup. On HP SNAplus2 Release 6, this is the path and name of the program to be run when a conversation is initiated with this workstation. You enter the path in the TP invocation screen (see Adding a TP definition using HP SNAplus2 Release 6).

(11) Local queue manager

This is the name of the queue manager on your local system.

(10) Link station name

This is a meaningful symbolic name by which the connection to a peer or host node is known. It defines a logical path to the remote system. Its name is used only inside SNAplus2 and is specified by you. The connection must be associated with an existing Link and owned by one local node. You must define one connection for each partner or host system.

(18) CPI-C symbolic destination name

This is a name given to the definition of a partner node. You choose the name. It need be unique only on this machine. Later you can use this name in the WebSphere MQ sender channel definition.

(20) Node ID to receive

This is the unique ID of the partner workstation with which you will be communicating. On other platforms this is often referred to as the Exchange ID or XID. For a connection to a host system any values except 000 FFFFF and FFF FFFFF may be specified. Your network administrator will assign this ID for you.