Hi @MariaD,   This thread caught my attention as it was an interesting request.  As @nhvdwalt pointed out, this is an OS issue and not so much as SAS issue.  However, I googled a bit and came across this thread on Stack Exchange.  It's been a long time since I had anything to do with AIX but I suspect that one of those solutions might work for you.  You might also consider configuring a Workspace server for explicit use by EM and using a variant of the 'nice -n -20 <sas>' for the processes that are spawned by that server.  If there is a specific group, the limits.conf might serve you better.  However, limits.conf and some of the other options will be system wide for that set of users and not just for EM.  For example, if they run any other process, it will run with the same priority as for EM with the limits.conf settings.  I would expect that their Sys Admins would be able to offer some advise as well.   =G= ... View more

SAS points to it's own private JRE so if you install a JVM elsewhere it should not interfere. I currently have at least 2 other versions of Java that we use for other apps and have not had any issues with SAS apps. This is in linux so if you are using Windows your mileage may vary. It might also interest you to know that I've added jolokia into the midtier with no apparent ill effects but this is not a supported configration but does give me direct access to the JVM without using a separate java. ... View more

Hey Jerry,   Could you clarify a point?  Are you planning to install an enterprise SAS instance with metadata server that the students will connect to then install the clients on the students laptops to have them connect to that environment or are you planning to install SAS Foundation, EG and EM locally on every laptop as well as the lab?  IIRC, EM will let you install a local thick client that can be used locally as well as let students log into an enterprise installation.  Local installs would require that SAS be installed on each laptop.  You will want to be sure your license allows you to distribute Foundation that way.  The local clients are only supported on Windows (except possibly Studio).   =G= ... View more

As an addendum to your du command, you will want to sort in to more easily see the biggest consumers:   du -sh /folder/* | sort -rh    This will list the folders fn decreasing order.  Just keep drilling down to narrow your scope (du -sh /folder/foo/* | sort -rh). ... View more

Recording a response file is something many might not realize the SAS Deployment Manager is even capable of.  Many likely have used that functionality with the Deployment Wizard.  So updating the licenses is one use case, there are many other opportunities as well.   =G= ... View more

Looking at the metadata logs may give you some helpful information but it probably won't let you know how many users are active on the system.  Once upon a time, there used to be an APM(?) package that you could download and add to your servers that would provide some helpful reports.  They may still be available via tech support (SAS uses Environment Manager in later versions).     It's been a while since I worked with SAS 9.2 but you may be able to look at the active sessions on the workspaces by logging into SAS Management Console and connecting to the Object Spawner machine (expand server manager, object spawner and right click on the machine name and select "connect") for each node (this is highly dependent on your topology).  Look under the "Options" tab for attrributes with CurrentRunningServers or CurrentServers for each node.  I'm not 100% sure if these are tracked in 9.2 but they may be.  Worst case, you can always count the number of sasexe processes on the Solaris server (which I'm assuming is where your workspaces live).  This will give you a rough idea of how many sas processes are running.  I would suggest seeing how many "SAS_work..." files are in your work directory but this may have stale content and/or nested SAS_work... files. ... View more

It would also help to know what version of SAS you are running, which solutions and what the operating system is.  Some of this information you may be able to get with Environment Manager and Auditing on newer SAS versions. ... View more

I had a siimilar issue recently for an unrelated project.  A little googling at the time turned up a few things to check...this doesn't appear to be a SAS-only concern.   Your Host OS is 64-bits (obviously is) Check that Intel Virtualization Technology and VT-d are both enabled in the BIOS. Ensure that he Hyper-V platform is disabled in your Windows Feature list.   If these don't help, you may want to check the Virtualbox forums to see if others fixed it.   =G= ... View more