IBM Support

IC79033: WMQ EXPLORER V7.0.1 ERROR TRYING TO CHANGE PROPERTIES FOR A LOCAL QUEUE MANAGER WHICH IS NOT RUNNING.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • WebSphere MQ Explorer v7.0.1 allows changes to the queue
    manager properties which affect registry settings.  For
    example, these include:
    
    o enabling exits
    o changing channels settings
    o transaction log files
    
    Some of these changes require a queue manager restart to be
    picked up.
    
    After setting up the queue manager to use a local API exit with
    an invalid module name, for example 'xxxx', the queue manager
    is stopped.  On restart, there is an error for the exit, and
    the queue manager fails to start.
    
    The error reported is:
    
    AMQ7214: The module for API Exit 'xxxx' could not be loaded.
    exitvalue = 71
    
    When an attempt is made to resolve this misconfiguration by
    re-editing the appropriate fields while the queue manager is
    stopped, WMQ Explorer reports:
    
    AMQ4043
    Queue manager not available for connection - reason 2059
    
    This procedure works when using WebSphere MQ v6, and is also
    successful if using 'amqmdain' commands rather than using
    WebSphere MQ Explorer v7.0.1 to make the configuration changes.
    

Local fix

  • Use amqmdain commands to fix the settings in the registry
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of WebSphere MQ Explorer V7.0.1, who
    try to alter the queue manager properties for a system local
    queue manager, while the queue manager is in the stopped state.
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM SUMMARY:
    When using the WebSphere MQ Explorer V7.0.1, when a user makes
    change to the queue manager properties page, a check is made to
    see if the queue manager is running.
    
    If the queue manager was stopped, the WebSphere MQ Explorer
    notified the user that the property change cannot be applied.
    However, this operation should be permitted for a system local
    queue manager, regardless of the running state of the queue
    manager.
    

Problem conclusion

  • The WebSphere MQ Explorer V7.0.1 code has been changed to allow
    an update to the queue manager properties for a system local
    queue manager, regardless of its running state.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC79033

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    701

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-10-03

  • Closed date

    2011-10-31

  • Last modified date

    2011-10-31

  • 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 WINDOWS V7

  • Fixed component ID

    5724H7220

Applicable component levels

  • R701 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":"7.0.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
31 October 2011