2.4.3 Language type of the system

You can display messages either in English or Japanese. Consider which language should be used for the language to display according to the usage.

The following table shows which version combinations are supported in an environment in which both domestic and overseas versions of JP1/AJS products are being used.

Table 2‒24: Supported combinations of domestic and overseas JP1/AJS products
			JP1/AJS - View				JP1/AJS - Agent
			Domestic		Overseas		Domestic		Overseas
			Japanese	English	Japanese	English	Japanese	English	Japanese	English
JP1/AJS - Manager	Domestic	Japanese	Yes	--	Yes	--	Yes	(Yes)2^#	Yes	Yes^#
	Domestic	English	(Yes)1^#	--	(Yes)1^#	(Yes)1	--	(Yes)1,(Yes)2	--	(Yes)1
	Overseas	Japanese	Yes	--	Yes	--	Yes	(Yes)2^#	Yes	Yes^#
	Overseas	English	Yes^#	--	Yes^#	Yes	--	(Yes)2	--	Yes

Legend:

Yes: Supported

(Yes)1: Supported only for the UNIX version of JP1/AJS - Manager.: Set C (English) in the LANG environment variable applied when the JP1/AJS service in JP1/AJS - Manager starts.
(Yes)2: Supported only for the UNIX version of JP1/AJS - Agent.: Set C (English) in the LANG environment variable applied when the JP1/AJS service in JP1/AJS - Agent starts.

--: Not supported

#

Set alphanumeric characters (ASCII) for all text and information used in JP1/AJS, including unit names, file names, characters used in files, messages in jobs being executed, monitoring conditions for event jobs, and information inherited by event jobs.

Organization of this subsection

(1) Values that can be specified in the LANG environment variable
(2) Available characters
(3) Changing the character code set
(4) Notes on an environment where more than one character code set is used
(5) Notes on using UTF-8 encoding

(1) 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 Unicode (UTF-8) is specified for the LANG environment variable of a product that does not support Unicode (UTF-8).

In Windows, the system language environment cannot be changed.

Table 2‒25: Values that can be specified in the LANG environment variable
OS	Language and code		LANG environment variable
HP-UX	Japanese	Shift-JIS	`ja_JP.SJIS`^#1 `japanese`
		EUC	`ja_JP.eucJP` `japanese.euc`
		UTF-8^#2	`ja_JP.utf8`
	English	ASCII	`C`
