...

The Configuration -> Inventory view allows to specify object names and job scripts to be specified using Unicode characters:

...

The Workflows view displays workflows using Unicode characters accordingly:

• The example below example makes use of Japanese object names.
• In addition, the JOC Cockpit interface language is has been switched to Japanese by use of JS7 - Profiles - Preferences.
  
  

...

The Log view window displays output of jobs and instructions.

• Partly output Output is partly created from the JOC Cockpit and is qualified with markers such as [MAIN], [SUCCESS], [DETAIL].
• Partly output Output is partly created from job scripts executed with an OS shell. Such output is marked as [STDOUT] and [STDERR].
  
  

...

• Output from Unix Operating Systems
  • Unix Operating Systems ship with built-in support for Unicode and UTF-8 encoding.
• Output from Windows Operating Systems
  • Windows does not offer Unicode. Instead the OS ships with different code pages preinstalled depending on the location in which the OS is used.
  • Some experimental Unicode support is available starting from Windows 10, however, as most Windows programs are not aware of Unicode there can be side-effects.
  • Therefore the encoding of output created by jobs depends on the code page in use for the respective Windows OS for which an Agent is operated on.

Controller

The Controller does not read or write files related to execution of workflows and jobs. The Controller reads configuration files and writes component log files only.

...

The Agent makes use of the code page that is active for the computer the Agent is operated foron.

• In Asia frequently code page 65001 or specific code pages such as 932 for Japan are frequently used.
• In Western Europe frequently code page 850 is frequently used.

...