| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Dealing with ErrorHandling subflow |
« View previous topic :: View next topic » |
| Author |
Message
|
| chris boehnke |
 Posted: Tue Jul 03, 2007 5:27 am Post subject: Dealing with ErrorHandling subflow |
 |
|
Partisan
Joined: 25 Jul 2006
Posts: 369
|
Hi Guys,
I am using the ErrorHandler flow at the catch terminal of the input node, SUBSTRING((Root.BLOB.BLOB FROM 1 FOR  ..msgIdentifier
If msgIdentifier = 'ABCD' then route to path with messageset
else
XML message path
Question: If there are many Cobol messages with different headers, then what to do?. Can we include those new header messages also in the same errorHandling subflow or do we need to have a new subflow to handle this?.
I am assuming, we can use the case statement in a compute node for different copybook headers. If we use the Compute node the performance is going to be reduced?
Suggestions please.
Thanks. |
|
| Back to top |
|
 |
| sknrt1 |
| Posted: Tue Jul 03, 2007 7:37 am Post subject: |
|
|
Apprentice
Joined: 22 Jan 2003
Posts: 39
Location: USA
|
I guess, need more details on what you were trying to do or the design.
| Quote: |
If msgIdentifier = 'ABCD' then route to path with messageset
else
XML message path |
what is the requirement to pass it through msgset in the catch block.
was the same messageset applied in the normal flow (prior to catch block)? If so, the error might have been due to msgset application and it can repeat in the catch block. Assume there was no error due to msgset, you can try to change your flow by including try-catch node and connection errorHandling to it. Part of errorHandling you can distinguish btn MQInput Node catch or try-catch. Point is by the time it comes to try-catch, you can have the data parsed according to msgset, to avoid application of msgset in the catch block. application of msgset is a reduces the performance.
If the msgset wasn't applied in the normal flow, probably you have a specific req to apply it in the catch block.
Generally, applying msgset has a performance effect, than having a case statement with multiple options (may be).
_________________
------------------------------------------
sk
MQ User since 2001
Message Broker User since 2001
IBM Certified
Solution Designer - WebSphere MQ
Solution Developer - Message Broker |
|
| Back to top |
|
|
| wbi_telecom |
| Posted: Tue Jul 03, 2007 9:34 am Post subject: |
|
|
Disciple
Joined: 15 Feb 2006
Posts: 188
Location: Harrisburg, PA
|
I am not sure why you would need a msgset to capture an exception that has occurred in your message flow. May be I am not understanding what you are trying to achieve, but your aim is to capture the errors that you have got while processing an MRM message, you can still do it using the XMLNS domain. All you will have to do is parse the ExceptionList correctly in your error handling subflow. I personally will avoid the use of message sets.
Cheers, |
|
| 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
|
|
|
|
