"DEV/TEST/PROD": If that term means something to you, then you are probably among our many customers that use SAS software across different environments. You might have one SAS environment for playing around ("dev" for "development"), another for testing candidate changes ("test"), and yet another for production processes ("prod").
Or, you might work with different environments that are segregated across business units: one for Finance, for example, and another for Human Resources. You can also create different profiles for a single environment, but with different user accounts -- for example, one account with admin privileges, and another as a "mere mortal" end user.
Wouldn't it be convenient to have different shortcuts on your desktop so that you can launch SAS Enterprise Guide and point directly to the environment that you want to use? We thought so, and so we added some command-line options in the 4.2 release to make this easy to do.
The command-line option is /profile:"ProfileName", where "ProfileName" is the friendly name you used to label your SAS profile definition. (The quotes are optional unless the profile name contains spaces or special characters, in which case the quotes are necessary.) Here is an example command that you can use in a desktop shortcut to connect to the "prod" environment:
"C:\Program Files\SAS\EnterpriseGuide\4.2\seguide.exe" /profile:prod
Here is a variation with a space in the profile name ("My Server"):
"C:\Program Files\SAS\EnterpriseGuide\4.2\seguide.exe" /profile:"My Server"
And finally, if you want to run with no profile: that is, without connecting to a SAS metadata server at all (using just your local SAS installation), you can run:
"C:\Program Files\SAS\EnterpriseGuide\4.2\seguide.exe" /noprofile
10 Comments
Hi Chris
Is there anyway to invoke the profile option for an EG project that is scheduled via the EG/Windows schedule function?
The VBS that is created calls a egp project file directly and then opens it via the windows association, so I can't seem to find a way of inserting the profile parameter.
Cheers
Shane
Shane, yes there is a way.
Use the SetActiveProfile method on the Application object. Example:
Set app = CreateObject("SASEGObjectModel.Application.4.3")
' Set to your metadata profile name, or "Null Provider" for just Local server
app.SetActiveProfile("My Server")
Full example is in this blog post:
http://blogs.sas.com/sasdummy/index.php?/archives/256-Using-SAS-Enterprise-Guide-to-run-programs-in-batch.html
Pingback: Review your metadata profiles using SAS Enterprise Guide automation - The SAS Dummy
I've got a slightly different problem. I'm running EG with a local SAS server (no profiles), and I'd like to change the options that are passed to SAS on startup (I'm
gnashing my teethdeveloping some options with ARM).How can I pass the ARM information to SAS at startup from EG?
Thanks,
Tom
Tom, if the options are "startup only" options (config file or SAS command line), then you must add them to the config file associated with the SAS Workspace definition. For example, on a default Windows installation, you'll find a sasv9_usermods.cfg file in ..\SAS\Config\Lev1\SASApp. You can edit that file and put your options there.
If running with just Local SAS for Windows, you can modify the default SAS command with these instructions.
Hi Christine, is there a option to pass -autoexec "myenv.sas" at command line to get all environment library assigned at startup.
Not from EG. You need to work with an administrator to assign those from the OS shell or in a config. But you can use the Autoexec Process flow in EG to set per-project options.
Chris, I believe in older version of SAS we had EGauto.sas which can be called at SAS invocation.. Is there any alternate approach in newer version 7.1?
I'm looking to accomplish something like this.. "C:\Program Files\SAS\EnterpriseGuide\7.1\seguide.exe" /profile:prod -autoexec "C:\user\ss\desktop\init.sas"
So libraries are assigned once per EG session.. Can you let me know how to accomplish this? Which section in config file needs update?
Thanks for your help!
EGAuto.SAS is a thing of the past, but there are a number of ways to "inject" Autoexec-like function in your process. Check Leonid's blog post for some ideas.
Hi Chris, is there a option to pass -autoexec "myenv.sas" at command line to get all environment library assigned at startup.