East Asian (CJK) Language Support Configuration

The CJK language set includes support for the following languages:

  • Traditional Chinese

  • Simplified Chinese

  • Japanese

  • Korean.

To set up your environment to support the CJK language set, you must configure and synchronize all the computer systems and databases before configuring the language settings for the following Control-M components:

  • Control-M/Agent

  • Control-M/EM

  • Control-M/Server

  • Control-M Reports

  • Control-M for AFT

Control-M/EM can communicate in English with earlier versions of Control-M/Server and with Control-M for z/OS\® installations that do not handle CJK characters. This communication is possible because the Gateway detects the type and version of the connected Control-M/Servers (and other Control-M installations such as z/OS) and translates the data accordingly.

Setting the Code Page for CJK Support on Windows

This procedure describes how to set the code page for CJK support on Windows. This must be done before you install Control-M.

Update the locale to the same value on every computer running Windows that runs the following components:

  • Control-M/EM

  • Control-M/Server

  • Control-M/Agent

  • Control-M Application Plug-Ins

Begin

  1. From a command line, type chcp <codePage>, where <codePage> can be one of the following values:

    • 932 (ANSI/OEM, Japanese Shift-JIS)

    • 936 (ANSI/OEM, Simplified Chinese GBK)

    • 949 (ANSI/OEM, Korean)

    • 950 (ANSI/OEM, Traditional Chinese Big5)

      chcp 932.

      If the code page is invalid, contact your system administrator to install the required code page.

      For Control-M components to communicate properly with each other, you must set the locale for all product components to the same value. Discrepancies between locale settings can corrupt data while data is passed from one component to another.

  2. Ensure that the corresponding code page is selected on the list of Code page conversion tables.

Setting the Locale Environment on UNIX or Linux

This procedure describes how to set the locale environment on a UNIX and Linux machine. This should be done on computers that runs components of the following products:

  • Control-M/EM

  • Control-M/Server

  • Control-M/Agent

  • Control-M Application Plug-Ins

Begin

  • Ensure that the required language locale is present on the computer.

    Use the same language locale for all affected computers. Discrepancies between locale settings, especially those involving different character sets, can corrupt data as it passes between components.

    1. To get a list of locales available on your computer, enter the locale -a command.

    2. Confirm that the list includes the required locale as described in CJK character set locale settings for UNIX and Linux. If the required locale is missing, ask your UNIX administrator to install it.

  • When configuring Control-M/Agent on operating systems not listed in the following table, use the locale setting for the operating system that corresponds to the one selected for ControlM/EM and Control-M/Server. Contact your UNIX administrator for additional assistance.

CJK Character Set Locale Settings for UNIX and Linux

The following table lists the CJK character set locale settings for UNIX and Linux:

Language

AIX

Solaris

Linux

Chinese (Simplified)

ZH_CN.UTF-8

zh.UTF-8

zh_CN.utf8

Chinese (Traditional)

ZH_TW.UTF-8

zh_TW.UTF-8

zh_TW.utf8

Japanese

JA_JP.UTF-8

ja_JP.UTF-8

ja_JP.utf8

Korean

KO_KR.UTF-8

ko.UTF-8

ko_KR.utf8

Configuring CJK Support for Jobs Submitted on Remote Hosts

This procedure describes how to configure CJK support for jobs submitted on remote host.

Begin

  1. Configure the remote host with Agents that are set to the required encoding as defined in the Tables - Control-M Agent language encodings available through ctmunixcfg and Control-M/Agent language encodings available through ctmwincfg (see Setting parameters for Control-M/Agent).

  2. Select remote host Agents according to the encoding available on either Windows or UNIX platforms. Windows CJK encoding is available only on Agents installed on Windows. Similarly UNIX CJK encoding is available only on Agents installed on UNIX.

Configuring Language Support on Control-M/Agent

This procedure describes how to configure language support for CJK on the Control-M/Agent machine.

Begin

  1. From the command-prompt window, run the ctmagcfg command-line utility.

  2. Select 7 Advanced parameters.

  3. Select 7 Foreign Language Support and then select CJK.

  4. Set the encoding that the Control-M/Agent uses to run jobs.

  5. Ensure that the required language locale or code page is present on the computer, as described in CJK locale settings for operating systems jobs. On UNIX, you can use the locale -a command to list the information.

  6. Ensure that the environment of the owner responsible for running jobs is set to the correct locale.

  7. Use the appropriate command-line utility to set the language encoding for jobs that Control-M/Agent runs.

  8. From UNIX, run the ctmunixcfg command-line utility, and set the CJK Encoding parameter to one of the language encodings, as listed in Control-M/Agent language encodings available through ctmunixcfg. The Control-M/Agent assumes that all jobs will be run in the same user-defined locale.

  9. From Windows, run the ctmwincfg command-line utility and set the CJK Encoding parameter to one of the available language encodings, as listed in Control-M/Agent language encodings available through ctmwincfg.

  10. Restart the Control-M/Agent.

