MONOCASE - Teradata Director Program

Teradata® Director Program Reference - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata Director Program
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-11-17
dita:mapPath
cki1641301536147.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
frc1470439950465
Product Category
Teradata Tools and Utilities

The MONOCASE directive optionally defines characters that have both lower and upper case. If this information is not supplied, then no monocasing is performed.

Syntax



Usage Notes

The actual monocase information is contained on statements that immediately follow the MONOCASE directive. Each such statement has the following syntax:

target_codepoint1<-target_codepoint2>: data_codepoint ...

where:

target_codepoint1
Specifies the first character defined on this statement.
target_codepoint2
Optionally specifies the last character defined on this statement.
data_codepoint
Defines the upper case equivalent for the associated target_codepoint character.

A codepoint is the hexadecimal representation of a character. The number of characters needed to specify a codepoint is dependent on the encoding scheme for the character set. With the current TDP support, the length is always two except for UTF16 encoding, for which the length is four.

If the second target codepoint is specified, then one data codepoint is required for each character in the range between the two target codepoints. If the second target codepoint is omitted, then any number of data codepoints can be specified, each associated with codepoint one greater than the previous.

All statements after the MONOCASE directive that contain a colon are associated with the MONOCASE directive. Lack of a colon indicates that the statement is a new directive and ends that MONOCASE directive.

The only codepoints that need be specified are those for which upper case equivalents exist.

The MONOCASE directive can be specified only once for each character set.

The order of data codepoints among different statements is not significant.

If the same character is defined more than once for a character set (either on a MONOCASE directive, or on a MONOCASE and a UNICODE directive), the last value is used.

If no CHARSET directive precedes MONOCASE, then a character set description is implicitly begun -- in effect, a CHARSET directive with no operands is assumed.

Example: MONOCASE

Define the monocase information for IBM Code Page 833, the single-byte component for IBM CCSID 933.

MONOCASE
81-89: C1 C2 C3 C4 C5 C6 C7 C8 C9
91-99: D1 D2 D3 D4 D5 D6 D7 D8 D9
A2-A9: E2 E3 E4 E5 E6 E7 E8 E9