SAS EG
Paper 265-2013
SAS Enterprise Guide® -- Implementation Hints and Techniques for
Insuring Success With the Traditional SAS Programmer
Roger D. Muller, Ph.D., Data-to-Events.Com, Carmel, IN
ABSTRACT
There are many configuration options available in SAS® Enterprise Guide® for both the product itself and the
included enhanced editor. There are also numerous software products from SAS® that may or may not be licensed at your site and greatly affect your workflow. Workflow options while developing the code are numerous and range from simple line-by-line execution up to and including the running of an entire process flow or project. Storage of SAS code under development also deserves careful thought. All of these topics and more are addressed to enable users to have a very thorough non-frustrating first-time experience with SAS Enterprise Guide. The presentation is aimed at users who have experience coding and running SAS programs. This presentation is a video presentation created using SAS Enterprise Guide 5.1 and SAS 9.3.
INTRODUCTION
Traditional SAS programmers develop SAS code in files and submit it for processing regardless of the operating environment (PC, Unix, etc.). SAS Enterprise Guide (EG) follows this model, but adds some unique additional
capabilities. This paper addresses setup, initialization and workflow ideas to smoothen and enhance the transition to the EG graphical user interface centered around a process flow window. Dual screen systems, split views and internal vs. external SAS code storage will be addressed. Certain features in SAS EG may either be hidden or
exposed with advantages to doing either. The number of process flows in an Enterprise Guide Project offers flexibility in constructing the total programming effort. Techniques for submitting developing code for step-by-step processing vs. the submission of entire project files is discussed. The video will address environmental settings for both EG itself and for the enhanced code editor. And lastly, the handiest key in EG, the F4 key, which is used to toggle back-and-forth between the current Process Flow window and the most recent window (program, data set, log, output, etc.) will be utilized.
This presentation is a video poster. The video will be referenced at the proceedings site for the 2013 SAS Global Forum and the author also maintains publicly available YouTube playlists. This paper will be very brief from an instructional standpoint and will only serve to partially overview the video content.
THE INITIAL SCREEN ONCE A PROGRAM HAS BEEN RUN
To create Display 1, Enterprise Guide was launched. A new project was started (File, New Project). A new process flow was started (File, New, Process Flow) and a new program was started (File, New, Program). The program could as well have been one that preexisted prior to this launch. This program was then ran. The concepts of project files, process flows and programs are all covered in Muller (2012) and Muller and Penix (2012) and will not be discussed further in this paper and video. The goal of this paper/video is to surface techniques and settings useful to the traditional file-based programmer to get up and running in the EG workflow.
The project name is noted in Display 1 (Item 1). There are two Process Flows (Items 2 and 3) shown in the Project Tree Window. The initial simple SAS program is shown in the project tree (Item 4). The actual code in this file is shown in a split window of the Process Flow (Item 7). Notice that the file name is shown as Item 6 at the top of that split window.
热门文档