| Author |
Message
|
| Charlie |
 Posted: Tue Nov 09, 2004 5:07 am Post subject: Finding the flow name in a COMPUTE node. |
 |
|
Newbie
Joined: 12 Oct 2004
Posts: 5
Location: Johannesburg S.A
|
Hi All,
Is there any way of getting hold of the "flow name" in a compute or any other node. We would like to use this for error tracking.
_________________
Thx
Charles Kapp
Liberty Life
IT Consaltant |
|
| Back to top |
|
 |
| KeeferG |
| Posted: Tue Nov 09, 2004 6:25 am Post subject: |
|
|
Master
Joined: 15 Oct 2004
Posts: 215
Location: Basingstoke, UK
|
This can easily be done inside a jave node. I do vaigly remember trying this in ESQL and will see if I can find it for you. I think it was something to do with the exceptionlist or local environment.
_________________
Keith Guttridge
-----------------
Using MQ since 1995 |
|
| Back to top |
|
|
| mayur2378 |
| Posted: Tue Nov 09, 2004 7:36 am Post subject: |
|
|
Apprentice
Joined: 26 May 2004
Posts: 47
|
Have a closer look at your exceptionlist. You should be able to get the flow name out of it ..
Mayur |
|
| Back to top |
|
|
| mayur2378 |
| Posted: Tue Nov 09, 2004 7:42 am Post subject: |
|
|
Apprentice
Joined: 26 May 2004
Posts: 47
|
Have a closer look at your exceptionlist. You should be able to get the flow name out of it ..
Mayur |
|
| Back to top |
|
|
| kirani |
| Posted: Tue Nov 09, 2004 9:20 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
|
| Back to top |
|
|
| KeeferG |
| Posted: Wed Nov 10, 2004 1:28 am Post subject: |
|
|
Master
Joined: 15 Oct 2004
Posts: 215
Location: Basingstoke, UK
|
It is true that a plug in node does give you a lot more access to information however, if all you need is the flow name, then I am pretty sure this is stored in the exception tree and can be accessed inside the comput node with standard ESQL..
I guess it depends how much information you want and how much effort you want to put in.
_________________
Keith Guttridge
-----------------
Using MQ since 1995 |
|
| Back to top |
|
|
| Charlie |
| Posted: Wed Nov 10, 2004 1:39 am Post subject: |
|
|
Newbie
Joined: 12 Oct 2004
Posts: 5
Location: Johannesburg S.A
|
Hi,
Sorry, I said that we want to use it for error tracking. This is not for error tracing in mqsi but more for if there was an error with our data accourding to our busseniss rules.
I can not use the exception list becuase there is no exception in mqsi.
_________________
Thx
Charles Kapp
Liberty Life
IT Consaltant |
|
| Back to top |
|
|
| RichA |
| Posted: Wed Nov 10, 2004 2:27 am Post subject: |
|
|
Centurion
Joined: 14 Mar 2002
Posts: 102
|
| If there is an error with the data could you not then throw a user exception from your code when error conditions are met? Then you'll have an exception list. |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Nov 10, 2004 9:54 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Writing a plug-in node is not very hard. That's sometimg you can do in a very short timeframe. Throwring "UserException" is a workaround. Your code will change if IBM decides to change the format of the ExceptionList. Also, If you decide to do it using "UserException" then you need to add atleast one Compute node to Throw Exception and make sure your Transaction processing does not roll-back.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| RichA |
| Posted: Wed Nov 10, 2004 10:06 am Post subject: |
|
|
Centurion
Joined: 14 Mar 2002
Posts: 102
|
Throwing a user exception is a workaround?
I would have said it was the other way round after all you can write plug in nodes to perform all functionality of message broker if you really want, then there's no chance IBM can change the format of messages, but frankly you're reinventing the wheel. Throwing a user exception you can insert additional diagnostic information and the exception can be handled by generic error handling routines. I see no need to distinguish between a business logic error and other message broker errors in the way they are handled (at least initially) |
|
| Back to top |
|
|
| kirani |
| Posted: Thu Nov 11, 2004 12:36 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
| RichA wrote: |
Throwing a user exception is a workaround?
|
It'd be workaround for getting the message flow name for his requirement. What I understand from his post is he wants to Trace bad data thats coming in incoming message.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
|
|
