Set up communication for IBM i

When a distributed-queuing management channel is started, it tries to use the connection specified in the channel definition. For it to succeed, it is necessary for the connection to be defined and available.

DQM is a remote queuing facility for IBM MQ for IBM i. It provides channel control programs for the IBM MQ for IBM i queue manager which form the interface to communication links, controllable by the system operator.

Before a channel can be started, the transmission queue must be defined as described in this section, and must be included in the message channel definition.

We can choose between the following two forms of communication between IBM MQ for IBM i systems:

Defining a TCP connection on IBM i
For TCP, a host address can be used, and these connections are set up as described in the IBM i Communication Configuration Reference.

In the TCP environment, each distributed service is allocated a unique TCP address which can be used by remote machines to access the service. The TCP address consists of a host name/number and a port number. All queue managers use such a number to communicate with each other by way of TCP.
Receiving on TCP
This form of communication requires the definition of an IBM i SNA logical unit type 6.2 (LU 6.2) that provides the physical link between the IBM i system serving the local queue manager and the system serving the remote queue manager. Refer to the IBM i Communication Configuration Reference for details on configuring communications in IBM i.

In addition, where needed, the triggering arrangement must be prepared with the definition of the necessary processes and queues.