IBM Enterprise Records, Version 5.1.+            

Running Disposition Sweep for an Auto Destroy action

The Disposition Sweep for an auto destroy action will immediately delete those records marked for Auto Destroy.

Attention: When running a disposition sweep for an auto destroy action on a multi-filed record, the record will be unfiled from the container targeted by the sweep but will remain in other containers not associated with the sweep.
In order for this type of sweep to complete successfully, you must have already tagged records with an Auto Destroy action. For more information, see Adding an action. You must have also updated the legacy disposition schedule to use Auto Destroy by changing the Phase properties. See Modifying a disposition schedule. There is also a special command for running disposition sweep for and Auto Destroy action if you have multiple profiles. Profiles allow you to save different configurations and run sweep using these configurations without the need to reconfigure them.

To run Disposition Sweep:

  1. Run Disposition Sweep with the -autodelete parameter from the RecordsManagerSweep folder on the machine where you installed the Disposition Sweep component. Use the following methods to run Disposition Sweep, depending on your operating system type:
    Option Description
    UNIX ./RecordsManagerSweep.sh -DispositionSweep -autodelete [-profile "profile name"]
    Windows ./RecordsManagerSweep.bat -DispositionSweep -autodelete [-profile "profile name"]
  2. You can verify whether Disposition Sweep ran successfully by viewing the error log file created in the RecordsManagerSweep folder. If the error file is empty, the Disposition Sweep process ran successfully. Otherwise, the file will contain errors that you can use to troubleshoot the problem.
  3. To stop Disposition Sweep, add the -stop parameter:
    Option Description
    UNIX ./RecordsManagerSweep.sh -DispositionSweep -stop [-profile "profile name"]
    Windows ./RecordsManagerSweep.bat -DispositionSweep -stop [-profile "profile name"]
    A message displays when the Disposition Sweep processes have stopped.
Checking the log file

After Disposition Sweep runs, check the activity log you configured. The log file shows when various types of processes start and end and lists entities processed and updated. If there are errors, a trace is included. What is not included though is a list of records that failed, since Content Engine is unable to supply the information.

By default, Disposition Sweep for an auto destroy action generates a transcript file with the name "AutoDestroy" plus the date and time to run auto destroy. For example, if you run RecordsManagerSweep.bat -DispositionSweep -autodelete on 12/03/2011 at 14:13:30, then AutoDestroy_2011_12_3_14_13_30.log will be found in the RecordsManagerSweep folder. This log file shows the following information:
  • The time, the RM entity's type (record or container) and id.
  • If the entity deletion succeeded or failed along with the reason for the failure (exception's localized message) if the deletion failed.
Running Disposition Sweep with -autodelete and generating the log file can cause some performance degradation. If you do not want the auto destroy log, you can run the following command which will run Disposition Sweep without generating a log file. There is also a special command which will run disposition sweep without generation a log file if you have multiple profiles.
Operating system Command
UNIX ./RecordsManagerSweep.sh -DispositionSweep -autodelete -notranscript [-profile "profile name"]
Windows ./RecordsManagerSweep.bat -DispositionSweep -autodelete -notranscript [-profile "profile name"]


Feedback

Last updated: August 2011
run_autodestroy_disposition_sweep.htm

© Copyright IBM Corporation 2011.
This information center is powered by Eclipse technology. (http://www.eclipse.org)