Naming conventions for WebSphere Message Broker for z/OS

Decide upon a naming convention for your WebSphere Message Broker components to make customizing, operating, and administering easier.

Each broker requires its own queue manager. Base your broker name on the queue manager name. For example, append BRK to the queue manager name of MQP1, to give MQP1BRK. This naming convention has the following advantages:
  • It is easy to associate the broker with the queue manager, because they both begin with the same characters.
  • The started task name has the same name as the broker.
  • You can have the broker name as part of the data set name, which makes it easier to administer.
Similarly, base the Configuration Manager and User Name Server name on the queue manager name. For example, append CMGR or UNS to the queue manager name.
Using this convention, you might have the following component names for a queue manager MQP1.
  • A broker called MQP1BRK with:
    • A started task name of MQP1BRK.
    • A started task user ID of MQP1BRK.
    • A PDSE containing definitions called hlq.MQP1BRK.xxx.
    • A UNIX System Services directory structure like /xxx/yyy/MQP1BRK.
    • A DB2 group called MQP1GRP.
  • A User Name Server called MQP1UNS with:
    • A started task name of MQP1UNS.
    • A started task user ID of MQP1UNS.
    • A PDSE containing definitions called hlq.MQP1UNS.xxx.
    • A UNIX System Services directory structure like /xxx/yyy/MQP1UNS.
  • A Configuration Manager called MQP1CMGR with:
    • A started task name of MQP1CMGR.
    • A started task user ID of MQP1CMGR.
    • A PDSE containing definitions called hlq.MQP1CMGR.xxx.
    • A UNIX System Services directory structure like /xxx/yyy/MQP1CMGR.
Plan for expansion by selecting names that allow growth.

If your broker name is in uppercase, ensure the broker name is also in uppercase in the workbench.

Related concepts
Brokers
User Name Server
Related tasks
Creating a broker on z/OS