WebSphere MQ planning

This is part of the larger task of customizing your z/OS environment.

You must have a separate WebSphere MQ queue manager for each broker and for each User Name Server (although you would typically have only one User Name Server in your environment). A broker and a User Name Server, however, can share the same queue manager. All WebSphere Business Integration Event Broker for z/OS system queues are defined during customization.

Your queue manager needs a dead-letter queue. Check this by using the WebSphere MQ command:
+cpf  DIS QMGR DEADQ
Check that the queue exists by using the command:
 +cpf DIS QL(name) STGCLASS
Then use the command:
+cpf DIS STGCLASS(...)
to check that the STGCLASS value is valid. If the queue manager does not have a valid dead-letter queue, you must define one.

Set up your channel initiator to use distributed queuing. You need channels between the z/OS queue manager and the queue manager of your Configuration Manager on Windows. If you are using Publish/Subscribe security, you also need access to the queue manager used by the User Name Server, which can be on z/OS or on another platform. You should be able to successfully start channels between the various queue managers before you can test that the broker is working. When configuring the transmission queues between the brokers on z/OS and the Configuration Manager on Windows, ensure that you set the maximum message size of the queues to 100 MB. This allows large reply messages concerning deployment to be returned to the Configuration Manager. See Creating a domain connection for details.

Related concepts
Broker
User Name Server
Related tasks
Customizing the z/OS environment
Creating a domain connection