The LocalEnvironment tree includes a subtree called Variables. This is always created, but is never populated by the message flow. You can use this area for your own purposes, for example to pass information from one node to another.
We recommend that you include all your information in this subtree. However, you can create other subtrees in the LocalEnvironment tree if you choose.
The advantage of creating your own data in a scratchpad in the LocalEnvironment is that this data is propagated as part of the logical tree to subsequent nodes in the message flow. If you create a new output message in a Compute node, you can also include all or part of the LocalEnvironment tree in the input message in the new output message.
However, any data updates or additions that you make in one node are not retained if the message flows back through the message flow (for example, if an exception is thrown, or if the message is processed through the second terminal of the FlowOrder node). If you want to create your own data, and want that data to be preserved throughout the message flow, you must use the Environment tree.
You can set values in the Variables subtree in a Compute node that are used later by another node (Compute, Database, or Filter) for some purpose that you determine when you configure the message flow.
SET LocalEnvironment.Variables.OutputLocation = 'MQ';
IF LocalEnvironment.Variables.OutputLocation = 'MQ' THEN DO; SET LocalEnvironment.Destination.MQ.DestinationData.queueManagerName = 'myQManagerName'; SET LocalEnvironment.Destination.MQ.DestinationData.queueName = 'myQueueName'; END IF;
For information about the full list of elements in the DestinationData subtree, see Data types for elements in the DestinationData subtree.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac16870_ |