Work with local IBM MQ objects

We can administer local IBM MQ objects to support application programs that use the Message Queue Interface (MQI).

About this task

In this context, local administration means creating, displaying, changing, copying, and deleting IBM MQ objects.

In addition to the approaches described in this section, we can use the IBM MQ Explorer to administer local IBM MQ objects. For more information, see Administration using the IBM MQ Explorer.

• Work with queue managers
  We can use control commands to start and stop a queue manager. We can use MQSC commands to display or alter queue manager attributes.
• Stopping MQI channels
  When we issue a STOP CHANNEL command against a server-connection channel, we can choose what method to use to stop the client-connection channel. This means that a client channel issuing an MQGET wait call can be controlled, and we can decide how and when to stop the channel.
• Work with local queues
  This section contains examples of some MQSC commands used to manage local, model, and alias queues.
• Work with remote queues
  A remote queue is a local definition of a remote queue. That is, a definition on a local queue manager that refers to a queue on a remote queue manager.
• Work with alias queues
  We can define an alias queue to refer indirectly to another queue or topic.
• Work with model queues
  A queue manager creates a dynamic queue if it receives an MQI call from an application specifying a queue name that has been defined as a model queue. The name of the new dynamic queue is generated by the queue manager when the queue is created. A model queue is a template that specifies the attributes of any dynamic queues created from it. Model queues provide a convenient method for applications to create queues as required.
• Work with dead-letter queues
  Each queue manager typically has a local queue to use as a dead-letter queue, so that messages that cannot be delivered to their correct destination can be stored for later retrieval. You tell the queue manager about the dead-letter queue, and specify how messages found on a dead-letter queue are to be processed. Using dead-letter queues can affect the sequence in which messages are delivered, so you might choose not to use them.
• Work with administrative topics
  Use MQSC commands to manage administrative topics.
• Work with subscriptions
  Use MQSC commands to manage subscriptions.
• Work with services
  Service objects are a means by which additional processes can be managed as part of a queue manager. With services, we can define programs that are started and stopped when the queue manager starts and ends. IBM MQ services are always started under the user ID of the user who started the queue manager.
• Manage objects for triggering
  IBM MQ enables you to start an application automatically when certain conditions on a queue are met. For example, you might want to start an application when the number of messages on a queue reaches a specified number. This facility is called triggering. We have to define the objects that support triggering.
• Use the dmpmqmsg utility between two systems
  The dmpmqmsg utility (formerly qload) has been incorporated into the product from Version 8.0. Formerly the utility has been available as SupportPac MO03.

Parent topic: Administer IBM MQ