I share woodfold's basic idea. I've had an instance where I started a defrag and walked away, when I came back and wanted to examine the log file, I noticed it was overwritten by a scheduled defrag which ran after the initial one had finished. Realizing you can specify the logfile name in the script, sometimes it's cumbersome to have to write multiple scripts that do the same thing, just so you can protect their log file. As such, I have the following macro suggestions:
!ScriptName! (for example "OptimizeWeekly")
!TimeStamp! (for example "20091002135501")
This would allow me to define something like:
Which would create a file called: OptimizeWeekly-20091002135501.log
These macros could prove useful in other applications as well.