The Micro Focus XDBC Local server is configured through a configuration file, mfdbc.cfg. This configuration file is where you define the location of your COBOL data files and system catalog, file case instructions, and other important program functions. You can create several different configuration files for different purposes. Configuration files must reside in your Micro Focus XDBC installation directory, specified by the GENESIS_HOME environment variable. You specify the exact name and path when setting up your DSNs on the client.
In a XDBC Local installation, mfdbc.cfg is the only configuration file that is required.
For mfdbc.cfg, you can use configuration variables from several key areas, as shown below. The DICTSOURCE and FILE_PREFIX variables are required. If you installed Micro Focus XDBC in a non-default directory, you must modify the DICTSOURCE and FILE_PREFIX variables in the client configuration file or generate a new configuration file with the mfgenconf batch or shell script file, which is included in your distribution to make the generation of configuration files easier. This utility takes the format:
mfgenconf [-d directory] [-c catalog] [-p prefix] [-n config_name]
|-d||Specifies the directory name to use for the GENESIS_HOME environment variable|
|-c||Specifies an optional directory name to use for the system catalog|
|-p||Specifies a location (path) to your data files|
|-n||Specifies a name for the configuration file that is created|
This utility will generate a configuration file for you with default values for the configuration options unless you override them with command-line parameters. Most of the settings are read from a template, sample\mfdbc\mfdbc.in, called from your install directory, so you will be able to use this to customize the generation settings for your site's particular needs.
The table below lists the configuration variables available, along with their defaults and brief descriptions. For complete descriptions, including examples, follow the links.
|DICTSOURCE||Install directory||Location (path) of your system catalog|
|FILE_PREFIX||Install directory||Location (path) of your data files
Note: If the value contains space(s), it should be enclosed in quotation marks. If the value can contain multiple directories that contain spaces, the entire entry should be enclosed in quotation marks.
|FILE_SUFFIX||None||Extension of your data files|
|FILE_CASE||Default (Mixed)||Indicates the file case of your data files|
|FILENAME_WILDCARD||None||Defines multi-company wildcards and their respective substitution characters|
|IGNORE_OWNER||0||Specifies whether you want the table owner to be included in a listing of tables|
|INVALID_NUMERIC_DATA||Error||Indicates how to treat non-numeric data in a numeric field|
|JULIAN_BASE_DATE||19000101||The base date for Julian date calculation|
|NULL_ALPHA_READ||Null||Defines how to read null alphanumeric data|
|NULL_ALPHA_WRITE||Spaces||Defines how to write null alphanumeric data|
|NULL_NUMERIC_READ||0||Defines how to read null numeric data|
|NULL_NUMERIC_WRITE||0||Defines how to write null numeric data|
|DATE_ZERO_VALUE||YYYYMMDDHHmmsshh (Year/Month/Day/Hour/Minute/Second/Hundredths)||When DATETIME = DATE_ZERO_VALUE, LOW-VALUES or all 0 are returned|
|DATE_NINE_VALUE||YYYYMMDDHHmmsshh (Year/Month/Day/Hour/Minute/Second/Hundredths)||When DATETIME = DATE_NINE_VALUE, HIGH-VALUES or all 9 are returned|
|DATE_NULL_VALUE||YYYYMMDDHHmmsshh (Year/Month/Day/Hour/Minute/Second/Hundredths)||DATETIME is SQL NULL, the value of the DATE_NULL_VALUE will be written to the COBOL data.|
|DATE_INVALID_VALUE||YYYYMMDDHHmmsshh (Year/Month/Day/Hour/Minute/Second/Hundredths)||When DATETIME = DATE_INVALID_VALUE, spaces will be written to the COBOL|
|DATE_MAX_HIGH_VALUES||HIGH-VALUES or 9||Setting to configure DATE_NINE_VALUE|
|DATE_MIN_LOW_VALUES||LOW-VALUES or 0||Setting to configure DATE_ZERO_VALUE|
|READ_ONLY||No||Read/write status of data files|
|DEBUG_LOGFILE||None||Name and location of the log file used for debugging|
|DEBUG_LOGLEVEL||0||The log level you desire for debugging|
Click here to view a sample configuration file mfdbc.cfg.