Note that NWCallsInit(3nw) must be called before any other NetWare API function. Note also that paths passed to functions must be uppercase or the functions fail for platforms other than UnixWare.
If the function supports the NLM® platform, the summary is followed by two lines that indicate whether the function can be called locally or remotely, and whether the function blocks or not. Blocking functions relinquish control of the CPU, allowing other functions to run: non-blocking functions do not relinquish control of the CPU, but run to completion.
Local Server indicates whether the function can be called on the server upon which the NLM is running (locally). Remote Server indicates whether the function can be called on a server other than the server that the NLM is running on (remotely). If ``N/A'' (not applicable) appears, that platform is not supported. That is, if the Remote Server category states ``N/A'', the function cannot be called remotely. Values other than ``N/A'' indicate that local/remote servers are supported, and also give blocking information as follows:
The NetWare Server line lists all the NetWare server versions supporting that function.
The Platform line lists all the client platforms supporting the function. The functions are only tested with the newest versions of the Requesters. If you want your application to run with older versions, you are responsible for fixing any resulting incompatibilities.
The UNIX platform designation is slightly different than the other platform designations. ``UNIX'' in this context is a generic term referring to many different implementations of UNIX. Specifically, ``UNIX'' indicates the function is supported for the UnixWare operating system.
The NetWare for UNIX Server line lists the NetWare for UNIX server versions that support the function.
This section notes the service group that the function belongs to, and corresponds to the information given in the following sections.
Lists the NCP calls used by the function.
The abstract data types employed by the NetWare Client API are defined in the nwalias.h header file. Throughout this documentation, the abstract data type is used to refer to a data item, wherever possible. For a complete list, refer to Abstract data types. For a listing of the error conditions returned by the NetWare Client API, refer to ``Error return values''.
Note that any references to VLM or VLM.exe refer to the NetWare 4 requestor on UnixWare platforms.
The following list gives the services affiliations of the functions of the NetWare API functions. Clicking on an entry will display a list of the functions in that service group.
For a list of the supported functions, refer to Accounting services functions; for a guide to the use of this API, see ``Accounting services''.
For a list of the supported functions, refer to Appletalk services functions; for a guide to the use of this API, see ``AppleTalk filing protocol services''.
For a list of the supported functions, refer to Auditing services functions; for a guide to the use of this API, see ``Auditing services for UnixWare''.
For a list of the supported functions, refer to Bindery services functions; for a guide to the use of this API, see ``Bindery services''.
For a list of the supported functions, refer to Connection services functions; for a guide to the use of this API, see ``Connection services''.
For a list of the supported functions, refer to Connection services (directory support) functions; for a guide to the use of this API, see ``Connection (directory support) services''.
For a list of the supported functions, refer to Data migration services functions; for a guide to the use of this API, see ``Data migration services''.
For a list of the supported functions, refer to Deleted file services functions; for a guide to the use of this API, see ``Deleted file services''.
For a list of the supported functions, refer to Directory services functions; for a guide to the use of the directory services supplied by this API, see the following topics:
For a list of the supported functions, refer to Extended attribute services functions; for a guide to the use of this API, see ``Extended attribute services''.
For a list of the supported functions, refer to File I/O services functions; for a guide to the use of the filesystem APIs, see ``File system services''.
For a list of the supported functions, refer to File server environment services functions; for a guide to the use of this API, see ``File server environment services''.
For a list of the supported functions, refer to Filesystem services functions; for a guide to the use of this API, see ``File system services''.
For a list of the supported functions, refer to Internationalization services functions; for a guide to the use of this API, see ``Internationalization services''.
For a list of the supported functions, refer to Message services functions; for a guide to the use of this API, see ``Message services''.
For a list of the supported functions, refer to Name space services functions; for a guide to the use of this API, see ``Name space services''.
For a guide to the use of these services, see ``NCP extension services''. The first group is that of the NLM NCP extension functions. If the NCP extension client is being programmed to run on a NetWare server machine these functions must be used instead of those functions found in the second group. For a list of the supported functions, refer to NCP extension services functions. The second group, the client NCP extension functions, are used when programming a client application that runs on any of the platforms specified. Workstations running DOS, Windows, NT, or OS/2, as well as those running UnixWare, are currently the platforms for which these functions have been developed. For a list of the supported functions, refer to NLS services functions.
For a list of the supported functions, refer to NLS services functions; for a guide to the use of this API, see ``Netware licensing system (NLS) services''.
For a list of the supported print server configuration functions, refer to Print server configuration services functions; for more information on the use of this API, see ``Print server configuration services''. For a list of the supported print server communications functions, refer to Print server communications services functions; for more information on the use of this API, see ``Print server communication services''.
For a list of the supported functions, refer to Print services functions; for a guide to the use of this API, see ``Print services''.
For a list of the supported functions, refer to QMS services functions; for a guide to the use of this API, see ``Queue management system (QMS) services''.
For a list of the supported functions, refer to Synchronization services functions; for a guide to the use of this API, see ``Synchronization services''.
For a list of the supported functions, refer to TTS services functions; for a guide to the use of this API, see ``Transaction tracking services''.
For a list of the supported functions, refer to Unicode services functions; for a guide to the use of this API, see ``Unicode services''.
For a list of the supported functions, refer to Volume services functions; for a guide to the use of this API, see ``Volume services''.
For a complete list, refer to Obsolete functions, where for each obsolete function, where appropriate, the equivalent new function is indicated.