I cannot get SAS Enterprise Guide 8.2 to create a log when I run programs.
I have:
1) turned on the log in the Project window>Project Log
2) turned on the log in Tools>Options>Application Logging
3) tuned on the log by right clicking the name of my project in the Project window>Properties>Project log
but none of these solutions works. I still get no useful log information. Only output similar to the below appears in my log whenever I run programs:
Project Log turned on at 11/16/2020 at 1:40:21 PM
Log for "p301a03.sas" run at 11/16/2020 1:44:49 PM on Local
Top of Step - Iteration #1
Top of Step - Iteration #2
Top of Step - Iteration #3
Top of Step - Iteration #4
Top of Step - Iteration #5
Top of Step - Iteration #6
Top of Step - Iteration #7
Top of Step - Iteration #8
Top of Step - Iteration #9
Top of Step - Iteration #10
Top of Step - Iteration #11
Top of Step - Iteration #12
Top of Step - Iteration #13
Top of Step - Iteration #14
Top of Step - Iteration #15
Top of Step - Iteration #16
Top of Step - Iteration #17
Top of Step - Iteration #18
Top of Step - Iteration #19
How do I turn on the log so that it creates output that is actually useful? The current output has no portion of my program, no notes, and no comments.
Next things I would check:
Look in your program for the setting of options NONOTES and NOSOURCE in the code.
Thanks - I checked and neither of these options is in the program.
Next things I would check:
This was it! There was an autoexec file from a previous workstream that had the NONOTES option. Once this was fixed, the log output properly.
Thank you so much!
Application logging is for EG itself, not for the SAS programs you run in EG. You normally only switch this on when diagnosing problems with EG.
Does the LOG EG tab for any program contain all source statements, notes, warnings and errors?
The log tab doesn't include any source statements or notes at all.
The log only includes warnings and errors (if any) as a single line, instead of within the working code (i.e. the log looks nothing like base SAS log).
@igibson246 - Then try adding: options source notes; at the start of the program. Does that add both source statements and notes to your SAS log tab after re-running?
SAS Innovate 2025 is scheduled for May 6-9 in Orlando, FL. Sign up to be first to learn about the agenda and registration!
SAS' Charu Shankar shares her PROC SQL expertise by showing you how to master the WHERE clause using real winter weather data.
Find more tutorials on the SAS Users YouTube channel.