Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Future consideration
Created by Guest
Created on Jan 31, 2020

make MQ rpm packages upgradable

This RFE is related to upgrade of rpm packages of MQ client and MQ server on RedHat (single stage migration).
RPM packages in general are upgradable. RMP or YUM take care of that.
There is no need to uninstall old maintenance level prior to installation of new version. However single stage MQ migration requires that on Linux: unistall old packages first, then install new version of rpm packages.
Could you make MQ rpm packages upgradable, like regular rpm packages?

Idea priority High
RFE ID 139844
RFE URL
RFE Product IBM MQ
  • Guest
    Reply
    |
    Feb 25, 2021

    Good day IBM Developement team and Sebastian Wilk,

    Thank you for your comments, input and improvements related to the upgrade procedure.
    I'm glad to see that the upgrade procedure from MQ 9.2.1 doesn't require uninstall anymore.
    "From IBM® MQ 9.2.1, you can upgrade an IBM MQ installation on Linux® systems without uninstalling the earlier version."

    https://www.ibm.com/support/knowledgecenter/bg/SSFKSJ_9.2.0/com.ibm.mq.mig.doc/q135200_.html

    Kind regards,

    Ikram Abasov

  • Guest
    Reply
    |
    Mar 18, 2020

    We will be considering this for a future version of MQ

  • Guest
    Reply
    |
    Mar 4, 2020

    Hey Ikram Abasov,

    we ran into the exact same issue when trying to update our MQ clients on Linux to a newer version.
    The solution IBM Support gave us is not satisfying at all, but less of a headache than uninstalling before installing a newer version.
    Instead of downloading the baseclient package for the Version you want to upgrade to, download the fixpack instead.

    For the sake of simplicity I'll provide our example:

    We started testing MQ Clients on linuxmachines with Version 9.1.0.1. For that we downloaded the base package(v 9.1.0.1) and installed it.
    We then tried to upgrade to Version 9.1.0.4 using the basepackage (v 9.1.0.4) and yum update.

    This ends up with the error that there is an existing Installation.

    We were then pointed to the fixpack 9.1.0.4 (https://www.ibm.com/support/pages/downloading-ibm-mq-version-9104)
    Despite fix central also being a massive pain in the [Deleted], using the fixpack you can "overinstall" your old Version.

    The fixpack will also have the character "U" in the Name of the files after you extracted it.

    We could then use yum install (not update) to upgrade to a newer version without uninstalling the old version.

    TL;DR

    Have a baseinstallation
    Download fixpack
    yum install (NOT update) the fixpack
    Done

    It is beyond me why the basic concept of updateable packages is not there, but for now this is what we have to deal with. Hope this helps.

    I left my vote here, since it causes alot of overhead to download separate packages with different content rather than just getting the new clientbase and roll with it.