Single-Byte and Double-Byte Considerations
Many single-byte languages support either national code pages or multinational code pages. The double-byte languages support specific individual national code pages by language.
Single-byte character sets use a collection of phonetic characters that require one byte to create a single character. Conversely, the double-byte character sets use ideographic characters and require two bytes to create a single character.
Single-byte languages can generally be run on single-byte or double-byte systems. Double-byte languages, such as Japanese, Chinese, and Korean, must run on machines configured to support a double-byte system. For example, a double-byte SQL Server or Oracle database is required for Chinese and Japanese languages.
The software can perform a Query By Example (QBE) on any character. However, when using a double-byte language, this process may not necessarily use an understandable collating sequence, although it can still use QBE for any double-byte column.
The following table shows the languages that the software supports and the LocalCodeSet
            values set in the JDE.INIjde.ini for each platform:
| Tier | Language | Language Code | LocalCodeSet Value | 
|---|---|---|---|
| 1 | English | E | US_EBCDIC | 
| 1 | French | F | US_EBCDIC | 
| 1 | German | G | US_EBCDIC | 
| 1 | Italian | I | US_EBCDIC | 
| 1 | Spanish | S | US_EBCDIC | 
| 1 | Portuguese | P | US_EBCDIC | 
| 1 | Japanese | J | JA_EBCDIC | 
| 2 | Danish | DN | US_EBCDIC | 
| 2 | Dutch | DU | US_EBCDIC | 
| 2 | Finnish | FN | US_EBCDIC | 
| 2 | Norwegian | NO | US_EBCDIC | 
| 2 | Swedish | W | US_EBCDIC | 
| 2 | Korean | KO | KO_EBCDIC | 
| 2 | Traditional Chinese | CT | TC_EBCDIC | 
| 2 | Simplified Chinese | CS | SC_EBCDIC | 
| 3 | Arabic | AR | n\a | 
| 3 | Czech | C | EE_EBCDIC | 
| 3 | Hungarian | HU | EE_EBCDIC | 
| 3 | Polish | PO | EE_EBCDIC | 
| 3 | Greek | GR | GR_EBCDIC | 
| 3 | Russian | RU | RS_EBCDIC | 
| 3 | Turkish | TR | TK_EBCDIC |