Abstract
--------
This document contains the readme for IBM MQ Version 9.0 Long Term Support release
and its maintenance, and also for IBM MQ Version 9.0 Continuous Delivery releases.
The English language version of this document is the most up to date version.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
DESCRIPTION
===========
This file describes product limitations and known problems.
The latest version of this file can be found here:
https://ibm.biz/mqreadmes
Translated versions can be found here:
ftp://public.dhe.ibm.com/software/integration/wmq/docs/V9.0/Readme/
In addition to this file, you can find more information on the IBM MQ website:
http://www.ibm.com/software/products/ibm-mq
The SupportPac web page is here:
https://ibm.biz/mqsupportpacs
For current information about known problems and available fixes, see the IBM MQ Support
page:
https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ
Web documentation updates:
The latest updates to the web-based IBM MQ documentation are available from
the IBM MQ library page:
http://www-01.ibm.com/software/integration/wmq/library/
Announcement letters:
The announcement letters for IBM MQ Version 9.0 (US English) are available at the locations
detailed below. See the announcement letters for the following types of information:
- Detailed product description, including description of new function
- Product-positioning statement
- Ordering details
- Hardware and software requirements
Announcement letters for Continuous Delivery Releases:
IBM MQ V9.0.5
https://www.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/9/897/ENUS218-069/index.html
IBM MQ V9.0.4
https://www.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/0/897/ENUS217-420/index.html
IBM MQ z/OS V9.0.4
https://www.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/6/897/ENUS217-416/index.html
IBM MQ for z/OS V9.0.3
https://www.ibm.com/common/ssi/rep_ca/5/897/ENUS217-165/index.html
IBM MQ Distributed V9.0.1
https://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&subtype=CA&htmlfid=897/ENUS216-447&appname=USN
IBM MQ for z/OS V9.0.1
https://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&subtype=CA&htmlfid=897/ENUS216-507&appname=USN
IBM MQ for z/OS one time charge offerings V9.0.1
https://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&subtype=CA&htmlfid=897/ENUS216-506&appname=USN
Announcement letters for IBM MQ Version 9.0.0:
IBM MQ Distributed V9.0.0
http://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=877&letternum=ENUSZP16-0205
IBM MQ for z/OS V9.0.0
http://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS216-206
IBM MQ for z/OS Value Unit Edition V9.0.0
http://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&appname=gpateam&supplier=877&letternum=ENUSZP16-0219
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
UPDATE HISTORY
16 Mar 2018 - Updates for IBM MQ Version 9.0.5
08 Mar 2018 - Updates for IBM MQ Version 9.0.0.3
30 Oct 2017 - Updates for IBM MQ Version 9.0.4
29 Sep 2017 - Updates for IBM MQ Version 9.0.0.2
23 May 2017 - Updates for IBM MQ Version 9.0.3
11 May 2017 - Updates for IBM MQ Version 9.0.0.1
22 Mar 2017 - Add "JRE security vulnerabilities" entry for V9.0.1 and V9.0.2
17 Mar 2017 - Updates for IBM MQ Version 9.0.2
15 Nov 2016 - Updates for IBM MQ Version 9.0.1
02 Jun 2016 - Updates for IBM MQ Version 9.0.0
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++ ++
++ INSTALLATION INSTRUCTIONS ++
++ ++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Installation instructions are available as part of the IBM MQ Version 9.0
product documentation published in IBM Knowledge Center:
http://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.ins.doc/q008250_.htm
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++ ++
++ LIMITATIONS AND KNOWN PROBLEMS FOR CONTINUOUS DELIVERY RELEASES ++
++ ++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
LIMITATIONS AND KNOWN PROBLEMS FOR VERSION 9.0.5
================================================
Changes to Product Insights support
-----------------------------------
In IBM MQ Version 9.0.5, the name of the Product Insights configuration stanza
in qm.ini changes from BluemixRegistration to ReportingService. Queue managers
configured with the old stanza name will not start until the stanza name is
changed or the stanza is removed from qm.ini.
Java client hangs when queue manager is quiescing as new connection attempt is made
-----------------------------------------------------------------------------------
This issue affects applications that use the following MQ features:
- Classes for JMS
- Classes for Java
- JCA resource adapter
- OSGi bundles
- Managed File Transfer
An MQ queue manager can send, to connected clients, notifications requesting a
controlled closure of conversations (connection handles). A queue manager sends
these notifications, for example, when the queue manager is being quiesced. If a
thread within a Java client receives one of these notifications at the same time
as another thread within the client requests a new conversation, a deadlock can
occur because both threads need access to the internal "connectionsLock" on the
RemoteConnectionSpecification object.
This issue is fixed in IBM MQ Version 9.0.5, by APAR IT22127. The fix launches
a new thread to re-associate the connection with its RemoteConnectionSpecification,
if necessary, so that the connection can be reused.
For the fix to work for your applications, you need to add the following new
policy to the policy file used by the Java Security Manager:
permission java.lang.RuntimePermission "modifyThread";
Changes to default values for some ciphers
------------------------------------------
The JRE has been updated to 8.0.5.10 in this release. By default, this level
of the JRE disables ciphers whose algorithms match DES40_CBC or RC4_40.
For example:
SSL_KRB5_EXPORT_WITH_DES_CBC_40_SHA
To re-enable these ciphers, update your java/lib/security/java.security
file to remove the algorithm that your cipher uses from the
jdk.tls.disabledAlgorithms name:value pair.
Spurious warning message and FDCs generated during RDQM uninstall process
-------------------------------------------------------------------------
If a replicated data queue manager exists when the MQSeries rpms are uninstalled
(for example, during an upgrade) FDCs with Probe Id XC721050 are generated,
during the uninstall, from program name amqiclen.
These can safely be ignored.
When the drbd-utils rpm is uninstalled, the following warning is displayed:
warning: /etc/drbd.d/global_common.conf saved as /etc/drbd.d/global_common.conf.rpmsave
This can safely be ignored.
Error message when updating RHEL system that has RDQM installed
---------------------------------------------------------------
If you do a "yum update" on a RHEL system that has RDQM installed, you get
an error about a libqb package. To avoid this, edit the /etc/yum.conf file
and add the following line:
exclude=libqb*
LIMITATIONS AND KNOWN PROBLEMS FOR VERSION 9.0.4
================================================
No known problems or limitations.
LIMITATIONS AND KNOWN PROBLEMS FOR VERSION 9.0.3
================================================
PTF needed for IBM MQ Advanced for z/OS VUE to connect to the IBM Blockchain
----------------------------------------------------------------------------
service on Bluemix
------------------
Version 9.0.3 introduces a new Connector Pack component for IBM MQ Advanced for
z/OS Value Unit Edition. This pack provides the following connectivity:
- IBM MQ for z/OS connectivity to the IBM Product Insights service on Bluemix
- IBM MQ for z/OS connectivity to the IBM Blockchain service on Bluemix
- MFT Agent running on z/OS connectivity to IBM MQ that runs on a remote z/OS system
To enable the connectivity to the IBM Blockchain service on Bluemix, you need to
install the PTF for APAR PI81206. If you do not do this, an attempt to run the
MQ Blockchain Bridge displays the following error text: "The MQ to BlockChain
bridge requires an enablement APAR to run. Consult the Knowledge Center for further
details."
LIMITATIONS AND KNOWN PROBLEMS FOR VERSION 9.0.2
================================================
JRE security vulnerabilities
----------------------------
There are multiple vulnerabilities in IBM Runtime Environment Java Version 8
used by IBM MQ Version 9.0.2. Further details, including CVSS scoring and
interim fix details, can be found here:
http://www.ibm.com/support/docview.wss?uid=swg22000304
This issue is fixed in the JRE that is included in IBM MQ Version 9.0.3.
FDC can incorrectly show missing subscriptions for a clustered queue manager
----------------------------------------------------------------------------
The cluster repository process includes maintenance checks. One check is that
internal subscriptions exist for queue and queue manager objects in the local
queue manager view of the cluster configuration. If a queue manager record is
found not to have subscriptions in the clusters it is a member of, an FDC with
probe RM702021 (Missing Subscription) is generated.
However, during the process of creating a new full repository there is a point
in time when the queue manger record can include a cluster name that the local
queue manager is not yet aware of (because it is not yet a full repository for
the named cluster, nor is it a partial repository either). In this case, the
generated FDC is misleading as there should not be any subscriptions.
APAR IT14931 checks if the queue manager could be a deferred full repository,
and if so does not generate the FDC. But the system cannot be sure that the
queue manager is about to become a full repository, so it is important that you
also make the following manual checks:
- Check that cluster receiver channels in the cluster configuration are shared
in the appropriate clusters.
- Check that namelists used by cluster receiver channels on remote queue
managers, contain the expected list of cluster names.
- Check that manually defined sender channels are correctly defined, and that
the destination is expected to be a full repository (manually defined channels
(CLUSSDR) are always expected to point to full repositories. CLUSSDRs that
point at partial repositories are a configuration error).
Certificate keystores might not open if they contain certificates
-----------------------------------------------------------------
with serial numbers that have a leading zero
--------------------------------------------
If you are using a JRE other than the one supplied in IBM MQ V9.0.2, note that
recently released JRE maintenance levels that are supported by IBM MQ, including
those provided by Oracle and by other IBM products, are known to fail to open
certificate keystores if they contain certificates with serial numbers that have a
leading zero in their encoding. This might impact product and application function.
Further details can be found here: http://www.ibm.com/support/docview.wss?uid=swg22000235
IBM MQ V9.0 Managed File Transfer agents publish XML status messages
--------------------------------------------------------------------
in bytes message format (MQFMT_NONE) by default
-----------------------------------------------
APAR IT15971, included in IBM MQ V9.0.2, adds a property messagePublicationFormat.
This property controls the format of messages that are published to the SYSTEM.FTE
topic. The default behavior of the MFT agent was not intended to change, so by
default the messages should have been published in the "mixed" format - that is, the
MQFMT_NONE and MQFMT_STRING format, depending on the Topic. However, under
APAR IT15971, when you specify messagePublicationFormat=mixed the effect
is the same as specifying messagePublicationFormat=MQFMT_NONE.
The issue is fixed in IBM MQ Version 9.0.3, by APAR IT19721.
LIMITATIONS AND KNOWN PROBLEMS FOR VERSION 9.0.1
================================================
JRE security vulnerabilities
----------------------------
There are multiple vulnerabilities in IBM Runtime Environment Java Version 8
used by IBM MQ Version 9.0.1. Further details, including CVSS scoring and
interim fix details, can be found here:
http://www.ibm.com/support/docview.wss?uid=swg22000304
This issue is fixed in the JRE that is included in IBM MQ Version 9.0.3.
MQ JMS ExceptionListener is not invoked for all cases of connection broken exceptions
-------------------------------------------------------------------------------------
The following issues affect a JMS application that uses the IBM MQ V9.0 classes for JMS:
- When you set the JMS ConnectionFactory property JmsConstants.ASYNC_EXCEPTIONS
to the value JmsConstants.ASYNC_EXCEPTIONS_ALL, your application's JMS
ExceptionListener should be called not only for broken connection exceptions,
but also for any exception raised during asynchronous message delivery to a
JMS MessageListener. However, non-connection broken exceptions (for example
MQRC_GET_INHIBITED) were not being delivered to the ExceptionListener.
- When a JMS Session uses a different TCP/IP socket to the JMS Connection, the
application's ExceptionListener was not invoked if only the socket used by the
JMS Session is broken.
- Your application's JMS ExceptionListener is only invoked for a connection broken
exception when the application is using asynchronous message consumers, and not
when using synchronous message consumers.
APAR IT14820 implements the following fixes:
- An ExceptionListener registered by an application is invoked for any connection
broken exceptions, regardless of whether the application is using synchronous or
asynchronous message consumers.
- An ExceptionListener registered by an application is invoked if a TCP/IP socket
used by a JMS Session is broken.
- Non-connection broken exceptions (for example MQRC_GET_INHIBITED) that arise
during message delivery are delivered to an application's ExceptionListener when
the application is using asynchronous message consumers and the JMS
ConnectionFactory used by the application has the ASYNC_EXCEPTIONS property set
to the value ASYNC_EXCEPTIONS_ALL.
GSKit 8.0.50.69 or later alters the stash file format
-----------------------------------------------------
APAR IT16295 updates the GSKit component level to 8.0.50.69 or later. This update
alters the stash file format used when generating a .sth file to stash the key
database password. Stash files generated by this level of the GSKit are not
readable by earlier GSKit levels.
To ensure compatibility, any applications or other installations that use a stash
file generated with this level of the GSKit should be updated to a version of MQ
that contains GSKit 8.0.50.69 or later.
If you cannot update applications or other installations, you can request
a backwards-compatible stash file format. You do this by supplying the "-v1stash"
parameter to the runmqakm or runmqckm commands when you use the "-stash" or
"-stashpw" options to generate a stash file.
You cannot generate a backwards-compatible stash file when using the iKeyman GUI.
Log-on issues when using Managed File Transfer agents on z/OS
-------------------------------------------------------------
When the IBM WebSphere MQ File Transfer Edition product became a
component of IBM MQ, a number of security enhancements were made.
These included restricting the following commands so that they can
only be issued by the user that the agent or logger processes were
running as:
- fteStartAgent
- fteStopAgent
- fteSetAgentTraceLevel
- fteShowAgentDetails
- fteStartLogger
- fteStopLogger
- fteSetLoggerTraceLevel
When you use IBM MQ Managed File Transfer on z/OS, you can run agents
as a started task. Such tasks typically run as an administrative user
that might not have log-on privileges. In this situation, you cannot
log on to the z/OS system as the same user that the agent is running
under, which in turn means that the following commands cannot be
issued for that agent:
- fteStartAgent
- fteStopAgent
- fteSetAgentTraceLevel
- fteShowAgentDetails
APAR PI52942 adds a new agent property "adminGroup" for use with
IBM MQ Managed File Transfer agents on z/OS. When this property is
set to the name of an existing group, members of that group can execute
the previous commands for that agent.
strmqweb (Web console) does not work on some Ubuntu systems
-----------------------------------------------------------
On Ubuntu, after you run the strmqweb command to launch the Web console, you might
find that you can log on and see a running queue manager, but when you try to
interact with the queue manager you get an error.
This issue seems only to affect Ubuntu systems where the default shell is Dash.
A workaround is to stop the web server by running the command "endmqweb", then
restart it by running the command "bash strmqweb". This ensures the script is run
under Bash.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++ ++
++ LIMITATIONS AND KNOWN PROBLEMS FOR LONG TERM SUPPORT RELEASES ++
++ ++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
LIMITATIONS AND KNOWN PROBLEMS FOR VERSION 9.0.0, Fix Pack 3
============================================================
Java client hangs when queue manager is quiescing as new connection attempt is made
-----------------------------------------------------------------------------------
This issue affects applications that use the following MQ features:
- Classes for JMS
- Classes for Java
- JCA resource adapter
- OSGi bundles
- Managed File Transfer
An MQ queue manager can send, to connected clients, notifications requesting a
controlled closure of conversations (connection handles). A queue manager sends
these notifications, for example, when the queue manager is being quiesced. If a
thread within a Java client receives one of these notifications at the same time
as another thread within the client requests a new conversation, a deadlock can
occur because both threads need access to the internal "connectionsLock" on the
RemoteConnectionSpecification object.
This issue is fixed in IBM MQ Version 9.0.0.3, by APAR IT22127. The fix launches
a new thread to re-associate the connection with its RemoteConnectionSpecification,
if necessary, so that the connection can be reused.
For the fix to work for your applications, you need to add the following new
policy to the policy file used by the Java Security Manager:
permission java.lang.RuntimePermission "modifyThread";
Changes to default values for some ciphers
------------------------------------------
The JRE has been updated to 8.0.5.10 in this release. By default, this level
of the JRE disables ciphers whose algorithms match DES40_CBC or RC4_40.
For example:
SSL_KRB5_EXPORT_WITH_DES_CBC_40_SHA
To re-enable these ciphers, update your java/lib/security/java.security
file to remove the algorithm that your cipher uses from the
jdk.tls.disabledAlgorithms name:value pair.
LIMITATIONS AND KNOWN PROBLEMS FOR VERSION 9.0.0, Fix Pack 2
============================================================
Cannot start MQ Explorer after reverting to an earlier Fix Pack on Windows 64
-----------------------------------------------------------------------------
After uninstalling a Fix Pack on 64-bit Windows, and reverting to the previous
Fix Pack, you might not be able to start MQ Explorer using strmqcfg in the
earlier Fix Pack. This issue was first seen when reverting from
Version 9.0.0, Fix Pack 2 to Version 9.0.0, Fix Pack 1.
To resolve this issue, see the following technote:
http://www.ibm.com/support/docview.wss?uid=swg22009137
LIMITATIONS AND KNOWN PROBLEMS FOR VERSION 9.0.0, Fix Pack 1
============================================================
Platform availability for this Fix Pack
---------------------------------------
Fix Packs are delivered for distributed platforms only. They are not delivered
for the z/OS platform, or for the IBM MQ Appliance. IBM MQ Version 9.0.0,
Fix Pack 1 is released only on AIX, IBMi, Linux, and Windows. It is not released
on HP-UX or Solaris.
FDC can incorrectly show missing subscriptions for a clustered queue manager
----------------------------------------------------------------------------
The cluster repository process includes maintenance checks. One check is that
internal subscriptions exist for queue and queue manager objects in the local
queue manager view of the cluster configuration. If a queue manager record is
found not to have subscriptions in the clusters it is a member of, an FDC with
probe RM702021 (Missing Subscription) is generated.
However, during the process of creating a new full repository there is a point
in time when the queue manger record can include a cluster name that the local
queue manager is not yet aware of (because it is not yet a full repository for
the named cluster, nor is it a partial repository either). In this case, the
generated FDC is misleading as there should not be any subscriptions.
APAR IT14931 checks if the queue manager could be a deferred full repository,
and if so does not generate the FDC. But the system cannot be sure that the
queue manager is about to become a full repository, so it is important that you
also make the following manual checks:
- Check that cluster receiver channels in the cluster configuration are shared
in the appropriate clusters.
- Check that namelists used by cluster receiver channels on remote queue
managers, contain the expected list of cluster names.
- Check that manually defined sender channels are correctly defined, and that
the destination is expected to be a full repository (manually defined channels
(CLUSSDR) are always expected to point to full repositories. CLUSSDRs that
point at partial repositories are a configuration error).
MQ JMS ExceptionListener is not invoked for all cases of connection broken exceptions
-------------------------------------------------------------------------------------
The following issues affect a JMS application that uses the IBM MQ V9.0 classes for JMS:
- When you set the JMS ConnectionFactory property JmsConstants.ASYNC_EXCEPTIONS
to the value JmsConstants.ASYNC_EXCEPTIONS_ALL, your application's JMS
ExceptionListener should be called not only for broken connection exceptions,
but also for any exception raised during asynchronous message delivery to a
JMS MessageListener. However, non-connection broken exceptions (for example
MQRC_GET_INHIBITED) were not being delivered to the ExceptionListener.
- When a JMS Session uses a different TCP/IP socket to the JMS Connection, the
application's ExceptionListener was not invoked if only the socket used by the
JMS Session is broken.
- Your application's JMS ExceptionListener is only invoked for a connection broken
exception when the application is using asynchronous message consumers, and not
when using synchronous message consumers.
APAR IT14820 implements the following fixes:
- An ExceptionListener registered by an application is invoked for any connection
broken exceptions, regardless of whether the application is using synchronous or
asynchronous message consumers.
- An ExceptionListener registered by an application is invoked if a TCP/IP socket
used by a JMS Session is broken.
- Non-connection broken exceptions (for example MQRC_GET_INHIBITED) that arise
during message delivery are delivered to an application's ExceptionListener when
the application is using asynchronous message consumers and the JMS
ConnectionFactory used by the application has the ASYNC_EXCEPTIONS property set
to the value ASYNC_EXCEPTIONS_ALL.
GSKit 8.0.50.69 or later alters the stash file format
-----------------------------------------------------
APAR IT16295 updates the GSKit component level to 8.0.50.69 or later. This update
alters the stash file format used when generating a .sth file to stash the key
database password. Stash files generated by this level of the GSKit are not
readable by earlier GSKit levels.
To ensure compatibility, any applications or other installations that use a stash
file generated with this level of the GSKit should be updated to a version of MQ
that contains GSKit 8.0.50.69 or later.
If you cannot update applications or other installations, you can request
a backwards-compatible stash file format. You do this by supplying the "-v1stash"
parameter to the runmqakm or runmqckm commands when you use the "-stash" or
"-stashpw" options to generate a stash file.
You cannot generate a backwards-compatible stash file when using the iKeyman GUI.
Log-on issues when using Managed File Transfer agents on z/OS
-------------------------------------------------------------
When the IBM WebSphere MQ File Transfer Edition product became a
component of IBM MQ, a number of security enhancements were made.
These included restricting the following commands so that they can
only be issued by the user that the agent or logger processes were
running as:
- fteStartAgent
- fteStopAgent
- fteSetAgentTraceLevel
- fteShowAgentDetails
- fteStartLogger
- fteStopLogger
- fteSetLoggerTraceLevel
When you use IBM MQ Managed File Transfer on z/OS, you can run agents
as a started task. Such tasks typically run as an administrative user
that might not have log-on privileges. In this situation, you cannot
log on to the z/OS system as the same user that the agent is running
under, which in turn means that the following commands cannot be
issued for that agent:
- fteStartAgent
- fteStopAgent
- fteSetAgentTraceLevel
- fteShowAgentDetails
APAR PI52942 adds a new agent property "adminGroup" for use with
IBM MQ Managed File Transfer agents on z/OS. When this property is
set to the name of an existing group, members of that group can execute
the previous commands for that agent.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++ ++
++ LIMITATIONS AND KNOWN PROBLEMS FOR THE INITIAL V9.0.0 RELEASE ++
++ ++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The MQ Explorer Managed File Transfer plugin does not handle passwords longer
-----------------------------------------------------------------------------
than 12 characters if MQCSP Authentication Mode is enabled
----------------------------------------------------------
If you use the MQ Explorer Managed File Transfer plugin, or have Managed File
Transfer agents that connect to a queue manager using the CLIENT transport and
specify a password, then the agent does not authenticate with the queue manager
if the password specified is greater than 12 characters in length. This is
because the code does not use MQCSP authentication, and authenticates
using "compatibility mode" which limits the password to 12 characters in length.
Under APAR IT17772, the code is updated so that you can disable the default
compatibility mode and enable MQCSP Authentication mode. You can do this
in the following ways:
- In the MQ Explorer:
- Select the queue manager you want to connect to.
- Right click, and select Connection Details > Properties.
- Click the Userid tab.
- Ensure "Enable user identification" is selected, and clear
the "User identification compatibility mode" checkbox.
- For MFT agents:
Add a new parameter "useMQCSPAuthentication" to the MFTCredentials.xml file for
the relavant user. Set the parameter to true. If the parameter is not there, it
is by default set to false and uses compatibility mode to authenticate the user
with the queue manager.
Here is an example entry to show how to set the useMQCSPAuthentication parameter
in the MFTCredentials.xml file:
This fix is implemented in IBM MQ Version 9.0.3, and in
IBM MQ Version 9.0.0, Fix Pack 2.
The File Transfer fteCleanAgent command, run with no parameters,
----------------------------------------------------------------
does the equivalent of -all
---------------------------
When running the fteCleanAgent command with only the agent name and no arguments
specified, the behavior is equivalent to fteCleanAgent -all. As a
result, all in-progress and pending transfers, resource monitor definitions and
scheduled transfers definitions on the agent the command was run against are
cleared. For example, the following two commands result in the same
behavior:
fteCleanAgent agent100
fteCleanAgent -all agent100
Under APAR IT15522, the fteCleanAgent command is updated so that a user must
specify which Managed File Transfer state to clear by passing the appropriate
parameters to the command, as well as providing an agent name. This APAR also adds
a new property to revert fteCleanAgent to its original behavior if required.
The property is called "failCleanAgentWithNoArguments" and is set in the
command.properties file. By default the value of "failCleanAgentWithNoArguments"
is true, and the fteCleanAgent command fails to run if only the agent name
parameter is specified.
This fix is implemented in IBM MQ Version 9.0.3, and in
IBM MQ Version 9.0.0, Fix Pack 2.
.NET client policy files are not shipped with early MQ Version 9 releases
-------------------------------------------------------------------------
Policy files for the .NET client of IBM MQ are not shipped with IBM MQ
Version 9.0.3 and earlier, or IBM MQ Version 9.0.0 Fix Pack 1 and earlier.
If an application has been compiled using an MQ version earlier than V9,
and you have to run it against one of the affected Version 9 releases,
either copy the contents of the NonPrimaryRedirect.config file (located at
&MQ_INSTALL_PATH&\Tools\dotnet\samples\cs\base) to the application's app.config
file, or recompile the application with the affected Version 9 release.
This issue is fixed by APAR IV98407. This fix is implemented in IBM MQ
Version 9.0.4, and in IBM MQ Version 9.0.0, Fix Pack 2.
Correlation ID selector defined on a JMS message listener is not passed
-----------------------------------------------------------------------
to the queue manager
--------------------
The correlation identifier message selector defined on the MessageConsumer or
JMSConsumer object on which a JMS MessageListener is registered is not being
passed to the queue manager. This results in all messages on the destination
being sent to the listener, instead of only those that match the selector.
This issue is fixed by APAR IT16016. This fix is implemented in
IBM MQ Version 9.0.3, and in IBM MQ Version 9.0.0, Fix Pack 2.
JMS application returns null, and triggers
------------------------------------------
"Receive interrupted by async Session start" message
----------------------------------------------------
When an application creates an asynchronous consumer on a JMS session,
associates a MessageListener with that consumer, then creates a synchronous
consumer in the onMessage method of that MessageListener using the same session
the original asynchronous consumer was created with, any subsequent receive on
that synchronous consumer returns null instead of a message, and outputs a
message to the console: "Receive interrupted by async Session start".
The JMS specification does not permit the use of a session for synchronous
methods when asynchronous message delivery is running. Your JMS application
must create a separate session if you want to use both synchronous methods and
asynchronous delivery simultaneously.
Under APAR IT13758, the message output by the console is changed to give this
explanation and solution. This change is implemented in IBM MQ Version 9.0.1,
and in IBM MQ Version 9.0.0, Fix Pack 1.
JRE Null pointer when using SUITEB SSL FIPS with the AMQP listener
------------------------------------------------------------------
When using IBM MQ's AMQP listener to authenticate an AMQP client using SUITEB
compliant certificates and ciphersuite with SSLFIPS(YES) set on the queue manager,
the listener might unexpectedly abend with a null pointer exception coming from
within the Java Runtime Environment's com.ibm.crypto.fips.provider.GCTR class.
This issue is fixed in the Java Runtime Environment by APAR IV83436.
The -mt flag in the java/lib64/Makefile must be removed on Linux systems
------------------------------------------------------------------------
When you compile the XA switch load libraries for the 64-bit IBM MQ
Classes for Java, you might get the following error:
gcc: error: unrecognized command line option ‘-mt’
If you get this error, remove the '-mt' flag from the following file:
/java/lib64/jdbc/Makefile
The flag is set in the following line:
LINK_OPTIONS = -eMQStart -m64 -mt -mcmodel=medium ${MQLIBPATH} ${MQLIBS}
The IBM MQ Managed File Transfer Java EE database logger generates warning
--------------------------------------------------------------------------
messages in WebSphere Application Server Community Edition Version 2.1 when
---------------------------------------------------------------------------
used with an Oracle DB
----------------------
This issue affects all users of the database logger to persist, to an Oracle
database, information published as XML log messages to the SYSTEM.FTE topic on
the coordination queue manager.
If any of the columns defined for a table created in the Oracle database are
of type CLOB (e.g., NCLOB), the Java class defined using Java Persistence
Architecture (JPA) to represent that table should annotate the class
member-variables representing the column of type CLOB with "@Lob". If not,
the column type is assumed to be of type "VARCHAR".
In previous versions of the product, this annotation was not included in the
Java classes provided with the IBM MQ Managed File Transfer component.
Therefore, when the JPA implementation tried to match the member field
representing a column in a database table with the actual column in the
database table, the difference was detected and reported as a warning.
This issue is fixed in IBM MQ Version 9.0.0, subject to the following
ongoing limitations:
- Columns with the names "SOURCE_BRIDGE_URL" and "DESTINATION_BRIDGE_URL"
in the table "FTELOG"."TRANSFER_EVENT" should be defined with the column
length 2083.
- Users of the MQ Managed File Transfer component that have a database logger
that connects to a DB2 database might have to update these column lengths
manually after applying this fix pack, if the length of these columns has
been defined as 1024. Otherwise if data longer than 1024 bytes is written
then the data is truncated and no warning is given by DB2.
Users might not be able to use GB18030 characters for Installation Description
------------------------------------------------------------------------------
on Windows
----------
During the installation of the server for Windows, you can specify an Installation
Description. If you try to use some GB18030 characters, they might not appear on
the input fields and might not be shown correctly on the Summary page.
MQ License, failure to determine system distribution on zLinux
--------------------------------------------------------------
On Linux systems that do not have the lsb_release command installed the following
message might be seen when running the mqlicense.sh command:
'WARNING: Unable to determine distribution and release for this system.
Check that it is supported before continuing with installation.'
If you receive this message, check that the system meets the requirements at
http://www-01.ibm.com/support/docview.wss?uid=swg27047751 and proceed with the
installation.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++ ++
++ COPYRIGHT, NOTICES AND TRADEMARKS ++
++ ++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
COPYRIGHT AND TRADEMARK INFORMATION
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this
information in other countries. Consult your local IBM representative for
information on the products and services currently available in your area. Any
reference to an IBM product, program, or service is not intended to state or
imply that only that IBM product, program, or service may be used. Any
functionally equivalent product, program, or service that does not infringe
any IBM intellectual property right may be used instead. However, it is the
user's responsibility to evaluate and verify the operation of any non-IBM
product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this information. The furnishing of this information does not give
you any license to these patents. You can send license inquiries, in writing,
to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte character set (DBCS) information,
contact the IBM Intellectual Property Department in your country or send
inquiries, in writing, to:
Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
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 states 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 information. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
information at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those
Web sites. The materials at those Web sites are not part of the materials for
this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of
the information which has been exchanged, should contact:
IBM United Kingdom Laboratories,
Mail Point 151,
Hursley Park,
Winchester,
Hampshire,
England
SO21 2JN
Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.
The licensed program described in this information and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Programming License Agreement, or any equivalent agreement
between us.
Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available
sources. IBM has not tested those products and cannot confirm the accuracy
of performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products. This information includes examples of data and
reports used in daily business operations. To illustrate them as completely
as possible, the examples include the names of individuals, companies, brands,
and products. All of these names are fictitious and any similarity to the names
and addresses used by an actual business enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which
illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing
application programs conforming to the application programming interface for
the operating platform for which the sample programs are written. These
examples have not been thoroughly tested under all conditions. IBM, therefore,
cannot guarantee or imply reliability, serviceability, or function of these
programs. You may copy, modify, and distribute these sample programs in any
form without payment to IBM for the purposes of developing, using, marketing,
or distributing application programs conforming to IBM's application
programming interfaces.
The following terms are trademarks of International Business Machines
Corporation in the United States, other countries, or both:
AIX, IBM, WebSphere, z/OS
Windows is a trademark 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 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.
For more information, see http://www.ibm.com/legal/copytrade.shtml