Could someone clarify what happens to SAS jobs on a server after Enterprise Guide has been closed? Normally, it seems that when you shutdown or terminate EG from the task manager that the SAS processes you initiated on the server are terminated. For example, if you've written a SAS program that writes output to a network location, the output is not created, even though the server could complete the process after you'd given the run command. But we've found that in some cases, processes can continue to run on the server, not creating output in fact but eating CPU cycles. At some point, the server crawls to a slow and the IT department needs to kill these runaway processes or even reboot the server. Can anyone explain how and when this occurs? We suspect it's related to EG being terminated using task manager while CPU-intensive processes like proc mixed are being run on the server. Perhaps there are sever settings that could prevent or correct this problem? We're using EG 4.3 with SAS 9.2, most client PCs are running WinXP, a few run Win7. Thanks for any help, John Hendrickx
... View more