SE needs to determine the code set that the server locale supports (the server code set) to perform the following tasks that are associated with the read/write operations to its operating-system files:
1
0
The Server Code Set When SE actually creates a file whose filename has non-ASCII characters, the server locale must support these non-ASCII characters. Before you start SE, you must set the SERVER_LOCALE environment variable to the name of a locale whose code set contains these non-ASCII characters. For example, suppose you want an SE message log with the path C1C2D1D2D3, where C1C2 and D1D2D3 are multibyte characters in the Japanese SJIS code set. You must perform the following steps to enable SE to create this message-log file from within a client application:
1. Set the SERVER_LOCALE environment variable on the server computer to the Japanese SJIS locale, ja_jp.sjis.
2. Set the CLIENT_LOCALE environment variable on the client computer to the Japanese SJIS locale, ja_jp.sjis, or to a locale that supports a convertible code set. For more information, see "Performing Code-Set Conversion".
3. Start up the client application from which you execute the following SQL statement: CREATE DATABASE A1A2B1B2 WITH LOG IN 'C1C2D1D2D3'
Data Portability Use of non-ASCII characters for SE database names and table names might present compatibility problems. To achieve maximum portability for SE, Informix recommends that you not use non-ASCII database names, so that you retain the option to shift the database to an operating system that is not 8-bit clean. To disable the capability of SE to generate 8-bit filenames (even if the operating system is 8-bit clean), set the GLS8BITFSYS environment variable to 0. Performing Code-Set Conversion Once SE creates the operating-system file, it has generated a filename and written file contents in the code set of the server locale (the server code set). Any Informix product or client application that needs to access this file must have a server-processing locale that supports this same server code set. You must ensure that the appropriate locale environment variables are set so that the server-processing locale supports a code set with these non-ASCII characters. (For more information on the server-processing locale, see page 1-34.)
SE checks the validity of a filename with respect to the server-processing locale before it references a filename. When SE transfers data to and from its operating-system files, it handles any differences in the code sets of the server-processing locale and the server locale as follows:
