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

Neoview 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.
• Within WMS, SQL statements are always assumed to be in UTF8 encoding for the SJIS and
Unicode configurations. In the ISO88591 configuration, SQL statements are in the client
locale character encoding and will therefore display properly through a Java client but not
through an ODBC client.
• Within WMS, query plans are assumed to be in the encoding specified by the ISO_MAPPING
value for the SJIS and Unicode configurations. In the ISO88591 configuration, characters are
provided in the client locale character encoding.
• In the ISO88591 configuration, WMS cannot ascertain the encoding of any extended characters
that are defined in character strings.
For more information, see the Neoview Workload Management Services Guide.
38 Capabilities and Limitations of Neoview Client Applications