Tag: Coding Tips

SAS Enterprise Guide: 3 Ways to Use the Note Feature

If you look at my desk, my addiction will present itself to you clearly.  I love sticky notes – any kind, color, or shape. My bottom desk drawer is full of notepads – some never used because I think they are too pretty to write on. The be…

SAS Stored Process: Debugging from the URL

Here’s an excerpt from “The 50 Keys to Learning SAS Stored Processes” book, which is 20% off until Dec 31. When Bad Things Happen to Good Stored Processes When the stored process fails, a standard error message appears with a button…

Code: Keeping Code in the Trunk

Last week while searching for a code snippet through several folders of information, I realized that the code was still on my old computer … ugh! One of my weekend projects was to organize my code examples somewhere –  I’m going to …

SAS Stored Process: Shake, Rattle, and a lil’ DelGobbo Style

One of the great things about attending user conferences such as WUSS is that you get to meet all kinds of fun and interesting people.  Vince DelGobbo is a witty, smart, and clever SAS developer, who also happens to work at SAS Institute.  Vince work…

SAS Stored Process: Benefits of Minimalist Programming

Minimalism SAS stored processes can do a lot.  While I haven’t taken on the life of a true minimalist, recently I have come to see the benefits of limiting my stored process source code to just one statement.  And the best part of this practice is, I can still do everything I want. When you create a stored process, SAS writes the source code somewhere (see Tricia’s post on where the code is stored).  Typically you enter the source code in the stored process wizard.  I am now in the habit of typing just one %INCLUDE statement in the source code, and I end up with a stored process window that looks like below.  I use the /source2 option to make sure the included code is written to the log.  Minimalist Stored Process The full stored process source code ends up as below, because SAS adds a bit of wrapper code: Minimalist Stored Process: Source Code The main code is DoSomething.sas.  It has the usual DATA steps, PROC steps,  macro calls, maybe even %INCLUDE statements to call other other sub-modules. Minimalist Stored Process: Main Code So what are the benefits? You can store the main SAS code (DoSomething.sas) wherever you want.  I’ve been writing SAS code for MUCH […]