WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

WebSphere MQ planning for z/OS

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

You are required to have a separate WebSphere® MQ queue manager for each broker.

All WebSphere Message Broker for z/OS system queues are defined during customization.

Your queue manager must have a dead-letter queue. Check that this queue exists 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:
+cpf DIS STGCLASS(...)
to check the STGCLASS value is valid. If the queue manager does not have a valid dead-letter queue, you must define one.

Creating and deleting components on z/OS requires the command server on the WebSphere MQ queue manager to be started. This component is normally started automatically (refer to the see the z/OS System Administration Guide section of the WebSphere MQ Version 7 Information Center online for more details).

The command server requires a reply-to queue based on SYSTEM.COMMAND.REPLY.MODEL; by default, this model queue is defined as permanent dynamic. However, if you leave the queue defined in this way, each time you run a create or delete component command these reply-to queues remain defined to the queue manager. To avoid these queues persisting, you can set the SYSTEM.COMMAND.REPLY.MODEL queue as temporary dynamic.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:46:59


Task topicTask topic | Version 8.0.0.7 | ae22140_