0.9b (c) 1995 Peter Childs
The function prepares a 386-HPFS drive for directory limits. Before any other directory limits functions can be used on a drive, that drive must be enabled (only once) for directory limits by using either this function, the NET DASD command, or the OS/2 LAN Server Administration Graphical User Interface.
Syntax
MyRc = NetMisc(NETDASDCONTROL, 'DASDControl', SrvName)
Parameters
The parameters required and returned are:
'DASDControl' The directory limits control variable, which is divided into:
o DASDControl.CtlFlag
The control function to be performed on the 386-HPFS drive. Available values for this control flag are:
Value Meaning ----- ------- 1 Enables directory limits support on the specified drive 2 Disables directory limits support on the specified drive 3 Recalculates the space used in all of the directories of the drive specified that have directory limits placed upon them
The default value is 1 (Enable directory limits)
o DASDControl.Drive
The letter of the drive upon which the DASD control function is to operate. This drive must reside on the server specified by the SrvName parameter. The default drive value is 'C'
SrvName The computer name of the server to perform the control on. The server name specified can be '' for a local server
Remark
If the call is executed on a remote server a timeout code might be returned if no response is received from the server. This function might take up to several minutes to complete execution, especially on a large drive. Therefore, it can return a nonzero return code, while the remote function is still running. If one of the following error codes is returned by a call to NetMisc(NETDASDCONTROL), a timeout probably has occurred:
Value Meaning ----- ------- 64 The network name was deleted 67 This network name cannot be found 240 The session was canceled 2141 The server is not configured for transactions
These error codes do not mean necessarily that the NetMisc(NETDASDCONTROL) function failed. The function might still be running remotely.
You can execute the function on the server in question to avoid this problem.
Example
/* Activate DASD directory limits on server */ call RxFuncAdd 'LoadLsRxutFuncs', 'LSRXUT', 'LoadLsRxutFuncs' call LoadLsRxutFuncs NETDASDCONTROL = 740 DASDControl.CtlFlag = 1 DASDControl.Drive = 'C' SrvName = '\\DOMAIN_CONTRLR' myRc = NetMisc(NETDASDCONTROL, 'DASDControl', SrvName) if myRc <> '0' then do say 'Got error from NetMisc() ' myRc exitRc = 9 end else do say 'DASD Directory Limits enabled successfully' exitRc = 0 end call DropLsRxutFuncs call RxFuncDrop 'LoadLsRxutFuncs' exit exitRc
Example Output
DASD Directory Limits enabled successfully
Inf-HTML End Run - Successful