BookmarkSubscribeRSS Feed
Dswain1
Calcite | Level 5

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 . image.pngimage.png

 

6 REPLIES 6
SASKiwi
PROC Star

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. 

SimonDawson
SAS Employee
You will need to read the object spawner log. Inside the object spawner log it will have a message that will tie the user who request a workspace to the process.
Dswain1
Calcite | Level 5

Is the pid created once lunch sas EG or it create a pid for  every programe / flow we run in one SAS EG session  ?

Kurt_Bremser
Super User

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?

SASKiwi
PROC Star

@Dswain1  - As I understand it a single EG workspace session works in one PID. If you check out the SASWORK folder you will see that the PID is used in the naming of the _TDnnnn_xxxxxx user sub-folders.

Kurt_Bremser
Super User

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.

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 6 replies
  • 1770 views
  • 2 likes
  • 4 in conversation