2.4.2 Language type and character encoding of the system
This subsection describes the language type and character encoding used in JP1/AJS3.
- Organization of this subsection
(1) Available language types
You can use Japanese, English, or Chinese in JP1/AJS3. The language should be used according to intended usage.
(2) Values that can be specified in the LANG environment variable
In UNIX, to set the systems language environment, use the LANG environment variable. The table below lists the values that can be specified in the LANG environment variable. Use this table to select a value. If you do not use a value listed in this table, C (English) will be set. Operation is not guaranteed if the values specified in this table are not specified.
For details about operation using a language other than Japanese, English, or Chinese, see (11) About the operations in multiple language environments.
In Windows, the system language environment cannot be changed.
- #1
-
Can only be used in SUSE Linux.
- #2
-
Only 7-bit ASCII characters can be used. Do not use characters other than 7-bit ASCII characters.
- Cautionary note
-
The character encoding used in JP1/AJS3 must be the same as the one used in JP1/Base. There might be some cases in which a character encoding usable in JP1/Base cannot be used in JP1/AJS3.
(3) Whether language settings can be mixed in the same device
If JP1/AJS3 is used on a logical host, whether hosts with mixed language types can exist or not depends on the host OS.
- In Windows:
-
Hosts with different language types cannot exist on the same device. All the logical hosts and physical hosts must have the same language type.
- In UNIX:
-
If the language types of all the hosts on the same device are Japanese or English, hosts with different language types can exist. Therefore, the language type can be either Japanese or English for each logical host.
However, hosts whose language settings are set to Chinese, Korean, German, French, Spanish or Russian cannot exist on the same device as another host that has a different language setting. The language type on all the logical hosts and physical hosts must be the same.
The following figure shows an example in which mixed language types exist on the same device.
Figure 2‒46: Example of mixed language types on the same device
In JP1/AJS3 - Manager, the character encoding of the host must match the character encoding of the scheduler service. The host and scheduler service cannot have different character encodings.
The following figure shows an example of mixed character encodings on the host and the scheduler service.
|
(4) Whether language settings can be mixed within a system
The following table shows whether a combination of language settings is allowed when hosts with different language types are combined in JP1/AJS3.
JP1/AJS - Agent, JP1/AJS - View, or JP1/AJS - Web Console |
||||
---|---|---|---|---|
Japanese |
English |
Chinese |
||
JP1/AJS - Manager |
Japanese |
Yes |
(Yes)2 |
(Yes)2 |
English |
(Yes)2 |
Yes |
(Yes)2 |
|
Chinese |
(Yes)2 |
(Yes)2 |
(Yes)1 |
- Legend:
-
Yes: Supported. If the language type is Japanese, hosts with a different character encoding can exist.
(Yes)1: Supported. The character encoding must be unified to the Chinese character encoding.
(Yes)2: Supported only when all the characters and information are unified to alphanumeric characters (ASCII).
- Cautionary note
-
The combinations (Yes)2 in Table 2-31 are environments of hosts with different language types. In this case, set alphanumeric characters (ASCII) for all texts and information including the unit name, file name, characters used in files, messages in jobs being executed, monitoring conditions for event jobs, and inherited information. If a character other than ASCII is used, the following conditions might occur:
-
Characters are garbled.
-
A standard job and HTTP connection job are placed in the Ended abnormally status or operate incorrectly.
-
An event job is placed in the Ended abnormally status, cannot be detected, or is detected incorrectly.
-
A process terminates abnormally.
-
(5) Overview of steps to set the language type and character encoding
This subsection gives an overview of the steps to set the language type and character encoding.
(a) If JP1/AJS3 is installed in a new installation
If JP1/AJS3 - Manager, JP1/AJS3 - Agent, or JP1/AJS3 - View is newly installed, the language type is automatically decided during the installation.
- In Windows:
-
The required language setting is automatically set according to the language type of the OS.
- In UNIX:
-
The required language setting is automatically set according to the LANG environment variable when Hitachi Program Product Installer is started. If necessary, specify the LANG environment variable before starting Hitachi Program Product Installer.
- Cautionary note
-
If you cannot define a job that includes a multi-byte character of the specified language or such a job cannot be executed properly, the LANG environment variable specified during the installation might have been wrong. See 7.9.6 Changing the language environment of the system in the JP1/Automatic Job Management System 3 Administration Guide and change the language setting.
(b) If JP1/AJS3 is installed in an overwrite installation or upgrade installation
If you install JP1/AJS3 in an overwrite installation or upgrade installation, the language setting before the installation is inherited.
(c) When a logical host is used
Specify the language setting on a logical host after setting up the logical host by using the jajs_setup_cluster command. For details about the jajs_setup_cluster command, see jajs_setup_cluster in 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference.
The following shows the language setting required for setting up a logical host:
- In JP1/AJS3 - Manager for Windows:
-
The language setting of the logical host is inherited from the physical host by the jajs_setup_cluster command. Because hosts with different language types cannot exist in Windows, do not change the language setting on the logical host.
- In JP1/AJS3 - Manager for UNIX:
-
The language setting of the logical host is inherited from the physical host by the jajs_setup_cluster command.
If you operate a logical host with a language type different from the one used on the physical host, see 7.9.6 Changing the language environment of the system in the JP1/Automatic Job Management System 3 Administration Guide. Referring to the guide, execute the jajs_setup_cluster command, and then change the language setting on the logical host and the scheduler service.
- Cautionary note
-
The -E option for the jajs_setup_cluster command can only be specified when the character encoding of the logical host is UTF-8. The -E option enables you to specify the same number of characters for names including the unit names between the Shift-JIS environment and the UTF-8 environment. When the -E option is specified, the character encoding of the scheduler database is set to UTF-8, so the character encoding of the logical host must be set to UTF-8.
- In JP1/AJS3 - Agent:
-
The language setting is inherited from the physical host. If you operate a logical host with a language type different from the one used on the physical host, see 7.9.6 Changing the language environment of the system in the JP1/Automatic Job Management System 3 Administration Guide. Referring to the guide, change the language setting on the logical host after executing the jajs_setup_cluster command.
(d) When a scheduler service is added (JP1/AJS3 - Manager only)
If you execute the jajs_setup command to add a scheduler service, the character encoding for the added scheduler service (the value of the AJSCHARCODE environment setting parameter) must match the character encoding on the logical host.
The following table lists the default character encoding of the scheduler service added by the jajs_setup command, and the value of the AJSCHARCODE environment setting parameter.
OS |
Default character encoding of the scheduler service |
The value of the AJSCHARCODE environment setting parameter |
---|---|---|
Windows |
Shift-JIS |
SJIS |
HP-UX |
Shift-JIS |
SJIS |
Solaris |
EUC |
EUC |
AIX |
Shift-JIS |
SJIS |
Linux |
UTF-8 |
UTF-8 |
For details about how to change the character encoding, see 7.9.6 Changing the language environment of the system in the JP1/Automatic Job Management System 3 Administration Guide.
- Cautionary note
-
The -E option for the jajs_setup command, which enables you to specify the same number of characters for names including the unit names between the Shift-JIS environment and the UTF-8 environment, can only be specified when the character encoding of the logical host is UTF-8. When the -E option is specified, the character encoding of the scheduler database is set to UTF-8, so the character encoding of the logical host must be set to UTF-8.
(6) Locations of the character encoding setting (UNIX only)
When you specify a character encoding in JP1/AJS3 - Manager or JP1/AJS3 - Agent, you must set the same character encoding for the definition files, environment variables, and environment setting parameters listed in the table below. For details about how to specify the character encoding, see 7.9.6 Changing the language environment of the system in the JP1/Automatic Job Management System 3 Administration Guide.
Settings (definition files, environment variables, and environment setting parameters) |
What the change affects |
Related products |
---|---|---|
The LANG environment variable applied when the JP1/AJS3 service starts |
The character encoding of messages output from the JP1/AJS3 service. |
M, A |
JP1/AJS3 environment definition file
|
|
M, A |
JP1/Base parameter definition file
|
|
M, A |
AJSCHARCODE parameter in the scheduler service environment definition |
The character encoding of the information that will be stored in the scheduler database. |
M |
SYSLOGCODE #1parameter in the scheduler service environment definition |
|
M |
The LANG environment variable#3 when a command#2 for unit operation is executed |
|
M |
The LANG environment variable when a command#5 used to operate execution agents |
The values stored in the agent management database. |
M |
The AJSI18N environment setting parameter in the JP1/AJS3 shared information |
The entire JP1/AJS3 |
M, A |
The LANG environment variable when the queueless agent service is started |
The character encoding of the messages output by the queueless agent service. |
M, A |
The AJSQL_CHARCODE#4 environment setting parameter in the queueless job execution environment setting |
|
M, A |
The LANG environment variable when the JP1/AJS3 Autonomous Agent service and the JP1/AJS3 Autonomous Agent Messenger service start |
Messages output by flexible job processes and the job execution results when the LANG environment variable is not specified in the login profile of the root user |
M, A |
- Legend:
-
M: JP1/AJS3 - Manager
A: JP1/AJS3 - Agent
- #1
-
Specify C if you use Chinese.
- #2
-
For details about the commands for manipulating units, see 1.5 Commands in the manual JP1/Automatic Job Management System 3 Command Reference.
- #3
-
Specify the character encoding that is specified in the AJSCHARCODE environment setting parameter of the scheduler service where the unit to be manipulated by the command is defined. If you use Chinese, specify a value that corresponds to the GB18030 character encoding.
- #4
-
If the manager host and the agent host use different character encodings, the AJSQL_CHARCODE environment setting parameter must be specified to enable character encoding conversion. For details about character encoding conversion for a queueless job, see 7.2.2 Environment settings for executing queueless jobs.
- #5
-
For details about the commands used to operate execution agents, see 1.5.5 Commands used to operate execution agents in the manual JP1/Automatic Job Management System 3 Command Reference.
The following figure shows the sections affected when the character encoding is changed.
|
When you specify a character encoding in JP1/AJS3 - Web Console, you must set the same character encoding for the definition files and environment variables listed in the table below.
Settings (definition files and environment variables) |
What the change affects |
---|---|
The LANG environment variable applied when the JP1/AJS3 HTTP Server service starts#1 |
The character encoding of internal logs that are output by JP1/AJS3 HTTP Server. |
The LANG environment variable applied when the JP1/AJS3 Web Application Server service starts#1 |
The character encoding of internal logs that are output by JP1/AJS3 Web Application Server. |
Environment definition file The language type setting for the messages output to logs specified in /etc/opt/jp1ajs3web/conf/ajs3web.conf #2 |
The character encoding of messages that are output to the integrated trace log, command log, and application server log. |
- #1
-
If automatic startup is enabled, the value specified in the LANG= line in the service automatic start script is applied.
- #2
-
If the setting is system, the character encoding specified in the LANG environment variable at the start of the JP1/AJS3 Web Application Server service is applied.
(7) Cautionary notes when Japanese is used as a language type
The following provides cautionary notes when Japanese is used as a language type.
(a) Available characters
If the language type is Japanese, you can use the following characters with JP1/AJS3:
-
ASCII and JIS characters
-
Single-byte katakana characters
-
JIS X 0208-1990
Some characters cannot be used with the following character encodings:
-
If the encoding is SJIS, EUC, or UTF-8:
External characters and machine-dependent characters cannot be used.
-
If the encoding is EUC:
If the character encoding used in JP1/AJS3 - Manager is EUC, the following characters cannot be used:
-
If the character encoding is UTF-8:
If the character encoding used in JP1/AJS3 - Manager is UTF-8, the following characters cannot be used:
Note that if the OS is UNIX, all text information used in JP1/AJS3 must be specified by using UTF-8-encoded strings in the shortest form. That text information includes unit names, file names, file contents, messages to be output during job execution, conditions for monitoring event jobs to be run, and information to be passed to event jobs. If a non-shortest form is used, JP1/AJS3 might be unable to operate correctly.
The 3rd level and 4th level Kanji characters added in JIS 2004 cannot be used.
(b) Cautionary notes when mixed types of character encodings exist
■ Cautionary notes when the manager host and agent host have different character encodings
If the language type is Japanese or English, and the manager host and agent host have different character encodings, the character encodings are converted to the one used by the communication destination when the manager host communicates with the agent host. The following lists the definitions, input files, and execution results whose character encodings are converted. That is, if data is transmitted from the manager to the agent, the data is converted to the character encoding used at the agent. If data is transmitted from the agent to the manager, the data is converted to the character encoding used at the manager. This conversion of the character encoding occurs for the following definitions, input files, and execution results.
- For PC jobs, Unix jobs, flexible jobs, and QUEUE jobs
-
- Definitions
-
-
Name of executable file
-
Command statement
-
Parameter
-
Script file name
-
Environment variable
-
Environment variable filename
-
Name of the work directory used during agent process execution
-
Standard input filename
-
Standard output filename
-
Standard error output filename
-
Transfer filename
-
Job name (for QUEUE job)
-
Values of macro variables defined in jobs
-
- Input files
-
-
Contents of transfer files 1 to 4
-
- Execution results
-
-
Contents of the standard output file
-
Contents of the standard error output file (execution result details)
-
- HTTP connection jobs
-
- Definitions
-
-
Conn. configuration file name
-
Trans. info. file name
-
Trans. info. file name (URL parameter)
-
Trans. info. file name (message body)
-
Status file name
-
Received header file name
-
Received body file name
-
Standard output file name
-
Standard error output file name
-
- Execution results
-
-
Contents of the standard output file
-
Contents of the standard error output file (execution result details)
-
- Action jobs and custom jobs
-
- Definitions
-
-
Information defined for jobs
-
Values of macro variables defined in jobs
-
- Execution results
-
-
Contents of the standard error output file (execution result details)
-
- Event jobs
-
- Definitions
-
-
Information defined for jobs
-
- Execution results
-
-
Contents of the standard error output file (execution result details)
-
Inherited information (values of macro variables defined in jobs)
-
In the case of Chinese, the character encoding is not converted at the time when the manager host communicates with the agent host. All the manager hosts and agent hosts must have the Chinese character encoding.
■ Cautionary notes when mixed Japanese character encodings are used
The following restrictions apply to combining different types of Japanese character encodings.
-
Remote execution of commands
When a command is remotely executed, the same character encoding must be set for the host where the command is entered and for the host where the command is executed.
If the character encoding on the host where the command is executed is UTF-8, you can remotely execute the command by setting EUC as the character encoding of the host where the command is entered.
For details about remote execution of commands, see 1.1.7 Remote execution of a command in the manual JP1/Automatic Job Management System 3 Command Reference.
The character encoding of the host where the command is entered is the character encoding specified in the OS by using the LANG environment variable, for example.
The character encoding of the host where the command is executed refers to one of the following:
-
Character encoding specified in the AJSCHARCODE environment setting parameter
-
Setting of the OS used when the JP1/AJS3 service is started
-
-
Remote jobnet
When a remote jobnet is executed, the character encodings of the host where the remote job is defined and the host where the remote job is executed must match.
The character encoding of the host where the remote job is defined and the character encoding of the host where the remote job is executed refer to one of the following:
-
Character encoding specified in the AJSCHARCODE environment setting parameter on each host
-
Setting of the OS used when the JP1/AJS3 service is started
-
-
Unix job, HTTP connection job, flexible job, action job, and event job
For JP1/AJS3 - View or a command, if the definition items for a job executed on the agent host in a UTF-8 environment contain Japanese characters, assume that one Japanese character requires 4 bytes. Based on this assumption, define the job so that the maximum value for each item is not exceeded. If sjis is specified for the DEFLENTYPE environment setting parameter, the maximum number of characters that can be specified for the following items is the same as in a Shift-JIS environment:
-
Unit name in the detailed unit definition
-
Comment in the detailed unit definition
-
Exclusive jobnet in the schedule settings
A Unix job, action job, or event job can be executed in a system configuration where the manager host operates in a Shift-JIS or EUC environment and the agent host operates in a UTF-8 environment. In this case, the number of bytes converted to the character encoding of the agent host is checked as the size of the information defined for the job. As a result, a job execution error might occur even if the definition in JP1/AJS3 - View or a command does not exceed the maximum number of bytes that can be entered for job items.
-
-
Event job
If the sum of the size of the event job passing information and the size of the macro variable name exceeds 4,096 bytes on the agent host, the excess data is truncated.
To pass information containing Japanese characters in a UTF-8 environment, assume that one Japanese character requires 4 bytes.
To use JP1/AJS3 that does not support UTF-8 to receive JP1 events issued from a UTF-8 environment, configure JP1/Base to run in character encoding compatibility mode. If you do not use character encoding compatibility mode, a JP1 event might not be detected correctly or another kind of error might occur.
For details on the character encoding compatibility mode, see JP1/Base User's Guide.
-
Commands used for executing submit jobs
If a command is executed from a host in a Shift-JIS or EUC environment for a manager host in a UTF-8 environment, an error might occur on the manager host even when the values of the options do not exceed the maximum number of bytes on the command execution host. The reason for the error is that the number of bytes in the option values containing Japanese characters increases due to character encoding conversion when the command execution host transfers data to the manager host.
Therefore, when you specify option values containing Japanese characters for commands executed on the manager host in the UTF-8 environment, assume that one Japanese character require 4 bytes. Based on this assumption, specify the options so that the value of each option is within the maximum number of specifiable bytes.
- Commands:
-
jpqjobsub, jpqjobcan, jpqjobalt, jpqjobmove, jpqjobget, jpqjobshow, jpqendjobshow, jpqjobdel, jpqqueopen, jpqqueclose, jpqqueshow, jpqqueadd, jpqquedel, jpqquealt, jpqagtlink, jpqagtunlink, jpqagtshow, jpqagtadd, jpqagtdel, jpqagtalt, jpqresshow, jpqresadd, jpqresdel
■ Notes on using UTF-8 encoding
-
If a command entered from a host that uses UTF-8 encoding is remotely executed on a host for which UTF-8 is specified as the character encoding in AJSCHARCODE, you must specify no for the AJSCONVERTUTF8 environment variable. If the AJSCONVERTUTF8 environment variable is not specified or if the command is remotely executed with yes specified, characters in the display results might be garbled or processing on the unit might not be performed correctly.
For details about the AJSCONVERTUTF8 environment variable, see 1.4 Environment variables in the manual JP1/Automatic Job Management System 3 Command Reference.
-
For details about the characters that you can use in a UTF-8 environment, see (a) Available characters.
-
If a queueless job entered from the manager host that uses UTF-8 encoding is executed on an agent host that does not support UTF-8 encoding, you must specify the QLMANCHARCODE environment setting parameter on the manager host. For details about the QLMANCHARCODE environment setting parameter, see 20.10 Setting up the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.
-
If UTF-8 encoding is used and sjis is specified for the DEFLENTYPE environment setting parameter, the number of characters that can be specified for the following items is the same as in a Shift-JIS environment:
-
Unit name in the detailed unit definition
-
Comment in the detailed unit definition
-
Exclusive jobnet in the schedule settings
Note, however, that the maximum number of nested units (maximum number of levels) is 10 (the default is 30).
-
-
For a version of JP1/AJS3 - View earlier than 09-50, if sjis is specified for the DEFLENTYPE environment setting parameter, a scheduler service and its lower units are not displayed. If sjis is specified for the DEFLENTYPE environment setting parameter for all scheduler services, the KAVV187-E message is output and none of the scheduler services or their lower units are displayed. If you use the ajs command or manager jobnet to access the scheduler service for which sjis is specified for the DEFLENTYPE environment setting parameter, the KAVV455-E message is output. The scheduler service and its lower units are not displayed.
(8) Cautionary notes when the Chinese language type is used
Only GB18030-2000 characters of 2 bytes or less can be used. Operation is not guaranteed if any other character is used.
- Cautionary note
-
When using the Chinese language, the following characters might not be displayed correctly:
-
Euro symbol (code:0xA2E3)
-
Comma (code:0xA6D9) #
-
Period (code:0xA6DA) #
-
Punctuation mark (code:0xA6DB) #
-
Colon (code:0xA6DC) #
-
Semicolon (code:0xA6DD) #
-
Exclamation mark (code:0xA6DE) #
-
Question mark (code:0xA6DF) #
-
Left black lenticular bracket (white) (code:0xA6EC) #
-
Right black lenticular bracket (white) (code:0xA6ED) #
-
Ellipses (code:0xA6F3) #
- #
-
For vertically written text.
-
(9) Cautionary notes common to all the language types
If you use an unsupported character in a definition item, such as a unit name, the following problems might occur. Unsupported characters cannot be used even in a stand-alone configuration.
-
Characters are garbled.
-
An error occurs during the creation of a new unit or redefinition of a unit.
-
A standard job and HTTP connection job are placed in the Ended abnormally status or operate incorrectly.
-
An event job is placed in the Ended abnormally status, cannot be detected, or is detected incorrectly.
-
A JP1/AJS3 process terminates abnormally.
Make sure that the data or files listed below do not contain unsupported characters. If there are any unsupported characters, the same problems as when unsupported characters are used in definition items might occur.
-
Data stored in the passing information#1
-
Data that is output to the standard error output and standard output#2
-
Standard input file, environment variable file, or transfer file#3
-
Text file or list file specified for sending an email#4
- #1
-
Applicable for the following passing information:
-
The information on which passing information is specified in the event job definition for passing the event information received by an event job to a succeeding job or jobnet
For details about how to pass the information received by an event job, see 2.4.4(6) Passing information received by an event job in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.
-
Passing information specified by a passing information settings job
For details about the passing information settings job, see 2.4.9 Passing information that changes dynamically to a succeeding unit (example of defining a jobnet that uses a passing information setting job) in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.
-
- #2
-
Applicable when the data is in the job execution results specified for a PC job, Unix job, or flexible job. For details about the standard error output and Standard output, see 12.4.6 Define Details - [UNIX Job] dialog box in the JP1/Automatic Job Management System 3 Operator's Guide, or 12.4.7 Define Details - [PC Job] dialog box in the JP1/Automatic Job Management System 3 Operator's Guide.
- #3
-
Applicable when the file is specified for a PC job or Unix job. For details about the standard input file, environment variable file and transfer file, see 12.4.6 Define Details - [UNIX Job] dialog box in the JP1/Automatic Job Management System 3 Operator's Guide, or 12.4.7 Define Details - [PC Job] dialog box in the JP1/Automatic Job Management System 3 Operator's Guide.
- #4
-
Applicable when PC is specified as the platform in the definition items. For details about the mail linkage, see 2. Linking Mail Systems in the JP1/Automatic Job Management System 3 Linkage Guide.
(10) Changing the language setting during operation
If you change the language type and character encoding during operation, reinstallation of JP1/AJS3 might be required depending on the combination of JP1/AJS3 and the OS. The following table lists the combination of JP1/AJS3 and the OS and whether reinstallation is required.
Product |
Windows |
UNIX |
---|---|---|
JP1/AJS3 - Manager |
Reinstallation is required. |
Reinstallation is required. |
JP1/AJS3 - Agent |
Reinstallation is required. |
Reinstallation is not required. |
JP1/AJS3 - View |
Reinstallation is required. |
Not supported. |
If reinstallation is required, migrate the setting information in accordance with the backup and recovery procedures. If reinstallation is not required, stop the JP1/AJS3 service, change the environment settings, and then cold-start the JP1/AJS3 service.
For details about how to change the character encoding, see 7.9.6 Changing the language environment of the system in the JP1/Automatic Job Management System 3 Administration Guide.
(11) About the operations in multiple language environments
Korean, German, French, Spanish, Russian, or Thai can be used for the unit name and the comment in JP1/AJS3. When using multiple languages, please set the same language for the OSs on which JP1/AJS3 - Manager, JP1/AJS3 - Agent, JP1/AJS3 - View, JP1/AJS3 - Web Console will be installed. Also, please set the same language and character code for JP1/AJS3 - Manager, JP1/AJS3 - Agent, JP1/AJS3 - View, JP1/AJS3 - Web Console. If the settings of language and character code are different to connection products, please use unit name and comment in the range of ASCII code.
Note: If you are using the Russian language or Thai language, you cannot set the same character encoding between Windows and Linux products, because Windows and Linux products use different character encodings. Therefore, the OSs used should be uniformly set to either Windows or Linux.
The Thai solar calendar cannot be used. Use the Gregorian (western) calendar. In Windows, change the OS settings to use the Gregorian calendar.
The following shows the procedure for specifying the settings required to use Korean, German, French, Spanish, Russian, or Thai. For details about how to change the language settings in the OS, see the Release Notes. For details about how to change the character encoding, see 7.9.6 Changing the language environment of the system in the JP1/Automatic Job Management System 3 Administration Guide.
(a) In Windows
■ For JP1/AJS3 - Manager and JP1/AJS3 - Agent
The detailed procedure for definition is as follows:
-
Change the language settings in the OS.
-
Install JP1/AJS3 - Manager or JP1/AJS3 - Agent.
-
Execute the following command:
jajs_config -k "[JP1_DEFAULT\JP1AJS2COMMON]" "AJSI18N"="yes"
■ For JP1/AJS3 - View
The detailed procedure for definition is as follows:
-
Change the language settings in the OS.
-
Install JP1/AJS3 - View.
-
In the environment settings file (ajs.conf), add the SetCharEncodingNameI18N definition line, and then specify the appropriate value as shown in the following table.
- File storage folder
-
JP1/AJS3-View-installation-folder\conf\ajs.conf
Table 2‒36: Values that can be specified in the environment settings file (ajs.conf) Language
Connection destination JP1/AJS3 - Manager OS
Value that can be specified for SetCharEncodingNameI18N
Korean
Windows
EUC_KR
Linux
EUC_KR
German
French
Spanish
Windows
ISO8859_1
Linux
ISO8859_1
Russian
Windows
CP1251
Linux
KOI8_R
Thai
Windows
MS874
Linux
UTF8
Example: When using German language
- Change from:
[STARTUP] lang=1
- Change to:
[STARTUP] lang=1 SetCharEncodingNameI18N=ISO8859_1
■ For JP1/AJS3 - Web Console
The detailed procedure for definition is as follows:
-
Change the language settings in the OS.
-
Install JP1/AJS3 - Web Console.
-
Specify the value in the following table for the I18N definition line of the environment settings file (ajscharcodemapping.properties).
- File storage folder
-
Web_Data_Path#\conf\ajscharcodemapping.properties
- File storage folder for operation in a cluster system
-
shared-folder\jp1ajs3web\conf\ajscharcodemapping.properties
- #
-
One of the following paths is indicated in Web_Data_Path:
If the installation folder is the default installation folder or is in a folder protected by the system:
%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\jp1ajs3web
The default value for %ALLUSERSPROFILE% is system-drive\ProgramData.
A folder protected by the system is the path to a folder in any of the following:
- system-drive\Windows
- system-drive\Program Files
If the installation folder is other than the above:
JP1/AJS3 - Web Console-installation-folder
Table 2‒37: Values that can be specified in the environment settings file (ajscharcodemapping.properties) Language
Connection destination JP1/AJS3 - Manager OS
I18N value
Korean
Windows
EUC_KR
Linux
EUC_KR
German
French
Spanish
Windows
ISO8859_1
Linux
ISO8859_1
Russian
Windows
CP1251
Linux
KOI8_R
Thai
Windows
MS874
Linux
UTF8
Example: When using German language
- Change from:
C=ASCII SJIS=MS932 EUC=EUC_JP UTF-8=UTF8 I18N=GB18030
- Change to:
C=ASCII SJIS=MS932 EUC=EUC_JP UTF-8=UTF8 I18N=ISO8859_1
(b) In Linux
■ For JP1/AJS3 - Manager and JP1/AJS3 - Agent
The detailed procedure for definition is as follows:
-
Specify C for LANG environment variable.
export LANG=C
-
Install JP1/AJS3 - Manager or JP1/AJS3 - Agent.
JP1/AJS3 - Manager or JP1/AJS3 - Agent is installed with English language settings.
-
Use the jajs_config command to set yes for the AJSI18N environment setting parameter.
jajs_config -k "[JP1_DEFAULT\JP1AJS2COMMON]" "AJSI18N"="yes"
-
Change the value of the LANG environment variable that is defined in the JP1/AJS3 environment definition file (jp1ajs_env.conf).
- For a physical host:
-
/etc/opt/jp1ajs2/conf/jp1ajs_env.conf
- For a logical host:
-
shared-directory/jp1ajs2/conf/jp1ajs_env.conf
Table 2‒38: Values that can be specified in the LANG environment variable Language
Character encoding
Value of LANG environment variable
Korean
EUC-KR
ko_KR.EUC-KR
German
ISO-8859-1
de_DE.ISO-8859-1
French
ISO-8859-1
fr_FR.ISO-8859-1
Spanish
ISO-8859-1
es_ES.ISO-8859-1
Russian
KOI8-R
ru_RU.KOI8-R
Thai
UTF-8
-
en_US.UTF-8
-
en_US.utf8
Example: When using German language
- Change from:
LANG=C
- Change to:
LANG=de_DE.ISO-8859-1
■ For JP1/AJS3 - Web Console
The detailed procedure for definition is as follows:
-
Specify C for LANG environment variable
export LANG=C
-
Install JP1/AJS3 - Web Console
JP1/AJS3 - Web Console is installed with English language settings.
-
Specify the value in the following table for the I18N definition line of the environment settings file (ajscharcodemapping.properties).
- Specified place
-
/etc/opt/jp1ajs3web/conf/ajscharcodemapping.properties
- Cluster configuration
-
shared-directory/jp1ajs3web/conf/ajscharcodemapping.properties
Table 2‒39: Values that can be specified in the environment settings file (ajscharcodemapping.properties) Language
Connection destination JP1/AJS3 - Manager OS
I18N value
Linux
Windows
EUC_KR
Linux
EUC_KR
German
French
Spanish
Windows
ISO8859_1
Linux
ISO8859_1
Russian
Windows
CP1251
Linux
KOI8_R
Thai
Windows
MS874
Linux
UTF8
Example: When using German language
- Change from:
C=ASCII SJIS=MS932 EUC=EUC_JP UTF-8=UTF8 I18N=GB18030
- Change to:
C=ASCII SJIS=MS932 EUC=EUC_JP UTF-8=UTF8 I18N=ISO8859_1
(c) When adding a scheduler service or logical host (for JP1/AJS3 - Manager only)
When you add a scheduler service or logical host in Windows or Linux, use the following procedure to change the language type settings.
-
Run the jajs_setup or jajs_setup_cluster command to add a scheduler service.
For details about the jajs_setup command, see jajs_setup in 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference.
For details about the jajs_setup_cluster command, see jajs_setup_cluster in 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference.
-
For the scheduler service that you added, change the value of the AJSCHARCODE environment setting parameter to C.
Execute the following command:
jajs_config -k " [{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER\scheduler-service-name]" "AJSCHARCODE"="C"