The following passages discuss the JIS characters that are valid and invalid for KanjiEBCDIC object names.

JIS Character Set Relevant passages in the book
JIS-x0201 Figure H-5 in Appendix H, “Japanese Character Sets”, documents the valid ranges for the KATAKANAEBCDIC character set for JIS-x0201. Figure H-6 in Appendix H documents the valid ranges for the KANJIEBCDIC5026_0I character set for JIS-x0201. Neither set permits Katakana symbols 0x41—0x45, nor Latin symbols other than $, #, and _. Appendix Figure H-7 in Appendix H documents the valid ranges for the KANJIEBCDIC5035_0I character set for JIS-x0201. This set does not permit Katakana symbols 0x42—0x46 nor Latin symbols other than $, #, and _.
JIS-x0208 Appendix Figure H-8 in Appendix H documents the valid ranges for JIS-x0208. Note that characters in the User and Marker areas in table are not allowed. Also, many KanjiEBCDIC characters cannot be mapped to JIS-x0208. A list of these characters is given in Table H-1 and Table H-2 in Appendix H.

The following passages discuss the JIS characters that are valid and invalid when creating object names under the KanjiEUC character set.

JIS Character Set Relevant passages in the book
JIS-x0201 The valid ranges for JIS-x0201 characters in KanjiEUC object names can be found in rows cs0 and cs2 in Table H-3 in Appendix H. The set does not permit Katakana symbols 0x8EA1—0x8EA5 nor Latin symbols other than $, #, and _.
JIS-x0208 The valid ranges for JIS-x0208 are given in row cs1 of the “EUC Code Set Localization” table. However, note that within the JIS-x0208 ranges, there are unassigned characters that are not allowed in object names; for example, the unassigned character 0xA9A1 is illegal. In addition, certain characters that are valid in JIS-x0208 do not map to the KanjiEBCDIC encoding and are not allowed at all under KanjiEUC. These are shown in Appendix I.
JIS-x0212 The JIS-x0212 characters found in row cs3 of the table Table H-3 are not allowed in KanjiEUC object names.

Teradata RDBMS for UNIX SQL Reference

4-9
Teradata SQL Lexicon

Japanese Character Object Names

Character Ranges for KanjiShift-JIS Object Names

The following passages discuss the JIS characters that are valid and invalid when creating object names under the KanjiShift-JIS character set.

JIS Character Set Relevant passages in the book
JIS-x0201 The valid ranges for JIS-x0201 characters in KanjiShift-JIS object names are listed in table Table H-5 in Appendix H. The set does not permit Katakana symbols 0x82A1—0x82A5 nor Latin symbols other than $, #, and _.
JIS-x0208 The valid ranges for JIS-x0208 are detailed in Table H-5 in Appendix H. Note that: Gaiji, with first byte values 0xF0-0xF9, and the IBM defined characters, with first byte values 0xFA-0xFC, as listed in Table H-5 are not allowed in object names. Within the JIS-x0208 ranges, there are unassigned characters that are not allowed in object names; for example, the unassigned character 0x8540 is illegal. Certain characters that are valid in JIS-x0208 do not map to the KanjiEBCDIC encoding and are not allowed under KanjiShift-JIS. These are given in Appendix I.

4-10

Teradata RDBMS for UNIX SQL Reference
Teradata SQL Lexicon

Rules for Non-ASCII Character Object Names

Object Name Validation Rules

How Validation Occurs

Rules for Non-ASCII Character Object Names

Note: This section only applies to the use of extended character

sets. Rules for ASCII (EBCDIC) are comparably simpler.

When constructing an object name from a session with character set

X, you must make sure that the following criteria are met:

• The single byte character Katakana characters are those defined in JIS-x0201, with the exceptions noted for each character set in the preceding passages.

• The multibyte character Kanji characters are those defined in JIS-x0208, with the exceptions noted for each character set in the preceding passages.

• The object name can be converted to any other character set Y and that it will not exceed 30 bytes in Ys encoding. That is, LEN

• Table names and column names are verified during the CREATE/ALTER TABLE and RENAME TABLE statements. View and macro names are verified during the CREATE/RENAME VIEW and CREATE/RENAME MACRO statements.