Implementing the Dead Letter Queue solution


Use the following procedure to implement the Dead Letter Queue solution.

  1. Update Rule MQDEDQ04 to specify queue managers that you want to automate with this solution.

  2. Update Rule MQDEDQ05 to specify a retry interval that the solution uses to re-send dead letter messages to the appropriate queue.

  3. Select and update the Rules named MQDEDQ06 - MQDEDQ18. When you are updating these Rules, you must specify the Rule-initiated EXEC parameters that:

    You must update one (or more) of these Rules (or create your own set of Rules) because if you do not, the solution takes no action when a dead letter message arrives.

  4. Make a backup copy of your Rules by copying the updated Rule Set named AAORULBQ to another data set member with a different name.BMC recommends that you make a back up copy because when you apply maintenance in the the future that includes updates to the distributed AAORULBQ Rule Set, you will lose any changes that you made.

  5. Decide which messages will use the default authority of the BMC AMI Ops Automation BBI-SS PAS jobname and which messages will use the original application authority (MQPMO_PASS_ALL_CONTEXT).

  6. Based on the decisions you made in step 5, specify the appropriate PA(xxx) setting in the Rules.

  7. Verify that BMC AMI OpsA has the correct authority setting on the z/OS MQ system to perform the OPEN, GET and PUT functions with the dead letter queue and any other queues and queue managers that the DLQ solution forwards or moves messages to.

  8. (optional) Execute the EXEC named QMQDEDQ5 which specifies any status or debug messages that you might want to write to the BBI journal.

  9. Enable the Rules that you have updated by entering an E next to them on the Rule Processor Ruleset Overview panel.The solution should now be ready to work.

This section contains the following topics:


 

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