Hi experts,
I would like to request another possible alternative, which consists of saving the SAS logs (generally for all users on Linux) in which the user ID and the query being executed can be viewed. This way, we can track the analysis of a specific day and identify the user who owns the specific query.
We are currently trying to modify the sasv9.cfg file located in the path /sas94/sashome/SASFoundation/9.4. Inside the file, we add the following:
-LOGPARM='logconfig=/sasdatos/logconfig.cfg'
Now, when creating the logconfig.cfg file in the specified path, we had trouble configuring it since it consists of LOG= and LOGPARM=.
Could you please guide us with an example of how to do it step by step from the beginning? We would greatly appreciate it
Start here: https://documentation.sas.com/doc/en/bicdc/9.4/bisag/p02ybml1gyskc6n1jmk88w7se9o8.htm
There are already several alternative logconfig files provided; I took one of those and modified it to get a full server-side log of all code run from EG.
Hello @Jose7
IMHO these are two plausible options
1.Advise users to output EG logs to a common location. The user would be having read/write access to this location. The log should have the necessary details for to identify /associate the log with the user/program/server.
2.Another alternative is to enable workspace server logging. This would consume lot of disk space.
@Sajid01 wrote:
.....
This would consume lot of disk space.
Only if masses of code are run. I used server-side logging without issues. I also set up automated archiving of logs beyond a certain age, of course.
April 27 – 30 | Gaylord Texan | Grapevine, Texas
Walk in ready to learn. Walk out ready to deliver. This is the data and AI conference you can't afford to miss.
Register now and lock in 2025 pricing—just $495!
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.
Ready to level-up your skills? Choose your own adventure.