|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
How to stop triggering on queue when error encountered |
« View previous topic :: View next topic » |
Author |
Message
|
ranstice |
Posted: Mon Mar 25, 2002 4:28 pm Post subject: |
|
|
Newbie
Joined: 24 Mar 2002 Posts: 8
|
Hi,
I am researching how to stop triggering on our input queue when we have an error encountered in a C program.
We have one program that monitors an input queue and spawns multiple programs that read from the input queue. If the database we try to write output to is down - we don't want to lose the input message - so we exit the program before doing a GET. The monitoring program sees messages still in the queue and triggers another program to start - which gets the same database error...and we go into an endless loop.
One solution is to have the spawned program turn off the triggering option on the input queue (so that the system that is writing data to that queue can continue writing messages). Unfortunately I haven't been able to weed through the documentation and find exactly what I need.
Can anyone help?
Thanks in advance,
Robin |
|
Back to top |
|
 |
mqonnet |
Posted: Tue Mar 26, 2002 6:46 am Post subject: |
|
|
 Grand Master
Joined: 18 Feb 2002 Posts: 1114 Location: Boston, Ma, Usa.
|
If you are doing this programatically then you might want to use either PCF messages to make the initiation queue get(disbaled) or you could use MQSET function to achieve the same functionality, if an error occurs on the triggered app.
Cheers.
Kumar
_________________ IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
Back to top |
|
 |
ranstice |
Posted: Tue Mar 26, 2002 10:09 am Post subject: |
|
|
Newbie
Joined: 24 Mar 2002 Posts: 8
|
Thanks for your response. Currently I'm not familiar with PFC messages - so I'll go the other route.
I researched MQSET previously but was unable to find the right call parameters for during triggering off in the MQSeries Info Center.
I was using the following sample:
MQSET(Hcon, /* connection handle */
Hset, /* object handle */
1L, /* Selector count */
Select, /* Selector array */
1L, /* integer attribute count */
IAV, /* integer attribute array */
0L, /* character attribute count */
NULL, /* character attribute array */
But could not find the right parameters to assign to Select and IAV.
Do you know what parameters I will need? Are the other parameters being passed to MQSET correct?
Thanks again. |
|
Back to top |
|
 |
ranstice |
Posted: Fri Mar 29, 2002 2:44 pm Post subject: |
|
|
Newbie
Joined: 24 Mar 2002 Posts: 8
|
For those interested in the resolution - this was coded in C.
1. The initiation queue when referred in the program must be called by it's actual name - not the alias.
2. When opening the queue, one of the open options must be MQOO_SET
3. In the MQSET statement, Hobj must be assigned to the initiation queue.
4. The selector parameter must be set to MQIA_TRIGGER_CONTROL
5. The integar attributes parameter must be set to MQTC_OFF
6. The remaining parameters are defined correctly above in my previous posting. |
|
Back to top |
|
 |
StefanSievert |
Posted: Fri Mar 29, 2002 3:35 pm Post subject: |
|
|
 Partisan
Joined: 28 Oct 2001 Posts: 333 Location: San Francisco
|
Hi,
thanks for posting the solution, that's great! One question though: Am I correct in assuming that you didn't modify the initiation queue, but your actual triggered application queue?
Just curious,
Stefan
_________________ Stefan Sievert
IBM Certified * WebSphere MQ |
|
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
|
|
|
|