CJK Locale Settings for Operating Systems Jobs

The following table lists the CJK locale settings for operating system jobs:

Language

AIX

Solaris

Linux

Windows

Chinese (Simplified)

ZH_CN.UTF-8

Zh_CN.GBK

Zh_CN.GB18030

zh.UTF-8

zh.GBK

zh_CN.GB18030

zh_CN.utf8

zh_CN.gb18030

zh_CN.gbk

CP936

Chinese (Traditional)

ZH_TW.UTF-8

Zh_TW.big5

zh_TW.IBM-eucTW

zh_TW.UTF-8

zh_TW.BIG5

zh_TW (EUC)

zh_TW.utf8

zh_TW.big5

zh_TW.euctw

CP950

Japanese

JA_JP.UTF-8

JA_JP.IBM-eucJP

Ja_JP.IBM-943

ja_JP.UTF-8

ja_JP.eucJP

ja_JP.PCK (Shiftjis)

ja_JP.utf8

ja_JP.eucjp

ja_JP.PCK (Shiftjis)

CP932

Korean

KO_KR.UTF-8

KO_KR.IBM-eucKR

ko.UTF-8

ko (EUC)

ko_KR.utf8

ko_KR.euckr

CP949

Control-M/Agent Language Encodings Available Through ctmunixcfg

The following table list the language encodings available through ctmunixcfg:

Job Language Option

Encoding

UTF-8

*.UTF-8

Japanese EUC

*.eucJP

Japanese SHIFT-JIS

Ja_JP.IBM-943

ja_JP.SJIS

ja_JP.PCK

Korean EUC

*.eucKR

Simplified Chinese GBK

*.GBK

Simplified Chinese GB

*.GB18030

Traditional Chinese EUC

*.eucTW

Traditional Chinese BIG5

*.big5

Control-M/Agent Language Encodings Available Through ctmwincfg

The following table lists the language encodings available through ctmwincfg:

Job Language Option

Encoding

Japanese

CP932

Korean

CP949

Simplified Chinese

CP936

Traditional Chinese

CP950

UTF-16

UNICODE

CJK Database Configuration

Before creating a Control-M/Server or Control-M/EM database, ensure that the database server fulfills the prerequisites, as listed in CJK prerequisites.

Review the additional CJK support issues, as described in CJK support issues for database installation when creating or installing a new database.

CJK Prerequisites

The following table lists the CJK prerequisites:

Type of Database

Prerequisites

PostgreSQL

Installed with UTF8 character sets

Oracle

Configured with AL32UTF8 or UTF8 character sets

MSSQL

None

CJK Support Issues for Database Installation

The following table lists the support issues for database installation:

If You Are

CJK Support Issue

Creating a Control-M/Server or Control-M/EM database on an Oracle database server

If CJK settings are detected, they are inherited automatically from the database server. Installation continues.

Creating a Control-M/Server or Control-M/EM database on an MSSQL database server

If CJK settings are detected, you are asked whether CJK support is required.

Installing a BMC-supplied PostgreSQL database

Choose the custom option for installation mode. During the custom installation, you are asked whether CJK support is required.

Configuring English Support on Japanese Microsoft Windows 7 and above

This procedure describes how to configure English support on Japanese Microsoft Windows 7 and above. The settings vary according to the version of Windows that is installed.

The system locale for all of the following product components must be set to the same value:

  • Control-M/EM

  • Control-M/Server

  • Control-M/Agent

  • Control-M Application Plug-Ins

Begin

  1. Set the system locale and language settings to English before installing any of the associated Control-M components.

    1. From the Control Panel select Regional Options > Language Settings.

    1. To receive all messages in English, select Western Europe and United States.

    1. At Control Panel > Regional Options > Your locale (location), select English (USA).

  1. After installation, reconfigure your computer for work with a non-English language.

Configuring English Support on Japanese UNIX

This procedure describes how to configure English support on Japanese UNIX systems that run the following components:

  • Control-M/EM

  • Control-M

  • Control-M Reports

  • Control-M/Server

  • Control-M/Agent

  • BMC Batch Impact Manager

  • Control-M Application Plug Ins

Begin

  1. At the command prompt, type locale -a.

    A list of locales available on your computer appears.

  2. Check that C, c, POSIX, or an English locale, as listed in ISO English-character-set locale settings for UNIX or Linux (for Japanese operating systems) is displayed. If none of these locales is displayed, ask your UNIX administrator to install it.

  3. Set the following values in the .cshrc file. If necessary, add lines for these environment variables.

    Add the lines in the same order as the environment variables, as listed in UNIX environment variables for English on Japanese systems in .cshrc.

  4. Run the source ~/.cshrc command to apply the new settings to the environment.

