Monitoring and controlling channels on IBM i

Use the DQM commands and panels to create, monitor, and control the channels to remote queue managers. Each queue manager has a DQM program for controlling interconnections to compatible remote queue managers.

The following list is a brief description of the components of the channel control function:
  • Channel definitions are held as queue manager objects.
  • The channel commands are a subset of the IBM® MQ for IBM i set of commands.

    Use the command GO CMDMQM to display the full set of IBM MQ for IBM i commands.

  • You use channel definition panels, or commands to:
    • Create, copy, display, change, and delete channel definitions
    • Start and stop channels, ping, reset channel sequence numbers, and resolve in-doubt messages when links cannot be re-established
    • Display status information about channels
  • Channels can also be managed using MQSC
  • Channels can also be managed using IBM MQ Explorer
  • Sequence numbers and logical unit of work (LUW) identifiers are stored in the synchronization file, and are used for channel synchronization purposes.

You can use the commands and panels to: define message channels and associated objects, and monitor and control message channels. By using the F4=Prompt key, you can specify the relevant queue manager. If you do not use the prompt, the default queue manager is assumed. With F4=Prompt, an additional panel is displayed where you can enter the relevant queue manager name and sometimes other data.

The objects you need to define with the panels are:
  • Transmission queues
  • Remote queue definitions
  • Queue manager alias definitions
  • Reply-to queue alias definitions
  • Reply-to local queues
  • Message channel definitions

For more information about the concepts involved in the use of these objects, see Configuring distributed queuing.

Channels must be completely defined, and their associated objects must exist and be available for use, before a channel can be started.

In addition, the particular communication link for each channel must be defined and available before a channel can be run. For a description of how LU 6.2 and TCP/IP links are defined, see the particular communication guide for your installation.

For more information about creating and working with objects, see: