Specify a Character Set - Parallel Data Pump

Teradata Parallel Data Pump Reference
Product
Parallel Data Pump
Release Number
15.10
Language
English (United States)
Last Update
2018-10-07
dita:id
B035-3021
lifecycle
previous
Product Category
Teradata Tools and Utilities

Specify a Character Set

Table 16 describes ways to either specify the character set or accept a default specification.

 

Table 16: Ways to Either Specify a Character Set or Accept a Default Specification 

Specification or Default Selection

Description

Runtime parameter specification

Use when Teradata TPump is invoked, as described earlier in this chapter:

  • charset=charactersetname for mainframe‑attached z/OS client systems
  • ‑c charactersetname for network‑attached client systems for UNIX OS and Windows

    • Client System Specification

    Specify the character set for a client system before invoking Teradata TPump by configuring the:

  • HSHSPB parameter for mainframe‑attached z/OS client systems
  • clispb.dat file for network‑attached client systems for UNIX OS and Windows

    • Note: The charactersetname specification used when Teradata TPump is invoked always takes precedence over the current client system specification.

    Teradata Database Default

    If a charactersetname specification is not used when Teradata TPump is invoked, and there is no character set specification for the client system, Teradata TPump uses the default specification in the Teradata Database system table DBC.Hosts.

    Note: If the DBC.Hosts table specification for the default character set is relied upon, make sure that the initial logon is in the default character set:

  • EBCDIC for mainframe‑attached z/OS client systems
  • ASCII for network‑attached client systems for UNIX OS and Windows

    • Teradata TPump Utility Default

    If there is no character set specification in DBC.Hosts, then Teradata TPump defaults to:

  • EBCDIC for mainframe‑attached VM and z/OS client systems
  • ASCII for network‑attached client systems for UNIX OS and Windows

    • Character Set Specifications for AXSMODs

    When an AXSMOD is used with Teradata TPump, the session character set is passed as an attribute to the AXSMOD for possible use. The attribute value is a variable‑length character string with either the character set name or the character representation of the character set ID. The attribute varies based on how the character set is specified.

    Table 17 contains a list of specifications for AXSMOD.

     

    Table 17: Character Set Specifications for AXSMOD 

    Specify the session character set by

    Attribute name is

    ID

    CHARSET_NUMBER

    name

    CHARSET_NAME

    Multibyte Character Sets

    Teradata Database supports multibyte characters in object names when the client session character set is UTF‑8 or UTF‑16. Refer to International Character Set Support (B035‑1125) for a list of valid characters used in object names. If multi-byte characters are used in object names in Teradata TPump script, they must be enclosed in double quotes.

    Multibyte character sets impact the operation of certain Teradata TPump commands, as well as object names in Teradata SQL statements.

    Table 18 describes the impact on multibyte character sets on certain Teradata TPump commands.

     

    Table 18: Character Sets Impact on Teradata TPump Commands 

    Teradata TPump Command

    Affected Element

    Impact

    ACCEPT

    Utility variables

    The utility variables may contain multibyte characters. If the client does not allow multibyte character set names, then the filename must be in uppercase English.

    BEGIN LOAD

    Table names:

  • Target tables
  • Error tables
    		•

    Target table names and error table names may contain multibyte characters.

    DML

    DML label name

    The label name in a DML statement may contain multibyte characters. The label name may be referenced in the APPLY clause of an IMPORT statement.

    FIELD

    Field name

    The field name specified may contain multibyte characters. The name can be referenced in other FIELD commands in NULLIF and field concatenation expressions, and in APPLY WHERE conditions in IMPORT commands. The FIELD command can also contain a NULLIF expression, which may use multibyte characters.

    FILLER

    Filler name

    The name specified in a FILLER command may contain multibyte characters.

    IF

    IF condition

    The condition in an IF statement may compare multibyte character strings.

    LAYOUT

    Layout name
    CONTINUEIF condition

    The layout name may contain multibyte characters and may be used in the LAYOUT clause of an IMPORT command. The CONTINUEIF condition may specify multibyte character set character comparisons.

    LOGON

    User name
    Password

    The user name and password may contain multibyte characters.

    LOGTABLE

    Table name
    Database name

    The logtable name and database name may contain multibyte characters.

    NAME

    set SYSJOBNAME

    This variable may contain kanji characters.

    SET

    Utility variable

    The utility variable may contain multibyte characters. The variable can be substituted wherever substitution is allowed.

    TABLE

    Table and database name

    The table name (and database name if the table name is fully qualified) specified in a TABLE statement may contain multibyte characters. Avoid using the TABLE command when using UTF‑8 or UTF‑16 character sets by explicitly specifying the layout.