OnLine 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
Figure 5-1 Message-Log Filename with Multibyte Characters
If GLS8BITFSYS is 1 (or is not set) on the server computer, OnLine assumes that the operating system is 8-bit clean, and it generates a file that is called C1C2D1D2 in the /A1A2B1B2 directory. For more information on an 8-bit clean operating system and the GLS8BITFSYS environment variable, see page 2-23.
The Server Code Set When OnLine actually creates a file whose filename has non-ASCII characters, the server locale must support these non-ASCII characters. Before you start OnLine, 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 OnLine message log 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 OnLine to create this message-log file on the server computer:
1. Modify the MSGPATH configuration parameter in the ONCONFIG file, as the example in Figure 5-1 shows.
2. Set the SERVER_LOCALE environment variable on the server computer to the Japanese SJIS locale, ja_jp.sjis.
3. Start up OnLine with the oninit utility.
OnLine checks the validity of a filename with respect to the server-processing locale before it references a filename. When OnLine 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:
