BookmarkSubscribeRSS Feed

 

It seems that as SAS was removing access to the SAS launch command by pushing users off SAS desktop and onto EG, they also moved the option to unbuffer the log to the commande line.

 

In V6 we had command line option -$logflush, then program option UNBUFLOG in V7, then invocation option again in V9 with option LOGPARM.

 

Not having the option to unbuffer the log output means that when your SAS session fails, it is very likely that the last bits of log information, which are the bits of interest for investigating the failure, will not be available.

 

 

 

8 Comments
ChrisHemedinger
Community Manager

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.

ChrisNZ
Tourmaline | Level 20

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.

ChrisHemedinger
Community Manager

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. 

ChrisNZ
Tourmaline | Level 20

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

ChrisNZ
Tourmaline | Level 20

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

ChrisNZ
Tourmaline | Level 20

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

ChrisNZ
Tourmaline | Level 20

I still miss being able to disable the log buffer.

ChrisNZ
Tourmaline | Level 20

@ChrisHemedinger Is this obviously necessary option still not under consideration?