This worked fine when I tried it. For you is it failing to delete the file or does adtempus say the job failed but it really was deleted? You could try the /q parameter to the del command to make it not prompt for confirmation. You could also use the capture console option when you set up the job to see what it's asking you for.

Well, I learned some things today.  First, the /f with the del will force the files to be deleted.  Second, you must make sure you don't have any extra spaces between the /f and the file name, it really only likes one.  Finally, I learned something I've known for years...if the file doesn't exist, you can't delete it.

On another note, do you have a good idea where I can get a key for those message codes that show up in the status reporting?

"message codes"--do you mean the "result" listed by adTempus? That's the exit code returned by the program. It depends on the program you are running. There's a snarky note about this in the user guide (http://www.arcanadev.com/adtempus/documentation/2.0/default.htm#notes/Exit_Codes.htm).

 

I foudn a similair issue but only when using unc paths which is of course not supported by the command line del, I have written a vb app that you can use as a command line execution with parameters, if anyone wants it let me know.