|
Component family
|
Processing/Fields
|
Note that this component is deprecated. The EBCDIC handling
capabilities are now fully supported by Talend Data Mapper that comes with any Talend
Platform solutions. For more information about Talend Data Mapper, see Talend Data Mapper User Guide.
|
|
Function
|
tExtractEBCDICFields generates
multiple columns from a given column according to the defined EBCDIC
schema.
|
|
Purpose
|
tExtractEBCDICFields allows you
to extract EBCDIC data from a formatted string.
|
|
Basic settings
|
Schema and Edit
schema
|
A schema is a row description, it defines the number of fields to
be processed and passed on to the next component. The schema is
either Built-in or stored remotely
in the Repository.
Since version 5.6, both the Built-In mode and the Repository mode are
available in any of the Talend solutions.
Click Edit schema to make changes to the schema. If the
current schema is of the Repository type, three options are
available:
-
View schema: choose this option to view the
schema only.
-
Change to built-in property: choose this option
to change the schema to Built-in for local
changes.
-
Update repository connection: choose this option to change
the schema stored in the repository and decide whether to propagate the changes to
all the Jobs upon completion. If you just want to propagate the changes to the
current Job, you can select No upon completion and
choose this schema metadata again in the [Repository
Content] window.
|
|
|
|
Built-in: Select this option to
edit the Built-in schema for the data to be processed.
|
|
|
|
Repository: The schema already
exists and is stored in the Repository, hence can be reused in
various projects and Job flowcharts. Related topic: see
Talend Studio User
Guide.
|
|
|
Sync columns
|
Click this button to retrieve the schema defined in the input component.
Note
This button is available only when an input component is
connected to this component via a Row > Main
connection.
|
|
|
Field
|
Select an incoming field from the Field list to extract.
|
|
|
Die on error
|
This check box is selected by default. Clear the check box to skip
the row on error and complete the process for error-free rows. If
needed, you can retrieve the rows on error via a Row > Reject connection.
|
|
Advanced settings
|
Encoding
|
Select the encoding type from the list or select Custom and define it manually. This field
is compulsory for DB data handling.
|
|
|
Trim all column
|
Select this check box to remove the leading and trailing
whitespaces from all columns. When this check box is cleared, the
Check column to trim table is
displayed, which lets you select particular columns to trim.
|
|
|
Check column to trim
|
This table is filled automatically with the schema being used. Select the check box(es)
corresponding to the column(s) to be trimmed.
|
| |
tStatCatcher Statistics
|
Select this check box to gather the processing metadata at the Job
level as well as at each component level.
|
|
Global Variables
|
ERROR_MESSAGE: the error message generated by the
component when an error occurs. This is an After variable and it returns a string. This
variable functions only if the Die on error check box is
cleared, if the component has this check box.
NB_LINE: the number of rows read by an input component or
transferred to an output component. This is an After variable and it returns an
integer.
A Flow variable functions during the execution of a component while an After variable
functions after the execution of the component.
To fill up a field or expression with a variable, press Ctrl +
Space to access the variable list and choose the variable to use from it.
For further information about variables, see Talend Studio
User Guide.
|
|
Usage
|
This component handles flow of data therefore it requires input
and output components. It allows you to extract data from a
delimited field, using a Row >
Main link, and enables you to
create a reject flow filtering data which type does not match the
defined type.
|
|
Log4j
|
The activity of this component can be logged using the log4j feature. For more information on this feature, see Talend Studio User
Guide.
For more information on the log4j logging levels, see the Apache documentation at http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Level.html.
|
|
Limitation
|
n/a
|
