SAS STP output in Config ... SASApp

[shoin]

I see many *.png files in SASApp location, run by sassrv and I would like to know where this is controlled or is this a pure developer control (%stpstart & % stpend)?  Is this controlled via config file or STP reserved macros?  (win 9.4 m7 x64 install)

R

[Sajid01]

Hello
Often SAS procedures  produces graphics as png files. When no path is specified for these files they are dropped into the SAS App folder.
In addition to png files this happens with datasets too.

One approach to resolve this is by changing the working directory to SAS Work Location.  The following link shows how to change the working directory
https://blogs.sas.com/content/sgf/2018/05/18/how-to-change-your-working-directory-for-sas-with-the-d...

[shoin]

Hi Sajid, thank you for your time and reply.  I do have the WORK location in my config files and I confirmed it via proc options as well.  That is why much surprised when I saw those png and (thank God) few *.sas7bdat.  Any other idea?  So basically sounds like it is a developer training thing.

[Sajid01]

Hello @shoin 
Asking each and every user to make changes to every code is neither practical not enforceable.
A better approach is to add the following  to the end of autoexec_usermod.sas for the workspace server on the SAS server.

 data _null_; 
      rc=dlgcdir("%sysfunc(pathname(WORK))");
      put rc=;
   run;

This will update the current working directory to the users work directory. Once the session terminates everything is automatically removed.

[gwootton · Accepted solution]

I would remove sassrv's permission to write to the SASApp directory to prevent this from being permitted.