IBM MQ and MQ Appliance News – October 2017

On Tuesday October 24th, IBM Hursley announced the next in the series of Continuous Delivery releases for IBM MQ V9.0 and the MQ Appliance. IBM MQ V9.0.4 was made available on November 6th.

Here are the various announcement letters:-

Links of interest:-


We’ll collect up any other links about the new release as we find them and put them all here.

Advertisements

Application Activity Trace Viewer

IBM MQ has a feature called Application Activity Trace, which allows you to trace what an application is doing, see the progression of MQ API calls, the objects utilised, the options used, the time taken for each call and so on.

To get the most out of this feature, which writes its output as PCF messages, you need to be able to, not only read the content of those PCF messages, but display them in a way that allows you to drill down into the data, exclude data from your view to allow you to focus on what’s important, search for particular objects in use, or particular reason codes, and so on.

To this end, MO71 now has an Application Activity Trace viewer. At it’s simplest, it allows you to see the progression of MQ API calls, just like the IBM-supplied sample amqsact. However it can do so much more than that.

Activity Trace Output

MO71 Activity Trace Output

Drilling down

Rather than having to decide to view every MQ API call in high detail, the viewer allows you to drill down into the verb you are interested in, without the confusion of seeing high detail of everything else at the same time.

Activity Trace Drill down MQINQ

MO71 Activity Trace – Drill down into MQINQ

Activity Trace API Selection

MO71 Activity Trace API Selection

Filter the output

With a trace that spans many pages full, even when only showing one line per verb, you may wish to reduce the clutter on your screen further. You can filter the output in many different ways to see what you’re looking for. For example, you could choose to hide all the MQPUTs and MQGETs and focus on the other calls, like the MQOPENs.

Activity Trace No PUTs and GETs

MO71 Activity Trace with PUTs and GETs excluded

You can filter the output to focus on a particular object or objects that you are interested in, or a particular process id. In fact there are many different factors that you can used to filter down the data to make is easier to view.

Activity Trace Settings

MO71 Activity Trace Settings Tab with filtering

Health-checking your application

There are a number of behaviours that MO71 can check for in your application. These are listed on the Health tab, and if any issues are found you will see them highlighted with a red exclamation mark. You can display the instances in a separate window which then allows you to jump into the main output window at the point where the issue was detected.

Activity Trace Health

MO71 Activity Trace Health Tab

The current list of health issues is not final, and if you have any other issues you would like to see MO71 check for, please comment below or get in touch in the usual ways.

The Application Activity Trace viewer in MO71 will help you make sense of, and get great insight from, your tracing of your applications.


The new version can be downloaded from the MO71 Download Page. Any current licensed users of MO71 can run the new version on their existing licence. If you don’t have a licence and would like to try out MO71 then send an email to support@mqgem.com and a 1-month trial licence will be sent to you.

Migrating a Queue Manager?

If you’re planning to migrate a queue manager, from one machine to another, or perhaps you’re consolidating some queue managers onto an MQ Appliance, you are probably aware of, and have even become familiar with, the steps required to export your object definitions and recreate them on the new queue manager. There are a number of tools available that can do this for you – including those from MQGem.

What about your messages though?

While it’s generally a good idea to reduce the load, and drain off as many messages as you can prior to migrating a queue manager. For example if it’s in a cluster, suspend it from the cluster before the move, to reduce the number of messages heading its way. Let all the applications drain the queues of messages and so on. However, it’s not always possible to drain every last message from all your queues.

QLOAD Offload all queuesIn the latest version of QLOAD, V9.0.1, there’s a new feature that will help out when migrating a queue manager. It allows you to unload the messages from all your queues, with one command. And then you can load the messages onto the queues on another queue manager, with one command (or piecemeal if you prefer). You would combine this with your favoured object definition export tool, and before loading the messages, you’d first recreate the queues on the new queue manager with the exported commands.

Here’s an example of QLOAD unloading all the queues on my queue manager.

qload -m MQG1 -i* -f*

The command will produce the following output to show what has been unloaded. Using the -i (lower case) flag means that the messages are only browsed on the queues and are not destructively removed.

