What's changed in IBM MQ 9.1.1

Change to format of trace timestamps

From IBM MQ 9.1.1, the format of Windows trace timestamps has changed. See Example trace data for Windows for an example of the revised format.

New -caseno parameter for the runmqras command

The -caseno parameter is equivalent to -pmrno, except it allows a valid Salesforce case number to specified. -caseno or -pmrno are both optional parameters, but it is not permitted to supply both together. For more information, see runmqras (collect IBM MQ diagnostic information).

New IGNSTATE parameter for runmqsc START and STOP commands

From IBM MQ 9.1.1, it is possible to specify what the return code from runmqsc START and STOP commands should be in the case where the object being started or stopped is already in the desired state. This makes it easier to write runmqsc scripts that give the same result when they are executed multiple times. The object types that IGNSTATE applies to are: CHANNEL, LISTENER, and SERVICE.

For more information about how you use this attribute, see START CHANNEL and STOP CHANNEL.

Behavioral changes to IBM MQ client connections

From IBM MQ 9.1.1, 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.

For more information, see Interaction of CHLAUTH and CONNAUTH and Resolving CHLAUTH access issues.

Removal of 12 character limit on MCAUSER user ID for AMQP channels on Windows

AMQP channels have an MCAUSER attribute, which you can use to set the IBM MQ user ID that all connections to that channel are authorized under (see MCAUSER setting on a channel). On Windows, before IBM MQ 9.1.1, the MCAUSER user ID setting is only supported for user IDs up to 12 characters in length. From IBM MQ 9.1.1, the 12 character limit is removed.

IBM MQ C redistributable client packages extended to include elements required to build applications

From IBM MQ 9.1.1, the IBM MQ C redistributable client packages include the elements required to build the application, that is the header files and copybooks. This simplifies application development process as it means that you no longer need to do a full installation of IBM MQ components in order to get started with developing your application. However, the sample source code is still not included in these packages.

The genmqpkg command that you can use to build a tailor made package with the subset of files needed for your application is extended so that the repackaging can now be done programmatically as well as interactively. This means that you can embed the rebuilding of the redistributable client into an automated development pipeline for onwards processing.

For more information, see Redistributable clients and Installation considerations for redistributable clients.

Reduction in the number of default objects

From IBM MQ 9.1.1 the number of default objects in Continuous Delivery releases has been reduced by one, from 84 to 83. This is because of the removal of the SYSTEM.MESSAGE.ASSOCIATION.QUEUE, previously used by the MQ Light web console. The console is no longer available in IBM MQ Continuous Delivery.

Replacement for Product Insights

Product Insights has been replaced by a metering service in IBM Cloud® Private.

For more information, see Configuring IBM MQ for use with the metering service in IBM Cloud Private.

Preventing accidental migration from an LTS release to a CD release

If the queue manager detects that you are migrating from an LTS release, such as IBM MQ 9.1.0, to a CD release, such as IBM MQ 9.1.1, a write to operator reply message is output to confirm that you want to migrate. If you do not respond to this message the queue manager does not start up.

See message CSQY041D for more information.

Reduction in the number of XMS.NET dynamic link libraries

From IBM MQ 9.1.1, the number of XMS.NET dynamic link libraries has been significantly reduced, to a total of five.

Changes to connection authentication for Managed File Transfer agents and logger

From IBM MQ 9.1.1, MQCSP authentication mode is enabled by default for connection authentication for the MFT agents and logger. This applies to connection authentication of the IBM MQ Explorer MFT Plugin connecting with a coordination queue manager or command queue manager, and connection authentication for a Managed File Transfer agent connecting with a coordination queue manager or command queue manager. For more information, see Enabling connection authentication for MFT and MFT credentials file format.