CONTROL-M Language Customization Guide - … L… · CONTROL-M Language Customization Guide Supporting CONTROL-M/Enterprise Manager version 6.3.01 ... to the GUI Server the first

www.bmc.com

CONTROL-MLanguage Customization Guide

Supporting

CONTROL-M/Enterprise Manager version 6.3.01BMC Batch Impact Manager version 6.3.01CONTROL-M/Server version 6.3.01CONTROL-M/Agent version 6.3.01

December 2006

Contacting BMC Software

You can access the BMC Software website at http://www.bmc.com. From this website, you can obtain information about the company, its products, corporate offices, special events, and career opportunities.

United States and Canada

Address BMC SOFTWARE INC2101 CITYWEST BLVDHOUSTON TX 77042-2827 USA

Telephone 713 918 8800 or800 841 2031

Fax 713 918 8000

Outside United States and Canada

Telephone (01) 713 918 8800 Fax (01) 713 918 8000

Copyright November 20, 2006 BMC Software, Inc., as an unpublished work. All rights reserved.

BMC Software, the BMC Software logos, and all other BMC Software product or service names are registered trademarks or trademarks of BMC Software, Inc.

IBM is a registered trademark of International Business Machines Corporation.

DB2 is a registered trademark of International Business Machines Corporation.

Oracle is a registered trademark, and the Oracle product names are registered trademarks or trademarks of Oracle Corporation.

All other trademarks belong to their respective companies.

BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted rights notices included in this documentation.

Restricted rights legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC SOFTWARE INC, 2101 CITYWEST BLVD, HOUSTON TX 77042-2827, USA. Any contract notices should be sent to this address.

http://www.bmc.com

3

Customer support

You can obtain technical support by using the BMC Software Customer Support website or by contacting Customer Support by telephone or e-mail. To expedite your inquiry, see “Before contacting BMC.”

Support website

You can obtain technical support from BMC 24 hours a day, 7 days a week at http://www.bmc.com/support_home. From this website, you can

■ read overviews about support services and programs that BMC offers■ find the most current information about BMC products■ search a database for issues similar to yours and possible solutions■ order or download product documentation■ report an issue or ask a question■ subscribe to receive proactive e-mail alerts when new product notices are released■ find worldwide BMC support center locations and contact information, including e-mail addresses, fax numbers, and

telephone numbers

Support by telephone or e-mail

In the United States and Canada, if you need technical support and do not have access to the web, call 800 537 1813 or send an e-mail message to [email protected]. Outside the United States and Canada, contact your local support center for assistance.

Before contacting BMC

Have the following information available so that Customer Support can begin working on your issue immediately:

■ product information

— product name— product version (release number)— license number and password (trial or permanent)

■ operating system and environment information

— machine type— operating system type, version, and service pack or other maintenance level such as PUT or PTF— system hardware configuration— serial numbers— related software (database, application, and communication) including type, version, and service pack or

maintenance level

■ sequence of events leading to the issue

■ commands and options that you used

■ messages received (and the time and date that you received them)

— product error messages— messages from the operating system, such as file system full— messages from related software

http://www.bmc.com/support_home

mailto:[email protected]

4 CONTROL-M Language Customization Guide

ContentsChapter 1 Western European configuration 9

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Compatibility with prior versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Upgrade and migration considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Additional resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Configuration procedure task flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Additional considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

General configuration on Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Setting the default Microsoft Windows command prompt code page . . . . . . . . . 15Set the default code page using Microsoft Windows registry . . . . . . . . . . . . . . . . 15

General configuration on UNIX and Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Additional CONTROL-M/EM configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Database configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Select the procedure for your database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Oracle configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Sybase configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23MSSQL configuration for the CONTROL-M/EM database . . . . . . . . . . . . . . . . . . 27MSSQL configuration for the CONTROL-M/Server database . . . . . . . . . . . . . . . 29MSSQL configuration for clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Chapter 2 East Asian (CJK) configuration 33

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Compatibility with prior versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Upgrade and migration considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Additional resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Configuration procedure task flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Additional considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

General pre-installation configuration on Microsoft Windows . . . . . . . . . . . . . . . . . . 36General pre-installation configuration on UNIX and Linux . . . . . . . . . . . . . . . . . . . . . 37

I18N System parameter for CONTROL-M/EM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Database configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38General post-installation configuration on UNIX and Linux . . . . . . . . . . . . . . . . . . . . 39CONTROL-M/Agent post-installation configuration . . . . . . . . . . . . . . . . . . . . . . . . . 40Configuring RJX job submission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Contents 5

Appendix A Parameters that support Western European special characters 43

Chapter B English configuration on Japanese-enabled systems 47

Configuration procedure task flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Configuration tasks for English support on Japanese UNIX . . . . . . . . . . . . . . . . . . . . 48Configuration tasks for English support on Japanese Microsoft Windows . . . . . . . . 50

Appendix C CJK support for product objects 51

CJK support for product files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51CJK support for parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52CJK support for command line utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Index 57


Tables 7

TablesConfiguration tasks for Western European language support . . . . . . . . . . . . . . . . . . 12ISO Latin-1 character set locale settings for UNIX and Linux . . . . . . . . . . . . . . . . . . . 17UNIX environment variables for West European languages in the .cshrc file . . . . . 18Setting system parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Possible character sets outputs and corresponding actions for Oracle . . . . . . . . . . . . 21Configuration tasks for East Asian language support . . . . . . . . . . . . . . . . . . . . . . . . . . 35CJK character set locale settings for UNIX and Linux . . . . . . . . . . . . . . . . . . . . . . . . . . 38Prerequisites for existing databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38CJK-support issues for database installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38CJK character set locale settings for operating system jobs . . . . . . . . . . . . . . . . . . . . . 40CONTROL-M/Agent language encodings available through ctmunixcfg . . . . . . . . 41CONTROL-M/Agent language encodings available through ctmwincfg . . . . . . . . . 41Parameters that support Western European special characters . . . . . . . . . . . . . . . . . . 43Exception alert fields that support western European special characters . . . . . . . . . 45Configuration tasks for English language support on Japanese systems . . . . . . . . . . 47ISO English character set locale settings for UNIX and Linux (for Japanese operating

systems) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49UNIX environment variables for English on Japanese systems in .cshrc . . . . . . . . . 49CJK support level for product files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Parameters that accept East Asian characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Parameters that accept English characters only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Exception alert fields that support East Asian special characters . . . . . . . . . . . . . . . . 54Command line utilities that support CJK characters . . . . . . . . . . . . . . . . . . . . . . . . . . . 54


Chapter 1 Western European configuration 9

C h a p t e r 11 Western European configuration

This chapter describes configuration procedures for the following Western European languages:

■ English (USA)■ English (British)■ Spanish■ German■ French

Introduction Instructions are provided for configuring CONTROL-M/EM, CONTROL-M/Server, CONTROL-M/Agent, and database servers (Oracle, Sybase, and MSSQL) to enable the support of Western European language special characters for the following components:

■ The CONTROL-M/EM GUI

■ CONTROL-M/Desktop■ CONTROL-M/Server utilities■ CONTROL-M/Agent utilities■ CONTROL-M/Forecast■ BMC Batch Impact Manager■ The Reporting facility

