Skip Headers
Oracle Procedural Gateway® for APPC User's Guide
10g Release 2 (10.2) for Microsoft Windows (32-Bit)

Part Number B16212-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

E National Language Support

This appendix documents the National Language Support (NLS) information for the gateway. More information about using NLS is in the Oracle Database 10g Server Application Developer's Guide.

This appendix includes the following sections:

E.1 Overview

National Language Support is a technology that enables Oracle applications to interact with users in their native language, using their conventions for displaying data.

The Oracle NLS architecture is data-driven, enabling support for specific languages and character encoding schemes to be added without requiring any changes in source code.

E.2 Languages Supported for Messages

The Oracle Procedural Gateway for APPC is capable of issuing its messages in languages other than English.

Table E-1 shows the currently supported languages in the left column, and the right column presents each language's corresponding language, territory, and recommended character set specifications for use in the language setting. Other character sets can be used, but care must be taken to ensure that the character set used contains the full set of characters required by the specified language.

Table E-1 Languages Supported for Messages Issued by the Gateway

Language Setting for language_territory.charset

American English

AMERICAN_AMERICA.US7ASCII

Brazilian Portuguese

BRAZILIAN PORTUGUESE_BRAZIL.WE8ISO8859P1

Czech

CZECH_CZECH REPUBLIC.EE8ISO8859P2

Danish

DANISH_DENMARK.WE8ISO8859P1

Dutch

DUTCH_THE NETHERLANDS.WE8ISO8859P1

Egyptian Abrabic

ARABIC_EGYPT.AR8ISO8859P6

French

FRENCH_FRANCE.WE8ISO8859P1

German

GERMAN_GERMANY.WE8ISO8859P1

Greek

GREEK_GREECE.EL8ISO8859P7

Hungarian

HUNGARIAN_HUNGARY.EE8ISO8859P2

Israeli Hebrew

HEBREW_ISRAEL.IW8ISO8859P8

Italian

ITALIAN_ITALY.WE8ISO8859P1

Japanese

JAPANESE_JAPAN.JA16SJIS

Korean

KOREAN_KOREA.KO16KSC5601

Norwegian

NORWEGIAN_NORWAY.WE8ISO8859P1

Polish

POLISH_POLAND.EE8ISO8859P2

Portuguese

PORTUGUESE_PORTUGAL.WE8ISO8859P1

Romanian

ROMANIAN_ROMANIA.EE8ISO8859P2

Russian

RUSSIAN_CIS.CL8ISO8859P5

Simplified Chinese

SIMPLIFIED CHINESE_CHINA.ZHS16GBK

Slovak

SLOVAK_SLOVAKIA.EE8ISO8859P2

Spanish

SPANISH_SPAIN.WE8ISO8859P1

Spainish Catalan

CATALAN_SPAIN.WE8ISO8859P1

Swedish

SWEDISH_SWEDEN.WE8ISO8859P1

Thai

THAI_THAILAND.TH8TISASCII

Traditional Chinese

TRADITIONAL CHINESE_TAIWAN.ZHT16BIG5

Turkish

TURKISH_TURKEY.WE8ISO8859P9


The language used by the Oracle Procedural Gateway for APPC server is specified by the LANGUAGE parameter in the initsid.ora file for the gateway. The syntax for the LANGUAGE parameter is:

LANGUAGE=language[_territory.charset]

where language, territory, and charset are valid values from the preceding table. If no LANGUAGE parameter is specified in the initsid.ora file, the default language used is American English.

The language used by the Procedural Gateway Administration Utility, PGAU, is specified by the NLS_LANG environment variable, in the same syntax as described for the LANGUAGE parameter for the server. If the NLS_LANG environment variable is not set, then the default language used is American English.

E.3 Languages Supported for Data Conversion

The Oracle Procedural Gateway for APPC does no data conversion in the gateway itself. Instead, all conversion of data flowing between the integrating server and the gateway is performed by the Oracle Integrating Server. This is accomplished through calls within the TIP to the UTL_RAW.CONVERT function, which converts data from the local character set at the integrating server to the character set of the OLTP system.

The character set of the remote OLTP system is specified for:

This information is generated into the TIP automatically by PGAU.

Attention:

It is extremely important to ensure that the character set or codepage of the OLTP data be specified for PGAU using these parameters:
  • DEFINE TRANSACTION . . . NLS_LANGUAGE

  • DEFINE TRANSACTION . . .REMOTE_MBCS

  • REDEFINE DATA . . . REMOTE_LANGUAGE

Languages and character sets supported by the UTL_RAW.CONVERT function are the same as those supported by the Oracle Integrating Server. Refer to the platform-specific documentation for your Oracle Integrating Server for information on which languages and character sets are supported. If your integrating server is on an ASCII platform, then the platform-specific documentation might not list any of the EBCDIC character sets. This does not necessarily mean they are not supported. You should contact Oracle Support Services in this case.