Date:         Tue, 23 May 2000 22:08:10 -0400
Reply-To:     Richard DeVenezia <radevenz@IX.NETCOM.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Richard DeVenezia <radevenz@IX.NETCOM.COM>
Organization: MindSpring Enterprises
Subject:      Re: Assign a directory at startup

The Libraries dialog (invoked with command DLGLIB via toolbar or just enter
DLGLIB into command window) is a host specific dialog.  As such, it writes a
host specific, undocumented catalog entry SASUSER.PROFILE.AUTOLIB.WINLIBS.
There is no documented way to read or write to that catalog entry.

You can alter the system-wide default autoexec.sas to include a text file or
source catalog entry to perform the library setups you want to have
programmatic control over.  The include is your 'extension function.'
Any user that decides to or is allowed to override the default autoexec.sas
should be told how to run the library setups.

e.g.
Your 'program' writes to a file 'custom-libs.sas' libname statements.
The autoexec.sas should do a:
filename autolib 'custom-libs.sas';
%include 'custom-libs.sas'.
filename autolib;

Your 'program' writes to a catalog entry 'SASUSER.PROFILE.AUTOLIB.SOURCE'.
The autoexec.sas should do a:
filename autolib catalog 'SASUSER.PROFILE.AUTOLIB.SOURCE';
%include autolib;
filename autolib;

"Benjamin Guralnik" <guralnik@BEZEQINT.NET> wrote in message
news:004901bfc405$e2c36500$327419d4@inXXguralnik...
> Hi,
>
> I've decided to post it as a separate question:
>
> How could the following steps be achieved programmatically?
> The user:
>     * goes to "Libraries"
>     * selects the appropriate lib
>     * and checks the "assign at startup" option under Modify Library.
>
> I guess that these settings could be maintained within either config.sas
or
> autoexec.sas, but are you actually supposed to *write* to these files on
> your own, at the appropriate place and all? Ideally, there would be an
> extension function or something.
>
> Thanks in advance,
> Benjamin