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

Enabling dynamic tracing of LDAP client library code shipped with IBM MQ

Before Version 8.0.0, Fix Pack 14, it was not possible to switch the LDAP client trace on and off without also stopping or starting the queue manager.

From Version 8.0.0, Fix Pack 14, you can switch LDAP client trace on with the strmqtrc command and off with the endmqtrc command without needing to stop or start the queue manager. To enable this behavior, it is also necessary to set an environment variable AMQ_LDAP_TRACE to a non-null value. For more information, see Enabling dynamic tracing of LDAP client library code.

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

From Version 8.0.0, Fix Pack 14, 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.

Change to inquiries used by dmpmqcfg command

From Version 8.0.0, Fix Pack 14, 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.

New environment variable AMQ_NO_BAD_COMMS_DATA_FDCS

From Version 8.0.0, Fix Pack 14, 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.