We are looking into the differences between using ARSADMIN Unload and ARSDOC Delete.
The CMOD Administration Guide suggests:
- ARSADMIN Unload function will delete the storage objects and index data related to a LoadID.
- ARSDOC Delete function will delete documents from the system.
In our setup, we have an application group in which we have very few documents loaded per LoadID (1 document per LoadID). In addition, we must maintain these documents in multiple test and pre-production environments (5 environments to be precise). So, in order to update 60 of these documents, we have to remove them before loading an updated version. That gives us a total of 300 LoadID?s to identify (60 LoadIDs X 5 environments). Note that this is a one-time (one-shot) maintenance task.
We are concerned with the amount of time required to identify all of these LoadID?s. We are considering using the OD toolbox to remove documents instead, but we require more info concerning the ARSDOC Delete function.
1. Does ARSDOC Delete remove the storage objects, or simply the index data? It has been brought to my attention that ARSDOC Delete simply removes the index data.2. What happens when all documents have been removed from a LoadID using ARSDOC Delete?
3. Is there any way to perform a cleanup of leftover LoadIDs, objects or references?We are running CMOD v.7.1.2.8 on an AIX Server and Windows Client v.7.1.2.8.
Any ideas or suggestions are welcome.
Thanks,
Pat Bastien
