Using the Dead Letter Queue (DLQ) solution
Note
The earlier version of the DLQ solution was designed to function mostly as a reporting tool, notifying operators when dead letters have arrived and moving invalid dead letters to another user-specified queue. You can continue to use this solution; refer to Using the Dead Letter Queue solution (version 6.4.xx only).
However, BMC Software recommends that you use the current version of the DLQ solution because of improvements made in this release, including greater flexibility. The current version of the DLQ solution performs more functions which includes specifying retry attempts for moving messages to their destination queues, and when that is not possible, moving the messages to another permanent queue.
Table 1 describes the functions that the DLQ solution can perform.
Table 1. Dead Letter Queue solution functions
| Function | The DLQ solution can be configured to |
|---|---|
| Retry | Make multiple attempts to PUT the dead letter messages onto their original destination queues |
| Forward | Forward a dead letter message to another queue that you specify, including forwarding to a different queue manager |
| Delete | Delete a dead letter message as soon as it arrives on the dead letter queue or, the solution retries to send the message and deletes the message if the retry fails |
| Ignore | Ignore a dead letter message as soon as it arrives on the dead letter queue or, the solution retries to send the message and ignores the message if the retry fails |
| RemoveDLH | Remove the dead letter header (DLH) of dead letter messages that are retried, forwarded or moved prior to the action or the DLH can be left in place The default for retries is to remove the DLH and reconstitute the message. |
| Move | As a final disposition, attempt to move the message to another queue on the local queue manager, or if the queue is defined as remote, the solution can PUT the message on a remote queue manager |
| Authority | That when a message is PUT (during a retry, forward or move), the authority of the original application that attempted the PUT action is used or, that the authority of the MainView AutoOPERATOR BBI-SS PAS jobname is used |
| Flexibility | Use selection criteria and one or more rules to specify exactly which types of dead letter messages you want the solution to handle, even if handling it means just to ignore them |
| Status and debugging | Write status messages to the BBI journal when a retry is attempted and if it fails There are also debugging parameters that can show what parameters the solution used in addition to parameters that you can use to debug situations when messages cannot be PUT to a queue. |
| Alert | Issue a MainView AutoOPERATOR ALERT to a queue that you specify when a retry fails The ALERT contains various data to help identify the particular message in question. |
| Utility | Include an EXEC that can display or delete the arrays and to set status and debugging parameters |
Comments
Log in or register to comment.