I have been running this way for years. It works for schedules and agents, as well as Run as... | Run in background...
But...
Now I wonder about the quality of the documentation and the knowledge of the consultants that set up my Cognos environment.
Pages 77-79 of the
IBM Cognos Analytics Version 11.0 Administration and Security Guide include information about this.
Saving report output files outside of IBM Cognos softwareReport output files can be saved to a file system outside of IBM Cognos software. Users can choose which
output files to save.
talks about
Archive Location File System Root and creating the aliases by using
Define File System Locations writes messy file names and provides no scripting options
Saving report output files in IBM Cognos SoftwareUsers can save copies of report output files in IBM Cognos software. All report output files are saved to a
location specified in Content Manager.
uses
Save report outputs to a file system = true
this mentions CM.OutPutLocation and CM.OutputScript
The two things appear to be unrelated. The first allows reports that are scheduled or run in the background to be sent to a directory on the file system. The second causes every saved "version" of a report to be also saved to the file system. Apparently the only reason I have not been duplicating all of my saved reports is I did not have CM.OutPutLocation set. (And I'm happy about that. Running out of drive space is not fun.) If that's true, it seems like I don't need
Save report outputs to a file system = true.
Bummer. I was hoping I could write a script to strip off the "_en_us" from all of the file names of my report outputs and delete all of the XML files.