NWReleaseFileLock2(3nw)


NWReleaseFileLock2 -- unlocks file but does not remove it from log table

Synopsis

   #include <nwfile.h> 
   or 
   #include <nwcalls.h> 
   

NWCCODE N_API NWReleaseFileLock2 (NWCONN_HANDLE conn, NWDIR_HANDLE dirHandle, pnstr8 path);

Description

The parameters are as follows:

conn
(IN) Specifies the NetWare server connection handle.

dirHandle
(IN) Specifies the directory handle of the new directory's root directory.

path
(IN) Points to the string containing the name and path of the new directory.

Return values

0x0000
SUCCESSFUL

0x8801
INVALID_CONNECTION

0x8998
VOLUME_DOES_NOT_EXIST

0x899B
BAD_DIRECTORY_HANDLE

0x899C
INVALID_PATH

Notices

path can specify either a file's complete path name or a path relative to the current working directory. For example, if a file's complete path name is SYS:ACCOUNT/DOMEST/TARGET.DAT and the directory handle mapping is SYS:ACCOUNT, path could be either of the following:
   SYS:ACCOUNT/DOMEST/TARGET.DAT 
   DOMEST/TARGET.DAT 
2.x servers return INVALID_PATH when a bad directory handle is passed.

NWReleaseFileLock2 is ignored if the requesting workstation does not have locked files.

Services

Synchronization

NCP calls

0x2222 05 Release File

 
 ------------------------------------ 
| 0x2222|  05|  Release File        | 
|-------|----|----------------------| 

References

NWClearFileLock2(3nw), NWClearFileLockSet(3nw), NWLogFileLock2(3nw), NWReleaseFileLockSet(3nw)


30 January 1998
© 1998 The Santa Cruz Operation, Inc. All rights reserved.