Upgrading an IBM MQ installation on Linux using the rpm command

You can use rpm to upgrade an IBM® MQ installation on Linux® systems.

Before you begin

The version that you are upgrading from must be IBM MQ 9.2.0, or later.

If your current version is at IBM MQ 9.4.0 Fix Pack 5 or later, you can use the rpm -Uvh command to upgrade your installation with fix packs installed. That is, the fix pack number in the version.release.modification.fixpack (V.R.M.F) release identifier does not need to be 0. If your current version is earlier than IBM MQ 9.4.0 Fix Pack 5, use the rpm -Uvh command to upgrade only if no fix packs are installed.

Important:
  • [Deprecated]The IBM MQ Bridge to Salesforce is deprecated across all releases from November 22 2022 (see US Announcement letter 222-341).
  • [Removed]The IBM MQ Bridge to Salesforce is removed from the product at IBM MQ 9.4.0. Salesforce connectivity can be achieved with IBM App Connect Enterprise. Salesforce Input and Salesforce Request nodes can be used to interact with Salesforce applications. For more information, see Using Salesforce with IBM App Connect Enterprise.

    On Linux for x86-64 only, if you are migrating from an installation where the IBM MQ Bridge to Salesforce is present, you must remove it before you upgrade to IBM MQ 10.0.0 or later.

  • [Removed]For Continuous Delivery, the IBM MQ Bridge to blockchain is removed from the product at IBM MQ 9.3.2.

    [Removed]For Long Term Support, IBM MQ Bridge to blockchain is removed at IBM MQ 9.3.0 Fix Pack 15.

    Blockchain connectivity can be achieved with IBM App Connect or through App Connect capabilities available with IBM Cloud Pak® for Integration.

    On Linux for x86-64 only, if you are migrating from an installation where the IBM MQ Bridge to blockchain is present, you must remove it before you upgrade to IBM MQ 10.0.0 or later.

  • From IBM MQ 9.3.0, IBM MQ Explorer has been removed from the IBM MQ install package. On Linux for x86-64 only, if you are migrating on an installation where the IBM MQ Explorer is present as part of the IBM MQ installation, you must remove it before you upgrade to IBM MQ 9.3.0 or later.
  • [MQ 10.0.0 Jun 2026]From IBM MQ 10.0.0, Russian language translation support is removed. If you are upgrading from an earlier version that includes this component on the Linux platform, you must manually uninstall it before proceeding with the upgrade. Failure to do so might result in the following error during the upgrade process:
    MQSeriesRuntime = 9.x.x-0 is needed by (installed) MQSeriesMsg_ru-9.x.x-0.x86_64
For more information about modifying an IBM MQ installation using rpm, see Uninstalling or modifying IBM MQ on Linux using rpm.

Procedure

  1. Complete the following tasks:
    1. Stop all your IBM MQ applications.

      If you use the Managed File Transfer (MFT) component, ensure that any file transfers that MFT agents are engaged in are completed. The SYSTEM.FTE.STATE queues must contain no messages.

    2. Stopped the mqweb server by using the endmqweb command.
    3. Stopped your listeners by using the endmqlsr command.
    4. Stopped all your queue managers by using the endmqm command.
      If a queue manager is part of a cluster, you must suspend the queue manager before you stop it. For more information, see Maintaining a queue manager in a cluster.
    5. Backed up your data.
  2. Log in as root, or switch to the root user by using the su or su - commands. Alternatively, you can use the sudo command to run commands as the root user, if your system administrator gave you the privilege to do so.

    To use the sudo command, add sudo before the command that you want to run. For more information about the su and sudo commands, see Exploring the differences between sudo and su commands in Linux on the Red Hat® website.

  3. Optional: If your installation media is a downloadable installation image, obtained from Passport Advantage, you must decompress the tar.gz file and extract the installation files from the file:
    1. Decompress the file by using the following command:
      gunzip partName.tar.gz
      where partName is the name of the installation image file.
    2. Extract the installation files from the file by using the following command:
      tar -xvf partName.tar
      where partName is the name of the installation image file.
      Important: You must use GNU tar (also known as gtar) to unpack any tar images.
  4. Set your current directory to the location of the installation files. The location might be a network location, or a local file system directory.
  5. Optional: If this is not the only installation on the system, or if you want to upgrade an IBM MQ installation in a non default location, run the crtmqpkg to create a unique set of packages to upgrade:
    ./crtmqpkg suffix
    where suffix specifies a name of your choosing that uniquely identifies the installation packages on the system. suffix is not the same as an installation name, although the names can be identical. suffix is limited to 16 characters in the ranges A-Z, a-z, and 0-9.
    Note: This command creates a full copy of the installation packages in a temporary directory. By default, the temporary directory is located at /var/tmp. You must ensure that the system has enough free space before you run this command. To use a different location, you can set the TMPDIR environment variable before you run the crtmqpkg command. For example:
    $ TMPDIR=/test ./crtmqpkg suffix installationPath
  6. Set your current directory to the location of the installation packages. If you used the crtmqpkg command, this directory is the location that is specified when the crtmqpkg command operation completes successfully.
  7. You have the option of accepting the license before or after you install the product. To accept the license before installing, run the mqlicense.sh script. The license agreement is displayed in a language appropriate to your environment and you are prompted to accept or decline the terms of the license:
    • To display the license agreement in the default manner, which uses an X-window where possible, use the following command:
      ./mqlicense.sh
    • To display the license agreement as text in the current shell, which can be read by a screen reader, use the following command:
      ./mqlicense.sh -text_only 
    See Accepting the license on IBM MQ for Linux for more information about license acceptance.
  8. Upgrade IBM MQ:
    • To upgrade all available components in the default location, use the following command:
      rpm -Uvh MQSeries*
    • To upgrade specific components in the default location, use the following command:
      rpm -Uvh packageName.rpm
      where packageName.rpm is a list of one of more components to upgrade. For a full list of components, see IBM MQ rpm components for Linux systems.
    • To upgrade all available components in a non default location, use the following command:
      rpm --prefix installationPath -Uvh MQSeries*
      where installationPath specifies the path where IBM MQ is installed.
    • To upgrade specific components in a non default location, use the following command:
      rpm --prefix installationPath -Uvh packageName.rpm
      where installationPath specifies the path where IBM MQ is installed, and packageName.rpm is a list of one of more components to upgrade. For a full list of components, see IBM MQ rpm components for Linux systems.
  9. Use the dspmqver command to verify that the version is as expected:
    dspmqver