Killer New Log Summary Feature in SAS Enterprise Guide 6.1!
Hey brilliant SAS Institute developers – I love your new SAS Enterprise Guide 6.1 Log Summary feature! When I was reading through the What’s New in SAS 9.4 for SAS EG 6.1 there were only a few entries. But BAM! the second bullet made me run over to the demo machine to see what I was missing:
improved programmer productivity with the new Log Summary window, which lists all the errors, warnings, and notes that were generated when the program ran, as well as related line numbers and a sample of the affected code.
Killer Log Summary Feature
Basically after running a program, you can visit the Log tab and click the Log Summary button for a quick view of what just happened. Seriously – look at the following graphic – the Log Summary area shows the number of Errors, Warnings, and Notes from the log. This extremely simple program only generated 3 Notes. Notice when I click on the line – it highlights the associated line in the log. How cool is that? [Yes – it’s okay to dance around!]
What if There are Errors in the SAS Log?
I’m sure most of you rarely make any coding errors, so just pass this tip along to those less skilled than you. I generated an error in the code to see what would happen. Of course the Log Summary buttons give me a count of the errors and warnings. However, those buttons also allow control of the detail – so if I click the Errors button the log is filtered to just show the errors. I can then click the Warnings button to also see the warnings.
This is a small log so it’s not as impressive as when you have pages, pages, and pages of logs and you need to understand the root of the issue. There should be a smile on your face now.
Other Neat Tricks
Here’s some other uses you may not have thought of yet.
Check the Observations
If you filter the Notes, you can quickly see the counts from the datasets. Many times I have to read in data where I start with 100 rows and I need to end with 100. This allows you to quickly view the log to check for the count instead of doing the Search/F3 dance through it.
Check Other Logs
If you need to check a troubled batch or SAS Stored Process log that was created separately, the Log Summary can handle it. Make sure the file extension is “.log”. From SAS Enterprise Guide, use the File>Open>Other to add it to your project. Very easy to see where things went wrong! [Need a log check program for batch?]
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)
- Seven Interesting Data Storytelling Examples - 2018-06-09
- Use Network Analysis to Understand Your Customers with SAS Visual Analytics 8.2 - 2018-01-21
- My 7 Favorite Features in SAS Visual Analytics 8.2 on Viya - 2018-01-14
- Designing Dashboards: Finding the Fantastic Five Colors - 2017-06-19
- Creating a Web Analytics Report in SAS Visual Analytics 8.1 - 2017-06-19