Generating DATABridge Client Scripts

In this phase, the DATABridge Client generates the script files that are used to create the DATABridge data tables in the relational database and to run the database bulk loader utility to populate them during the data extraction phase.

The generate command creates scripts only for those data sets that have an active column set to 1 in the corresponding entry in the DATASETS client control table. The DATABridge Client keeps track of the data sets that have generated scripts. These scripts will only be generated again if a redefine command is executed or if a define command determines that the layout of a table has changed. If you need to force the DATABridge Client to generate the scripts for all data sets that have a corresponding active column value of 1 in the DATASETS client control table, you can specify the -u option on the command line for the generate command.

To view a list of the scripts that are generated, see Summary of Script Files.

To generate the DATABridge Client scripts

  1. If you plan to use the dbridge.cfg file for signon parameters, set them before you continue. (See the DATABridge Installation Guide.)
  2. Make sure that the following parameters, which affect the generate command, are set correctly in the appropriate section of the Client configuration file:

    [params]
    global_table_suffix
    global_table_suffix
    create_table_suffix
    create_index_suffix

    [bulk_loader]
    bcp_batch_size
    bcp_packet_size
    bcp_code_page
    bcp_copied_message
    sqlld_rows
    sqlld_bindsize
    inhibit_direct_mode
    enable_parallel_mode
    sqlldr_name
    max_errors

    Note: For your changes to take effect, you must run the generate command again and specify the -u option to force the program to regenerate the scripts.

  3. Enter the following command:

    dbutility [signon_options misc_options] generate datasource

    Where

    Is

    signon_options

    The command line options (for each DATABridge Client type) that sign on to the relational database.

    SQL Server or DB2:

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

    Oracle:

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

    misc_options

    Any of the following miscellaneous command line options:

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

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

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

    -u, unconditionally generates scripts for all tables mapped from data sets that have a corresponding active column value of 1 in the DATASETS client control table.

    See dbutility Command-Line Options.

    datasource

    The name that matches the entry in the DATASOURCES client control table. You can enter the data source name in uppercase or lowercase.

    Status messages indicate the progress of the command.

  4. To check on the results of the generate command, see Summary of Script Files. For information on when to run generate next, see When to Run dbutility generate.

    At this point, you are ready to run a process or clone command to create and populate the DATABridge tables in the relational database with DMSII data. See Populating the DATABridge Data Tables.