[V9.1.5 Apr 2020][z/OS]

New IBM MQ 9.1.5 features for z/OS

On the z/OS® platform, IBM® MQ 9.1.5 delivers a number of new features that are available with base and advanced entitlement.

Support for data set encryption

From IBM MQ 9.1.5, IBM MQ for z/OS introduces support for the use of z/OS data set encryption, for shared message data sets .

This, together with the support for encrypting page sets and logs that was added in IBM MQ 9.1.4, means that all data stored in IBM MQ for z/OS data sets can now be protected on disk.

For more information, see Confidentiality for data at rest on IBM MQ for z/OS with data set encryption

Enhanced protection of stored passwords in MQIPT

From IBM MQ 9.1.5, all passwords that are stored in the IBM MQ Internet Pass-Thru (MQIPT) configuration can be protected by encrypting the passwords using the mqiptPW command. IBM MQ 9.1.5 also introduces a new, more secure, protection method for passwords that are stored for use by MQIPT, and the ability for you to specify an encryption key that is used to encrypt and decrypt stored passwords.

For more information, see Encrypting stored passwords.

Publish messages to topics with the messaging REST API

From IBM MQ 9.1.5, you can publish messages to a specified topic by using the messaging REST API. You can use the /messaging/qmgr/{qmgrName}/topic/{topicString}/message resource with an HTTP POST to publish a message to the topic.

For more information, see POST /messaging/qmgr/{qmgrName}/topic/{topicString}/message.

Version 2 of the REST API

IBM MQ 9.1.5 introduces version 2 of the REST API. This version increase applies to the administrative REST API, messaging REST API, and MFT REST API.

This version increase changes the resource URL that is used for the REST API. The URL prefix for the resource URLs at version 2 is the following URL:
https://host:port/ibmmq/rest/v2/

You can continue to use the version 1 URL for existing applications. Most REST API resources are available in both versions. However, new REST API resources are available only with the version 2 URL. For example, the new publish URL in the messaging REST API is available only with the version 2 URL.

The following REST API resources are not available in version 2:
  • GET subscription
  • GET channel
  • POST queue
  • PATCH queue
  • GET queue
  • DELETE queue
You can use the MQSC resource URL as an alternative to using these version 1 REST API resources.