These components can accept characters in English, German, Spanish, and French from the Latin-1 character set (ISO 8859-1) in almost all text fields and parameters.

Introduction


The following characters are not supported for any parameter under any circumstances:

Compatibility with prior versions

CONTROL-M/EM can communicate in English with CONTROL-M/Servers from versions prior to version 6.2.01 that do not handle Western European language special characters, as well as CONTROL-M for z/OS installations. 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.

Before you begin

The tasks in this section indicate how to check and set the locale. Locale settings must be the same on every computer or UNIX account running CONTROL-M/EM, CONTROL-M/Server, CONTROL-M/Agent, and BMC Batch Impact Manager.

NOTE For a list of parameters that support Western European Language special characters, see Appendix A, “Parameters that support Western European special characters.”

WARNING Perform customization tasks on every computer or UNIX account running CONTROL-M/EM, CONTROL-M/Server, CONTROL-M/Agent, and BMC Batch Impact Manager. Coordinate this effort for each product across the entire enterprise. Problems can occur if all products are not configured the same way.

WARNING Conflicts between the locale settings on each computer and UNIX account, especially if they involve different character sets, can corrupt your data.

Configuration procedure task flow


Upgrade and migration considerations

■ The processes for upgrading or migrating to CONTROL-M version 6.3.01 do not automatically configure the database for ISO Latin-1 language support.

■ When working with an existing Sybase database server: The upgrade and migrate procedures do not configure the database server when using a database that was created by a previous installations, or one that was created by the customer.

■ When using an MSSQL database server, the database must be configured as case-sensitive when working with foreign languages. For more information, see the appendix entitled "Working with CONTROL-M/EM Databases that are not Case-Sensitive" in the CONTROL-M/Enterprise Manager Installation Guide.

Additional resources

For additional information, see the following:

Configuration procedure task flow Table 1 on page 12 lists:

■ tasks for configuring language support■ computers on which the tasks should be performed■ links to the instructions for performing the task

These tasks can be performed in any order.

Task Topic and book

List the parameters that support Western European Language special characters

Appendix A, “Parameters that support Western European special characters”

Indicate the parameters that do not support Western European Language special characters

Individual parameter descriptions in the CONTROL-M Job Parameter and Variable Reference Guide

Perform a migration CONTROL-M/EM Migration Guide



Additional considerations

Table 1 Configuration tasks for Western European language support

Task Perform on computers running components of these products

“General configuration on Microsoft Windows”

■ CONTROL-M/EM■ CONTROL-M/Desktop■ CONTROL-M/Server■ CONTROL-M/Agent■ BMC Batch Impact Manager■ CONTROL-M/Forecast

“General configuration on UNIX and Linux”

■ CONTROL-M/EM■ CONTROL-M/Desktop■ CONTROL-M/Server■ CONTROL-M/Agent■ BMC Batch Impact Manager■ CONTROL-M/Forecast

“Additional CONTROL-M/EM configuration”

■ CONTROL-M/EM

“Database configuration” ■ Any one database client that connects to the Database Server (Oracle, Sybase, or MSSQL)

Product / component Comments

CONTROL-M/Desktop When CONTROL-M/Desktop is first installed, its language is set according to the local settings of the computer. When CONTROL-M/Desktop connects to the GUI Server the first time, CONTROL-M/Desktop language settings are automatically updated to match those of CONTROL-M/EM.

CONTROL-M Control Modules

Language configuration for Control Modules is handled when CONTROL-M/Agent is configured for language support. Additional language configuration is not necessary for Control Modules.

General configuration on Microsoft Windows


General configuration on Microsoft Windows Perform this task to enable specification of Western European special characters from the Latin-1 character set. Perform this task on every Microsoft Windows computer running components of the following products:

■ CONTROL-M/EM

■ CONTROL-M/Server ■ CONTROL-M/Agent ■ CONTROL-M/Desktop■ The Reporting facility■ CONTROL-M/Forecast■ BMC Batch Impact Manager■ CONTROL-M Control Modules

To configure the environment on Microsoft Windows

1 In the Input Locales panel of the Regional Options menu, remove any Input languages that belong to an ISO group that blocks the specification of Latin-1 languages in the ISO-1 group.

2 For CONTROL-M components to communicate properly with each other, you must set the Locale for all product components to the same value.

Ensure that the required language locale is present on the computer using the procedure relevant to your operating system.

Microsoft Windows 2000

A From the Start menu, choose Settings => Control Panel and select Regional Options.

B In the Input Locales panel, add the language to the list of installed input locales. Click OK.

WARNING Discrepancies between Locale settings, especially those involving different character sets, can corrupt data while data is passed from one component to another.



Microsoft Windows XP and 2003

A Choose Settings => Control Panel => Regional and Language Options from the Start menu.

B Using the Details field in the Languages tab, add the language to the list of installed input locales. Click OK.

3 Configure the Command Prompt window code page.

A Open a Command Prompt window by choosing Run from the Start menu and typing cmd. Press Enter.

B To set the code page for the currently active Command Prompt window, type chcp 1252 and press Enter. Active Code Page: 1252 is displayed.

4 Configure the font of the Command Prompt window.

A Right-click the upper-left corner of the Command Prompt window and select the Properties option.

B Set the font on the Font tab to Lucida Console and click OK.

NOTE You must perform step B each time you open a Command Prompt window to configure Western European language support. For instructions on setting the Command Prompt code page on a permanent basis, see page 15.



C At the prompt, select the Save properties for future windows with same title option to save the properties as a default. These changes are set automatically each time a Command Prompt window is opened. Click OK.

Where to go from here

You have performed the general configuration tasks in the Microsoft Windows environment. Perform the remaining procedures listed in Table 1 on page 12 as relevant at your site.

Setting the default Microsoft Windows command prompt code page

This optional task sets the default code page to 1252 for all Microsoft Windows Command Prompt windows.

If this task is not performed, the code page must be set manually each time a Microsoft Windows Command Prompt window is opened.

Set the default code page using Microsoft Windows registry

1 Define the following entry in the Microsoft Windows Registry:

WARNING BMC Software recommends that only users experienced with the Microsoft Windows Registry attempt to edit it, and only after backing it up first.

User Key: [HKEY_LOCAL_MACHINE\Software\Microsoft\CommandProcessor]Value Name: AutoRunData Type: REG_SZ (String Value)Value Data: chcp 1252

General configuration on UNIX and Linux


■ If the AutoRun entry does not exist, create it:

— Click the right mouse button inside the right pane.— Choose New => String Value.— Specify AutoRun as the entry name.

■ If the entry exists with another value that you want to keep:

— Create a batch file containing the original value on the first line and the command chcp 1252 on the second line.

— Save the batch file in a location that is in the path environment variable.— Specify the batch file name as the entry value data.


You have completed setting the default code page. Perform the remaining substeps under step 3 on page 14.

General configuration on UNIX and Linux Perform this task to enable specification of Western European special characters from the Latin-1 character set.

This task must be performed on every computer or UNIX account running components of the following products:

■ CONTROL-M/EM

