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

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 Command Interface (NCI)” (page 35)
• “Neoview DB Admin” (page 35)
• “Neoview Loader” (page 36)
• “Neoview Management Dashboard” (page 36)
• “Neoview Manageability Repository” (page 37)
• “Neoview Transporter Client” (page 37)
This chapter also describes the capabilities and limitations of the Neoview Character Sets feature
in Neoview Workload Management Services (WMS). See “Neoview Workload Management
Services (WMS)” (page 38).
Neoview Command Interface (NCI)
NCI communicates with the Neoview database through JDBC. The Neoview JDBC driver handles
all required character translations and manages all SQL statements and character data in UTF16.
Obey files and log files are assumed to be encoded in the client locale character set and are
translated by the Java runtime to UTF16.
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.
Neoview DB Admin
The Neoview DB Admin GUI interface is Java-based and accepts characters in any language that
is installed on a connected client workstation. Character translation operates as follows:
• Client locale character encoding is translated to UTF16 for internal use, then converted by
the JORB to UTF8 and sent to the SQL server.
• The SQL server accepts the UTF8 characters and performs the necessary internal translations,
including converting all characters to the ISO_MAPPING encoding and translating data
being returned to the Neoview DB Admin servers from the ISO_MAPPING encoding to
UTF8. Any character that is not properly translated to UTF8 on the server side is reported
as a CORBA exception.
• Character data sent in its client locale character encoding is translated to UTF16 for internal
use by Neoview DB Admin.
• The UTF16 data is converted to UTF8 and sent to the CORBA interfaces and the SQL server.
• Character data retrieved by Neoview DB Admin from the Neoview database is first converted
to UTF8, then internally to UTF16, and finally encoded in its client locale character set.
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.
Neoview Command Interface (NCI) 35