Here are the most common errors that new developers make when creating a stored process.

Error #1: LIBNAME is Not Assigned

If you develop your stored process code in SAS Enterprise Guide, then the code uses your Connection Profile.  Thus it has access to all of your libraries.  When that code is moved to the stored process, you might find its generates a “LIBNAME not found error”. A best practice is to always add the LIBNAME statement to your stored process.  You can learn more about how the libraries are assigned  in the SAS 9.3 user documentation: “Assigning Libraries“. If you are still confused, I thought the SAS 9.2 documentation had a helpful description of pros and cons here.

You don’t have to read the entire background – just find the library connection you need to make as shown below.  Note: For this example, system library simply means it does not exist in the metadata so you call the library from the file system.

Error #2: Unexpected or No Results with Macros 

If you have added the %STPBegin and %STPEnd macros in your stored process, then you must ensure the Stored Process Wizard does not add it back. If you have added the macros and the wizard has added the macros, then you see where some interesting results might occur. The worsT part of troubleshooting the issue is that it can take several hours with the log to determine the issue. 

More Read

How Does Next-Gen SIEM Prevent Data Overload For Security Analysts?

Harvard Gets Access to Twitter Data Stream to Predict Foodborne Illness Outbreaks

IBM Brings Sophistication to Customer Analytics and Prediction

Data Analytics Plays a Vital Role in Teacher Verification Software

Do Predictive Modelers Need to Know Math?

Error #3: Prompt Always Uses the Same Values

Did your prompt work, but it keeps making the same choice no matter what you select?  For instance, you selected the East region but it returns the West region – no matter how many times you select it? You might want to double-check the code to see if you left the LET statements in it.  Many programmers test the prompts to ensure they work or create errors to confirm the prompt will fail.  If it’s a large stored process, then you may forget you did it.  That’s worth some more time trying to find why your prompt failed.  

This one has caught me more than once.

What Tripped You Up?

Did you have a funny or hair-pulling experience troubleshooting a SAS Stored Process?  Share it in the comments.