■ CONTROL-M/Server■ CONTROL-M/Agent■ BMC Batch Impact Manager■ CONTROL-M Control Modules

NOTE Alternatively, you can create a .reg file to update the Microsoft Windows registry:

Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\Software\Microsoft\CommandProcessor]"CompletionChar"=dword:00000000"DefaultColor"=dword:00000000"EnableExtensions"=dword:00000001"AutoRun"="chcp 1252"



To configure the environment on UNIX or Linux

1 For all CONTROL-M components to communicate properly with each other, you must set the Locale for all product components to the same value.

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

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

B Check that the language locale appears according to Table 2. If the locale is missing, ask your UNIX administrator to install it.

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

WARNING Discrepancies between Locale settings, especially those involving different character sets, can corrupt data while data is passed from one component to another.

Table 2 ISO Latin-1 character set locale settings for UNIX and Linux

LanguageAIX, Solaris, Compaq (OSF) HP-UX Linux (RedHat) Linux (SuSE)

English (USA) en_US.ISO8859-1 en_US.iso88591 en_US.iso88591 en_US

English (British) en_GB.ISO8859-1 en_GB.iso88591 en_GB.iso88591 en_GB

German de_DE.ISO8859-1 de_DE.iso88591 german german

French fr_FR.ISO8859-1 fr_FR.iso88591 french french

Spanish es_ES.ISO8859-1 es_ES.iso88591 spanish spanish

NOTE When configuring CONTROL-M/Agent on operating systems not listed in Table 2, use the locale setting for the operating system that corresponds to the one selected for CONTROL-M/EM and CONTROL-M/Server. Contact your UNIX administrator for additional assistance.

NOTE The lines should be added in the same order as the environment variables are listed in Table 3 on page 18.



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

Table 3 UNIX environment variables for West European languages in the .cshrc file

Environment variable Description / value

LC_ALL This environment variable should be ““ (an empty string). Set this variable by adding the following line to the .cshrc file:

setenv LC_ALL ““

LC_CTYPE andLANG

These environment variables should be set to the value of the required language locale. See Table 2 on page 17 for UNIX locales.Set these variables by adding the following lines to the .cshrc file:

setenv LC_CTYPE localeNamesetenv LANG localeName

LC_COLLATE This environment variable should be C for all languages (or c, as defined on the computer). To check if the C locale is present, use the locale -a command.

Note: If the C (or c) locale is not present, you can use POSIX or one of the English locales that appear in Table 2 on page 17.

Set this variable by adding the following line to the .cshrc file:setenv LC_COLLATE C

LC_MESSAGES For CONTROL-M/Server only: This environment variable should be C (or c, as defined on the computer) for all languages on accounts where CONTROL-M/Server is installed. To check if the C locale is present, use the locale -a command.

Note: If the C (or c) locale is not present, you can use POSIX or one of the English locales that appear in Table 2 on page 17.

Set this variable by adding the following line to the .cshrc file:setenv LC_MESSAGES C

EXAMPLE The following examples reflect the values that are set after applying the values to the environment in the next step.

LC_ALL=LC_CTYPE=de_DE.ISO8859-1LANG=de_DE.ISO8859-1LC_COLLATE=CLC_MESSAGES=C

Additional CONTROL-M/EM configuration



Perform the remaining procedures listed in Table 1 on page 12 that are relevant at your site.

Additional CONTROL-M/EM configuration Perform this task on computers running CONTROL-M/EM components to enable specification of Western European special characters from the Latin-1 character set.

This task must be performed on every computer or UNIX account running components of the following products:

■ CONTROL-M/EM

■ CONTROL-M/Desktop■ BMC Batch Impact Manager■ The Reporting facility

To configure the CONTROL-M/EM environment

1 Set the following system parameters by choosing Tools => System Parameters in the Configuration Manager.

Table 4 Setting system parameters

Parameter Section Description

Language General This parameter defines the language for the entire CONTROL-M enterprise. Valid values:

■ use_account_locale for the local system locale as defined on the account or computer.

■ English for both American and British English.■ German for German.■ French for French.■ Spanish for Spanish.

These values are not case-sensitive.

Database configuration


2 If CONTROL-M components were running when these system parameters were modified, recycle the components.



Database configuration This task configures the database servers and clients. Configure the database server and clients for the language according to the database vendor.

Select the procedure for your database

EBCDIC_cp Gateway This parameter is relevant for CONTROL-M for z/OS users only. It defines the EBCDIC code page to which ASCII data is translated.Note: The same character set code should be defined in CONTROL-M for z/OS. Valid values:

■ 0 for the default translation table created in a previous version of CONTROL-M.

■ 1047 for English (USA)■ 285 for English (British)■ 273 for German■ 297 for French■ 284 for Spanish

Notes: Use the Comp. Name field to set the scope for this parameter. Specify a specific CONTROL-M name in the Comp. Name field, or an asterisk * for all CONTROL-Ms. See the instructions for displaying and modifying system parameters in the CONTROL-M/Enterprise Manager Administrator Guide.

I18N General Set automatically by the system to value latin1.

Task Reference

“Oracle configuration” page 21

“Sybase configuration” page 23

“MSSQL configuration for the CONTROL-M/EM database” page 27

Table 4 Setting system parameters

Parameter Section Description



Oracle configuration

Run this procedure for your Oracle database to support Western European language special characters.

Perform this task once, on any computer with a database client that connects to the Oracle database server.

To configure Oracle

1 Check the database configuration from within an SQLPLUS session.

A Check the character set currently in use with the following command:

select value from nls_database_parameters where parameter='NLS_CHARACTERSET';

Depending on the output displayed, take the appropriate actions as indicated in Table 5.

“MSSQL configuration for the CONTROL-M/Server database” page 29

“MSSQL configuration for clients” page 30

NOTE Do not perform this task for all database clients.

Table 5 Possible character sets outputs and corresponding actions for Oracle

Output Description and ActionVALUE------------------------WE8ISO8859P1

The current character set is compatible with the ISO Latin-1 character set. No changes are necessary. Continue with step C below.

VALUE------------------------US7ASCII

The current character set is not compatible with the ISO Latin-1 character set, but can be changed. Continue with step C below.

Any other output The current character is not compatible. To find out if character set conversion is possible without data loss, continue with step B.

Task Reference



B To verify that character set conversion is possible without data loss, run the Oracle Scanner utility (csscan.exe in the Oracle binaries directory). This utility simulates the new character sets and generates a report containing the (system or user) objects that are affected if the character set is changed. For the latest version of the utility and information about running it, see the Oracle OTN site at http://otn.oracle.com/software/tech/globalization/index.html.

If the conversion completes successfully and no problems are indicated in the generated report, continue with the following steps. If problems are listed in the report, contact BMC Software Customer Support.

C Check the sort order:

select * from nls_database_parameters where parameter in ('NLS_COMP','NLS_SORT');

The output should be similar to the following, indicating the binary sort order:

PARAMETER VALUE-------------------------- -----------NLS_SORT BINARYNLS_COMP BINARY

If the sort order is different, contact BMC Software Customer Support. Do not continue customizing Western European language support.

