# tAS400Output Writes, updates, makes changes or suppresses entries in a database. tAS400Output executes the action defined on the table and/or on the data contained in the table, based on the flow incoming from the preceding component in the Job. ## tAS400Output Standard properties These properties are used to configure tAS400Output running in the Standard Job framework. The Standard tAS400Output component belongs to the Databases family. The component in this framework is available in all Talend products. Information noteNote: This component is a specific version of a dynamic database connector. The properties related to database settings vary depending on your database type selection. For more information about dynamic database connectors, see [DB Generic components](https://help.qlik.com/talend/r/en-US/8.0/components/db-generic/db-generic-component). ## Basic settings | Properties | Description | | --- | --- | | Database | Select the desired database type from the list and click
Apply. | | Property
type | Either Built-in or Repository.

| | ![](https://help.qlik.com/talend/en-US/components/8.0/Resources/images/Save_Icon.png) | Click this icon to
open a database connection wizard and store the database connection
parameters you set in the component Basic settings view.

For more information about setting up
and storing database connection parameters, see [Centralizing database metadata](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/centralizing-database-metadata). | | DB Version | Select the AS/400
version in use | | Use an existing
connection | Select this check box and in the Component
List drop-down list, select the desired connection component to
reuse the connection details you already defined.

Information noteNote: When a Job contains the parent Job and the child Job, do the following if you
want to share an existing connection between the parent Job and the child Job (for example,
to share the connection created by the parent Job with the child Job).

  1. In the parent level, register the database connection to be shared in the Basic settings view of the connection component which creates that very database connection.
  2. In the child level, use a dedicated connection component to read that registered database connection.


For an example about how to share a database connection across Job levels,
see [Sharing a database connection](https://help.qlik.com/talend/r/en-US/7.3/studio-user-guide/sharing-database-connection). | | Host | Database server IP
address | | Port | Listening port
number of DB server. | | Database | Name of the
database | | Username and Password | DB user
authentication data.

To enter the password, click the [...] button
next to the password field, enter the password in double quotes in the pop-up dialog box,
and click OK to save the settings. | | Table | Name of the table to
be written. Note that only one table can be written at a
time | | Action on
table | On the table
defined, you can perform one of the following operations:


None: No operation is carried out.


Drop and create a table: The table is
removed and created again.


Create a
table: The table does not exist and gets created.


Create a table if not exists: The table
is created if it does not exist.


Drop a table if exists
and create: The table is removed if it already exists
and created again.


Clear a table: The table
content is deleted. | | Action on
data | On the data of the table defined, you can
perform:


Insert: Add new entries to the table.
If duplicates are found, Job stops.

Update: Make
changes to existing
entries.

Information noteNote: In cases where all the schema
columns are set as keys, this action yields an error and the Job fails.

Insert or
update: Insert a new record. If the record with the given reference
already exists, an update would be
made.

Information noteNote: In cases where all the schema
columns are set as keys, this action yields a warning message and the Job
continues.

Update or
insert: Update the record with the given reference. If the record does
not exist, a new record would be
inserted.

Information noteNote: In cases where all the schema
columns are set as keys, this action yields a warning message and the Job
continues.


Delete: Remove entries corresponding to
the input flow.

Information noteWarning: It is necessary to specify at least one column as a primary key
on which the Update and Delete operations are based.
You can do that by clicking Edit Schema and selecting the
check box(es) next to the column(s) you want to set as primary
key(s). For an advanced use, click the Advanced
settings view where you can simultaneously
define primary keys for the Update and Delete
operations. To do that: Select the Use field options check box and
then in the Key in
update column, select the check boxes next to
the column names you want to use as a base for the Update
operation. Do the same in the Key in delete column for the
Delete operation.

Information noteNote: The dynamic schema feature can be
used in the following modes: Insert; Update; Insert or update; Update or insert;
Delete. | | Schema and Edit
schema | A schema is a row description. It defines the number of fields
(columns) to be processed and passed on to the next component. When you create a Spark
Job, avoid the reserved word line when naming the
fields.

This component offers the advantage of the
dynamic schema feature. This allows you to retrieve unknown columns from source
files or to copy batches of columns from a source without mapping each column
individually. For further information about dynamic schemas, see [Dynamic schema](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/dynamic-schema).

This
dynamic schema feature is designed for the purpose of retrieving unknown columns of a
table and is recommended to be used for this purpose only; it is not recommended for the
use of creating tables.


Built-In: You create and store the schema locally for this component
only.


Repository: You have already created the schema and stored it in the
Repository. You can reuse it in various projects and Job designs.

When the schema to be reused has default values that are
integers or functions, ensure that these default values are not enclosed within
quotation marks. If they are, you must remove the quotation marks manually.

For more information, see [Retrieving table schemas](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/retrieving-table-schemas?tocId=_C1~eFOlN~GM_JR2qkBYZg).

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

| | 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>Rejects link. | ## Advanced settings | Properties | Description | | --- | --- | | Use commit
control | Select this check
box to have access to the Commit every field where you can define the commit
operation.


Commit
every: Enter the number of rows to be completed before
committing batches of rows together into the DB. This option ensures
transaction quality (but not rollback) and, above all, better
performance at execution. | | Additional JDBC
parameters | Specify additional
connection properties for the DB connection you are creating. This
option is not available if you have selected the Use an existing connection
check box in the Basic settings.

Information noteNote: You can press
Ctrl+Space to access a list of predefined global
variables. | | Additional
Columns | This option is not
offered if you create (with or without drop) the DB table. This option
allows you to call SQL functions to perform actions on columns, which
are not insert, nor update or delete actions, or action that require
particular preprocessing.

| | Use field
options | Select this check
box to customize a request, especially when there is double action on
data. | | Debug query mode | Select this check box to display each step during processing entries
in a database. | | Use Batch | Select this check box to activate the batch mode for data processing.

Information noteNote: This check box is available only when you have
selected the Insert, Update or Delete option in the Action on data
field. | | Batch
Size | Specify the number of records to be processed in each batch.

This field is available only when the Use batch mode
check box is selected. | | Support null in "SQL WHERE" statement | Select this check box to validate
null in "SQL WHERE" statement. | | Return generated keys | Select this option to return the key of a record when the record is
inserted.

Selecting this option decreases the performance because the component
will send records to the database row by row regardless of the batch settings.

Note that this option is not selected by default, meaning that the
component does not return record keys by default, which is different from the
way in which the component works when the 8.0.1-R2023-03 Talend Studio Monthly update (or a later one) is not installed. With the 8.0.1-R2023-03
Talend Studio Monthly update (or a later one) installed, a migration task will be carried
out for the Jobs that contain the tAS400Output component. The migration task
improves the performance of such kind of Jobs by preventing the tAS400Output
components from returning record keys. The migration task also has this option
selected in Jobs that contains the tAS400LastInsertId components, so that the
tAS400LastInsertId components can work properly. See [tAS400LastInsertId](https://help.qlik.com/talend/en-US/components/8.0/as400/tas400lastinsertid) for related information.

However,
this option may cause issues in Jobs that retrieve record keys through custom
code. For such Jobs, you need to select this option manually.

This
option is available when Insert is selected from the
Action on data in the Basic
settings view.

Information noteNote: This option is available only when you
have installed the 8.0.1-R2023-03 Talend Studio Monthly update or a later one delivered by Talend. For more information, check with your administrator. | | Set Query Timeout | Select this option to set a timeout period for the query or the batch query. The Job will be
terminated if the query or the batch query is timed out. You can set the
timeout period (in seconds) in the Timeout field.

Information noteNote:

| | tStat
Catcher
Statistics | Select this check
box to collect log data at the component level. | | Enable parallel
execution | Select this check box to perform high-speed data processing, by treating
multiple data flows simultaneously. Note that this feature depends on the database or
the application ability to handle multiple inserts in parallel as well as the number of
CPU affected. In the Number of parallel executions
field, either:



Note that when parallel execution is enabled, it is not possible to use global
variables to retrieve return values in a subJob.

| ## Usage | Usage guidance | Description | | --- | --- | | **Usage
rule** | This component
offers the flexibility benefit of the DB query and covers all of the SQL
queries possible.

This
component must be used as an output component. It allows you to carry
out actions on a table or on the data of a table in a AS/400 database.
It also allows you to create a reject flow using a Row > Rejects link
to filter data in error. For an example of tMysqlOutput in use, see [Retrieving data in error with a Reject link](https://help.qlik.com/talend/en-US/components/8.0/mysql/tmysqloutput-tmap-tfileoutputdelimited-tfileinputdelimited-retrieving-data-in-error-with-reject-link-standard-component-this). | | Dynamic
settings | Click the [+] button to add a row in the table
and fill the Code field with a context
variable to choose your database connection dynamically from multiple
connections planned in your Job. This feature is useful when you need to
access database tables having the same data structure but in different
databases, especially when you are working in an environment where you
cannot change your Job settings, for example, when your Job has to be
deployed and executed independent of Talend Studio.

The Dynamic settings table is
available only when the Use an existing
connection check box is selected in the Basic settings view. Once a dynamic parameter is
defined, the Component List box in the
Basic settings view becomes unusable.

For examples on using dynamic parameters, see [Reading data from databases through
context-based dynamic connections](https://help.qlik.com/talend/r/en-US/8.0/components/defining-context-groups/reading-data-from-databases-through-context-based-dynamic-connections) and [Reading data from different MySQL databases
using dynamically loaded connection parameters](https://help.qlik.com/talend/r/en-US/8.0/components/context/reading-data-from-different-mysql-databases-using-dynamically-loaded-connection-parameters). For more information on
Dynamic settings and context variables, see
[Dynamic schema](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/dynamic-schema) and [Creating a context group and define context
variables in it](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/creating-context-group-and-define-context-variables-in-it). | **Related concepts** * [Handling data with AS/400](https://help.qlik.com/talend/en-US/components/8.0/as400/tas400input-tas400output-tfixedflowinput-tlogrow-handling-data-with-as-400-standard-component-this)