2.3.3 Settings required immediately after installation (for UNIX)
Specify in a JP1/Base environment variable the language encoding in which JP1/IM - Manager runs. You must specify the language encoding in both the environment variable file and the common definitions. Effective with version 11-00, environment variables of JP1/IM (jp1co_env.conf file) are no longer used.
The language encoding in the environment variable file and common definitions must match on all local hosts. Additionally, use the character encoding of events in the JP1/SES format to unify the language environment of a system that monitors events in the JP1/SES format. This subsection describes how to set the language encoding in the environment variable file and common definitions.
- Organization of this subsection
(1) Setting the language encoding in the environment variable file
Using a text editor such as vi, open the /etc/opt/jp1base/conf/jp1bs_env.conf file and, following LANG= on the first line, set the appropriate value for the LANG environment variable based on the following table.
|
OS |
Language type |
Encoding |
Value of LANG environment variable#3 |
|---|---|---|---|
|
Linux |
Japanese |
SJIS#1 |
ja_JP.SJIS or ja_JP.sjis |
|
UTF-8#2 |
ja_JP.UTF-8 or ja_JP.utf8 |
||
|
English |
C |
C |
|
|
Chinese |
GB18030 |
zh_CN.gb18030 |
- #1
-
Applicable to SUSE Linux only.
- #2
-
In UTF-8 encoding, two character codes are used to represent each of the following symbols:
Yen sign (\): 0x5C or 0xC2A5
Tilde (~): 0x7E or 0xE280BE
In JP1/IM - Manager, \ is represented by 0x5C and ~ is represented by 0x7E.
- #3
-
Do not specify a LANG value that is not listed in the table. The value of LANG is case sensitive.
These definitions take effect the next time JP1/IM - Manager starts.
- Important
-
When you select English as the language type, do not use multi-byte characters when you configure JP1/IM - Manager. If you do, JP1/IM - Manager handles the multi-byte characters as ASCII characters. As a result, JP1/IM - Manager might not operate normally.
(2) Checking the language environment settings of JP1/Base
-
Check the setting value in the /etc/opt/jp1base/conf/jp1bs_env.conf file.
Confirm that the value set after LANG = in the jp1bs_env.conf file matches the value set in 2.3.3(1) Setting the language encoding in the environment variable file.
For details about the jp1bs_env.conf file, see the JP1/Base User's Guide.
-
Check the setting value in the /etc/opt/jp1base/jbs_start file.
Confirm that the value set after LANG = in the jbs_start file matches the value set in 2.3.3(1) Setting the language encoding in the environment variable file.
For details about the jbs_start file, see the JP1/Base User's Guide.
- Note
-
Once you have set the encoding and started the operation, you can still use the steps above to change the encoding.
For details about the language environment settings of JP1/Base, see the part that describes the language type settings in the JP1/Base User's Guide.
(3) Setting the language encoding in the common definitions
-
Edit the jp1bs_param.conf file.
Use a text editor to open the /etc/opt/jp1base/conf/jp1bs_param.conf file. After LANG=, set a value for the LANG environment variable based on the table below.
Table 2‒2: Values that can be specified for LANG in the jp1bs_param.conf file Language type
Code
LANG value
Japanese
Shift JIS code
SJIS
EUC code
EUCJIS
UTF-8 code
UTF-8
English
C
Chinese
GB18030
-
Stop JP1/IM - Manager.
-
Stop JP1/Base.
-
Execute the following command:
/opt/jp1base/bin/jbssetcnf /etc/opt/jp1base/conf/jp1bs_param.conf
If you need to change the environment variables of JP1/IM - Manager while Central Scope is running, perform the following procedure:
-
Use the jcsdbexport command to output the information stored in the monitoring object database to a local file.
-
Stop JP1/IM - Manager.
-
Change the language encoding used by JP1/IM - Manager when it runs and start JP1/IM - Manager.
-
Use the jcsdbimport command to apply the contents of the monitoring object database (output to the local file) to the monitoring object database of Central Scope.
If you do not perform the above procedure, the Monitoring Tree window and Visual Monitoring window will not be displayed correctly.