APP1.INPUT                                           2  Done.
APP1.RESULT                                         10  Done.
APP2.INPUT                                           1  Done.
APP2.RESULT                                          4  Done.
Q1                                                  28  Done.
Q2                                                  42  Done.
SYSTEM.ADMIN.QMGR.EVENT                              7  Done.
SYSTEM.AUTH.DATA.QUEUE                             126  Done.
SYSTEM.CHANNEL.SYNCQ                                 3  Done.
SYSTEM.CHLAUTH.DATA.QUEUE                            5  Done.
SYSTEM.CLUSTER.REPOSITORY.QUEUE                      3  Done.
SYSTEM.DURABLE.SUBSCRIBER.QUEUE                      1  Done.
SYSTEM.HIERARCHY.STATE                               2  Done.
SYSTEM.INTER.QMGR.FANREQ                             1  Done.
SYSTEM.RETAINED.PUB.QUEUE                            2  Done.
WORK.REQUEST                                         7  Done.

Total : 7 Queues, 94 Messages
 plus : 9 System Queues, 150 Messages

Listing the directory where I ran the qload command, I can now see I have a file for each queue, with an extension .qld. If you prefer to have a different extension then you can alter the command accordingly. For example, use -f*.txt.

I can copy these files to another machine, or simply use a client connection to the other machine accordingly. Then I can run the following QLOAD command to load the messages onto the new queue manager.

qload -m MQG1 -o* -f*

QLOAD will make some checks when you run a load for multiple queues in this way. It will check that all the queues exist that it has files for in the directory matching the file pattern you specified (which assumes an extension of .qld if you just use ‘*’), and it will check that all those queues are empty. If it finds any problems it will report as follows:-

APP1.RESULT                            RC(2085) Unknown object name.
APP2.RESULT                            Not empty.

There are potential problems with these queues.
Are you sure you want to continue?

This lets you know to go and define the missing queues if you need them – there are messages to go onto them so the assumption is that you do need them. It also warns you of non-empty queues. Now if you’ve already started using this queue manager, you might be expecting this situation, but otherwise, you should rectify it, and then re-run QLOAD.

APP1.INPUT                                       2     Done.
APP1.RESULT                                      10    Done.
APP2.INPUT                                       1     Done.
APP2.RESULT                                      4     Done.
Q1                                               28    Done.
Q2                                               42    Done.
WORK.REQUEST                                     7     Done.

Total : 7 Queues, 94 Messages

You’ll notice that this output does not mention the SYSTEM queues that were offloaded. A generic upload will not upload most SYSTEM queues.
SYSTEM.CLUSTER.TRANSMIT.QUEUE and SYSTEM.DEAD.LETTER.QUEUE are the exceptions. The messages were unloaded to files though, so if you really need to load them you can do so the traditional way, by specifying the full queue name on the command and not using the generic upload.


The new version can be downloaded from the QLOAD Download Page. Any current licensed users of QLOAD can run the new version on their existing licence. If you don’t have a licence and would like to try out QLOAD then send an email to support@mqgem.com and a 1-month trial licence will be sent to you.

IBM MQ and MQ Appliance News – May 2017

On Tuesday May 30th, IBM Hursley made available the next in the series of Continuous Delivery releases for IBM MQ V9.0 and the MQ Appliance. IBM MQ V9.0.3 is now available.

Downloading IBM MQ Version 9.0.3 Continuous Delivery

This was announced on z/OS VUE:-

Links of interest:-


We’ll collect up any other links about the new release as we find them and put them all here.

IBM MQ and MQ Appliance News – March 2017

On Firday March 17th, IBM Hursley made available the next in the series of Continuous Delivery releases for IBM MQ V9.0 and the MQ Appliance. IBM MQ V9.0.2 is now available.

Downloading IBM MQ Version 9.0.2 Continuous Delivery

Unlike V9.0.1 there are no announcement letters.

Read about the changes in this blog post by Leif Davidsen.

Other links of interest:-

Or read this IBM InterConnect 2017 conference presentation from David Ware and Pete Siddall.

Or watch this video.


We’ll collect up any other links about the new release as we find them and put them all here.


The next Continuous Delivery (CD) release is now available. Read more about V9.0.3.

Looking back on 2016

In this post we look back on the year that was 2016 and what happened in both IBM MQ, and MQGem Software.

New Versions

Both IBM MQ and MQGem Software products had a number of new releases in 2016.

MQGem Software products

Three new versions of our premier product, MO71 – a graphical administrative product for IBM MQ. Major version 9.0.0 was released in June to support the IBM MQ V9.0.0 release as well as adding several new features. Then two micro releases, version 9.0.1 was released in August, and version 9.0.2 was released in October.

An update to version 8.0.1 of MQSCX – our extended MQSC product, was released in January, and a series of blog posts described the new features. Then later in the year, major version 9.0.0 was released in July to support the IBM MQ V9.0.0 release as well as adding several major new features, for example, functions.

