What's changed in IBM MQ 9.3.2
Before upgrading your queue managers to the latest product version, review these changes to functions and resources since IBM® MQ 9.3.1 and decide whether you must plan to make changes to existing applications, scripts, and procedures before starting to migrate your systems.
- Installation and migration
- Administration
- Containers
Migration considerations relating to IBM MQ Bridge to blockchain removal
For Continuous Delivery, the IBM MQ Bridge to blockchain is removed from the product at IBM MQ 9.3.2.
On Linux® for x86-64 only, if you are migrating on an installation where the IBM MQ Bridge to blockchain is present, you must remove it before you upgrade to IBM MQ 9.3.2 or later.
New OAMLdapResponseWarningTime parameter in TuningParameters stanza of qm.ini
If a connection to an LDAP server took longer than the threshold number of seconds specified by the OAMLdapResponseWarningTime parameter, then an AMQ5544W message will be written to the error log. For more information, see TuningParameters stanza of the qm.ini file.
Changed return code for endmqm
If an endmqm command was issued to a queue manager that was in the process of starting up, the generic code 71 'unexpected error' was returned. An attempt to end a queue manager that is starting up now returns the code 4 ' Queue manager is being started'. See endmqm.
Changed environment variables for the IBM MQ Advanced for Developers container image
- MQ_LOGGING_CONSOLE_SOURCE
- MQ_LOGGING_CONSOLE_FORMAT (which supersedes LOG_FORMAT)
- MQ_LOGGING_CONSOLE_EXCLUDE_ID
For use in containers, a certificate must have a unique Subject Distinguished Name
Queue manager certificates with the same Subject Distinguished Name (DN) as the issuer (CA) certificate are not supported for use with IBM MQ containers. The product now checks for this condition, and stops it from occurring.