HP OpenView Operations Administrator's Reference - filibeto.org

About OVO Language Support
About Language Support on Managed Nodes
302
About the ASCII Character Set
NOTE Only NCS- or DCE-based managed nodes can be run in ASCII mode.
The American Standard Code for Information Interchange (ASCII) is
supported as an internal character set on the managed node and as a
character set for the OVO Logfile Encapsulator.
ASCII is a 7-bit character set and, therefore, a subset of all the character
sets OVO supports, for example, the 8-bit Shift JIS character set. You can
manage English-language nodes (running with ASCII as an internal
character set) with a Japanese-language management server. Note 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.
Changing the Character Set of the OVO Logfile Encapsulator
To change the character set of the OVO Logfile Encapsulator on the
managed node, you must first remove the existing logfile templates from
the managed nodes by de-assigning and re-distributing them. After the
template has been successfully removed, change the character set from
multibyte to ASCII, and assign and distribute the template again.
Managing English-language Nodes with a Japanese-language
Management Server
To manage English-language nodes with a Japanese-language
management server, you must assign templates to the managed node.
These templates may contain ASCII data only. Japanese-language
installations can upload English-language templates as well as the
multibyte Japanese-language templates from the OVO database.
However, you must first change the template name if it is identical to the
English name. Make sure to set LANG=C before calling opccfgupld(1M).
Chapter 8