Desktop productivity for business analysts and programmers

Issue with WORK folder in SAS Enterprise Guide on Localhost

Reply
Frequent Contributor
Posts: 131

Issue with WORK folder in SAS Enterprise Guide on Localhost

Hi SAS experts,

 

I have been searching the web for a couple of days now without finding any solution to my issue.

 

First, let me tell what is my local setup of SAS:

- Windows 7

- SAS 9.4

- SAS EG 6.1 (using the default "no profile" server --> localhost)

- NO SAS MetaData Server

 

Now, the description of my issue: when I launch SAS EG (and open an existing project, or create a new one), I can see the WORK library listed below the Local Server (in the task pane). Right clicking on it, and looking at its properties allow me to see what is the folder that is assigned to the libname (i.e. one session in my SAS Temporary Files folder on the C:\ drive). So far so good! The issue comes once I have ran some SAS code from a process flow and then refresh the WORK library (by running the whole flow, or a selection: issue is the same). I don't see the datasets which have been created in the WORK library... Trying to figure out how that could be possible, I have submitted a "%put %sysfunc(pathname(WORK));" in order to programmatically check what the location of the WORK is and figured out that it is different! It points to another work directory (i.e. with a name like "#TD....") in my SAS Temporary Files folder on the C:\ drive...

 

I would really appreciate if you could help me out finding why SAS EG is not making use of the same work directory for the WORK library that is visible under the task pane, and the WORK library in which the datasets are created when I run SAS code with Enterprise Guide.

 

Thanks a lot in advance for you help!

 

Kind regards,

 

Florent D.

Trusted Advisor
Posts: 1,709

Re: Issue with WORK folder in SAS Enterprise Guide on Localhost

Hello @Florent,

 

form the operating system point of view, every time you create a session, it would be a new folder for work, so the SAS sessions won;t be messing around with the temporary data of other parallel SAS sessions.

 

That being said, the SASWORK is defined on a variable on your SASFoundation/9.4/nls/[lang]/sasv9.cfg file, you cans et another location.

 

More things to consider:

 

if you run "data work.mydata;a=1;b=1;run;" (or "data mydata;a=1;b=1;run;", it is the same) you should be able to open your Libraries tree and see, under WORK the mydata dataset. Hence, work would be using all correctly. 

 

If any of this is not right in your case, please enable the project logging with these instructions http://support.sas.com/kb/17/730.html and send us the logs, perhaps also the sasv9.cfg file as well, and the output of running "%put _ALL_;".

 

Hope it helps.

 

Kind regards,

Juan

Frequent Contributor
Posts: 131

Re: Issue with WORK folder in SAS Enterprise Guide on Localhost

[ Edited ]
Posted in reply to JuanS_OCS

Hello @JuanS_OCS,

 

Thank you for the quick reply!

 

I know that the SAS WORK is defined in the CFG file you have mentioned, and that SAS creates a new temporary folder when I create a session. My issue with EG is that, for the same session, SAS seems to create two different temporary folders for wok (1 for the WORK library listed under the task pane --> at opening of SAS EG, and another one as soon as I run a piece of SAS code that creates a datasets in the WORK library).

 

Please find attached the additional information that you have requested.

 

LOG from EG:

 

Project Log cleared at 4/25/2018 1:06:10 PM
Log for "Test" run at 4/25/2018 1:06:26 PM on Local
1          %_eg_hidenotesandsource;
5          %_eg_hidenotesandsource;
26
27         data work.mydata;a=1;b=1;run;

NOTE: The data set WORK.MYDATA has 1 observations and 2 variables.
NOTE: Compressing data set WORK.MYDATA increased size by 100.00 percent.
      Compressed is 2 pages; un-compressed would require 1 pages.
NOTE: DATA statement used (Total process time):
      real time           0.01 seconds
      cpu time            0.01 seconds