Skip the remaining steps if, after checking the database configuration in Step 1, the current database configuration is compatible with the ISO Latin-1 character set and a binary sort.

2 Shut down all CONTROL-M/EM and CONTROL-M/Server components and applications that may connect to the database server.

3 Export the data by running the command appropriate for the application (as a safety precaution):

Application/component Command

CONTROL-M/EM UNIX:ecs util -U user -P password -export -type all -file exportFile

Microsoft Windows:util -U user -P password -export -type all -file exportFile

CONTROL-M/Server ctm_backup_bcp

http://otn.oracle.com/software/tech/globalization/index.html



4 Log in to the SQLPLUS application with administrator privileges using the following commands:

5 Shut down the database using the command:

6 Run the following command sequence to configure the database character set:

7 For the changes to take effect, run the following commands to shut down and restart the database:

8 Restart all components that you shut down.



Sybase configuration

Run this procedure for your Sybase Adaptive server to support Western European language special characters.

Perform this task once using the System Administrator login name of the Sybase Adaptive server.

sqlplus /nologconnect / as sysdba

SHUTDOWN IMMEDIATE;

STARTUP MOUNT;

ALTER SYSTEM ENABLE RESTRICTED SESSION;

ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0;

ALTER SYSTEM SET AQ_TM_PROCESSES=0;

ALTER DATABASE OPEN;

ALTER DATABASE CHARACTER SET INTERNAL_USE WE8ISO8859P1;

SHUTDOWN IMMEDIATE

STARTUP;



To configure Sybase

1 Check the character set by running the following commands within the isql session.

A Check the character set by running the following command:

sp_configure "default character set id"go

If the output is a number other than 1, you must configure the character set.

B Check the sort order by running the following command:

sp_configure "default sortorder id"go

If the output is a number other than 50, you must configure the sort order.

Skip the remaining steps if, after checking the database configuration in Step 1, the current database configuration is compatible with the ISO Latin-1 character set and a binary sort.


3 Export the data by running the command appropriate for the application:

4 Drop the database by running the command appropriate for the application.

WARNING If the database server was originally configured for the Roman-8 character set, and extended ASCII characters (with an ASCII value greater than 128) were used, some data might be lost when reconfiguring the database. Contact BMC Software Customer Support.

Application / component Command

CONTROL-M/EM UNIX: ecs util -U user -P password -export -type all -file exportFile

Microsoft Windows:util -U user -P password -export -type all -file exportFile

CONTROL-M/Server ctm_backup_bcp



5 To configure either or both the character set or the sort order, perform the following steps.

A Change to the directory where the Sybase Adaptive server is installed:

UNIX: cd $SYBASE/charsets/iso_1

Microsoft Windows: cd %SYBASE%\charsets\iso_1

B Run the following command:

charset -U user -P password -S serverName binary.srt

C Run the following command from within an ISQL session to change the character set:

sp_configure "default character set id",1

D Run the following command to change the sort order:

sp_configure "default sortorder id",50

Application / Component Command

CONTROL-M/EM UNIX:ecs util -U user -P password -clean_database

Microsoft Windows:util -U user -P password -clean_database

CONTROL-M/Server Skip this step.

NOTE Changing of the character set and sort order of the database server affects all databases associated with the database server. You cannot retain the original sort order and character set for a database on the same database server that does not relate to CONTROL-M/EM or CONTROL-M.

To handle this situation, install another database server and create a new database for use with CONTROL-M/EM or CONTROL-M/Server, as necessary. The sort order and character set for the new database server should be configured according to step A through step D.



6 Rebuild the database.

7 Import the data.

8 Restart all components previously shut down.



Application / component Action

CONTROL-M/EM Run the following command according to the operating system:

UNIX:ecs util -U user -P password -build_schema

Microsoft Windows:util -U user -P password -build_schema

CONTROL-M/Server Use the CONTROL-M Main menu to rebuild the database using the Database Creation menu described in the Maintenance chapter in the CONTROL-M/Server Administrator Guide.

Application/component Command

CONTROL-M/EM UNIX: ecs util -U user -P password -import -replace -type all -file exportFile

Microsoft Windows:util -U user -P password -import -replace -type all -file exportFile

exportFile is the name of the file exported in step 3 on page 24.

CONTROL-M/Server ctm_restore_bcp



MSSQL configuration for the CONTROL-M/EM database

Run this procedure for your CONTROL-M/EM MSSQL database to support Western European language special characters.

To configure the MSSQL Server database

1 Log in as a regular user to the database that you want to configure for Western European language support.

2 Check the character set, code page, and sort order of the database configuration by running the following command from within the isql session:

Check the following database collation attributes. If an attribute does not match, you have to reconfigure the database.

If all the attributes match, you do not need to reconfigure the database. Skip the remaining steps and perform the instructions for “MSSQL configuration for clients” on page 30.


4 Export the data by running the following command:

5 Drop the database by running the following command.

declare @X varchar(40)

SELECT @X=CAST(DATABASEPROPERTYEX( db_name() , 'Collation' ) AS VARCHAR)

SELECT 'Database Collation: ' + description FROM ::fn_helpcollations() WHERE name=@X

SELECT 'Database Code Page ' + CAST(COLLATIONPROPERTY(@X, 'CodePage') As VARCHAR)

Attribute Value

Character Set Latin1-General

Sort Order binary sort

Database Code Page 1252

util -U user -P password -export -type all -file exportFile

util -U user -P password -clean_database



6 Configure the database server for the ISO-1 character set, code page 1252, and the binary sort order.

A Find the database name using the command:

select db_name()

B Verify that the database is empty using the query:

select count(*) from sysobjects where type='U' and name <>'dtproperties'

C Use the following command to verify that no other user is connected to this specific database:

select count(*) from master..sysprocesses where dbid=DB_ID()

D Log in as a system administrator and run the following command:

Alter database databaseName Collate Latin1_General_BIN

7 Rebuild the database by running the following command:

8 Load the data by running the following command:

exportFile is the name of the file exported in step 4 on page 27.


NOTE If the database is not empty (meaning, the output from the previous query is not equal to 0), contact BMC Software Customer Support.

NOTE If other users or applications are currently connected to the database (meaning, the output from the previous query is not equal to 1: you), request that all users disconnect and shut down all connected applications.

util -U user -P password -build_schema

util -U user -P password -import -replace -type all -file exportFile




Configure the MSSQL clients using the instructions provided in “MSSQL configuration for clients” on page 30.

MSSQL configuration for the CONTROL-M/Server database

Run this procedure for your CONTROL-M/Server MSSQL database to support Western European language special characters.

Perform this task once on any computer with a database client that connects to the MSSQL database server.

To configure the MSSQL Server

1 Log in as a regular user to the database that you want to configure for Western European language support.

2 Check the character set, code page, and sort order of the database configuration by running the following command from within the isql session:

Check the following database collation attributes. If an attribute does not match, reconfigure the database.

NOTE Do not perform this task for all database clients.

declare @X varchar(40)

SELECT @X=CAST(DATABASEPROPERTYEX( db_name() , 'Collation' ) AS VARCHAR)

SELECT 'Database Collation: ' + description FROM ::fn_helpcollations() WHERE name=@X

