Disk Library for mainframe: A DLm config install may fail with: "ERROR Mounting storage procedure failed: Tape library name '/lockdir' is a reserved folder name"

A DLm Configuration may fail with the following on the DLmConsole Screen, and/or in the /opt/webconsole/logs/apply.log, and logAll.txt.
Look for the mention of the /lockdir folder name or something smilar to it.  
Note: The /lockdir folder name could be something else than /lockdir.   Only /lockfs works now.

Start configuration operation at Tue Jan 21 09:51:58 2020
Tue Jan 21 09:52:01 2020 Check on DLMABCD
DLMABCD: Installation will not require Virtuent application restart
DLMABCD: Check finished
Tue Jan 21 09:52:08 2020 Install on DLMABCD
DLMABCD: Shutting down snmptrapd:..done
DLMABCD: Starting snmptrapd:..done
DLMABCD: Configuration update finished unsuccessfully. All changes will be rolled back...
DLMABCD: Performing roll back operations...
DLMABCD: ERROR Rollback procedure failure: Mounting storage procedure failed: Tape library name '/lockdir' is a reserved folder name, please choose another name.
DLMABCD: ERROR Mounting storage procedure failed: Tape library name '/lockdir' is a reserved folder name, please choose another name.
DLMABCD: --- Exit Code: 11
ERROR Install on DLMABCD failed, return code 11

All DLM configurations running with an Additional Parameter  "VOLSERLOCKDIR /lockdir/LOCK" and mount point to match, require the removal of the Additional Parameter "VOLSERLOCKDIR /lockdir/LOCK" and the mount point changed from /lockdir/LOCK to /lockfs/LOCK at 4.5.5 code. 

This Additional Parameter "VOLSERLOCKDIR /lockdir/LOCK" parameter is used to turn on the 'Enhanced File System' in the DLm. Later generations of the DLm no longer require this, and have a "Use Default lock FS" box. In DLm 4.5.5 code, /lockfs/LOCK is now checked for this specific name. 

All configurations that have this back-level parameter run into this issue at 4.5.5 code and later, and each configuration must be corrected.   

 
  

Modifying the configurations:     

1. On the Device Tab in the Additional Parameters area, click on the Parameters and change VOLSERLOCKDIR /lockdir/LOCK to VOLSERLOCKDIR /lockfs/LOCK  and click OK.  
2. On the Configuration Tab, save the config. Doing this removes the grayed out mount point /lockdir/LOCK in the Storage Tab (Available).
3. On the Storage Tab (Available), modify mount point /lockdir/LOCK to mount point /lockfs/LOCK.
4. Select the VTE tab(s) next to the Available tab and check mark the missing mount point /lockfs/LOCK for each VTE in the configuration.
5. On the Configuration Tab, save the config.
6. On the Device and Storage Tabs, check all the changes and you will notice:     

• On the Devices Tab, the Additional Parameter VOLSERLOCKDIR /lockfs/LOCK is GONE.
• A  USE default lock FS  box appears above the Additional Parameters and it is check marked.
• Once the changes are verified, install the modified config to validate the changes.   
  • The  Restart Virtuent if required  may be required for the configuration to be installed.

Note: All user configurations need to be checked and fixed.