IBM Support

IT31856: Messages on SYSTEM.PROTECTION.ERROR.QUEUE cannot be processed byrunmqdlq using a DESTQ rule

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • runmqdlq fails to process a message from
    SYSTEM.PROTECTION.ERROR.QUEUE  using a rule which has full name
    of the queue in DESTQ attribute of dlq rule.
    for example:
    REASON(MQRC_SECURITY_ERROR)  DESTQ(MY.LOCAL.QUEUE) +
    ACTION(FWD) FWDQ(QL1) FWDQM(QM1) HEADER(NO)
    

Local fix

  • To be able to retrieve a message matching the rule, use a
    wildcard in DESTQ keyword.
    Ie:
       DESTQ(MY.LOCAL.QUEUE*)    or
       DESTQ(MY.LOCAL.*)
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users using the runmqdql dead letter queue handler against the
    MQ AMS SYSTEM.PROTECTION.ERROR.QUEUE, with a rule that specified
    a DESTQ value with a specific queue name.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    Messages put to the SYSTEM.PROTECTION.ERROR.QUEUE incorrectly
    provided the destination queue name in the dead letter header
    (MQDLH) as null-terminated, instead of space-padded as defined
    by the MQDLH specification.
    
    This caused runmqdlq DESTQ pattern matching to fail if a
    complete queue name was specified for the DESTQ in the match
    rule
    

Problem conclusion

  • The MQ AMS code has been modified to ensure the destination
    queue name in  the dead letter header is space padded when a
    message is put to the SYSTEM.PROTECTION.ERROR.QUEUE.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0 LTS   9.0.0.11
    v9.1 CD    TBC.
    v9.1 LTS   9.1.0.7
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT31856

  • Reported component name

    IBM MQ BASE M/P

  • Reported component ID

    5724H7261

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-02-13

  • Closed date

    2020-06-11

  • Last modified date

    2020-06-11

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    IBM MQ BASE M/P

  • Fixed component ID

    5724H7261

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
12 June 2020