From the client point of view, a complete NetWare file path includes the names of the NetWare server, the volume, any parent directories, and the file itself. For example, in the following file path FS1 is the server, SYS is the volume, DOC and REPORT are directories, and CHAP1.TXT is the filename:
FS1/SYS:DOC/REPORT/CHAP1.TXT
NetWare accepts forward slashes or back slashes between the components of a file path.
WARNING:All filenames and path parameters must be consistent with the name space used to access the directory entry. For DOS names, all characters should be upper case. Generally, directory handles and path names are expected to follow DOS conventions unless you are running a different OS and the corresponding name space is loaded for the specified volume.
Also see the Combining a Path and Directory Handle task.
Many functions accept wildcard characters within a filename parameter. For example, with NWIntEraseFiles the file path can include wildcard characters, in which case a single request is able to erase multiple files. The following table shows the wildcard characters supported by NetWare®.
Functions operating on directory entries typically include a search attribute. The attribute specifies the type of entries to include in the operation. The search attribute lets you include system and hidden files and files in subdirectories.
For functions that can operate on both directories and files, typically do one to the exclusion of the other. For these functions, the search attribute lets you specify whether to operate on files or directories. Below are the possible bits defined by the search attribute:
NSS volumes store file and directory names in Unicode. NetWare 6.5 SP2 has added an NCP that allows you to access these names directly in UTF-8 (a Unicode encoding), rather than converting them to the server's or the client's code page. This functionality prevents the potential mangling of characters when the client and the server are using different code pages.
To use this functionality, the following requirements must be met:
The files and directories must reside on an NSS volume.
The server operating system must be NetWare 6.5 SP2 or later. This version adds a new set of file system NCPs: 0x2222 89.
You must use the new file system functions and pass all path and filenames as UFT-8 strings.
For client applications, the NetWare client must be version 4.90 SP2 or later. This version is available only for Windows 2000 and Windows XP clients
If one of these new function fails because one or more of the requirements are not met, the function converts the strings to the local code page and tries again using the old NCPs.
The following functions have been added for obtaining file system information:
The following functions have been added for managing trustees and effective rights:
NWGetObjectEffectiveRightsExt in the Bindery Management manual
NWScanObjectTrusteePathsExt in the Bindery Management manual
The following functions have been added for salvaging deleted files:
The following functions have been added for managing extended attributes (found in the Single and Intra-File Services manual):