I'm not sure if I understood, please specify. I can surf between directories on server but I'm not sure what to look for according to Your suggestion.   I just need a list with usernames from Metadata and to modify the sctipt in a way it displays output to stdout (for sending it to file) or writes the output to file.     ... View more

Thanks for the reply.   The main goal is to get users list from metadata daily and store the list. It means, all users who currently have an account in Metadata to access SAS. Output format is not so critical as I could manipulate with it later from Bash. So it doesn't matter if the script shows the list on screen and I send stdout to file or writes it directly to file whether it is csv or just text. The command <sashome>/SASFoundation/9.4/sas -sysin /<path-to-script>/<script-name>.sas -log /<path-to-log-files>/<logfile> generates a log file and result was pasted on previous posts.   This is not a Grid environment. We have 3 separate server (mid/meta, SASApp and SASApp_VA) but I think it's irrelevant as the users list query is done to metadata and I assume it writes all the output to the server where the script was executed.   Thanks!     ... View more

When I added the similar line to code in EG, at first if complained about bad path for "retail.csv" file. It tried to write the file straight to the server and was unable due to permissions. So i added:   %ds2csv (runmode=b, csvfile=<path-i-have-write-permission>/retail.csv); And it worked. A little step forward.   ... View more

Thank You for the reply.   I took the script posted on https://communities.sas.com/t5/Administration-and-Deployment/Querying-the-metadata-for-a-list-of-users-and-groups/td-p/391924 and added a line to the end of script so it looks like:       ... break after name / skip; run; %ds2csv (openmode=APPEND, runmode=b, csvfile=/opt/sas/data/fail.csv);   "Append" was just for testing. I'd prefer that each output goes to separate "yyyy-mm-dd.csv" format file but I'll deal with it later. I didn't specify "data" parameter as the documentation noted "if you omit the data set name, DS2CSV attempts to use the most recently created SAS data set". I'm not sure, maybe it already "forgot" the latest dataset after the last "run;" and the %ds2csv should be a bit earlier in the script? Because it complains:     95 %ds2csv (openmode=APPEND, runmode=b, csvfile=/opt/sas/data/fail.csv); ERROR: The connection to the X display server could not be made. Verify that the X display name is correct, and that you have access authorization. See the online Help for more information about connecting to an X display server. ERROR: Device does not support full-screen. ERROR: Errors printed on page 3.     Any hints?   Thanks!   PL     ... View more

I agree. If IWA mechanism is for MC, I'd expect full functionality (incl Validation). But that's what they said. ¯\_(ツ)_/¯ We did a Teams meeting and turned on debug log for Workspace Server but didn't see any lines about failed/success authentication when Validating while MC with IWA. Note that "browsing" SASApp and SASApp_VA server's folder tree was OK, so this means that the IWA worked with Metadata (logging in to EG) and also for Workspace server (browsing folders from EG). ... View more

The problem is still glowing underneath and today the same behaviour occured (temporary files at /tmp which is not on a separate partition so the / was filled for a minute or so). I asked the user about the procedure she said she was doing some manipulations with tables (which failed, of course). So to get a solution to the current topic, just as an update. I have turned on the Trace logging for Audit.Data.Dataset and there are lines talking about the problematic /tmp: 2022-10-05 11:09:13 WorkSpaceSRV_VA (199341): Audit.Data.Dataset.Open: TRACE [00000005] 2:sassrv - Libref=WORK Engine=V9 Member=ACCOUNT_NAME MemberType=DATA Openmode=INPUT Path=/tmp/SAS_work3FF400030AAD_sasva2/SAS_work 877E00030AAD_sasva2 2022-10-05 11:09:13 WorkSpaceSRV_VA (199341): Audit.Data.Dataset.Open: TRACE [00000005] 2:sassrv - Libref=WORK Engine=V9 Member=GRANT_NAME MemberType=DATA Openmode=INPUT Path=/tmp/SAS_work3FF400030AAD_sasva2/SAS_work 877E00030AAD_sasva2 2022-10-05 11:09:13 WorkSpaceSRV_VA (199341): Audit.Data.Dataset.Open: TRACE [00000005] 2:sassrv - Libref=WORK Engine=V9 Member=CLIENT_NAME MemberType=DATA Openmode=INPUT Path=/tmp/SAS_work3FF400030AAD_sasva2/SAS_wor k877E00030AAD_sasva2 2022-10-05 11:09:13 WorkSpaceSRV_VA (199341): Audit.Data.Dataset.Open: TRACE [00000005] 2:sassrv - Libref=WORK Engine=V9 Member=LIIK_NAME MemberType=DATA Openmode=INPUT Path=/tmp/SAS_work3FF400030AAD_sasva2/SAS_work8 77E00030AAD_sasva2 There is a Libref=WORK which has the /tmp as a destination. Now the question is how to change it. I already have these lines written to SASApp_VA/sasv9_usermods.cfg -set STPWORK /opt/sas/data/tmp -set TMPDIR /opt/sas/data/tmp -set WORK /opt/sas/data/tmp and ObjectSpawner2 restarted.   Is there any other variable I should add? I can't find the Work Library from Management Console (probably it is so called "system library"). Is it a bad idea to keep these STPWORK, TMPDIR and WORK at the same folder?   Thanks!       ... View more

