What's changed in IBM MQ 9.3.0 Fix Pack 30

Addition of a toString() method to the TransferExitResult class to output the attributes of the current object

[CANCEL_TRANSFER, FileFilterExit: NullPointerException]

For more information, see FileTransferResult.java interface.

Disabled CipherSuites in MQIPT

From IBM MQ 9.3.0 Fix Pack 30, SSL_ECDH CipherSuites are disabled by default in IBM MQ Internet Pass-Thru (MQIPT). For more information about the CipherSuites that MQIPT supports, see CipherSuites supported by MQIPT.

Performance monitoring enhancements

From IBM MQ 9.3.0 Fix Pack 30, you can use the mqperfck command to generate an HTML report containing performance metrics for specified queues or channels over a set time period. The report shows key system and queue manager metrics such as CPU load and IO rate, as well as metrics for the object(s) under observation such as lock contention, MQI counts, selector and match-option mismatches, and network time. The report allows customers and IBM Support to review and compare workload between normal and problematic time periods or performant and non-performant environments. It is intended to gain insight into workload patterns during times of performance sensitivity without the need to capture IBM MQ trace. For more information, see mqperfck (MQ performance check) and Metrics published on the system topics.

You can suppress the publication of the new statistics and their metadata by setting the AMQ_NO_MQPERFCK_STATS environment variable to any value before starting the queue manager.

Changes to operating system authentication for the IBM MQ Console and REST API

To resolve issues with only the user primary group being reported when verifying group membership for access or authorisation, from IBM MQ 9.3.0 Fix Pack 30, the IBM MQ Console and REST API allow operating system authentication to be done in a similar way to the queue manager. To enable this behavior, you must set the MQS_GETGROUPLIST_API environment variable before starting the mqweb server hosting the IBM MQ Console.

For more information, see Solving certain group membership problems on Linux®.

Changes to allow IBM MQ Java client properties com.ibm.mq.cfg.TCP.ClntRcvBuffSize and com.ibm.mq.cfg.TCP.ClntSndBuffSize to be set to zero

From IBM MQ 9.3.0 Fix Pack 30, if the value of either the com.ibm.mq.cfg.TCP.ClntRcvBuffSize or the com.ibm.mq.cfg.TCP.ClntSndBuffSize property is set as zero for an IBM MQ Java client, the Java Message Queuing Interface (JMQI) uses the buffer size provided by the network layer. This resolves a previous issue where setting the properties to zero would incorrectly result in the JMQI using TCP/IP send and/or receive buffers of size 32K when communicating with a queue manager. For more information, see TCP stanza of the client configuration file.

Changes to the IBM MQ Bridge to Salesforce

From IBM MQ 9.3.0 Fix Pack 30, the IBM MQ Bridge to Salesforce has been updated to use Eclipse Jetty 12 and an IBM Semeru Runtime 21. The JRE is included as part of the MQSeriesSFBridge rpm, and can only be used to run the IBM MQ Bridge to Salesforce. Using it to run other applications is not supported.

If the IBM MQ Bridge to Salesforce was previously configured to use one of these to create a secure TLS connection to IBM MQ, it will need to be reconfigured to use a different CipherSuite. For more information about CipherSuites, see TLS CipherSpecs and CipherSuites in IBM MQ classes for JMS.

New DNSResolutionOrder attribute of TCP stanza

From IBM MQ 9.3.0 Fix Pack 30, the DNSResolutionOrder attribute specifies the order in which IBM MQ looks up host names in mixed IPv6 and IPv4 environments. If the AMQ_NO_IPV6 environment variable is set, IBM MQ acts as if DNSResolutionOrder=IPV4 is set, no matter what value is configured.

For more information, see TCP stanza of the qm.ini file and TCP stanza of the client configuration file.