[V9.1.0 Jul 2018][z/OS]

z/OS changes for IBM MQ 9.1.0

A number of commands have changed at IBM® MQ 9.1.0.

Db2 Universal Table Spaces

IBM MQ 9.1.0 provides additional samples, demonstrating how a queue sharing group can be set up to use Universal Table Spaces (UTS) in Db2® 12.

For more information, see Planning your Db2 environment.

Improvements to z/OSMF

From IBM MQ 9.1.0, the IBM z/OS® Management Facility (z/OSMF) workflows for provisioning IBM MQ resources have been updated to take advantage of newer Cloud Provisioning capabilities that are being made available in z/OSMF V2.2.

Additionally, the workflow to provision local queues has been enhanced to include actions to display selected attributes of a queue, and to browse or destructively get a message from a queue.

For more information on the improvements to z/OSMF, see Using IBM z/OSMF to automate IBM MQ.

Changes in z/OS product identifier (PID) recording

IBM MQ 9.1.0 introduces an improved method of including the correct PID for each of the following components:
  • Base IBM MQ
  • Advanced Message Security
  • Managed File Transfer
  • IBM MQ for z/OS Value Unit Edition (VUE)
  • IBM MQ Advanced for z/OS Value Unit Edition

For more information, see Product usage recording with IBM MQ for z/OS products.

Display queue manager utility on z/OS

IBM MQ 9.1.0 provides the CSQUDSPM utility on z/OS, which displays information about queue managers, and provides the equivalent function to dspmq on Multiplatforms.

Cluster workload exits for z/OS

From IBM MQ 9.1.0, cluster workload exits run in the channel initiator address space, instead of the queue manager address space. If you have a cluster workload exit, you should remove the CSQXLIB DD statement from your queue manager started task procedure, and add the dataset containing the cluster workload exit to the CSQXLIB concatenation on your channel initiator started task procedure.

Removal of OPMODE parameter

From IBM MQ 9.1.0, the OPMODE parameter in the CSQ6SYSP macro has been removed, and no longer has any effect. See OPMODE for details.

Checking that the mqweb server is correctly configured on z/OS

The information Checking that the mqweb server is correctly configured on z/OS has been moved to Troubleshooting the IBM MQ Console and REST API.