SELECT 'Database Code Page ' + CAST(COLLATIONPROPERTY(@X, 'CodePage') As VARCHAR)

Attribute Value

Character Set Latin1-General

Sort Order binary sort

Database Code Page 1252



If all the attributes match, you do not need to reconfigure the database. Skip the remaining steps and perform the instructions for “MSSQL configuration for clients” on page 30.


4 Export the data by running the following command:

5 Specify the following command:

This process deletes the MSSQL database and rebuilds it configured for Western European language special characters.

6 Load the data by running the following command.



Configure the MSSQL clients using the instructions provided in “MSSQL configuration for clients.”

MSSQL configuration for clients

Run these procedures for MSSQL database clients that need to support Western European language special characters.

Perform these tasks on every computer with an MSSQL database client, including: ■ Gateway■ GUI Server■ CONTROL-M/Server■ Global Condition Server (GCS)■ Global Alert Server (GAS)

ctm_backup_bcp

ctmmakedb -existing

ctm_restore_bcp



To check that the value of the Default Language parameter is correct

1 Using a login name with administrator privileges, choose Start => Programs => Microsoft SQL Server => Enterprise Manager.

2 In the Tree view, expand SQL Server directory => Security => Logins.

3 For your login name, check if the value for Default Language is correct. If it is not, configure it properly.

To configure MSSQL clients

1 Choose Start => Programs => Microsoft SQL Server => Client Network utility. The SQL Server Client Network Utility dialog box is displayed.

2 Select the DB-Library Options panel.

3 Clear the checkmark for the Automatic ANSI to OEM conversion field.

4 Check the Use international settings field.

5 Click OK.






C h a p t e r 22 East Asian (CJK) configuration

This chapter describes configuration procedures for the following East Asian languages:

■ Traditional Chinese■ Simplified Chinese■ Japanese■ Korean

Introduction Instructions are provided for the configuration tasks that enable the support of East Asian characters on the following CONTROL-M components:

■ The CONTROL-M/EM GUI■ CONTROL-M/Server■ CONTROL-M/Agent■ The Reporting facility■ CONTROL-M/CM for AFT

NOTE

For a list of files, parameters, and command line utilities that support East Asian characters, see Appendix C, “CJK support for product objects.”

Introduction


Compatibility with prior versions

CONTROL-M/EM can communicate in English with CONTROL-M/Servers from versions prior to version 6.3.01 that do not handle East Asian characters, as well as CONTROL-M for z/OS installations. 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.

Upgrade and migration considerations

■ Upgrading or migrating to CONTROL-M version 6.3.01 with support for East Asian languages is possible only from an English-language installation. You cannot upgrade or migrate from installations set to other Western European languages.

■ If you are migrating from an English-language database, the migration procedures will work only if the target database server is configured for East Asian language support.

Additional resources

For additional information, see the following:

Task Topic and book

List the parameters, fields, and files that support East Asian characters

Appendix C, “CJK support for product objects”

Perform a migration CONTROL-M/EM Migration Guide



Configuration procedure task flow Table 6 on page 35 lists:

■ tasks for configuring language support■ computers on which the tasks should be performed■ links to the instructions for performing the task

Additional considerations

Table 6 Configuration tasks for East Asian language support


“General pre-installation configuration on Microsoft Windows”

■ CONTROL-M/EM■ CONTROL-M/Server■ CONTROL-M/Agent■ CONTROL-M Control Modules

“General pre-installation configuration on UNIX and Linux”

“Database configuration” ■ Oracle, Sybase, or MSSQL database client and server

“General post-installation configuration on UNIX and Linux”


“CONTROL-M/Agent post-installation configuration”


Product / component Comments

CONTROL-M/Desktop When CONTROL-M/Desktop is first installed, its language is set according to the local settings of the computer. When CONTROL-M/Desktop connects to the GUI Server for the first time, CONTROL-M/Desktop language settings are automatically updated to match those of CONTROL-M/EM.

CONTROL-M Control Modules

Only the CONTROL-M/Control Module for Advanced File Transfer supports East-Asian language characters. The basic language setting (either Latin-1 or CJK) is inherited from the CONTROL-M/Agent (see step 1 under “CONTROL-M/Agent post-installation configuration” on page 40). In addition, when configuring Advanced File Transfer accounts, you must specify the language encoding of the FTP server through the Language parameter of the Account Management utility.

BMC Batch Impact Manager and CONTROL-M/Forecast

BMC Batch Impact Manager and CONTROL-M/Forecast do not support East-Asian language characters.

General pre-installation configuration on Microsoft Windows


General pre-installation configuration on Microsoft Windows

To enable the use of East Asian characters, perform the task described in this section before product installation on any Microsoft Windows computer that will run components of the following products:

■ CONTROL-M/EM

■ CONTROL-M/Server ■ CONTROL-M/Agent ■ CONTROL-M Control Modules

To configure the environment on Microsoft Windows 2000

1 From the Start menu, choose Settings => Control Panel and select Regional Options.

2 On the Input Locales tab, add the desired language to the list of installed input locales.

3 On the General tab, enable the desired language by clicking its checkbox.

4 Press the Set default button, select the appropriate locale for the desired language in the Select System Locale dialog box, and click OK.

5 Click OK in the Regional Options dialog box to finalize the configuration.

Microsoft Windows XP and 2003

1 Choose Settings => Control Panel => Regional and Language Options from the Start menu.

2 On the Language tab, ensure that Install files for East Asian languages is checked.

3 On the Advanced tab, select the required language under Language for non-Unicode programs.

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

General pre-installation configuration on UNIX and Linux


Ensure that the corresponding code page is selected on the list of Code page conversion tables. CONTROL-M support for East Asian languages is based on the following code pages:

■ 932: ANSI/OEM - Japanese Shift-JIS■ 936: ANSI/OEM - Simplified Chinese GBK■ 949: ANSI/OEM - Korean■ 950: ANSI/OEM - Traditional Chinese Big5

4 Click OK.

General pre-installation configuration on UNIX and Linux

To enable the use of East Asian characters, perform the task described in this section before product installation on any computer or UNIX account that will run components of the following products:

■ CONTROL-M/EM

■ CONTROL-M/Server■ CONTROL-M/Agent■ CONTROL-M Control Modules

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


B Check that the language locale appears according to Table 7. If the locale is missing, ask your UNIX administrator to install it.

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

NOTE When configuring CONTROL-M/Agent on operating systems not listed in Table 7, use the locale setting for the operating system that corresponds to the one selected for CONTROL-M/EM and CONTROL-M/Server. Contact your UNIX administrator for additional assistance.



I18N System parameter for CONTROL-M/EM

The I18Nparameter is set automatically by the system to value CJK.

Database configuration Before creating a CONTROL-M/Server database on an existing database server, ensure that the existing database server fulfills the prerequisites listed in Table 8:

Table 9 summarizes additional CJK-support issues that you must take into consideration during installation or creation of the database:

Table 7 CJK character set locale settings for UNIX and Linux

Language AIX HP-UX Solaris Linux

Chinese (Simplified) ZH_CN.UTF-8 zh_CN.utf8 zh.UTF-8 zh_CN.utf8

