Neoview Character Sets Administrator's Guide (R2.4, R2.5)

Non-ASCII characters do not occur in the other fields defined for these entities, except show
related displays.
• Non-ASCII character set support has been provided for the East Asian locales supported
by the latest Neoview release.
• In Show Related displays, characters outside the ASCII numeric code set are not displayed.
• Capture of EDL with non-ASCII data is not supported.
• Commands issued in the Command and Control facility might fail or have unexpected
results if the queries on which they operate have domain names that contain non-ASCII
characters.
• The Client Server Gateway (CSG) cannot establish a connection to the Neoview platform
on behalf of a workstation that has non-ASCII characters in its name. Thus, the Dashboard
Client will obtain no data from the Neoview platform. A workaround for this limitation is
to use dynamic workstation names by clearing the Term Name option on the SSG property
sheet, as described in the Neoview Management Dashboard Client Guide for Database
Administrators.
• A table whose name contains characters other than 7-bit ASCII cannot be explicitly configured
(by HP Support) for monitoring by Dashboard. Such a table will be monitored only if the
SQL compiler reports that the table has missing or obsolete statistics.
For detailed information about the Dashboard Client, see the Neoview Management Dashboard
Client Guide for Database Administrators.
Neoview Manageability Repository
The Repository supports these character set encoding features:
• The Repository is aware of whether a Neoview platform uses the ISO88591, SJIS, or Unicode
configuration.
• If the Neoview platform uses the ISO88591 configuration, the character fields in all Repository
tables and views will contain ISO8859-1 character data.
• If the Neoview platform uses the SJIS or Unicode configuration, character fields in some,
but not all, Repository views will contain double-wide UCS2–encoded data.
For more information, see the Neoview Repository User Guide.
Neoview Transporter Client
For this Neoview release, the Neoview Transporter 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
• Logging all event messages in UTF8 format
For information about managing character translation and encoding for the Neoview Transporter
client, see “How Character Encoding Is Implemented in the Neoview Transporter Client”
(page 49). For general information about the Neoview Transporter, see the Neoview Transporter
User Guide.
Neoview Manageability Repository 37