13.1.5 Language environment considerations

(a) Operation in English

Set the system locale to English. Otherwise, the characters displayed in the window might be garbled.

(b) Operation in Japanese

• Set the system locale to Japanese. Otherwise, the characters displayed in the window might be garbled.

• JP1/IM does not support character codes other than SJIS character code, such as JIS Third and Forth Levels.

(c) Operation in Chinese

• Set the system locale to Chinese. Otherwise, the characters displayed in the window might be garbled.

• JP1/IM supports the GB18030 character code only.

• If you display characters other than those that can be used with the font Simsun, the characters displayed in the window might be garbled.

• Before setting up the IM database, you need to set GB18030 as the character code of JP1/IM - Manager.

• When using JP1/IM - Manager in Chinese, you need to set GB18030 as the character code of JP1/Base. Check the JP1/Base character code setting by performing the following procedure:

Execute the following commands:

For a physical host

jbsgetcnf ><save-file-name>.txt

For a logical host

jbsgetcnf -h <logical-host-name> ><save-file-name>.txt

Use a text editor to open the file <save-file-name>.txt, and make sure the value GB18030 is set for the definition item LANG in [JP1_DEFAULT\JP1BASE\]. In the case of a logical host, set JP1_DEFAULT to <logical-host-name>.

• If the value of LANG is not GB18030, set it to GB18030.

• In the central console items below, you can use only characters of two bytes or less in the GB18030 character code. In the other central console items, you can use characters of four bytes or less in the GB18030 character code.

  • Conditions for Updating List of Action Results window

  • Action Parameter Detailed Definitions (for compatibility) window

  • Action Parameter Detailed Definitions (Extended Event

  • Information) window

  • Edit Extended Attributes window

  • Automatic action notification definition file (actnotice.conf)

  • Extended startup process definition file (jp1co_service.conf)

  • Health check definition file (jcohc.conf)

  • Automated action environment definition file (action.conf.update)

  • IM parameter definition file (jp1co_param_V7.conf)

  • Communication environment definition file (console.conf.update)

  • Communication environment definition file (view.conf.update)

  • Correlation event generation definition file

  • Automated action definition file (actdef.conf)

• In the central scope items below, you can use characters of four bytes or less in the GB18030 character code. In the other central scope items, you can use only characters of two bytes in the GB18030 character code.

  • Attribute values of individual conditions in the Status-Change Condition Settings window

  • Attribute values of common condition details in the Common Condition Detailed Settings window

  • Regular expressions of guide information files (jcs_guide_xxx.txt)

• In the IM configuration management items below, you can use characters of four bytes or less in the GB18030 character code. In the other central scope items, you can use only characters of two bytes in the GB18030 character code.

  • Configuration files for log file trap information in the Display/Edit Profiles window

  • Configuration files for event log file trap information in the Display/Edit Profiles window

  • Content of export files of central scope of the jcfmkcsdata command