Date:         Wed, 30 Oct 2002 14:07:09 -0600
Reply-To:     Kevin Myers <KevinMyers@AUSTIN.RR.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Kevin Myers <KevinMyers@AUSTIN.RR.COM>
Subject:      Re: sas/le - where do I put the autoexec?
Comments: To: "Fehd, Ronald J. (PHPPO)" <rjf2@cdc.gov>
Content-Type: text/plain; charset="iso-8859-1"

Hi Ron -

Unfortunately, -INSERT doesn't work with all of the directory list type
options, and in particular SASAUTOS.  I can't remember exactly why offhand,
but it has to do with the fact that the SASAUTOS value is created with
the -SET option in the default configuration file, while other options such
as -SASHELP don't use -SET.  I don't know the reasoning behind these
inconsistencies, but suspect they may have risen from historic issues and
the need to maintain compatibility.  In any case, you can still effectively
insert into SASAUTOS, as you can see in the example from my prior email:

-SASAUTOS ("!petRoot\sasmacro" "!sasUtils\sasmacro"  "!playpen\..\sasmacro"
SASAUTOS)

The above line inserts 3 additional directories in front of the default
SASAUTOS value, which is represented by the occurance of SASAUTOS within the
parentheses.  This is basically SAS concatenated library syntax.  Make
sense?  Enjoy!

By the way, even if -INSERT doesn't show up in the OS companion for Windows,
that is where I have always used it.

Hope you won't mind, I'm copying the list so that other folks will be aware
of these issues as well.

s/KAM


----- Original Message -----
From: "Fehd, Ronald J. (PHPPO)" <rjf2@cdc.gov>
To: "'Kevin Myers'" <KevinMyers@AUSTIN.RR.COM>
Sent: Wednesday, October 30, 2002 1:25 PM
Subject: RE: sas/le - where do I put the autoexec?


> > For example, below is one customized config.sas that I have
> > used previously. Note how the -CONFIG option points through
> > to the system installed config.sas file, and also note the
> > use of the -SASAUTOS, -INSERT, and -PATH options.  Most folks
> > won't need the -INSERT and -PATH options, but they are available...
> >
> > s/KAM
> >
> > -SET sasRoot  "C:\Program Files\SAS Institute\SAS\V8"
> > -SET petRoot  "d:\petroleum"
> > -SET sasUtils "d:\saskbm\utils"
> > -SET playpen  "d:\saskbm\sashelp"
> >
> > -CONFIG "!sasroot\sasv8.cfg"
> >
> > /* -SASUSER c:\saskbm\sasuser */
> >
> > -SASAUTOS ("!petRoot\sasmacro" "!sasUtils\sasmacro"
> > "!playpen\..\sasmacro"
> > SASAUTOS)
> > -INSERT SASHELP ("!playpen")
>
> Keven,
> I've not doing something right with this INSERT command
> if I understand it correctly, it prepends the directory to the named
option
>
> - - - sitev8.cfg - - -
> -SET sasRoot  "C:\Program Files\SAS Institute\SAS\V8"
> -CONFIG "!sasroot\sasv8.cfg"
>
> -SET siteroot "u:\dls\SAS"
> -INSERT SASAUTOS "!SITEroot\macros"
> - - - end sitev8.cfg - - -
>
> however, -verbose tells me I have only the named directory for SASAUTOS
>
> SASAUTOS        "!SITEroot\macros"
>
> ah, so, well the INSERT is not working:
>
> 2    %put sasautos %sysget(sasautos));
> sasautos ("!sasroot\core\sasmacro"
> "!sasext0\access\sasmacro"
> "!sasext0\assist\sasmacro"
> ...
> ))
>
> INSERT only shows up in some of the OpSys companions, not Win.
>
> ok, nevermind, I prepend my site macro directory in my autoexec.
>
> big thanks for this tip.
> will make my life soooo much easier.
> 'acts as an %include' was a key phrase.
>
> Ron