HI All ,
The workspace /stored process server are set to lunch by sassrv user credential .
So , Processes are created with sassrv user id in the application server . We get request from users to kill their jobs , so we have trouble in identifying the user and client they use .
How can we identify the user, client from a pid .
Since you are using token-based credentials to start SAS processes there is definitely no OS-based solution to doing this. The only possible way this might work is to turn on SAS's job-level performance monitoring, but I'm not sure if that would provide the pid to user linkage you need. Someone else more knowledgeable than me might know if this is possible.
Switching from token to user-based credentials would be an obvious solution.
As soon as you need SAS (to run code or display libraries/datasets), EG will start a workspace server, and use that for the session, unless you manually disconnect.
But you were talking about stored process servers (and showing the respective configuration) in your first post, so which is it?
Be aware that stored process servers are pooled and re-used by the object spawner. If user requests cause a STP to hang, you need to fix the stored process responsible for that. Indiscriminately killing processes that the spawner thinks are still there is not the correct way to solve your issue.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.
Find more tutorials on the SAS Users YouTube channel.