Abstract -------- This document contains the readme for WebSphere MQ Version 7.0.1 and its maintenance. The English language version of this document is the most up to date version. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ DESCRIPTION ----------- This file describes the following: 1. Limitations and known problems 2. How to obtain and install this fix pack 3. IBM Message Service Client for .NET V2.0.0.13 4. Notices and trademarks The latest version of this file can be found here: https://ibm.biz/mqreadmes The latest version of the product license file can be found here: http://www.ibm.com/support/docview.wss?uid=swg27006097 In addition to this file, you can find more information on the IBM MQ web site: http://www.ibm.com/software/integration/wmq/ The SupportPac web page is here: https://ibm.biz/mqsupportpacs For current information about known problems and available fixes, see the Support page of the IBM MQ web site: http://www.ibm.com/software/integration/wmq/support/ Web documentation updates The latest updates to the web-based IBM MQ documentation are available from the IBM MQ web site: http://www.ibm.com/software/integration/wmq/library/ Announcement letter The announcement letter for WebSphere MQ Version 7.0 (US English) is available here: http://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&appname=GPA&htmlfid=897/ENUS208-068 (for distributed platforms), or http://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&appname=GPA&htmlfid=897/ENUS208-067 (WebSphere MQ for z/OS ). See the announcement letter for the following types of information: - Detailed product description, including description of new function - Product-positioning statement - Ordering details - Hardware and software requirements +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ UPDATE HISTORY 05 Aug 2016 - Updates for WebSphere MQ Version 7.0.1, Fix Pack 14 12 Feb 2016 - Updates for deprecated SSLv3 CipherSpecs in Fix Pack 13 01 Jul 2015 - Refactor by fix pack, and updates for Fix Pack 13 14 Mar 2014 - Updates for WebSphere MQ Version 7.0.1, Fix Pack 12 20 Aug 2013 - Updates for WebSphere MQ Version 7.0.1, Fix Pack 11 17 Dec 2012 - Updates for WebSphere MQ Version 7.0.1, Fix Pack 10 06 Jul 2012 - Updates for WebSphere MQ Version 7.0.1, Fix Pack 9 13 Jan 2012 - Updates for WebSphere MQ Version 7.0.1, Fix Pack 8 03 Oct 2011 - Updates for WebSphere MQ Version 7.0.1, Fix Pack 7 03 Jun 2011 - Updates for WebSphere MQ Version 7.0.1, Fix Pack 6 03 Feb 2011 - Updates for WebSphere MQ Version 7.0.1, Fix Pack 5 01 Oct 2010 - Updates for WebSphere MQ Version 7.0.1, Fix Pack 4 12 Aug 2010 - Updates for WebSphere MQ Version 7.0.1, Fix Pack 3 28 Jan 2010 - Updates for WebSphere MQ Version 7.0.1, Fix Pack 2 20 Nov 2009 - Updates for WebSphere MQ Version 7.0.1, Fix Pack 1 16 Jul 2009 - Updates for WebSphere MQ Version 7.0.1 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++ ++ ++ SECTION 1: LIMITATIONS AND KNOWN PROBLEMS ++ ++ ++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ LIMITATIONS AND KNOWN PROBLEMS FOR VERSION 7.0.1, FIX PACK 14 ============================================================= Withdrawal of migmbbrk migration utility ---------------------------------------- The migmbbrk utility has been previously supplied with all WebSphere MQ Version 7 releases, and was used to migrate publish/subscribe configuration data from WebSphere Event Broker Version 6.0 or WebSphere Message Broker Version 6.0 or 6.1 to WebSphere MQ Version 7. To facilitate its operation, additional software components were supplied with the product. Given the withdrawal of support for the applicable WebSphere Event Broker and WebSphere Message Broker releases, the migmbbrk utility and its dependencies are no longer supplied as part of the MQ product installation. For compatibility, identically named placeholder files are shipped instead to preserve the installation layout on disk. A standalone edition of the migmbbrk utility is to be made available on the IBM support site. LIMITATIONS AND KNOWN PROBLEMS FOR VERSION 7.0.1, FIX PACK 13 ============================================================= Deprecation of support for weaker CipherSpecs --------------------------------------------- WebSphere MQ Version 7.0.1, Fix Pack 13 deprecates the SSLv3 protocol and the use of the following CipherSpecs on channel definitions associated with the queue manager: AES_SHA_US (SSLV3 only) RC4_SHA_US RC4_MD5_US TRIPLE_DES_SHA_US DES_SHA_EXPORT1024 RC4_56_SHA_EXPORT1024 RC4_MD5_EXPORT RC2_MD5_EXPORT DES_SHA_EXPORT TLS_RSA_WITH_DES_CBC_SHA (not SSLV3) NULL_SHA NULL_MD5 FIPS_WITH_DES_CBC_SHA FIPS_WITH_3DES_EDE_CBC_SHA TLS_RSA_WITH_NULL_SHA256 (not SSLV3) Attempting to use or configure one of these CipherSpecs results in one or more of the following messages in the queue manager error log: AMQ8242, AMQ9616, AMQ9635. To continue using any SSLv3 CipherSpecs in the previous list (that is, any CipherSpec except the two that are flagged as "not SSLV3"), set the environment variable AMQ_SSL_V3_ENABLE to the value "TRUE" in the environment used to start the queue manager. Alternatively, add the following entry to the SSL stanza of the queue manager's qm.ini file: AllowSSLV3=Y Setting the environment variable overrides any value specified in the qm.ini file. To continue using any CipherSpecs in the previous list except the one that is flagged as "SSLV3 only", set or export to "Yes" the environment variable AMQ_SSL_WEAK_CIPHER_ENABLE in the environment used to start the queue manager. Alternatively, add the following entry to the SSL stanza of the queue manager's qm.ini file: AllowWeakCipherSpec=Yes Setting the environment variable overrides any value specified in the qm.ini file. LIMITATIONS AND KNOWN PROBLEMS FOR VERSION 7.0.1, FIX PACK 12 ============================================================= This fix pack contains no new limitations or problems that require your attention. LIMITATIONS AND KNOWN PROBLEMS FOR VERSION 7.0.1, FIX PACK 11 ============================================================= The Introduction section of the EGA.readme.mbr file shipped with WebSphere MQ 7.0.1 iSeries base code contains an outdated reference to the Quick Beginnings book being available from the download site -------------------------------------------------------------------------- "Introduction These instructions apply to installing WebSphere MQ for i5/OS Version 7.0.1 from an installation image downloaded from IBM. Use it with the WebSphere MQ for i5/OS Quick Beginnings manual for this release. A version of the Quick Beginnings book is available from the download site, it has a description of 'WebSphere MQ V7.0 Install Doc'." This document is no longer available on the Passport Advantage site. The information is now available online in the WebSphere MQ version 7 Information Center in the 'Quick Beginnings for i5/OS' section: http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.amqwac.doc/iq10120_.htm LIMITATIONS AND KNOWN PROBLEMS FOR VERSION 7.0.1, FIX PACK 10 ============================================================= WebSphere MQ Explorer - English messages in non-English environment ------------------------------------------------------------------- When Fix Pack 10 is installed in a non-English environment, some messages in WebSphere MQ Explorer might still appear in English and might not display the latest translation. This is caused by Eclipse Bug 201489: https://bugs.eclipse.org/bugs/show_bug.cgi?id=201489 To install the Eclipse fix for this issue, first run WebSphere MQ Explorer in Eclipse Workbench mode. To select Eclipse Workbench mode, click Window > Preferences > WebSphere MQ Explorer > in an Eclipse Workbench. Restart WebSphere MQ Explorer for this to take effect. On Linux platforms, in order to be able to view and install updates, run WebSphere MQ Explorer as root. Launch the update manager by clicking Help > Software Updates Select "RCP Patch (bug:201489)" from the available updates and follow the instructions to install the fix. To return WebSphere MQ Explorer to stand-alone mode if required, select the appropriate option from the WebSphere MQ Explorer preferences page. WebSphere Application Server support on z/OS -------------------------------------------- Before you deploy Fix Pack 10 on or within a WebSphere Application Server environment on z/OS, read the technotes below that are relevant to the versions of WebSphere Application Server you are using: Version Link -------- ------------------------------------------------------------- 7.0 http://www.ibm.com/support/knowledgecenter/prodconn_1.0.0/com.ibm.scenarios.wmqwasusing.doc/topics/swg21316899.htm 8.0 http://www.ibm.com/support/knowledgecenter/prodconn_1.0.0/com.ibm.scenarios.wmqwasusing.doc/topics/swg21498708.htm 8.5 http://www.ibm.com/support/knowledgecenter/prodconn_1.0.0/com.ibm.scenarios.wmqwasusing.doc/topics/swg21498708_85.htm APAR IV31952 ------------ The fix for APAR IV31952 changed the authority checks that WebSphere MQ makes on channel objects when you run the RESET CHANNEL command. Applying this fix can give changed behavior and you might need to alter some authorities. Your systems are affected only if your channels run with an MCAUSER userID resolving to a non-mqm user. The Reset Channel command can run internally within WebSphere MQ code, so, even though you have not run the Reset Channel command manually, your system might still be affected. Ensure that, at a minimum, your channel's MCAUSER userID has both +DSP and +CTRLX authority on the channel object, so that the userID can run Reset Channel commands. Before the fix for IV31952, WebSphere MQ checked that the userID had +ALTUSR authority which you might previously have granted to make your channel work. After applying fix pack WebSphere MQ fix pack 7.0.1.10 or later, you can remove your MCAUSER's +ALTUSR authority on the channel object because it is not required for the Reset Channel command. You should also check that your MCAUSER userID has +DSP and +CTRLX authority on the channel object. LIMITATIONS AND KNOWN PROBLEMS FOR VERSION 7.0.1, FIX PACKS 8 AND 9 =================================================================== These fix packs contain no new limitations or problems that require your attention. LIMITATIONS AND KNOWN PROBLEMS FOR VERSION 7.0.1, FIX PACK 7 ============================================================ Installing a V7.0.1 fix pack on HP-UX when a V7.1 installation exists --------------------------------------------------------------------- On HP-UX, when an attempt is made to upgrade 7.0.1 Fix Pack 6 to 7.0.1 Fix Pack 7 on a machine that also has a WeSphere MQ V7.1 installation, the fix pack installation log might contain the following errors repeated a number of times. However, this does not prevent the fix pack from installing successfully. rm: MQSERIES.MQM-RUNTIME: non-existent ERROR: You have specified more than one fileset selection. You must specify only a single fileset when performing file or control file modifications. Removing a V7.0.1 fix pack from Linux while a V7.1 queue manager is running --------------------------------------------------------------------------- On Linux (all architectures), when you try to remove a V7.0.1 fix pack, the removal might partially fail if both of the following conditions are true: - removing the V701 fix pack leaves the installed version of V7.0.1 at an earlier version than Fix Pack 6 - there is a v7.1 queue manager running on the system at the time. The error messages output from the 'rpm' command have the following form: ERROR: WebSphere MQ shared resources for this installation are still in use. Please ensure no WebSphere MQ processes are running before removing this maintenance package error: %preun(MQSeriesJRE-U844092-7.0.1-7.s390x) scriptlet failed, exit status 1 For example, on a system where the following installation order has been used: (1) Install a fresh installation of WebSphere MQ V7.0.1, Fix Pack 3. (2) Install WebSphere MQ V7.0.1, Fix Pack 7. (3) Install WebSphere MQ V7.1.0.0. (4) Create and start a V7.1 queue manager (5) Uninstall the WebSphere MQ V7.0.1.7 fix pack To avoid this issue, take one of the following actions: (a) Ensure that all queue managers on the system are in the stopped state before removing the fix pack. (b) Ensure that the 'MQSeriesRuntime' rpm package is the last package to be removed from the fix pack uninstallation. The rpm syntax varies by rpm version - you might need to consult your Operating System vendor in order to determine this information for your system. For Red Hat Enterprise Linux Server 5.7, which uses rpm version 4.4.2.3, the removal order is the reverse of that specified on the command line. Therefore specifying the 'MQSeriesRuntime' first in the removal list will allow the fix pack to be removed. For example, on Red Hat Enterprise Linux Server 5.7, use the following command syntax to successfully remove an instance of V7.0.1, Fix Pack 7 while a V7.1.0.0 queue manager is running: rpm -e MQSeriesRuntime-U844091-7.0.1-7 MQSeriesConfig-U844091-7.0.1-7 MQSeriesMsg_es-U844091-7.0.1-7 MQSeriesMsg_ru-U844091-7.0.1-7 MQSeriesMan-U844091-7.0.1-7 MQSeriesMsg_ko-U844091-7.0.1-7 MQSeriesServer-U844091-7.0.1-7 MQSeriesJava-U844091-7.0.1- MQSeriesMsg_cs-U844091-7.0.1-7 MQSeriesMsg_hu-U844091-7.0.1-7 MQSeriesMsg_pl-U844091-7.0.1-7 MQSeriesMsg_Zh_TW-U844091-7.0.1-7 MQSeriesTXClient-U844091-7.0.1-7 MQSeriesClient-U844091-7.0.1-7 MQSeriesJRE-U844091-7.0.1-7 MQSeriesMsg_de-U844091-7.0.1-7 MQSeriesMsg_it-U844091-7.0.1-7 MQSeriesMsg_pt-U844091-7.0.1-7 MQSeriesSamples-U844091-7.0.1-7 MQSeriesKeyMan-U844091-7.0.1-7 MQSeriesMsg_ja-U844091-7.0.1-7 MQSeriesSDK-U844091-7.0.1-7 MQSeriesFTA-U844091-7.0.1-7 MQSeriesMsg_fr-U844091-7.0.1-7 MQSeriesMsg_Zh_CN-U844091-7.0.1-7 If you do encounter this issue, complete removal of the V7.0.1 fix pack by completing the following steps: 1. Stop all WebSphere MQ queue managers on the system. 2. Remove the remaining rpm packages associated with the fix pack that were not removed with the first removal attempt. Changes to DEFXMITQ attribute of the queue manager object --------------------------------------------------------- Additional checks have been introduced in Fix Pack 7 to disallow setting the value "SYSTEM.CLUSTER.TRANSMIT.QUEUE" for the DEFXMITQ attribute for the queue manager object.A new reason code "MQRCCF_DEF_XMIT_Q_CLUS_ERROR" (number 3269) has been created to describe a failed attempt to set the DEFXMITQ attribute of the queue manager object to "SYSTEM.CLUSTER.TRANSMIT.QUEUE". Additionally, to prevent problems if DEFXMITQ has previously been incorrectly set to SYSTEM.CLUSTER.TRANSMIT.QUEUE, a new validity check has been added to prevent an MQOPEN or MQPUT1 call from using this incorrect mechanism. The reason code on failure is "MQRC_DEF_XMIT_Q_USAGE_ERROR" (number 2199). LIMITATIONS AND KNOWN PROBLEMS FOR VERSION 7.0.1, FIX PACK 6 ============================================================ Changes to the default behaviour of MQPUT1 API with MQPMO_SYNCPOINT when used in a client application ------------------------------------------------------------------- The default behaviour of MQPUT1 with MQPMO_SYNCPOINT has been changed in Fix Pack 6, to put the message synchronously so that MQMD and MQOD output fields are populated during the MQPUT1 call. The default behaviour can be changed by setting the client configuration file attribute Put1AsyncPut in the Channels stanza. Valid values for Put1AsyncPut are: (a) no : Put is always synchronous. This is the default. (b) yes : Put is always asynchronous. (c) syncpoint : Put is asynchronous if MQPMO_SYNCPOINT is set and synchronous otherwise. The new attribute Put1AsyncPut does not replace Put1DefaultAlwaysSync. If there is a need to change the default back to the pre-Fix Pack 6 default, the client configuration file attribute Put1AsyncPut must be set to "syncpoint". LIMITATIONS AND KNOWN PROBLEMS FOR VERSION 7.0.1, FIX PACK 5 ============================================================ Improved handling of WebSphere MQ running on HP-UX 11i V3 (Itanium hardware) ---------------------------------------------------------------------------- This item affects only users on HP-UX 11i V3 (Itanium hardware) where the system hostname is longer than 8 characters. Before Fix Pack 5, WebSphere MQ obtained the hostname by calling a system call, uname(). On HP-UX 11i V3 (Itanium hardware), the uname() call can fail if the hostname is greater than 8 characters. During the install processing and also during normal queue manager processing, the failed uname() call could then cause the WebSphere MQ code to fail to operate correctly. Directories under /var/mqm that contain the hostname can then incorrectly be created with the name "Unknown" instead of the hostname. APAR IZ87770 addresses the problem by using the gethostname() system call instead. After installing Fix Pack 5 or higher fix packs, please manually remove the directories incorrectly named "Unknown". Specifically the directories named "Unknown" will be under these locations: - /var/mqm/ipc - /var/mqm/sockets - /var/mqm/qmgrs//@app - /var/mqm/qmgrs//@qmgr Do NOT delete any other directories, for example those that hold message data under /var/mqm/qmgrs//queues. More information about this APAR can be found here: http://www.ibm.com/support/docview.wss?uid=swg1IZ87770 Improvement to the way in which trigger monitor sends information to the triggered application ----------------------------------------------------------------- APAR IC72003 improves the way in which the trigger monitor sends information to the triggered application. Percent and dollar characters are now escaped by double quotes (Windows) or a backslash (UNIX). This change causes the expansion of environment variables by the operating system to be suppressed for the data inside the MQTMC2 structure that is passed as a parameter to the triggered application. For example, if the APPLICID field of a process was defined to be "java cp %CLASSPATH% TriggerApp", then on Windows this will be changed to "java cp "%"CLASSPATH"%" TriggerApp" when constructing the MQTMC2. In this example, the application will receive "java cp %CLASSPATH% TriggerApp" as an input parameter. From Fix Pack 5, applications no longer receive an expanded version of environment variables inside the MQTMC2 structure. Instead they must use alternative means of expanding the environment variables if their content is important. Changes to the usage of MQGMO_CONVERT in WebSphere MQ v7.0 classes for JMS -------------------------------------------------------------------------- APAR IC72897 changes the way in which WebSphere MQ V7.0 classes for JMS request messages from the queue manager. Prior to Fix Pack 5, the WebSphere MQ V7.0 classes for JMS requested messages from the queue manager using the WebSphere MQ API option MQGMO_CONVERT. This option requests that the queue manager performs message data conversion before sending the message to the receiving JMS application. The WebSphere MQ V6.0 classes for JMS did not use this option. This change of JMS client behaviour can affect JMS applications when migrating from V6.0 to V7.0. The code change associated with this APAR reverts the default action of the V7.0 classes to the V6.0 behaviour. When Fix Pack 5 or higher is installed, WebSphere MQ V7.0 classes for JMS applications no longer use MQGMO_CONVERT. Therefore the queue manager performs no message data conversion when messages are requested. New properties have also been added as part of this APAR, to allow the application to choose whether queue manager data conversion is requested or not. These properties can be configured programmatically using the setter method on the com.ibm.mq.jms.MQDestination class, administratively using a property set in the JNDI namespace for the destination, or as a system wide environment variable within the JVM using the property "com.ibm.msg.client.wmq.receiveConversionCCSID". A full description of this APAR, including how to use the new properties, and the settings to use to retain the behaviour of the V7.0 classes prior to this fix pack, is available at: http://www.ibm.com/support/docview.wss?uid=swg21459994 LIMITATIONS AND KNOWN PROBLEMS FOR VERSION 7.0.1, FIX PACK 4 ============================================================ Behavior of the UNCOM output field for DISPLAY QSTATUS ------------------------------------------------------ APAR IZ76189 has changed the behaviour of the DISPLAY QSTATUS command in runmqsc so that the behaviour of UNCOM now matches the description under the runmqsc Information Center pages. The runmqsc interface will now display the number of uncommitted messages rather than simply YES or NO. You can now use UNCOM in a filter: for example, WHERE(UNCOM LT 10). It may be necessary to modify your scripts that contain DISPLAY QSTATUS commands to runmqsc, if they rely on this value being YES or NO. Improvement to dead-letter handling within the WebSphere MQ v7 classes for JMS ------------------------------------------------------------------------------ APAR IZ78515 has changed the default behavior for dead-letter handling within the WebSphere MQ V7 classes for JMS. When using the WebSphere MQ V7 classes for Java Message Service (JMS) before Fix Pack 4, poison messages that cannot be sent to the named backout queue were converted to type JMSBytesMessage before being sent to the queue manager's dead-letter queue (for example, SYSTEM.DEAD.LETTER.QUEUE). This had been a change in behavior from WebSphere MQ V6. In V6, the JMS classes put the messages to the dead-letter-queue in their original format, without converting them to type JMSBytesMessage. APAR IZ78515 changes the behavior so that poison messages are now put to the dead-letter queue without doing any conversion. This is the correct behavior for this function, and matches WebSphere MQ v6. New information in WebSphere MQ Explorer : some non-English text missing. ------------------------------------------------------------------- Some of the newest text (added in Fix Pack 4) is missing from non-English versions of the WebSphere MQ Explorer. (a) The MQ Explorer authorization functionality now contains a new panel which allows you to "Add Role Based Authorities". There are two "More Information" links on this screen. At Fix Pack 4, the lower of the two links doesn't give any information unless you are running the MQ Explorer in English. (b) A number of items of recently introduced SSL/TLS functionality have been added into the MQ Explorer at Fix Pack 4. These items relate to channel and queue manager configuration. Specifically, they allow: - Configuration of SHA-2 CipherSpecs from the MQ Explorer. - Specification of an HTTP Proxy Server for OCSP use. - Configurable change to the way certificates are validated which is useful to a small number of users. When running the MQ Explorer in English the information in these panels has been updated to reflect the new SSL/TLS values; in other languages some of this new information is not displayed, though the main panels themselves are properly translated. LIMITATIONS AND KNOWN PROBLEMS FOR VERSION 7.0.1, FIX PACK 3 ============================================================ Fix Pack 3 and later clients using JMS to connect to Fix Pack 2 servers ----------------------------------------------------------------------- If upgrading to Fix Pack 3 or higher on an installation where WebSphere MQ classes for Java Message Service (JMS) are in use, please read the following information. From Fix Pack 3 onwards, When using the WebSphere MQ classes for Java Message Service (JMS) to connect to a Fix Pack 2 queue manager, there can be a problem when stopping the SVRCONN channel instance. For example, you type: STOP CHANNEL(MY.SVRCONN.CHANNEL) Stopping a channel being used by the Java application can result in the channel status remaining in a STOPPING state. When the channel is restarted, the channel status moves to STARTED and another channel instance is created. This issue has been resolved by APAR IZ77323, fixed in Fix Pack 3. Therefore you should upgrade the server installation of WebSphere MQ to Fix Pack 3 or higher before the clients that connect to it, if your clients are using JMS. Additional error cases now found by Explorer security tests ----------------------------------------------------------- After you install Fix Pack 3 or higher, if you run the Explorer Default Tests you will probably get error messages in the Test Results, even if your results were error-free previously. This is because the Default Tests now test aspects of your configuration that were not previously tested. The most common errors arise because your inbound system and default channels (ones with names starting with "SYSTEM") have not been adequately protected against unwanted access. Another common cause of new errors is that your SSL/TLS system files allow unnecessarily high levels of access. You can reconfigure your system to remove error Test Results, and, where appropriate, warning Test Results. Advice on how to do this is given in the "Further Information" associated with the Test Result. You may wish to use the same SSL/TLS system files to hold both client and queue manager keys and certificates. However, this is an insecure configuration and is discouraged. In general the access control/permission required for such a configuration is incompatible with the new SSL/TLS system file test. If you persist with sharing SSL/TLS system files between the client and queue manager, but want error-free Explorer Test Results, you can configure your own set of standard tests using the Explorer "Run Custom Test Configuration..." facility. LIMITATIONS AND KNOWN PROBLEMS FOR VERSION 7.0.1, FIX PACKS 1 AND 2 =================================================================== These fix packs contain no new limitations or problems that require your attention. LIMITATIONS AND KNOWN PROBLEMS FOR VERSION 7.0.1.0 ================================================== 64-bit GSKit 7 not updated with MQ fix pack install on Windows -------------------------------------------------------------- Due to a known limitation in the install code, the 64-bit version of GSKit 7 on Windows is not upgraded when WebSphere MQ fix packs are installed. This means that 64-bit MQ client applications using SSL/TLS connections on Windows are not running at the latest GSKit fix level. However, the 32-bit GSKit 7 installation is upgraded when the fix pack is installed. This means that queue managers, server-side channels and 32-bit SSL/TLS client applications are still able to use the newer GSKit fix levels when WebSphere MQ maintenance is applied. Java and JMS clients do not use GSKit for their SSL/TLS functionality, and are therefore unaffected by this issue. Information relating to maintaining multi-instance queue managers ----------------------------------------------------------------- Guidance can be found here for applying fix packs where multi-instance queue managers are in use: http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.amqaac.doc/cr00060_.htm In general, a multi-instance queue manager can have instances running at a mixture of 7.0.x.y and 7.0.a.b. Exceptions to this are listed below. Other than these exceptions, it is the general rule that the standby instance can be on an installation at a newer or older fix pack level than the active instance. This enables upgrading or rolling back of maintenance with the minimum of down time. The following is the list of exceptions: Windows: 7.0.1.0 and >= 7.0.1.0 cannot be used in combination. i5/OS: 7.0.1.0 does not support multi-instance queue managers so cannot be used for the standby or active instance. Launching Explorer with a previous installation of WebSphere MQ Version 7.0.1 ----------------------------------------------------------------------------- If you have a previous installation of WebSphere MQ Version 7.0.1, for example a Beta version, you might experience a problem when you launch the WebSphere MQ Explorer. If you find that Eclipse starts but the WebSphere MQ perspective does not open properly, perform the following actions: 1. In the Explorer, click the Window menu and select "Restart perspective". 2. If the previous step does not fix the problem: a. Close the Explorer b. Issue the following command at the command line: strmqcfg -i c. Start the Explorer again 3. If the previous step does not fix the problem: a. Close the Explorer b. Check there is no Eclipse process running. c. (Note: The following action removes Explorer data such as remote queue manager definitions and custom schemes and filters, so make a note of any such data you want to keep.) Delete the following folders: On Windows: C:\Documents and Settings\\Application Data\IBM\MQ Explorer C:\Documents and Settings\\.eclipse On Linux: /home//.mqdata /home//.eclipse d. Issue the following command at the command line: strmqcfg -i e. Start the Explorer again Support for WebSphere MQ on Windows Vista Japanese Edition ---------------------------------------------------------- WebSphere MQ does not support the Japanese standard, JIS X 0213:2004. Windows Vista Japanese Edition formally supports JIS X 0213:2004 characters. These JIS X 0213:2004 characters include Unicode CJK Ideographs Extension-B characters (UTF-16 surrogate pair (four bytes) characters). Installation verification test program for JCA with WAS CE ---------------------------------------------------------- For the JCA IVT to work on WebSphere Application Server Community Edition (WAS CE) there must be a connection factory with a name of "qcf" and a queue with a message-destination-name of "jmstestQ" defined in the geronimo-rar.xml when you deploy the RAR file. For the wmq.jmsra.ivt.ear file to deploy on version 2.0.1 or later of WAS CE the following xml files within the EAR file have to be updated as below: geronimo-application.xml xmlns:nam="[http://geronimo.apache.org/xml/ns/naming-1.2]"> openejb-jar.xml Clustering of topics -------------------- Though clustering of topics is generally supported, do not cluster SYSTEM.BASE.TOPIC or SYSTEM.DEFAULT.TOPIC. The CLUSTER parameter of these topics must be blank. Topics in overlapping clusters ------------------------------ If you define two or more topics, with one topic string being a more qualified version of the other (for example SPORTS and SPORTS/FOOTBALL), with the topics in different but overlapping clusters, publications can be delivered to unexpected recipient queue managers. For example: - Queue manager qmAB is in both clusters ClusterA and ClusterB - SPORTS is a cluster topic in ClusterA - SPORTS/FOOTBALL is a cluster topic in ClusterB Subscribers to SPORTS/FOOTBALL on queue managers which are only in ClusterA also receive publications from queue manager qmAB. Similarly, if a cluster topic and a local topic share a name, unexpected publications can be received. For example: - SPORTS is a cluster topic in ClusterA - Queue manager qmC in ClusterA defines a topic SPORTS with no cluster Subscribers for SPORTS on queue managers in ClusterA receive publications from qmC. MQ Explorer fails using Firefox on Linux ---------------------------------------- The WebSphere MQ Explorer might fail with the message "JVM terminated" when attempting to launch the Help Center. There is a known problem when running the Standard Widget Toolkit (SWT) browser inside Eclipse on some Linux distributions when the default browser is Firefox. To avoid this problem, set the value of the MOZILLA_FIVE_HOME environment variable to the folder containing your Firefox installation. For example, if Firefox is installed in /usr/lib/firefox-3.0.10, use the command: export MOZILLA_FIVE_HOME=/usr/lib/firefox-3.0.10 or setenv MOZILLA_FIVE_HOME /usr/lib/firefox-3.0.10 depending on the shell you are using. (This requirement is noted in the SWT FAQs section of the Eclipse Web site: http://www.eclipse.org/swt/faq.php#browserlinux) File Transfer Application help system not automatically available on Linux -------------------------------------------------------------------------- If the Help in the GUI is unavailable, an error is displayed when the File Transfer Application is started. You can find the html help files in /opt/mqm/eclipse/fta-help/plugins/com.ibm.mq.fta.doc_7.0.1.0/doc.zip Multi-instance queue managers are not supported on IBMi -------------------------------------------------------- Multi-instance queue managers are introduced with WebSphere MQ Version 7.0.1. IBM Knowledge Center states that these are available on all platforms except z/OS. However, they are not available on IBMi (formerly i5/OS). "Java Messaging and Web Services" component now includes XMS ------------------------------------------------------------ On Windows the component formerly known as "Java Messaging and Web Services" is now called "Java and .NET Messaging and Web Services". As part of this change additional files are installed with this component to enable use of the Message Service Client for .NET, also known as XMS. If you upgrade a Java-only installation you will also install the Message Service Client for .NET. For more information about XMS messaging see IBM Knowledge Center. Simplification of publish/subscribe authorities ----------------------------------------------- The way authorities are determined at the top of the topic tree has been simplified. If authorities are defined on the SYSTEM.BROKER.DEFAULT.STREAM or SYSTEM.BROKER.DEFAULT.SUBPOINT topic objects (and those topic objects still have empty topic strings), those authorities will no longer take effect. In order to apply topic authorities at the top of the topic tree, you should apply the authorities to the SYSTEM.BASE.TOPIC object. Use of HP Hotspot JVM --------------------- If you use an HP Hotspot JVM, set the Java System property -XX:+UseGetTimeOfDay. If you do not set this property, your application might not be aware of system time changes. XMS assemblies left in Global Assemblies Cache after uninstall -------------------------------------------------------------- On windows, uninstalling WebSphere MQ after installing WebSphere MQ7.0.1 through the fix pack might result in some assemblies (IBM.XMS.*.dll) being left in the .NET Global Assembly Cache (GAC). This will occur if the .NET framework is available on the machine and the "Java Messaging and Web Services" feature was selected in the original WebSphere MQ v7 installation (selected by default). This behaviour can be prevented by either rolling back the WebSphere MQ v 7.0.1 refresh pack or by running "amqiRegsiterdotNet.cmd /u" (available in the "\bin" directory) before uninstalling WebSphere MQ. MIGRATION ISSUES FOR VERSION 7.0.1 ================================== Migration from WebSphere MQ Version 6.0.2.3 or earlier on Windows ----------------------------------------------------------------- When you migrate from WebSphere MQ Version 6.0.2.3 or earlier to Version 7.0.1, the "exits" directory is emptied. This is normally c:\Program Files\IBM\WebSphere MQ\exits, or c:\Program Files\IBM\WebSphere MQ (x86)\exits, but you might have installed to a different directory. This issue only affects Windows installations. To fix it prior to migration, apply service patch 6.0.2.4 or later to the Version 6 installation. See APAR IC48397 for details. Otherwise, back up your "exits" directory before migrating. Migration from WebSphere MQ Version 6 to WebSphere MQ Version 7 on Windows -------------------------------------------------------------------------- When migrating WebSphere MQ from v6 to v7, if a queue manager has a startup property set to Automatic, the property will get changed to Interactive( manual) during the migration. To set queue manager startup property back to Automatic use the following MQ command: amqmdain auto QMgrName Migration from WebSphere MQ Version 6 earlier than CSD 6.0.2.3 -------------------------------------------------------------- The first time the WebSphere MQ Explorer is started after migration, error message AMQ4473 might be displayed and an FDC file written stating that the WMQ_Schemes.xml file used to save schemes was found to be in an invalid format, and that all user-defined schemes must be re-created. Before CSD 6.0.2.3 schemes were not saved correctly. If you use schemes, you will have experienced this problem and upgraded to a later CSD level. If you have not created your own schemes and are using an earlier version of WebSphere MQ, you will see this message on starting WebSphere MQ Explorer. However, MQ Explorer continues, creating a new default set of schemes, so no action is required. Migration: save JMSAdmin.config ------------------------------- Save the file JMSAdmin.config (in the /java/bin directory) to another location before upgrading to WebSphere MQ v.7.0 or it will be overwritten. migmbbrk might not migrate ACLS correctly when subscription points are used --------------------------------------------------------------------------- The WebSphere Message Broker publish/subscribe state migration tool (migmbbrk) might not migrate ACLS correctly when subscription points are used. Consider the following scenario: 1. A subscription to a WebSphere Message Broker broker references the topic tree a/b/c. 2. A publication to a/b/c uses a subscription point called SB1. 3. The topic string a/b has an ACL that grants publish access to a user, USER1. The migration to the queue manager creates two topic objects and a setmqaut command. It emulates subscription points by creating a topic object for SB1 with the topic string SB1/a/b/c. It also creates a topic object for a/b with an ACL granting publish access to USER1. The setmqaut command grants publish access to USER1 for the topic a/b. As a result of the migration the topic tree has two branches, a/b and SB1/a/b/c. The ACL is defined for the a/b branch but not for the SB1/a/b/c branch. Therefore publish access permission is granted to USER1 on a/b, but not granted to USER1 for the topic string SB1/a/b/c. If your topic tree includes both subscription points and user-defined ACLs, review both to see whether the ACLs that are defined in the broker and then migrated to the queue manager need to be manually replicated for the topic trees that lie below subscription points. Other changes ============= Updates in the XA sample makefile --------------------------------- Updates are made to the xaswit.mak file, so that it now contains up-to-date references to database product install directories. The default directories used in the sample makefile are changed to be more up-to-date. If you need to rebuild a switch load file, and need to continue to use old database product install directories or versions, please check and amend the xaswit.mak file so that it contains the correct information for your target machine. Do not rebuild your switch load file(s), unless it is necessary. You will ONLY need to rebuild a switch load file IF the install directory of your database product changes - eg. after installing a new version of the database product. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++ ++ ++ SECTION 2 : HOW TO OBTAIN AND INSTALL THIS FIX PACK ++ ++ ++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Product/Component Release: 7.0 Update Name: WebSphere MQ fix pack 7.0.1.13 2.1 Download location --------------------- Download the fix pack from the following location: http://www.ibm.com/support/docview.wss?uid=swg21254675 2.2 Prerequisites and corequisites ---------------------------------- Before downloading the fix pack, perform the following steps: 1. Ensure that your system meets all the system requirements: http://www.ibm.com/software/integration/wmq/requirements/index.html This action prevents technical problems that might occur after the installation and configuration of the fix pack. 2. Review the Flashes and Authorized Problem Analysis Reports (APARs) on the WebSphere MQ for UNIX(R) and Windows(R) product support Web site: http://www.ibm.com/software/integration/wmq/support/ APARs describe defects that have been addressed in a fix pack, For a list of APARs for this fix pack, refer to: http://www.ibm.com/support/docview.wss?uid=swg27014224 3. Ensure that you have sufficient file system free space to download and extract the fix pack. You need to have a file system with one gigabyte of free space to contain the compressed file and the uncompressed installation image. 4. Ensure that you have the free space required to install the fix pack. The free space must be available in the location of the WebSphere MQ installation that you are updating. To determine the space used by the existing WebSphere MQ products on UNIX platforms, perform the command: du -k -s MQDIR where MQDIR represents the location where the WebSphere MQ product is installed. 5. If you already have the WebSphere MQ v7 product installed and have obtained special fixes, contact IBM(R) support to determine whether you need an updated version of the fixes before you install the fix pack. This helps to ensure that your system is in a consistent state and that no special fixes are lost. 2.3 Installing -------------- Before proceeding with the installation process, view the online version of the readme file to check if information has changed since the readme file download: https://ibm.biz/mqreadmes 2.3.1 Prior to installation --------------------------- Before installing the fix pack, perform the following steps: 1. Read all of this readme. Note particularly the additional steps that are necessary if you have installed GSKit in order to use SSL channels with WebSphere MQ. 2. Download the fix pack to an appropriate location. 3. Uncompress the fix pack. 4. Stop all WebSphere MQ processes and its applications. 2.3.2 Downloading the fix pack to an appropriate location ------------------------------------------------------------- There must not be any spaces in the directory path where you plan to download and uncompress the fix pack. If there are spaces in the directory path, the installation will fail. For example, make sure that your directory path resembles the following: /home/WMQFixPack/FP1/ ... It should not resemble the following: /home/WMQ FixPack/FP1/ ... 2.3.3 Uncompressing the fix pack installation images ---------------------------------------------------- All fix pack installation images on the download site are compressed in gz/Z/zip format. Before you can apply the fix pack from this format, copy the downloaded file to a temporary directory and use gunzip/uncompress and tar to extract the fix pack installation image. 2.3.4 Extract the fix pack install files ---------------------------------------- To extract the fix pack install files, perform the following steps: 1. Copy the gzipped/Z image to a temporary location. 2. Change to the directory where you copied the image. 3. The following are example commands to extract the fix pack installation image: gunzip -c filename.tar.gz | tar -xvf - zcat filename.tar.Z | tar -xvf - unzip filename.zip where filename.tar.gz etc. is the name of the downloaded file. 2.3.5 Stopping all WebSphere MQ processes ----------------------------------------- You must ensure that all WebSphere MQ processes are stopped and do not start automatically during the installation procedure. To stop all WebSphere MQ processes, perform the following steps: 1. Log in as a user in the mqm group. 2. Use the endmqm command to stop all running queue managers. 3. Stop any listeners associated with the queue managers, using the command: endmqlsr -m QMgrName 4. To check that you have stopped all of them, enter the following: ps -ef | grep mq Check that there are no processes listed that are running command lines beginning amq or runmq. Ignore any that start with amqi. 5. Take any further administrative actions (as root if necessary) to stop all applications that use queue managers on the system, and prevent them from restarting automatically during the installation procedure 2.3.6 Installation ------------------ For more information about how to install the fix pack see the appropriate Quick Beginnings section of the WebSphere MQ product information: AIX: http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.amqaac.doc/aq10720_.htm HP-UX: http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.amqcac.doc/hq10790_.htm Linux: http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.amq1ac.doc/lq10860_.htm Solaris: http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.amqdac.doc/sq10780_.htm Windows: http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.amqtac.doc/wq11230_.htm 2.4 Post installation --------------------- 2.4.1 More information about installations of GSKit and JRE ------------------------------------------------------------ For information about the levels of GSKit and JRE included with this product, see the following link: http://www.ibm.com/support/docview.wss?uid=swg27038676 Perform the necessary tasks after installation ---------------------------------------------- After installing this fix pack, perform the following steps: 1. Verify the installation. Refer to the Quick Beginnings section of the WebSphere MQ product documentation for the appropriate platform. 2. Restart the queue managers. After applying a fix pack, it is not mandatory to recompile applications. 2.4.2 More Information about Installations of GSKit, JDK, JRE and IA9H (IBM Service client for .NET) ------------------------------------------------------------------- For information about the levels of GSKit and JRE included with this product, see the following link: http://www.ibm.com/support/docview.wss?uid=swg27038676 2.4.3 Installing GSKit ----------------------- For information about installing GSKit, refer to the Quick Beginnings section of the WebSphere MQ product documentation for the appropriate platform: AIX:http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.amqaac.doc/aq20040_.htm HP-UX: http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.amqcac.doc/hq10870_.htm Linux:http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.amq1ac.doc/lq10980_.htm Solaris: http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.amqdac.doc/sq10860_.htm Windows: http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.amqtac.doc/wq12150_.htm 2.4.4 Troubleshoot Installation from Support site ------------------------------------------------- Before contacting IBM you are recommended to view the web site http://www.ibm.com/support/docview.wss?uid=swg21229861 which has specific advice on problem solving and data collection for WebSphere MQ. 2.5 Uninstalling ---------------- For more information about how to remove the fix pack see the appropriate Quick Beginnings section of the WebSphere MQ product documentation: AIX: http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.amqaac.doc/aq10740_.htm HP-UX: http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.amqcac.doc/hq10810_.htm Linux: http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.amq1ac.doc/lq10880_.htm Solaris: http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.amqdac.doc/sq10800_.htm Windows: http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.amqtac.doc/wq11270_.htm 2.6 List of fixes ----------------- Fixes included in this fix pack: http://www.ibm.com/support/docview.wss?uid=swg27014224 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++ ++ ++ SECTION 3 : IBM MESSAGE SERVICE CLIENT FOR .NET V2.0.0.13 ++ ++ ++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 3.1 Changes in this release --------------------------- This version of XMS .NET has been tested for interaction with IBM WebSphere MQ 7.0.1.13. In addition, several fixes have been applied to resolve issues highlighted from continued testing and customer feedback. If Microsoft .NET Framework Version 4.0 is installed on the machine, you might need to create or set the HKEY_LOCAL_COMPUTER\SOFTWARE\Microsoft\.NETFramework registry key as follows: "OnlyUseLatestCLR"=dword:00000001 3.2 Troubleshooting XMS .NET issues -------------------------------- a) User authentication for WebSphere MQ is performed by using the details of the logged on user and not the information provided in the XMSC.USERID and XMSC.PASSWORD fields. This is designed to maintain consistency with WebSphere MQ. See IBM Knowledge Center for further details about authentication. b) On a Windows 64-bit platform, the setting or getting of values for the property type "double" using the SetDoubleProperty() or GetDoubleProperty() methods might not work correctly, if the values involved are smaller than Double.Epsilon. For example, if you try to set a value of 4.9E-324 for a property with type double, the Windows 64-bit platforms treat it as 0.0. So, in a distributed messaging environment, if a JMS or other application sets the value for a double property as 4.9E-324 on any Unix or Windows 32-bit machine, and XMS .NET runs on a 64-bit machine, the value returned by GetDoubleProperty() is 0.0. This is a known issue with Microsoft .NET 2.0 Framework. Refer to the following link for more details: http://support.microsoft.com/kb/970495 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++ ++ ++ SECTION 4 : COPYRIGHT, NOTICES AND TRADEMARKS ++ ++ ++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 4.1 Copyright and trademark information --------------------------------------- http://www.ibm.com/legal/copytrade.shtml 4.2 Notices ----------- INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. THIRD-PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided or referenced below. Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version. Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities (collectively "IBM"), the third party software code identified below are "Excluded Components" and are subject to the following terms and conditions: * the Excluded Components are provided on an "AS IS" basis * IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE * IBM will not be liable to you or indemnify you for any claims related to the Excluded Components * IBM will not be liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages with respect to the Excluded Components. 4.3 Trademarks -------------- The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: AIX FFST i5/OS IBM MQSeries SupportPac WebSphere z/OS Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. UNIX is a registered trademark of The Open Group in the United States and other countries Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others.