17.20 - KANJI1 Character Expectations - Analytics Database - Teradata Vantage

Teradata Vantage™ - Analytics Database International Character Set Support - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-01-27
dita:mapPath
aju1628095815656.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
hqj1472245413611

KANJI1 character data is usually a mixture of single- and multibyte characters. Therefore, even when a session uses a non-Japanese client character set, such as standard EBCDIC or ASCII, certain character configurations are interpreted either as starting a multibyte character string or as control characters.

The following interpretations apply to name and data characters for all client character sets when the server character set is KANJI1.

Characters with a client encoding of … Are …
0x0E

0x0F

interpreted as the Shift-Out or Shift-In character respectively, which delimit the start or end of a multibyte character string.
0x80

0xFF

translated internally into characters that are reserved for the ss 2 and ss 3 escape characters of KanjiEUC data.