The client code set
When the processor creates a file whose file name has non-ASCII characters, the client locale must support these non-ASCII characters.
Before you start the HCL® OneDB® database server, you must ensure that the code set of the client locale (the client code set) contains these characters.
When you use a nondefault locale, you must set the CLIENT_LOCALE environment variable to the name of a locale whose code set contains these non-ASCII characters.
For example, suppose you want to process the source file with the path
/A1A2B1B2/C1C2D1D2, where
A1A2, B1B2,
C1C2, and D1D2 are multibyte characters in the Japanese SJIS code
set. You must perform the following steps to enable the esql command to create
the intermediate C source file on the client computer:- Set the CLIENT_LOCALE environment variable on the client computer to the Japanese SJIS locale, ja_jp.sjis.
- Process the source file with the esql command.
If the code sets that are associated with the file name
and with the client locale do not match, a valid file name might contain
invalid characters with respect to the client locale. The processor
rejects any file name that contains invalid characters and the following
error message is displayed:
Illegal characters in filename.