340 Chapter 8
ITO Language Support
Language Support on Managed Nodes
Table 8-4 Supported Character Sets on Managed Nodes in a Japanese
Environment
a. For Solaris, Shift JIS is only supported with Solaris version 2.6 and higher.
b. 2-byte Extended UNIX Code.
c. Code Page 932 is analogous to Shift JIS.
The character set used for a node can be modified in the Advanced
Options window of the Add/Modify Node window. All managed node
processing is performed using this character set.
The ASCII Character Set
ASCII is supported as internal character set on the managed node and as
character set for the ITO Logfile Encapsulator. It is a 7-bit character set
and therefore a subset of the 8-bit Shift JIS character set. This means
that ASCII can be converted to Shift JIS without loss of data and enables
you to manage English nodes (running with ASCII as internal character
set) with a Japanese management server. Note however, that if you are
using ASCII as the character set for internal processing ( in the Node
Advanced Options window), you must also specify ASCII as the
character set for the monitored logfile messages.
NOTE To change the character set of the ITO Logfile Encapsulator on the
managed node, you must first deassign and remove the logfile template
from the managed nodes. Once the template has been successfully
removed, stop and start the agent processes, change the character set
from multibyte to ASCII, and assign and distribute the template.
To manage English nodes with a Japanese management server, you must
assign templates to the managed node which only contain ASCII data.
Japanese installations can upload English templates in addition to the
multibyte Japanese templates from the ITO database but must change
the template name to be able to do so. Make sure to set LANG=C before
calling opccfgupld(1M).
Platform Character Set
HP-UX, AIX, Solaris, Digital UNIX Shift JIS
a
, EUC
b
, ASCII
Windows NT (intel-based) Japanese ANSI Code Page 932
c
, ASCII
