An Idea Exchange for SAS software and services

Comments
by Community Manager
on ‎08-03-2016 12:21 PM

With Log4SAS and the SAS logging facility, you can capture that workspace log if you need to diagnose issues.  Use the ImmediateFlush option for whatever Appender you've configured in the logging.  Doc on the Logging Facility is here.

 

Workspace Logging isn't something you'd have turned on all of the time, as it would accumulate lots of output in a large multiuser environment.  But when diagnosing problems it's extremely useful.

by PROC Star
on ‎08-03-2016 05:41 PM

Thanks for your reply Chris. The Logging Facility requires the involvement of the SAS administrator. I don't have any more access to him than I have access to the command line (and I don't want to ask for a SAS environment change). When needed, proc printto used in combination with option unbuflog did a fine job of capturing SAS's last breath with a simple line of code. I can't image why it's been removed.

by Community Manager
on ‎08-04-2016 08:57 AM

The UNBUFLOG option was removed, but replaced with:

 

-logparm 'write=immediate'

The LOGPARM option, as far as I can tell, provides a lot more flexibility. 

by PROC Star
on ‎08-04-2016 05:29 PM

As stated, LOGPARM is useless to EG users since they can't access the command line.

by PROC Star
on ‎01-18-2017 05:08 PM

 Any news on this front? It is still a pain to see EG die and miss the latest part of the log.

by PROC Star
on ‎02-09-2017 09:19 PM

I still miss having an up-to-date/complete log when killing EG processes.

by PROC Star
on ‎04-18-2017 02:17 AM

I still miss being able to disable the log buffer.

Idea Statuses
Top Liked Authors