Remove locale and code-set-conversion files
To save disk space, you might want to keep only those files that you intend to use.
These topics describe which of these files you can safely
remove from your HCL OneDB™ installation.
You can safely remove the following GLS files from your HCL OneDB installation:
- For those locales that you do not intend to use, you can remove
locale source and object files (.lc and .lco)
from the subdirectories of the lcX subdirectory
in your HCL OneDB installation.
For more information about the lcX path name, see Locale-file subdirectories.
- For those code-set conversions that you do not intend to use,
you can remove code-set-conversion source and object files (.cv and .cvo)
from the subdirectories of the cvY subdirectory
in your HCL OneDB installation.
For more information about the cvY path name, see Code-set-conversion file names.
Restriction: Do not remove the locale object file
for the U.S. 8859-1 English locale, 0333.lco in
the en_us locale-file subdirectory. In addition, do not remove
the Code-Set Name-Mapping file, registry. HCL OneDB products use these
files for the language processing of all locales.
Because HCL OneDB products do not access source versions of locale and code-set conversion files, you can safely remove them. These files, however, provide useful online documentation for the supported locales and code-set conversions. If you have enough disk space, it is recommended that you keep these source files for the GLS locales (*.lc) and code-set conversions (*.cv) that your HCL OneDB installation supports.