Starting the CICS-MQ bridge
If you are using a CICS®-MQ monitor to
control the bridge and if the MQMONITOR resource has been configured correctly, the bridge
automatically starts when the connection to the MQ queue manager is established. Using an MQMONITOR
resource is the recommended method of controlling the bridge. You can also manually start the bridge
using the CKBR transaction.

Before you begin
- If you want to use a CICS-MQ monitor to control the bridge, you must define and install an MQMONITOR resource for controlling the MQ bridge. For detailed instructions, see Setting up a MQMONITOR resource for the CICS-WebSphere MQ bridge.
- In addition, if security checking is active (that is, the SEC system initialization parameter is set to YES), ensure that the user ID associated with the transaction that attempts to set the MQ monitor state to started is a surrogate of the user ID defined in MONUSERID and is authorized to start transactions associated with the MONUSERID. In the case of setting the MQ monitor state through a CICSPlex SM API interface such as the CICS Explorer, the user ID to be associated with the MQ monitor transaction is either the region user ID or the PLTPIUSR user ID (if specified).

Procedure
What to do next
If you are running multiple bridge monitors sharing a request queue, you can start one of the monitors by putting a message onto the bridge request queue. However, for private local queues, only one trigger message is produced, so the bridge monitor starts on only one CICS region. To start further bridge monitors, you should therefore consider alternative methods, such as using a program in the CICS startup PLT processing to start the transaction with the required parameters, or using automation products to start the transaction. If you shut down the bridge by altering the request queue attributes, remember to reset GET(ENABLED) after the bridge has shut down.