tLogRow Standard properties
These properties are used to configure tLogRow running in the Standard Job framework.
The Standard
tLogRow component belongs to the Logs & Errors family.
The component in this framework is generally available.
Basic settings
Schema and Edit schema |
A schema is a row description. It defines the number of fields (columns) to Click Edit schema to make changes to the schema.
This component offers the This dynamic schema |
Built-In: You create and store the |
|
Repository: You have already created |
|
Sync columns | Click to synchronize the output file schema with the input file schema. The Sync function is available only when the component is linked with the preceding component using a Row connection. |
Basic | Displays the output flow in basic mode. |
Table | Displays the output flow in table cells. |
Vertical |
Displays each row of the output flow as a key-value list. With this mode selected, you can choose to show either the unique name |
Separator (For Basic mode only) |
Enter the separator which will delimit data on the Log display. |
Print header (For Basic mode only) |
Select this check box to include the header of the input flow in the output display. |
Print component unique name in front of each (For Basic mode only) |
Select this check box to show the unique name the component in front |
Print schema column name in front of each (For Basic mode only) |
Select this check box to retrieve column labels from output |
Use fixed length for values (For Basic mode only) |
Select this check box to set a fixed width for the value |
Print content with log4j |
Select this check box to output the data flow content if the log4j |
Global Variables
Global Variables |
NB_LINE: the number of rows processed. This is an After
ERROR_MESSAGE: the error message generated by the A Flow variable functions during the execution of a component while an After variable To fill up a field or expression with a variable, press Ctrl + For further information about variables, see |
Usage
Usage rule |
This component can be used as intermediate step in a data flow or as a |