Deciding whether to share non-application queues

Use this information when considering sharing non-application queues.

Initiation queues

If you define a shared initiation queue, we do not need to have a trigger monitor running on every queue manager in the queue sharing group, as long as there is at least one trigger monitor running. (We can also use a shared initiation queue even if there is a trigger monitor running on each queue manager in the queue sharing group.)

If we have a shared application queue and use the trigger type of EVERY (or a trigger type of FIRST with a small trigger interval, which behaves like a trigger type of EVERY) your initiation queue must always be a shared queue. For more information about when to use a shared initiation queue, see Table 1.

SYSTEM.* queues

We can define the SYSTEM.ADMIN.* queues used to hold event messages as shared queues. This can be useful to check load balancing if an exception occurs. Each event message created by IBM MQ contains a correlation identifier indicating which queue manager produced it.

We must define the SYSTEM.QSG.* queues used for shared channels and intra-group queuing as shared queues.

We can also change the definitions of the SYSTEM.DEFAULT.LOCAL.QUEUE to be shared, or define your own default shared queue definition. This is described in the section Defining system objects in the Plan on z/OS .

We cannot define any other SYSTEM.* queues as shared queues.

Parent topic: Application programming with shared queues