@Gaetan,   I had some free time a couple of weekends ago, and your post inspired me to write a slightly more elegant solution to this problem. I got a bit carried away, so now we've ended up with this utility called WORKtop, that not only periodically sizes and decodes your work&util directory names, but also gives you with a nice way of identifying the Metadata User owner of each workspace session (if they're configured to run as sassrv). SASWORK, UNIX top.... WORKtop. Get it?       I've put it all up on GitHub, so head over to https://github.com/boemska/worktop to read all about it and get the code. It's just a shell script which should work fine on Red Hat Enterprise Linux 6 and newer.   And @JuanS_OCS, thank you for the kind words about ESM! I'm very happy that our enterprise monitoring product is making your job easier and more enjoyable. The thing is, like you say, ESM is a big tool that does a lot more than just solve this relatively simple problem of monitoring SASWORK and UTIL directories, so using it would be overkill just to solve a problem that can be addressed with a few lines of bash. Although it's a valid suggestion as ESM does work perfectly on SAS 9.2 🙂   Anyway, I hope that someone finds this WORKtop utility useful. I had a lot of fun writing it.     Nik     ... View more

Amit,   If you're interested in a third party commercial solution, our Enterprise Session Monitor for SAS addresses the exact challenge you're having (easily finding the user or program that is currently filling your SASWORK/UTIL disk). It measures the SASWORK size for each session in real time and at any time gives you a breakdown of exactly how that space is being used with one click. It can also tell you how that space was being used at any arbitrary point in time over the last 4 weeks, as well as doing a bunch of other stuff like automatically associating workspace sessions to the metadata users that own them, letting users keep an eye on what resources the sessions they own are currently using on the server, allowing superusers to clean up unwanted sessions very easily, etc. etc.   Check out this screencast on Vimeo - relevant bits are around 50 seconds in, and then again around 3 minutes in. Product page can be found here.     If you were on a UNIX-based OS, as a workaround I would suggest a couple of script-based solutions similar to what Kurt has suggested. Turning on SASWORK compression is a good idea but I'd definitely want to profile your disk throughput performance and look at CPU headroom before flicking the switch in production.    Hope that helps.   Nik ... View more