IBM announces IBM MQ V8


There are some things that come around every day. Good things, like new business and new customers. Other daily occurrences are not so good, like hardware failures, network problems, or security fixes to apply. Then there are some things that come around much less frequently, but they are worth waiting for. Good days like when a new version of IBM MQ is announced. Days like today.

That’s right. At IBM we are happy to announce IBM MQ V8. You can read the announcement letters here: Click here for the announcement letter for IBM MQ V8 on distributed platforms. Click here for the announcement letter for IBM MQ for z/OS V8. And click here for the announcement letter for the various IBM MQ V8 offerings on z/OS with a One Time Charge pricing metric.

There are a lot of new capabilities, and plenty of enhancements and improvements included in the announcements. At this point I will just call out a few of the high level items, and leave myself plenty of opportunity to come back on subsequent blogs and dive a little deeper into some of the new and improved areas.

Let’s start with one of the changes that maybe either big or small depending on your perspective. We are starting, with this version, to call this product IBM MQ, as opposed to WebSphere MQ, mirroring a change you may have seen in some other products in recent years. After all MQ connects your entire infrastructure, so referring to it as IBM MQ rather than WebSphere MQ is perhaps more indicative of that breadth of coverage. It does of course continue to work with all the previous releases of WebSphere MQ, and in fact when you order it and install it, you will still see it as WebSphere MQ, but over time, expect changes in the product to reflect the new branding, while continuing to deliver the same robust messaging infrastructure.

So what else is new? Plenty of course has changed for the better, and many of the changes can be grouped as enhancements to boost both security and scalability, improving support for standards, and also doing more to exploit the hardware being used. This changes should reflect an overall improvement in the ease of use of IBM MQ in this release, simplifying configuration and reducing operational tasks.

From a security point of view, some of the key changes include the authentication of userids defined in the operating system, or in LDAP for distributed platforms. More changes include support for multiple certificate authorities in a single queue manager, and the use of DNS Hostnames in Channel Authentication Records.

From a scalability point of view MQ is now better at scaling to the limits of a SMP machine. And there are various other enhancements, especially for publish-subscribe, including a change in the way clustering works for pub-sub. These changes in scalability are particularly designed to improve real-world scalability, rather than being tuned to demonstrate performance in confected examples.

Notable in new standards is support for JMS 2.0 with new messaging features and updates to the API. Also there are enhancements in Microsoft .NET support as well as WCF extensions. And for improved connectivity options, the function that was previously a part of MQ Telemetry Advanced is now a part of MQ Telemetry, giving customers more for less.

For our customers using MQ on z/OS there are some particularly notable enhancements that offer new capabilities and exploit some of hardware updates likely to be available. There is support for 64 bit buffer pools, and a wider log Relative Byte Address as well as support for the zEDC compression and Coupling Facility Flash. Likely to be of real interest is the announcement that we have removed the Client Attachment Feature, meaning that there will no longer be a charge to connect MQ Clients on other platforms to MQ on z/OS. This applies from today, not just on MQ V8 but on WMQ V7.0.1 and V7.1 as well.

As I said, there is quite a lot of new information to share here. I didn’t even get a chance to mention that the MQ AMS code is now integrated into the base on all platforms, and available on IBM i for the first time. Lots more detail to come so please come back for more, and hopefully I will see you at IBM Impact next week in fabulous Las Vegas.



Tags: , , , , , , , , , , ,

8 Responses to “IBM announces IBM MQ V8”

  1. sunny Says:

    Curious to hear what the new “client attachment features” are..

  2. leifdavidsen Says:

    The “client attachment feature” I mentioned was a feature that customers using MQ for z/OS would need to buy in order to be licensed to attach MQ Clients on other platforms directly to MQ for z/OS. Without this feature they would need to connect to MQ for z/OS via another Queue Manager on another platform. Now we have removed the Client Attachment Feature, meaning there is now no charge for connecting MQ clients directly to MQ for z/OS queue managers

  3. sunny Says:

    Ok. Thanks for clarifying !

  4. Daniel J Says:

    The announcement letter request in ‘minimum levels’ Enterprise COBOL for z/OS V5.1
    Does anybody know the reason for that? Is it a typo, is it valid for new features only or a real requirement?
    Anyway: What could be the reason for such a requirement? I don’t see a relationship between the COBOL compiler version and the MQ version. The program runs under LE, even it’s compiled with an older version. And all new stuff such as DLL support is supported with older releases as well.
    So please, can someone enlighten me?

  5. leifdavidsen Says:

    Daniel – happy to confirm that 3.4, 4.2 or 5.1 of COBOL will all work. I will get that updated.

  6. Peter Zpat Says:

    I would like to know more about the FTE changes.

  7. leifdavidsen Says:

    Hi Peter – What about the changes to our Managed File Transfer capabilities would you like to know – are you referring to the earlier blog post: – or looking for details to some of the functional updates we made in V8?

  8. New book underway – MQ V8 | Travels with my MQ Says:

    […] Hursley and started on the next IBM Redbook for MQ. This time it’s about the newly announced MQ V8. After just two days writing, it’s already taking shape with the contents and scenarios […]

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: