Hi, For the first part, no, MQ can't distribute the workload, but CICSPLEX can. The trigger message gets picked up by whichever CKTI instance MQGETs it first, which in turn initiates a CICS transaction. CICSPLEX will then schedule the CICS transaction to a CICS system, according to its configuration.
The second: not as such, but to an equivalent outcome - If one CICS system is dead, only the other system's CKTI is active, so it gets the trigger message. All the above assume that both CICS systems' CKTI's monitor the same MQ initiation queue, and that the MQ and CICS systems are hosted by the same Sysplex member. To get one stage smarter, if your systems are Sysplex'ed, you could consider sharing the initiation and application queue. In this case, a message could be serviced by any CICS system in the plex. However, only consider this after thorough analysis of volumes, message length etc., so as to not break your coupling facility. Alan -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of MQA Sent: 05 October 2004 18:12 To: [EMAIL PROTECTED] Subject: MQ Trigger Monitor - Load Balancing? Dear MQA, We are studying on sharing of a single queue manager by multiple CICS regions. If we use CICS trigger monitor (i.e. CTKI), can the trigger monitor distribute workload equally among the two CICS regions? If otherwise, which component (MQ, CICS or else) can govern the workload distribution. Besides, if one of the CICS regions fails, can all the incoming messages be distributed to the remaining one for processing. TIA. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
