12-18-2017 06:07 AM
12-18-2017 08:23 AM
12-18-2017 09:08 AM
12-18-2017 09:22 AM
So it looks that you either use a pooled workspace server or that all your metadata users point to the same OS account. You need to fix that, so that every user starts the workspace server session with their own userid.
12-18-2017 09:51 AM
12-18-2017 11:49 AM
12-19-2017 02:08 AM
I would add that in my case all metadata users point to the same OS account.
There you have it. Fix that. Everybody who needs a workspace server MUST have their own OS account, period. Not because SAS, but common sense demands it. Your troubles with the audit trail are just one tiny foreshadowing of all the problems you'll have in the future.
12-20-2017 06:39 AM
12-20-2017 07:27 AM
Thank you so much for your reply. So as I understand, the only one thing to audit "real" user (_CLIENTUSERID in my case) is to re-configure the whole environment.
It is such a pity that I cannot configure audit trial (for example change sysuserid to clientuserid) ... :-(
There's a very simple reason for that. The audit trail has to rely on the macro variable, and while &sysuserid is set by the SAS system at the initialization of any session, &_clientuserid is set only by some clients and not always there.
There are other reasons why usage of a generic user is considered, ahem, suboptimal. You cannot use any operating system tools for managing individual user workload (workload manager, filesystem quotas, ...), and the system itself has no means of tracking the "real" user behind any operation.
For something like the workspace server, usage of a common user is strictly forbidden in our company.