Intercommunication

Defining a TCP connection

The channel definition at the sending end specifies the address of the target. The TCP service is configured for the connection at the receiving end.

Specify the host name, or the TCP address of the target machine, in the Connection Name field of the channel definition. Port number 1414 is assigned by the Internet Assigned Numbers Authority to WebSphere MQ.

To use a port number other than the default, change the connection name field thus:

Connection Name REMHOST(1822)

where REMHOST is the hostname of the remote machine and 1822 is the port number required. (This must be the port that the listener at the receiving end is listening on.)

Alternatively you can change the default sending port number by specifying it in the queue manager configuration file (qm.ini):

TCP:
  Port=1822

For more information about the values you set using qm.ini, see Appendix C, Configuration file stanzas for distributed queuing.

Receiving channels using Compaq (DIGITAL) TCP/IP services (UCX) for OpenVMS

To use Compaq (DIGITAL) TCP/IP Services (UCX) for OpenVMS, you must configure a UCX service as follows:

Create a file consisting of one line and containing the DCL command to start the TCP/IP receiver program, amqcrsta.exe:
```
    $ mcr amqcrsta [-m Queue_Man_Name]
```
Place this file in the SYS$MANAGER directory. In this example the name of the file is MQRECV.COM.
Notes:
1. If you have multiple queue managers you must make a new file and UCX service for each queue manager.
2. Ensure that the protection on the file and its parent directory allow it to be executable, that is, the protection is /PROT=W:RE.
Create a UCX service to start the receiving channel program automatically:
```
$ UCX
UCX> set service <p1>/port=<p2>/protocol=TCP/user_name=MQM -
UCX> /process=<p3>/file=<p4>/limit=<p5>
```
where:

p1
Is the service name, for example MQSERIES01. A unique name is required for each queue manager defined.
p2
Is the TCP/IP port number in the range 1 to 65 535. The default value for WebSphere MQ is 1414.
p3
Is the process name. This consists of a string up to 15 characters long.
p4
Is the name of the startup command file, for example, SYS$MANAGER:MQRECV.COM.
p5
Is the process limit. This is the maximum number of connections allowed using the port number. If this limit is reached, subsequent requests are rejected.
Note:
Each channel represents a single connection to the queue manager.

If a receiving channel does not start when the sending end starts, it is probably due to the permissions on the file being incorrect.
To enable the service upon every system IPL (reboot), issue the command
$ UCX SET CONFIGURATION ENABLE SERVICE MQSERIES

Using the TCP/IP SO_KEEPALIVE option

If you want to use the SO_KEEPALIVE option (as discussed in Checking that the other end of the channel is still available) you must the add the following entry to your queue manager configuration file (qm.ini) or the Windows NT registry:

TCP:
   KeepAlive=yes

Receiving channels using Cisco MultiNet for OpenVMS

To use Cisco MultiNet for OpenVMS, you must configure a MultiNet service as follows:

Create a file consisting of one line and containing the DCL command to start the TCP receiver program, amqcrsta.exe:
```
    $ mcr amqcrsta.exe [-m Queue_Man_Name]
```
Place this file in the SYS$MANAGER directory.
Notes:
1. If you have multiple queue managers you must make a new file and MultiNet service for each queue manager.
2. Ensure that the protection on the file and its parent directory allow it to be executable, that is, the protection is /PROT=W:RE.

Create a MultiNet service to start the receiving channel program automatically:

$ multinet configure/server
MultiNet Server Configuration Utility 3.5 (101)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG> add WebSphere MQ
[Adding new configuration entry for service "MQSERIES"]
Protocol: [TCP]
TCP Port number: 1414
Program to run: sys$manager:mqrecv.com
[Added service MQSERIES to configuration]
[Selected service is now MQSERIES]
SERVER-CONFIG> set flags UCX_SERVER
 MQSERIES flags set to <UCX_SERVER>]
SERVER-CONFIG> set username MQM
[Username for service MQSERIES set to MQM]
SERVER-CONFIG> exit
[Writing configuration to MULTINET_COMMON_ROOT:SERVICES.MASTER_SERVER]
$

The service is enabled automatically after the next system IPL (reboot). To enable the service immediately, issue the command
'MULTINET CONFIGURE /SERVER RESTART'.

Receiving channels using Attachmate PathWay for OpenVMS

To use Attachmate PathWay for OpenVMS to start channels, you must configure a PathWay service as follows:

Create a file consisting of one line and containing the DCL command to start the TCP/IP receiver program, amqcrsta.exe:
```
      $ mcr amqcrsta [-m Queue_Manager_Name]
```
Place this file in the SYS$MANAGER directory. In this example the name mqrecv.com is used.

Create an Attachmate service to start the receiving channel program automatically.

You do this by adding the following lines to the file TWG$COMMON:[NETDIST.ETC]SERVERS.DAT.

      # MQSeries
      service-name    MQSeries
      program         SYS$MANAGER:MQRECV.COM
      socket-type     SOCK_STREAM
      socket-options  SO_ACCEPTCONN | SO_KEEPALIVE
      socket-address  AF_INET , 1414
      working-set     512
      priority        4
      INIT            TCP_Init
      LISTEN          TCP_Listen
      CONNECTED       TCP_Connected
      SERVICE         Run_Program
      username        MQM
      device-type     UCX

Receiving channels using Process Software Corporation TCPware

To use Process Software Corporation TCPware, you must configure a TCPware service as follows:

Create a file consisting of one line and containing the DCL command to start the TCP receiver program amqcrsta.exe:
```
     $ mcr amqcrsta (-m Queue_Manager_Name)
```
Place this file in the SYS$MANAGER directory. In this example the name of the file is MQRECV.COM.
Notes:
1. If you have multiple queue managers you must make a new file and TCPware service for each queue manager.
2. Ensure that the protection on the file and its parent directory allow it to be executable, that is, the protection is /PROT=W:RE.

Create a TCPware service to start the receiving channel program automatically:

Edit the TCPWARE:SERVICES. file and add an entry for the service you want to use:
```
         MQSeries 1414/tcp # MQSeries port
```

Edit the TCPWARE:SERVERS.COM file and add an entry for the service defined in the previous step:

         $! SERVERS.COM
         $!
         $ RUN TCPWARE:NETCU
         ADD SERVICE MQSeries BG_TCP -
 
             /INPUT=SYS$MANAGER:MQRECV.COM -
             /LIMIT=6 -
             /OPTION=KEEPALIVE -
             /USERNAME=MQM
 
         EXIT