ALLBASE/SQL lets you manipulate databases in a wide variety of
native languages in addition to the default language, known as
n-computer.
You can use either 8-bit or 16-bit character data, as
appropriate for the language you select. In addition, you can
always include ASCII data in any database, since ASCII is a
subset of each supported character set. The collating sequence
for sorting and comparisons is that of the native language
selected. A list of supported languages is in /usr/lib/nls/config.
You can use native language characters in a wide variety of
places, including:
Host variables for CHAR or VARCHAR data (but not variable names).
ALLBASE/SQL object names.
WHERE and VALUES clauses.
If your system has the proper message files installed,
ALLBASE/SQL displays prompts, messages and banners in the
language you select, and it displays dates and time according to
local customs. In addition, ISQL accepts responses to its
prompts in the native language selected. However, regardless of
the native language used, the syntax of ISQL and SQL
commands—including punctuation—remains in ASCII.
In order to use a native language other than the default, you
must do the following:
Make sure your I/O devices support the character set you wish
to use.
Set the HP-UX environment variable to the native language
(LanguageName) you wish to use. For the C shell, use the following command:
For the K shell, use the following command (no spaces before
or after the equals sign):
typeset -x LANG=LanguageName
|
For the Bourne shell, use the following commands:
LANG = LanguageName
export LANG
|
This language then becomes the current language. (If
LANG is not set, the current langauge is n-computer.)
Use LANG = LanguageName option syntax in the START DBE NEW
command to specify the language when you create a DBEnvironment.
If you are using a language with 16 bit character data to
name database objects referenced in your program, enable NLS
for the FORTRAN compiler by using either the $NLS_SOURCE ON
compiler directive or the -Y command line option.
You can use native language characters in the DBEnvironment
name. If you do so, you must set the LANG environment variable
to the same language before you can connect to the
DBEnvironment. To avoid confusion, it is advised that you
always use the same language for the DBEnvironment that you
use in the LANG variable.
Resetting the LANG variable while you are connected to a
DBEnvironment has no effect on the current DBE session.
