The following figure shows an example of importing a source table into an identical table that has the same table format, table name, column names, and so on.

Figure 4-1 Example of importing into an identical table

Explanation

• Tables subject to processing
  At the source, use the extraction statement in the extraction definition to specify the source table, in authorization-identifier.table-identifier format.
  At the target, use the to clause of the import table definition to specify the target table, in authorization-identifier.table-identifier format.
  
• Columns to be extracted
  At the source, use the extraction statement to specify the columns to be extracted. To extract all columns without sorting them, you can use the asterisk (*) in place of the column names.
  
• Name of the update information
  Define with a single extraction statement an extraction condition for the single table. Use the to clause of the extraction statement to define a name for the update information that is to be extracted based on this extraction condition; this name is called the update information name. To specify multiple extraction conditions for a single table, specify one extraction statement for each extraction condition.
  
• Destination of the extracted update information
  Specify with the send statement in the extraction definition the destination of the extracted update information. Use the send statement to specify one update information name for each destination. To specify multiple update information names for a single destination, specify one send statement for each update information name that is to be sent.
  
• Mapping keys
  Mapping keys are used to identify the rows to be extracted or imported. You must establish the correspondence of the mapping keys between the source and target tables. You use the key clause of the extraction statement to specify the mapping key.
  
• Omitting the import definition
  You can omit the import definition in this example because it imports a table into an identical table (same table and column names). When you omit the import definition, Datareplicator uses the extraction definition for the import definition and executes data linkage. Note that the assumed authorization identifier, table identifier, and column names depend on the source database. The following table shows the values that are assumed for these items when the import definition is omitted.
  

  Table 4-3 Values assumed for the authorization identifier, table identifier, and column names when the import definition is omitted

  Source database							Target database
  HiRDB	XDM/SD E2#	XDM/RD E2	ADM	PDM2 E2	TMS-4V/SP	RDB1 E2	HiRDB
  Authorization identifier	Schema name	Authorization identifier	Database name	DBM name	Authorization identifier	Authorization identifier	Authorization identifier
  Table identifier	Least significant record type name	Table identifier	Segment	Dataset name	Table identifier	Table identifier	Table identifier
  Column name	Component name	Column name	Field name	Field name	Column name	Column name	Column name

#: If the component name and the redefined item name specified with the RESTRUCT statement in the extraction redefinition are not unique within the same extraction definition, you cannot omit the import definition because the import table corresponding to the redefined item name cannot be defined.

The following figure shows an example of importing a source table by changing the table name or column names.

Figure 4-2 Example of importing by changing the table name or column names

Explanation

• Changing the column names definition
  Define the new column names in name clauses in the update information field definition. You must define in these clauses all field names in the update information. Of the field names defined here, specify in the load statement in the import table definition those fields that are subject to import processing. If you are importing all fields in the same sort order, you can omit the update information field definition.
  
• Changing the table name or column names
  Specify the new column names in the load statement in the import table definition and specify the new table name in the to clause.