Chinese (Traditional) ZH_TW.UTF-8 zh_TW.utf8 zh_TW.UTF-8 zh_TW.utf8

Japanese JA_JP.UTF-8 ja_JP.utf8 ja_JP.UTF-8 ja_JP.utf8

Korean KO_KR.UTF-8 ko_KR.utf8 ko.UTF-8 ko_KR.utf8

Table 8 Prerequisites for existing databases

Type of existing database Prerequisites

Sybase Configured with UTF8 character sets

Oracle Configured with AL32UTF8 or UTF8 character sets

MSSQL Database instance with a far east server collation for one of the following Windows code page:

■ 932 for Japanese■ 936 for Simplified Chinese■ 949 for Korean■ 950 for Traditional Chinese

Table 9 CJK-support issues for database installation

Database installation task CJK-support issue

Creating a CONTROL-M/Server database on an existing Oracle or Sybase database server

If CJK settings are detected, they are inherited automatically from the database server and installation continues accordingly.

General post-installation configuration on UNIX and Linux


For more information regarding database installation, see the CONTROL-M/Enterprise Manager Installation Guide.

General post-installation configuration on UNIX and Linux

Perform this task after product installation to enable the use of East Asian characters. Perform this task on every computer or UNIX account running components of the following products:

■ CONTROL-M/EM

■ CONTROL-M/Server ■ CONTROL-M/Agent ■ CONTROL-M Control Modules

1 In the .cshrc file, set the LC_CTYPE environment variable to the value of the required language locale (see Table 7 on page 38 for UNIX locales), by adding or editing the following line:

setenv LC_CTYPE <localeName>

All other environment variables pertaining to locale in the .cshrc file are set automatically during installation to the following values:

LC_ALL=““ (an empty string)LANG=CLC_COLLATE=CLC_MESSAGES=C

Creating a CONTROL-M/Server database on an existing MSSQL database server

If CJK settings are detected on the database server during the installation, you are explicitly asked whether CJK character support is required.

Installing a dedicated (BMC Software supplied) Oracle or Sybase database server

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

EXAMPLE setenv LC_CTYPE KO_KR.UTF-8

Table 9 CJK-support issues for database installation

Database installation task CJK-support issue

CONTROL-M/Agent post-installation configuration



CONTROL-M/Agent post-installation configuration

Language and locale configuration must be performed for each CONTROL-M/Agent through the Agent Configuration utilities, as described in the following procedure.

1 Run the ctmagcfg command line utility through a command prompt. For the Foreign Language Support parameter, specify the value CJK (the default is Latin-1).

2 Set the encoding used for running jobs by the CONTROL-M/Agent.

A Ensure that the required language locale or code page is present on the computer. (On UNIX, use the locale -a command.) Table 10 lists the locales supported by CONTROL-M/Agent on the various operating systems.

B On UNIX, ensure that the environment of the owner responsible for running jobs is set to the correct locale.

C Set the language encoding for jobs that are run by the CONTROL-M/Agent, through the appropriate command line utility.

Table 10 CJK character set locale settings for operating system jobs

Language AIX HP-UX Solaris Linux Windows

Chinese (Simplified)

ZH_CN.UTF-8Zh_CN.GBKZh_CN.GB18030

zh_CN.utf8zh_CN.gb18030

zh.UTF-8 zh.GBKzh_CN.GB18030

zh_CN.utf8zh_CN.gb18030zh_CN.gbk

CP936

Chinese (Traditional)

ZH_TW.UTF-8Zh_TW.big5zh_TW.IBM-eucTW

zh_TW.utf8zh_TW.big5zh_TW.eucTW

zh_TW.UTF-8zh_TW.BIG5zh_TW (EUC)

zh_TW.utf8zh_TW.big5zh_TW.euctw

CP950

Japanese JA_JP.UTF-8JA_JP.IBM-eucJPJa_JP.IBM-943

ja_JP.utf8ja_JP.eucJPja_JP.SJIS

ja_JP.UTF-8ja_JP.eucJPja_JP.PCK (Shiftjis)

ja_JP.utf8ja_JP.eucjpja_JP.PCK (Shiftjis)

CP932

Korean KO_KR.UTF-8KO_KR.IBM-eucKR

ko_KR.utf8ko_KR.eucKR

ko.UTF-8ko (EUC)

ko_KR.utf8ko_KR.euckr

CP949

NOTE

The CONTROL-M/Agent assumes that all jobs will be run in the same user-defined locale.

Configuring RJX job submission


■ On UNIX, run the ctmunixcfg command line utility and set the CJK Encoding parameter to one of the available language encodings (as listed in Table 11).

■ On Windows, run the ctmwincfg command line utility and set the CJK Encoding parameter to one of the available language encodings (as listed in Table 12).

Configuring RJX job submissionWhen you require jobs to run with a specific CJK encoding on a remote host, you must configure the remote host with Agents that are set to the required encoding as defined in Table 11 and Table 12.

Remote host Agents must be selected according to the encoding available on Windows or UNIX platforms. Windows CJK encoding is available only on Agents installed on Windows platforms. Similarly UNIX CJK encoding is available only on Agents installed on UNIX platforms.

For more information regarding Agent configuration, see the CONTROL-M/Agent for UNIX and Microsoft Windows Administrator Guide.

Table 11 CONTROL-M/Agent language encodings available through ctmunixcfg

Job language option Encoding

UTF-8 *.UTF-8

Japanese EUC *.eucJP

Japanese SHIFT-JIS Ja_JP.IBM-943ja_JP.SJISja_JP.PCK

Korean EUC *.eucKR

Simplified Chinese GBK *.GBK

Simplified Chinese GB *.GB18030

Traditional Chinese EUC *.eucTW

Traditional Chinese BIG5 *.big5

Table 12 CONTROL-M/Agent language encodings available through ctmwincfg

Job language option Encoding

Japanese CP932

Korean CP949

Simplified Chinese CP936

Traditional Chinese CP950

UTF-16 UNICODE

Configuring RJX job submission



A p p e n d i x AA Parameters that support Western European special characters

This appendix lists parameters that support Western European language special characters.

NOTE Discrepancies between the language support for a parameter for z/OS and other platforms is noted where relevant.

Table 13 Parameters that support Western European special characters (Part 1 of 3)

Parameter Subparameter

Application

Application Type

Author

Auto Edit (Set Var) Name

Auto Edit (Set Var) Value

Calendar Description

Calendar Name

Command

Condition Name

Confcal Special characters are not supported in z/OS

Control Resources Resource Name

CONTROL-M

Days Calendar (Month Days Calendar)

Description

Do AutoEdit Name

Do AutoEdit Value


Do Condition Name

Do ForceJob Job Name

Do ForceJob Special characters are not supported in z/OS

SCD Table

Do Mail Special characters are not supported in z/OS

cc

Do Mail Message


Subject


To

Do Shout Destination

Do Shout MSG

Do SYSOUT Prm

Do SYSOUT From Class

Doc File (formerly called Doc Mem) Special characters are not supported in z/OS

Doc Path (formerly called Doc Lib)Special characters are not supported in z/OS

File Name

From Class

Group

In Condition Name

Job Name

Mem LibSpecial characters are not supported in z/OS

