# tSystem Calls other system processing commands, already up and running in a larger Job. ## tSystem Standard properties These properties are used to configure tSystem running in the Standard Job framework. The Standard tSystem component belongs to the System family. The component in this framework is available in all Talend products. ## Basic settings | Properties | Description | | --- | --- | | Use home directory | Select this check box to change the name and path of a dedicated
directory. | | Use Single Command | When the required command is very simple, to the degree that, for
example, only one parameter is used and without space, select this
option to activate its Command
field. In this field, enter the simple system command. Note that the
syntax is not checked.

Information noteWarning:

*In Windows, the MS-DOS commands do not allow you to
pass directly from the current folder to the folder
containing the file to be launched. To launch a file, you
must therefore use an initial command to change the current
folder, then a second one to launch the file* | | Use Array Command | Select this option to activate its Command field. In this field, enter the system
command in array, one parameter per line.

For example, enter the following command with consecutive spaces
in array for
Linux:

```

"cp"
"/temp/source.txt"
"/temp/copy to/"

``` | | Standard
Output and Error
Output |

Select the type of output for the processed data to be transferred to.
to console: data is passed on to be viewed in the Run view.
to global variable: data is passed on to an output variable linked to the tSystem component.
to console and to global variable: data is passed on to the Run view and to an output variable linked to the tSystem component.
normal: data is passed on to the component that comes next.

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

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.
Click Sync columns to retrieve the schema from the preceding component in the Job.
Built-in: You create and store the schema locally for this component only. For more information about a component schema in its Basic settings tab, see Basic settings tab.
Repository: You have already created the schema and stored it in the Repository. You can reuse it in various projects and Job flowcharts. For more information about a component schema in its Basic settings tab, see Basic settings tab.

| | Environment variables | Click the [+] button to add as
many global variables as needed.

name: Enter the syntax of the new
variable.

value: Enter a value for this
variable according to the context. | ## Advanced settings | Properties | Description | | --- | --- | | tStatCatcher Statistics | Select this check box to collect log data at the component level. | ## Global Variables | Variables | Description | | --- | --- | | 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 checkbox is
cleared, if the component has this checkbox.

OUTPUT: the standard output
from a process. This is an After variable and it returns a string.

ERROROUTPUT: the
erroneous output from a process. This is an After variable and it returns a
string.

EXIT\_VALUE: the exit code from a process. 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 more information about variables, see [Using contexts and variables](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/contexts-and-variables). | ## Usage | Usage guidance | Description | | --- | --- | | **Usage rule** | This component can typically used for companies which already
implemented other applications that they want to integrate into
their processing flow through Talend. | | Connections | Outgoing links (from this component to another):

Row: Main.

Trigger: On Subjob Ok; On Subjob
Error; Run if.

Incoming links (from one component to this one):

Row: Main; Reject; Iterate.

Trigger: On Subjob Ok; On Subjob
Error; Run if; On Component Ok; On Component Error; Synchronize;
Parallelize.

For further information regarding connections, see [Using connections in a Job](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/using-connections-in-job). | **Related concepts** * [Echoing 'Hello World!'](https://help.qlik.com/talend/en-US/components/8.0/system/tsystem-echoing-hello-world-standard-component "This scenario is one single component tSystem to execute a system command and shows the results in the Run view \"console\".") * [Executing an external command with multiple parameters using tSystem](https://help.qlik.com/talend/en-US/components/8.0/system/executing-cmd-with-multiple-para-using-tsystem-overview "This scenario executes an external command with multiple parameters using the tSystem component. It demonstrates the use of the Use Array Command option of the component. The system command copy {source} {destination} is used for this purpose. The command has two parameters: {source} and {destination}.")