Learning SAS? Welcome to the exclusive online community for all SAS learners.

SAS University Edition 3.5 VMWare Workstation 12 Player

Accepted Solution Solved
Reply
Contributor
Posts: 59
Accepted Solution

SAS University Edition 3.5 VMWare Workstation 12 Player

How do you create a SASUSER Library in SAS University Edition?

 

How do you specify a permanent library in SAS University Edition?

 

How can you save your SAS Data Files in a library other than WORK in SAS University Edition?

 

Why does SAS University Edition have the file storage restrictions / limitations in comparison with Normal SAS?


Accepted Solutions
Solution
‎07-29-2016 09:37 AM
Super User
Posts: 17,784

Re: SAS University Edition 3.5 VMWare Workstation 12 Player

All of your questions are answered here:

https://support.sas.com/software/products/university-edition/faq/main.htm

 

And in the Analytics U forum. You can limit your searches to this forum specifically.

 

Why does SAS University Edition have the file storage restrictions / limitations in comparison with Normal SAS?

 

I think the only limitation is the 2GB RAM on the VM, so you can't deal with large datasets in memory. This will affect some procedures but in general if used for learning you shouldn't have any issues. I've processed datasets that are several GB in relatively short time periods, but again not using any memory intensive procs. 

View solution in original post


All Replies
Super User
Super User
Posts: 6,499

Re: SAS University Edition 3.5 VMWare Workstation 12 Player

[ Edited ]

SAS UE is full SAS (at least for the modules that it includes).  There is not any limitation, other than the size of the virtural machine that you can use to run it on.

 

SAS UE already defines the SASUSER  libref for you, just like SAS always does. However it does point it at a readonly folder and also set the RSASUSER option (so SAS knows that SASUSER is readonly).  You should never count on having write access to your SASUSER library anyway.  If you launch two sessions of SAS at once you will get SASUSER set to readonly for the second one, so you might as will treat it as readonly most of the time anyway.

 

You can make a libref using the LIBNAME command.

 

You can map folders from your real machine to be visible in the virtual machine where SAS is running.  Read the documentation.

 

Contributor
Posts: 59

Re: SAS University Edition 3.5 VMWare Workstation 12 Player

The reason that I asked the questions is because the standard LIBNAME
statement did not work.

I could not find any reference or examples to help me solve this problem in
the Help File.

I do not necessarily want to create a SASUSER Library just one that enables
me to store my SAS Data Sets permanently.

BTW, I have never experienced any problems using SASUSER with normal SAS

##- Please type your reply above this line. Simple formatting, no
attachments. -##
Super User
Posts: 17,784

Re: SAS University Edition 3.5 VMWare Workstation 12 Player

 

 

What does "Did not work" mean? Did you get an error message?

 

Did you check this FAQ

 

http://support.sas.com/software/products/university-edition/faq/SAS_libname.htm

Solution
‎07-29-2016 09:37 AM
Super User
Posts: 17,784

Re: SAS University Edition 3.5 VMWare Workstation 12 Player

All of your questions are answered here:

https://support.sas.com/software/products/university-edition/faq/main.htm

 

And in the Analytics U forum. You can limit your searches to this forum specifically.

 

Why does SAS University Edition have the file storage restrictions / limitations in comparison with Normal SAS?

 

I think the only limitation is the 2GB RAM on the VM, so you can't deal with large datasets in memory. This will affect some procedures but in general if used for learning you shouldn't have any issues. I've processed datasets that are several GB in relatively short time periods, but again not using any memory intensive procs. 

☑ This topic is SOLVED.

Need further help from the community? Please ask a new question.

Discussion stats
  • 4 replies
  • 468 views
  • 0 likes
  • 3 in conversation