The --override setting will override any default or explicit retention placed on a committed file, it has no impact on empty SmartLock directories or uncommitted files. An example of override in use:  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 | 2014-01-01 00:00:00 |  1d       | None   |  1w   | None | On  mav1-1# isi smartlock info --path=/ifs/smartlock1/1.txt SmartLock Info for: /ifs/smartlock1/1.txt   SmartLock Root Directory ------------------------ ID    | Root Path ------+---------------- 65536 | /ifs/smartlock1   SmartLock State: COMMITTED  Expires: 2013-11-26 12:29:11 * Expire date currently overridden to: 2014-01-01 00:00:00   The addition of an override date will impact all existing committed files and any new files that are committed as long as the override is in place. It can be removed at any time and will impact all committed files; see example below, the same file but the override on the directory has been removed.   mav1-1# isi smartlock modify --path=/ifs/smartlock1 --override=none   !! Override date set: None   mav1-1# isi smartlock info --path=/ifs/smartlock1/1.txt SmartLock Info for: /ifs/smartlock1/1.txt   SmartLock Root Directory ------------------------ ID    | Root Path ------+---------------- 65536 | /ifs/smartlock1   SmartLock State: COMMITTED  Expires: 2013-11-26 12:29:11  File no longer has an override date attached. Expiration is now based on the date that was used when file was committed; default, min/max or explicit.  Min/Max are related to explicit retention when used and an override date will just place the explicit override date on that file irrespective of those settings.
I see the --override option in isi worm mkdir command:  {--override | -o} { | none}  Specifies an override retention date. The override retention date is a specific date that files committed to a WORM state within this directory are released from a WORM state. You can only increase the retention period expiration date of WORM committed files.  What does override option do when isi worm is creating a new SmartLock directory, where there's no WORM file in the new directory at all? Does the override value application to new WORM file? If so how does the override value works together with the min/max/default retention period?
isi worm mkdir --override