Solaris	Japanese	Shift-JIS	`ja_JP.PCK`
		EUC	`ja`^{#1, #3} `ja_JP.eucJP`^#3
		UTF-8^#2	`ja_JP.UTF-8`
	English	ASCII	`C`
AIX	Japanese	Shift-JIS	`Ja_JP`^#1 `Ja_JP.IBM-932`
		EUC	`ja_JP` `ja_JP.IBM-eucJP`
		UTF-8^#2	`JA_JP` `JA_JP.UTF-8`
	English	ASCII	`C`
Linux	Japanese	Shift-JIS	Cannot be used.
		EUC	Cannot be used.
		UTF-8	`ja_JP.UTF-8`^#1 `ja_JP.utf8`
	English	ASCII	`C`

#1

This value is specified in jp1ajs_env.conf when you install or set up JP1/AJS3 for the first time. For details about the locations where you need to specify a character encoding, see (3) Changing the character code set.

#2

UTF-8 cannot be used for compatible ISAM configurations.

#3

For Solaris 11, ja and ja_JP.eucJP can be used.

For Solaris 10, only ja can be used.

To Page Top

(2) 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:

The 3rd level and 4th level Kanji characters added in JIS 2004 cannot be used.

If unsupported characters are used in definition items such as a unit name, the problems below might occur. Unsupported characters cannot be used even in a stand-alone configuration.

Characters are garbled.
A standard job is placed in the Ended abnormally status or operates 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 when 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 Job Management Partner 1/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 or Unix job. For details about the standard error output and Standard output, see 15.4.6 Define Details - [UNIX Job] dialog box in the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide, or 15.4.7 Define Details - [PC Job] dialog box in the Job Management Partner 1/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 15.4.6 Define Details - [UNIX Job] dialog box in the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide, or 15.4.7 Define Details - [PC Job] dialog box in the Job Management Partner 1/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 Job Management Partner 1/Automatic Job Management System 3 Linkage Guide.

To Page Top

(3) Changing the character code set

In UNIX, you must set the same character encoding for the definition files, environment variables, and environment setting parameters listed in the following table.

Table 2‒26: Settings you must specify when changing the character code set
Settings (definition files, environment variables, and environment setting parameters)	What the change affects
The `LANG` environment variable applied when the JP1/AJS3 service starts	The character code set for messages output from the JP1/AJS3 service
JP1/AJS3 environment definition file For a physical host: `/etc/opt/jp1ajs2/conf/jp1ajs_env.conf` For a logical host: The `LANG` environment variable in: `shared-directory/jp1ajs2/conf/jp1ajs_env.conf`	Value of the `LANG` environment variable to be applied when the JP1/AJS3 service starts Character encoding of the information to be output to integrated trace logs and internal logs by schedule control, event/action control, and job execution control When the user profile does not contain the `LANG` environment variable, the default for `LANG` during job execution.
JP1/Base parameter definition file For a physical host: `/etc/opt/jp1base/conf/jp1bs_param.conf` For a logical host: The `LANG` environment variable in: `shared-directory/jp1base/conf/jp1bs_param.conf`	The character code set of the data to be exchanged between the JP1/AJS3 manager host and agent host when standard jobs, event jobs, action jobs, and custom jobs are executed The character code set of the data to be exchanged between the jobnet connector and the connected jobnet when the jobnet connector is used to control the execution order of root jobnets
`AJSCHARCODE` parameter in the scheduler service environment definition	The character code set for the information that will be stored in the scheduler database.
`SYSLOGCODE` parameter in the scheduler service environment definition	The character code set for messages output by the scheduler services to `SYSLOG`. The value of the `LANG` environment variable used at the start of the service when a value other than `C` (English) is specified.
`CHARCODE` parameter in the JP1/AJS3 Console Manager environment definition	The character code set for information that will be stored in the user definition data.
`SYSLOGCODE` parameter in the JP1/AJS3 Console Manager environment definition	The character code set of messages output by the JP1/AJS3 Console Manager service to `SYSLOG`. The value of the `LANG` environment variable used at the start of the service when a value other than `C` (English) is specified.
The `LANG` environment variable when the JP1/AJS3 Console Manager service is active	The character code set for messages output from the JP1/AJS3 Console Manager service
`SYSLOGCODE` parameter in the JP1/AJS3 Console Agent environment definition	The character code set for messages output by the JP1/AJS3 Console Agent service to `SYSLOG`. The value of the `LANG` environment variable used at the start of the service when a value other than `C` (English) is specified.
The `LANG` environment variable when the JP1/AJS3 Console Agent service is active	The character code set for messages output from the JP1/AJS3 Console Agent service
The `LANG` environment variable when the queueless agent service is active	The character code set for messages output from the queueless agent service
The `AJSQL_CHARCODE`^#1 environment setting parameter used by the queueless agent service	Data accepted from the scheduler service Transfer file data Result file data Reply data to the scheduler service
The `LANG` environment variable^#3 when a command^#2 for unit operation is executed	The values stored in the scheduler database by the command that operates on the unit The log data and character code set for messages that are output by the command that operates on the unit

#1

If the manager and agent hosts use different character code sets, the AJSQL_CHARCODE environment setting parameter must be set for character code conversion.

For details about character code conversion for queueless jobs, see 7.2.2 Environment settings for executing queueless jobs.

#2

For details about the commands for manipulating units, see 1.5 Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

#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.

The following figure shows what is affected by changing the character code set from the default one.

Figure 2‒36: What is affected by changing the character code set

In Windows, the system language environment cannot be changed. In UNIX, for details about how to change the system language environment, see 13.4.1 Setting the language environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

You must redefine any unit names containing Kana characters or two-byte characters that are already being used in JP1/AJS3.

To Page Top

(4) Notes on an environment where more than one character code set is used

When applications are executed by two or more linked hosts working together, text that includes Japanese character codes cannot be displayed in an English environment. Set the same language type for all hosts. For details about the language types that can be combined in heterogeneous JP1/AJS products, see Table 2-24.

The following restrictions apply to combining different types of Japanese character codes.

Remote execution of commands

When a command is remotely executed, the same character code set 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 Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

The character code set of the host where the command is entered is the character code set specified in the OS by using the LANG environment variable, for example.

The character code set 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 code sets of the host where the remote job is defined and the host where the remote job is executed must match.

The character code set of the host where the remote job is defined and the character code set 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, 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 code set 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 code compatibility mode. If you do not use character code compatibility mode, a JP1 event might not be detected correctly or another kind of error might occur.

For details on the character code compatibility mode, see Job Management Partner 1/Base User's Guide.
Character encoding of the JP1/AJS3 Console Manager data directory

When the character encoding of the JP1/AJS3 Console Manager data directory is English, you can only specify the AJS3 unit names in alphanumeric characters (ASCII). If you want to use both English and Japanese to monitor applications, specify a Japanese character encoding for the JP1/AJS3 Console Manager data directory.

When you use the function for automatically creating the monitored objects for a unit to be monitored whose full unit name contains Japanese, and C (English) is specified as the character encoding in the environment settings of JP1/AJS3 Console Manager, an error message (KAVC4635-E The automatically created monitored object information is not saved.) appears. Also note that the function might not work for units whose full unit names do not contain Japanese if multiple units are to be automatically created.

If you use the function, select only units whose full unit names do not include Japanese.
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 code 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

To Page Top

(5) 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 Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.
For details about the characters that you can use in a UTF-8 environment, see (2) 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 2.7 Setting up the queueless job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.
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, manager jobnet, or JP1/AJS3 Console View 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.
UTF-8 can be used only in Linux for compatible ISAM configurations.

To Page Top