<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SAS STP output in Config ... SASApp in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-STP-output-in-Config-SASApp/m-p/904261#M27568</link>
    <description>I would remove sassrv's permission to write to the SASApp directory to prevent this from being permitted.</description>
    <pubDate>Wed, 22 Nov 2023 17:02:10 GMT</pubDate>
    <dc:creator>gwootton</dc:creator>
    <dc:date>2023-11-22T17:02:10Z</dc:date>
    <item>
      <title>SAS STP output in Config ... SASApp</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-STP-output-in-Config-SASApp/m-p/903391#M27525</link>
      <description>&lt;P&gt;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 &amp;amp; % stpend)?&amp;nbsp; Is this controlled via config file or STP reserved macros?&amp;nbsp; (win 9.4 m7 x64 install)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;R&lt;/P&gt;</description>
      <pubDate>Wed, 15 Nov 2023 22:49:59 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-STP-output-in-Config-SASApp/m-p/903391#M27525</guid>
      <dc:creator>shoin</dc:creator>
      <dc:date>2023-11-15T22:49:59Z</dc:date>
    </item>
    <item>
      <title>Re: SAS STP output in Config ... SASApp</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-STP-output-in-Config-SASApp/m-p/903728#M27547</link>
      <description>&lt;P&gt;Hello&lt;BR /&gt;Often SAS procedures&amp;nbsp; produces graphics as png files. When no path is specified for these files they are dropped into the SAS App folder.&lt;BR /&gt;In addition to png files this happens with datasets too.&lt;/P&gt;
&lt;P&gt;One approach to resolve this is by changing the working directory to SAS Work Location.&amp;nbsp; The following link shows how to change the working directory&lt;BR /&gt;&lt;A href="https://blogs.sas.com/content/sgf/2018/05/18/how-to-change-your-working-directory-for-sas-with-the-dlgcdir-data-step-function/" target="_blank"&gt;https://blogs.sas.com/content/sgf/2018/05/18/how-to-change-your-working-directory-for-sas-with-the-dlgcdir-data-step-function/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 17 Nov 2023 20:35:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-STP-output-in-Config-SASApp/m-p/903728#M27547</guid>
      <dc:creator>Sajid01</dc:creator>
      <dc:date>2023-11-17T20:35:55Z</dc:date>
    </item>
    <item>
      <title>Re: SAS STP output in Config ... SASApp</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-STP-output-in-Config-SASApp/m-p/904020#M27559</link>
      <description>&lt;P&gt;Hi Sajid, thank you for your time and reply.&amp;nbsp; I do have the WORK location in my config files and I confirmed it via proc options as well.&amp;nbsp; That is why much surprised when I saw those png and (thank God) few *.sas7bdat.&amp;nbsp; Any other idea?&amp;nbsp; So basically sounds like it is a developer training thing.&lt;/P&gt;</description>
      <pubDate>Mon, 20 Nov 2023 21:40:13 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-STP-output-in-Config-SASApp/m-p/904020#M27559</guid>
      <dc:creator>shoin</dc:creator>
      <dc:date>2023-11-20T21:40:13Z</dc:date>
    </item>
    <item>
      <title>Re: SAS STP output in Config ... SASApp</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-STP-output-in-Config-SASApp/m-p/904260#M27567</link>
      <description>&lt;P&gt;Hello &lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/15279"&gt;@shoin&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;Asking each and every user to make changes to every code is neither practical not enforceable.&lt;BR /&gt;A better approach is to add the following&amp;nbsp; to the end of autoexec_usermod.sas for the workspace server on the SAS server.&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt; data _null_; 
      rc=dlgcdir("%sysfunc(pathname(WORK))");
      put rc=;
   run;&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;This will update the current working directory to the users work directory. Once the session terminates everything is automatically removed.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Nov 2023 16:54:16 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-STP-output-in-Config-SASApp/m-p/904260#M27567</guid>
      <dc:creator>Sajid01</dc:creator>
      <dc:date>2023-11-22T16:54:16Z</dc:date>
    </item>
    <item>
      <title>Re: SAS STP output in Config ... SASApp</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-STP-output-in-Config-SASApp/m-p/904261#M27568</link>
      <description>I would remove sassrv's permission to write to the SASApp directory to prevent this from being permitted.</description>
      <pubDate>Wed, 22 Nov 2023 17:02:10 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-STP-output-in-Config-SASApp/m-p/904261#M27568</guid>
      <dc:creator>gwootton</dc:creator>
      <dc:date>2023-11-22T17:02:10Z</dc:date>
    </item>
  </channel>
</rss>

