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.

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.

DB Version

Select the AS/400 database version you are using.

Host name

Database server IP address.

Database

Name of the CDC database.

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.

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.

Subscriber

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.

Member

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.

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.

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.

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.

Usage rule

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:

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.