[V8.0.0.12 May 2019]

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

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

Change to authorities needed for IBM MQ classes for JMS to query the BackoutThreshold and BackoutRequeueQName of a cluster queue

From Version 8.0.0, Fix Pack 12, the IBM MQ classes for JMS have been updated so that only inquire access is required to query the BackoutThreshold and BackoutRequeueQName of a cluster queue. Before Version 8.0.0, Fix Pack 12, browse and get access are also required. For more information, see Handling poison messages in IBM MQ classes for JMS.

Distributed

New environment variable AMQ_CONVEBCDICNEWLINE

Before Version 8.0.0, Fix Pack 12, the ConvEBCDICNewline attribute, which you can use to specify how IBM MQ is to convert an EBCDIC NL character into ASCII format, is available only by using the mqs.ini file. From Version 8.0.0, Fix Pack 12, you can use the AMQ_CONVEBCDICNEWLINE environment variable instead of the ConvEBCDICNewline stanza attribute, for example to provide ConvEBCDICNewline functionality on the client side in situations where the mqs.ini file cannot be used. For more information, see All queue managers and Environment variables.

[AIX]

Change to linking mechanism used in IBM MQ sample code to build Sybase XA switch files

From Version 8.0.0, Fix Pack 12, the supplied makefile has been modified to use different linking options (-bstatic -bdynamic) which accommodates the change in the format of the XA library files shipped at Sybase 15 ESD#5 and later. For more information, see Sybase configuration.

[Windows]

Changes to Windows program directory security permissions

The IBM MQ installer on Windows now sets additional permission restrictions as part of the security configuration of the MQ installation directories. The logic that does this is run at installation, upgrade, modification, and fix pack installation time.

You might find that, due to the increased security, you are unable to do certain things exactly the same way you used to do them. For example:
  • An MQ Administrator (who is not also a member of the Administrators group) can no longer edit or recompile the sample programs in the Tools subdirectory. If you wish to do this, take a copy of the directory (or the portions you are interested in) and change your copies of the build scripts to reflect the new location.

In normal use, however, you should be unaware of the change, except for the little extra time required by the installer to make the changes. During this period the message Initializing security... will be displayed. A similar short pause will occur when installing the fix pack files or applying a patch.

The update of the security writes a log (amqidsec-<Installationname>.txt) to the TEMP directory on the machine. If you see the main install failing in custom action 'iwiLaunchAmqidsec', you should consult this file.

Note: When installing the fix pack files, you must have a security group called “mqm” on the machine. This will be the case already if you have installed IBM MQ on the machine. If, however, you have a machine that only has IBM MQ fix packs on it (or you wish to install the fix pack files first, before you install IBM MQ) then you will need to create this local group.