Appendix

This appendix lists the configuration parameters for Databridge Flat File Client. Refer to Appendix C: Client Configuration in the Databridge Client Administrator's Guide for a complete description of Client Configuration files.

Client Configuration Files

The Databridge Flat File Client uses binary configuration files. Binary configuration files are compatible with both service-initiated operations and command-line operations. However, if you use the service, you must use binary configuration files. (Command-line operations can use either binary or text configuration files, although we recommend always using binary configuration files. The configuration file is named "dbridge.cfg" and it resides in the "config" subdirectory of the data source\'s working directory.

Command-Line Options

The following command-line options have no equivalent configuration parameter:

Syntax

Follow these conventions in the configuration file:

• For hexadecimal values, use the 0xnnnn format.

• A semicolon (;), except within double-quoted strings, indicates that the remainder of the current line is a comment.

• Enclose section headers in square brackets.

• Section headers and parameter names are not case-sensitive.

• Spaces and tabs between entries are ignored; however, spaces within double quoted values (for example, password values) are read.

• If you are not using a parameter, either comment the parameter out or delete the corresponding line in the configuration file. Do not leave an uncommented parameter without a value after the equal sign (=). Doing so results in syntax error.

You can specify some of these parameters only in the Client configuration file. Other parameters have equivalent command-line options. For a complete list of configuration file parameters, their equivalent command-line options, and their related Client command, see [params].

Sample Flat File Client Configuration File

You can view the configuration file by using the export command. Refer to the Databridge Client Administrator's Guide for details on the export command.

To use a parameter that is commented out, delete the semi-colon ( ; ) and after the equals sign (=) enter a value that is appropriate for your site. Boolean parameters can be represented by True or False.

In the example below, some of the commented-out parameters have a value of -1. These parameters include the DBEngine control file parameters that can be overridden by the client (commit frequency parameters and engine workers). This value indicates that the corresponding parameter in the Databridge Engine (or Server) control file will not be overridden by the Client. Do not uncomment these lines, unless you want to supply an actual value. Otherwise, the Client will issue an error.

;
; Databridge Client Version 7.1 Flat File configuration file -- generated programmatically
;

[Signon]
;user                   = USERID
;password               = PASSWORD
;datasource             = DATASOURCE
;hostpasswd             = HOSTPASSWD

[Log_File]
file_name_prefix        = "db"
;max_file_size          = 0
logsw_on_size           = false
logsw_on_newday         = false
newfile_on_newday       = true
single_line_log_msgs    = false

[Trace_File]
file_name_prefix        = "trace"
;max_file_size          = 0

[PCSPan]
;
;  (1) DMSII data redaction parameters
;
redacted_database        = 0
;
;  (2) Flat File client parameters
;
add_item_names          = false
add_nl_chars            = false
decimal_char            = "."
delimiter               = ","
extracts_dir            = ""
filename_mask           = csv
fixups_dir              = ""
format                  = csv
ltrim_zeroes            = true
prefix_columns          = 0x00000000
quote                   = "'"
real_format             = scientific,11,6
rtrim_spaces            = true
span_date_delim         = ""
span_date_format        = 21
span_date_scale         = 0
treat_real_as           = real
updates_dir             = ""
use_plus_sign           = false
use_quotes              = true
;
[Params]
;
;  (1) define/redefine command parameters
;
allow_nulls             = true
automate_virtuals       = false
convert_ctrl_char       = false
default_user_columns    = 0x00000000
enable_dms_links        = false
;external_column[n]     = ["name"][,[sql_type][,[sql_length][,"default"]]]
extract_embedded        = false
flatten_all_occurs      = false
force_aa_value_only     = 0
miser_database          = true
read_null_records       = true
sec_tab_column_mask     = 0x00000000
split_varfmt_dataset    = false
strip_ds_prefixes       = false
suppress_new_columns    = false
suppress_new_datasets   = true
use_binary_aa           = false
use_column_prefixes     = false
use_date                = true
use_decimal_aa          = false
use_nullable_dates      = true
;
; (2) process/clone command parameters
;
alpha_error_cutoff      = 10
;batch_job_period       = 00:00, 00:00
century_break           = 50
;commit_absn_inc        = -1
;commit_idle_database   = -1
;commit_longtrans       = -1
;commit_time_inc        = -1
;commit_txn_inc         = -1
;commit_update_inc      = -1
controlled_execution    = false
;convert_reversals       = -1
correct_bad_days        = 0
dbe_dflt_origin         = direct
defer_fixup_phase       = false
discard_data_errors     = false
display_bad_data        = false
enable_doc_records      = false
;engine_workers         = -1
error_display_limits    = 10,100
inhibit_8_bit_data      = false
inhibit_console         = false
inhibit_ctrl_chars      = false
keep_undigits           = false
linc_century_base       = 1957
max_discards            = 0,100
max_retry_secs          = 20
max_srv_idle_time       = 0
max_wait_secs           = 3600,60
min_check_time          = 600
n_dmsii_buffers         = 0
n_update_threads        = 8
null_digit_value        = 9
numeric_date_format     = 23
preserve_deletes        = false
set_blanks_to_null      = false
set_lincday0_to_null    = false
show_perf_stats         = true
show_statistics         = true
show_table_stats        = true
sql_exec_timeout        = 180,0
statistics_increment    = 100000,10000
stop_after_fixups       = false
stop_after_gc_reorg     = false
stop_after_given_afn    = false
stop_on_dbe_mode_chg    = false
track_vfds_nolinks      = true
use_dbwait              = false
use_latest_si           = false
;
; (3) Server options
;
;shutdown {until | for} hh:mm after stop
;stop {before | after} task "name"
;stop {before | after} time hh:mm[:ss]
;
; (4) miscellaneous command parameters
;
display_active_only     = true
;
; (5) user scripts
;
user_script_bu_dir      = ""
user_script_dir         = "scripts"
;
; (6) external data translation parameters
;
use_ext_translation     = false
eatran_dll_name         = "DBEATRAN.DLL"

[Scheduling]
;
; dbutility process command only
;
;daily                  = 08:00, 12:00, 17:00, 24:00
;exit_on_error          = false
;sched_delay_secs       = 600
;sched_minwait_secs     = 3600
;sched_retry_secs       = 3600

[EbcdicToAscii]
; e1 = a1
; e2 = a2
;  ...
; en = an
;

[DBConfig]
default_date_fmt        = 21
global_type0_changes    = true

[Encryption]
ca_file                 = ""
ca_path                 = ""
certify_server_name     = false
enable_encryption       = false
tls_host_name           = ""

Processing Order

Command-line options override configuration file options.

The parameter processing order is as follows:

1. The operating system login name (user ID) is used as the lowest level default for the database user ID

2. Command-line options -d (for full tracing), -v (for verbose messages), -t(for creating a Databridge Client trace file) and -T (for forcing the client to start a new trace file), and -f (for specifying a configuration file other than the default dbdridge.cfg). These options are processed in the order in which they appear on the command line.

3. Parameters specified in the configuration file. You can specify the configuration file via the -f option. If you do not specify a configuration file name via the -foption, the Databridge Client tries to open the default configuration file ( dbridge.cfg in the config subdirectory of the data source\'s working directory); if the file does not exist, the Databridge Client uses the default values for each configuration file parameter. The absence of a configuration file is not treated as an error only when running the command-line client. If you use the service or daemon, the absence of a configuration file named dbridge.cfg is treated as an error.

4. All remaining command-line options. In the final pass, a command-line option with a configuration file equivalent overrides the configuration file entry.