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

For information about using gcmd to set the value of the cSetConversion (-cc) argument to
specify whether or not the Neoview Loader should perform character set conversion, see “How
Character Encoding Is Implemented on the Neoview Loader” (page 47).
Neoview DB Admin
For this Neoview release, Neoview DB Admin references the character set values defined in the
SYSTEM_DEFAULTS table. It displays and allow users to enter characters in all the supported
client locale character encodings.
For this Neoview release, Neoview DB Admin imposes these restrictions:
• If the characters you enter from Neoview DB Admin are not recognized by or compatible
with the SQL database, the Neoview DB Admin operation will be rejected by SQL with an
error.
• When the ISO88591 configuration is used, Neoview DB Admin reverts to using only 7-bit
ASCII characters and will not support the use of 8-bit ASCII or multibyte characters from
the client locales.
• It returns CORBA errors when you attempt to retrieve character data inserted from a different
client workstation using a character set that is incompatible with the current workstation.
For more information, see Table 5-1 (page 35).
For more information about Neoview DB Admin, see the Neoview DB Admin Online Help.
Neoview Management Dashboard Client
For this Neoview release, the Dashboard Client does not support the Neoview Character Sets
feature.
For general information about the Dashboard Client, see the Neoview Management Dashboard
Client Guide for Database Administrators.
Neoview Command Interface (NCI)
Any obey file that you run from the Neoview Command Interface must be opened in the character
set that is configured on the client workstation from which the operation is issued. An obey file
encoded with a different character set than the client locale might not open. For example, if your
client locale is a Windows workstation configured with a code page for Japanese characters, the
obey file must also be in Japanese characters.
For more information about the Neoview Command Interface, see the Neoview Command Interface
(NCI) Guide.
Workload Management Services (WMS)
For this Neoview release, WMS has these character encoding behaviors:
• WMS service names can be defined and created through ODBC, JDBC, or NCI. The service
names can be provided in any character set that is supported by the Neoview platform for
this Neoview release.
• Service names are sent to EMS logs in UTF8. Internally, the names are transmitted and stored
in UTF8 in WMS
• Service names must be enclosed in double quotes when the service name is case sensitive
or when it contains multibyte characters.
• A WMS service name can be up to 24 characters, and each character can be from one to four
bytes. For the QUERY_NAME column returned in the STATUS QUERY/QUERIES commands,
the service name is truncated to 16 characters and followed by two vertical lines (||) and
the application ID.
32 Capabilities and Limitations of Neoview Client Applications