Editing IBM MQ (section)

==History==

===Version release dates===

{| class="wikitable sortable"
|-
! Version name !! Release date 
|-
|IBM MQ 9.4 LTS
|18 June 2024
|-
|-
|IBM MQ 9.3 LTS
|23 June 2022
|-
| IBM MQ 9.2 LTS || 23 July 2020<ref>{{cite web|url=https://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/8/897/ENUS220-238/index.html&request_locale=en|title=IBM announcement of IBM MQ 9.2|date=21 July 2020 |publisher=International Business Machines (IBM)|access-date= 22 October 2020}}</ref>
|-
| IBM MQ 9.1 LTS || 23 July 2018<ref>{{cite web|url=https://www.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/6/897/ENUS218-246/index.html&request_locale=en|title=IBM announcement of IBM MQ 9.1|date=3 July 2018 |publisher=International Business Machines (IBM)|access-date= 6 August 2018}}</ref>
|-
| IBM MQ on IBM Cloud || 13 March 2018 <ref>{{cite web|url=https://www.ibm.com/blogs/bluemix/2018/03/off-mq-ibm-cloud/|title=IBM announcement of IBM MQ on IBM Cloud|publisher=International Business Machines (IBM)|access-date= 6 August 2018}}</ref>
|-
|IBM MQ for HPE Nonstop 8.0
|23 June 2017
|-
| IBM MQ 9.0 LTS|| 2 June 2016 <ref>{{cite web|url=http://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS216-153|title=IBM announcement of IBM MQ 9.0|date=19 April 2016 |publisher=International Business Machines (IBM)|access-date=17 June 2016}}</ref>
|-
| IBM MQ 8.0 || 23 May 2014 
|-
| WebSphere MQ 7.5 || 15 June 2012 
|-
| WebSphere MQ 7.1 || November 2011
|-
| WebSphere MQ 7.0 z/OS || June 2008 
|-
| WebSphere MQ 7.0 (Distributed, iSeries) || May 2008 
|-
| WebSphere MQ 6.0 z/OS || June 2005 
|-
| WebSphere MQ 6.0 (Distributed, iSeries) || May 2005 
|-
| WebSphere MQ 5.3 z/OS || June 2002 
|-
| WebSphere MQ 5.3 (Distributed, iSeries) || June, July, Oct, Nov 2002 
|-
| MQSeries 5.2 (Distributed) || Dec 2000 
|-
| MQSeries for OS/390 V5.2 || Nov 2000 
|-
| MQSeries for AS/400 V5.1 || July-Aug 2000 
|-
| MQSeries for OS/390 V2.1 || Feb 1999 
|-
| MQSeries 5.1 || April (NT), June 1999 
|-
| MQSeries for AS/400 V4.2 || Feb 1998 
|-
| MQSeries 5.0 || October 1997 
|-
| MQSeries for MVS/ESA 1.2 || 29 August 1997 <ref>{{cite web|url=https://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&htmlfid=897/ENUS297-245&language=enus|title=MQSeries for MVS/ESA Version 1.2|date=8 July 1997 |publisher=International Business Machines (IBM)|access-date=10 Dec 2018}}</ref>
|-
| MQSeries for MVS 1.1.4, || June 1996 
|-
| MQSeries 2.2 (Sun OS/Solaris, DC/OSx) || June, July 1996 
|-
| MQSeries 2.0 Windows NT || 2Q 1996 
|-
| MQSeries 2.2 (HP, SCO) || 4Q 1995 
|-
| MQSeries for MVS 1.1.3 || May 1995 
|-
| MQSeries 2.0 (OS/2, AIX) || Feb 1995 (the beginning of the end of ezBridge) 
|-
| MQM/400 V3 || 4Q 1994 
|-
| ezBridge Transact for MQSeries 3.0 || July 1994 
|-
| MQSeries for MVS 1.1.2 || June 1994
|-
| MQM/400 V2.3 || Feb/April 1994 
|-
| ezBridge Transact for MQSeries || March, Sept, Nov, Dec 1993 (different platforms)
|-
| MQSeries for MVS V1.1.1 || December 31, 1993
|}

===Version end of support dates===
The following table applies to MQ software. The MQ Appliance has different lifecycle dates for both firmware and hardware than those in the table.<ref>{{cite web |url=http://www-01.ibm.com/software/support/lifecycle/ |title=IBM Software Support Lifecycle}}</ref>

{| class="wikitable"
|-
! Version name !! General availability !! End of marketing !! End of support
|-
|IBM MQ 9.4
|18 June 2024
| -
| -
|-
|IBM MQ 9.3
|23 June 2022
| -
| -
|-
|IBM MQ 9.2
|23 July 2020
| -
| 30 Sep 2025
|-
| IBM MQ 9.1 || 23-Jul-2018 || 15-Sep-2023 || 30-Sep-2023 
|-
| IBM MQ 9.0 || 02-Jun-2016 || 17-Sep-2021 || 30-Sep-2021
|-
| IBM MQ 8.0 || 13-Jun-2014 || 17-Apr-2020 || 30-Apr-2020
|-
| WebSphere MQ 7.5 || 06-Jul-2012 || 16-Dec-2016 || 30-Apr-2018
|-
| WebSphere MQ 7.1 || 25-Nov-2011 || 12-Jul-2016 || 30-Apr-2017
|}

===Background architectural reference===
With the advent of computers, IBM saw an opportunity to apply new technology to the need for message switching.

In the early 1960s, IBM marketed the IBM 7740 Communication Control System and the IBM 7750 Programmed Transmission Control, which were programmable message switching systems.

The IBM System/360 was announced in April 1964 and with it came communication access methods such as [[BTAM]] and [[QTAM]] (Basic and Queued Telecommunications Access Methods). In 1971, TCAM, the [[Telecommunications Access Method]], offered its users a more advanced form of message switching or message routing. TCAM was widely accepted, especially in the financial and brokerage industries.  It supported asynchronous messaging, as with the later MQ. TCAM 3.0 added in reusable disk message queues for recovery soon thereafter, as with MQ. A high-level PL/I program could be used to access TRANSIENT datasets (dynamic message queues). Reading a message from a transient dataset resulted in that message being removed from the queue, as with a non-browse READ with MQ.

In the late 1970s, transaction management systems came into being, each trying to achieve a leadership position in the industry. Within IBM, [[CICS]] and [[IBM Information Management System|IMS]] were chosen as strategic products to address the need for transaction management. Within both CICS and IMS, each had its version of message switching, IMS being a front-end queued system and CICS having its Transient Data facility as the possible basis for message switching.{{cn|date=June 2021}}

CICS established itself as a popular transaction management system in the 1968-1971 timeframe. Those users who had adopted TCAM for its message handling capabilities now wanted a combined use of TCAM with CICS. In December 1971, IBM announced CICS support of TCAM as part of the CICS/OS-Standard product, to be delivered in December 1972. For interested customers, this enabled them to use TCAM for its message handling strengths and also have TCAM-connected terminals or computers interface with CICS online applications.{{cn|date=June 2021}}

In January 1973, TCAM continued to be supported by CICS/OS-Standard Version 2.3. However, TCAM support was omitted from the initial release of CICS/VS, announced in February 1973 and delivered in June 1974. Needless to say, many CICS-TCAM customers were not happy with that product direction.

With considerable pressure from CICS-TCAM customers, the CICS support of TCAM was reinstated in the CICS/VS 1.1 product, as of September 1974. In addition to the previous DCB support, with this reinstatement of TCAM support, CICS began to support TCAM access via VTAM, also known as the ACB support. CICS TCAM ACB support was discontinued as of the CICS/ESA Version 3 product in 1990.

In 1992, IBM announced a new product called MQSeries. This brand name was later renamed to WebSphere MQ (however its official short name remained MQ) in 2002 to support the WebSphere family name and the product. In 2014, it was renamed IBM MQ. MQ was to be the extension of TCAM functionality from IBM-only systems to all other platforms. MQ has an architecture that enables heterogeneous systems to communicate with each other (e.g. IBM, HP, Sun, Tandem, etc.). MQ can be used with CICS systems to send and receive data to/from any other MQ-eligible system. MQ can be used to initiate work in a CICS system or a CICS transaction can initiate work in another CICS or non-CICS system.

IBM MQ now supports 80 different environments and has become the leading message assured delivery switching/routing product in the industry.<ref>{{cite web |url=http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&supplier=897&letternum=ENUS211-395 |title=IBM WebSphere MQ V7.1 is enhanced with lower cost of ownership, improved time to value, and more configurable security. |work=IBM United States Software Announcement 211-395 |publisher=IBM |date=October 4, 2011}}</ref>