IBM Support

System Requirements for WebSphere MQ V6 on Linux for System z

Product Documentation


Abstract

This document contains system requirements for WebSphere MQ V6 on Linux for System z.

Content

The System Requirements documented on this page, for the Linux on zSeries s390x platform, are for the 64-bit zSeries operating systems. If you require support information about the 31-bit operating systems, refer to the Linux for S/390 platform System Requirements.

Operating Systems
  • Red Hat Enterprise Linux (RHEL) V4.0 or later update [see note12]
  • Red Hat Enterprise Linux (RHEL) V5.0 or later update [see notes 7 and 12]
  • SUSE Linux Enterprise Server (SLES) 9 with SP1 or later update
  • SUSE Linux Enterprise Server (SLES) 10 with SP1 or later update [see note 7]
  • SUSE Linux Enterprise Server (SLES) 11 or later update [see note 13]
Hardware Requirements
  • Linux on zSeries s390x platform: IBM zSeries or IBM eServer (or equivalent) 64-bit processor - any hardware that is explicitly compatible and fully capable of running the specified operating system, all the corresponding supporting software shown below, and any associated applications unmodified.
Java and JMS Client
  • 31 bit
    • IBM 31-bit SDK for Linux on zSeries, Java 2 Technology Edition, V1.4.2 (supplied with WebSphere MQ)
    • IBM 31-bit SDK for Linux on zSeries, Java 2 Technology Edition V5.0 (SR1 or above) [Only if the JDK is supplied with another IBM product]
    • IBM 31-bit SDK for Linux on zSeries, Java 2 Technology Edition V6.0 (SR3 or above) [see note 11]
  • 64 bit
    • IBM 64-bit SDK for Linux on zSeries, Java 2 Technology Edition, Version 1.4.2 (supplied with WebSphere MQ)
    • IBM 64-bit SDK for Linux on zSeries, Java 2 Technology Edition V5.0 (SR1 or above) [Only if the JDK is supplied with another IBM product]
    • IBM 64-bit SDK for Linux on zSeries, Java 2 Technology Edition V6.0 (SR3 or above) [see note 11]
Databases
Where IBM WebSphere MQ is acting as the transaction manager.
  • IBM DB2 Universal Database V8.2 [see note 6]
  • IBM DB2 Universal Database V9.1 (JDBC/XA not supported) [see notes 6 and 7]
  • IBM Informix Dynamic Server (IDS) V9.40 plus Client SDK V2.90
  • IBM Informix Dynamic Server (IDS) V10 plus Client SDK V2.90
  • Oracle 10G Release 2
Compilers
  • GNU C Compiler (gcc) and g++ V3.3
  • GNU C Compiler (gcc) and g++ V3.4 [see note 9]
  • GNU C Compiler (gcc) and g++ V4.1 [see note 9]
  • Micro Focus Server Express V4.0 (COBOL)
  • Micro Focus Server Express V5.1 (COBOL) [see note 14]
Connectivity
  • TCP/IP (provided by the operating system)
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.
  • IBM WebSphere Application Server, including the WebSphere Application Server client container, V6.0.2 (see this document for more information) [see note 2]
  • IBM WebSphere Application Server, including the WebSphere Application Server client container, V6.1 (see this document for more information)
  • IBM WebSphere Application Server, including the WebSphere Application Server client container, V7.0 (see this document for more information)
  • BEA Tuxedo V8.1
  • BEA WebLogic Server 8.1 + SP4 on RHEL 3.0 or SLES 9 and IBM JDK 1.4.2 [see note 10]
SOAP Support
  • IBM 64-bit SDK for Linux on zSeries, Java 2 Technology Edition, Version 1.4.2 (supplied with WebSphere MQ)
  • Apache Axis V1.1 (supplied with WebSphere MQ)
Cryptography Cards
Refer to the Cryptography Card List for WebSphere MQ v6 and v7 document for further information.

Notes:

  1. JDBC/XA usage is not supported on this platform.
  2. Only the 31-bit version is supported.
  3. On platforms where WebSphere MQ provides a 64-bit product, both 32-bit and 64-bit MQ APIs are supported and the OS must be capable of running 64-bit applications.
  4. 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. Customers 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.
  5. The 'MQ Explorer' is not supported on this platform.
  6. Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ.
  7. WebSphere MQ V6.0.2.0 or later is required.
  8. 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.
  9. 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
  10. The use of the WebSphere MQ classes for JMS in EJBs and MDBs is fully supported. The WebSphere MQ base classes for Java are supported with restrictions - for more details see, Using WebSphere MQ Java Interfaces in J2EE/JEE Environments.
  11. WebSphere MQ V6.0.2.5 or later is required.
  12. SELinux must be disabled.
  13. WebSphere MQ V6.0.2.6 or later is required.
  14. WebSphere MQ V6.0.2.8 or later is required.


Change History
  • 26 October 2005: Published the page.
  • 2 May 2006: Added support for IBM SDK V5.0.
  • 6 October 2006: Added "SP1 or later" to SLES 9.
  • 15 January 2007: Added support for IBM DB2 Universal Database V9.1 (JDBC/XA not supported).
  • 24 January 2007: Added note 5 "Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ."
  • 1 February 2007: Added support for SUSE Linux Enterprise Server (SLES) 10 with SP1 or later.
  • 19 March 2007: Added support for Oracle 10G Release 2.
  • 11 July 2007: Added Red Hat Enterprise Linux (RHEL) V5.0 or later maintenance update.
  • 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 October 2008: Added BEA WebLogic Server 8.1 + SP4 on RHEL 3.0 or SLES 9 and IBM JDK 1.4.2 [see note 10] and note 10.
  • 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/64-bit SDK for Linux on zSeries, Java 2 Technology Edition V6.0.
  • 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).
  • 5 Sept 2011: Republished the page.

[{"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Documentation","Platform":[{"code":"PF016","label":"Linux"}],"Version":"6.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Product Synonym

WMQ MQ

Document Information

Modified date:
17 June 2018

UID

swg27006794