HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide

[Contents][Glossary][Index][Back][Next]

hdeprep (create an extraction definition preprocessing file)

In the Windows edition of Datareplicator or HiRDB version 08-02 or later, execute this command from the source HiRDB's command prompt.

Function

The hdeprep command analyzes the contents of the extraction definition file, converts it to the internal format, and creates an extraction definition preprocessing file.

Format
hdeprep -f extraction-definition-filename[ -u user-ID/password ]
      [ -k {not_null_unique|unique|none}]

Options

-f extraction-definition-filename
~ <pathname of 1-64 bytes>
Specify the name of the extraction definition file, as an absolute or relative pathname. If you specify a relative pathname, Datareplicator assumes $HDEPATH/relative-pathname as the absolute pathname. In this case, specify the pathname so that the final absolute pathname will not exceed 125 bytes.

-u user-ID/password
user-ID ~ <symbolic name of up to 8 characters>
password ~ <symbolic name of up to 28 characters>
Specify the user ID and password of a user who has the DBA privilege for the source Datareplicator. Both user ID and password are case-sensitive. Do not specify any spaces before or after the delimiter slash (/). For the user ID, specify a symbolic name of 1 to 8 characters; for the password, specify a symbolic name of 1 to 28 characters.
If you omit the -u option, Datareplicator assumes the value of the PDUSER environment variable for the source HiRDB. If this environment variable is not specified, the hdeprep command results in an error during connection establishment processing with the source HiRDB.

-k {not_null_unique|unique|none}
Specify the condition for unique check on the mapping key column.
This value becomes the default when the check clause is omitted in the extraction definition. The specification values and the details of checking are the same as for the check clause of the extraction definition. For details, see the check clause under Explanation of the operands in 5.5 Extraction definition.
If the specified condition is not satisfied, the command terminates abnormally. When this option is omitted, not_null_unique is assumed.

Rules

Notes