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.

Optional Rule-initiated EXEC parameter settings that determine how the DLQ solution processes DLQ messages


The following table describes the EXEC parameters that you can use to specify how the Rule-initiated EXEC processes DLQ messages.

Parameter

Description

DP

Disposition: specifies a 1-character value which configures how the DLQ solution processed a message in the dead letter queue.

Choose one of the following optional parameters:

  • R (Retry)—the DLQ solution should attempt to PUT the message on either the destination queue, the ReplyToQ or a forwarding queue as specified with the FQ( ) parameter. Refer to the FQ( ) parameter in this table for more information. The default value for this parameter is 3.
  • D (Delete)—the message should be deleted from the dead letter queue by performing a destructive GET for the message.
  • F (Forward)—the DLQ solution should forward (PUT) the message to a queue specified by the user with parameter FQ(qname). If this PUT fails, the message will be ignored from that point on.
  • I (Ignore)—the message is ignored by the DLQ solution. Note that the array that keeps track of dead letter messages will retain a row for each message that is ignored. For each ignored message the solution will have to get an extra row from the array during processing. Another option would be to forward the message to another queue. The default setting for this parameter is I.

FD

Final Disposition: specifies a one-character value that tells the DLQ solution what to do if the retries fail.

Possible values are as follows:

  • D (Delete)—the message is deleted from the dead letter queue by performing a destructive GET for the message
  • I (Ignore)—the message is ignored by the DLQ solution

    Note

    The array which keeps track of dead letter messages retains a row for each message that is ignored. For each ignored message, the solution obtains an extra row from the array during processing.

    The default setting for this parameter is I (ignore).

  • M (Move)—the message is moved to another user-specified queue with the parameter MQ(queue)

    BMC Software recommends that you use this setting when the message cannot be placed on its original destination queue but you do not want to delete the message. This setting leaves the DLQ solution with fewer messages to maintain past while processing dead letter messages.

FQ

Forward Queue:

Specify one of the following values:

  • R (Reply)—Reply to Queue from the Message Descriptor

    Example

    FQ(R)

  • D (Destination)—Destination queue from the DLH

    Example

    FQ(D)

    The default value for this parameter is D.

  • Blank—Specify a queue of your choosing to which the message will be forwarded after arriving on the dead letter queue.

    FQ(queuename)The message is PUT on the local queue manager unless a different queue manager is specified in the FQM(qm) parameter. Refer to the description FQM(qmgr) in this table for more information.

FQM

Forward Queue Manager: specifies a remote queue manager to which the message should be forwarded when the FQ(qname) parameter is used.

Specifies one of the following values:

  • R (ReplyToQMgr)—ReplyToQMgr from the Message Descriptor

    Example

    FQM(R)

  • D (DestQMgr)—DestQMgr from the DLH

    FQM(D)This is the default value for this parameter.

  • Blank—Specify a queue manager name of your choosing on which the forwarded message will be PUT when the forwarding FQ( ) parameter is used

RD

Remove Dead Letter Header: specifies whether or not the Dead Letter Header (DLH) should be removed when the message is retried, forwarded or moved (moved applies to final disposition processing only).

Specify Y or N.

Example

RD(Y)

For retry processing the default is Y; for forwarding and moving the default is N. With this option, the original message is reconstituted by moving the Encoding, CodedCharSetId and Format fields from the DLH back into the message descriptor (MD) prior to the PUT of the message.

PA

Put Authorization: specifies whether to use the authority of the original application that is attempting to PUT the message or that of the BMC AMI Ops Automation for MQ BBI-SS PAS jobname when retrying the message or forwarding or moving it to another queue.

Specifying PA(D) for default, causes the jobname of the BBI-SS PAS to be used (MQPMO_SET_IDENTITY_CONTEXT) for authority checking by MQ. This is the default setting.

Specifying PA(C) will cause the context fields from the original application that PUT the message to be used for authority checking (MQPMO_PASS_ALL_CONTEXT).

R

Retry: specifies the number of retries in which the DLQ solution should attempt to PUT the dead letter message on its original destination queue or other queue as specified in the FQ(xxx) parameter.

Valid values are 1-999999999. The default is 3.

Example

R(2)

After all retries have been exhausted the message is subject to Final Disposition processing.

AL

Alert: specifies a queue name in which an alert should be created should all retries fail. The queue name specified must follow the normal syntax requirements. See Using-Rules-with-BMC-AMI-Ops-Automation and Using-advanced-automation-with-BMC-AMI-Ops-Automation for more information about how to create ALERTs.

There is no default and if you do not specify a value for this parameter means that the Rule will not create an LALERT.


Example

AL(MQ_Q1)

When the Rule issues the ALERT, the ALERT will contain the following attributes:

  • Queue Manager
  • Destination Queue
  • Last 4 bytes of MsgId in hexadecimal
  • DLH Reason
  • Number of retries
  • Final Disposition



 

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