You can change the NLS environment using the Web-based System Manager Users application or the Manage Language Environment SMIT interface to:
In addition, you can use the setmaps command to set the code set map of a terminal.
The setting of the LANG environment variable (the "LANG = <name>" string in the /etc/environment file) designates the default locale, which is a language-territory-code-set combination. The default locale provides formats for default collation, character classification, case conversion, numeric and monetary formatting, date-and-time formatting, and affirmative or negative responses. The default locale includes reference to the code set.
If more than one code set is supported for a given language-territory combination, multiple low-function terminal (LFT) keyboard mappings exist. The selected keyboard mapping has to match the code set of the selected language environment.
Users can perform such tasks as selecting the active font and selecting the font to load for the next system restart. The selected font has to support the same code set as the selected language environment and LFT keyboard mapping.
Message catalogs are shipped in one code set for each translated language-territory combination. The code set of the message catalog has to match the code set of the locale.
User-defined flat files of one code set can be converted to another code set when appropriate (IBM-850 to ISO8859-1, for example).
There are several NLS-related scenarios some users may encounter on the system. This section lists common scenarios with suggested actions to be taken.
The user may be satisfied with the default code set for language-territory combinations even where more than one code set is supported. The user may keep the default code set if the current user environment uses that code set, or if the user is new and has no code set preference.
The language-territory selected at system installation time will be defaulted to the appropriate locale based on the default code set. The default keyboard mappings, default font, and message catalogs are all established around the default code set. This scenario requires no special action from the user.
Flat text files that require conversion to the preferred code set may be converted through the Web-based System Manager Users application, the Manage the Language Environment SMIT menu, or the iconv utility. User-defined structured files require conversion through user-written conversion tools that use the iconv library functions to convert the desired text fields within the structured files.
If a special locale is desired (that is, a locale different from any of those provided), take the following steps with a user ID that allows read or write permissions (for example, root):
cd /usr/lib/nls/loc cp en_GB.ISO8859-1.src gwm.src
vi gwm.src change d_fmt "%d%m%y" to d_fmt "%m-%d-%y"
localedef -f ISO8859-1 -i gwm.src gwm
LOCPATH=/usr/lib/nls/loc; export LOCPATH
Note: All setuid and setgid programs ignore the LOCPATH environment variable.