Table of Contents
Advertisement
Input through user commands is always converted from the external
character set to the node character set.
No input conversion is performed for configuration files; configuration
files are always in the node character set.
No output conversion is done for local logfiles; the contents of logfiles
is always in the node character set.
MIB processing is always performed in the node character set.
Action agents receive their input in the management server character
set, and convert it into the node character set before actions are
started.
Example:
Scenario
ITO agent-processing character set on an HP-UX 10.x
managed node is EUC.
LANG=ja_JP.SJIS
opcmsg msg_text="This is a message with Shift JIS
characters"
Conversion
Input conversion of the opcmsg is from Shift JIS to
EUC.
Output conversion, before forwarding the message to
the management server, is from EUC to Shift JIS (the
database character set).
Tips
On HP-UX, it is possible to define different character sets for different
managed nodes. It is recommended that you set the character set most
frequently used on each managed node. For example, if you mostly
monitor logfiles with Shift JIS characters, you should use Shift JIS for
your managed nodes. Similarly, if your environment mostly generates
input data for ITO in the EUC character set, you should set the managed
node character set to EUC. If in doubt, use Shift JIS.
Note that you can use a different character set for each HP-UX managed
node. You determine the managed node character set by the character
sets used in your environment.
Chapter 8
ITO Language Support
Character Conversion in ITO
349
Advertisement
Table of Contents
Troubleshooting
