| Author |
Message
|
| vinodh_niit |
 Posted: Thu May 30, 2002 12:26 am Post subject: MQ vs CICS |
 |
|
Apprentice
Joined: 22 May 2002
Posts: 36
Location: chennai
|
hi all
For a distributed environment with Request-Reply mode, which is preferred CICS or MQ. <The GUI based system places a request to host & on reply from host displays the result>.
any plz help me in comparing this.
thanx in advance.
Rgds
vinodh
_________________
vinodh
ssg-mq ream |
|
| Back to top |
|
 |
| Cliff |
| Posted: Thu May 30, 2002 3:54 am Post subject: |
|
|
Centurion
Joined: 27 Jun 2001
Posts: 145
Location: Wiltshire
|
Vinodh,
CICS and MQ are two totally different products, doing entirely different jobs, so it's not really an either/or thing.
What many people do however, is to use the MQSeries triggering mechanism to start a CICS transaction when a message arrives (from a erquesting application) on a queue. The CICS txn then (typically) interrogates a database and sends a reply message to the reply-to queue specified on the incoming message. The requesting application may be waiting for the reply to arrive, or it could be triggered by the arrival of the reply message.
HTH - Cliff |
|
| Back to top |
|
|
| vinodh_niit |
| Posted: Thu May 30, 2002 8:14 pm Post subject: MQ vs CICS |
|
|
Apprentice
Joined: 22 May 2002
Posts: 36
Location: chennai
|
Hi cliff
Thanks a lot for your reply. I will try to get some more info on this.
Thanks & rgds
vinodh
_________________
vinodh
ssg-mq ream |
|
| Back to top |
|
|
| zpat |
| Posted: Fri May 31, 2002 12:13 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
It's more efficient NOT to trigger, but have a long running CICS transaction with an outstanding MQGET with WAIT on the request queue.
We actually then invoke the target CICS transaction passing data in the commarea and then repeat the MQGET with WAIT for the next request.
This avoids the additional overhead of an MQPUT and MQGET of the trigger message which would otherwise occur. Triggering is better used for low-volume intermittent applications such as a hourly or daily transaction, and not for busy client/server applications. |
|
| Back to top |
|
|
| Cliff |
| Posted: Fri May 31, 2002 12:58 am Post subject: |
|
|
Centurion
Joined: 27 Jun 2001
Posts: 145
Location: Wiltshire
|
Well, that's a perfectly valid approach but the triggered approach also works well in client/server type of app especially if the triggered CICS txn has a sensible GET WAIT period, so tends to service messages as they arrive. Another consideration is whether you want 40 different request types serviced from a single input queue (what if the transactions do big slow DB2 SELECTS?) and whether the 32K commarea size is big enough for your data passing requirements.
I guess you pays your money and you takes your choice ...
Cheers - Cliff |
|
| Back to top |
|
|
|
|
