Setting up multiple CICS-WebSphere MQ bridge monitors

If you expect a high volume of requests for CICS® applications through the CICS-WebSphere® MQ bridge, consider setting up additional bridge monitors in further CICS regions. You might also want to use additional bridge monitors to provide more granular security.

About this task

The default transaction ID for the bridge monitor is CKBR, but you can change this or define additional transaction IDs.

When you set up multiple bridge monitors, you can create a separate request queue for each bridge monitor for its sole use. The advantage of this approach is that you may give each bridge monitor different service characteristics. However, the disadvantage is that applications must know the name of the appropriate request queue to use when making requests through the CICS-WebSphere MQ bridge. For this reason, you might prefer to have several bridge monitors share the same request queue.

If you decide to use a shared request queue with several bridge monitors, ensure that you follow these requirements:

Procedure

What to do next

For problem determination with multiple CICS bridge monitors, you might have to look at all the logs of all the CICS regions to find any error messages produced by the bridge. You can use the command DISPLAY QSTATUS(queuename) TYPE(HANDLE) on each queue manager to show which CICS regions have the queue open.



multiplebridge.html | Timestamp icon Last updated: Sunday, 4 June 2017