There is a wide array of papers (from SAS, conferences, on blog posts, etc) discussing the need to move WORK (the SAS temporary files) off to other locations.
In the SAS Intelligence Platform it's the same way, however there are a BUNCH of SAS configuration files to start worrying with. This is great because you can put WORK for one compute service in a separate location from another. You can also define the configuration for the entire system in one location.
The MAIN thing - (C:\\Program Files\\SAS\\SASFoundation\\9.2\\sasv9.cfg) applies options to the rest of the system. However this runs first, so you can overwrite this in any of the below configurations.
Each of the server configuration folders has two configuration files. sasv9.cfg and sasv9_usermods.cfg.
http://support.sas.com/documentation/cdl/en/bisag/60945/HTML/default/viewer.htm#a003147155.htm
SAS recommends that you modify or add options only to the sasv9_usermods.cfg (when available) and store these modifications in a backup location.
References:
http://support.sas.com/rnd/papers/sgf07/sgf2007-iosubsystem.pdf
http://support.sas.com/resources/papers/ETLperformance07.pdf
http://support.sas.com/rnd/emi/EbiApm92/sas92.ebiapm.win.pdf
1 Comment
The same goes for the autoexec.sas files. There are autoexec.sas and autoexec_usermods.sas for the SAS/Connect servers, Workspace Servers, and Stored Process Servers for changes you'd like to apply to these servers. The SAS Application Server (named SASApp by default in SAS 9.2)has an appserver_autoexec.sas and appserver_autoexec_usermods.sas for changes you want applied to the SAS Application Server.