If you have a central, shared logs location for SASApp, then you could try running some SAS code. You can modify as needed, of course, but I do this to find out who owns a standard WorkspaceServer session that was grid-launched. There's probably a better way to do this, but this is how I do it: %LET SASCONFIG=/your/sas/config/location;
/*Retrieve long listing of work directory contents*/
FILENAME XCMD2 PIPE "ls -ltr &SASCONFIG./Lev1/Logs/*WorkspaceServer*";
DATA _NULL_;
CALL SYMPUTX('TODAY',PUT(TODAY(),YYMMDD10.));
RUN;
%PUT &TODAY;
DATA Details;
INFILE XCMD2 DSD TRUNCOVER;
LENGTH TEXT $512.;
INPUT @1 TEXT;
USERID = SCAN(TEXT,3,' ');
GROUPID = SCAN(TEXT,4,' ');
PID = SCAN(SCAN(TEXT,-1,'_'),1,'.');
DROP TEXT;
RUN; Note that we are running in a Linux environment, so you may need to change some things depending on your OS and setup.
... View more
![SASGF 2020 [Virtual] Attendee](/html/@A53A708409112314CE528E074D4C8C1F/badge_icons/badge_sasgf20_attendee.png "SASGF 2020 [Virtual] Attendee"){kind=icon}
