Release 9.2.0.1.0 for IBM AS/400
Part Number A97615-01
 Contents |
 Index |
| Oracle Transparent Gateway for DB2/400 Installation and User's Guide Release 9.2.0.1.0 for IBM AS/400 Part Number A97615-01 |
|
This appendix documents the National Language Support (NLS) information for the Oracle Transparent Gateway for DB2/400. For more information about using NLS refer to Oracle9i Application Developer's Guide - Fundamentals.
This appendix contains the following sections:
NLS is a technology enabling 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.
There are a number of different settings in the gateway, DB2/400, Oracle server, and the client that affect NLS processing. In order for translations to take place correctly, character settings of these components must be compatible. Each character in one encoding scheme must have a matching character in another encoding scheme.
Once the gateway is installed, you must use the CHGORATUN command if you need to change language settings.
The CHGORATUN command allows you to change the language parameter that defines the character set used for the gateway. The language parameter entered with this command specifies the conventions such as language used for gateway messages, names of days and months, symbols for AD, BC, AM, and PM, and the default language sorting mechanism.
The syntax for specifying the language parameter is:
language[_territory.character_set]
|
|
is any valid language documented in "Supported Languages and Territories" . |
|
|
is optional and defaults to AMERICA. Valid values are documented in "Supported Languages and Territories". |
|
|
is optional and defaults to WE8EBCDIC37. Valid values are documented in "Supported Character Sets". |
The default setting is:
AMERICAN_AMERICA.WE8EBCDIC37
To change this setting, use the Gateway language field on the CHGORATUN main menu panel. The gateway must be shutdown and restarted before the new parameter takes effect. For more information about the CHGORATUN command, refer to "CHGORATUN, Change Initialization Parameters".
If the coded character set identifier (CCSID) of the AS/400 data file is different from 65535, then the Oracle language parameters must match the CCSID of the AS/400 data file that is being accessed. For example, if the CCSID is 280 for Italy, then the Oracle character set must be set to I8EBCDIC280. The exception to this is for columns with a CCSID of 13488 (UCS-2). the data in these columns will always be converted to the character set that is determined by NLS_LANG. Contact your DBA or refer to the IBM manual for AS/400 National Language Support for additional information about AS/400 CCSID codes.
Oracle Transparent Gateway for DB2/400 supports the following languages and values for character_set.
Note that the character sets marked with an asterisk (*) are the Euro versions of the immediately preceding character set.
Oracle Transparent Gateway for DB2/400 supports these language and territory combinations:
There are a number of NLS parameters that control NLS processing between the Oracle server and the client. You can set language-dependent behavior defaults for the server and set language-dependent behavior for the client that overrides these defaults. For a complete description of NLS parameters, refer to the NLS chapter in the Oracle9i SQL Reference. These parameters do not affect gateway processing. However, you must ensure the character set is compatible with the character set you specify on the gateway and DB2/400. In other words, each character in one encoding scheme must have a matching character in another encoding scheme.
When you create your database, the character set used to store data is specified by the CHARACTER SET parameter. Once the database is created, the database character set cannot be changed unless you recreate the database.
Normally US7ASCII is the default for CHARACTER SET on non-EBCDIC platforms. US7ASCII only supports 26 Latin alphabetic characters. If you have specified 8-bit character sets on the gateway and DB2/400, you must have a compatible 8-bit character set defined for your database. To check the character set of an existing database, issue this command in SQL*Plus:
SELECT userenv('language') FROM DUAL
Availability of the supported language message modules depends on which modules are installed in the Oracle product set that is running on the server. If you do not have message modules installed for a particular language set, then specifying that language with a language parameter results in no messages being displayed for that module in the requested language. Only a generalized (and rather uninformative) message will be provided.
When converting DB2/400 datatypes to Oracle datatypes, if support for DB2/400 GRAPHIC datatypes (GRAPHIC, VARGRAPHIC, or LONG VARGRAPHIC) is required, special consideration must be given to the selection of the NLS_LANG character set. Refer to "DB2/400 GRAPHIC Support" for more information.
|
 Copyright © 2002 Oracle Corporation. All Rights Reserved. |
|
