Windows grid display manager how to#
Windows grid display manager pdf#
Windows grid display manager upgrade#

Windows grid display manager pdf#

They also generated PDF files by calling Adobe Distiller and RTF / DOC files via DDE code. Many of our SAS programs directly invoked Windows commands and batch scripts to prepare raw data, such as unzipping input files received from vendors. Clearly, using SAS EG could not easily duplicate this successful model. Our scheduled batch jobs used a similar approach. The two commands guaranteed that each SAS session would start in the right folder, could access the correct files and libraries, and would produce various kinds of output in the right locations. The standard procedure for launching SAS was to use a Windows Command Prompt, type a command to set the environment, and then launch SAS with another command. The overwhelming majority of our SAS processing, be it for development, testing or production, was tightly integrated with our unique Windows file system structure tailored for clinical studies. This was at best a small learning curve, but we had a much bigger hurdle.

Windows grid display manager how to#

With the exception of a few users who had utilized SAS EG on our legacy UNIX systems, most of our SAS programmers did not know how to use SAS EG. Therein lay our essentially insurmountable problems. All the grid enablement features are built-in within SAS EG 5.1 checking a couple of boxes is all you need to go to the grid.

In preparing for the upgrade, we realized that SAS grid actually favors SAS Enterprise Guide as the user interface.

Windows grid display manager upgrade#

The plan was to upgrade from single-server SAS 9.2 to grid-based SAS 9.3. To solve the chronic resource contention issues and better prepare for future growth, we purchased the SAS grid software.

There were also huge batch jobs scheduled to run on the server for clinical data management. Our SAS programmers, statisticians, and other SAS users typically connected to the production server via Remote Desktop Connection and launched the SAS Display Manager for all their development, testing, and production needs. They both ran on Windows 2008 R2 and had attached local disks for data storage. INTRODUCTION In the pharmaceutical company where I work as a SAS administrator, there were two SAS environments: a production server and a validation server. There are a number of things you can do to make the transition to SAS grid as smooth and painless as possible, and your users get to keep their favorite SAS Display Manager. If you like to play a hero in your little world, this is your opportunity. This is utterly unacceptable to the user community because almost everything has to change in a big way. But after the contract is signed and implementation begins, you as the SAS administrator suddenly realize that your company-wide standard mode of SAS operations, i.e., using the traditional SAS Display Manager on a server machine, runs counter to the expectation of SAS grid – your users are now supposed to switch to SAS Enterprise Guide on a PC. Deploying a User-Friendly SAS® Grid on Microsoft Windows Houliang Li, Frederick, MDĪBSTRACT Your company’s chronically overloaded SAS environment, adversely impacted user community, and the resultant lackluster productivity have finally convinced your upper management that it is time to upgrade to SAS grid to eliminate all the resource problems once and for all.