Connecting failure terminals

The nodes sometimes generate errors that you can predict, and it is in these cases that you might want to consider connecting the failure terminal to a sequence of nodes that can take sensible actions in response to the expected errors.

Examples of expected errors are:

• Temporary errors when the input node retrieves the message.
• Validation errors detected by an MQInput, Compute, or Mapping node.
• Messages with an internal or format error that cannot be recognized or processed by the input node.
• Acceptable errors when a node accesses a database, and you choose not to configure the node to handle those errors.
• ESQL errors during message flow development (some ESQL errors cannot be detected by the editor, but are recognized only by the broker; these cause an exception if you have not connected the failure terminal. You can remove the fail flow when you have completely tested the runtime ESQL code).

You can also connect the failure terminal if you do not want WebSphere® MQ to try a message again or put it to a backout or dead letter queue.