What's changed in IBM MQ 9.1.0 Fix Pack 5

Change to authorities needed for XMS .NET to query the BackoutThreshold and BackoutRequeueQName of a cluster queue

From IBM MQ 9.1.0 Fix Pack 5, the XMS .NET client has been updated so that only inquire access is required to query the BackoutThreshold and BackoutRequeueQName of a cluster queue. For more information, see Open options for cluster queues in Poison messages in XMS.

Queue file size limit

From IBM MQ 9.1.0 Fix Pack 5, the queue manager limits the maximum queue file size to 2 TB by default.

Update to IBM MQ AMQP service

From IBM MQ 9.1.0 Fix Pack 5, the IBM MQ AMQP service has been updated such that when the SSLPEER attribute is set and the SSLCAUTH attribute is set to REQUIRED, the "distinguished name" of the client certificate is checked with the SSLPEER attribute.

For more information, see Creating and using AMQP channels.

Change to exception messages for failed managed transfer requests that require a new directory to be created on an SFTP file server

Managed File Transfer protocol bridge agents use the third-party JSch library to communicate with file servers using the SFTP protocol. If the protocol bridge agent attempts to transfer a file into a directory that does not exist on a file server and JSch is unable to perform the requested SFTP operation to create that directory, because the user that the protocol bridge agent logs into the file server with does not have permission to do so, JSch throws an exception back to the protocol bridge agent. The protocol bridge agent then marks the managed transfer as "Failed" and generates a supplementary message.

BFGTR0072E:  The transfer failed to complete due to the exception: 
BFGBR0209E: Bridge agent was unable to create directory directory name

Change to default trace name for IBM MQ classes for Java and IBM MQ classes for JMS

For more information, see the subtopics of Tracing IBM MQ classes for Java applications and Tracing IBM MQ classes for JMS applications.

Change to inquiries used by dmpmqcfg command

From IBM MQ 9.1.0 Fix Pack 5, the inquiries used by the dmpmqcfg command inquire only QSGDISP(QMGR) definitions by default. You can inquire additional definitions by using the environment variable AMQ_DMPMQCFG_QSGDISP_DEFAULT. For more information, see dmpmqcfg.

Case-insensitive matching of usernames in the CLNTUSER and USERLIST attributes

Some LDAP schemas are implemented such that the short username for the connection comes from a field that is case-sensitive for lookups (configured this way in the LDAP schema). Before IBM MQ 9.1.0 Fix Pack 4, the behavior of the queue manager on Linux and Unix platforms was to fold short usernames from their original case returned by LDAP, to be all lowercase. In V9.1.0.4, in situations where LDAP is the definitive source of user information, APAR IT29065 changed this behavior and kept short usernames in their original case as returned by LDAP. However, this change affected the operation of the CHLAUTH rules of TYPE(USERMAP) and TYPE(BLOCKUSER). This is described in more detail in What's changed in IBM MQ 9.1.0 Fix Pack 4.

In V9.1.0.5, APAR IT31578 allows usernames in CHLAUTH rules to be matched case-insensitively.

To enable the new behavior, add ChlauthIgnoreUserCase=Y in the Channels stanza of the qm.ini file. See usage details for ChlauthIgnoreUserCase in Channels stanza of the qm.ini file. If there is no Channels stanza, you will have to create one.

  setmqini -m YOUR-QMNAME -s Channels -k ChlauthIgnoreUserCase -v Y

New environment variable AMQ_NO_BAD_COMMS_DATA_FDCS

From IBM MQ 9.1.0 Fix Pack 5, you can use the AMQ_NO_BAD_COMMS_DATA_FDCS environment variable to suppress the capture of FFSTs when reporting AMQ9207E error messages on initial communications flows. For more information, see Environment variables descriptions.