Skip to content

Processing - General

This page defines run time options that do not require running a Configure or Redefine command to make them take effect.

Configuration file parameters are included below with the following_font.

Display only active data sets in display command

Parameter: display_active_only

This option affects the Log Control Tables command in the data source's Advanced button drop-down (equivalent to the display command when using the command-line Client).

When this option is enabled the command only shows the Client control table entries for data sets whose active column is 1. This results in a lot less output when you have a lot of data sets whose active column is 0. If this option is disabled, the control table entries for all data sets are displayed.

Number of auxiliary (ODBC/OCI) statements (0 minimum to 200 maximum)

Parameter: aux_stmts

Specifies the number of database API (that is, ODBC or OCI) statements that can be assigned to individual SQL statements. Using multiple statements allows SQL statements to be parsed once and executed multiple times, provided that the statement is not reassigned to hold another SQL statement. Increasing the number of database API statements significantly reduces processing time.

Audit unavailable action

Wait and retry

Parameter: use_dbwait

When this option is enabled, the Databridge Engine (DBEngine or Enterprise) enters a wait-and-retry loop when it reaches the end of the audit trail, instead of stopping the Client with an end-of-audit status. Enable this option if you use real/time replication.

Use the following two parameters to control the wait-and-retry loop:

  • Retry interval (in seconds)

    Parameter: max_retry_secs

    Specifies the time interval between retries by the Databridge Engine when it is in a wait-and-retry loop. If the Databridge Engine finds new entries in the audit, it will start processing from where it left off. Otherwise, it will wait until the next retry time and try again.

  • Maximum wait time (in seconds)

    Parameter: max_wait_secs

    Specifies the maximum amount of time that the Databridge Engine stays in a wait-and-retry loop before it stops the Client. A value of 0 for this parameter is interpreted as a request to the Databridge Engine to wait and retry forever.

  • Incremental wait time (in seconds)

    Parameter: max_wait_secs

    Enabling this option makes an input field visible. This input field is used to specify the incremental value of max_wait_secs that is optionally used to break up large wait times into smaller increments by making the Client repeatedly issue DBWAIT calls using this second value. The second value, which must be smaller than the first value (unless the first value is 0). For example, setting max_wait_secs to 3600,60 will result in the Client issuing a DBWAIT remote procedure call with a max_wait_secs value of 60 seconds.

    Upon getting a "no more audit available" return status, the Client will issue another DBWAIT call until it has received no updates for the amount of time indicated by the first parameter. This method ensures that an idle line has traffic, which makes it possible to detect situations where the network goes down and neither side knows about it. Upon receiving an update the Client resets the timer that keeps track of the time during which no updates are received. A value of 0 for this option makes the Databridge Engine handle the wait-and-retry loop without any involvement by Client.

Store NULL DMSII numbers as

Paramter: null_digit_value

000... Stores NULL DMSII numbers as zeros (0).

999... Stores NULL DMSII numbers as nines (9).

Caution

Do not change this parameter after you have cloned the DMSII database, as numeric columns that do not allow nulls will get different values when the data is NULL.