Creating the broker queues

This is part of the larger task of creating a broker on z/OS.

Before you start

Before starting this step, you must have completed Creating the broker database

If your queue manager has security enabled, you need to set up access to the queue manager and to the queues.

  • Allow the broker-started task user ID to connect to the queue manager. For example, for the queue manager MQP1, use the RACF command:
    PERMIT MQP1.BATCH  CLASS(MQCONN) ID(userid) access(READ) 
  • Protect the broker internal queues. For example, for the queue manager MPQ1, use the following RACF commands:
    RDEFINE MQQUEUE MQP1.SYSTEM.BROKER.** UACC(NONE)
    PERMIT MQP1.SYSTEM.BROKER.** CLASS(MQQUEUE) ID(WMQIGRP) ACCESS(UPDATE)
    where WMQIGRP is the user ID or group to which you are giving the permission.
  • Publish/Subscribe applications need to be able to PUT to SYSTEM.BROKER.CONTROL.QUEUE. For example, use the RACF commands:
    RDEFINE MQQUEUE MQP1.SYSTEM.BROKER.CONTROL.QUEUE UACC(NONE)
    PERMIT MQP1.SYSTEM.BROKER.CONTROL.QUEUE CLASS(MQQUEUE) ID(psusers) ACCESS(UPDATE)
    where psusers is the name, user ID, or group containing user IDs to be given access to the queue.

Ensure that the WebSphere MQ queue manager is running before you continue with this step. Submit the following job from your broker PDSE to define the WebSphere MQ objects needed by the broker. Should you have problems, submit BIP#MQ01 to delete WebSphere MQ objects, but ensure that you have the stopped the broker before submitting BIP#MQ01.

WebSphere MQ job Description
BIP$MQ01 Creates the broker queues

When this job has run successfully, you do not need to submit it again during a subsequent recustomization, unless you are directed to do so by IBM.

Related concepts
Broker
Broker domain
Publish/Subscribe

Related tasks
Creating a broker on z/OS
Creating the broker database
Defining the broker started task user ID