On 23 Nov, 12:12, "Richard A. DeVenezia" <rdevene...@wildblue.net>
> nancynpaul-s...@yahoo.com wrote:
> > Hi Richard,
> > I've only used the -sysparm option for this and then parsed the
> > &sysparm macro variable for the values that need to be assigned to
> > application macro variables. I'd be interested your requirements that
> > make it necessary to assign values to macro variables at invocation
> > time.
> In short, a systems startup sequence utilizes code that allows overrides
> %if (&iroot=) %then %let iroot = I: ;
> In other words, if a value is already assigned to a macro variable, it will
> be left alone. If I can get the macro variable to take on the value I want
> _prior_ to the above statement, then I will have overridden the default.
> The solution used was to create a new custom shortcut with a modified target
> -autoexec c:\dev\v913\migrationof\foo\testingAutoexec.sas
> and have testingAutoexec.sas contain
> %let IROOT=c:\dev\v913\migrationof\foo;
> %include "autoexec.sas";
> Things were additionally complicated because all this has to be performed
> automagically by a script that executes a migration and writes the testing
> autoexec and shortcut to start the migrated system.
> Richard A. DeVeneziahttp://www.devenezia.com/
by having a system environment variable set up like
name : sas_option
value : sasv9.cfg
Then in each folder where you start a sas session with a command line
it will seek not only the config file in !sasroot, but _also_ a
normally named config file in the "current folder"
It is that "local" config file that you could place an -initstmt
option, -set options of even -autoexec to point to your migrating
autoexec file. Obviously the list is not endless, it just seems that
author of the SGF paper "Easy SAS(R) Session Customization"