Integrated File System Introduction

 

Use QDLS through the integrated file system interface

The QDLS file system can be accessed through the integrated file system interface using either the OS/400 file server or the integrated file system commands, user displays, and C language APIs. In using the integrated file system interfaces, be aware of the following considerations and limitations.

Integrated file system and HFS in the QDLS file system

Operations can be performed on objects in the QDLS file system not only through the Document Library Objects (DLO) CL commands but also through either the integrated file system interface or APIs provided by a hierarchical file system known as HFS. Whereas the integrated file system is based on the integrated language environment (ILE) program model, HFS is based on the original iSeries server program model.

The HFS APIs allow you to perform a few additional operations that the integrated file system does not support. In particular, you can use HFS APIs to access and change directory extended attributes (also called directory entry attributes). Be aware that the naming rules for using HFS APIs are different from the naming rules for APIs using the integrated file system interface.

For more information about HFS, see the Hierarchical File System APIs topic in the iSeries Information Center.

User enrollment in the QDLS file system

You must be enrolled in the system distribution directory when working with objects in QDLS.

Case-sensitivity in the QDLS file system

QDLS converts the lowercase English alphabetic characters a to z to uppercase when used in object names. Therefore, a search for object names using only those characters is not case-sensitive.

All other characters are case-sensitive in QDLS.

For more details, see the Folder and Document Name topic in the iSeries Information Center.

Path names in the QDLS file system

• Each component of the path name can consist of just a name, such as:

       /QDLS/FLR1/DOC1
  

  or a name plus an extension (similar to a DOS file extension), such as:

       /QDLS/FLR1/DOC1.TXT
  

• The name in each component can be up to 8 characters long, and the extension (if any) can be up to 3 characters long. The maximum length of the path name is 82 characters, assuming an absolute path name that begins with /QDLS.
• The directory hierarchy within QDLS can be 32 levels deep. If / and QDLS are included as the first two levels, the directory hierarchy can be 34 levels deep.
• The characters in names are converted to the code page of the job when the names are stored unless data area Q0DEC500 has been created in the QUSRSYS library. If this data area exists, then the characters in names are converted to code page 500 when the names are stored. This function provides compatibility with the behavior of the QDLS file system in previous releases. A name may be rejected if it cannot be converted to the appropriate code page.

  For more information about code pages, see the Globalization topic in the iSeries Information Center.

Links in the QDLS file system

Symbolic links cannot be created or stored in the QDLS file system.

The integrated file system handles the relationship between a folder and document library objects in a folder as the equivalent of one link between the folder and each object in the folder. Thus, it is possible to link to an object in the QDLS file system from a file system that supports symbolic links.

See Link for a description of links.

Use integrated file system commands and displays in the QDLS file system

The commands listed in Perform operations using CL commands can operate on the QDLS file system, except for the following:

• The ADDLNK command can be used only to link to an object in QDLS from another file system that supports symbolic links.
• The CHKIN and CHKOUT commands are supported for files, but not for directories.
• The APYJRNCHG, ENDJRN, SNDJRNE, and STRJRN commands are not supported.

The same restrictions apply to the user displays described in Perform operations using iSeries menus and displays.

Use integrated file system APIs in the QDLS file system

The C language functions listed in Perform operations using APIs can operate on the QDLS file system, except for the following:

• The symlink() function can be used only to link to an object in QDLS from another file system that supports symbolic links.
• The following functions are not supported:

  givedescriptor()

  ioctl()

  link()

  QjoEndJournal()

  QjoRetrieveJournalInformation()

  QJORJIDI()

  QJOSJRNE()

  QjoStartJournal()

  Qp0lGetPathFromFileID()

  readlink()

  takedescriptor()

---

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