Note: See the
System API Reference,
SC41-4801 book for more details on the
open() API and the O_TEXTDATA and O_CODEPAGE options.
QPWFSERVER Authorization List
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.
Mounting and QSYS.LIB
Users can mount the QSYS.LIB file system on a client, but users cannot mount
over the QSYS.LIB file system. Users should export and mount a sub-library from
QSYS.LIB rather than mounting QSYS.LIB directly on the client. The reason for this
is that QSYS.LIB contains hundreds of objects. Trying to display or process all of
the objects can affect client performance.
Support for User Spaces
NFS supports the exporting and mounting of user spaces, with the following
exceptions:
vUser spaces cannot be over 16 megabytes
vUser spaces are not CCSID-tagged or tagged for a code page by default. If a
CCSID is asked for, NFS will translate the data if the user specifies the CCSID.
vUser space files (*USRSPC object type) can be appended to using NFS, but this
may produce unpredictable results with how data is written.
File Modes of Database Members
The file mode of any database members needs to be the same as the file mode of
the parent file. No matter what users specify, NFS will always create new database
members with the file mode of the parent. If users specify other file modes than that
of the parent, they will not receive an error return code. NFS will create the new
member with the file mode of the parent no matter what the user specifies.
Path Names of .FILE Objects
Users need to be aware of the maximum database record length when editing
database members. Users specify the record length when creating a physical file.
The default record length for all .FILE objects created in QSYS.LIB is 92 bytes if
created with one of the following methods:
1. mkdir() API
2. MKDIR (Make Directory) command
3. MD (Make Directory) command
4. CRTDIR (Create Directory) command
Source physical files contain a date stamp (6 bytes) and sequence number (6
bytes), using 12 total bytes of data. This is accounted for by subtracting 12 bytes
58 OS/400 Network File System Support V4R4
|
|
|
|
|
|
|