A new version of QLOAD – our unload/load IBM MQ queues product, QLOAD V8.0.2 was released in January.

Our newest product MQEdit – a live-parsing IBM MQ message editor – was announced in Beta in August, and is free to run until at least January 2017. A new driver was released in November providing a new major feature, user formats.

IBM MQ Fix Packs and new function

The last Fix Pack on IBM WebSphere MQ V7.0.1, Fix Pack 7.0.1.14 was released in August. Two new Fix Packs on IBM WebSphere MQ V7.1. Fix Pack 7.1.0.7 in November, and 7.1.0.6 in January. Two new Fix Packs on IBM WebSphere MQ V7.5. Fix Pack 7.5.0.6 was released in March. Fix Pack 7.5.0.7 was released in September. One new Fix Pack on IBM MQ V8. Fix Pack 8.0.0.5 was released in February.

2016 saw the latest major release of IBM MQ, V9.0.0, announced in April and available in June. At the same time, hardware updates were made to the MQ Appliance. As we were later to discover, V9.0.0 was the starting point for a new delivery model for IBM MQ. In November, V9.0.1, the first continuous delivery (CD) release was made available. You can now choose whether to move forward with new function in regular drops, or stay on the Long Term Service (LTS) release and get new function after a longer period has elapsed. At the same time, the MQ Appliance became a V9 queue manager.

Changes were also made to the MQLight function. Now it is available in IBM Message Hub, with advice to migrate from the MQLight Service to Message Hub if you’re a Bluemix user.

Conference Events

There have been quite a number of events throughout 2016 that have had IBM MQ content delivered at them. A separate post contains all the material that is available on-line from these various events.

Online articles

There have been some really great blog posts written throughout 2016. Lots of the guys in IBM Hursley have been blogging about the new features they have been releasing throughout the year. The IBM MQ Blogosphere has really grown over 2016. Read more in IBM MQ Blogosphere in 2016.

2016 has been a great year for all things MQ. MQGem wishes all its customers, readers, and friends a Happy and Prosperous 2017. HAPPY NEW YEAR!

IBM MQ Blogosphere in 2016

The IBM MQ Blogosphere is the set of blogs that cover content about the IBM MQ product. I wrote about the MQ Blogosphere at the end of 2015. This post is an update showing the new bloggers we’ve gained in 2016, and the existing bloggers that have continued to post great articles for you to read. I hope you’re following all these great blogs to get a feed of interesting an informative MQ blog posts.

