Integrated File System APIs

The integrated file system is a part of the IBM® i operating system that supports stream input/output and storage management similar to personal computer and UNIX® operating systems while providing an integrating structure over all information stored on your system.

The stream file support is designed for efficient use in client/server applications. Stream files are particularly well suited for storing long continuous strings of data such as the text of documents, images, audio, and video.

The integrated file system provides a hierarchical directory structure that supports UNIX-based open system standards, such as Portable Operating System Interface for Computer Environments (POSIX) and The Single UNIX Specification. This file and directory structure provides the users of PC operating systems with a familiar environment.

In addition to providing an interface for users and applications to access stream files, the integrated file system also provides a common interface to access database files, documents, and other objects stored on the system.

For more information, see the Integrated file system topic collection.

The integrated file system APIs are:

The integrated file system exit programs are:

In addition to the functions above, the following functions, which are described in Sockets APIs, also can operate on files in the integrated file system.

Other Functions that Operate on Files
Function Description
givedescriptor() Give file access to another job

Give socket access to another job

select() Check I/O status of multiple file descriptors

Wait for events on multiple sockets

takedescriptor() Take file access from another job

Take socket access from another job

Note: These functions use header (include) files from the library QSYSINC, which is optionally installable. Make sure QSYSINC is installed on your system before using any of the functions. See Header Files for UNIX-Type Functions) for the file and member name of each header file.

Many of the terms used in this chapter, such as current directory, file system, path name, and link, are explained in the Integrated file system topic collection. Examples: APIs and exit programs also shows an example of using several integrated file system functions.

To determine whether a particular function updates the access, change, and modification times of the object on which it performs an operation, see Integrated File System APIs--Time Stamp Updates.



[ Back to top | UNIX-Type APIs | APIs by category ]