Error subflow for the Record Distribution to WebSphere MQ: one-way pattern

This subflow tests whether an error message must be written and is determined by the user-defined property: ErrorLoggingOn.

If an error is caught during processing in the message flows, the Error subflow is called. The following actions are taken by the Error subflow:

  1. If error messages are required, an error message is prepared and written to the error queue. Details of the exception are written as an XML message. These details include:
    • Broker name
    • Flow name
    • Time stamp
    • File directory
    • File name
    • Record number, when error occurred
    • Number of records written to default queue
    • Summary of the exception data

    The summary of the exception data contains the message flow label, error number, text description, and a list of inserts giving further details.

  2. An exception is produced that causes the flow to end unsuccessfully. This action moves the file to the backout subdirectory.
Note: Messages that cannot be routed are written to a default destination. This action is not treated as an error.

Any failure that stops a record being read from the file and written to disk is treated as an error.

Back to the Record Distribution to WebSphere MQ: one-way pattern specification