AS/400 IBMi configuration parameters - 7.3

Talend Change Data Capture Installation Guide

Version
7.3
Language
English
Product
Talend Change Data Capture
Module
Talend Change Data Capture
Content
Data Governance > Third-party systems > Database components (Integration) > Change Data Capture
Data Quality and Preparation > Third-party systems > Database components (Integration) > Change Data Capture
Design and Development > Third-party systems > Database components (Integration) > Change Data Capture
Last publication date
2023-10-05

DD_USRDATA/DD_DAEMON data area

The DD_DAEMON data area contains the parameters for the IP daemon (engine that supports IP connections). It is also used on a source to know the parameters used to connect to the IP daemon. The parameters are separated from one another by a comma.

Parameter Description

Port

Contains the IP port that polls the Talend Change Data Capture IP daemon.

The default value is 1310.
Warning: If you modify this parameter, you must change it to the same value on all the machines (sources, targets, manager).
For more details, go to Changing TCP communications port section.

DataQueue

Not used in current application version.

PathServerPar

Not used in current application version.

PathServerRep

Not used in current application version.

TimeOut

This parameter contains the maximum time delay, expressed in seconds, during which the Talend Change Data Capture IP daemon must respond. The default value assigned during the installation is 300 seconds, i.e., five minutes.

DD_USRDATA/DD_CFG data area

The DD_CFG data area contains various parameters for the communication and the source and target engines.

The parameters are separated from each other by commas.

Parameter Description

MapFile

Contains the name of the table used to make conversions for non-AS/400 IBMi targets and to convert Unicode UCS-2 within AS/400 IBMi.

The default value is E297_AANSI.

TimeOut

This parameter contains the maximum time delay, expressed in seconds, during which the correspondent IP must respond.

The TimeOut management for the replication engine is "toggled" i.e., the TimeOut is sometimes applied to the source, and sometimes to the target.

The default value assigned during the installation is 300 seconds, i.e., five minutes.

TimeOutMax

This parameter contains the maximum time delay expressed in seconds, during which the target program must respond.

This parameter supplements the TimeOut parameter.

The target program may take more time to perform an action in the target database or to run a program or a script.

This parameter is used to allocate the maximum time for such long actions.

The default value assigned during the installation is 300 seconds, i.e., five minutes.

HollowUser

This parameter contains the name of the user that is invisible to the source engine.

Hollow means that all the journal sequences that have this username are just simply ignored by the source engine, regardless of sequence type.

This parameter is used to hide actions from the source engine.

The default value assigned during installation is "DD_HOLLOW".

Sleep

This parameter is used to indicate that the source engine must be dormant for n (0 to 9) cycles after each request for sequences made to the journal.

This is aimed at exchanging fewer blocks, but with greater volumes of data.

The end purpose is to drastically cut down CPU consumption (under 0.1%).

The default value assigned during installation is 0.

It is recommended that you test various values (0 to 9) before making your choice.

This value impacts all replications after you restart.

TraceCom

This parameter specifies to the source and target engines running on this machine that you want to track the communications through the data packets sent and received. The trace is generated in a file called See_cccddd on the source and Ree_sssddd on the target (where ee is the environment ID, ccc the target ID, sss the source ID, and ddd the distribution ID). You cannot use this parameter in conjunction with the trace records enabled by the manager. To enable or disable the trace, you must restart the engines. The trace records generated may be very bulky. Sample trace:
Processor time in milliseconds <===> (direction), Size in octet
                                0 ===> Receive size=32276
                                0 <=== Send size=146
                                78 ===> Receive size=32276
                                93 <=== Send size=418
                                172 ===> Receive size=32276