New AIX, Linux and Windows features

On AIX®, Linux® and Windows, IBM® MQ 9.0.5 delivers a number of new features.

Improvements to error logging
Improved performance for non-transacted persistent put operations
New method for LDAP authorization
AMQP service starting by default
IBM MQ custom channel for WCF enabled for send replying messages in MQSTR format
Disaster recovery replicated data queue managers (DR RDQMs)
New queue manager attribute for identifying IBM MQ Advanced entitlement

Improvements to error logging

IBM MQ 9.0.5 introduces various improvements to the management and output of error logs. The main changes are, that you can:

Log diagnostic messages, using additional file services and syslog on UNIX platforms, as well as AMQERR01.LOG.
Use JSON for the description of the messages, as well as the existing format; see JSON format diagnostic messages.
Reformat a log into another language or style; see mqrc.

For more information, see Diagnostic message services, and QMErrorLog service.

Improved performance for non-transacted persistent put operations

From IBM MQ 9.0.5, a new tuning parameter in the qm.ini file, ImplSyncOpenOutput improves performance on put operations of persistent messages outside of syncpoint. For more information, see Implicit syncpoint and Tuning parameters.

New method for LDAP authorization

IBM MQ 9.0.5 introduces a new authorization method for users and groups in an LDAP repository.

This method adds support for LDAP configurations where group membership is indicated by an attribute in the group entry containing the short user names of all the users that belong to the group.

This new authorization method is enabled by setting AUTHORMD to SRCHGRPSN on an authentication information object with an AUTHTYPE of IDPWLDAP.

For more information, see the AUTHORMD parameter of the DEFINE AUTHINFO command.

AMQP service starting by default

From IBM MQ 9.0.5, the AMQP service is started by default, which means that:

AMQP channels can be started and stopped as soon as the queue manager is started.
The AMQP JVM will be running, and show up in ps/top/task manager as soon as a queue manager is started, but if, and only if, the MQSeriesAMQP component is installed.

For more information, see Creating and using AMQP channels.

IBM MQ custom channel for WCF enabled for send replying messages in MQSTR format

From IBM MQ 9.0.5, if you put a WCF request message onto a queue using IBM MQ Custom channel for WCF, in MQMFT_STRING (MQSTR) format, you can select to receive the reply message in the same MQMFT_STRING (MQSTR) format.

For more information, see Sending MQSTR formatted messages.

Disaster recovery replicated data queue managers (DR RDQMs)

From IBM MQ 9.0.5, you can build a disaster recovery solution based on replicated data queue managers (RDQMs).

You have a primary instance of a DR queue manager running on one server, and a secondary instance of the queue manager on another server (that acts as the recovery node). Data is replicated between the queue manager instances. If you lose your primary queue manager, you can manually make the secondary instance into the primary instance and start the queue manager, then resume work from the same place.

You can configure for synchronous replication of data between primary and secondary queue managers, or asynchronous replication.

For more information on DR RDQM, see RDQM disaster recovery.

New queue manager attribute for identifying IBM MQ Advanced entitlement

At IBM MQ 9.0.4, a new queue manager attribute was added to enable z/OS® queue managers with IBM MQ Advanced entitlement to identify themselves as Advanced queue managers. From IBM MQ 9.0.5, this capability is extended to all platforms.

For more information, see the ADVCAP attribute of the DISPLAY QMGR MQSC command, and the MQIA_ADVANCED_CAPABILITY attribute of the Inquire Queue Manager (MQCMD_INQUIRE_Q_MGR) PCFcommand.