What's changed in Version 9.0.0, Fix Pack 2

IBM MQ Version 9.0.0, Fix Pack 2 includes a number of changes to functions and resources.


New constant JMS_IBM_SUBSCRIPTION_USER_DATA added to the JmsConstants interface

From Version 9.0.0, Fix Pack 2, the IBM MQ classes for JMS are updated so that when a message is consumed from a queue that contains an RFH2 header with the MQPS folder, the value associated with the Sud key, if it exists, is added as a String property to the JMS Message object returned to the IBM MQ classes for JMS application. To enable an application to retrieve this property from the message, a new constant, JMS_IBM_SUBSCRIPTION_USER_DATA, is added to the JmsConstants interface. This new property can be used with the method javax.jms.Message.getStringProperty(java.lang.String) to retrieve the subscription user data. For more information, see Retrieval of user subscription data and DEFINE SUB.


New environment variable AMQ_SSL_LDAP_SERVER_VERSION

From Version 9.0.0, Fix Pack 2, we can set the environment variable AMQ_SSL_LDAP_SERVER_VERSION to ensure that IBM MQ passes the required lightweight directory access protocol (LDAP) version, that is LDAP v2 or LDAP v3, to GSKit when a certificate is validated against a higher version of LDAP Certificate Revocation List (CRL) server. For more information, see Environment variables.


Sample configuration file for IBM MQ classes for Java

From Version 9.0.0, Fix Pack 2, a sample configuration file, mqjava.config, is supplied in the bin subdirectory of the IBM MQ classes for Java installation directory. For more information, see The IBM MQ classes for Java configuration file.


Changes to the dmpmqcfg command

From Version 9.0.0, Fix Pack 2, a command line switch -w is added to dmpmqcfg. This switch allows you increase the time, in seconds, that dmpmqcfg waits for a reply message from the command server. For more information, see dmpmqcfg.


Changes to the strmqm command

From Version 9.0.0, Fix Pack 2, the strmqm command checks the syntax of the CHANNELS and SSL stanzas in the qm.ini file before starting the queue manager fully, which makes it much easier to see what is wrong, and correct it quickly if strmqm finds that the qm.ini file contains any errors. For more information, see strmqm.


Change to handling of errors relating to corrupted character data within internal MQ command messages used by queue manager clustering component

From Version 9.0.0, Fix Pack 2, the way in which the queue manager handles errors that relate to corrupted character data within internal MQ command messages that are used by the clustering component of the queue manager is changed. The field(s) that might contain unconvertible characters are blanked out and the conversion is retried. If the conversion succeeds, the update is stored with a blank description and error messages AMQ6174 and AMQ9880 are written, to inform the administrator. If the message is still unconvertible, it is moved to the Dead Letter Queue and an error message is written.


Change to behavior of Managed File Transfer fteCleanAgent command

From Version 9.0.0, Fix Pack 2, the fteCleanAgent command has been updated so that you 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 change in behavior ensures that, by default, fteCleanAgent does not clear all in-progress and pending transfers, resource monitor definitions and scheduled transfer definitions for the agent specified.

If required, we can revert to the previous behavior of fteCleanAgent by setting the new failCleanAgentWithNoArguments property in the command.properties file to false.

For more information, see fteCleanAgent (cleans up a Managed File Transfer Agent) and The command.properties file.


Enabling MQCSP authentication in Managed File Transfer

From Version 9.0.0, Fix Pack 2, we can disable the default compatibility mode and enable MQCSP authentication for connection authentication for:

  • A Managed File Transfer agent connecting to a coordination queue manager, or command queue manager.
  • The IBM MQ Explorer MFT Plugin connecting to a coordination queue manager or command queue manager.
For more information, see Enabling MQCSP authentication mode.


New messagePublicationFormat property for Managed File Transfer installation.properties file

From Version 9.0.0, Fix Pack 2, a new property, messagePublicationFormat, is added to the installation.properties file. This property allows you to specify the message publication format used by MFT agents for their status XML messages. For more information, see The installation.properties file.


Comparison check of transfer identifier and value of groupId attribute restored for message-to-file transfers

From Version 9.0.0, Fix Pack 2, Managed File Transfer is updated to restore the comparison check, previously removed by APAR IT18213, of the transfer identifier and the value of the groupId attribute within the transfer request XML payload. If these two identifiers are equivalent, the source agent uses the identifier as a message identifier match option (as opposed to a group identifier match option) for the first MQGET attempt that is made on the input queue for the message-to-file transfer. See also Transferring data from messages to files.