A correlation name is a field reference that identifies a well-defined starting point in the logical message tree and is used in field references to describe a standard part of the tree format.
When you access data in any of the four trees (message, environment, local environment, or exception list), the correlation names that you can use depend on the node for which you create ESQL or mappings, and whether the node creates an output message. For example, a Trace node does not alter the content of the message as it passes through the node, but a Compute node can construct a new output message.
You can introduce new correlation names with SELECT expressions, quantified predicates, and FOR statements. You can create non-correlation names in a node by using reference variables.
Most message flow nodes do not create an output message; all ESQL
expressions that you write in ESQL modules or in mappings within these nodes
refer to just the input message. You can use the following correlation names
in Database and Filter (ESQL modules) nodes. You cannot use these correlation
names in the expression of any mapping for a Mapping, Extract, Warehouse,
DataInsert, DataUpdate, or DataDelete node.
See Using anonymous field references for a description of how to use *.
If you are coding ESQL for a Compute node, the correlation names are different because there are two message trees involved: the input message and the output message. The correlation names in ESQL within these nodes are:
See Using anonymous field references for a description of how to use *.
In a Compute node, there is no correlation name OutputBody.
While this correlation name is always valid, it has meaning only when the Compute Mode property of the Compute node indicates that the Compute node is propagating the ExceptionList.
While this correlation name is always valid, it has meaning only when the Compute Mode property of the Compute node indicates that the Compute node is propagating the LocalEnvironment.
Related concepts
Environment tree
LocalEnvironment tree
ExceptionList tree
ESQL field references
Message modeling
Related tasks
Developing message flow applications
Manipulating message body content
Manipulating other parts of the message tree
Using anonymous field references
Related reference
Built-in nodes
Compute node
Database node
Filter node
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac00510_ |