Mem NameSpecial characters are not supported in z/OS

Node Group

Node ID

On Code

On Statement

On Statement On Codes

On Statement Proc Step

On Statement Program Step

Out Condition Name

Over LibSpecial characters are not supported in z/OS

Owner




Password

Path

Periodic Calendar Values Special characters are only supported by z/OS

Quantitative Resources Name

Scheduling Table Special characters are not supported in z/OS

Name

Scheduling Tag Special characters are not supported in z/OS

Name

Shout Message

Shout To (Destination)

Step Range Name

SYSOUT From Class

SYSOUT Parameter

User Daily

User Name

Week Days Calendar

Table 14 Exception alert fields that support western European special characters

Field name

Message

Note

Key1

Key2

Key3

Key4

Key5





C h a p t e r BB English configuration on Japanese-enabled systems

This chapter describes configuration procedures for running CONTROL-M/EM, CONTROL-M/Desktop, CONTROL-M/Server, CONTROL-M/Agent, and BMC Batch Impact Manager in English on Japanese-enabled operating systems.

These configuration procedures are necessary if you plan to use only standard English characters in CONTROL-M components installed on Japanese-enabled operating systems, and do not want Japanese characters to be accepted, for example, in any free text fields or parameters.

Configuration procedure task flow Table 15 lists:

■ tasks for configuring language support■ computers on which the tasks are performed■ links to the instructions for performing the tasks

These tasks can be performed in any order.

Table 15 Configuration tasks for English language support on Japanese systems


“Configuration tasks for English support on Japanese UNIX”

■ CONTROL-M/EM■ CONTROL-M/Server■ CONTROL-M/Agent■ BMC Batch Impact Manager

Configuration tasks for English support on Japanese UNIX



Perform this task to enable CONTROL-M components to run in an English-only mode on UNIX operating systems that support Japanese.

This task must be performed after installation or upgrade on every UNIX computer running CONTROL-M components including:

■ CONTROL-M/EM ■ CONTROL-M/Desktop■ The Reporting facility■ CONTROL-M/Server ■ CONTROL-M/Agent■ BMC Batch Impact Manager■ CONTROL-M Control Modules

To configure the environment on UNIX

1 For all CONTROL-M components to communicate properly with each other, you must set the Locale for all product components.

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


B Check that C, c, POSIX, or an English locale (according to Table 16) is displayed. If none of these locales is displayed, ask your UNIX administrator to install it.

“Configuration tasks for English support on Japanese Microsoft Windows”

■ CONTROL-M/EM■ CONTROL-M/Desktop■ CONTROL-M/Server■ CONTROL-M/Agent■ BMC Batch Impact Manager

WARNING

Discrepancies between locale settings, especially those involving different character sets, can corrupt data while data is passed from one component to another.

Table 15 Configuration tasks for English language support on Japanese systems




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

.


Table 16 ISO English character set locale settings for UNIX and Linux (for Japanese operating systems)

LanguageAIX, Solaris, Compaq (OSF) HP-UX, Linux (Red Hat) Linux (SuSE)

English (USA) en_US.ISO8859-1 en_US.iso88591 en_US

English (British) en_GB.ISO8859-1 en_GB.iso88591 en_GB

NOTE

Add the lines in the same order as the environment variables are listed in Table 17.

Table 17 UNIX environment variables for English on Japanese systems in .cshrc

Environment variable Description / value

LC_ALL This environment variable should be ““ (an empty string). Set this variable by adding the following line to the .cshrc file:setenv LC_ALL ““

LC_CTYPE LANGLC_COLLATELC_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 Table 16 on page 49.

Set these variables by adding the following lines to the .cshrc file:setenv LC_CTYPE Csetenv LANG Csetenv LC_COLLATE Csetenv LC_MESSAGES C

Configuration tasks for English support on Japanese Microsoft Windows


Configuration tasks for English support on Japanese Microsoft Windows

Perform this task to enable CONTROL-M components to run in an English-only mode on Microsoft Windows operating systems that support Japanese.

Before You Begin

This task must be performed before installing the following products on Microsoft Windows computers:

■ CONTROL-M/EM■ CONTROL-M/Desktop■ The Reporting facility■ CONTROL-M/Server■ CONTROL-M/Agent■ CONTROL-M Control Modules■ BMC Batch Impact Manager

To configure the environment on Microsoft Windows

1 Set the system locale and language settings to English before installing any of the components listed above.

A Select Western Europe and United States in Control Panel => Regional Options => Language Settings for the system to receive all messages in English.

B Select English (USA) in Control Panel => Regional Options => Your locale (location) to set the locale to English.

2 After installation you can reconfigure your computer for work with a non-English language.


A p p e n d i x CC CJK support for product objects

This appendix categorizes product objects according to their level of support for East Asian (CJK) characters. The following object types are discussed:

■ files■ parameters■ command line utilities

CJK support for product filesTable 18 summarizes the level of CJK support for the various types of product files:

Table 18 CJK support level for 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)

