Advanced Parameters (Processing)

Specify processing settings for the selected data source. Configuration file parameters are provided in parentheses.

General

Automated virtual data sets (automate_virtuals)

Select this option to preserve the link between virtual data sets and the real data sets from which they are derived during a clone or process command. (This assumes that you have already set up links between the virtual data sets and the real data sets from which they are derived. You can use the Client Configurator to do this.) The client uses this link information to determine the processing order of data sets during data extraction and to ensure that whenever you select a virtual data set you also select its parent data set.

Enable optimized SQL updates (enable_optimized_sql)

Select this option if you want the Optimize SQL Updates property to be honored at run time. This option lets you disable the use of BI/AI records (and the number of updates) for data sets that have lots of items with unflattened OCCURS clauses, while avoiding the need to redefine the data source.

Preserve deleted records during a reclone (preserve_deletes)

Preserves deleted records when the data set is recloned.

Redefine all active data sets after a DMSII reorg (redef_all_active_ds)

Forces the Client to redefine all data sets after a DMSII reorganization is detected, even if the data sets aren't affected by the reorganization. This option prevents the Client from missing changes to the DASDL that do not cause the update level of a data set to change. A typical example is a change to the KEYCHANGEOK attribute of a SET that the client uses as a source for the index.

Multithreaded updates

Number of DMSII buffers (n_dmsii_buffers)

Specify the number of RPC buffers. Raising this value may improve performance by ensuring there are enough buffers queued to keep the update workers busy at all times.

Number of update threads (n_update_threads)

Specify the number of update threads, which are responsible for executing SQL to update the user tables. If you have disk arrays, setting this parameter to a high value will increase the update processing speed at the expense of additional memory. Avoid setting this parameter to 1, as this effectively passes off all updates to the single worker thread, when executing them directly is preferable.