If you are just getting started with SAS stored processes, you might find the sample stored processes shipped with the SAS BI tool useful for learning some quick techniques. Here’s how to access the samples and a trial run. You can access the sampl…
Tag: Stored Processes
Troubleshooting a web file upload
Functionality to upload files onto the SAS server (from 9.2 on) is available using stored processes and an html input type=”file”. I introduced this topic last year in my blog post using the SAS Stored Process Developer Guide sample. Of course, it is n…
Prompts: How do I use a Date Range Prompt?
After some not-so careful consideration, I decided to take the SAS BI Content Developer exam. Some folks I know who have passed the exam recommended that I study how to work with prompts and stored processes. So I am making up examples and working through some exercise drills of my own creation (oooh … scary). I am noticing some of the features and nuisances of working with the Date Range prompts. When I started using stored processes several years ago, it was not quiet this easy to setup date prompts, so the prompts are a welcome improvement. In this example, a Proc Tabulate summarizes the sales by location and date. The Date Range prompt allows the user to select a custom date range between Jan 1995 and December 1998. This figure shows how the prompt looks and the results. Check if the User is Insane … I like this prompt because it does have some built in “sanity” checks. For instance, I tried to make the end date before the start date and it didn’t like it. You can see it generated an error message. This capture is a little dramatic with a date of June 1900. If using Jan 1996 […]
Updating your global style
Every six months or so I try to find a recent picture that captures who I am and what I am feeling. Loading this into my various social/online profiles in Twitter, SAS Community, Forums, LinkedIn, corporate internal, Facebook etc then take me a bit of …
Stored Process: How do I get to the Library? Libname Errors!
Eeeeek!!! Your stored process failed. It worked when in EG – how could this disaster have happened? If you check the log, you may see an error similar to the following about the Libname not being assigned. The library where you stored the data, in this case, MYLIB was either available to SAS EG but not widely known to the SAS BI system or maybe it has a different name in the metadata. To move forward, you need to add a LIBNAME statement that describes where the metadata is located to the stored process. So you would add the following to the code: LIBNAME name meta liburi=”SASLIBRARY?@name=’metadata_name‘ “; You have seen LIBNAME statements before – but wow this one has some extra goodies. My Enchanted Mouse Tricks You may be wondering how I knew what to assign the values – clearly it must be some kind of BI white magic. Yes, using my enchanted mouse in EG, I pointed-and-clicked my way to the answer. In the Server List, I located the dataset being used (SALES_CANDY_HISTORY) and noted the library name, which is Candy. If you review the Candy library properties, you can see some information about the library, where it is stored […]
Double, no triple check those stpbegin and stpend macros from Enterprise Guide
Be very aware of when the %STPBEGIN and %STPEND macros are & are not needed in your SAS Stored Process. When opening a stored processes directly from Enterprise Guide to make modifications, the ‘Include Code for’ option to reinsert these two macros is automatically turned back on. So even if you have turned it off previously, always make sure that if you do not need them the option is off.
Where is my stored process code?
As you register your stored process, you may notice that the stored process wizard incorporates your code in Step 2. Ever wondered where the wizard places this code?
In step 3 of the creation process, you are actually selecting a location and the f…
Editing .sas source code repository from 9.3 SAS Management Console
As I have previously mentioned, SAS 9.3 has some sweet new functionality for stored processes. The topic of the prior post was on storing .sas code for the stored process directly within the metadata and how to edit/access that raw code. Did you know t…