Hi, an end-user asked if it was possible for the log to refresh (say you have a multi-step, many hours long SAS job) while the job was running. For example: a database load. Presently (I believe) the log is only present at the conclusion of the job.
Hi,
In SAS Studio 3.5 (the first release where SAS Studio introduced background submit) the log was locked until the conclusion of the background submit job on non-Windows platform. In SAS Studio 3.6 (which has just been released) this issue has been fixed so the log is readable during the run on all supported platforms.
HTH
Try -logparm "write=immediate" on the commandline or in the config of the server process.
With EG, I see log updates every time a step or run block finishes.
If these are regular production batch jobs then you would be better off scheduling them via SAS Management Console. The SMC batch job logs are easy to monitor as you can specify a single directory where they are written and they get updated in near real time.
LSF is just one of the options. You could use OS scheduling with SMC at no extra cost.
Hi,
In SAS Studio 3.5 (the first release where SAS Studio introduced background submit) the log was locked until the conclusion of the background submit job on non-Windows platform. In SAS Studio 3.6 (which has just been released) this issue has been fixed so the log is readable during the run on all supported platforms.
HTH
Join us for SAS Innovate April 16-19 at the Aria in Las Vegas. Bring the team and save big with our group pricing for a limited time only.
Pre-conference courses and tutorials are filling up fast and are always a sellout. Register today to reserve your seat.
What’s the difference between SAS Enterprise Guide and SAS Studio? How are they similar? Just ask SAS’ Danny Modlin.
Find more tutorials on the SAS Users YouTube channel.