Newer version of documentation BMC provides a newer version of the documentation for this version of the product. As a result, BMC no longer accepts comments in this space.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see bao8301.

Using the Dead Letter Queue (DLQ) solution


BMC AMI Ops Automation

 includes the Dead Letter Queue (DLQ) solution that contains two parts you can use together or separately.

Following table describes the functions that the DLQ solution can perform.

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 BMC AMI Ops Automation 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 BMC AMI OpsA 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

This section contains the following topics:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*