{{ extract DBM-name.dataset-name
    ({ { field-name|redefined-field-name }
    [ {{,{ field-name|redefined-field-name }}} ...]|* })
  to update-information-name
  key({ field-name|redefined-field-name }
  [{{ ,{ field-name|redefined-field-name }}} ...])}} ...

• extract DBM-name.dataset-name
  ~ <symbolic name of 1-6 characters>
  In the case of the PDM2 E2 log format, specify the DBM name and dataset name. In the case of a variable dataset using the coded record facility, specify the dataset name followed by the value of the record code.
  
• field-name|redefined-field-name
  field-name ~ <symbolic name of 1-30 characters>
  

Specify a field name or a redefined field name. You can specify the field names in any order, but you must not specify the same name more than once. The all-columns specification (*) is permitted only when there are no extraction redefinition statements.

• to update-information-name
  ~ <symbolic name of 1-8 characters>
  Specify a name for the extracted update information. This update information name must be unique among all extraction statements contained in the update information definition.
  
• key field-name|redefined-field-name
  field-name ~ <symbolic name of 1-30 characters>
  Specify the name of a field or redefined field corresponding to the mapping key. All fields and redefined fields specified in the key clause must have been specified in an extract statement. If the all-columns specification (*) is used in the extract statement, each field name must be unique in the PDM2 E2 definitions.
  

• You cannot extract only a mapping key column.
• You must specify the DBM, dataset, and field names in uppercase letters.
• Redefined field names and update information names are case-sensitive.
• To specify a Datareplicator reserved word as a DBM, dataset, field, or redefined field name, you must enclose the name in double quotation marks ("). For details about the Datareplicator reserved words, see Appendix B. Datareplicator Reserved Words.
• The field and redefined field names specified in the extract operand must be unique column names. The field and redefined field names in the key operand must also be unique.
• If you update the mapping key, import processing might result in an error (no data with matching key value) or data might be imported into an unexpected row, because the target system uses the updated data as the key. For this reason, it is not advisable to update the mapping key.
• You can specify a maximum of 16 mapping key columns in the key operand.
• If you specify a column with either of the following attributes, you must check that the column length does not exceed 255 bytes:
  
  • CHAR
  • NCHAR