IBM Support

IT22455: IBM MQ Appliance: queue manager configured as a primary DR queuemanager cannot be started or deleted

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

  • After a queue manager is configured as a primary DR queue
    manager using the
    crtdrprimary command, it can no longer be started or deleted.
    
    The user may see errors such as these when trying to delete or
    start the queue manager:
    
    dltmqm MYDRQM
    Removing high availability configuration on this appliance.
    Failed to remove high availability configuration on this
    appliance.
    AMQ7021: An error occurred while deleting the directory
    structure for
    the queue
    manager.
    
    strmqm MYDRQM
    IBM MQ Appliance queue manager 'MYDRQM' HA sub-system is already
    active.
    
    The addDRPrimary trace file from runmqras may show entries such
    as this:
    
    Mon Oct 30 09:09:14 EDT 2017:    drbdadm -- --force create-md
    drbd_MYDRQM
    Mon Oct 30 09:09:14 EDT 2017:    drbd.d/MYDRQM.res:32: Parse
    error: 'ssocks | sdp | ipv4 | ipv6 | <ipv4 address> ' expected,
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of the IBM MQ Appliance who configure primary and
    secondary DR queue managers may be affected by this issue.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The crtdrprimary command accepts a RecoveryIP for the -i option.
     If a valid hostname is given instead of an IP address then this
    is accepted and stored as a field inside a configuration file.
     A task which is called during strmqm and dltmqm later read the
    field inside the configuration file and expected to find a
    resolved IP address.  When a hostname was found the task ended
    abnormally and this caused the strmqm and dltmqm commands to
    fail.
    

Problem conclusion

  • The MQ Appliance firmware has been modified so that a valid
    hostname will be resolved to an IP address and this address is
    then stored in the configuration file.  An invalid hostname will
    result in a configuration error and it will not be stored in the
    configuration file.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0 CD    9.0.5
    
    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

    IT22455

  • Reported component name

    IBM MQ APPL M20

  • Reported component ID

    5725Z0900

  • Reported release

    902

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-09-19

  • Closed date

    2018-01-12

  • Last modified date

    2018-01-12

  • 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

    5725Z0900

Applicable component levels

[{"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":"902","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
12 January 2018