28
29         %put _ALL_;
GLOBAL SASWORKFOLDER "C:\Users\ECF525\AppData\Local\Temp\SEG10584\SAS Temporary Files\_TD5008_UPLCI098360_\Prc2/"
GLOBAL SASWORKLOCATION "C:\Users\ECF525\AppData\Local\Temp\SEG10584\SAS Temporary Files\_TD5008_UPLCI098360_\Prc2/"
GLOBAL SYS_SQL_IP_ALL -1
GLOBAL SYS_SQL_IP_STMT
GLOBAL _CLIENTAPP 'SAS Enterprise Guide'
GLOBAL _CLIENTAPPABREV EG
GLOBAL _CLIENTMACHINE 'UPLCI098360'
GLOBAL _CLIENTPROJECTNAME 'Test_Project.egp'
GLOBAL _CLIENTPROJECTPATH 'C:\Users\ECF525\Desktop\Test_Project.egp'
GLOBAL _CLIENTTASKLABEL 'Test'
GLOBAL _CLIENTUSERID 'ECF525'
GLOBAL _CLIENTUSERNAME 'xxxxxx'
GLOBAL _CLIENTVERSION '6.100.0.4180'
GLOBAL _EGNOTES NOTES
GLOBAL _EGSOURCE SOURCE
GLOBAL _EG_WORKSPACEINIT 1
GLOBAL _SASHOSTNAME 'localhost'
GLOBAL _SASPROGRAMFILE 'C:\Users\ECF525\Desktop\Test.sas'
GLOBAL _SASSERVERNAME 'Local'
AUTOMATIC AFDSID 0
AUTOMATIC AFDSNAME
AUTOMATIC AFLIB
AUTOMATIC AFSTR1
AUTOMATIC AFSTR2
AUTOMATIC FSPBDV
AUTOMATIC SYSADDRBITS 32
AUTOMATIC SYSBUFFR
AUTOMATIC SYSCC 0
AUTOMATIC SYSCHARWIDTH 1
AUTOMATIC SYSCMD
AUTOMATIC SYSDATASTEPPHASE
AUTOMATIC SYSDATE 25APR18
AUTOMATIC SYSDATE9 25APR2018
AUTOMATIC SYSDAY Wednesday
AUTOMATIC SYSDEVIC ACTIVEX
AUTOMATIC SYSDMG 0
AUTOMATIC SYSDSN WORK    MYDATA
AUTOMATIC SYSENCODING wlatin1
AUTOMATIC SYSENDIAN LITTLE
AUTOMATIC SYSENV BACK
AUTOMATIC SYSERR 0
AUTOMATIC SYSERRORTEXT
AUTOMATIC SYSFILRC 1
AUTOMATIC SYSHOSTINFOLONG W32_7PRO WIN 6.1.7601 Service Pack 1 Workstation
AUTOMATIC SYSHOSTNAME UPLCI098360
AUTOMATIC SYSINDEX 28
AUTOMATIC SYSINFO 0
AUTOMATIC SYSJOBID 5008
AUTOMATIC SYSLAST WORK.MYDATA
AUTOMATIC SYSLCKRC 0
AUTOMATIC SYSLIBRC 0
AUTOMATIC SYSLOGAPPLNAME
AUTOMATIC SYSMACRONAME
AUTOMATIC SYSMAXLONG 2147483647
AUTOMATIC SYSMENV S
AUTOMATIC SYSMSG
AUTOMATIC SYSNCPU 4
AUTOMATIC SYSNOBS 1
AUTOMATIC SYSODSESCAPECHAR 
AUTOMATIC SYSODSGRAPHICS 0
AUTOMATIC SYSODSPATH  SASUSER.TEMPLAT(UPDATE) SASHELP.TMPLMST(READ)
AUTOMATIC SYSPARM
AUTOMATIC SYSPBUFF
AUTOMATIC SYSPROCESSID 41DB6C1D06E27EFA4018000000000000
AUTOMATIC SYSPROCESSMODE SAS Workspace Server
AUTOMATIC SYSPROCESSNAME Object Server
AUTOMATIC SYSPROCNAME
AUTOMATIC SYSRC 0
AUTOMATIC SYSSCP WIN
AUTOMATIC SYSSCPL W32_7PRO
AUTOMATIC SYSSITE 50600035
AUTOMATIC SYSSIZEOFLONG 4
AUTOMATIC SYSSIZEOFPTR 4
AUTOMATIC SYSSIZEOFUNICODE 2
AUTOMATIC SYSSTARTID
AUTOMATIC SYSSTARTNAME
AUTOMATIC SYSTCPIPHOSTNAME UPLCI098360
AUTOMATIC SYSTIME 13:03
AUTOMATIC SYSTIMEZONE
AUTOMATIC SYSTIMEZONEIDENT
AUTOMATIC SYSTIMEZONEOFFSET 7200
AUTOMATIC SYSUSERID ECF525
AUTOMATIC SYSVER 9.4
AUTOMATIC SYSVLONG 9.04.01M1P120413
AUTOMATIC SYSVLONG4 9.04.01M1P12042013
AUTOMATIC SYSWARNINGTEXT
30
31         %_eg_hidenotesandsource;
42
43
44         %_eg_hidenotesandsource;
47

 

Thanks again for your support!

 

Kind regards,

Florent

Ask a Question
Discussion stats
  • 2 replies
  • 104 views
  • 0 likes
  • 2 in conversation