Alias Process Object

The Integrator Alias process object allows columns to be renamed in the flow by applying aliases to the column names. It consists of an array of alias definitions in the form old column name=new column name. Blanks before or after the column names are ignored. The output flow will have the old column name renamed to the new column name. If new column is blank, the given column is removed from the output flow. Alias is useful when renaming columns prior to the output (OUTP) object.

Alias Attributes

Attribute	Type	Description
process_type (required)	String	Identifies the object as an Alias process object. The value of this string is "alias".
input (required)	String	Defines the object from which the data flow is arriving.
aliases (required)	Array of Strings	Renames input columns. Format is "oldname=newname". If multiple columns are aliased to the same name, Integrator will issue a warning. If new column name is blank, then the given column is deleted from the output flow. NOTE: This attribute is Alias Lines in Visual Integrator.
prefix	String	Defines a prefix that is prepended to all columns in the flow that are not aliased using the aliases array. If you want a space between the prefix and the column name, include that space in the prefix string definition.
keep_columns	Array of Strings	Defines a list of columns to be kept by the input object. If this attribute is not used, all columns are kept. The output flow of the object is limited to those columns that are listed, and no excluded columns are available to subsequent process objects. Column names in the keep_columns array should be given after they are aliased or prepended with the prefix string.
rename_duplicates	Boolean	Creates new column names for duplicate columns names that appear in the input flow for this object. Subsequent columns for a column with the same name as a column name will be given the names name_2 ... name_(n) based on the positional order in the input. If, for some reason, a column in the input flow already has this name, that number will be skipped. For example, if the input flow already has a column named "DESC_2", the object will name the duplicate column DESC as "DESC_3". The duplicate naming process occurs before attributes defining aliases, prefixes or the columns to keep are applied, so these generated column names can be aliases to another name. Using this attribute will disable certain column optimizations that the Integrator performs on data flows; it is recommended that you put the alias objects immediately after an object that has duplicate columns, to avoid having the Integrator process more data than is necessary.
trace_after	Sub-object	Traces data flows leaving the specified object, which makes debugging scripts easier. This is equivalent to adding a Trace process object immediately after the current object. See Embedded Trace Object for more on using trace sub-objects.
trace_before	Sub-object	Traces data flows entering the specified object. This is equivalent to adding a Trace process object immediately before the current object. See Embedded Trace Object for more on using trace sub-objects.