Domino Diva

I am at the airport, heading to the ZendCon conference in San Jose, CA.  I am expanding my companies' services into the PHP arena and had the opportunity to attend the ZendCon conference.  I'm looking forward to meeting with the developers and hearing from the industry experts that are presenting sessions.

 In working with a customer recently, we were looking for ways to free up some disk space on their iSeries server.  This customer had this as their Domino upgrade path over the past several years:

6.5.0 -> 6.5.1 -> 6.5.2 -> 6.5.3 -> 8.0.1 -> 8.5

The older Domino code loads had all been removed, however the contents of the /QIBM/ProdData/Lotus/DominoXXX directories had not been cleaned up.  We found code in the /Domino650, /Domino 651, /Domino652, and Domino653 subdirectories.  The /Domino801 subdirectory was empty, however the subdirectory was still on the system. 

All of the programs, service programs, and jar files for a specific release of Domino are stored in the /DominoXXX subdirectory for that specific release of Domino server code.  With the actual licensed program product for the release of Domino removed from the server, there was no need to have these directory structures left on the server. 

In order to delete these directories and their contents, we used the Edit File utility (EDTF) which has an option to recursively delete the contents of the subdirectories and then the subdirectories themselves. Upon entering the command below, you will see all of the /DominoXXX subdirectories that exist on your system.