ISO English-Character-Set Locale Settings for UNIX or Linux (for Japanese Operating Systems)

The following table lists the ISO English-character-set locale settings for UNIX or Linux for a Japanese operating system:

Language

AIX, Solaris, Compaq (OSF)

Linux (Red Hat)

Linux (SuSE)

English (USA)

en_US.ISO8859-1

en_US.iso8859-1

en_US

English (British)

en_GB.ISO8859-1

en_US.iso8859-1

en_GB

UNIX Environment Variables for English on Japanese Systems in .cshrc

The following table list the UNIX environment variables for English on Japanese systems in .cshrc:

Environment Variable

Description / Value

LC_ALL

*.UTF-8

LC_CTYPE

LANG

LC_COLLATE

LC_MESSAGES

These environment variables should be C (or c, as defined on the computer).

NOTE: If the C (or c) locale is not present, you can use POSIX or one of the English locales that appear in the previous table.

Set these variables by adding the following lines to the .cshrc file:

setenv LC_CTYPE C

setenv LANG C

setenv LC_COLLATE C

setenv LC_MESSAGES C

CJK Support for Product Files

The following table summarizes the level of CJK support for various types of product files:

File Type

File Names and Paths

File Contents

drafts

English only

CJK (UTF-8)

reports

English only

CJK (UTF-8)

templates (skeletons)

English only

CJK (UTF-8)

OUTPUT (job log)

CJK supported

various CJK encodings

job scripts (for Edit JCL)

CJK supported

various CJK encodings

OS job executable

CJK supported

various CJK encodings

Doc Path (formerly Doc Lib)

CJK supported

various CJK encodings

Doc File (formerly Doc Mem)

CJK supported

various CJK encodings

%%LIBMEMSYM variable

CJK supported

CJK (UTF-8)

xml files

English only

CJK (UTF-8)

command-line arguments*

N/A

on UNIX: CJK (UTF-8)

on Windows: CJK (UTF-8)

file watcher rule file

English only

on UNIX: CJK (UTF-8)

on Windows: CJK (UTF-8)

input_file

English only

on UNIX: CJK (UTF-8)

on Windows: CJK (UTF-8)

CJK Support for Parameters

The following table lists parameters that support CJK characters.

Parameters that accept CJK characters:

Parameter

Subparameter

Application*

 

Command*

 

Condition Name*

 

Lock Resources*

Resource Name

Description

 

Set Variable*

Name

Set Variable*

Value

Do Condition Name*

 

Do Mail*

cc

Do Mail*

Message

Do Mail*

Subject

Do Mail*

To

Notify*

Destination

Notify*

MSG

handle Output*

Prm

Do OUTPUT*

From Class

Doc File* (formerly called Doc Mem)

 

Doc Path* (formerly called Doc Lib)

 

File Name*

 

From Class*

 

Sub Application*

 

Wait for Event*

Name

Job Name*

 

Mem Lib*

 

Mem Name*

 

On Code*

 

On Statement*

 

OUTPUT*

Parameter

Event*

Name

Override Path*

 

Path*

 

Resource Pool*

Name

Shout*

Message

Shout*

To (Destination)

Step Range*

Name

Order Method

 

User Daily Name*

 

Variable (Set Var)*

Name

Variable (Set Var)*

Value

* CJK characters for this parameter are not supported on z/OS.

Parameters that accept English characters only:

Parameter

Subparameter

Component Names

 

Control-M/Server Name

 

Host Names

 

Host Group

 

Host ID

 

Run As

 

Password

 

Periodic Calendar Values

 

Rule Based Calendar

Name

User Name

 

The following are exception alert fields that support CJK special characters:

  • Message

  • Note

  • Key1

  • Key2

  • Key3

  • Key4

  • Key5

CJK Support for Command-Line Utilities

The following table lists the command-line utilities that support CJK characters. These utilities accept parameters in UTF-8 on UNIX and also UTF-8 on Windows.

Product/Component

Command-line Utilities

Control-M

  • ctmdbbck

  • ctmdbcheck

  • ctm_backup_bcp

  • ctm_restore_bcp

  • ctmfw

  • ctmjsa

  • ctmorder

  • ctmsys

  • ctmudly

  • ctmvar

  • ctmdefine

  • ctmcontb

  • ctmcreate

Control-M/Agent

  • ctmorder

  • ctmudly

  • ctmvar

  • ctmdefine

  • ctmcontb

  • ctmcreate

EM servers

These functions include the following operations of the util utility:

  • export data from the Control-M/EM database

  • import data to the Control-M/EM database

  • delete the Control-M/EM database

  • clear the Control-M/EM database

  • build the Control-M/EM database

  • export a specified definition folder

  • export a specified definition SMART folder

  • import a specified definition folder

  • import a specified definition SMART folder

EM clients

XML utilities:

  • defjob

  • exportdefjob

  • updatedef