SAS Studio issues forces user to terminate run sequence and lose libraries

[THE_HUMAN_UNIT]

Hello SAS Community:

I have been having log in issues and SAS studio operational problems for the past 3 weeks.

Taking hours just to get into SAS studio

Once in and compiling SAS code, program is constantly spinning (thinking mode) for hours without generating an output, forcing me to terminate the RUN sequence and lose my libraries and shortcuts created.  I did discover I can have the libraries re created every timee I log in, so I did choose that option.

Why is the program doing this?  Is it because too many users are online at same time? utilizing all of the bandwidth available for all users.  Not sure what the online user limits are.

Also having memory issues with code output.  Warning window opens up stating that the output files would use up more than 2GB of memory and it may cause other apps to not function properly.  When I choose "download anyway" option, I discovered that none of my Microsoft apps would work properly as told.  Is this an issue with my computer memory storage capacity or SAS?

When I choose "Terminate"  I lose my libraries and shortcuts. I have resolved this issue.

[hollandnumerics]

Hi THE_HUMAN_UNIT,

Could it be that the SAS program is in a loop?

Please can you post the program here, so that we can check it for issues?

............Phil

[tom_grant]

Hello,

Sorry you are having difficulties.  Are you using SAS OnDemand for Academics or Viya for Learners or local install of SAS?

[THE_HUMAN_UNIT]

Phil:

Yes it was a loop, I had set me seed length too long for PMM imputation and it would never stop running.

[hollandnumerics]

Hi THE_HUMAN_UNIT,

If you are looking for advice, then treat the 1st run of a program as a prototype by limiting the processing time to a minimum. This would have saved you losing code and information, and is especially important when the program is likely to run for an extended time.

Another tip would be to save the program BEFORE submitting it. I have been doing that much more recently, because my own programming platform has become a little more unstable. It has saved me quite a bit of programming time!

..........Phil