Integrated File System Introduction

 

Use QOPT through the integrated file system interface

The QOPT 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 APIs. In using the integrated file system interface, be aware of the following considerations and limitations.

For more details, see the publication Optical Support .

Integrated file system and HFS in the QOPT file system

Operations can be performed on objects in the QOPT file system 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) or to work with held optical files. 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 on HFS APIs, see the hierarchical file system APIs topic in the iSeries Information Center, or in the publication Optical Support .

Case-sensitivity in the QOPT file system

Depending upon the format of the optical media, case may or may not be preserved when creating files or directories in QOPT. However, file and directory searches are case insensitive regardless of the optical media format.

Path names in the QOPT file system

• The path name must begin with a slash (/). The path is made up of the file system name, the volume name, the directory and sub-directory names, and the file name. For example:

       /QOPT/VOLUMENAME/DIRECTORYNAME/SUBDIRECTORYNAME/FILENAME
  

• The file system name, QOPT, is required.
• The volume and path name length vary by optical media format.
• You can simply specify /QOPT in the path name or include one or more directories or subdirectories in the path name. Directory and file names allow any character except X'00' through X'3F', X'FF'. Additional restrictions may apply based on the optical media format.
• The file name is the last element in the path name. The file name length is limited by the directory name length in the path.

For more details on path name rules in the QOPT file system, see the "Path Name Rules" discussion in the publication Optical Support .

Links in the QOPT file system

The QOPT file system supports only one link to an object. Symbolic links cannot be created or stored in QOPT. However, files in QOPT can be accessed by using a symbolic link from the "root" (/) or QOpenSys file system.

See Link for a description of links.

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

Most commands listed in Perform operations using CL commands can operate on the QOPT file system. There are, however, a few exceptions in the QOPT file system. Keep in mind that it may not be safe to use these CL commands in a multi-thread capable process; Certain restrictions may apply, depending on the optical media format. The same restrictions apply to the user displays described in Perform operations using iSeries menus and displays.

The following integrated file system commands are not supported by the QOPT file system:

• ADDLNK
• APYJRNCHG
• CHKIN
• CHKOUT
• ENDJRN
• SNDJRNE
• STRJRN
• WRKOBJOWN
• WRKOBJPGP

Use integrated file system APIs in the QOPT file system

All of the C language APIs listed in Perform operations using APIs can operate on the "root" (/) file system in a threadsafe manner, except for the following:

• QjoEndJournal()
• QjoRetrieveJournalInformation()
• QJORJIDI()
• QJOSJRNE()
• QjoStartJournal()

---

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