System Requirements for WebSphere MQ V6 on Linux for S/390
This document contains system requirements for WebSphere MQ V6 on Linux for S/390.
The System Requirements documented on this page, for the Linux on zSeries platform, are for the 31-bit zSeries operating systems. If you require support information about the 64-bit operating systems please refer to the Linux for System z platform System Requirements.
|Java and JMS Client||
|Databases||Where IBM WebSphere MQ is acting as the transaction manager.
|Transaction Manager||Where one of these products is acting as the transaction manager and IBM WebSphere MQ is acting as a resource manager, it's recommended that you contact the transaction manager vendor in the first instance for support.
|Cryptography Cards||Refer to the Cryptography Card List for WebSphere MQ v6 and v7 document for further information.|
- JDBC/XA usage is not supported on this platform.
- Where higher levels of WebSphere Application Server V6 are suggested, this only includes V6.x levels and does not include other product versions.
- The WebSphere MQ for Linux (zSeries) product only provides 32-bit MQ APIs however it is supported on 64-bit OS's on 64-bit hardware.
- On 64-bit platforms where WebSphere MQ provides both a 32-bit and a 64-bit product, there is NO migration path from V6 32-bit Queue Managers to V6 64-bit Queue Managers. You are strongly advised to install WebSphere MQ 64-bit products on 64-bit platforms as there is a migration path from V5 32-bit products to V6 64-bit products.
- The 'MQ Explorer' is not supported on this platform.
- WebSphere MQ V126.96.36.199 or later is required.
- For details of the Support Statement for JCA (on WebSphere MQ V188.8.131.52 or later only) please see here.
- Defect support is available for virtualisation environments where they relate to releases of this platform already supported by WebSphere MQ, regardless of whether Linux for zSeries is running natively in a LPAR or within a z/VM, or whether IFLs are used. Unless stated elsewhere in the system requirements, WebSphere MQ has not been specifically tested in virtualisation environments. WebSphere MQ Support is therefore unable to assist in issues related to configuration and setup, or issues that are directly related to the virtualisation environment itself.
- On Linux platforms, if you need to use SSL in a C++ MQ application then you must link the application against the libstdc++.so.5 runtime library. This is because the version of the GSkit SSL libraries supplied with MQ depends on libstdc++.so.5 and this GSkit version is not compatible with other C++ runtime library versions. MQ C++ applications built against the GCC 3.2 or 3.3 C++ runtime libraries comply with this restriction and will be able to use SSL.
- WebSphere MQ V184.108.40.206 or later is required.
- SELinux must be disabled.
- WebSphere MQ V220.127.116.11 or later is required.
- WebSphere MQ V18.104.22.168 or later is required.
- WebSphere MQ V22.214.171.124 or later is required.
- Defect support is available for Linux environments that are fully compatible - both source and binary - with Red Hat Enterprise Linux V5. Unless stated otherwise, WebSphere MQ has not been specifically tested in such compatible environments. WebSphere MQ Support is therefore unable to assist in issues related to configuration and setup, or issues that are directly related to the linux environment itself.
If issues arise that are related to the compatible linux environment, the user may need to contact the linux environment vendor for support, or the issue may need to be recreated inside an environment tested by IBM in order to receive WebSphere MQ support.
- 30 September 2005: Added support for Red Hat Enterprise Linux (RHEL) V4.0.
- 26 October 2005: Modifications to the format & minor clarifications.
- 2 May 2006: Added support for IBM SDK V5.0.
- 6 October 2006: Added "SP1 or later" to SLES 9.
- 1 February 2007: Added support for SUSE Linux Enterprise Server (SLES) V10 with Service Pack (SP) 1 or later.
- 7 February 2007: Added "or later" to SUSE Linux Enterprise Server (SLES) V8 with Service Pack (SP) 3.
Added support for IBM DB2 Universal Database V9.1 (JDBC/XA not supported) [see note 5]
- 30 March 2007: Added note 7.
- 10 July 2007: Added Red Hat Enterprise Linux (RHEL) V5.0 or later maintenance update
- 12 July 2007: Made change to databases IBM DB2 and Connectivity TCP/IP.
- 6 March, 2008: Added support for Micro Focus Server Express V5.0 (COBOL).
- 10 March 2008: Added virtualisation note.
- 17 June 2008: Added support for GNU C Compiler (gcc) and g++ V4.1.
- 19 June 2008: Added SSL note 9.
- 10 July 2008: In the Transaction Manager section added the IBM WebSphere Application Server V6.0.2 and V6.1 entries.
- 10 November 2008: Added support for IBM WebSphere Application Server, including the WebSphere Application Server client container, V7.0.
- 11 November 2008: Added support for Red Hat Enterprise Linux (RHEL) V5.1 and V5.2.
- 22 December 2008: Added the Cryptography Cards section.
- 7 April 2009: Added support for IBM 31-bit SDK for Linux on zSeries, Java 2 Technology Edition V6.0 (SR3 or above).
- 9 July 2009; Added support for Red Hat Enterprise Linux (RHEL) V5.3 and SUSE Linux Enterprise Server (SLES) V11.
- 22 October 2009: Added support for Micro Focus Server Express V5.1 (COBOL).
- 14 April 2010: Added support for Red Hat Enterprise Linux (RHEL) V5.4.
- 10 May 2011: Added the Linux Redhat V5.0 compatibility support statement.
- 3 July 2012: Updated expiry date to keep current.
- 3 July 2014: Updated expiry date to keep current.
Original publication date
WebSphere MQ WMQ