tAS400CDC properties - 6.1

Talend Components Reference Guide

Talend Big Data
Talend Big Data Platform
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Open Studio for Big Data
Talend Open Studio for Data Integration
Talend Open Studio for Data Quality
Talend Open Studio for ESB
Talend Open Studio for MDM
Talend Real-Time Big Data Platform
Talend Studio
Data Governance
Data Quality and Preparation
Design and Development

Component family

Databases / AS/400



tAS400CDC extracts data from a source system that has changed since the last extraction and transports it to another/other system(s). By default, this component automatically calls the AS/400-dedicated program RUNCDC to write the latest update information into a change table (a CDC table) and runs queries in the same table to read changes.

Note that the RUNCDC program is automatically installed by the Studio using a savf script stored in the following directory:


For further information about this fitcdc.savf script and the command used to install the RUNCDC program, see the section describing how to set up CDC in Redo/Archive log mode (journal) for AS/400 in Talend Studio User Guide


tAS400CDC addresses data extraction and transportation needs. tAS400CDC only extracts the changes carried out on the source operational data and makes them available to the target system(s) using database CDC views.

Basic settings

Use an existing connection

Select this check box and in the Component List click the relevant connection component to reuse the connection details you already defined.


When a Job contains the parent Job and the child Job, if you need to share an existing connection between the two levels, for example, to share the connection created by the parent Job with the child Job, you have to:

  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 Talend Studio User Guide.


Property type

Either Built-in or Repository



Built-in: No property data stored centrally.



Repository: Select the repository file in which the properties are stored. The fields that follow are completed automatically using the data retrieved.


Reset the DB type by clicking the relevant button to select the CDC connection.


DB Version

Select the AS/400 database version you are using.


Host name

Database server IP address.



Name of the CDC database.


The CDC database in which are stored the modified data must be different from the one containing the source data.


Username and Password

DB user authentication data.

To enter the password, click the [...] button next to the password field, and then in the pop-up dialog box enter the password between double quotes and click OK to save the settings.


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. The schema is either Built-In or stored remotely in the Repository.

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



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


Reset the DB type by clicking the relevant button to select the schema of the CDC connection.


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.


Table Name

Short name of the source table where changes made to data should be captured. The target CDC table uses automatically this short name to name itself.


Source Library

The AS/400 database's source library.


The library name must not contain more than 10 characters. The database name is generally used.



Enter the name of the application that will use the change table.


Events to catch

Insert: Select this check box to catch the data inserted in the change table since the last extraction.

Update: Select this check box to catch the data updated in the change table since the last extraction.

Delete: Select this check box catch the data deleted in the change table since the last extraction.



Enter the name of the member that holds the desired records. A member is part of a physical file in the library and contains a group of entries. For details, search format of an AS/400 file at http://www.ibm.com.

Advanced settings

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.


Keep data in CDC Table

Select this check box to keep the changes made available to one or more target systems, even after they have been consulted.


Trim all the String/Char columns

Select this check box to remove leading and trailing whitespace from all the String/Char columns.


Trim column

Remove leading and trailing whitespace from defined columns.


Deselect Trim all the String/Char columns to enable Trim columns in this field.


Disable command

Select this check box to be able to manually call the RUNCDC program by yourself to write changes to the CDC table.


Customize command

Select this check box to write custom commands that override the default commands used by tAS400CDC.

For example, tAS400CDC by default executes the following command:

<CDC_library_name>/RUNCDC FILE(<Source_library_name>/<Source_table_name>) LIBOUT(<CDC_library_name>) MODE(*DETACHED) MBROPT(*ADD)

This command does not automatically detach a receiver from its corresponding journal and cannot create and attach a new one to that journal, either. In this situation, you can enter your customized command as follows to automate the detachment and attachment process:

<CDC_library_name>/RUNCDC FILE(<Source_library_name>/<Source_table_name>) LIBOUT(<CDC_library_name>) MODE(*DETACHED) MBROPT(*ADD) DTCHJRN(*YES)

Note that the name of the CDC library is often the name of the CDC database.


tStatCatcher Statistics

Select this check box to collect log data at the component level.


This component is used as a start component. It requires an output component and row Main link.

Note that the journal and the receiver required by CDC are typically controlled by the administrator of the AS/400 system. For this reason, since version 5.4.2 (included) of the Studio, tAS400CDC runs the RUNCDC program only and does not automatically create, activate, deactivate, modify or delete any journal or receiver of that AS/400 system any more. You need to contact the AS/400 administrator before performing any of these operations. Depending on the policy in your company, the administrator will either perform the operation or provide you with the authorization to do it yourself.

Because of this behavior updates, since 5.4.2, the tAS400CDC component does not execute the following command as it did in the 5.4.1 or earlier versions:

CHGJRN JRN(<Source_library_name>/<Source_table_name>) JRNRCV(*GEN)

This command is used to ensure that an older receiver is detached from a journal and a newer one is attached to the journal to retrieve the last change. You are then recommended to execute this command in your AS/400 system before running this component. Alternatively, enter the example command given above for the Customize command check box is selected, in order to automate the detachment and attachment process.

For further information about how the CDC for AS/400 is handled by the Studio since version 5.4.2, see the sections describing the CDC architecture and how to set up CDC in Redo/Archive log mode (journal) for AS/400 in Talend Studio User Guide.


If you are using a subscription-based version of the Studio, 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.