User exits

A user exit is user-provided custom software, written in C, to track data passing through message flows.

User-provided functions can be invoked at specific points during the life cycle of a message while it passes through the message flow, and can invoke utility functions to query information about the point in the flow, and the contents of the message assembly.

The user exits can be invoked when one or more of the following events occur:
Basic message flow
In the basic message flow shown here, you can track messages at two levels:
At the transaction level, you can track the following events:
At the node level, you can track the following events:
Therefore, you can track four different types of event, which occur in the following sequence:
  1. A message is dequeued from the input source (read into the flow).
  2. A message is propagated to the node for processing.
  3. Node processing is completed.
  4. The end of the transaction.
Related tasks
Exploiting user exits
Developing a user exit
Deploying a user exit
Related reference
User-defined extensions
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:19:59

ac02140_