Creating Client Control Tables

Use this procedure to create a set of control tables in a new installation.

When you upgrade your DATABridge Client software, the dbfixup program updates your control tables to the current version. It unloads your previous Client control tables to a file, recreates them using a configure command, and then restores them from the unload file.

Client control tables contain information about the data sets in a DMSII database and information about the corresponding tables and their layout in the relational database. These tables are stored and maintained in the relational database.

To run dbutility configure

  1. Make sure that the database software and the appropriate Windows services or UNIX processes are running. For more information, see your relational database documentation.
  2. Make sure that the current directory is the working directory for the data source (DMSII database) that you are cloning. For details about the working directory, see the DATABridge Installation Guide.
  3. From a Windows Command Prompt or UNIX terminal session, enter the following:

    dbutility [signon_options misc_options] configure




    For each DATABridge Client type, the following command-line options sign on to the relational database:

    SQL Server or DB2:

    [-U userid] [-P password] [-O ODBCdatasource]


    [-U userid] [-P password] [-D database]


    Any of the following miscellaneous command line options:

    -T fileprefix to specify a prefix to be used instead of the default trace file prefix.

    -f filename to specify a configuration file other than the default dbridge.cfg file in the config subdirectory of the Client working directory.

    -L forces the client to use a new log file for this run.

    -u, if you want to override conditions that dbutility would otherwise interpret as a possible user error. For example, you may want to create a second set of control tables within one relational database (these must be owned by a different user), or you might want to drop and re-create the control tables, removing all of the state information associated with the user tables.

    In most cases you do not need the -u option.

    Note: You only need to run dbutility configure once, unless you drop your tables via the dbutility dropall command and have to start over.

  4. (Optional) To display the tables created by dbutility configure, use a utility appropriate for your relational database. For example, for Microsoft SQL Server you can use the Query window of SQL Server Management Studio to enter the following:

    select name from sysobjects where type = "U" order by name

    For Oracle, you can use the SQL*Plus utility and enter the following:

    select table_name from user_tables order by table_name