You should only create or update a configuration file using the dbfhconfig command line utility.
set MFDBFH_CONFIG=<location-and-name-of-file>
If you do not set this variable, a file named MFDBFH.cfg is assumed to be located in the current directory.
dbfhconfig -add -server:<server-name> -provider:db2
where <server-name> is the name of the database server instance. An entry of localhost:<port> is also valid, which defaults to your machine name. If you have already updated the configuration file with the Db2 datastores, this entry will already exist, and you will receive a message informing you of this; you can skip to the next step.
Now specify the required databases within the instance.
dbfhconfig -add -server:<server-name> -dsn:<name> [-db:<existing-db>] [odbcdsn:<dsn-name>] -type:datastore -optio:<opts> -name:<dsname> [-user:<user-name>] [-password:<password>] [-bitism:<bit>] [-connect:<connection-string>]
where <name> is either the name you will give an ODBC data source for the datastore (in which case, make a note of it for a later step), or a unique name within the server configuration in which to reference the datastore if you are using a connection string; <existing-db> is the name of an existing database in which the datastore is stored - if this option is omitted, it is implied that the datastore is housed in its own database; <dsn-name> is the name of the data source used as a shared database connection (if you are using ODBC data sources and using a single physical database) - see Database Connections for more information; <opts> are the optimizations to be applied to I/O operations, <dsname> is the actual name of the datastore (as configured in the data source properties); <user-name> and <password> are valid credentials for the instance - you do not need to specify theses if you are using a connection string; <bit> is the bitism of the associated ODBC data source - you do not need to specify this if you are using a connection string; and <connection-string> is the database connection string if you are establishing a database connection without the use of an ODBC data source - see Database Connection Strings for the database-specific syntax.
| option | description |
|---|---|
| all | All optimizations applied, as if +<opt> had been specified for each available option. You can then selectively disable certain options using -<opt>. |
| none | No optimizations applied. |
| {+|-}oiseq | Enables (+) or disables (-) optimizations for line-sequential files opened for input. |
| {+|-}ooseq | Enables (+) or disables (-) optimizations for line-sequential files opened for output. |
| {+|-}oi | Enables (+) or disables (-) optimizations for ESDS, KSDS, and RRDS files opened for input. |
| {+|-}oo | Enables (+) or disables (-) optimizations for ESDS, KSDS, and RRDS files opened for output. |
The following is an example of a configuration file that contains a datastore, a region database, and a cross-region database, using direct connection syntax. As the login credentials are required to establish a connection to this database, the secrets vault has also been enabled: see Configure a Secrets Vault for the Micro Focus Database File Handler for more information.
<datastores usevault="true">
<server name="localhost:50000" type="db2" access="odbc">
<dsn name="DB2.VSAM" type="datastore" dsname="VSAM" optio="none +ooseq" dbname="MYMFFILS" connect="$$vault$$"/>
<dsn name="DB2.ESDEMO" type="region.cas" region="ESDEMO" feature="all" dbname="MYMFFILS" connect="$$vault$$"/>
<dsn name="DB2.CROSSREGION" type="crossregion.cas" dsname="$XREGN$" dbname="MYMFFILS" connect="$$vault$$"/></server>
</datastores>
Next, if you have not used connection strings in your database configuration file, you must create the data sources for each of the databases you have configured. If you have used connection strings, you can skip the data source creation and use the dbfhdeploy command line utility to upload files to your datastores.