History Tables

Use the following parameters to customize the selected data source before you clone it. Configuration file parameters are included in parentheses.

Data set history tables

These parameters define the initial value of two data set property bits, which we show as History Tables (None, Save History, History Only). You can override a setting for individual data sets by changing the setting in the data set properties. The history_tables parameter applies to all three options.


No history tables are created.

Save history

Creates normal and history tables in the DATATABLES client control table. The normal table replicates the host data set. The history table contains a record of the updates, including the update type, the data for the update record, and the sequence. A data warehouse can receive the synchronized clone from the normal table first. History tables use the original table name with "_h" appended to it. After periodically importing the history table into the data warehouse, the history table can be purged.

Save history only

Creates only history tables. These tables receive cloned data and updates, in addition to records of the updates. The normal data table is not created or populated.


Enable dynamic history (enable_dynamic_hist)

Lets you add history tables without recloning all of the affected data sets. You can specify the default history columns in this dialog box (Customizing > User Columns). When you're done, you'll need to run the Reorganize command to create the history tables and their indexes.

Inhibit Drop (inhibit_drop_history)

Prevents the DATABridge Client from inadvertently dropping history tables during a clone, process, or drop command.

This is a safeguard to prevent an unrecoverable error. If you drop tables, it's recommended that you reselect this option when you restart the client.