Integrated File System Introduction

---

Name continuity

When you use the "root" (/), QOpenSys, and user-defined file systems, you can take advantage of system support that ensures characters in object names remain the same. This also applies when you use these file systems across iSeries servers and connected devices that have different character encoding schemes (code pages). Your server stores the characters in the names in a 16-bit form that is known as UCS2 Level 1 (that is also called Unicode) for *TYPE1 directories and UTF-16 for *TYPE2 directories. Refer to *TYPE2 directories for more information about the directory formats. UCS2 Level 1 and UTF-16 are subsets of the ISO 10646 standard. When the name is used, the system converts the stored form of the characters into the proper character representation in the code page being used. The names of extended attributes associated with each object are also handled the same way.

Figure 9. Keeping characters the same across encoding schemes

This support makes it easier to interact with a server from devices using different code pages. For example, PC users can access an iSeries server file using the same file name, even though their PCs do not have the same code page as your server. The conversion from one code page to another is handled automatically by your server. Of course, the device must be using a code page that contains the characters used in the name.

---

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]