Which version of operating system, SAS and Enterprise Guide? Take a look at the spawner log, maybe you can find a pattern. It could be that your server system kills inactive processes when under load. Or you see the results of intermittent network problems (is a VPN involved?) ... View more

The root error is "Physical file does not exist". Try to repair that (physical filename should end with .xml instead of .html) before advancing. ... View more

Alas, the performance of SAS's SQL when doing large table joins has proven so inferior to proc sort/data step sequences (epsecially when several are running concurrently) that we only use SQL where absolutely required (eg cartesian join). ... View more

As was already stated, you CANNOT change the title during execution of a proc or data step. You can just try to simulate it. One way to achieve the desired result is to generate the whole output manually with a data _null_ step. But this means you have to write the whole report syntax in eg html. Which takes knowledge in css, html and the intricacies of the put statement. ... View more

I think that SAS should at least give a note when this happens. ... View more

The error most probably comes from the DB2 ODBC driver. You might get a clue here: IBM DB2 10.5 Information Center for Linux, UNIX, and Windows Maybe the where condition is the culprit (numeric/char conversion?) ... View more

I have found through dire experience that the only half-way reliable process for importing/exporting Excel data is through csv. Everything else is dependent on Windows version, Office version, EG version, local setup of the PC, and time of day/season of year/gold price. If you are a SAS administrator/developer, don't get into the business of fixing Ballmer&Co's stupidities. ... View more

Web servers usually serve the requests with something like nouser/nogroup or nobody/nobody. Only the core process is started by root in order to use the privileged (< 1024) port 80/443. And, as the others said, the install user (and the one who will own the metadata server process) must not be root. ... View more

Please provide the offending code, it makes it much easier to find the right answer. Just supplying the error message without a log containig the offending code is usually not helpful. The probable reason for your error is that you try to write a dataset in the library containing the V6 dataset. Since this library uses the V6 engine, you have to adhere to V6 naming conventions, which means that variable names must not exceed 8 characters. Ht_A_pctl contains 9 characters. ... View more

SAS deployment manager is a graphic GUI and needs a X11 server to display on and get input from. Get an X11 server (eg Xmanager) running on your PC, enable X11 tunneling in your putty and your sshd on the server, and you should be fine. ... View more

Since you cannot change the title while proc print is running, and you placed the condition on values of the dataset to be printed, your problem is unsolvable. ... View more

The problem with R is that it works only in memory (unless you use special extensions), where one usually runs into limits quickly when operating with large real-world datasets. Scoring is usually done on the complete customerbase/whatever. That's where SAS's ability to scale (almost) indefinitely comes into play. If there are literally "hundreds of thousands" equally structured lines of code, then an approach where the code is manipulated automatically along some predefined may be of great help. This could be done in a sophisticated data step or by employing standard text-manipulating tools like awk. If the R source tree always looks the same and just the factors change, a customized filter to do the optimizations could lead to a completely automated process. ... View more

Since you do have a specific action for missing values: if you put that first, you can then drop all comparisons to missing values (.z). That may speed up the code, but it surely makes it easier to read. As Reeza said, put calculated, but basically fixed values into one constant, and leave the original code in a comment for clarification. I'm not sure if the SAS data step compiler is able to do such optimizations on its own. If you already checked for VAR2 <= 3.5, and there is no other breakoff value after that, the comparison VAR2 > 3.5 is unnecessary and will probably eat CPU cycles. A simple "else" is enough. ... View more