IBM Support

IT23413: Running crtmqm -md against an existing queue manager removes thequeue manager's data directory

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

  • Running "crtmqm -md <directory> <qmName>" against a queue
    manager which already exists removes the queue manager's data
    directory.
    

Local fix

  • Do not run crtmqm -md against an existing queue manager
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of MQ v8 and v9, who incorrectly supply
    the name of an existing queue manager and the -md flag to the
    crtmqm command.
    
    Furthermore, this issue is only observed if the queue manager
    was originally created using the default data directory.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A logic error within the crtmqm code path taken when an
    alternate data directory was specified with the -md option
    resulted in destructive file operations being performed before
    the check that the queue manager did not exist.
    
    In the case where all of the conditions described in the users
    affected section were true, this resulted in the removal of the
    existing queue manager's data directory.
    

Problem conclusion

  • This issue in the crtmqm command has been addressed so that the
    command returns with the following error in this scenario:
    
    AMQ8110: WebSphere MQ queue manager already exists.
    
    The existing queue manager's data directory remains in place.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.9
    v9.0 CD    9.0.5
    v9.0 LTS   9.0.0.3
    
    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

    IT23413

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-12-07

  • Closed date

    2018-02-13

  • Last modified date

    2018-02-13

  • 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 MP

  • Fixed component ID

    5724H7251

Applicable component levels

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

Document Information

Modified date:
13 February 2018