GuyA clarified his problem in a response to montura's insightful reply:
> On Jan 12, 2:02 pm, montura <montura...@gmail.com> wrote:
> > Anti-Virus.
> > The IT department left the default setting where every SAS source
> > and SAS dataset is scanned for virus content.
> > Welcome to the party.
> Do you think that's the issue? I don't know of any changes made, as I
> have two computers, each with SAS, both connected to the same network
> and only one has had this problem start today...
GuyA, I was thinking along the lines of montura, but you nixed that idea, above.
My "Plan B" thought was that you likely have a SAS client-server install and this is a network issue. But, your new information--that one computer doesn't have a problem while one does shoots that theory down in flames, too. So, if all SAS things are equal on both of those computers--same version of SAS, same SAS configuration, same SAS maintenance, etc., you need to look at the non-SAS things that may make a difference--e.g. does your errant computer need a defrag, is it running out of disk space, does it have some memory-crunching super app running on it that the other one doesn't, etc.
Some thoughts to... think about!
GuyA, best of luck in all your SAS endeavors!
I hope that this suggestion proves helpful now, and in the future!
Of course, all of these opinions and insights are my own, and do not reflect those of my organization or my associates. All SAS code and/or methodologies specified in this posting are for illustrative purposes only and no warranty is stated or implied as to their accuracy or applicability. People deciding to use information in this posting do so at their own risk.
Michael A. Raithel
"The man who wrote the book on performance"
Author: Tuning SAS Applications in the MVS Environment
Author: Tuning SAS Applications in the OS/390 and z/OS Environments, Second Edition
Author: The Complete Guide to SAS Indexes
A government that robs Peter to pay Paul can always depend
on the support of Paul. - George Bernard Shaw