Using a common queue for activity reports

Depending on the queue manager attribute, ACTIVREC, activity reports are delivered to either:

In some cases a system administrator might prefer for activity information not to be returned the reply-to queue specified in the message. If this is the case then activity reports can be delivered to the local system queue. If a number of queue managers in a queue manager network are set this way, then it can be time consuming determining the locations of the activity reports related to a specific message. An alternative is to use a common queue on a single node.

A single node is a queue manager that hosts a common queue. All the queue managers in a queue manager network can deliver activity reports to this common queue. For an example of this configuration, see Figure 2. The benefit of using a common queue is that queue managers do not have to deliver activity reports to the reply-to queue specified in a message, and when determining the locations of the activity reports related to a message only one queue need be queried.

To set up a common queue, do the following:

  1. Select, or define, a queue manager as the single node.

  2. On the single node select, or define, a queue for use as the common queue.

  3. On all queue managers where activity reports are to be delivered to the common queue, redefine the local system queue SYSTEM.ADMIN.ACTIVITY.QUEUE as a remote queue definition specifying the following:

    • The name of the single node as the remote queue manager name.

    • The name of the common queue as the remote queue name.