SAS 9.4M5 on Windows Server 2012R2, client access via EG 7.15 or SAS Studio 3.71 (mid-tier)
I've recently noticed old SAS processes remaining on our compute server and realised that this coincided with more people using SAS Studio. A bit of experimentation has got me thinking that this is because when users finish their sessions they are simply closing their browser session rather than logging off.
I can distribute a message asking people to remember to log off but chances are this will only be partly effective. Is there a way to ensure that these processes are terminated? I suppose I could run a daily search for SAS processes from earlier than the current day but that has the potential to kill bona fide long-running processes.
Thanks @gwootton. How would these settings affect people who are signed in but just not doing anything? A lot of our users start up SAS at the beginning of the day and just leave it idle for most of the time. I'd rather not have them being kicked out
I'm still reluctant to implement something like that. I can't be absolutely sure but I think there are users who will run things, go and do something else, and then come back and expect the contents of their WORK library still to be there. Although I suppose I could just make the change and then sit back and see how many yells of anguish I get!
Thanks for your suggestions anyway
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.
Find more tutorials on the SAS Users YouTube channel.