Use <a href="http://www.setgetweb.com/p/iSeries/v5r3/rzaaxmstqnetw.htm">QNetWare</a> through the <a href="http://www.setgetweb.com/p/iSeries/v5r3/rzaaxmst03.htm">integrated file system</a> interface

Integrated File System Introduction

Use QNetWare through the integrated file system interface

The QNetWare 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. You should be aware of the following considerations, limitations, and dependencies.
Authorities and ownership in the QNetWare file system

Files and directories in QNetWare are stored and managed by Novell NetWare servers. When using commands and APIs to retrieve or set the authorities of either owners or users, QNetWare maps NetWare users to iSeries server users based on the name of a user. If the NetWare name exceeds ten characters or a corresponding iSeries server user does not exist, then the authority is not mapped. Owners that cannot be mapped are automatically mapped to the user profile QDFTOWN. The authorities of users can be displayed and changed using the WRKAUT and CHGAUT commands. When authorities are transferred to and from the server they are mapped to iSeries server authorities.
Audit in the QNetWare file system

Although Novell NetWare supports the auditing of files and directories, the QNetWare file system cannot change the auditing values of these objects. Therefore, the CHGAUD command is not supported.
Files and directories in the QNetWare file system

The QNetWare file system does not preserve the case in which files or directories are entered in a command or API. All names are set to uppercase in transmission to the NetWare server. Novell NetWare also supports the namespaces of multiple platforms, such as DOS, OS/2, Apple Macintosh, and NFS. The QNetWare file system only supports the DOS namespace. Since the DOS namespace is required on all Novell NetWare volumes, all files and directories will appear in the QNetWare file system.
NDS objects in the QNetWare file system

The QNetWare file system supports the display of NDS names in uppercase and lowercase.
Links in the QNetWare file system

The QNetWare file system supports only one link to an object. Symbolic links cannot be created or stored in QNetWare. However, symbolic links can be created in the "root" (/) or QOpenSys directories that point to a QNetWare file or directory.
Use integrated file system commands and displays in the QNetWare file system

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

ADDLINK
APYJRNCHG
CHGAUD
CHGPGP
CHKIN
CHKOUT
ENDJRN
SNDJRN
STRJRN
WRKOBJOWN
WRKOBJPGP

In addition to the previous commands, the following commands cannot be used against NDS objects, servers, or volumes:

CHGOWN
CPYFRMSTMF
CPYTOSTMF
CRTDIR

Use integrated file system APIs in the QNetWare file system

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

givedescriptor()
link()
QjoEndJournal()
QjoRetrieveJournalInformation()
QJORJIDI()
QJOSJRNE()
QjoStartJournal()
readlink()
symlink()
takedescriptor()

In addition to the previous APIs, the following APIs cannot be used against NDS objects, servers, or volumes:

chmod()
chown()
create()
fchmod()
fchown()
fcntl()
ftruncate()
lseek()
mkdir()
read()
readv()
unmask()
write()
writev()

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