Start MQ Pub/Sub Broker (STRMQMBRK)

Where allowed to run: All environments (*ALL)
Threadsafe: Yes

The Start IBM® MQ broker (STRMQMBRK) command starts a broker for a specified queue manager.

Parameters

Keyword	Description	Choices	Notes
MQMNAME	Message Queue Manager name	Character value	Required, Positional 1
PARENTMQM	Parent Message Queue Manager	Character value	Optional, Positional 2

Message Queue Manager name (MQMNAME)

Specifies the name of the queue manager.

queue-manager-name: Specify the name of the queue manager.

Parent Message Queue Manager (PARENTMQM)

Specifies the name of the queue manager that provides the parent broker function. Before you can add a broker to the network, channels in both directions must exist between the queue manager that hosts the new broker, and the queue manager that hosts the parent.

On restart, this parameter is optional. If present, it must be the same as it was when previously specified. If this is the root-node broker, the queue manager specified becomes its parent. You cannot specify the name of the parent broker when you use triggering to start a broker.

After a parent has been specified, it is only possible to change parentage in exceptional circumstances in conjunction with the CLRMQMBRK command. By changing a root node to become the child of an existing broker, two hierarchies can be joined. This causes subscriptions to be propagated across the two hierarchies, which now become one. After that, publications start to flow across them. To ensure predictable results, it is essential that you quiesce all publishing applications at this time.

If the changed broker detects a hierarchical error (that is, if the new parent is found also to be a descendant), it immediately shuts down. The administrator must then use CLRMQMBRK at both the changed broker and the new, false parent to restore the previous status. A hierarchical error is detected by propagating a message up the hierarchy, which can complete only when the relevant brokers and links are available.