01-31-2018 12:53 AM
So just as a departure point. It's not EG so much that gets pointed to a particular sasv9.cfg, it's Base SAS (local) that would use that.
There are a couple of those in effect, so we would need some additional context.
01-31-2018 05:12 AM
01-31-2018 05:50 AM
Ok, I get you.
Forgetting about Base SAS, what settings in E Guide are you looking to have different between the projects ?
01-31-2018 09:28 AM
Of that last question's possible premises, reading between the lines, you're saying "it doesn't work that way". I found "Autoexec options" at (https://communities.sas.com/t5/General-SAS-Programming/Autoexec-options/td-p/...) . I'm surprised EG doesn't call SAS like SAS/CONNECT called remote servers. This is making me rethink things.
I'm tied also because I work with a community who is still working in SAS Interactive and I'm trying not to change my system to much. If that makes sense, I use to understand these things better several years ago, I feel.
01-31-2018 12:53 PM
When working with just Local SAS and EG, there is only one SAS command/config that can be registered at a time. That's stored in a Windows registry key, as described in this topic. SAS Enterprise Guide launches SAS with a COM call.
If you have a SAS Metadata Server and an object spawner, you can define multiple "SAS commands" and place them in Logical SAS Workspace objects. Then you can choose which SAS to launch from within EG -- there will be multiple options in the Server list. But that's a lot of work and overhead for just a local configuration.
A possible workaround: you could define some options and Autoexec logic based on environment variables. Then instead of launching EG from its standard shortcut, launch from a BAT (or CMD) file in which you SET the values of these environment variables. Rework your Autoexec.SAS or default config file to include references to the environment variables with the !ENV notation.