IBM Support

IT19240: MQ APPLIANCE MANUAL STRMQM FAILS AFTER FAILED AUTOMATED STARTUP ATTEMPTS

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

  • In the case where the HA layer has logged a number of failed
    attempts to automatically start the queue manager (for example
    due to
    a full filesystem) after the issue has been resolved, running
    strmqm will
    fail to start the HA queue manager due to these previously
    logged failed attempts.
    

Local fix

  • Reboot the MQ Appliance
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the MQ Appliance who are attempting
    to use strmqm to start a queue manager which is part of an HA
    group, and has failed to be started automatically multiple times
    due to a transient issue which is now resolved.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    An omission in the logic of the HA queue manager startup routine
    failed to clear internal state from previous automated startup
    attempts when a manual start was requested.
    
    This meant that the queue manager did not attempt to start, even
    if the startup would have succeeded.
    

Problem conclusion

  • This internal state information is now correctly cleared when
    performing a manual queue manager start using the strmqm
    command.
    
    If the original error condition (which prevented automated
    startup attempts from succeeding) still persists, an error will
    be logged by strmqm in the queue manager error log.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.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

    IT19240

  • Reported component name

    IBM MQ APPL M20

  • Reported component ID

    5725S1400

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-13

  • Closed date

    2017-04-28

  • Last modified date

    2017-04-28

  • 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 APPL M20

  • Fixed component ID

    5725S1400

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS5K6E","label":"IBM MQ Appliance"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
28 April 2017