17.00 - Syntax - Parallel Data Pump

Teradata® Parallel Data Pump Reference

prodname
Parallel Data Pump
vrm_release
17.00
created_date
June 2020
category
Programming Reference
featnum
B035-3021-220K


where the following is true:

layoutname
Name assigned to the layout for reference by one or more subsequent IMPORT commands.
A layoutname must obey the same rules for its construction as Teradata SQL column names.
The name specified also may be used in the LAYOUT clause of an IMPORT command.
MACROCHARSET
An optional clause on the layout command. If no field-level MACROCHARSET is present for a field of character type, but a layout-level MACROCHARSET is present, TPump generates a CHARACTER SET clause in the macro creation DDL for the corresponding field using the specified layout character set.
servercharsetname
Server storage character set name. The following two documents are for the valid server storage character set names: Teradata Vantage™ - Advanced SQL Engine International Character Set Support, B035-1125 and Teradata Vantage™ - SQL Data Definition Language Syntax and Examples, B035-1144.
CONTINUEIF condition
following:
position = value
where position is an unsigned integer (never an asterisk) that specifies the starting character position of the field of every input record that contains the continuation indicator, and where value is the continuation indicator specified as a character constant or a string constant. Teradata TPump uses the length of the constant as the length of the continuation indicator field.
In the CONTINUEIF option, the condition specified as position = value is case-sensitive; verify that the correct case has been specified for this parameter.
If the condition is true, Teradata TPump forms a single record to be sent to the database, by concatenating the next input record at the end of the current record. (The current record is the one most recently obtained from the external data source.)
If the condition parameter is false, Teradata TPump sends to the database, the current input record either by itself, or as the last of a sequence of concatenated records.
Note that the starting position of the continuation indicator field is specified as a character position of the input record. Character positions start with character position one. Teradata TPump removes the continuation indicator field from the input records so that they are not part of the final concatenated result.
For other fields whose startpos is specified as an unsigned integer, the startpos refers to the field position within the final concatenated result. Consequently, the continuation indicator field cannot be defined as all or part of a field defined with the FIELD, FILLER, or TABLE commands. Refer to the startpos parameter of the FIELD command.
When the character set of the job script is different from the client character set used for the job (for example, on z/OS the job script must be in Teradata EBCDIC when using the UTF-8 client character set, or UTF-16 client character set can be used with the job script in UTF-8), Teradata TPump translates the specified value, which is either a character constant or a string constant, from the script character set form to the client character set form before evaluating the condition. Teradata TPump uses the length of the constant in the client character set form as the length of the continuation indicator field.
When using the UTF-8 client set on the mainframe, be sure to examine the definition in Teradata Vantage™ - Advanced SQL Engine International Character Set Support, B035-1125 to determine the code points of the special characters required. Different versions of EBCDIC do not always agree as to the placement of these characters.
The mappings between Teradata EBCDIC and Unicode can be referred to Teradata Vantage™ - Advanced SQL Engine International Character Set Support, B035-1125.
INDICATORS
Condition that the data is in the indicator mode
This means that the first n bytes of each record are indicator bytes, where n is the rounded-up integer quotient of the number of fields defined by this LAYOUT command for transmission to the database, divided by 8.
Teradata TPump sends all the FIELD commands, including redefines, to the database. If a field has been defined and then redefined, indicator bits must be set for both. FILLER commands also need to have indicator bits set. Teradata TPump sends both the defined and the redefined fields to the database. This demonstrates the inefficiency of redefines which cause the transfer of an extraneous field.
If INDICATORS is specified on the LAYOUT command and the data file does not contain indicator bytes in each record, the target table will be loaded with spurious data. Conversely, if INDICATORS is not specified and the data file contains indicator bytes in each record, the target table will likewise be corrupted. Exercise caution to guard against either occurrence.
A LAYOUT command that includes the INDICATORS option must accurately describe all fields of the record to agree with the column descriptions and ordering of the table from which this indicator-mode data was previously selected. If the INDICATORS option is specified, Teradata TPump sends the data to the database with indicators.
The NULLIF parameter of the FIELD command can be specified with or without the INDICATORS option. If NULLIF is specified, Teradata TPump sends the data to the database with indicators, whether or not the INDICATORS option is specified.