+

Search Tips | Advanced Search

Coexistence

Queue managers, with different names, can coexist on any server as long as they use the same IBM MQ installation. On z/OS, UNIX, Linux, and Windows, different queue managers can coexist on the same server and be associated with different installations. In addition to queue managers coexisting on a server, objects, and commands must work correctly with different queue managers running at different command levels.


Multiple queue manager versions in z/OS

There can be several IBM MQ subsystems in a z/OS image, and they can use different versions of IBM MQ, provided that the IBM MQ early code modules are of the latest version being used. (These modules are loaded at z/OS IPL time and are shared among all the IBM MQ subsystems in the z/OS image.)

This means that we can run one queue manager at the latest version and another in the same image with an earlier version, provided that the early code is that of the latest version.

The coexistence section lists restrictions in the use of objects and commands when they are used with queue managers at multiple command levels. The queue managers might be running on a single server, or in a cluster.

  • Queue manager coexistence
    Queue managers, with different names, can coexist on any server as long as they use the same IBM MQ installation. On z/OS, UNIX, Linux, and Windows, different queue managers can coexist on the same server and be associated with different installations.
  • Multi-installation queue manager coexistence on UNIX, Linux, and Windows
    We can install multiple copies of IBM MQ for UNIX, Linux, and Windows on the same server. The installations must be at Version 7.1 or later, with one exception. One Version 7.0.1 installation, at fix pack level 6, or later, can coexist with multiple Version 7.1, or later installations.
  • Mixed version cluster coexistence
    A cluster can contain queue managers running at IBM MQ Version 9.2, and any currently supported earlier level of the product. However new features cannot be exploited from queue managers at an earlier level.
  • ISPF operations and control panels on z/OS
    When using the operations and control panels, the IBM MQ libraries we use in ISPF must be compatible with the queue manager we are working with.
  • Queue sharing group coexistence on z/OS
    In general, queue managers running on IBM MQ for z/OS Version 9.2.0 can be part of a queue sharing group with queue managers running on IBM MQ for z/OS Version 9.0.0 or later. This applies to any combination of Continuous Delivery and Long Term Support releases from Version 9.0.0.
  • Properties of objects in a queue sharing group with queue managers at different versions on z/OS
    Attributes that did not exist in earlier versions can be created and altered on queue managers of a later version in a mixed queue sharing group. The attributes are not available to queue managers in the group that are at an earlier level.
  • MQSC commands in a queue sharing group with queue managers at different versions on z/OS
    Existing MQSC commands using new keywords and attribute values can be entered for routing to a migrated queue manager. We can enter the commands on any queue manager. Route the commands using CMDSCOPE. Commands with new keywords and attribute values, or new commands, routed to a previous version of queue manager, fail.

Parent topic: Coexistence, compatibility, and interoperability


Related concepts


Related tasks

Last updated: 2020-10-04