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 to open the SAS log. If stored process results are not returned as expected, the log may not appear either. So you do not know what happened. Rather than asking the SAS administrator to get the most recent log off the server, you can add a parameter to the URL path to see the log quickly.
From the SAS Stored Process Web Application, add the &_DEBUG=131 option to the end of the stored process path and press Enter.
The stored process runs and the log appears in the Web browser. You can scroll or search the log to locate errors or read the log messages. [Yippie!]
Note: When creating custom forms and chaining stored process forms, the subsequent forms might not work using this method. During the development process, you must add the debug option as a hidden value.
Learn More about SAS Stored Processes and Prompts
You can learn more tips and tricks for creating, debugging, and using SAS stored processes in the 50 Keys to Learning SAS Stored Processes book. It's a complete guide to SAS stored processes. Check Amazon for best pricing and quick shipping!
Latest posts by Tricia Aanderud (see all)
- Can SAS Visual Analytics Replace PowerPoint for a Small Business? - November 11, 2013
- User Groups: SESUG in St Pete Beach was Great! - October 27, 2013
- Data Management: Who cares about Big Data - October 18, 2013
- Data Visualization: How to Avoid an Epic Fail - October 10, 2013
- Dashboards: Review of Information Dashboard Design Second Edition - September 23, 2013