Author |
Message
|
run |
Posted: Thu Jun 11, 2009 9:49 am Post subject: Triggering Mechanism Approach "Needed Advice" in M |
|
|
 Apprentice
Joined: 14 May 2007 Posts: 45 Location: Newyork, USA
|
To all grand masters out there needed an advice on two approaches that we are considering right now
Overview: This is a synchronous transaction. An XML to CPY vice verse (Note: mainframe is VSE and MQ version 2 does not participate in clustering so it’s a point to point). A Single transaction (XML message comes in transformed to a CPY sent to MAINFRAME but as a response multiple messages are put on the response queue in a group which are picked up by the broker to process.***Note(throughput here is 800,000 per day)
1 Approach: when a message arrives on local queue say MFREQUEST on mainframe (triggering is set up on the queue) that triggers a COBOL program to pick up the messages that arrived). The COBOL program picks up then picks up all the messages and process them by sending to other COBOL programs and sent out responses on to a MFRESPONSE queue.
2 Approach: Message arrives on the request MFREQUEST queue. A COBOL program keeps hitting the queue checking for messages every 2 seconds and process them when the message is available on the queue.
Questions: 1) which approach uses high CPU? 2) What is a better approach as the throughput is pretty high?
3) Any other approach that can be considered?
Any advice is deeply appreciated |
|
Back to top |
|
 |
Vitor |
Posted: Thu Jun 11, 2009 10:53 am Post subject: Re: Triggering Mechanism Approach "Needed Advice" |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
run wrote: |
1) which approach uses high CPU? |
It depends - see below
run wrote: |
2) What is a better approach as the throughput is pretty high? |
800,000 messages a day is not a lot. The better question is how many messages arrive in a block: if the messages arrive throughout the day then a long running application will be more efficient (though use get with wait rather than polling or you'll burn CPU); if you have a large block of messages followed by periods of non-delivery triggering will offer advantages
run wrote: |
3) Any other approach that can be considered?
|
Possibly - certainly there are a number of variants of these methods. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
fjb_saper |
Posted: Thu Jun 11, 2009 12:33 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
MQ version 2 on the Mainframe ? Is that even still supported? Upgrade! Upgrade!  _________________ MQ & Broker admin |
|
Back to top |
|
 |
run |
Posted: Thu Jun 11, 2009 12:52 pm Post subject: |
|
|
 Apprentice
Joined: 14 May 2007 Posts: 45 Location: Newyork, USA
|
Its VSE not Z/OS VSE supports version 2 so far.IBM came out with version 3 but its not yet watched enough to actually upgrade. |
|
Back to top |
|
 |
gbaddeley |
Posted: Thu Jun 11, 2009 7:52 pm Post subject: |
|
|
 Jedi Knight
Joined: 25 Mar 2003 Posts: 2538 Location: Melbourne, Australia
|
|
Back to top |
|
 |
run |
Posted: Thu Jun 11, 2009 7:57 pm Post subject: |
|
|
 Apprentice
Joined: 14 May 2007 Posts: 45 Location: Newyork, USA
|
Thank you very much for the feedback I will go through it. Any further links and advices will be appreciated. |
|
Back to top |
|
 |
|