Neoview Character Sets Administrator's Guide (R2.3)

4 Capabilities and Limitations of Neoview Client

Applications

This chapter describes the capabilities and limitations of these Neoview client applications with

respect to the Neoview Character Sets feature for this Neoview release:

• “Neoview Transporter Java Client” (page 31)

• “Neoview Loader” (page 31)

• “Neoview DB Admin” (page 32)

• “Neoview Management Dashboard Client” (page 32)

• “Neoview Command Interface (NCI)” (page 32)

• “Workload Management Services (WMS)” (page 32)

Neoview Transporter Java Client

For this Neoview release, the Neoview Transporter Java Client supports:

• Using delimited identifiers in table and column names that are encoded in the ISO8859-1,

SJIS, EUC-JP, BIG 5, GB2312, GB18030, KSC, and UTF8 character sets

• In the ISO88591 configuration, loading input data sources “as is,” without translation, into

ISO88591 columns

• In the ISO88591 configuration, using client locale character encoding for table and column

names

• In the SJIS configuration, loading SJIS and EUC-JP encoded input data sources into the

Neoview database

• In the Unicode configuration, loading GB2312, GB18030, KSC, BIG5, EUC-JP, and

SJIS-encoded data sources

• Reporting all character translation errors as bad records

• Sending all errors in UTF8 format

• Logging all event messages in UTF8 format

• Encoding data files in any of the Java-supported character sets

For information about managing character translation and encoding for the Neoview Transporter

Java Client, see “How Character Encoding Is Implemented on the Neoview Transporter Java

Client” (page 43). For general information about the Neoview Transporter, see the Neoview

Transporter User Guide.

Neoview Loader

Table 4-1 (page 31) describes the input file encoding guidelines for the Neoview Loader in the

three Neoview character set configurations.

Table 4-1 Neoview Loader Capabilities and Limitations

Unicode ConfigurationSJIS ConfigurationISO88591 Configuration

Input files for ISO88591 columns must

be encoded in UTF8 with pass-through

mode set to OFF.

• Input files for ISO88591 columns

must be encoded in SJIS MS932.

• Always inserts SJIS-encoded data

into ISO88591 columns.

Input files for ISO88591 columns

must be encoded in ISO8859-1.

For all three configuration, input files for UCS2 columns must be encoded in UTF8.

For all three configurations, delimited 7-bit ASCII or ISO8859-1 characters must be used in table and column names.

Neoview Transporter Java Client 31