Dear community,
I would be glad if you could comment on this "rather exotic" issue of mine.
The scenario is the following:
I started a program yesterday evening in order to let it run overnight.
The log is redirected to a file via
proc printto log="c:\directory-name\filename.log"; run;
Clumsy as I am, I had the following added to the program:
options nonotes nosource nosource2 errors=0;
So you can imagine, how informative my log is.
The program is still running and I suspect something suspicious is going on.
But looking at the "log" will not help.
Can I somehow "edge in"
options notes source source2 errors=20;
to fill the log with life again?
I do not want to terminate the program, for I do not have a "feeling" at which point the program is.
Maybe, something is really wrong and it is e.g. at 7%, or, I terminate at 99% and everything is lost.
I see, this is a very "special" constellation, having come into existence due to my sheer idioty.
But still, maybe there is some hope for me.
If not, I learn something about how SAS-program-processing works (hey, it is something).
Yours sincerely,
Sinistrum
I guess you ran it from EG?
But anyway, the only option you have is stopping/terminating the job.
Another reason why one should never reduce the information going to the log.
I guess you ran it from EG?
But anyway, the only option you have is stopping/terminating the job.
Another reason why one should never reduce the information going to the log.
Thank you for your reply.
I guess, "EG" means "Enterprise Guide"?
Then no, I have run it with base SAS (yes, there is a base SAS users as stupid as me out there).
I will terminate the program.
Are you ready for the spotlight? We're accepting content ideas for SAS Innovate 2025 to be held May 6-9 in Orlando, FL. The call is open until September 25. Read more here about why you should contribute and what is in it for you!
Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.