[V8.0.0.11 Dec 2018]

What's new and changed in Version 8.0.0, Fix Pack 11

Changes to functions and resources in IBM® MQ 8.0.0, Fix Pack 11 are described in this section.

[Windows]

Addition of Microsoft Visual Studio 2013 C/C++ runtimes on Windows

From IBM MQ 8.0.0, Fix Pack 11, some elements of IBM MQ require the Microsoft Visual Studio 2013 C/C++ (VS2013) runtimes. These runtimes are installed by any fresh installation of IBM MQ 8.0.0, Fix Pack 11 or later.

If the VS2013 runtimes are not present on the machine, when you install a fresh client or server, upgrade an earlier release to these levels, or apply a fix pack. In most cases, this process requires no user action but, should you encounter an installation failure when applying the server fix pack, there is an environment variable that you might need to specify so that you can install the runtimes manually. For more information, see Installation of Microsoft Visual Studio 2013 C/C++ runtimes in a server fix pack.

Behavioral changes to IBM MQ client connections

From Version 8.0.0, Fix Pack 11, there are a number of minor changes to the way in which a client channel connects to a queue manager. The changes are most specifically in the interactions between security exits and the application of CHLAUTH mapping rules. For more information, see the technote Behavioral changes to MQ client connections introduced by APAR IT25839.

Updates for messages produced during backout queue and dead letter queue processing for IBM MQ classes for JMS

From IBM MQ 8.0.0, Fix Pack 11, when an attempt by the IBM MQ classes for JMS to re-queue a message either to a specified backout queue, or to the queue manager's dead-letter queue fails, a message is written to the log indicating the message ID of the message, the name of the backout or dead-letter queue the message could not be moved to, and the exception or error that prevented the move.
  • A failure to move a message to the backout queue results in the following log message:
    JMSWMQ1120 = Message "message ID", could not be moved to backout queue 
"backout queue name" for reason "exception or error", it will be  
moved to the dead letter queue or discarded.
  • A failure to move a message to the dead-letter queue results in the following log message:
    JMSWMQ0035 = Message "message ID", could not be moved to dead letter queue 
"dead-letter queue name" because of exception "exception or  error", 
it will be returned to the source queue.
  • If there is an exception listener registered on a consumer which tries and fails to re-queue a message to the dead-letter queue, as well as the log message being written, an exception containing the exception message text is sent to this exception listener:
    JMSWMQ1079: Unable to write a message to dead letter queue.
For more information, see JMS Exception Messages.