Integrated File System Introduction
Use QSYS.LIB through the integrated file system interface
The QSYS.LIB 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.
QPWFSERVER authorization list in the QSYS.LIB file system
The QPWFSERVER is an authorization list (object type *AUTL) that provides additional access requirements for all objects in the QSYS.LIB file system being accessed through remote clients. The authorities specified in this authorization list apply to all objects within the QSYS.LIB file system.
The default authority to this object is PUBLIC *USE authority. The administrator can use the EDTAUTL (Edit Authorization List) or WRKAUTL (Work With Authorization List) commands to change the value of this authority. The administrator can assign PUBLIC *EXCLUDE authority to the authorization list so that the general public cannot access QSYS.LIB objects from remote clients.
File handling restrictions in the QSYS.LIB file system
- Logical files are not supported.
- Physical files supported for text mode access are program-described physical files containing a single field and source physical files containing a single text field. Physical files supported for binary mode access include externally-described physical files in addition to those files supported for text mode access.
- Byte-range locking is not supported. (For more information about byte-range locking, see the fcntl() topic in the iSeries Information Center.)
- If any job has a database file member open, only one job is given write access to that file member at any time. Other requests are allowed only read access.
Support for user spaces in the QSYS.LIB file system
QSYS.LIB supports stream input/output operations to user space objects. For example, a program can write stream data to a user space and read data from a user space. The maximum size of a user space is 16 776 704 bytes.
Be aware that user spaces are not tagged with a CCSID (coded character set identifier). Therefore, the CCSID returned is the default CCSID of the job.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]