Date:         Sat, 5 Sep 2009 00:21:58 +0800
Reply-To:     Murphy Choy <goladin@GMAIL.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Murphy Choy <goladin@GMAIL.COM>
Subject:      Re: Libname User
Comments: To: Norm Weston <nweston@amgen.com>
In-Reply-To:  <200909041541.n84AlHb4008981@malibu.cc.uga.edu>
Content-Type: text/plain; charset=ISO-8859-1

Hi,

You can try using this statement.

%sysfunc(libname(user));

On Fri, Sep 4, 2009 at 11:41 PM, Norm Weston <nweston@amgen.com> wrote:

> I recently took over a job from another programmer.  This programmer
> routinely uses the command Libname User and quite a lot of their programs
> require PC SAS.  I use PC SAS alot in my own development but find that,
> once I execute the program, the normal "WORK" directory no longer holds my
> temporary datasets and that they are now written out to some predesignated
> Libname USER.  While I can see some benefit to this in that I have
> the "Temporary" datasets within a given set process written out, it is
> annoying when I am developing something to have it written out to a
> perminant dataset.
>
> My question is, is there any way to unassign the USER library after it has
> been set?  I find myself in the midst of developing something, have to run
> something for production and then when I go back to developing, the USER
> library is in place.
>
> Now I know the simple solution is to remove the USER library from all
> programs.  I say simple but it is very prevasive and would take a LOT of
> time.  Also, for production runs, I see definite benefit.  I just hate
> that I have to close out PC SAS and re-open it every time I run a
> production job.
>
> Anyone else have this problem?  Is there a solution?
>



--
Regards,
Murphy Choy

Certified Advanced Programmer for SAS V9
Certified Basic Programmer for SAS V9
DataShaping Certified SAS Professional