No PhotoAlamelu Nagarajan started blogging in 2016. He blogs on the MQDev blog – see his posts. developerWorks Logo
MQDev Logo
Andy OwenAndy Owen dipped a toe into the MQ Blogosphere this year – see his first post on the MQDev blog. developerWorks Logo
MQDev Logo
Ant BeardsmoreAnthony Beardsmore has been blogging for several years, often about Queue Manager Clustering, but now he has turned his attention to blogging about the MQ Appliance. He blogs on the MQDev blog – see his posts. LinkedIn Logo
developerWorks Logo
MQDev Logo
Twitter Logo
Anil SahuAnil Sahu has rekindled his blogged career in 2016 after writing a little back in 2014. He blogs on the MQDev blog – see his posts. developerWorks Logo
MQDev Logo
Twitter Logo
Arthur BarrArthur Barr started blogging about MQ in 2015 and it’s great to see more posts from him in 2016. He blogs on the MQDev blog – see his posts. LinkedIn Logo
developerWorks Logo
MQDev Logo
Chris MatthewsonChris Matthewson snuck in his first blog post on MQDev right at the end of the year. Is this a sign of things to come? developerWorks Logo
MQDev Logo
Chuck MisuracaChuck Misuraca works for an MQ ISV, Perficient, and he occasionally blogs over on the Perficient blog – see his posts. LinkedIn Logo
Colin PaiceColin Paice has his own blog, Colin Paice Blog, where he writes stories about the things he discovers about MQ on z/OS. Colin has been stressing the performance and usability of MQ on z/OS for as long as I can remember, and gets changes made to the product for the benefit of its customers as a result of the things he discovers. He also makes regular appearances on the MQDev blog – see his posts. developerWorks Logo
MQDev Logo
Gwydion TudurA brand new blogger in late 2015, Gwydion Tudur has continued his blogging on MQDev throughout 2016 – see his posts. I am very happy to see him continue to post. LinkedIn Logo
developerWorks Logo
MQDev Logo
No PhotoJames Robertson snuck in his first blog post on MQDev right at the end of the year. Is this a sign of things to come? developerWorks Logo
MQDev Logo
Jamie SquibbA brand new blogger in 2016, Jamie Squibb blogs on MQDev – see his posts. Jamie has worked in the IBM MQ for z/OS area for many years, and I am glad to see he’s now also turning his hand to blogging. I hope to see many more posts from Jamie in 2017! LinkedIn Logo
developerWorks Logo
MQDev Logo
John ColgraveA new member of the IBM MQ Blogosphere in late 2015, John Colgrave has continued blogging throughout 2016 – see his posts. LinkedIn Logo
developerWorks Logo
MQDev Logo
Twitter Logo
Jon RumseyThose of you lucky enough to have met Jon Rumsey will soon realise the breadth and depth of his knowledge of the IBM MQ product is incredible. Most recently he’s majored in security, being extremely knowledgeable about Advanced Message Security and also channel security. He’s also a big fan of the IBM i platform. He’s been blogging for a couple of years now. You can read his posts over on the MQDev blog. LinkedIn Logo
developerWorks Logo
MQDev Logo
Leif DavidsenLeif Davidsen has his own blog, Leifdavidsen’s Blog, where he writes about Messaging, Connectivity and more. It’s a wordpress blog just like this one, and so is very easy to follow, and well worth it! He also comes up with some of the best titles for blog posts! LinkedIn Logo
Twitter Logo
Lyn ElkinsLyn Elkins has her own blog, Lyns Random Thoughts, where she writes about MQ on her favourite platform, z/OS. After going offline last year, Lyn’s now got her domain back up and running with a new blog. LinkedIn Logo
Mark BluemelMark Bluemel is an occasional blogger, writing on subjects he is very knowledgeable about, namely the Java and JMS support in IBM MQ – see his posts on the MQDev blog. developerWorks Logo
MQDev Logo
Mark CampbellMark Campbell snuck in his first blog post on MQDev right at the end of the year. Is this a sign of things to come? developerWorks Logo
MQDev Logo
Mark TaylorMark Taylor started blogging on MQDev in late 2015, and has written a fair few posts this year too. See his posts. You’ll also find lots of MQ videos featuring Mark. LinkedIn Logo
developerWorks Logo
MQDev Logo
Twitter Logo
No PhotoMark Whitlock dipped a toe into the MQ Blogosphere this year – see his first post on the MQDev blog. developerWorks Logo
MQDev Logo
Mark WilsonMark Wilson has been blogging since 2014, and has written on the AIM Support Blog, the IBM Messaging blog and the MQDev blog. Mark started his MQ career on the z/OS platform, but has been expanding his knowledge to cover the distributed platforms too. LinkedIn Logo
developerWorks Logo
MQDev Logo
Mark WomackMark Womack has been blogging over on the AIM Support Blog for a number of years, always with a perspective to help MQ customers, his ‘tracking technical trends’ posts are always interesting – see his posts. LinkedIn Logo
developerWorks Logo
Matt LemingMatt Leming has been blogging about MQ since 2014. He writes about the MQ on z/OS product over on the MQDev blog – see his posts. LinkedIn Logo
developerWorks Logo
MQDev Logo
Matt WhiteheadMatt Whitehead has been blogging for a year or two now. He writes about MQLight and Bluemix, over on the MQDev blog – see his posts. LinkedIn Logo
developerWorks Logo
MQDev Logo
Twitter Logo
Mayur RajaMayur Raja has worked on IBM MQ for z/OS for many years and is a very experienced z/OS developer. He has started blogging about MQ this year. He blogs on the MQDev blog – see his posts. developerWorks Logo
MQDev Logo
Twitter Logo
Miguel RodriguezMiguel Rodriguez works in IBM in the L2 Service team for IBM MQ, and he blogs over on the AIM Support Blog – see his posts. developerWorks Logo
Morag HughsonMorag started her blogging career in IBM. After leaving IBM she joined MQGem Software, an MQ ISV that produces tools to assist with your MQ system, and she now blogs on the MQGem Software blog, and also over on the IBM MiddleWare User Community. You’ll also see her regularly answering questions on StackOverflow. LinkedIn Logo
developerWorks Logo
Twitter Logo
Nathan WilsonNathan Wilson works for an MQ ISV, W3Partnership, and he occasionally blogs over on the W3Partnership blog – see his posts. LinkedIn Logo
Twitter Logo
Paul TitheridgePaul Titheridge started blogging at the start of 2016, although he’s been a successful IBM MQ writer through many IBM Technotes in the past. He writes up problems seen in his day job in Level 3 service that are useful for all users to see. It’s a great way to get the word out about common problems. He blogs on the MQDev blog – see his posts. Paul can also be found on the IBM MQ Service YouTube channel. LinkedIn Logo
developerWorks Logo
MQDev Logo
Pete SiddallAnyone who’s met Pete Siddall, the STSM for MQ on z/OS, knows how passionate he is about the platform and the MQ product that runs on it. Pete helps MQ on z/OS customers in a million different ways, and still has found time to write the occasional blog post over on MQDev – see his posts. LinkedIn Logo
developerWorks Logo
MQDev Logo
Twitter Logo
Richard PilotHaving started his blogging career in 2015, Richard Pilot continued with a few posts this year too – see his posts. Looking forward to more in 2017! LinkedIn Logo
developerWorks Logo
MQDev Logo
Twitter Logo
Rob ParkerRob Parker has been blogging for a year or two now. You can read his posts over on the MQDev blog. LinkedIn Logo
developerWorks Logo
MQDev Logo
Twitter Logo
Roger LacroixRoger Lacroix has his own blog, Roger’s Blog on MQ, Java, C, etc…, where he writes about MQ as well as a variety of other subjects. Roger works for Capitalware, an MQ ISV that produces exits and tools for your MQ system, and runs the annual MQTC Conference. LinkedIn Logo
Sajina Puthalath KandySajina Puhtalath Kandy started blogging in 2016. She blogs on the MQDev blog – see her posts. LinkedIn Logo
developerWorks Logo
MQDev Logo
No PhotoSam Goulden started blogging about the MQ Appliance this year. He blogs on the MQDev blog – see his posts. developerWorks Logo
MQDev Logo
Twitter Logo
Sam MasseySam Massey works in the performance team for Distributed MQ, and has entered the MQ Blogosphere this year with a few performance related posts – see his posts on the MQDev blog. LinkedIn Logo
developerWorks Logo
MQDev Logo
ShashiShashikanth Thambrahalli has been blogging for as long as I can remember. I think he might have been one of the founding members of the MQDev blog! Shashi is passionate about the service of our product, and the go to man for .NET and XMS too. This years he’s also been blogging about MFT. See his posts on the MQDev blog. You’ll also see him regularly answering questions on StackOverflow. LinkedIn Logo
developerWorks Logo
MQDev Logo
No PhotoSimon Davitt started his blogging career in 2016 with a couple of posts on MQDev. Hope to see more in 2017. developerWorks Logo
MQDev Logo
No PhotoSridhar Ravindra started blogging in 2016. He blogs on the MQDev blog – see his posts. developerWorks Logo
MQDev Logo
Thomas LeendTom started blogging at the start of 2016, writing up problems seen in his day job in Level 3 service, that are useful for all users to see. It’s a great way to get the word out about common problems. He blogs on the MQDev blog – see his posts. Tom can also be found on the IBM MQ Service YouTube channel. LinkedIn Logo
developerWorks Logo
MQDev Logo
T.RobT.Rob Wyatt has his own blog, Store and Forward – A blog about securing and using WebSphere MQ, where he writes about MQ, and then he also writes over on the IBM MiddleWare User Community. T.Rob has looked at MQ from every angle, he’s been a customer, an IBMer and now, a consultant offering his incredible knowledge about MQ, to get your MQ system running smoothly. You’ll also see him regularly answering questions on StackOverflow. LinkedIn Logo
developerWorks Logo
Twitter Logo
Tony SharkeyTony Sharkey is an IBM MQ for z/OS Performance expert. If you’ve got any interest in MQ on z/OS, you’ve probably read at lot of Tony’s writing over the years as he’s contributed hugely to the Performance Reports you get for every release. Now he’s blogging as well. He blogs on the MQDev blog – see his posts. developerWorks Logo
MQDev Logo
Twitter Logo

It is so great to see so many IBM MQ experts taking the time to write blog posts for you all to read. If you don’t follow one or more of these blogs, you should. Clicking on the “Follow” button is easy! I look forward to reading many more blog posts in 2017, and sharing them in our Monthly Newsletter. Thanks to all our MQ bloggers!


Footnote: If you’ve blogged about IBM MQ in 2016 and you’re not in the above list, let me know in the comments and I’ll add you to the list, and your blog to our IBM MQ Resources Page if it’s not already there.