That's a good idea. I haven't found an answer to how the variable for Pooled Workspace server temporary files location is called. Some results from Google mention that it might be TMPDIR or WORK. I'll keep searching but a hint would be much appreciated. Thanks! ... View more

The variable STPWORK is already set up <Lev1>/SASApp_VA/sasv9_usermods.cfg file. I know for sure it was set on August and later there has been restarts to the same server's ObjectSpawner. Still, there are some directories on the /tmp folder created even today. The names are like "SAS_util000100011FDC_sasva2" and "SAS_work42DF00011FDC_sasva2". Luckily, as there are previously mentioned directories, lsof shows the process number and it is a child process of ObjectSpawner:   $ lsof | grep /tmp/SAS_work42DF00011FDC_sasva2/ sas 73692 sassrv 21uW REG 253,0 0 16778272 /tmp/SAS_work42DF00011FDC_sasva2/sas.lck $ ps axfu [--8<--] sas 72258 0.0 0.0 113288 1488 ? S Sep14 0:00 /bin/sh -p /opt/sas/config/Lev1/ObjectSpawner2/ObjectSpawner.sh start2_tag sas 72268 0.0 0.0 880496 23832 ? Sl Sep14 0:06 \_ /opt/sas/home/SASFoundation/9.4/utilities/bin/objspawn -dnsmatch somehost.domain.dn -sspi -sasSpawnerCn Object Spawner 2 - sasva2 -xmlconfigfile /op root 72269 0.0 0.0 21504 1328 ? S Sep14 0:00 \_ sasels 7 4 8 2 f5019 root 72280 0.0 0.0 70540 2716 ? Ss Sep14 0:00 \_ /opt/sas/home/SASFoundation/9.4/utilities/bin/sasauth root 73684 0.0 0.0 70540 2720 ? S Sep14 0:00 \_ /opt/sas/home/SASFoundation/9.4/utilities/bin/sasauth sassrv 73685 137 57.7 516571112 456745408 ? Ssl Sep14 2037:28 \_ /opt/sas/home/SASFoundation/9.4/sasexe/sas -memsize 0 -cpucount ACTUAL -noterminal -noxcmd -netencryptalgorithm SASProprietary -metaserve root 73824 0.0 0.0 21504 1168 ? S Sep14 0:00 | \_ saselssrv 13 10 14 2 823cf -classfactory 440196D4-90F0-11D0-9F41-00A024BB830C sassrv 73692 0.0 0.1 3239652 1488804 ? Ssl Sep14 0:29 \_ /opt/sas/home/SASFoundation/9.4/sasexe/sas -memsize 0 -cpucount ACTUAL -noterminal -noxcmd -netencryptalgorithm SASProprietary -metaserver root 73823 0.0 0.0 21504 1168 ? S Sep14 0:00 \_ saselssrv 13 10 14 2 f483e -classfactory 440196D4-90F0-11D0-9F41-00A024BB830C   So there must be some other variable. ... View more