The GLS feature

In a database application, some of the tasks that the database server and the client application perform depend on the language and culture conventions of the data that they handle.

For example, the database server must sort U.S. English data differently from Chinese character data. The client application must show Canadian currency differently from Thai currency.

If the HCL OneDB™ database server or client product included the code to perform these data-dependent tasks, each would need to be written specially to handle a different set of culture-specific data.

With support for GLS, HCL OneDB products no longer need to specify how to process culture-specific information directly. Culture-specific information is in a GLS locale. When the HCL OneDB product needs culture-specific information, it calls the GLS library, which accesses the GLS locale and returns the information to the HCL OneDB product.

The GLS feature is a portable way to support culture-specific information. Although many operating systems provide support for non-English data, this support is usually in a form that is specific to the operating system. Not many standards yet exist for the format of culture-specific information. This lack of conformity means that if you move an application from one operating-system environment to another, you might need to change the way in which the application requests language support from the operating system. You might even find that the new operating-system environment does not provide the same aspect of language support that the initial environment provided.

The GLS feature can access culture-specific information about a UNIX™ or Windows™ operating system. HCL OneDB products can locate the locale information about any platform to which they are ported.

In order for GLS to support a nondefault locale, the version of Windows that you are using must also support that locale. That is, you cannot support a Chinese client application on Windows unless that application is running on the Chinese version of Windows.

To use the GLS feature, the tasks that you must perform depend on whether you are a system administrator, database administrator, user of a client application, user of a database server utility, or client application developer. The following table lists these optional and mandatory tasks.

Audience Optional tasks Mandatory tasks
System administrator, database administrator, or user of client application
  • For non-default locales, set the DB_LOCALE, CLIENT_LOCALE, and SERVER_LOCALE environment variables.
  • To customize display formats, set the GL_DATE, GL_DATETIME, and DBMONEY environment variables. For , you can set DBTIME instead of GL_DATETIME.
 None
  • To configure a GLS environment for , set the CC8BITLEVEL and ESQLMF environment variables.
  • To perform additional configuration for the GLS environment, set the DBLANG and GLS8BITFSYS environment variables.
  • To issue an SQL statement, follow the guidelines in SQL features, and Database server features.
  • To remove GLS files, follow the guidelines in Remove unused files.
  • To get information about GLS files on UNIX, follow the guidelines in The glfiles utility (UNIX).
User of database server utility Same as above Follow the guidelines in Locale-specific support for utilities.
Client application developer