I want to submit the statement ods path work.mystore(update) sashelp.tmplmst(read); when I invoke SAS so I can modify templates temporarily. I tried to include it in the configuration file sasv9.cfg but it doesn't work. Could I get some suggestions as to how I can achieve this?
I use SAS 9.3 M1 x64 on Windows 7 Pro.
Thanks!
Beginning with version 9.2 SAS installs with a set of config files and autoexecs which are not meant to be modified. It says clearly in the header of such files:
* Do NOT modify this file. Any additions or changes should be made in autoexec_usermods.sas.
So if you change the standared autoexec and config files don't complain if the next patch or upgrade simply wipes out all of your modifications.
You can always add site specific modifications to the "usermods" versions or even create additional files.
Don't change config and autoexec files if the name does not contain "usermods".
If you're usin SAS EG then define it best as code to be run when you open the project (that's done in EG).
Else: You could put your code into a usermods autoexec if you must.
PTD_SAS wrote:
I want to submit the statement ods path work.mystore(update) sashelp.tmplmst(read); when I invoke SAS so I can modify templates temporarily. I tried to include it in the configuration file sasv9.cfg but it doesn't work. Could I get some suggestions as to how I can achieve this?
Very simple ... put it in your AUTOEXEC file. You may want to create a custom CONFIG file and AUTOEXEC file so the original remains unchanged.
Beginning with version 9.2 SAS installs with a set of config files and autoexecs which are not meant to be modified. It says clearly in the header of such files:
* Do NOT modify this file. Any additions or changes should be made in autoexec_usermods.sas.
So if you change the standared autoexec and config files don't complain if the next patch or upgrade simply wipes out all of your modifications.
You can always add site specific modifications to the "usermods" versions or even create additional files.
Thanks to all for the answers, autoexec_usermode.sas did the trick.
Good news: We've extended SAS Hackathon registration until Sept. 12, so you still have time to be part of our biggest event yet – our five-year anniversary!
Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.
Ready to level-up your skills? Choose your own adventure.