07-05-2015 06:59 AM
Every new SAS session will create an unique fold for WORK library . Therefore there would not be a problem for many sas session .
Use the following code to check where is your WORK library.
%put &path ;
07-05-2015 10:24 AM
The SASWork is just meant for temporary data and it is physical unique for each sas session and user.
The OS is generating a unique ProcessID for each session that one can be found (obfuscated) as is date/time within the physical naming.
With Windows (Sas base) it is set the the users %tmp% personal setting normally located on a local disk.
On Unix there should be as file system being opened for all users read/write/execute (and sticky-bit !! on the directory mounted to that)
It is very well possible to see a saswork directory being creating in a saswork directory. As parallel code submission is possible with Eguide 5.1 multiple sessions are started for that not sharing the saswork.