MQSeries.net :: View topic - Error Processing: Message content VS. Environment errors

catwood2

Input appreciated.

My main flow is wired as:
MQInput -> Compute -> MQOutput
Compute node will Transform message based on external database lookup and set to Validate 'Content and Value'.

My error handler is wired to MQInput catch terminal:

Filter-> Compute Node ->MQOutput

The purpose of the Filter is to determine if the error condition is specific to the message itself(bad xml, etc) or an issue with the environment (external db down, output queue full, etc).

If the issue is with the message itself - the path will result in the message being written to a queue and the flow is onto the next message.

If the issue is determined to be with the environment - the path will result in a looping over this same message (implicitly stopping the flow) until the environment issue is resolved.

Initially, I was thinking that I had a good handle on potential issues with the message content and treat everything else as 'environment'. That doesn't seem to well thought out tho....as, that halts processing altogether and it would be better to err on the side of 'content' issue. I have been looking thru the 'Messages' manual with the hopes that there would be some way to decipher that an error code is "environmental" but I am not seeing it.