| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ CICS Adapter program |
« View previous topic :: View next topic » |
| Author |
Message
|
| babu_murugesan |
 Posted: Sun Nov 12, 2006 2:09 am Post subject: MQ CICS Adapter program |
 |
|
Novice
Joined: 11 Nov 2006
Posts: 19
|
Hi,
I am planning to have a MQ Trigger as EVERY. I have few questions,
1. Can we use EVERY option? (we are expecting 7000 concurrent users)
2. Please let me know the step by step process of CICS Adapter which would get triggered for each message and should get the message to start a transaction.
3. If anybody has sample CICS Adapter , please send it my mail id
babujini@gmal.com.
Thanks,
Babu M |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Sun Nov 12, 2006 4:48 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
There is a trigger monitor delivered with the product.
Regardless of the number of users if you do use trigger every you need to limit the resources available to the transaction in CICS.
Although I am not working with Mainframes I believe it is called Tclassing the transaction...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| hopsala |
| Posted: Sun Nov 12, 2006 9:00 am Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
As saper said, there's a trigger monitor supplied with the standard WMQ package; it's called CKTI, look it up.
Now, concerning the throughput issue - it doesn't really matter how many "users" you have, whatever that means, but how many messages per second and of what average message size. After you've determined that decide whether to use EVERY or FIRST according to these considerations:
1. It's easier to write transactions triggered with EVERY, since they just MQGET once, process, and shut down. No hassle.
2. It's far less efficient to work with EVERY since you have to MQCONN+MQOPEN for each message
3. Also, with EVERY you have to load the transaction each time.
4. And finally, with EVERY you have to MQCMIT for each message, which makes for poor performance.
So, a long story short: If you don't have a performance problem, go with EVERY, if you need to conserve valualbe resources, use FIRST.
Naturally, if we're takling about an already existant program, then you don't really have a choice, now do you?
EDIT: Oh, and you can restrict the resources the transaction takes up, and the maximum number of concurrent running transactions. Approach your CICS admin, he'll know what to do. |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Mon Nov 13, 2006 5:48 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
| Quote: |
| 2. It's far less efficient to work with EVERY since you have to MQCONN+MQOPEN for each message |
IIRC MQCONN shouldn't be an issue under CICS. It is ignored as CICS does the connect at startup and ignores the programs MQCONN....but MQOPEN certainly is going to be an issue.  |
|
| Back to top |
|
|
| hopsala |
| Posted: Tue Nov 14, 2006 10:28 pm Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
| kevinf2349 wrote: |
| Quote: |
| 2. It's far less efficient to work with EVERY since you have to MQCONN+MQOPEN for each message |
IIRC MQCONN shouldn't be an issue under CICS. It is ignored as CICS does the connect at startup and ignores the programs MQCONN....but MQOPEN certainly is going to be an issue. |
Woops! Forgot about that, thanks for the correction |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
