Last week, a customer emailed an interesting request. They have 2 AIX hub servers running WebSphere MQ V6.0 and they want to determine what applications are using the 2 MQ hub servers, so that they can upgrade to a newer release of MQ. That made me clean my glasses because MQ v6 went out of support in September 2012 (almost 9 years ago).
They asked if either MQ Auditor and/or MQ Channel Connection Inspector (MQCCI) could obtain the IP address of the incoming MQ connection. I said yes, both can get the IP address and if they didn’t want any other information (i.e. queue names, MQ headers, message data, etc) then MQCCI would be the best/easiest solution.
Yesterday, I drove over to my offsite facility to search for backup DVDs of MQ v6. I have 2 boxes of DVD backups, it took about 30 minutes to find 2 backup DVDs with MQ v6 for AIX. I figured at least one of them should be ok.
So, I created a reservation on IBM’s CECC portal for AIX v7.1, uploaded and installed MQ v6 and, of course, I had to install IBM’s XLC compiler because for some strange reason, CECC does not include it for AIX (but they do for Linux on Power and IBM i).
MQCCI was created and launched in May 2018, long, long after MQ v6 went out of support. So, when I tried to do a build, I got several errors about unknown defines (i.e. MQCD_VERSION_9). So, I added a bunch of “#ifdefs” to the code and bam, it compiled and linked successfully.
I created a queue manager and I did a bunch of tests with MQCCI. Everything went smoothly, so I let the customer know that I have a build for them to test out.
At this point in my life, I’m never surprised by the odd requests I get. 🙂
Regards,
Roger Lacroix
Capitalware Inc.
