See information about the latest product version
Using WebSphere MQ shared queues for input and output (z/OS)
On z/OS® systems, you can define WebSphere® MQ shared queues as input and output queues for message flows. You might need to serialize access to those messages.
Shared queues are available only on z/OS. Use the WebSphere MQ for z/OS product facilities to define these queues and specify that they are shared.
You cannot use shared queues for broker component queues such as the SYSTEM.BROKER.CONTROL.QUEUE.
If you use shared queues, you can provide failover support between different images running WebSphere Message Broker on a sysplex.
Some messaging transactions depend on the exact sequence of messages from a queue, and for that sequence to be maintained in the event of a failure of the queue manager. In these instances, you must serialize the access to those messages.
Serialization of messages is achieved by using specialized connection options, and a unique connection token. This connection token is used when the application that empties the messages from a queue issues a connect call to the WebSphere MQ queue manager that owns that queue.
For example, WebSphere Message Broker can use this feature when multiple brokers, with multiple execution groups, are each running message flows that empty from a shared input queue. If one broker queue manager fails, the message flow can be started automatically on another broker. The transactional integrity and original sequencing of the messages on the shared queue are maintained.
To configure shared input queues and define serialization tokens for message flows, follow the instructions in Serialization token - user tasks on z/OS.
For more information, see the z/OS Concepts and Planning section of the WebSphere MQ Version 7 Information Center online.