Bookmark and Share

Notice: On March 31, it was announced that Statalist is moving from an email list to a forum. The old list will shut down on April 23, and its replacement, statalist.org is already up and running.


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: st: Stata Temp File issue


From   Eric Booth <ebooth@ppri.tamu.edu>
To   "<statalist@hsphsun2.harvard.edu>" <statalist@hsphsun2.harvard.edu>
Subject   Re: st: Stata Temp File issue
Date   Tue, 14 Dec 2010 20:16:14 +0000

<>

Adding to Kevin's comment:   I've always set the temp directory before launching Stata as described in the FAQ:
http://www.stata.com/support/faqs/data/statatmp.html

For some reason, setting the temp file location in DOS doesn't always "take" when I launch Stata afterward.   That is,  if I set the tempfile location in DOS (as described on the page linked above) and then double click on my Stata icon I still don't always get the right tempfile path path when I type 
tempfile j
di "`j'"
in the new instance of Stata.  However, I've had more success if set the tempfile location in DOS and then subsequently launch Stata from DOS.  I don't know that this is what _causes_ the new instance of Stata to use the correct tempfile location or not; but it seems to work for me if I follow this process.

- Eric
__
Eric A. Booth
Public Policy Research Institute
Texas A&M University
ebooth@ppri.tamu.edu


On Dec 14, 2010, at 1:56 PM, Kevin Geraghty wrote:

> 
> try << display "`c(tmpdir)'" >> and see what it tells you.
> 
> Hm. It looks like you can't set it once you launch stata, that you have to set it beforehand using environment variables.
> 
> so you would have to do something like this on windows:
> in a shell script or on the command line of a dos window:
> 
> set STATATMP="c:\temp" (or your choice of temp directory for this invocation)
> <then invoke your executable from your shell window>
> 
> you can check if you got it right by typing << display "`c(tmpdir)'" >> again
> 
> 
> 
> 
> 
> 
> 
> 
> ----- "John C. Vernaleo" <john.vernaleo@adainvestments.com> wrote:
> 
>>> I realize you shouldn't have to do this, that stata ought to be able
>> to keep track of this stuff on its own, but one straightforward fix
>> for this problem might be explicitly setting the temp directory at the
>> start of each concurrent job, so that they don't share the same
>> temp/work directory, and there will be no file naming conflicts for
>> active temporary files.
>> 
>> Assuming I'm understanding my situation correctly, that solution would
>> be
>> great.
>> 
>>> 
>>> something like:
>>> 
>>> sysdir set tmpdir <my chosen temporary directory>
>> 
>> When I try that I get:
>> . sysdir set tmpdir     "C:\temp\"
>> tmpdir not found
>> 
>> And then:
>> . sysdir list
>> STATA:  C:\Program Files\Stata9\
>> UPDATES:  C:\Program Files\Stata9\ado\updates\
>> BASE:  C:\Program Files\Stata9\ado\base\
>> SITE:  C:\Program Files\Stata9\ado\site\
>> PLUS:  c:\ado\plus\
>> PERSONAL:  c:\ado\personal\
>> OLDPLACE:  c:\ado\
>> 
>> So it doesn't look like tmpdir is something Stata knows about.  I
>> guess it
>> just uses whatever Windows sets as the temp directory (do you know if
>> Stata uses TEMP or TMP offhand since I seem to have both defined by
>> Windows?).
>> 
>> If that is the case I guess I can set the Windows temp variable (once
>> I
>> figure out which one it is) to something specific for each of the
>> Stata
>> processes.
>> 
>> I will of course report back if I have success with that.
>> 
>> John
>> 
>> This communication is for informational purposes only. It is not
>> intended to be, nor should it be construed or used as, financial,
>> legal, tax or investment advice or an offer to sell, or a solicitation
>> of any offer to buy, an interest in any fund advised by Ada Investment
>> Management LP, the Investment advisor.  Any offer or solicitation of
>> an investment in any of the Funds may be made only by delivery of such
>> Funds confidential offering materials to authorized prospective
>> investors.  An investment in any of the Funds is not suitable for all
>> investors.  No representation is made that the Funds will or are
>> likely to achieve their objectives, or that any investor will or is
>> likely to achieve results comparable to those shown, or will make any
>> profit at all or will be able to avoid incurring substantial losses. 
>> Performance results are net of applicable fees, are unaudited and
>> reflect reinvestment of income and profits.  Past performance is no
>> guarantee of future results. All f!
>> inancial data and other information are not warranted as to
>> completeness or accuracy and are subject to change without notice.
>> 
>> Any comments or statements made herein do not necessarily reflect
>> those of Ada Investment Management LP and its affiliates. This
>> transmission may contain information that is confidential, legally
>> privileged, and/or exempt from disclosure under applicable law. If you
>> are not the intended recipient, you are hereby notified that any
>> disclosure, copying, distribution, or use of the information contained
>> herein (including any reliance thereon) is strictly prohibited. If you
>> received this transmission in error, please immediately contact the
>> sender and destroy the material in its entirety, whether in electronic
>> or hard copy format.
>> 
>> *
>> *   For searches and help try:
>> *   http://www.stata.com/help.cgi?search
>> *   http://www.stata.com/support/statalist/faq
>> *   http://www.ats.ucla.edu/stat/stata/
> *
> *   For searches and help try:
> *   http://www.stata.com/help.cgi?search
> *   http://www.stata.com/support/statalist/faq
> *   http://www.ats.ucla.edu/stat/stata/




*
*   For searches and help try:
*   http://www.stata.com/help.cgi?search
*   http://www.stata.com/support/statalist/faq
*   http://www.ats.ucla.edu/stat/stata/


© Copyright 1996–2014 StataCorp LP   |   Terms of use   |   Privacy   |   Contact us   |   Site index