Cloning Specific Data Sets

To clone specific data sets via the dbutility clone command

  1. Make sure that DBServer or DBEnterprise is running. If it is not, the DATABridge Client tries to connect to the server and eventually times out.
  2. Make sure that your signon parameters are configured appropriately.
  3. If you plan to use the [EbcdictoAscii] section to customize character translation or any other parameters in the dbridge.cfg file, set them before you continue. In particular, make sure you have appropriate settings for the following parameters. (For information on setting these parameters, see Appendix D.)

    For Microsoft SQL Server:
    bcp_date_format

    For Oracle and DB2:
    bcp_delim
    bcp_decimal_char

    For all relational databases:
    show_statistics
    statistics_increment
    show_perf_statistics
    show_table_stats
    max_temp_storage (Windows only)
    max_clone_count
    controlled_execution
    min_check_time
    stop_after_given_afn
    defer_fixup_phase
    stop_after_fixups
    linc_century_base
    inhibit_ctrl_chars
    inhibit_8_bit_data
    convert_ctrl_char
    error_display_limits
    discard_data_errors
    suppress_dup_warnings
    display_bad_data
    century_break
    enable_optimized_sql
    use_ext_translation
    eatran_dll_name

  4. Enter the following command:

dbutility [signon_options misc_options] clone datasource datasetname1 [... datasetnamen]

Where

Is

signon_options

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]

Oracle:

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

misc_options

Any of the following miscellaneous command line options:

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

-T fileprefix to specify a prefix to be used instead of the default trace prefix ("trace")

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

-c (toggle defer_fixup_phase in dbridge.cfg)

-s (max_clone_count in dbridge.cfg). For DB2 databases, you must use the -s option if you want to use the use_binary_AA parameter.

datasource

The name of the source specified in the DBServer control file or by Enterprise Server.

datasetname1
[... datasetnamenn]

The names of the data sets you want to clone. You must specify at least one data set name. If you specify more than one data set name, separate the names with spaces.

Note the following:

  • The data set names you enter must match the names of the data sets as they are defined in the DASDL for the DMSII database. DATABridge Client automatically converts them to uppercase for you. For example, if the data set you want to clone is named ORD-DETAIL, you must type ORD-DETAIL or ord-detail. You must use a hyphen (-), not an underscore (_).
  • The exact data set names are listed in the DATASETS client control table.
  • If a DMSII data set is a relational database reserved word, enter it normally without quotes or any other delimiter.
  • If you specify a data set that has variable-format records, all record types are cloned except for those that have a corresponding active column of 0 in the DATASETS client control table.
  • The active column of the selected data sets must be set to 1. Otherwise, an error appears when you specify the data set at the command line.

If for some reason the clone command abends, do not rerun it before you determine whether or not some of the data sets completed the data extraction phase and are recoverable. Rerunning the clone command starts the cloning operations from scratch.