Proc Logistic Spawns _DOCTMP000000000000000000

[JBerry]

In SAS Enterprise Guide, when I run PROC LOGISTIC ...  the process spawns a bunch of temp table shortcuts to appear on my Process Flow work space.

It's immensely annoying because it causes clutter and it always readjusts the positioning of my objects.  Any way to suppress this behavior?

The temp tables are all named like...

_DOCTMP000000000000000000000026

_DOCTMP000000000000000000000027

_DOCTMP000000000000000000000028

_DOCTMP000000000000000000000029

_DOCTMP000000000000000000000030

Sample code:

%LET VARS = v1 v2 v3 v4;

%LET OUTDATA = work.outdata;

ods graphics on;

proc logistic data=work.indata NAMELEN=32;

model Y_VAR(event='1') = &VARS.

  / SELECTION = STEPWISE rsq lackfit;

    roc;

  OUTPUT OUT=&OUTDATA. p=myPrediction ;

run;

title;

title1;

proc reg data=data=work.indata;

model Y_VAR= &VARS.

/ TOL VIF COLLIN;

run;

ods graphics off;

[JBerry]

A shameless /bump

[ChrisHemedinger · Accepted solution]

It looks like there are a few ODS document "work" tables that aren't being deleted when the procedure completes.  What version of SAS are you using?  I tried a similar example but wasn't able to replicate the problem.

You can work around the issue by adding this to the end of your program:

proc datasets lib=work nolist nodetails;
  delete _DOCTMP:;
quit;

Chris

[JBerry]

Thank you Chris! The workaround seems to work!

I'm using EG 6.1 M1HF1 for Windows 7 x64 on SAS 9.4.1.0

[DanielFuhrmann]

Hello Chris,

I am seeing this phenomenon in my current SAS session, too. I am running the desktop version of SAS 9.4 (TS1M1) on a X64_7PRO platform. The temporary data sets are being created by both PROC REG and PROC SYSLIN in my project.

Best,

Daniel

[JBerry]

Hi Daniel,  I have been religiously using Chris's suggestion above to delete datasets that spawn at the end of my programs, it really helps keep my workspace looking neater.

[DanielFuhrmann]

Hello Jberry,

I like Chris's recommendation, too. It's very useful. My post was purely to inform Chris that this problem occurs not only in SAS EG but also in the desktop client's windowing environment of SAS.

Take care,

Daniel