IBM MQ is a message oriented middleware product that provides a proprietary API as well as implementing the Java Message Service (JMS) API. As of v8.0, the product name became IBM MQ, having being previously called WebSphere MQ and before that, MQSeries. The websphere-mq and mqseries tags are synonyms.
General information
IBM MQ is a message oriented middleware product that provides a proprietary API as well as implementing the Java Message Service (JMS) API.
Tips for asking questions on this topic
The following tips will help the people responding to provide an accurate, timely and effective answer.
Let us know if you are using the MQ client. If you are, then provide information for both the QMgr and the client for most of the remaining points. For example, when giving the version provide it for the QMgr and the client.
And please do provide the version. MQ changes significantly version to version and the interactions between client and server differ by version. Preferably, give us the output of a
dspmqvercommand. If the question pertains to things other than the base code (for example GSKit or JMS classes) then usedspmqver -ainstead.Describe the technology. It makes a difference if you are using the compiled C client or the Java client, .Net, COBOL, etc. Similarly, is it running on mainframe, Windows, UNIX, Linux, or other? Provide these details for the client too, if it is used.
Please provide the MQ Reason Code. If using JMS, you can get the MQ reason code by printing the Linked Exception (a best practice for JMS regardless of transport vendor). Most other commands or API calls return the reason code directly. If there's no reason code, it may not be an MQ problem!
Describe any diagnostic you have already tried, and the results. Any QMgr will have two sets of error logs, possibly issue event messages, and write FDC (dump) files. Were any entries made to these, and if so, what were they?
Getting started?
Links to everything you need to get up and running with IBM MQ:
- IBM MQ Advanced for Developers - full-featured, no-charge, no support development license includes both server and client code, Managed File Transfer, Advanced Message Security and MQ Extended Reach (called MQXR internally, a.k.a. MQTT). Paid support for this version is available as an add-on.
- IBM MQ v9.2 Client - The stand-alone MQ client includes the C, Java, JMS and .Net client functions.
- IBM MQ v9.1 Client - The stand-alone MQ client includes the C, Java, JMS and .Net client functions.
- IBM MQ v9.0 Client - The stand-alone MQ client includes the C, Java, JMS and .Net client functions.
- IBM MQ v8.0 Client - The stand-alone MQ client includes the C, Java, JMS and .Net client functions.
- IBM MQ Explorer - MQ Explorer is now a stand-alone install. It can coexist with but has no dependency on the MQ Client.
- Downloaded the product code? Great! For an overview of how it all works, take a look at the MQ Primer. It is an IBM Redpaper that introduces the concepts of MQ.
- The IBM Messaging Community on developerWorks is IBM's official MQ blog where you can interact with the product developers and management.
- There is a large collection of articles on MQ at IBM MQ on IBM developerWorks.
- IBM Messaging and IBM Support TV on YouTube cover MQ topics.
- The Store and Forward blog covers MQ Security topics in depth.
Product Documentation
IBM MQ v9.2 documentation
IBM MQ v9.1 documentation
IBM MQ v9.0 documentation
IBM MQ v8.0 documentation
IBM MQ v8.0 Appliance documentation
WebSphere MQ v7.5 documentation
WebSphere MQ v7.1 documentation
WebSphere MQ v7.0 documentation
Reference Links
IBM MQ product page
IBM MQ System Requirements
IBM MQ Recommended Fixes - Fix Packs and interim fixes.
IBM MQ SupportPacs - Product extensions.
IBM MQ Request For Enhancement (RFE) Community - Make feature requests here.
IBM MQ Appliance product page - MQ Messaging in an appliance form factor.
IBM Software Support Lifecycle - Find release and end-of-life dates for MQ and other products.
History, packaging and branding
- As of v8.0, released June 2014, the product name became IBM MQ.
- Versions 5.3 - 7.5 were known as WebSphere MQ.
- Versions prior to 5.3 were known as MQSeries.
Service Dates
Product Version Release End of Support
============ ======= ========== =================
IBM MQ 9.2.x 2020-07-23 Not yet announced
IBM MQ 9.1.x 2018-07-23 Not yet announced
IBM MQ 9.0.x 2016-06-02 2021-09-30
IBM MQ 8.0.x 2014-06-13 2020-04-30
WebSphere MQ 7.5.0 2012-07-06 2018-04-30
WebSphere MQ 7.1.0 2011-11-25 2017-04-30
WebSphere MQ 7.0.1 2009-09-25 2015-09-30
WebSphere MQ 7.0.0 2008-06-27 2015-09-30
Websphere MQ 6.0 2005-06-24 2012-09-30
Websphere MQ 5.3 2002-11-29 2007-09-28
MQSeries 5.2 2000-12-15 2003-12-31
MQSeries 5.2.x 2000-12-15 2004-04-30
MQSeries 5.2.1 2001-05-25 2003-12-31
MQSeries 5.2.0 2000-12-15 2003-12-31
MQSeries 5.1.x 2000-04-14 2009-04-30
MQSeries 2.2.1 1995-09-29 2005-04-30
MQSeries 2.1.2 2003-03-14 2010-09-30
MQSeries 2.1.1 2000-09-29 2006-03-31
MQSeries 2.1.0 1998-10-16 2005-09-30
Additional products built on or extending WebSphere MQ
IBM Integration Broker
IBM MQ Extended Reach (MQTT)
IBM MQ Light (AMQP)
WebSphere Message Broker
WebSphere MQ Advanced Message Security (Now integrated into IBM MQ)
WebSphere MQ File Transfer Edition (Now integrated into IBM MQ)
WebSphere MQ Low Latency Messaging
WebSphere MQ Telemetry
Miscellaneous Notes
As of WebSphere MQ v7.5, WebSphere MQ Advanced Message Security was integrated into WebSphere MQ and sold as an entitlement rather than separately delivered code. WebSphere MQ File Transfer Edition was also integrated into the product and renamed as WebSphere MQ Managed File Transfer. WMQ MFT is also sold as an entitlement in the new version. As part of the integration, the documentation for these products was combined with the WebSphere MQ v7.5 documentation.
WebSphere MQ v7.5 was delivered on distributed platforms only. For z/OS the highest version of WebSphere MQ was v7.1 and both WMQ AMS and WMQ FTE products are delivered as separate products in that release.
As of v8.0, IBM MQ Advanced Message Security and Managed File Transfer are available on Distributed and z/OS platforms integrated into the main product and enabled via license entitlement.
