07-19-2015 10:28 AM
In your situation sas DI jobs on Unix SAS is installed on Unix not Windows.
The fist thing for working SAS on Unix is understanding Unix than getting access to by SSH on the same machine so you can see your processes running (ps).
As you need SSH the NOXCMD setting from SAS to Unix is humbug. It is a signal there is no alignment with your IT department. Start there...
07-19-2015 06:25 PM
First thing: You need access to the SAS log. If you're using DI Studio then you have access to the log within DI, if you're running your deployed jobs in batch then you need access to the file systems where the SAS logs get stored (SSH using something like WinSCP).
For the SAS logs to give you enough information you want options like "fullstimer" turned on, if interacting with a database you want also options "SASTRACE=',,,d' SASTRACELOC=SASLOG NOSTSUFFIX" set.
Very often poor performance comes from poor design/code so that's the first thing I would be looking into. What are the long running steps? Why are they long running? Could it be done more efficiently (eg. less movement of data between servers).
It can of course also be caused by environmental limitations. Here for a start: SAS(R) 9.4 Companion for UNIX Environments, Fifth Edition