IBM Support

IV62648: MQCMD_RESET_Q_STATS processing ends for all queues if one queue is damaged

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The command MQCMD_RESET_Q_STATS can be given a generic queue
    name, like ABC*. In this case the command server should return
    results for all matching queues. However, if the command
    encounters a damaged queue during its processing loop, then the
    loop stops, and the command server returns no more results for
    any other queues after that point. The output from the command
    will seem fine except that it will not include output for all
    queues that have been requested. This is unexpected. The user
    would expect to see results from as many queues as possible, and
    an error report at the end, if an error was encountered.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of the command MQCMD_RESET_Q_STATS in IBM MQ.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The processing loop should only end for severe errors. It should
    not cease trying to provide details for later queues in the loop
    if one queue is damaged.
    

Problem conclusion

  • The IBM MQ product code has been altered to cause the loop to
    continue even if a queue is damaged. In the case where one queue
    cannot be queried (example: object damaged), the loop will
    continue, attempting to return results for as many queues as
    posssible, and will add an error report at the end of the loop,
    containing the compcode/reason for the first failure
    encountered. If more than once failure occurs, then still only
    the first failure will be notified via a PCF error return. If
    there is a severe error, then the loop will stop immediately, as
    before.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.1       7.1.0.7
    v7.5       7.5.0.5
    v8.0       8.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

    IV62648

  • Reported component name

    WMQ AIX V7

  • Reported component ID

    5724H7221

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-07-17

  • Closed date

    2014-08-15

  • Last modified date

    2014-08-15

  • 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

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCPQ63","label":"APAR \/ Maintenance"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"710","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
15 August 2014