IBM Support

IV78343: runmqtrm incorrectly discards a non-trigger message if it fails to put it to the dead letter queue

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • WebSphere MQ utility program runmqtrm (Run MQ Trigger Monitor),
    on encountering an error condition while processing a message
    from its input queue, attempted to put the message to the Dead
    Letter Queue (DLQ).
    
    The first error condition was because the user had supplied the
    wrong queue name via the -q switch on the command line.  So,
    runmqtrm was reading a message that was not a valid trigger
    message.
    
    The trigger monitor encountered a further error when trying to
    put to the DLQ (example: queue-full). In this situation,
    runmqtrm should normally back out the MQGET from its input
    queue, and stop, but instead the MQGET was committed, and so the
    message was lost.
    
    (The only valid exception to this rule is when the message
    descriptor's report options include MQRO_DISCARD_MSG.  Messages
    with that flag are eligible to be discarded by a program if they
    appear on its input queue).
    

Local fix

  • Ensure that runmqtrm is only run against a INITQ which will
    contain only validly-formed trigger messages.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of runmqtrm, where they mistakenly supply the wrong queue
    name via the -q switch on the command line.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    runmqtrm was not obeying normal message exception processing
    practices.
    

Problem conclusion

  • The product source code for runmqtrm has been corrected so it
    will obey normal practices for exception processing.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.1.15
    v7.1       7.1.0.8
    v7.5       7.5.0.8
    v8.0       8.0.0.6
    v9.0 CD    9.0.2
    v9.0 LTS   9.0.0.1
    
    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

    IV78343

  • Reported component name

    WMQ AIX V7

  • Reported component ID

    5724H7221

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-10-26

  • Closed date

    2016-07-28

  • Last modified date

    2017-06-01

  • 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

    WMQ AIX V7

  • Fixed component ID

    5724H7221

Applicable component levels

  • R710 PSY

       UP

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

Document Information

Modified date:
08 March 2021