For an application, the local queue manager is the queue manager to which the application is connected. Queues managed by the local queue manager are said to be local to that queue manager.
Use the MQSC command DEFINE QLOCAL to create a local queue. You can also use the default defined in the default local queue definition, or you can modify the queue characteristics from those of the default local queue.
Using the MQSC command shown below, we define a queue called ORANGE.LOCAL.QUEUE, with the following characteristics:
DEFINE QLOCAL (ORANGE.LOCAL.QUEUE) + DESCR('Queue for messages from other systems') + PUT (ENABLED) + GET (ENABLED) + NOTRIGGER + MSGDLVSQ (PRIORITY) + MAXDEPTH (5000) + MAXMSGL (4194304) + USAGE (NORMAL);
We recommend that each queue manager has a local queue to be used as a dead-letter queue so that messages that cannot be delivered to their correct destination can be stored for later retrieval. You must tell the queue manager about the dead-letter queue. You do this by specifying a dead-letter queue name on the crtmqm command (crtmqm -u DEAD.LETTER.QUEUE, for example), or by using the DEADQ attribute on the ALTER QMGR command to specify one later. You must define the dead-letter queue before using it.
We supply a sample dead-letter queue called SYSTEM.DEAD.LETTER.QUEUE with the product. This queue is automatically created when you create the queue manager. You can modify this definition if required, and rename it.
A dead-letter queue has no special requirements except that:
WebSphere MQ provides a dead-letter queue handler that allows you to specify how messages found on a dead-letter queue are to be processed or removed. For further information, see The WebSphere MQ dead-letter queue handler.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
deflq |