| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Setting UserException in Compute node for Catch processing |
« View previous topic :: View next topic » |
| Author |
Message
|
| BergerC |
 Posted: Tue Apr 09, 2002 12:14 pm Post subject: |
 |
|
Novice
Joined: 08 Apr 2002
Posts: 15
|
I've read an excellent article re: MQSI Exception Processing, but I've hit a snag in implementing similar functionality. Based on Compute node ESQL logic, I can choose to SET the UserException as follows:
SET OutputExceptionList.UserException.Text = 'No valid Order ID received from Host';
At the end of the message flow, a Filter node checks the CARDINALITY of ExceptionList.UserException, and if greater than 0, it routes the message to a Throw node. This is all well and good.
However, it seems that once the Throw node rolls the message back to the catch terminal of the MQInput node, my Trace output shows that the ExceptionList has been overwritten with the property values in the Throw node. There's no evidence of the UserException text I added in the Compute node.
The Advanced Tab mode of the Compute node is set to "All", and the ExceptionList is copied forward prior to writing the value above.
My impression was that text written to the UserException portion of the ExceptionList is incorporated into the ExceptionList after rollback through the Catch terminal of the MQInput node. Is this incorrect?
Any help is appreciated. |
|
| Back to top |
|
 |
| TorpedoSTu |
| Posted: Thu Apr 11, 2002 1:05 am Post subject: |
|
|
Acolyte
Joined: 14 Nov 2001
Posts: 73
|
Hiya,
What u should be doing is throwing the user exception AND supplying hte error text at the same time.
Try -
Throw user exception catalog 'WMQIv210' message 2949 values ('Whoops - something went wrong !);
Note that messge no's 2949 thru 2999 are user definable and won't be overwritten.
Regs
Stu
|
|
| Back to top |
|
|
| BergerC |
| Posted: Thu Apr 11, 2002 4:52 am Post subject: |
|
|
Novice
Joined: 08 Apr 2002
Posts: 15
|
My apologies - I should have mentioned we're on version 2.0.2. It seems there are some new capabilities in v2.1 that I'm already looking forward to.
To explain a bit more clearly, using Trace I can see the ExceptionList.UserException.Text as it leaves the Compute node, but after the message is routed to the Throw node, then rolled back through the Catch terminal of MQInput, the ExceptionList has been regenerated, and the values I set in the ESQL are over-written, apparently by the Throw node settings.
I get the feeling (from experience) I'm missing something simple here... |
|
| Back to top |
|
|
| BergerC |
| Posted: Fri Apr 12, 2002 12:20 pm Post subject: |
|
|
Novice
Joined: 08 Apr 2002
Posts: 15
|
Thanks to Alex - can't be done in v2.0.2 - the Throw node must contain the properties you want in the ExceptionList.
Another reason to look towards v2.1. |
|
| 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
|
|
|
|
