|On this page|
Each work item keeps a list of environment variables that should be set in the environment the work item’s command line runs in. These are stored as work item attributes with a
$ prefix on the name (for example,
The list of variables gets passed down from parent to child items down through the network. This node lets you edit the environment variable list of the work items passing through the node.
Work Item Generation
Whether this node generates static or dynamic work items. You should generally leave this set to "Automatic" unless you know the node’s work items can be computed statically, or that they need to be generated dynamically.
This node always creates dynamic work items: it waits until the upstream work items are known, and generates new work items from the upstream work items.
This node always creates static work items: it creates the number of work items it thinks it needs based on the parameters (and any upstream static items) before the network runs.
If the input is static (a static processor, or a partitioner with only static inputs, or a mapper), this node generates static work items, otherwise it generates dynamic work items.
Clears the incoming list of environment variables (don’t inherit the list of variables set on the upstream items).
Use this multiparm to set up the environment variables to add/set in the outgoing work items.
The name of the variable to set, not including the
The data type of the value. Note that this is only used internally for the work item. In the execution environment, all environment variables are just strings.
The value to set the variable to.
This example demonstrates how to modify the environment variables before spawning a child process.
The following examples include this node.