To start the bridge, run the CICS(R) bridge transaction. The default transaction is CKBR but you might have defined a different one; it has five optional parameters:
Remember that names of objects within WebSphere MQ are case-sensitive.
The default wait time is unlimited.
You are recommended to specify a wait time. If you do not specify a wait time, the CICS bridge might inhibit CICS or queue manager shut down.
Start the CKBR task running by using one of the following methods:
CKBR Q=<queue name>,AUTH=<auth option>,WAIT=nnn,MSG=<msg option>,PASSTKTA=<applid>
For example:
CKBR Q=MyQueue,AUTH=IDENTIFY,WAIT=30,MSG=LOG,PASSTKTA=APP1
You can have a program which runs as part of CICS PLTPI processing which issues this command, and specify the userid which the bridge monitor transaction is to run under.
CSQCBR00 is a long running task and this program will only return when the bridge stops.
If you are running multiple bridge monitors sharing a 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 will be produced, so the bridge monitor will only start on one CICS region. You should therefore consider alternative ways of starting the bridge monitors, for example 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.
The level of security you want to use influences how you start the monitor task. See the WebSphere MQ for z/OS System Setup Guide for information on the security options available to you.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csq846f |