Configuration file options override environment variables. Command-line options override both environment variables and configuration file options.
The parameter processing order is as follows:
- In Windows, the environment variable (USERNAME) is used as the lowest level default for the user ID. In UNIX, the login name is used as the lowest level default.
- Environment variables (DBUSERID, DBPASSWD, DBDATABASE, and DBHOSTPW).
- Command-line options -d (for full tracing), -v (for verbose messages), -t (for creating a DATABridge Client trace file) and -T (for specifying a trace filename prefix), 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.
- 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 -f option, dbutility 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.
- All remaining command-line options. In the final pass, a command-line option with a configuration file equivalent overrides the configuration file entry.