thinking about your options.... for a secure and tracable/auditble approach. On linux/Unix still running with a personal account the log will be created wirh that ownership. Kurt, you can hide that location hoping the user will not find that location, hiding away is not securing. The same could be doen at windows wiht Unc's and special ACL's being set. No real difference. The best security is by having users unable to do anaything. With normal advanced usages (data mining) you need sufficiënt access in a shell level. Linus, blocking xcmd is saying your are doing a LAMP approach. No SAS needed for that kind of commodity of IT. Agree on the server approach. Are there tools in place that are doing monitoring/audting as coomon services? Why not use those. Having the SAS logging framwork active? Maybe there is an option. http://support.sas.com/documentation/cdl/en/logug/67485/HTML/default/viewer.htm#p00ofr134yp6fjn1hubsnom3ra4t.htm There are a lot of appenders. system log files can get some information but are out of scope of the personal user. Going into DBappenders http://support.sas.com/documentation/cdl/en/logug/67485/HTML/default/viewer.htm#p0w1cv36n6ududn1gnzzkh6h8fr7.htm Sadly this doc's are telling to hard-code the user/password of the destination database.
... View more