Signals on Linux and UNIX can be used to manage process execution. You could pause all execution of code in SAS Stored Processes by finding the process ID's of the Stored Process servers then sending them SIGSTOP to pause their execution. Once you want them executing again sending it a SIGCONT will get them running again. ... View more

Ubuntu 18.04 is not a supported distribution of GNU/Linux. Just out of curiosity why have you select Ubuntu 18.04 for your deployment?   Just incase this is useful to others when you deploy the SAS software to a system the Java interpreter used by that SAS installation is unpacked from the SAS software depot into the SASHome. The OpenJDK deployed onto a host if its installed is not the JVM used by the SAS software. The Java used by the SAS software is deployed under the SASHome/SASPrivateJavaRuntimeEnvironment/9.4/jre directory.   For your case @rwan1 unless you have a very good reason for needing to stick on Ubuntu 18.04 I would strongly advice deploying the SAS software onto a supported operating system. The SAS testing teams only test the SAS software on supported distributions so who know what edge case quirk you are hitting. ... View more

Can't say definitively but I can only imagine it's customer demand vs. effort to support more platforms. ... View more

My daily driver laptop is running Linux so I've got a similar conundrum. I wouldn't say I'm a SAS user though so keep that in mind when you consider my experiences. To help users debug issues I don't often need to actually use the clients. On the odd occasion I need to test a small bit of SAS code I'll ssh to a box with SAS installed on it then run SAS on the command line with sas -nodms and from there I copy/paste code snippets into my terminal from my text editor on my desktop. I use the SAS Management Console by SSH'ing to a box and running sasmc with X11 forwarding setup. If I'm writing a bit of code that is a bit more involved I'll login to SASStudio and interact with my code with my web browser. For the infrequent time I need to use a thick client I have various virtual machines running Windows with the clients on it. This setup is fine for me, I'm happy to seutp/install and support my own vms for this purpose. If this is going to be a large scale deployment of Macs you are going to need to support for users then Citrix might be something to consider, this would make patching the clients much simpler. A terminal server would fill the same function too. I use Citrix on my Linux workspace  for an application I spend a significant amount of my time in and it works well. ... View more

What is your WORK option set to in your sasv9.cfg? ... View more

I have submitted Tracking number 7612624054 @syedhisam that specific track appears to be dealing with hardware requirements. Not to worry though @alexal has got you covered and is doing some investigation to see where this Xmotfif requirement comes from. ... View more

Something to bring up with SAS Technical Support to dig into to get a definitive answer and perhaps prompt a documentation amendment. In my own installations of the SAS software I typically start with a fairly lean RHEL base then I install the xorg-x11-xauth package, this brings with it a bunch dependencies. On top of that I add libXtst, libXp, libXrender and libjpeg-turbo. With those packages deployed I can use all the GUI applications I need to use.   EDIT: I should add that I add all the other mentioned in the documentation also (numactl, libpng, etc.) ... View more

When I mentioned presentation virtualisation I was specifically referring to Citrix. From my experience with using Citrix across a very high latency link (300-400ms) there is no issues with the latency of web apps between the browser and middle tier of whatever apps because they are both close to each other. The only latency you get sometimes is with graphics being rendered and obviously scrolling in certain applications is quite jarring.   I can't speak much to using SAS client applications specifically but I'll speak to my own experience of using another desktop application over a connection to the other side of the globe. In this application I use I predominately edit text and navigate through various screens doing data entry and manipulation. Occasionally I'll need to use web applications over the Citrix connection also. The most interesting thing about this application I'm interacting with is that it responds orders of magnitude faster when using Citrix when navigating between screens when compared with running the application locally. This app is quite chatty to populate the various things on the screen. The only thing I do sometimes notice is there is a bit of latency with operations like cut and paste when you edit text. It takes a little getting used to but once you are used to it like I mentioned before it's perfectly usable.   If I was to think about how I use SAS locally myself I'm confident I could port my workflows to a Citrix connection on the other side of the world and for me it would not make much difference but I guess it depends on your users. ... View more

 -- Tried to post this yesterday but the forums went offline for maintenance --   XFS is a great choice. Red Hat have a paper on their site about tuning RHEL for SAS workloads. Their "bake off" put XFS on top in their case. https://access.redhat.com/articles/1593123   While I do love fast things and you should certainly listen to the advice @MargaretC and @alexal have given you, I'll play devils advocate for a bit. The difference based purely on the file system for most workloads is marginal. For a lot of workloads your users won't notice the difference. Depending on what your requirements are you might want to think about your choice considering the broader picture. What is ubiquitous across your environments, consider not just your SAS deployments. What are your system administrators and application administrators are familiar with? Do you have other constraints on your file system choice? As a simple example some backup solutions only support specific file systems.   The far more important thing to get right is the storage on which the file system resides. Getting your disks and volumes correctly setup to support your SAS deployment is far more important than the file system you pick. Spend some time to ensure you have the correct layout of drives, number of disks and spindles, and appropriate disk attachment method to the systems for the various types of storage you'll need. Getting the storage laid out correctly is where you will get the most bang for your buck. ... View more