11-03-2014 05:34 PM
I have a program that uses proc sql to create several data sets. The program has worked fine in the past. Recently, I have run the program and noticed that the data sets created by proc sql appear to have been created in the work library based on log statements. The programs don't appear in my work library, however. This causes problems because when I run a second program that references the work data the program fails because the data sets are not found. If I run my code in sections, everything works fine and I see the data sets in work. Having to run the program piece meal slows me down. Any thoughts on what could be going on or a possible work-around?
I'm running SAS Enterprise Guide Version 5.1
The first table that is created has 408,240 rows and 1 column
The second table has 62,612,434 rows and 29 columns
Thanks in advance for your help.
11-04-2014 09:19 AM
Are you explicitly stating the work folder or are you allowing SAS to default to work? Posting your code would also help troubleshoot.
11-04-2014 03:07 PM
5.1 is having the options of parallel processing. Marvelous to increase speed.
As result every session has his own sas-work and it is not being shared among the SAS sessions.
For intermediate data for several nodes it is better using a defined dedicated staging-area (just a piece of storage like work)