tFSCheck – Docs for ESB 5.x

Component family

FileScale

Note that this component is deprecated.

Function

tFSCheck validates all the
records in an input file against a sort type and order. Validation
can be carried out in full or partly. This component has real-time
capabilities for checking large scale files. To optimize
performance, the component usually sorts data before processing
it.

Purpose

tFSCheck helps ensure the quality
of data in a source file according to a sort type and order.

Basic settings

Schema type 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.

Click Edit schema to make changes to the schema. If the
current schema is of the Repository type, three options are
available:

Repository: You have already
created the schema and stored it in the Repository. You can reuse it
in various projects and job flowcharts. Related topic: see
Talend Studio
User Guide.

Built-in: You create and store
the schema locally for this component only. Related topic: see
Talend Studio
User Guide.

Property type

Either Built-in or Repository.

Since version 5.6, both the Built-In mode and the Repository mode are
available in any of the Talend solutions.

Built-in: No property data stored
centrally.

Repository: Select the repository
file where Properties are stored. The fields that follow are filled
in automatically using fetched data.

Input File Name

Name of the file holding the data you want to check.

Record separator (char)

Character, string or regular expression used to separate records
(rows).

Field separator (char)

Character, string or regular expression used to separate fields in
a record.

Header

Number of records to be skipped at the beginning of the
file.

Footer

Number of records to be skipped at the end of the file.

Criteria

Click the plus button to add as many lines as required to check if
the source file is well sorted or not.

Schema column: Click in the cell
and select the schema column label on which you want to base the
sorting process.

Sort type: Click in the cell and
select the sort type: numerical or alphabetical.

Order type: Click in the cell and
select the order type: ascending or descending.

Advanced settings

Generate FSLang File

Select this check box to generate the FSLang file corresponding to
your Job and click the three-dot button next to the FSLang File Name field to specify its
path and name.

Assign FileScale Path

Select this check box and then click the three-dot button next to
the FileScale Path field to select
the FileScale program executable file required to execute the
component.

Specify Number of Process Child

Select this check box and enter the number of child processes to
use to carry out aggregation.

Custom FileScale Parameter (separated
by,)

Enter the parameters for any specific operation you want to add to
the FileScale executable call.

Check Schema

Checks the schema. The result returned in the console is “Ok” if
the schema is valid. Otherwise, no result is returned.

tStatCatcher Statistics

Select this check box to gather the Job processing metadata at a
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.

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 files therefore it does not require input
or output data flows. It is used to validate data in large scale
files.

Limitation

tFSCheck limitations depend on
the limits imposed by the physical memory and CPU architecture. For
example, the total length of processed files cannot exceed the file
system limit for LargeFile support (maximum value of 64 signed
bits).