Specify processing settings for the selected data source. Configuration file parameters are provided in parentheses.
Automatically reclone after table purge or garbage collection reorg (auto_reclone)
When selected, changes in DMSII record locations caused by reorganizations are handled automatically by recloning the data set as soon as AA values are discovered to be invalid.
Display active data sets only in display command (display_active_only)
Shows only active data sets when the Display command is selected.
Number of auxiliary (ODBC/OCI) statements (aux_stmts)
Set the number of database API (that is, ODBC or OCI) statements that can be assigned to individual SQL statements. Using multiple database API statements allows SQL statements to be parsed once and executed multiple times, provided the statement is not reassigned to hold another SQL statement. Increasing the number of database API statements significantly improves processing time, if your system has enough memory. A value of zero indicates that the Databridge Client should parse and execute all SQL statements using a single database API statement.
Note: Do not exceed the value of the open_cursors parameter defined in the database initialization file for the Oracle instance (initSID.ora, where SID is the name of the instance). The session uses one additional statement for all control table updates.
Rollback segment name (rollback_segment)
This parameter makes the client use the specified rollback segment by executing the SQL "SET TRANSACTION USE ROLLBACK SEGMENT Rollback_segment_name" at the start of every transaction. Applies only to Oracle client.
Audit unavailable action
Wait and retry (use_dbwait)
When this option is selected, 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. Select this option if you use real/time replication. Use the following two parameters to control the wait-and-retry loop.
Retry interval (in seconds) (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 that new entries written to the audit, it will start processing where it left off. Otherwise, it will wait until the next retry time.
Maximum wait time (in seconds) (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.
Store NULL DMSII numbers as (null_digit_value)
000... Stores NULL DMSII numbers as zeros (0).
999... Stores NULL DMSII numbers as nines (9).