SYSOUT (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

%%LIBMEMSYS AutoEdit variable

CJK supported CJK (UTF-8)

xml files English only CJK (UTF-8)

command line argumentsa N/A on UNIX: CJK (UTF-8)on Windows: CJK encodings

File watcher rule file English only on UNIX: CJK (UTF-8)on Windows: CJK encodings

CJK support for parameters


CJK support for parameters■ Table 19 lists parameters that support East Asian characters.■ Table 20 on page 53 lists parameters that accept English characters only.

aSee “CJK support for command line utilities” on page 54 for a list of command line utilities that support CJK.

Table 19 Parameters that accept East Asian characters (Part 1 of 2)


Auto Edit (Set Var) Name

Auto Edit (Set Var) Value

Command

Condition Name

Confcala

Control Resources Resource Name

Description

Do AutoEdit Name

Do AutoEdit Value

Do Condition Name

Do ForceJob Job Name

Do ForceJoba SCD Table

Do Maila cc

Do Mail Message

Do Maila Subject

Do Maila To

Do Shout Destination

Do Shout MSG

Do SYSOUT Prm

Do SYSOUT From Class

Doc Filea (formerly called Doc Mem)

Doc Patha (formerly called Doc Lib)

File Name

From Class

Group

In Condition Name

Job Name

Mem Liba

CJK support for parameters


Mem Namea

On Code

On Statement

On Statement On Codes

On Statement Proc Step

On Statement Program Step

Out Condition Name

Over Liba

Path

Quantitative Resources Name

Scheduling Tablea Name

Shout Message

Shout To (Destination)

Step Range Name

SYSOUT From Class

SYSOUT Parameter

User Daily

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

Table 20 Parameters that accept English characters only


Component Names

CONTROL-M/Server Name

Host Names

Node Group

Node ID

Owner

Password

Periodic Calendar Values

Scheduling Tag Name

User Name

Table 21 Exception alert fields that support East Asian special characters

Field name

Message

Note

Table 19 Parameters that accept East Asian characters (Part 2 of 2)


CJK support for command line utilities


CJK support for command line utilitiesTable 22 lists the command line utilities that support CJK characters. These utilities accept parameters in UTF-8 on UNIX and native encoding on Windows.

Key1

Key2

Key3

Key4

Key5

Table 22 Command line utilities that support CJK characters

Product/component Command line utilities

CONTROL-M ■ ctmdbbck■ ctmdbcheck■ ctm_backup_bcp■ ctm_restore_bcp■ ctmfw■ ctmjsa■ ctmorder■ ctmreindex■ ctmsys■ ctmudly■ ctmvar■ ctmdefine■ ctmcontb■ ctmcreate

CONTROL-M/Agent ■ ctmorder■ ctmudly■ ctmvar■ ctmdefine■ ctmcontb■ ctmcreate

Table 21 Exception alert fields that support East Asian special characters

Field name



EM servers The following functions 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 table■ Import a specified definition table

EM clients The following XML utilities:■ defjob■ exportdefjob■ updatedef

Table 22 Command line utilities that support CJK characters

Product/component Command line utilities



A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Index

Symbols.cshrc file

English support on Japanese UNIX 49general configuration 17post-installation configuration 39

Numerics1252 (ANSI-Latin 1) code page

Microsoft Windows default 15Microsoft Windows XP and 2003 14MSSQL for CONTROL-M/EM 27–28MSSQL for CONTROL-M/Server 29

932 (ANSI/OEM-Japanese Shift JIS) code page 37936 (ANSI/OEM-Simplified Chinese GBK) code page 37949 (ANSI/OEM-Korean) code page 37950 (ANSI/OEM-Traditional Chinese Big5) code page 37

AANSI/OEM code page 37ANSI-Latin 1 (1252) code page


BBMC Software, contacting 2

Ccase sensitivity

CONTROL-M/EM Language parameter 19MSSQL database servers 11

character set conversionin Oracle output 21Microsoft Windows XP and 2003 37MSSQL clients 31

Chinese configurationCONTROL-M/Agent 40–41database servers 38

environment variables 39Microsoft Windows 36migration considerations 34overview 33–34product object support 51–55task flow 35UNIX and Linux 37, 39upgrade considerations 34

CJK. See East Asian (CJK) language configurationcode page, ANSI/OEM 37code page, ANSI-Latin 1 (1252)


code page, EBCDIC 20compatibility issues

East Asian (CJK) languages 34Western European languages 10

CONTROL-M/Agent configurationEast Asian (CJK) languages 36–38, 39–41English support on Japanese systems 48–50Western European languages 13–19

CONTROL-M/EM configurationcompatibility with prior versions 10, 34East Asian (CJK) languages 36–38, 39English support on Japanese systems 48–50Western European languages 13–20

CONTROL-M/Server configurationcompatibility with prior versions 10East Asian (CJK) languages 36–38, 39English support on Japanese systems 48–50Western European languages 13–19

customer support 3

Ddatabase configuration

East Asian (CJK) languages 34, 38Western European languages 20–31See also MSSQL configuration, Oracle configuration,

Sybase configuration

Index 57


EEast Asian (CJK) language configuration

CONTROL-M/Agent 40–41database servers 38environment variables 39Microsoft Windows 36migration considerations 34overview 33–34product object support 51–55task flow 35UNIX and Linux 37, 39upgrade considerations 34

EBCDIC code page 20English configuration

CONTROL-M/EM 19–20database servers and clients 20–31environment variables 18Microsoft Windows 13–16migration considerations 11MSSQL for clients 30–31MSSQL for CONTROL-M/EM 27–29MSSQL for CONTROL-M/Server 29–30on Japanese-enabled systems 47–50Oracle databases 21–23overview 9–??special character support 43–45Sybase databases 23–26task flow 11–??UNIX and Linux 16–19upgrade considerations 11

environment variablesEast Asian (CJK) languages 39English support on Japanese systems 49path 16Western European languages 18

FFrench configuration

CONTROL-M/EM 19–20database servers and clients 20–31environment variables 18Microsoft Windows 13–16migration considerations 11MSSQL for clients 30–31MSSQL for CONTROL-M/EM 27–29MSSQL for CONTROL-M/Server 29–30Oracle databases 21–23overview 9–??special character support 43–45Sybase databases 23–26task flow 11–??UNIX and Linux 16–19upgrade considerations 11


GGerman configuration


IISO-1 character set

in Oracle output 21locale settings, English on Japanese systems 49locale settings, Western European 17MSSQL configuration 28Oracle configuration 23Sybase configuration 25

JJapanese configuration

CONTROL-M/Agent 40–41database servers 38environment variables 39Microsoft Windows 36migration considerations 34overview 33–34product object support 51–55task flow 35UNIX and Linux 37, 39upgrade considerations 34

Japanese-enabled systems, English support forenvironment variables 49Microsoft Windows 50task flow 47UNIX 48–49

KKorean configuration

CONTROL-M/Agent 40–41database servers 38environment variables 39


Microsoft Windows 36migration considerations 34overview 33–34product object support 51–55task flow 35UNIX and Linux 37, 39upgrade considerations 34

LLANG environment variable

East Asian (CJK) languages 39English support on Japanese systems 49Western European languages 18

Latin-1 character setin Oracle output 21locale settings, Western European 17See also Western European language configuration

LC_ALL environment variableEast Asian (CJK) languages 39English support on Japanese systems 49Western European languages 18

LC_COLLATE environment variableEast Asian (CJK) languages 39English support on Japanese systems 49Western European languages 18

LC_CTYPE environment variableEast Asian (CJK) languages 39English support on Japanese systems 49Western European languages 18

LC_MESSAGES environment variableEast Asian (CJK) languages 39English support on Japanese systems 49Western European languages 18

Linux configurationEast Asian (CJK) languages 37, 39locale settings 38Western European languages 16–19

locale settings, UNIX and LinuxEast Asian (CJK) languages 38, 40English support on Japanese systems 49Western European languages 17

MMicrosoft Windows configuration

East Asian (CJK) languages 36English support on Japanese systems 50registry update 15Western European languages 13–16

migration considerationsEast Asian (CJK) languages 34Western European languages 11

MSSQL configurationEast Asian (CJK) languages 38

ISO-1 character set 28Western European languages 11, 27–31

OOracle configuration

East Asian (CJK) languages 38ISO-1 character set 21, 23Western European languages 21–23

Ppath environment variable 16product objects, CJK support 51–55product support 3

Rregistry, Microsoft Windows 15

SSpanish configuration


support, customer 3Sybase configuration

East Asian (CJK) languages 34, 38ISO-1 character set 25UTF-8 character set 34Western European languages 11, 23–26

Ttechnical support 3

UUNIX configuration

Index 59


East Asian (CJK) languages 37, 39English support on Japanese systems 48–49locale settings 38Western European languages 16–19

upgrade considerationsEast Asian (CJK) languages 34Western European languages 11

UTF-8 character setlocale settings for UNIX and Linux 38, 40

Vvariables, environment

East Asian (CJK) languages 39English support on Japanese systems 49path 16Western European languages 18

WWestern European language configuration



Notes

*63780**63780**63780**63780*

*63780*

Documents

CONTROL-M Language Customization Guide - … L… · CONTROL-M Language Customization Guide Supporting CONTROL-M/Enterprise Manager version 6.3.01 ... to the GUI Server the first