If the Teradata-defined Japanese character sets described in Japanese Client Character Set Support are not appropriate for your site, you can define your own character sets using the following names, IDs, and encodings.
| Character Set Name | ID | Description |
|---|---|---|
| SDKATAKANAEBCDIC_4IF | 77 | Japanese Katakana EBCDIC for mainframe clients. The encoding form is EBCDIC Shift-Out/Shift-In, where the shift-out character 0x0E and shift-in character 0x0F bracket zero or more double-byte characters. |
| SDKANJIEBCDIC5026_4IG | 78 | IBM Japanese Extended Katakana character set for mainframe clients. The high order bit of the first byte in a sequence distinguishes single-byte characters from double-byte characters. |
| SDKANJIEBCDIC5035_4IH | 79 | IBM Japanese Extended English character set for mainframe clients. The high order bit of the first byte in a sequence distinguishes single-byte characters from double-byte characters. |
| SDKANJIEUC_1U3 | 91 | Japanese character set for network-attached clients that is compatible with the UNIX operating system. The encoding form is Extended UNIX Code (EUC), composed of four code sets: cs0 for one-byte characters, cs1 and cs2 for two-byte characters, and cs3 for three-byte characters. |
| SDKANJISJIS_1S3 | 92 | Windows-compatible Japanese character set for network-attached clients. The first byte in a sequence distinguishes single-byte characters from double-byte characters. |
The system uses the two characters following the underscore (_) in the character set name as a link to the mapping file you create in the TPA etc or TPA cfg directory. The name of the mapping file must start with “map_” and end with the first two characters following the underscore in the character set name.
For example, if you define a character set for SDKANJISJIS_1S3, you must create a mapping file named map_1S that provides the translation tables between the transitional forms and Unicode.