No, the --privdelete sub-command is only a parameter to 'isi worm mkdir' and 'isi worm modify' commands as it is a SmartLock directory setting. The command controls the ability to actually administratively delete committed files using the filedelete command.   mav1-1# isi smartlock modify --path=/ifs/smartlock1 --privdel=on   !! Privileged delete enabled.   mav1-1# isi smartlock list -l ID|Root Path |Type |Override Date |Def. Ret. |Min. Ret. |Max. Ret. |Autocommit Period |Priv.Del. ------+-----------------+-----------+---------------+-----------+-----------+-----------+-------------------+----------- 65536 | /ifs/smartlock1 | SmartLock | None       | None      | None      | None      | None              | On   isi worm filedelete is the only method to delete committed files from a SmartLock directory but this is dependent on the privdel status of the directory.  --privdel    -- Privileged delete state, where is on (allowed) off (not allowed) or disable (PERMANENTLY disabled) (SmartLock Enterprise directories only.)  On a Compliance Mode SmartLock directory, this is always set to (PERMANENTLY disabled).   I would suggest not using the isi domain commands to manage SmartLock directories.
I am a little hesitate to conclude it on my own, so thought I'd just ask.  In the OneFS 7.1 CLI Administration Guide, the command isi worm privdelete are mentioned in both isi worm mkdir and isi worm modify commands. But when I tried the command, I received an error: isi worm: Unrecognized sub-command: privdelete  Should it actually be isi worm filedelete? And is isi worm filedelete the only command to delete files in CLI? (I noticed isi domain filedelete is an alias of isi worm filedelete.)
isi worm privdelete?