B Globalization Support

This appendix documents the Globalization Support for the Access Manager. The following topics are included:

Access Manager Globalization Support
Oracle Character Set Names
Oracle NLS_LANG Specifications

Access Manager Globalization Support

The Access Manager is designed to support a multitude of single-byte character sets. Source files containing SQL packages can be written in any of the coded character set identifiers (CCSID) that are listed in Table B-1. The Access Manager does not support double-byte character sets as the underlying IBM ARD interface does not support those character sets.

Oracle Character Set Names

In the table are the Oracle character set names that can be included as the third part of an Oracle Globalization Support language specification. The Oracle language specification can be explicitly set for an invocation of the Access Manager by having access to a data area named NLS_LANG.

Table B-1 Oracle Character Set Names

CCSID	Oracle Character Set Name
37	`WE8EBCDIC37`
273	`D8EBCDIC273`
277	`DKEBCDIC277`
278	`S8EBCDIC278`
280	`I8EBCDIC280`
284	`WE8EBCDIC284`
285	`WE8EBCDIC285`
297	`F8EBCDIC297`
500	`WE8EBCDIC500`
838	`TH8TISEBCDIC`
870	`EE8EBCDIC870`
875	`EL8EBCDIC875`
1140	`WE8EBCDIC1140`
1141	`D8EBCDIC1141`
1142	`DK8EBCDIC1142`
1143	`S8EBCDIC1143`
1144	`I8EBCDIC1144`
1145	`WE8EBCDIC1145`
1146	`WE8EBCDIC1146`
1147	`F8EBCDIC1147`
1148	`WE8EBCDIC1148`

The NLS_LANG data area that is shipped with the Access Manager defaults to AMERICAN_AMERICA.WE8EBCDIC37. All data emanating from a SQL package is data to be transmitted from the AS/400 to the Oracle Database. This data is translated from the character set that is associated with the CCSID of the package to the character set that is denoted explicitly by NLS_LANG or by the default for NLS_LANG. Data that is returned from the Oracle server to the AS/400 is translated by the IBM Application Requester Driver API.

Oracle NLS_LANG Specifications

An Oracle NLS_LANG specification includes three parts:

a language
a territory
a character set

For example:

language_territory.character set
AMERICAN_AMERICA.D8EBCDIC1141

For the Access Manager, the language is AMERICAN, and the territory is AMERICA. The error messages are currently in American English only. The third part is the Oracle character set name from Table B-1. The NLS_LANG values in Table B-2 are currently supported:

Table B-2 Oracle NLS_LANG Values

Language	Setting for language_territory.charset
Austrian/German	`AMERICAN_AMERICA.D8EBCDIC273` and `AMERICAN_AMERICA.D8EBCDIC1141`
Danish/Norwegian	`AMERICAN_AMERICA.DK8EBCDIC277` and `AMERICAN_AMERICA.DK8EBCDIC1142`
Eastern European	`AMERICAN_AMERICA.EE8EBCDIC870`
Finnish/Swedish	`AMERICAN_AMERICA.S8EBCDIC278` and `AMERICAN_AMERICA S8EBCDIC1143`
French	`AMERICAN_AMERICA.F8EBCDIC297` and `AMERICAN_AMERICA F8EBCDIC1147`
Greek	`AMERICAN_AMERICA.EL8EBCDIC875`
Italian	`AMERICAN_AMERICA.I8EBCDIC280` and `AMERICAN_AMERICA I8EBCDIC1144`
Thai	`AMERICAN_AMERICA.TH8TISEBCDIC`
Western European	`AMERICAN_AMERICA.WE8EBCDIC37` and `AMERICAN_AMERICA WE8EBCDIC1140`
Western European	`AMERICAN_AMERICA.WE8EBCDIC500` and `AMERICAN_AMERICA WE8EBCDIC1148`

Each user can have its own NLS_LANG data area. To change the NLS_LANG data area, change the Access Manager Globalization Support language parameter by using the CHGSQLDFLT command as described in Chapter 6, "Configuring Access Manager".