Best practice: do not change copied components used in the same runset
Using copied components in the same runset has a performance benefit. Runsets process copied components more efficiently than identical components that are created separately or cloned.
When multiple components in a runset have the same ID, (as copied components do) the runset discards all but one copy. This results in faster processing. However, to avoid unexpected results, you must take care not to change the definition of any of the copied components.
It is also a best practice to keep track of those components that you copy, so you do not inadvertently change a copy. You should create a workspace named COM (for Common) that contains all the components you copy, and that you use COM as a prefix in all the copies of components, to make it easy to recognize that these are copied components that should not be changed.
Copyright IBM Corporation 2012. All Rights Reserved.