In his blog, Jared details the hoops one must jump through to convince SAS to run system shell commands (such as the X command and SYSTASK) from SAS Enterprise Guide. Here is the explanation: SAS Enterprise Guide is a client application, and SAS runs as a server application. When launched
If you deploy the SAS 9 environment on Windows, you may have multiple SAS processes running on a single box (metadata process, OLAP server, multiple workspace servers). Windows Task Manager doesn't provide a great way to distinguish one sas.exe process from another, but Process Explorer does. Process Explorer lets you
My new favorite typeface for programming is Consolas, a font designed for use with Microsoft Visual Studio 2005. I use it there, but I now also use it for SAS programming. It uses ClearType technology, so the "crisp and clean" benefits kick in only when you have ClearType smoothing enabled.
A colleague asked me to run a certain SAS program and then try to view the output in SAS Enterprise Guide. The output contained an SQL VIEW, and darn it, the application refused to open it, reporting only that the data "could not be opened." There was nothing wrong with
Let's say you use SAS Report format, the latest tagset supported by ODS. After all, it's the lingua franca of SAS BI applications, since it's also used by SAS Web Report Studio, SAS Add-In for Microsoft Office, and SAS Enterprise Guide. You've discovered how to use the report builder in