Cleaning Up a Previous dataxform Session
When dataxform execution completes (or aborts), it leaves behind status files that it uses to regulate subsequent executions. Whenever the dataxform starts, it looks for these files and if it finds them, either resumes running where it left off, or displays an informative message and exits without transforming any files. The exiting prevents dataxform from running repeatedly. Prior to running dataxform, a protected host administrator must execute the utility’s “cleanup” function to eliminate status files from previous runs. If a transformation fails, the protected host administrator must repair the problem, complete transformation, and then execute the cleanup function.
Warning
NEVER run a cleanup operation after a partial transformation, as you will be unable to resume transforming the remaining files.
When dataxform is run, it checks the status in the dataxform_status-gp file. If the status is “done”, dataxform exits with “data transform status for GuardPoint_dir: previous attempt completed” error message. Remove the status file and other configuration files with the --cleanup option.
The command syntax for cleaning a previous dataxform session is:
For example:
The --cleanup operation does not return a message indicating a successful completion. If there are no errors, the cleanup operation completed successfully, and you can now run dataxform on the GuardPoint.
