Configuration parameters for an LU 6.2 connection
The information in this section applies only to WebSphere MQ for Linux for Intel. It does not apply to WebSphere MQ for Linux for zSeries.
Table 31 presents a worksheet listing all the parameters needed to set up communication from Linux to one of the other WebSphere MQ platforms using Communications Server for Linux. 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 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 to the values in the ID column. The entries in the Parameter Name column are explained in Explanation of terms.
Table 31. Configuration worksheet for Communications Server for Linux
ID Parameter Name Reference Example User Value Parameters for local node (1) Configuration file name sna_node.cfg (2) Control point name LINUXPU (3) Node ID to send 05D 30A55 (4) Network name NETID (5) Local APPC LU LINUXLU (6) APPC mode #INTER (7) Invokable TP MQSERIES (8) Local MAC address 08005AC6DF33 (9) Port name MQPORT (10) Command path /opt/mqm/bin/amqcrs6a (11) Local queue manager LINUX Connection to an OS/2 system The values in this section of the table must match those used in Table 15, as indicated.
(12) Link station name OS2CONN (13) Network name (2) NETID (14) CP name (3) OS2PU (15) Remote LU (6) OS2LU (16) Application TP (8) MQSERIES (17) Mode name (17) #INTER (18) CPI-C symbolic destination name OS2CPIC (19) Remote network address (10) 10005AFC5D83 (20) Node ID to receive (4) 05D 12345 Connection to a Windows system The values in this section of the table must match those used in Table 17, as indicated.
(12) Link station name NTCONN (13) Network name (2) NETID (14) CP name (3) WINNTCP (15) Remote LU (5) WINNTLU (16) Application TP (7) MQSERIES (17) Mode name (17) #INTER (18) CPI-C symbolic destination name NTCPIC (19) Remote network address (9) 08005AA5FAB9 (20) Node ID to receive (4) 05D 30F65 Connection to an AIX system The values in this section of the table must match those used in Table 21, as indicated.
(12) Link station name AIXCONN (13) Network name (1) NETID (14) CP name (2) AIXPU (15) Remote LU (4) AIXLU (16) Application TP (6) MQSERIES (17) Mode name (9) #INTER (18) CPI-C symbolic destination name AIXCPIC (19) Remote network address (8) 123456789012 (20) Node ID to receive (3) 071 23456 Connection to an HP-UX system The values in this section of the table must match those used in Table 24, as indicated.
(12) Link station name HPUXCONN (13) Network name (4) NETID (14) CP name (2) HPUXPU (15) Remote LU (5) HPUXLU (16) Application TP (7) MQSERIES (17) Mode name (6) #INTER (18) CPI-C symbolic destination name HPUXCPIC (19) Remote network address (8) 100090DC2C7C (20) node ID to receive (3) 05D 54321 Connection to an AT&T GIS UNIX (NCR UNIX) system The values in this section of the table must match those used in Table 26, as indicated.
(12) Link station name GISCONN (13) Network name (2) NETID (14) CP name (3) GISPU (15) Remote LU (4) GISLU (16) Application TP (5) MQSERIES (17) Mode name (7) #INTER (18) CPI-C symbolic destination name GISCPIC (19) Remote network address (8) 10007038E86B (20) Node ID to receive (9) 03E 00018 Connection to a Solaris system The values in this section of the table must match those used in Table 28, as indicated.
(12) Link station name SOLCONN (13) Network name (2) NETID (14) CP name (3) SOLARPU (15) Remote LU (7) SOLARLU (16) Application TP (8) MQSERIES (17) Mode name (17) #INTER (18) CPI-C symbolic destination name SOLCPIC (19) Remote network address (5) 08002071CC8A (20) Node ID to receive (6) 05D 310D6 Connection to an OS/400 system The values in this section of the table must match those used in Table 50, as indicated.
(12) Link station name AS4CONN (13) Network name (1) NETID (14) CP name (2) AS400PU (15) Remote LU (3) AS400LU (16) Application TP (8) MQSERIES (17) Mode name (17) #INTER (18) CPI-C symbolic destination name AS4CPIC (19) Remote network address (4) 10005A5962EF Connection to a z/OS system without CICS The values in this section of the table must match those used in Table 35, as indicated.
(12) Link station name MVSCONN (13) Network name (2) NETID (14) CP name (3) MVSPU (15) Remote LU (4) MVSLU (16) Application TP (7) MQSERIES (17) Mode name (6) #INTER (18) CPI-C symbolic destination name MVSCPIC (19) Remote network address (8) 400074511092 Connection to a VSE/ESA system The values in this section of the table must match those used in Table 52, as indicated.
(12) Link station name VSECONN (13) Network name (1) NETID (14) CP name (2) VSEPU (15) Remote LU (3) VSELU (16) Application TP (4) MQ01 (17) Mode name #INTER (18) CPI-C symbolic destination name VSECPIC (19) Remote network address (5) 400074511092
Explanation of terms
- (1) Configuration file name
- This is the unique name of the Communications Server for Linux 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 xsnadmin.
- (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
- 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 MQ01.
- (8) 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 Linux 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
- This is the path and name of the script file that invokes the WebSphere MQ program to run.
- (11) Local queue manager
- 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 Communications Server for Linux 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.
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.
AIX is a trademark of the IBM Corporation in the United States, other countries, or both.